My current backup strategy is to use Veeam free edition on a Windows 10 computer to back up a few VMWare ESXi VMs, and a physical Windows Server, and store the backups on a Linux SMB server with a btrfs volume.
The Linux box uses snapper to take btrfs snapshots (read-only - helps with ransomware protection), and uses snapper cleanup service to prune snapshots according to timeline retention rules.
I want to add Kopia into the mix to take an offsite copy of the data up to Google Storage.
I am trying to get clear in my head the best way to start.
I am wondering if I should let Kopia try to back up the live directory on the NAS box (that’s simplest, and I can tell it to ignore the hidden .snapshots directory), or should I point it at a snapshot? A snapshot is going to be difficult because every time Kopia runs, I would want it to look at only the latest snapshot. but at the same time, it feels like pointing Kopia at a read-only snapshot folder will at least mean Kopia can get on with its job without the next scheduled Veeam backup affecting things.
OTOH I gather Kopia ‘snapshots’ somehow before doing a backup, but it’s not using filesystem features to do that is it? and these will be very large backup files that Kopia is being asked to back up to cloud.
TL;DR: What’s the best way to use Kopia to back up existing incremental backup images (VHD, Veeam, etc.) to cloud?