Follow the below mentioned steps to add a node to the cluster to convert and promote the backup node as the primary node.
Install Privileged Account Manager on the new server and register it with the existing primary manager server. By default, the newly registered manager becomes a backup manager.
Log in and verify in the hosts console if all the Privileged Account Manager modules are in the backup mode on the newly installed PAM manager.
Promote the registry manager module to become the primary on the new PAM manager server. Allow the setup to run for few hours to ensure that information between PAM managers are in sync.
Promote all the other modules as primary on the new PAM manager server.
Verify that all the Privileged Account Manager modules are being run as primary on the newly added PAM manager. Also verify they are run as the backup of the old PAM manager.
You have successfully installed a new PAM manager to your existing deployment and promoted it as primary.
NOTE:If you have requirement to retain old audit data and want it to be available on new PAM manager server, then raise a support ticket.
Let your PAM deployment run for few days while you verify that PAM deployment continues to work as expected.