Originally posted by jlittle
View Post
When it comes to my data on this critical server, it's all either old and new media collected over time, or backups of what the users on my network think is worth saving either via automated backup problems like deja-dup or simply copies to their server directory. So rolling back of snapshots would never be useful on that server. There is never any experimenting on that server. One of the advantages of running a LTS version of *buntu is I've never had an OS security patch or system update not work out. You can't say that about my lab Archlinux system. Those rolling releases need fixing from updates all the time. Playing with Arch keeps my production stuff on LTS *buntu.
Based on what happened to me yesterday, I think your critical data backup and restore scheme needs to factor in how it will work in a panic situation. Remembering how to replace snapshots under those situation could be problematic and lead to mistakes. I found this out my having one of my test systems start running a muck and deleting files, but I forget my backup server was attached via SMB/CIFS and the mount point cause the test system to start walking some of those backup directories.
Luckily all those file are on my Cloud server, IDrive.com. So I spent the last 12 hours restoring ~500GB from my online backup. Lots of fun and panic.
So I think I'm going to reserve btrfs with snapshots to my daily driver PCs and there the snapshot rollback makes sense. More likely to need to rollback a recent install or update. Critical data is still on the server for those PCs
Leave a comment: