Brent, > On Tue, Sep 16, 2008 at 11:51 PM, Ralf Ramge <[EMAIL PROTECTED]> > wrote: >> Jorgen Lundman wrote: >> >>> If we were interested in finding a method to replicate data to a 2nd >>> x4500, what other options are there for us? >> >> If you already have an X4500, I think the best option for you is a >> cron >> job with incremental 'zfs send'. Or rsync. >> >> -- >> >> Ralf Ramge >> Senior Solaris Administrator, SCNA, SCSA >> > > We had some Sun reps come out the other day to talk to us about > storage options, and part of the discussion was AVS replication with > ZFS. > I brought up the question of replicating the resilvering process, and > the reps said it does not replicate. They may be mistaken, but I'm > hopeful they are correct.
The resilvering process is replicated, as AVS can not differentiate between ZFS resilvering writes, and ZFS filesystem writes. > Could this behavior have been changed recently on AVS to make > replication 'smarter' with ZFS as the underlying filesystem? No 'smarter' changes have been made to AVS. This issue at hand, is that as soon as ZFS makes the decision to not write to one of its configured vdevs, that vdev and its replica will now contain stale data. When ZFS is told to use the vdev again, (a zpool replace), ZFS starts resilvering all in-use data, plus any new ZFS filesystem writes on the local vdev, both of which will be replicated by AVS. It is the mixture of both resilvering writes, and new ZFS filesystem writes, that make it impossible for AVS to make replication 'smarter'. > -- > Brent Jones > [EMAIL PROTECTED] > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss Jim Dunham Engineering Manager Storage Platform Software Group Sun Microsystems, Inc. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
