Can anyone recommend best practices and 'gotchas'? (besides following the
manual)
We are upgrading from 4.1 MP1 to 5.0 (to finally get rid of some EMC issues
with trespassing)
Last time I had to do this (MP1), we were forced to upgrade the kernel,
which broke tons of things (particularly replaced
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.a
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 ri
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]
-
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 bunk
