- 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.
10-15-2021 01:57 AM
Hi,
In our DR vault server just need to update some config change . Restart service required.
How to make privateark service running in DR and then restart service to make change effective with less downtime.
Thanks,
Padmanabhan.H
10-15-2021 06:26 AM
Yes , you should be able to do this. Make sure
ActivateManualFailover=Yes and EnableFailover=No in PADR.ini and revert these settings back before you stop server service and start DR service
10-15-2021 06:04 AM
@Padmanabhan Harikumar
you would just need to make the change, stop the DR service, start the Privateark Server service, then stop the Server service and restart DR service.
-Matt
10-15-2021 06:17 AM
@M - Private ark service is already running on prod vault server. I need to update dbparm.ini in dr vault since service is not running on this server.
Can i do this manually on DR vault server start the Privateark Server service, then stop the Server service .
10-15-2021 06:21 AM
Yes, you would manually do these steps on the DR server.
-Matt
10-15-2021 06:26 AM
Yes , you should be able to do this. Make sure
ActivateManualFailover=Yes and EnableFailover=No in PADR.ini and revert these settings back before you stop server service and start DR service
10-19-2021 01:03 AM
I'd ask the question, why do you need to even start the DR Vault after making the change to the dbparm.ini ?
The change to dbparm will not have any effect to the DR Vault until it is actually active, so you can just update the dbparm and leave it at that. If/When the DR Vault comes online the new parameter will be used.
That being said, if you needed to test that the parameter has the desired effect on the DR Vault, then @Matt Jennison and @Vinay Vasanth's comments are the way to go.
Just a couple of notes around Vinay's comment:
1) Once the DR Vault has been started with ActivateManualFailover=Yes, this value will automatically be set to No by the DR service, so you do not need to manually revert it.
2) Changing EnableFailover=No will have no effect on starting the DR Vault, this parameter is purely to enable automatic failover in the case of a Primary Vault outage. It may be that he meant FailoverMode=No, in which case, this value will need to be set back to No after a manual failover to ensure that the DR service does not just bring the Vault back online when you are finished testing.
10-19-2021 06:24 AM
@George Boddey
this is to ensure the changes take affect. if there is a syntax error within the DBParm.ini file then the vault will not start, so testing in this way will ensure there are no errors or issues when you need it to work.
-Matt
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!

