Promoting Secondary ESA to Primary ESA

Promoting Secondary ESA to Primary ESA

If there is a failover from Primary ESA P1 to Secondary ESA S3 in DR Site, refer this Architecture Diagram, and if the down time of Primary ESA P1 is going to be for more than an hour, then it is recommended to perform the following steps:

1. Make secondary ESA S3 as Primary. Create a replication task to replicate the Policy Management and other required data from Secondary ESA S3 to Primary ESA P1.

2. As soon as the Primary ESA P1 is online, ensure to disable the replication task that is already created.

Perform the following steps for performing failover from Primary to DR Site and failback, that is, from DR site to Primary site:

1. Failover to DR site

   Since ESA P1 in primary site is down, failover to DR site’s ESA, that is, ESA S3 happens.

2. Promote Secondary ESA to Primary in DR Site

   Secondary ESA S3 is now promoted to Primary by enabling the TAC replication job to replicate from ESA S3 to all other ESAs.

3. Bring up ESA P1 in Site A as Secondary

   1. Once ESA P1 in primary site is ready to be brought up, bring it up as secondary ESA.

   2. As ESA S3 is already elevated to Primary, ESA P1 would start getting the latest updates from ESA S3 through replication.

      This can be confirmed through the following steps:

      a. Log in to ESA P1 Web UI.

      b. Navigate to System > Task Scheduler.

      c. Select the replication task.

      d. Scroll down the page to view the details of the scheduled task.

      e. Ensure that Exportimport command in the Command line shows the updated command as per Step 2.

   3. Allow for replication tasks from ESA S3 to ESA P1 to happen for atleast 2 cycles.

4. Failback to Primary Site

   1. After the original primary ESA (ESA P1) has replicated from primary ESA, that is, ESA S3, then follow the below steps to disable the replication task in ESA S3 to other ESAs.

      a. Log in to web UI of ESA S3.

      b. Disable the replication task to replicate data from ESA s3 to other ESAs.

   2. Perform the following steps to enable replication task in ESA P1:

      a. Log in to web UI of original primary ESA (ESA P1).

      b. Enable the replication task to replicate data from ESA P1 to ESA S3.

      c. Restore GTM to point to primary site.

      d. Validate that all the pepserver node entry in the ESA P1 is GREEN.