I have set up backups on my working machine.
-
Today I mistakenly deleted the file I was working with on the last few months. On Ext4 FS, so I got some new white hair while experimenting with the r-linux recovering tool.
Advice: on Ext4 most probably the name of the file is lost, but date of the inode might be intact, so sort by time and look for your data in those thousands of inode76569u468 files. Better than just straightforwardly losing the data though.
Now I have automatic backups.
-
Today I mistakenly deleted the file I was working with on the last few months. On Ext4 FS, so I got some new white hair while experimenting with the r-linux recovering tool.
Advice: on Ext4 most probably the name of the file is lost, but date of the inode might be intact, so sort by time and look for your data in those thousands of inode76569u468 files. Better than just straightforwardly losing the data though.
Now I have automatic backups.
Now I have automatic backups.
Nodding approvingly
-
Today I mistakenly deleted the file I was working with on the last few months. On Ext4 FS, so I got some new white hair while experimenting with the r-linux recovering tool.
Advice: on Ext4 most probably the name of the file is lost, but date of the inode might be intact, so sort by time and look for your data in those thousands of inode76569u468 files. Better than just straightforwardly losing the data though.
Now I have automatic backups.
Today my working machine behaved weirdly after reboot, when I needed to make small changes fast, instead 3 hours of playing with usb drives, live isos, faulty nvme, obscure btrfs invocations. Backups would have saved me at least an hour. (I want to say that immediately after resolving those issues I've made and configured regular backups, but that would be a lie)
-
Today my working machine behaved weirdly after reboot, when I needed to make small changes fast, instead 3 hours of playing with usb drives, live isos, faulty nvme, obscure btrfs invocations. Backups would have saved me at least an hour. (I want to say that immediately after resolving those issues I've made and configured regular backups, but that would be a lie)
I want to say that immediately after resolving those issues I’ve made and configured regular backups, but that would be a lie
Do it now. Yes, right now. It is a 30-minute adventure: rsync here, some script there... And it will inevitably save your ass eventually.
-
Today I mistakenly deleted the file I was working with on the last few months. On Ext4 FS, so I got some new white hair while experimenting with the r-linux recovering tool.
Advice: on Ext4 most probably the name of the file is lost, but date of the inode might be intact, so sort by time and look for your data in those thousands of inode76569u468 files. Better than just straightforwardly losing the data though.
Now I have automatic backups.
Two kinds of people. Those that have backups and those that haven't lost data yet. Or almost lost.
Now test your restore regularly
-
Two kinds of people. Those that have backups and those that haven't lost data yet. Or almost lost.
Now test your restore regularly
Any tips for testing? I use free file sync. So far my best idea is to write a script to compare md5 hashes of the source and backed up file (if that's not already an option in FFS)
-
Any tips for testing? I use free file sync. So far my best idea is to write a script to compare md5 hashes of the source and backed up file (if that's not already an option in FFS)
I create daily timestamped files on the datastores that are involved in the backups and have a script that restores specifically those files from the backup and compares the content. If that succeeds, the backup is considered working. Its not perfect, but it's fast and automated.
