OS migration

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

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

OS migration

L2 Linker

Hi Experts,

For CyberArk PAM Self-Hosted OS and version migration. I would like to confirm the recommended approach and any potential technical challenges

Current Setup:

  • CyberArk Version: 13.2
  • Architecture: Physical HA Cluster (Active/Passive with shared storage)
  • OS: Windows Server 2016

Target Setup:

  • CyberArk Version: 14.2
  • Architecture: Primary–DR (no shared storage; replication-based)
  • Platform: VM-based on Windows Server 2022

Planned Approach:

  • Build a new parallel environment (Primary and DR Vaults) on Windows 2022.
  • Configure replication (PADR) between the new Vaults.
  • Use Vault metadata migration (via PA Replicate or similar process) to bring over data from the existing HA Vault.
  • Perform a controlled cutover once the new environment is validated.
  • Repoint all components (PVWA, CPM, PSM, PSMP, PTA) to the new Primary Vault.

Questions for clarification:

  1. Are there any specific technical challenges or known limitations when migrating from an HA Cluster (shared storage) to a Primary/DR (replication) model?
  2. Is there a recommended CyberArk-supported method to move Vault data between these two architectures?
  3. Any precautions around shared storage cleanup or DR replication to avoid data corruption or split-brain issues?
  4. Any real-world lessons or pitfalls others have faced during a similar HA → Primary/DR transition?

 

Thanks,

MA

 

1 accepted solution

Accepted Solutions

L7 Applicator

Hi @Mohd Arsh​ 

 

 

 

Are there any specific technical challenges or known limitations when migrating from an HA Cluster (shared storage) to a Primary/DR (replication) model?

 

  • Ensure new servers are in the same network zone
  • Make sure that all Firewall rules configured for existing servers are also available for new servers
  • consider the data transfer time and impact to network if doing during business hours
  • make hard hardening GPOs are correctly applied to new servers
  • If using HSM in existing make sure that new Vault is also encrypted using same keys

 

Is there a recommended CyberArk-supported method to move Vault data between these two architectures?

 

  • Ensure same application version in new environment
  • Once new Vaults are setup, temporarily start new Primary Vaults as DR point to existing Vault which will replicate your data then you can start Primary Vaults as Primary. It will then copy the data to new DR Vaults
  • You can reach out to your CyberArk counterpart

 

Any precautions around shared storage cleanup or DR replication to avoid data corruption or split-brain issues?

 

  • In addition to above data replication method, you can perform SAN disk level migration from existing to new SAN disk
  • When you start the new Vault using new SAN disk, you will be able to validate the data accurately

 

Any real-world lessons or pitfalls others have faced during a similar HA → Primary/DR transition?

 

  • I’ve led the same project successfully last year and have shared some of the keys points above.
  • Start with Test environment.
  • Validate all aspects and approach in pre-production
  • Perform thorough technical and user testing

 

I would suggest to work with CyberArk for this kind of major uplift.

 

Hope it helps !

View solution in original post

4 REPLIES 4

L7 Applicator

Hi @Mohd Arsh​ 

 

 

 

Are there any specific technical challenges or known limitations when migrating from an HA Cluster (shared storage) to a Primary/DR (replication) model?

 

  • Ensure new servers are in the same network zone
  • Make sure that all Firewall rules configured for existing servers are also available for new servers
  • consider the data transfer time and impact to network if doing during business hours
  • make hard hardening GPOs are correctly applied to new servers
  • If using HSM in existing make sure that new Vault is also encrypted using same keys

 

Is there a recommended CyberArk-supported method to move Vault data between these two architectures?

 

  • Ensure same application version in new environment
  • Once new Vaults are setup, temporarily start new Primary Vaults as DR point to existing Vault which will replicate your data then you can start Primary Vaults as Primary. It will then copy the data to new DR Vaults
  • You can reach out to your CyberArk counterpart

 

Any precautions around shared storage cleanup or DR replication to avoid data corruption or split-brain issues?

 

  • In addition to above data replication method, you can perform SAN disk level migration from existing to new SAN disk
  • When you start the new Vault using new SAN disk, you will be able to validate the data accurately

 

Any real-world lessons or pitfalls others have faced during a similar HA → Primary/DR transition?

 

  • I’ve led the same project successfully last year and have shared some of the keys points above.
  • Start with Test environment.
  • Validate all aspects and approach in pre-production
  • Perform thorough technical and user testing

 

I would suggest to work with CyberArk for this kind of major uplift.

 

Hope it helps !

L4 Transporter

Hi,

as it is a major upgrade you should consult Cyberark to get their advices and help during the process.

As for your question you can't upgrade the Vault through DR replication only. DR replication works when the same version is used on both vaults.

You have to :

install a DR in w2022 and version 13.2 without hardening,

perform the replication,

then launch the upgrade to 14.2 (or 14.6) from this setup.

Do the hardening of the vault on 14.2.

 

Another waiting DR in 14.x can be synchronised right after the upgrade of the first one.

 

Regards,

Thanks @Malhar Vora​ for your inputs.

L7 Applicator

hey @Mohd Arsh​ 

This is considered a major migration and working with CyberArk or a Certified Delivery Partner is required. Please reach out to your account executive to get this scheduled.

 

-Matt

  • 1 accepted solution
  • 145 Views
  • 4 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!