Some files would be expire the lock for some time before the next prune to relock them and would be vulnerable during that time. So, after every prune, it would need to relock any files that are not locked (but ONLY files that are not locked). Since duplicacy reuses existing chunks forever, you don’t know how long to lock them for. Every prune will try to delete these, and eventually it will work.) (Or don’t worry about this issue at all, and silently ignore lock errors when deleting, knowing that eventually one day, the delete will work. Just don’t set any pruning for less than however long the lock period is. Pruning / deleting files from the backup. The old ones can be deleted out as their locks expire. It should always copy the highest numbered file to a new one.

This could be fixed by using a new config file copy every time, and deleting the old config files after the lock expires.įor example, instead of using config.data (or whatever), you would use Looks like they finally moving in the right direction with object lock support…įor this to work in duplicacy, basically you would have 3 issues to deal with:Īny duplicacy config files that get changed during every backup. I also emailed Backblaze about recovering files in case of rogue action - and was told that no such option exists. Then I discovered - the price is not too bad and free 7 daily immutable snapshots are a great option. I wanted to set things up so the client only does backup and prune is done on sever after temporary resetting immutable attribute for the duration of the operation. I played around with locking destination folder with immutable attribute on Linux - but it broke the backup: This may become very complex, unfortunately. If object is locked, delete will fail - In this case Duplicacy would need to account for this during prune operation and only delete files when lock attribute expires.

Luckily, backup vendor was able to restore from backup. I speak from experience in recovering friend’s business from such attack… Attackers discovered backup software and deleted all files. If you keep permission to delete files, you will not have any protection - when ransomware strikes, people who launch attack do appropriate work to find all remote backups and delete them.

Veeam backblaze