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. > > 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. > > Thoughts?
+1 Add to this some churn/replication throttling and you may not want just a command-line interface but a library also. E.g., if the stdout/remote connection of zfs send -f blocked for long/broke then zfs should snapshot at the latest TXG and hold on to that snapshot until the output could drain and/or connection be restored, then resume by sending the incremental from the current TXG to that snapshot... Nico -- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
