On Jun 8, 2010, at 20:17, Moazam Raja wrote:
One of the major concerns I have is what happens when the primary
storage server fails. Will the secondary take over automatically
(using some sort of heartbeat mechanism)? Once the secondary node
takes over, can it fail-back to the primary node once the primary
node is back?
My concern is that AVS is not able to repair the primary node after
it has failed, as per the conversation in this forum:
Either the primary node OR the secondary node can have active writes
to a volume, but NOT BOTH at the same time. Once the secondary becomes
active, and has made changes, you have to replicate the changes back
to the primary. Here's a good (though dated) demo of the basic
functionality:
http://hub.opensolaris.org/bin/view/Project+avs/Demos
The reverse replication is in Part 2, but I recommend watching them in
order for proper context. For making the secondary send data to the
primary:
-r
Reverses the direction of the synchronization so the primary volume
is synchronized from the secondary volume. [...]
http://docs.sun.com/app/docs/doc/819-2240/sndradm-1m
For detecting a node failure, and automatic fail over, you could use
Solaris Cluster:
http://en.wikipedia.org/wiki/Solaris_Cluster
http://hub.opensolaris.org/bin/view/Community+Group+ha-clusters/
http://mail.opensolaris.org/pipermail/ha-clusters-discuss/
If you have a SAN (or iSCSI?), you can have two machines have read-
write access to the same LUN using something like QFS:
http://en.wikipedia.org/wiki/QFS
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
