In the active data center, perform “How do I back up the NSP cluster databases?” in the NSP System Administrator Guide.

Perform Step 3 to Step 10 on the standby data center.

Perform the following steps on the NSP deployer host to make sure all the existing PVCs including nsp-backup-storage are deleted.

1. Open the following file using a plain-text editor such as vi:

   /opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/config/nsp-config.yml

2. Edit the following line in the platform section, kubernetes subsection to read:

   deleteOnUndeploy: true

Uninstall NSP.

Enter the following:

Note: If the NSP cluster VMs do not have the required SSH key, you must include the --ask-pass argument in the command, as shown in the following example, and are subsequently prompted for the root password of each cluster member:

nspdeployerctl --ask-pass uninstall

# ./nspdeployerctl uninstall ↵

Enter the following:

# ./nspdeployerctl unconfig ↵

Configure the following parameters in the platform section, kubernetes subsection of the nsp-config.yml file as shown below:

  storage:

    readWriteOnceLowIOPSClass: "storage_class"

    readWriteOnceHighIOPSClass: "storage_class"

    readWriteOnceClassForDatabases: "storage_class"

    readWriteManyLowIOPSClass: "storage_class"

    readWriteManyHighIOPSClass: "storage_class"

where

readWriteOnceLowIOPSClass—for enabling ReadWriteOnce operations and maintaining storage IOPS below 10,000

readWriteOnceHighIOPSClass—for enabling ReadWriteOnce operations and maintaining storage IOPS above 10,000

readWriteOnceClassForDatabases—for enabling ReadWriteOnce operations and maintaining storage IOPS below 10,000 for NSP databases

readWriteManyLowIOPSClass—for enabling ReadWriteMany operations and maintaining storage IOPS below 10,000

readWriteManyHighIOPSClass—for enabling ReadWriteMany operations and maintaining storage IOPS above10,000

storage_class is your storage class name

Check if the storage classes meet the IOPS requirements.

Run the script to check the IOPS of the configured storage classes.

1. Enter the following on the NSP deployer host:

   # cd /opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/tools/support/storageIopsCheck/bin

2. Run the script by selecting each storage class individually or by selecting All Storage Classes.

   Output like the following is displayed and indicates if the script passes or fails.

   [root@ ]# ./nspstorageiopsctl 

   date time year -------------------- BEGIN ./nspstorageiopsctl --------------------

    

   [INFO]: SSH to NSP Cluster host ip_address successful

   1) readWriteManyHighIOPSClass            5) readWriteOnceClassForDatabases

   2) readWriteOnceHighIOPSClass            6) All Storage Classes

   3) readWriteManyLowIOPSClass             7) Quit

   4) readWriteOnceLowIOPSClass

   Select an option: 1

   [INFO] **** Calling IOPs check for readWriteManyHighIOPSClass - Storage Class Name (ceph-filesystem) Access Mode (ReadWriteMany) ****

   [INFO] NSP Cluster Host: ip_address

   [INFO] Validate configured storage classes are available on NSP Cluster

   [INFO] Adding helm repo nokia-nsp

   [INFO] Updating helm repo nokia-nsp

   [INFO] Executing k8s job on NSP Cluster ip_address

   [INFO] Creating /opt/nsp/nsp-storage-iops directory on NSP Cluster ip_address

   [INFO] Copying values.yaml to /opt/nsp/nsp-deployer/tools/nsp-storage-iops

   [INFO] Executing k8s job on NSP Cluster ip_address

   [INFO] Waiting for K8s job status...

   [INFO] Job storage-iops completed successfully.

   [INFO] Cleaning up and uninstalling k8s job

   [INFO] Helm uninstall cn-nsp-storage-iops successful

   STORAGECLASS         ACCESS MODE    READIOPS   WRITEIOPS  RESULT    STORAGECLASSTYPE

   ------------         -----------    --------   ---------  ------    ----------------

   storage_class     ReadWriteMany  12400      12500      true      readWriteManyHighIOPSClass

   [INFO] READ IOPS and WRITE IOPS meet the threshold of 10000.

   date time year ------------------- END ./nspstorageiopsctl - SUCCESS --------------------

If these requirements are not met, this may result in system performance degradation.

Configure and install NSP. See To install the NSP

Check data synchronization is complete for the following:

• For PostgreSQL and Neo4j, perform “How do I check NSP database synchronization?”in the NSP System Administrator Guide.

• For nsp-tomcat and nrcx-tomcat, see the following.

  This is an example of a consistent database returning a successful check:

  kubectl exec -it -n nsp-psa-restricted $MY_POD -c nsp-tomcat -- \

   /opt/nsp/server/replication/bin/neo4j-admin check-consistency --database=graph.db  --report-dir=/tmp

  Selecting JVM - Version:11.0.18+10-alpine-r0, Name:OpenJDK 64-Bit Server VM, Vendor:Alpine

  date time INFO  [o.n.k.i.s.f.RecordFormatSelector] Selected RecordFormat:PageAlignedV4_3[AF4.3.0] record format from store /opt/nsp/server/tomcat/work/data/databases/graph.db

  date time INFO  [o.n.k.i.s.f.RecordFormatSelector] Format not configured for store /opt/nsp/server/tomcat/work/data/databases/graph.db. Selected format from the store files: RecordFormat:PageAlignedV4_3[AF4.3.0]

  ...

  ... 100%

  Consistency check

  ...

  ... 100%

• File Service rsync

  Output includes:

  ... Running scheduled task to rsyncFileServerFiles to DR site with command: ...

  ... rsync result: Warning: Permanently added IP_address to the list of known hosts.

  ...

  ... rsync result: sending incremental file list ...

Perform the following on the NSP deployer host.

1. Open the following file using a plain-text editor such as vi:

   /opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/config/nsp-config.yml

2. Edit the following line in the platform section, kubernetes subsection to read:

   deleteOnUndeploy: false

Perform a NSP DR switchover to change the state of the standby data center to active.

Perform Step 3 to Step 10 on the previous active data center.

End of steps