PingAccess

Manually promoting the replica administrative node

Manually promote the replica administrative node to the administrative node if the administrative node fails.

About this task

The replica administrative node is intended to be used for disaster recovery purposes. If you can recover the clustered console, then you should focus on recovery rather than failing over to the replica administrative node.

Only one primary administrative node should be running for the cluster at any given time.

Steps

  1. Open <PA_HOME>/conf/run.properties in a text editor.

  2. Locate the pa.operational.mode line and change the value from CLUSTERED_CONSOLE_REPLICA to CLUSTERED_CONSOLE.

    These properties are case-sensitive.

    Do not restart the replica node during the promotion process. PingAccess can detect and apply this change without a restart, and restarting the node during its promotion can cause file corruption or failure to promote correctly.