If you configure auto failover in GCO (not recommended), then you need to make sure you are using sync replication only.
-----Original Message----- From: Cronin, John S [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 10:07 AM To: Jim Senicka; Pavel A Tsvetkov; Veritas-ha@mailman.eng.auburn.edu Subject: RE: [Veritas-ha] Veritas Volume Replicator in ReplicatedDataCluster question I believe auto-failover is a configurable option with GCO, unless something has changed recently (I didn't go look at the docs). The default is operator confirmation before fail-over, but I have agreed to configured GCO for auto-failover before if a split-brain did not present any significant risk to the customer (eg the customer said it was OK and their preference, and after inquiring into the facts of the situation, I agreed with their conclusions). -- John Cronin 678-480-6266 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Senicka Sent: Wednesday, March 14, 2007 5:14 AM To: Pavel A Tsvetkov; Veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] Veritas Volume Replicator in ReplicatedDataCluster question RDC = autofailover. GCO = Operator confirmed failover. So in GCO, an operator makes a choice to startup on old data or wait on original primary. This is not possible inside a single cluster. And for bunker, this is a GCO config as well [Sent from my Nokia E62 handheld via goodlink] -----Original Message----- From: Pavel A Tsvetkov [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 02:09 AM Pacific Standard Time To: Jim Senicka; Veritas-ha@mailman.eng.auburn.edu Subject: Re: Re: [Veritas-ha] Veritas Volume Replicator in Replicated DataCluster question Hello Jim! Thank you for the answer. But if I have a choice for replication mode in global cluster it can be useful to have the same thing in RDC. Let it be not up-to-date data on the Secondary , but it is still consistent. :) So the application can be started. And we should take the bunker into consideration! The bunker uses synchronous connection with Primary SRL, so the asynchronous Secondary site can have up-to-date data from the bunker. So if we use bunker and the bunker agent it is quite possible to take RDC in asynchronous mode. With best regards, Pavel >>We do not support an automatic failover to out of date secondary. So RDC is sync only. If you need async, you need to not treat the the >replication like a shared disk, and instead treat it like replication. Take a look at global cluster option, now part of VCS HA/DR edition _______________________________________________ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha ***** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA622 _______________________________________________ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
