Starting over with kopia from scratch, having my first small setup with an sftp repo on one server and kopia writing there from 3 other servers. Basics work fine, I still learn about the concepts etc
On one server I run ~5 VMs with QEMU/KVM. The VMs are mostly LVM-based, their virtual disks are raw Logical Volumes in terms of LVM. I have an old and reliable script that pauses the VMs, does LVM-snapshots, unpauses the VMs and archives the snapshots to a separate directory, then syncs it over to the backup server.
Now I think of optimizing this with kopia.
So far I would keep the old script in place and let it create compressed tarballs in a local directory /mnt/virt-backup
. Each VM gets its own subdir there.
From there I would create kopia snapshots to the remote sftp-repo.
I wonder if it makes sense to create one big snapshot of /mnt/virt-backup
? Or is it better to do separate snapshots of
- /mnt/virt-backup/VM1
- /mnt/virt-backup/VM2
- /mnt/virt-backup/VM3
?
I think of writing some wrapper (bash-)script and call it via systemd-timer, btw. As far as I understand it’s good (or necessary?) to add a connect-command at first, right? Or does kopia connect by itself, just by reading the config-file?
Should I maybe skip compression in my initial backup script and better let kopia compress things?
As soon as I have this in place, I will also add another stage and sync the sftp-repository to a GCS-repository. Only mentioning, not in place yet (I wait for an admin to assign me a bucket, different story).
So far I haven’t fully understood all the features of kopia’s policies. I assume they will help me to maybe only sync selected snapshots to GCS etc … looking forward to all these possibilities.
Help and hints welcome, thanks all for this great software.