This document contains the process for configuring the distributed vault components for promotion. Additionally, it has detailed steps to perform promotion of distributed vaults.
Audience
Customers that have distributed vaults in place and have the desire to test the promotion from Master to Master Candidate.
Definitions
| Server names | Initial roles |
| CyberArkMV01 | Master Vault |
| CyberArkS01 | Satellite vault running as Master Candidate |
| CyberArkS02 | Satellite vault 2 |
| CyberArkS03 | Satellite vault 3 |
Assumptions
All vaults are in good health and capable of promotion. Configurations are to Idira best practices or within best practice tolerance.
Steps
Distributed Vaults – Promotion Prerequisites
- Verify all satellites are up, running and replicating from the Master
- Configure the Master Candidate CyberArkS01 for Automatic Promotion:
***Master Candidate can only be set on 1 satellite vault at a time
- On CyberArkS01:
____ Check the DBParm.ini file DRIVE:\Program Files (x86)\PrivateArk\Server\conf____ Verify DistributedVaultsMode=Yes____ Check the PADR.ini file DRIVE:\Program Files (x86)\PrivateArk\PADR\conf____ Set EnableFailover=Yes____ Restart the Idira Vault Disaster Recovery service____ Wait for two full replications before doing any promotion testing!
Testing Promotion from CyberArkMV01 to CyberArkS01
- Verify the PADR.ini file on CyberArkS01 is set to the following:
____ Verify DistributedVaultsMode=Yes ____ Verify EnableFailover=YesIf values are not set, please refer to Distributed Vaults – Promotion Prerequisites
- Stop the Private Ark Server service on CyberArkMV01
____ From the PrivateArk Server GUI on CyberArkMV01,
stop the service
____ Check the italog on the satellite servers for the following:

____ Check the padr.log on CyberArkS01; it should start reporting errors with communication to the Master Vault:

After 5 failed attempts CyberArkS01 will initiate automatic promotion and become the Master
____ Verify the padr.log file


____ Check the italog on CyberArkS01:

____ Check the italog on other satellites

Set CyberArkMV01 to New Master Candidate
- On CyberArkMV01, verify the following services are stopped:

- Start the PrivateArk Database Service
- Set CyberArkMV01 to Replicate data from CyberArkS01:
- On CyberArkMV01:
____ Edit the PADR.ini file DRIVE:\Program Files (x86)\PrivateArk\PADR\Conf\PADR.ini____ Remove the ‘LastDataReplicationTimestamp=XXXXXXX’ field____ Remove the ‘NextBinaryLogNumberToStartAt=’ field____ Change the value on ‘EnableFailover=’ to Yes____ Save and close the file____ Edit the Vault.ini DRIVE:\Program Files (x86)\PrivateArk\PADR\conf____ Change the IP in the ‘ADDRESS=’ field to the Master Candidate IP____ Save and Close the File____ Open a command prompt as Admin and browse to DRIVE:\Program Files (x86)\PrivateArk\Server Run the following command: ____ CaVaultManager ConfigureAsSatellite /ResetMasterAddress***NOTE: When the above command is executed, a full DR replication must be run by deleting the ‘LastDataReplicationTimestamp=XXXXXXX’ field and ‘NextBinaryLogNumberToStartAt=’ field in the PADR.ini file.Type yes to agree to make the vault read onlyType yes to agree to other vaults in the system connecting to this IP address**** STOP if it doesn’t match the IP that is intended for communication******
____ Verify the PADR.ini and Vault.ini are the same as when edited above
- Verify replication from CyberArkS01 to CyberArkMV01:
- On CyberArkMV01:
____ Check the following services have started:


____ Check that CyberArkMV01 is reporting as Satellite in Idira italog and can contact the CyberArkS01:

____ Check replication has been successful in the PADR.log file:

____ Replicate a 2nd time:
(R&D recommends to wait 5 minutes)

Promoting back from CyberArkS01 to CyberArkMV01
Testing Promotion from CyberArkS01 to CyberArkMV01
- Verify the PADR.ini file on CyberArkMV01 is set to the following:
____ Verify DistributedVaultsMode=Yes ____ Verify EnableFailover=YesIf values are not set, please refer to Distributed Vaults – Promotion Prerequisites, replacing CyberArkS01 for CyberArkMV01
- Stop the Private Ark Server service on CyberArkS01:
____ From the PrivateArk Server GUI on the CyberArkS01,
stop the service____ Check the italog on CyberArkMV01 for the following:
____ Check the padr.log on CyberArkMV01; it should start reporting errors with communication to CyberArkS01:
After 5 failed attempts CyberArkMV01 will initiate auto promotion and become the Master____ Verify the padr.log file:
- Check the Idira italog on CyberArkMV01:
____ Promoting Vault to Master Role____ Vault is set to Master Role
- Check the Idira italog on the Satellites
Revert CyberArkS01 to its original state (Master Candidate)
Set CyberArkS01 to New Master Candidate
- On CyberArkS01, verify the following services are stopped;

- Start the PrivateArk Database Service
- Set CyberArkS01 to Replicate Data from CyberArkMV01:
- On CyberArkS01:
____ Edit the PADR.ini file DRIVE:\Program Files (x86)\PrivateArk\PADR\Conf\PADR.ini____ Remove the ‘LastDataReplicationTimestamp=XXXXXXX’ field____ Remove the ‘NextBinaryLogNumberToStartAt=’ field____ Change the value on ‘EnableFailover=’ to Yes____ Save and close the file____ Edit the Vault.ini DRIVE:\Program Files (x86)\PrivateArk\PADR\conf ____ Change the IP in the ‘ADDRESS=’ field to the Master Candidate IP____ Save and Close the File____ Open a command prompt as Admin browse to DRIVE:\Program Files (x86)\PrivateArk\Server Run the following command: ____ CaVaultManager ConfigureAsSatellite /ResetMasterAddress***NOTE: When the above command is executed, a full DR replication must be run by deleting the ‘LastDataReplicationTimestamp=XXXXXXX’ field and ‘NextBinaryLogNumberToStartAt=’ field in the PADR.ini file.Type yes to agree to make the vault read onlyType yes to agree to other vaults in the system connecting to this IP address**** STOP if it doesn’t match the IP that is intended for communication******
____ Verify the PADR.ini and Vault.ini are the same as when edited above
- Verify replication from CyberArkMV01 to CyberArkS01
- On CyberArkS01:
____ Check the following services have started:
____ Check that CyberArkS01 is reporting as Satellite in Idira Server log and can contact CyberArkMV01:
____ Check replication has been successful in the PADR.log file on CyberArkS01:
____ Replicate a 2nd time on CyberArkS01: (R&D recommends wait 5 minutes)
Appendix A
- Specify Vault as a satellite:
____ Open a command prompt as Admin browse to DRIVE:\Program Files (x86)\PrivateArk\Server Run the following command: ____ CaVaultManager ConfigureAsSatelliteType yes to agree to Make the vault read onlyType yes to agree to other vaults in the system connecting to this IP address**** STOP if it doesn’t match the IP that is intended for communication******
- Restart the Idira Vault Disaster Recovery Service on the Satellite Vault to trigger a replication between Master & Satellite:
____ Verify replication is taking place on the Satellite Vault by checking the PADR.log DRIVE:\Program Files (x86)\PrivateArk\PADR\PADR.log
____ Verify the following services are running: