- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
11-27-2025 01:44 AM
Hi Team
I have one Primary CyberArk site and two DR sites.
My current upgrade plan is to upgrade the DR sites first and temporarily make the DR vault independent/active. I want to validate whether my approach is correct and supported.
My planned steps:
I completed a full DR replication from the Primary Vault to the DR Vault.
I will perform a manual failover to make the DR Vault active.
I will upgrade the DR Vault.
I will then upgrade PVWA in the DR site.
Main Question – Vault IP During PVWA Upgrade
During PVWA installation/upgrade, it asks for the Vault IP to create the PVWA environment.
Since I want DR to act as an independent site during this phase:
Should I provide the DR Vault IP to the PVWA installer?
This will cause PVWA to create its environment (safes, accounts, configuration) inside the DR Vault instead of the Primary Vault.
Or should be upgarded pointing toward Primay vault?
Concern – After Failback to Primary
Later, once I upgrade the Primary Vault, I plan to:
Perform DR → Primary failback, making the Primary Vault active again
Point DR PVWA/CPM/PSM back to the Primary Vault IP
My question is:
If PVWA was upgraded and registered using the DR Vault IP, will it work normally when I switch back and point PVWA to the Primary Vault?
Is this supported as per CyberArk documentation and community best practices?
Will any issues occur because PVWA’s environment/safes were created in the DR Vault during the upgrade window?
Objective
I want to ensure:
DR site can run independently during upgrade
After failback, no configuration, auditing, or component registration issues occur
All components (PVWA/CPM/PSM) will communicate properly with the Primary Vault after switching back
Has anyone followed this “DR-first upgrade” approach?
Any guidance or official confirmation from CyberArk documentation or practical experience would be really helpful.
Thanks in advance!
11-27-2025 12:20 PM
Hi @Mohd Arsh
For any major upgrade reach out to CyberArk.
Here are the answers based on my experiences with the major upgrades.
Your approach is correct to upgrade the DR site first and test before touching the Primary.
Yes, you should provide the DR Vault IP which will be active in your DR site to the PVWA installer.The PVWA, CPM, and PSM components must connect to and register with the Vault that is currently active to function and complete the upgrade process.
The replication from DR to Primary will ensure that these new configurations and Safes are replicated back to the Primary Vault.
The PVWA will work normally when you switch back to Primary Vault
The approach you have is supported.
No issues should arise regarding configuration consistency provided replication is fully completed from
DR to Primary.
Hope it helps !
11-27-2025 12:20 PM
Hi @Mohd Arsh
For any major upgrade reach out to CyberArk.
Here are the answers based on my experiences with the major upgrades.
Your approach is correct to upgrade the DR site first and test before touching the Primary.
Yes, you should provide the DR Vault IP which will be active in your DR site to the PVWA installer.The PVWA, CPM, and PSM components must connect to and register with the Vault that is currently active to function and complete the upgrade process.
The replication from DR to Primary will ensure that these new configurations and Safes are replicated back to the Primary Vault.
The PVWA will work normally when you switch back to Primary Vault
The approach you have is supported.
No issues should arise regarding configuration consistency provided replication is fully completed from
DR to Primary.
Hope it helps !
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!

