Closed zorbathut closed 7 months ago
i suspect your common snapshot does not actually match.
check the guid of both common snapshots, or use the latest version in the master branch. (that will check the guid automaticly)
or use the latest version in the master branch. (that will check the guid automaticly)
This seems to have done it; it had about half an hour of copying to do and it was done, which is way less than starting from scratch (which would have been about three days).
I have no idea what the underlying issue was and if there's anything further you want me to do to troubleshoot, let me know, otherwise I'm calling this done. Thank you!
ah nice! did the new version warn you about a incompatible snapshot, which it then could delete for you?
Yep! Log snippet:
NOTE: [Target] backup-b/tank/borg@backup-a-20240205131009: Common snapshot has invalid guid, ignoring.
[Source] tank/borg@backup-b-20240117131045: Destroying
[Source] tank/borg@backup-b-20240123080223: Destroying
[Target] backup-b/tank/borg@backup-b-20240117131045: Destroying
[Target] backup-b/tank/borg@backup-b-20240123080223: Destroying
[Source] tank/borg@backup-b-20240205131028: -> backup-b/tank/borg
[Source] tank/borg@backup-b-20240205131141: -> backup-b/tank/borg
[Source] tank/borg@backup-b-20240205131204: -> backup-b/tank/borg
[Source] tank/borg@backup-b-20240205131218: -> backup-b/tank/borg
[Source] tank/borg@backup-b-20240205131241: -> backup-b/tank/borg
[Source] tank/borg@backup-b-20240205131714: -> backup-b/tank/borg
[Source] tank/borg@backup-b-20240205131746: -> backup-b/tank/borg
[Source] tank/borg@backup-b-20240205133033: -> backup-b/tank/borg
[Source] tank/borg@backup-b-20240205133323: -> backup-b/tank/borg
[Source] tank/borg@backup-b-20240206225456: -> backup-b/tank/borg
NOTE: [Target] backup-b/tank/public@backup-a-20240205131009: Common snapshot has invalid guid, ignoring.
[Source] tank/public@backup-b-20240122180205: Destroying
[Source] tank/public@backup-b-20240122180816: Destroying
[Source] tank/public@backup-b-20240122180938: Destroying
[Source] tank/public@backup-b-20240123014640: Destroying
[Source] tank/public@backup-b-20240123080223: Destroying
[Target] backup-b/tank/public@backup-b-20240122180205: Destroying
[Target] backup-b/tank/public@backup-b-20240122180816: Destroying
[Target] backup-b/tank/public@backup-b-20240122180938: Destroying
[Target] backup-b/tank/public@backup-b-20240123014640: Destroying
[Target] backup-b/tank/public@backup-b-20240123080223: Destroying
[Source] tank/public@backup-b-20240205131028: -> backup-b/tank/public
[Source] tank/public@backup-b-20240205131141: -> backup-b/tank/public
[Source] tank/public@backup-b-20240205131204: -> backup-b/tank/public
[Source] tank/public@backup-b-20240205131218: -> backup-b/tank/public
[Source] tank/public@backup-b-20240205131241: -> backup-b/tank/public
[Source] tank/public@backup-b-20240205131714: -> backup-b/tank/public
[Source] tank/public@backup-b-20240205131746: -> backup-b/tank/public
[Source] tank/public@backup-b-20240205133033: -> backup-b/tank/public
[Source] tank/public@backup-b-20240205133323: -> backup-b/tank/public
[Source] tank/public@backup-b-20240206225456: -> backup-b/tank/public
NOTE: [Target] backup-b/tank/scratch@backup-a-20240205131009: Common snapshot has invalid guid, ignoring.
[Source] tank/scratch@backup-b-20240122180205: Destroying
[Source] tank/scratch@backup-b-20240122180816: Destroying
[Source] tank/scratch@backup-b-20240122180938: Destroying
[Source] tank/scratch@backup-b-20240123014640: Destroying
[Source] tank/scratch@backup-b-20240123080223: Destroying
[Target] backup-b/tank/scratch@backup-b-20240122180205: Destroying
[Target] backup-b/tank/scratch@backup-b-20240122180816: Destroying
[Target] backup-b/tank/scratch@backup-b-20240122180938: Destroying
[Target] backup-b/tank/scratch@backup-b-20240123014640: Destroying
[Target] backup-b/tank/scratch@backup-b-20240123080223: Destroying
[Source] tank/scratch@backup-b-20240205131028: -> backup-b/tank/scratch
[Source] tank/scratch@backup-b-20240205131141: -> backup-b/tank/scratch
[Source] tank/scratch@backup-b-20240205131204: -> backup-b/tank/scratch
[Source] tank/scratch@backup-b-20240205131218: -> backup-b/tank/scratch
[Source] tank/scratch@backup-b-20240205131714: -> backup-b/tank/scratch
[Source] tank/scratch@backup-b-20240205131746: -> backup-b/tank/scratch
[Source] tank/scratch@backup-b-20240205133033: -> backup-b/tank/scratch
[Source] tank/scratch@backup-b-20240205133323: -> backup-b/tank/scratch
[Source] tank/scratch@backup-b-20240206225456: -> backup-b/tank/scratch
NOTE: [Target] backup-b/tank/srv@backup-a-20240205131009: Common snapshot has invalid guid, ignoring.
[Source] tank/srv@backup-b-20240205131028: -> backup-b/tank/srv
[Source] tank/srv@backup-b-20240205131141: -> backup-b/tank/srv
[Source] tank/srv@backup-b-20240205131714: -> backup-b/tank/srv
[Source] tank/srv@backup-b-20240205133033: -> backup-b/tank/srv
[Source] tank/srv@backup-b-20240206225456: -> backup-b/tank/srv
I'm reading this as "rewinding to something compatible, then going from there".
yes that is correct. :)
I'm trying to update an existing backup and getting the following error:
cannot receive incremental stream: most recent snapshot of backup-b/tank does not match incremental source
The platform in question is a TrueNAS Scale system with a manual install of zfs_autobackup. I got this error a while back (I don't have a log from the last try, sorry) and decided to just update zfs_autobackup and redo the backup; I updated zfs_autobackup to v3.2.2 and did a new backup from scratch, but now that I'm trying to update the backup I'm getting the same error.
The only slightly odd thing I'm doing is mounting ZFS via Truecrypt (yes, I know I should be using ZFS built-in encryption, but this is a platform without AES hardware support and it's phenomenally slow).
This time, I did a backup, intentionally interrupted it midway through to test resuming (it worked fine), ended up interrupting it again midway through for a reboot (it resumed fine), finished it up, and ran it again to verify that I could update. I could! Then I did another update a few weeks later and ran into this problem again.
Debug log follows:
I don't personally see anything useful in here so I've attached a --debug-output log as well: zfsautobackup.txt
I am happy to troubleshoot as requested; let me know what would be useful to know and I'll go find it for you! But I really don't want to have to redo my backup from scratch every single time.