Shawn Perry

I would definitely suggest something along these lines. "file resiliency guarantees" don't help you when the file you are working with is corrupt somehow. But then, I'm a backup nut....

Sure.

I wouldn't yet. Proxborg and PBS have different niches. Proxborg can upload to many cloud services via rclone/rsync. It also works with rsync.net and others where PBS does not. I'll...

I don't know how to fix it. It conflicts. Here is the text. - https://github.com/michabbs/proxborg (This script automates backup of Proxmox VMs (both qemu and lxc) to a borg repository.)

Doing pull backups goes a long way to help with that.

I have the current release version running on CentOS 7, Debian 11, Ubuntu 18.04, 20.04, and 22.04, as well as Proxmox 7. Both sanoid and syncoid are working perfectly.

Does Sanoid handle not trying to delete snapshots that are cloned? That would be a handy addition.

So I'll receive this error every time sanoid runs until excluded or it can actually delete it. Maybe a patch to include an option to ignore this error?

Default to off, of course. I could always just rename the snapshot when I clone it too.

@ryanjaeb Might I suggest using the daily/weekly/monthly snapshot for borg backups? That's how I'm doing it.