When I wrote a script for this, I used separate snapshots, with a different naming convention, to use as the endpoints for the incremental send. With this, it becomes easier: find the newest snapshot with that naming convention on the sending side, and check that it exists on the receiving side. This way, you don't have to deal with the latest frequent/hourly on the target side having been removed from the source side since the last backup.
Tim On Wed, Sep 12, 2012 at 2:44 PM, Edward Ned Harvey (opensolarisisdeadlongliveopensolaris) < opensolarisisdeadlongliveopensola...@nedharvey.com> wrote: > I send a replication data stream from one host to another. (and receive). > **** > > I discovered that after receiving, I need to remove the auto-snapshot > property on the receiving side, and set the readonly property on the > receiving side, to prevent accidental changes (including auto-snapshots.)* > *** > > ** ** > > Question #1: Actually, do I need to remove the auto-snapshot on the > receiving side? Or is it sufficient to simply set the readonly property? > Will the readonly property prevent auto-snapshots from occurring?**** > > ** ** > > So then, sometime later, I want to send an incremental replication stream. > I need to name an incremental source snap on the sending side... which > needs to be the latest matching snap that exists on both sides.**** > > ** ** > > Question #2: What's the best way to find the latest matching snap on > both the source and destination? At present, it seems, I'll have to > build a list of sender snaps, and a list of receiver snaps, and parse and > search them, till I find the latest one that exists in both. For shell > scripting, this is very non-trivial.**** > > ** ** > > Thanks...**** > > _______________________________________________ > zfs-discuss mailing list > email@example.com > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > >
_______________________________________________ zfs-discuss mailing list firstname.lastname@example.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss