I do the backup with a script I put together. The systems being backed up are all Linux.
There's no automatic re-sync. If a file is lost it can be restored. If an entire disk is lost in one of the backup clients, the client would have to be re-built with a new disk, then a restore performed to recover the data. If one of the backup targets was lost, it would have to be replaced, then backup "sets" (collections of backups) copied to it from another target.
A couple of times I've tried a home "DR" excercise. I pretend the main PC is completely lost, along with the password archive, then try to recover from there. In the real scenario you would probably start by buying a new PC or disk. For testing I've recovered into a Raspberry Pi and got a usable desktop with all my data present. Throws up some interesting issues eg. with passwords. No PC, no password manager/archive available. Even the backups are password protected, so at least one password has to be remembered some how.
There's no automatic re-sync. If a file is lost it can be restored. If an entire disk is lost in one of the backup clients, the client would have to be re-built with a new disk, then a restore performed to recover the data. If one of the backup targets was lost, it would have to be replaced, then backup "sets" (collections of backups) copied to it from another target.
A couple of times I've tried a home "DR" excercise. I pretend the main PC is completely lost, along with the password archive, then try to recover from there. In the real scenario you would probably start by buying a new PC or disk. For testing I've recovered into a Raspberry Pi and got a usable desktop with all my data present. Throws up some interesting issues eg. with passwords. No PC, no password manager/archive available. Even the backups are password protected, so at least one password has to be remembered some how.
Comment