How to disable automatic fail-over in the event of CA link failure?

[Sajith V Mannadiar]

Hello there,

In our Metro Cluster configuration, we have set AUTO_NONCURDATA=1, which will allow the SG packages to start at remote site, if whole of the primary site fails.

i.e, when the remote state is in EX_ENORMT state.

but now we have an issue with this config.

If our CA links were to fail, since we are using synchronous mode, it will change only the local state to PVOL_PSUE.

and if we were to loose the site, after the CA link failure, we will end up starting the packages at remote site with NON-CURRENT data.

Is there a way to stop the automatic failover in the event of a rolling disaster. ie. CA link failing and then loosing the primary site?

Please advice

Thanks,
Sajith

[harry d brown jr]

Well you should always have at least two seperate (physical routes and telecom carriers) to the remote site, thus reducing the potential for a rolling disaster.

There's probably no "failsafe" method to get it right, all the time, for every situation. The more redundancy you put in place, and the elimination of single and dual points of failure will help reduce the potential bogus start up of the remote site. Even with addition of human intervention will not prevent it, but could help (like humans never make mistakes).

live free or die
harry d brown jr