![]() To restore, I would create a new pool on the target if there wasn't already one, and then use the restore command of zfs_uploader or otherwise zfs recv and the snapshot and related data manually, and write it to the poolk as a new dataset (Or addition to an existing one) I have to restore the entire dataset (Typically a folder, like your homefolder or a specific service may have its own dataset) Duplicacy vs arq full#One disadvantage of the full ZFS setup is not being able to retrieve a single file from your backup. I would have to reformat my disks thoughīut how do you restore the data on another system? For example if you want to restore just something on say a Mac? I would have to reformat my disks thoughīut how do you restore the data on another system? For example if you want to restore just something on say a said: Interesting. If you don't use ZFS, don't sweat the details, just use Borgmatic and be happy. ![]() If you don't use ZFS, don't sweat the details, just use Borgmatic and be said: what is the advantage of zfs snapshots over regular backups? If you already use ZFS, then you should look into increment snapshots and zfs send/ zfs recv or the above zfs_uploader project for making backups from it. I just generally love using ZFS to manage filesystems and the data within them, it would be way too exhaustive for me to say everything I love and use about ZFS here. You have no overhead searching through every subdir for changed files, since ZFS is already tracking that and can make a snapshot in an instant.Īnd ZFS has compression (and encryption if needed) built-in, so as long as you remember to keep it when sending the backup you get those benefits without aditional overhead each and every backup. This results in much faster backups since it uses the equaly speed of your disk. You don't need to crawl through every subdirectory and send every (changed) file one by one, you can just stream the however-many-GB snapshot as one. The two times recently that I've needed to restore anything (one was due to filesystem corruption, the other due to human error) all was said: what is the advantage of zfs snapshots over regular backups?įor real though, mainly that ZFS snapshots can be sent as blocks of data rather than a set of files. I might get around to improving it some day, but it works well enough. In my case the backups locations scan and verify checksums and send alerts on unexpected changes to protect from corruption due to bad drives or my error, checksums of the latest snapshot are also verified against live data (ignoring files modified recently, to reduce false positives), some VMs have a low-spec mirror that automatically wipes data and restores from latest backup (errors sent as alerts, and I manually check they have recent data occasionally) so I know the restore process is solid (these mirrors are not on the same server as what they mirror, so at a pinch they could be given more resource and with DNS changes made active in the event of an issue that fully takes out the original).Īll manually scripted, which can be a faf to maintain. How do you test your backups? (which can be as important as taking them in the first place) A couple of important keys are backed up physically (QR on “indestructible” paper, usually stored away from anything with easy access to what they unlock) for extra paranoia. A small selection of important stuff (keys, some personally significant data) also copied to removable media. Everything encrypted at rest (not that I have anything particularly sensitive). Everything covered by RAID1 or similar either using multiple physical drives or the provider promising the same (RAID is not a backup solution, but it does reduce the risk of needing to rebuild/restore due to hardware issues). A third resource pulls data from one of those without being able to connect to the sources or vice-versa as a soft-offline backup. Everything I can't re-obtain easily: rsync to two off-site locations, hard-linked snapshots are kept so I don't just have the latest version of content. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |