CPM upgrade using setup.exe

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

CPM upgrade using setup.exe

L1 Bithead

Hi,

We are planning to upgrade the CPM and PSM components using the installation wizard. To reduce the impact during the upgrade, we intend to keep the services running on the Primary and begin by upgrading the DR (Secondary) CPM and PSM connectors first.

During the upgrade, since the services will remain active on the Primary, we need clarification on how to proceed with upgrading the Secondary CPM. Specifically:

  • If we upgrade the Secondary CPM while the Primary remains active, is there any risk of a split‑brain scenario, considering that services may automatically start during the upgrade?
  • Do we need to enable CPM services on the Secondary during the upgrade process, or should they remain running on primary connector?

 

Thank you.

 

1 accepted solution

Accepted Solutions

L4 Transporter

Hi!

 

The split-brain concept typically applies to database clusters where two nodes accept writes simultaneously.

In a CyberArk environment, the CPM does not host the central vault database; it only connects to it . Therefore, simply running the upgrade wizard on the Secondary (DR) server while the Primary is active will not cause a database conflict.

 

 The actual risk occurs after the upgrade is complete. If you allow the CPM service on the DR server to start and connect to the Primary Vault while the Primary CPM is still running, you could have two CPM instances trying to perform password rotations and verifications on the same accounts. This can lead to race conditions, account lockouts, and inconsistent password states.

 

 The services on the DR server should remain stopped and set to a manual startup type after the upgrade is complete.

View solution in original post

2 REPLIES 2

L4 Transporter

Hi!

 

The split-brain concept typically applies to database clusters where two nodes accept writes simultaneously.

In a CyberArk environment, the CPM does not host the central vault database; it only connects to it . Therefore, simply running the upgrade wizard on the Secondary (DR) server while the Primary is active will not cause a database conflict.

 

 The actual risk occurs after the upgrade is complete. If you allow the CPM service on the DR server to start and connect to the Primary Vault while the Primary CPM is still running, you could have two CPM instances trying to perform password rotations and verifications on the same accounts. This can lead to race conditions, account lockouts, and inconsistent password states.

 

 The services on the DR server should remain stopped and set to a manual startup type after the upgrade is complete.

L4 Transporter

Hi @Supriya Devaraj​ ,

 

No issue, you can upgrade secondary while the primary is active. CPMs are working separately and do not sync each other’s configurations.

 

  • 1 accepted solution
  • 66 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!