restoring from an incremental backup breaks the parent UUIDs, making it
impossible to continue doing incremental backup.
1) assume you do incremental backup from "home" to "BACKUP":
btrfs subvol snapshot -r /home /home/backup1
btrfs send /home/backup1 | btrfs receive /BACKUP
btrfs subvol snapshot -r /home /home/backup2
btrfs send /home/backup2 -p /home/backup1 | btrfs receive /BACKUP
2) then you delete "home", mkfs.btrfs, and attempt to restore:
btrfs send /BACKUP/backup2 | btrfs receive /home
btrfs subvol snapshot /home /home/home-rw
btrfs subvol snapshot -r /home/home-rw /home/home-rw/backup3
btrfs send /home/home-rw/backup3 -p /home/backup2 | btrfs receive /BACKUP
#send|receive fails with "parent not found"
#the next step would be to set-default to home-rw, remount, and continue
inc backup as above
receive fails with "parent not found", which makes sense since the
parent UUIDs are not the same, but is highly undesirable. i need to
delete my backup drive and reseed which is mucho scary. perhaps there is
some obvious way to do this that im missing?
thanks, and sorry if this is too vague or is not actually a misfeature.
let me know if theres anything i can do to help. {please CC me for
replies, im not subscribed}
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
