Hi, I am trying to design an effective backup for my personal data. I’ve looked at a few tools like perkeep and duplicity, and restic I like restic because it seems straightforward to use and also has powerful features like tags and FUSE support.
I don’t like the “foot-guns” that are provided by “forget” and “prune”, so my first question is: does running the rest server in “append only” mode disable these features of the client?
this is the setup I’m thinking about creating:
- run restic server “append only” mode on a zfs NAS (freenas probably, or just ubuntu with zfs) on my local network.
- copy backup to s3
- move older snapshots to glacier
duplicity has the concept of doing a full backup after some period of time, to protect against potential bugs in the “backup chain”, the idea being if there is some flaw in the incremental backups you would lose everything after that point in the incremental snapshots. Does restic support this, or is this even necessary? i.e. is restic designed in a way that this is unnecessary.
should I use rclone to sync the backup files to s3Z or, somehow copy snapshots of the zfs file system to s3. or, use restic to back itself up to s3 somehow. not sure what the best approach here is. my goal here is to have local and remote backup, and also be reasonably protected against ransomware.
for moving files to glacier, not sure if it is possible to identify “old snapshots” in the way restic stores its incremental backups on disk, so not sure if this would be possible.
Reason I want to run the rest server locally is because the cost of block storage (EBS) is, in my opinion, prohibitively expensive