On Wed, Feb 10, 2010 at 4:31 PM, David Dyer-Bennet <d...@dd-b.net> wrote:
> > On Wed, February 10, 2010 16:15, Tim Cook wrote: > > On Wed, Feb 10, 2010 at 3:38 PM, Terry Hull <t...@nrg-inc.com> wrote: > > > >> Thanks for the info. > >> > >> If that last common snapshot gets destroyed on the primary server, it is > >> then a full replication back to the primary server. Is that correct? > >> > >> -- > >> Terry > >> > >> > > > > I think a better way of stating it is that it picks the newest common > > snapshot. > > That can't be right, zfe send-receive communicate unidirectionally, so > nobody can "pick" the newest common snapshot. > > I have no idea what you're talking about. If there was no ability to pick a common snapshot, or to figure out which snapshots are common, there would be no incremental zfs send at all. Directly from the zfs documentation: Generate a replication stream package, which will replicate the specified filesystem, and all descendent file systems, up to the named snapshot. When received, all properties, snapshots, descendent file systems, and clones are preserved. *If the -i or -I flags are used in conjunction with the -R flag, an incremental replication stream is generated. The current values of properties, and current snapshot and file system names are set when the stream is received.* If the -F flag is specified when this stream is received, snapshots and file systems that do not exist on the sending side are destroyed. --Tim
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
