Manual Failover

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

Manual Failover

L4 Transporter

I have three vaults, 2nd vault is on autofail over from primary.

Now implementing third vault . on 3rd vault DR will be running to replicate from primary but failover would be manual.

 To configure manual failover. DR would be running as automatic and  Privateark service would be disable.

in padr.ini  ​Enablefailover=Yes (by default). Wondering to achieve manual failover should this value be = NO ?

 

1 accepted solution

Accepted Solutions

If EnableFailover is set to No then there will be no failover when it loses connection to the vault it's looking at in the vault.ini

 

@Sebastien Siegl​ is right, the instructions I gave you originally will be immediate, so be warned! If you don't want it to be immediate you are right in setting EnableFailover to No will not trigger failover automatically.

View solution in original post

9 REPLIES 9

L5 Sessionator

Hi @Syed Shah​ , yes you must set EnableFailover=no. This way your DR will never start PrivateArk Server, even if the main vault goes down.

 

However, with this configuration and in case the vault goes down, your DR will try 5 connections, which will fail, and then stop replication. To ensure it retries indefinitely to connect to the Vault, you must also set a higher number of Retries (limited but high number of retries), or set EnableCheck to no (unlimited number of retries).

L4 Transporter

Morning @Syed Shah​ - so you can add in a section into the PADR.ini called 'ActivateManualFailover=Yes' - there are instructions that have been published in a KB article and I think this is what you need - hope this helps you.

 

https://community.cyberark.com/s/article/00004628

L4 Transporter

​Thanks for you replies.

I am reading through this documents. It says to add 'ActivateManualFailover=Yes' but not saying anything about Enablefailover= ? should we leave this value as yes ?

 

 

Be advised that the documentation linked by @Abi Catt​ is to perform a manual and immediate failover.

L4 Transporter

​@Sebastien Siegl​  thanks for notifying this.

 

that means it will fail over manually from primary to DR as soon as we reset DR service on DR Vault . (after adding 'ActivateManualFailover=Yes')

 

Exactly, so this procedure is to be followed only on the day you decide to failover to your third vault.

If EnableFailover is set to No then there will be no failover when it loses connection to the vault it's looking at in the vault.ini

 

@Sebastien Siegl​ is right, the instructions I gave you originally will be immediate, so be warned! If you don't want it to be immediate you are right in setting EnableFailover to No will not trigger failover automatically.

L4 Transporter

​many thanks you just saved a day 🙂

even if we have Enablefailover=No still adding 'ActivateManualFailover=Yes' will cause failover or we have to change Enabelfailover=yes on the day when manual failover would be performed.

 

 

L4 Transporter

​Thanks for your help guys

  • 1 accepted solution
  • 1494 Views
  • 9 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!