I'm not sure where the poster got this information, or how it seems to be at odds with the design goals of AVS. Perhaps they only looked at one piece of the puzzle and then got lost?
I wrote it :-) It's right there in the manual, in fact: http://docs.sun.com/source/819-6148-10/chap4.html#pgfId-1009132
Changing the flow is done with a simple CLI command.
The point I was trying to get across is that the primary and secondary roles under AVS are fixed. Under DRBD, if a primary has failed and the secondary has taken over, the roles reverse (under the direction of Linux HA). The secondary becomes the acting primary. When the real primary is restarted, it will be the acting secondary and the mirroring changes direction. This happens on the fly. AVS cannot do that at all! The primary must fully be brought back online as the real, active primary for the synchronization to be able to reverse direction. That means until the primary can be switched to that state, which may not be immediately be practical if users needed to be disconnected, there won't be any replication. (ZFS mirroring of iSCSI volumes works like DRBD in this regard.)
Unless, of course, you're implying Nexenta has done something to AVS' code to change this behavior.
-- Maurice Volaski, maurice.vola...@einstein.yu.edu Computing Support, Rose F. Kennedy Center Albert Einstein College of Medicine of Yeshiva University _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
