MaxRep: Intermittent HA failover issues and failover not working properly
(Doc ID 2277296.1)
Last updated on JANUARY 31, 2019
Applies to:Pillar Axiom Replication Engine (MaxRep) - Version 3.0 to 3.0 [Release 3.0]
Information in this document applies to any platform.
Intermittent MaxRep HA failover issues where the Active Engine in the MaxRep cluster has failed over its resources to the Passive Engine.
Confirmation that a MaxRep HA failover has occurred can be observed in the Control Service Engine Support page http://<MaxRep Control Service Engine IP>/support navigate to the "Dashboard" page -> select the Cluster IP. and look at the "Role:" if it shows Active the Engine is the Active Engine in the cluster and the other Engine is Passive in the cluster. If a failover occurred the Engine that was Passive will show as being Active.
There also may be issues if the failover process did not working properly. This is noticed that the retention LUN that was mounted on the previously Active Engine is not automatically mounted on the new Active Engine in the cluster. Logging into the UI at http://<MaxRep Control Service Engine IP>/ui navigate to "Protect" tab -> from the left menu click "Manage Protection Plan", from this page under column Servers the Source Engine and Target Engine should reflect the current Active Engines in each cluster, if not then the failover did not work properly.
A failover will only occur if the Protection Plans were Activated at the time the HA failover occurred.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document