*snip* >> a 'zfs send' on the sending host >> monitors the pool/filesystem for changes, and immediately sends them to >> the >> receiving host, which applies the change to the remote pool. > > This is asynchronous, and isn't really different from running zfs send/recv > in a loop. Whether the loop is in userland or in the kernel, either way > you're continuously pushing changes across the wire. > >> presumably, if fishworks is based on (Open)Solaris, any new ZFS features >> they >> created will make it back into Solaris proper eventually... > > Replication in the 7000 series is mostly built _on top of_ the existing ZFS > infrastructure. > > -- Dave > > -- > David Pacheco, Sun Microsystems Fishworks. http://blogs.sun.com/dap/ >
Sun advertises Active/Active replication on the 7000, how is this possible? Can send/receive operate bi-directional so changes on either reflect on both sides? I always visualized send/receive only being beneficial in Active/Passive situations, where you must only perform operations on the primary, and should fail over occur, you switch to the secondary. -- Brent Jones [EMAIL PROTECTED] _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
