On Tue, May 09, 2006 at 01:33:33PM -0700, Darren Reed wrote:
> Eric Schrock wrote:
>
> >...
> >Asynchronous remote replication can be done today with 'zfs send' and
> >zfs receive', though it needs some more work to be truly useful. It has
> >the properties that it doesn't tax local activity, but your data will be
> >slightly out of sync (depending on how often you sync your data,
> >preferably a few minutes
> >
>
> Is it possible to add "tail -f" like properties to 'zfs send'?
>
> I suppose what I'm thinking of for 'zfs send -f' would be to send
> down all of the transactions that update a ZFS data set, both the
> metadata and the data.
'zfs send' always sends all the changes, including metadata and data.
> The catch here would be to start the 'zfs send -f' at the same time
> as the filesystem came online so that there weren't any transactional
> gaps.
You can always simply run 'zfs snapshot; zfs send -i ... | ssh ...' in a
loop. This is an implementation of best-effort remote replication.
Perhaps you're looking for a more real-time remote replication. See:
5036182 want remote replication (intent-log based)
Another possible remote replication implementation would allow the
administrator to put a bound on how much the remote side can be out of
date (eg. by an amount of time, or amount of modified data). This could
be implemented by using 'zfs send -i', with some hooks to stall changes
to the filesystem if the 'zfs send -i' gets too far behind.
--matt
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
