Workflow: prepare for an NSP DR switchover

Description

Before you perform an NSP DR switchover, you must ensure that the conditions are in place for a successful reversal of the primary and standby NSP cluster roles.

The following sequence of high-level actions describes how to ensure that the primary and standby NSP clusters are in the correct state for a successful DR switchover.

Stages
 
1 

Use the System Health dashboard to verify that there are no outstanding Critical or Major alarms against any NSP cluster and to check the node status.

2 

On the primary cluster, verify that each pod listed in the following table is in the state shown.

On the standby cluster, ensure that all pads are running, including the pods in the following table.

Pod

Primary cluster

Standby cluster

nspos-zookeeper

Running

Running

nspos-postgresql 1

Running

Running

nspos-tomcat

Running

Running

nspos-prometheus

Running

Running

nspos-kafka

Running

n/a

nsp-tomcat

Running

Running

nspos-keycloak

Running

Running

nspos-oauth2-proxy

Running

Running

nspos-asm-app

Running

Running

nsp-role-mgr

Running

Running

nsp-file-service-app 2

Running

Running

Notes:

  1. Restarts during switchover to change role and functions

  2. If present; pod not required in all deployment types

3 

Perform How do I identify the NSP cluster DR roles? on each cluster.

4 

Perform How do I check NSP database synchronization? to ensure that the primary and standby databases are 100% synchronized.