#Cobian backup faq full#
#Cobian backup faq verification#

If no issues occur, it will probably be вЂњquickerвЂќ, however thatвЂ™s a bigger issue for bigger backups. Reasons for a backup probably donвЂ™t include вЂњquieterвЂќ unless something goes wrong on the recreate and it gets noisy.

Backup duplicati database: is it better or doesnвЂ™t matter? provides another statement about when it helps, and IвЂ™m still thinking intentionally deleting it is contrary to the expected usage. Back up the configuration somewhere other than Duplicati to use for getting Duplicati back if a disk gets lost.Дatabase backup is not as easy. Starting with the easier question, backing up the configuration starts with Configuration -> Export on the job menu, and this merges in the default options on the global settings, but omits non-job stuff like UI password. Losing a database is painful, but your plan seems to demand intentional deletion.Дuplicati works best backing up to a continuing database and destination, and your wish is kind of oppositeвЂ¦ The retention policy idea in this topic and elsewhere refers to handling backup versions from a continuing job. Unless you backup the local job database, recovery from parked backups will have to do extra work building a partial temporary database. The job schedule is kept in the server database, and might put up with this. monthly) could probably be cobbled together with enough scripting and maybe some tools to copy off the backup files, The DELETE command with вЂ“allow-full-removal can probably empty out destination files, and file deletion can delete the local per-job database.

#Cobian backup faq full#

Making a full from-scratch backup, copying it elsewhere, and repeating the process periodically (e.g.

You can adjust the amount higher by setting вЂ“backup-test-samples or you can force a (likely time-consuming) test of as many files as you care to do, using The TEST command.

#Cobian backup faq verification#

Heavy verification can ensure it went in right, and some verification of this and other destination files happens automatically by default on every backup. The first backup is most different in that itвЂ™s typically larger, thus it produces more destination files to damage.

Ideally you would periodically do heavy verification or a test restore. Backing up to different destinations using different software would be safest. Even a complete backup gets damaged if the destination gets damaged.