On Tue, August 10, 2010 23:13, Ian Collins wrote: > On 08/11/10 03:45 PM, David Dyer-Bennet wrote:
>> cannot receive incremental stream: most recent snapshot of >> bup-wrack/fsfs/zp1/ddb does not >> match incremental source > That last error occurs if the snapshot exists, but has changed, it has > been deleted and a new one with the same name created. So for testing purposes at least, I need to shut down everything I have that creates or deletes snapshots. (I don't, though, have anything that would delete one and create one with the same name. I create snapshots with various names (2hr, daily, weekly, monthly, yearly) and a current timestamp, and I delete old ones (many days old at a minimum).) And I think I'll abstract the commands from my backup script into a simpler dedicated test script, so I'm sure I'm doing exactly the same thing each time (that should cause me to hit on a combination that works right away :-) ). Is there anything stock in b134 that messes with snapshots that I should shut down to keep things stable, or am I only worried about my own stuff? Are other people out there not using send/receive for backups? Or not trying to preserve snapshots while doing it? Or, are you doing what I'm doing, and not having the problems I'm having? -- David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.net/photography/gallery/ Dragaera: http://dragaera.info _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
