Ie automatically creates a snapshot and sends the incremental changes since previous snapshot to a backup destination like a NAS or S3 blob storage.
Ie automatically creates a snapshot and sends the incremental changes since previous snapshot to a backup destination like a NAS or S3 blob storage.
https://github.com/tasket/wyng-backup
edit: requires lvm thin provisioned volumes
There is also thin-send-recv which basically does the same as zfs send/recv just with lvm:
https://github.com/LINBIT/thin-send-recv
it uses the same functions of the device mapper to allow incremental sync of lvm thin volumes.
It's just such a low-effort peace of mind. Just a few clicks and I know that regardless what happens to my disk or my system, I can be up and running in very little time with very little effort.
On Linux it's always a bit more work, but backups and restore is one of those things I prefer is not too complicated, as stress level is usually high enough when you need to do restore to worry about forgetting some incantation steps.
Backing up a linux system in combination with REAR:
and a backup utility of your choice for the regular backup has never failed me so far. I used it to restore linux systems to complete different hardware without any troubles.
While I've had to recover in anger twice, I've used the same procedure to migrate to new hardware many times. Just restore to the new disk in the new machine, and let Windows reboot a few times and off I went.
REAR looks useful, hadn't seen that before.
I just make a full dedupped backups from LVM snapshots with kopia, but I've set that up only on one system, on others I just use kopia as-is.
It takes some time, but that's fine for me. Previous backup of 25 GB an hour ago took 20 minutes. I suppose if it only walked files it knew were changed it would be a lot faster.
> I suppose if it only walked files it knew were changed it would be a lot faster.
Right, for me I'd want to set it up to do the full disk, so could be millions of files and hundreds of GB. But this trick should work with other backups software, so perhaps it's a viable option.
Here's the script, should it be of benefit to someone, even if it of course needs to be modified:
#!/bin/sh
success=false
teardown() {
umount /mnt/backup/var/lib/docker || true
umount /mnt/backup/root/.cache || true
umount /mnt/backup/ || true
for lv in root docker-data; do
lvremove --yes /dev/hass-vg/$lv-snapshot || true
done
if [ "$1" != "no-exit" ]; then
$success
exit $?
fi
}
set -x
set -e
teardown no-exit
trap teardown EXIT
for lv in root docker-data; do
lvcreate --snapshot -L 1G -n $lv-snapshot /dev/hass-vg/$lv
done
mount /dev/hass-vg/root-snapshot /mnt/backup
mount /dev/hass-vg/docker-data-snapshot /mnt/backup/var/lib/docker
mount /root/.cache /mnt/backup/root/.cache -o bind
chroot /mnt/backup kopia --config-file="/root/.config/kopia/repository.config" --log-dir="/root/.cache/kopia" snap create / /var/lib/docker
kopia --config-file="/root/.config/kopia/repository.config" --log-dir="/root/.cache/kopia" snap create /boot /boot/efi
success=true