search cancel

Cluster Primary Site Member Replication status - Recovering

book

Article ID: 239139

calendar_today

Updated On:

Products

CA Privileged Access Manager (PAM)

Issue/Introduction

Our primary site member today is showing to be in Replication status of "Recovering". We have tried to wait for it to finish replication but it is still in "Recovering" status. 

We have tried to refresh the replication status, but it is still in "recovery" mode. 

Environment

Release : 3.4.x, 4.0.x

Component : PRIVILEGED ACCESS MANAGEMENT

Resolution

In this environment inside they Primary Site, which had 4 machines and 3 are in good standard.  This means that you can eject this member without bringing down the cluster because you have a Quorum:

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/privileged-access-manager/4-0-1/deploying/set-up-a-cluster/cluster-synchronization-promotion-and-recovery/primary-site-fault-tolerance.html

To sum up the procedure:

  • Take snapshot of primary server if a VMware machine
  • Backup the database in PAM,
  • Put it in maintenance mode
  • On the Clustering Page -> Global Status Tab
  • Eject it (Leave Cluster)
  • After leaving successfully:
  • On the Clustering Page -> Global Status Tab
  • Click on Load Configuration from member
  • Choose any member
  • After it loads, please add this member to the site
  • Click Subscribe to active cluster