2 ms·
The whole scheme could use some improvements, tar.gz feels like a bad tool here. 1. If you can, use btrfs/zfs/lvm snapshot and skip the waiting completely. The
by viraptor 4y ago
The whole scheme could use some improvements, tar.gz feels like a bad tool here.
1. If you can, use btrfs/zfs/lvm snapshot and skip the waiting completely. There's no point in duplication.
2. If you do want the copies, use something that can do incremental backup instead. For example Borg can both compress and deduplicate and on top of that will only copy the changes, not the whole directory.
3. (optional) If you're into running custom latest software, you can save some time by using nixpkgs instead, which will also ensure you don't risk collisions in /usr/local. (takes some upfront time investment though)
- tuatoru 4y ago> There's no point in duplication. Duplication is precisely the point of backups. Well, multiplication preferably, more than duplication. The old chestnut is that 99% of restores are due to user error. There's still that 1% rump, though.
- viraptor 4y agoIn general sure, but not in this context. The author specifically says this is a short term copy done before installation, so it's more of a restore checkpoint than a proper backup. The use case is: > With a handy /usr/local archive, if something goes crazy wrong during my new install, it’s easy to revert.
- smeagull 4y agoYou know what I like about tar.gz? gzip is often a transparent compression layer on some tools, like say Athena. Tar is a simple concatenation of files + header. Therefore, even though Athena/Hive/Presto doesn't handle tar, I can use tar (or grep) to search the files without having to decompress them.