@mr-flibble Well, problems with a reboot during backup sounds not very userfriendly. I can’t rely on a user to not shut down his computer after he has copied a large amount of data to the computer (for example from a digital camera) until backup has finished its job.
@drwtsn32 I wouldn’t want to run a canary release, the documentation is pretty clear about this.
@ts678 I understand the difference in the design of sersion 1 and 2. The problem I apparently run into with Duplicati 1 was most probably a chain of incremental backups, which was broken somehow and I ended up with an incomplete set of data, and that was AFTER I spent a lot of time with manual disaster recovery.
So I thought about the definition of “production”, in my case, I need a solution to backup two or three windows client to an scp-server (some commercial software charges extra for scp or doesn’t support it at all). I my scenario, I would define the following points for production ready software.
1: It needs to run reliably without user interaction and/or regular manual control by the user on the client computer (if there is a real problem, the user should get an alert).
2: After an initial local sync, it needs to be able to make regular backups over a slow uplink without regular full backups (some of the software I evaluated can’t do this).
3: It needs to be able to restore all user data after the ssd/hard drive of a client computer stops working, with only server credentials and encryption key at hand (Even if the last full backup was years ago).
4: It needs to have some history of backups. I don’t need to be able to restore every single day for the last decade, but again, if the initial backup was done 5 years ago, I still need to be able to make a full restore of last weeks data, if the SSD stops working.