Workflow: stop and start DR NSP clusters
Description
CAUTION System Degradation |
If the primary NSP cluster and associated primary components outside the cluster are not in the same data center, the maintenance shutdown described in this workflow may cause an undesired DR switchover of one or more components, which can be service-affecting.
Before you attempt to use this workflow, you must ensure that the primary NSP cluster and associated primary components outside the cluster are in the same data center. If not, perform the appropriate procedure to ensure that all component roles in each data center are aligned.
The following is the sequence of high-level actions required to stop and start the active and standby NSP clusters in a graceful manner for maintenance purposes.
See the following procedures for information about stopping and starting a cluster:
Stages
Perform orderly shutdown of standby components outside NSP cluster | |
1 |
If the NSP deployment includes NSP analytics servers, stop each analytics server in the standby data center, as described in How do I start or stop an analytics server?. |
2 |
If the NSP deployment includes NSP Flow Collectors:
|
3 |
If the NSP deployment includes an auxiliary database, stop the auxiliary database cluster in the standby data center, as described in How do I stop an auxiliary database cluster?. |
4 |
If the NSP deployment includes the NFM-P, perform the following steps.
|
Perform standby NSP cluster maintenance | |
5 |
Stop the standby NSP cluster, as described in How do I stop an NSP cluster?. |
6 |
Perform the required maintenance on the standby cluster. |
7 |
Start the standby cluster, as described in How do I start an NSP cluster?. |
Switch NSP cluster roles | |
8 |
Perform an activity switch to change the standby cluster role to active, as described in How do I perform an NSP DR switchover?. The standby cluster assumes the active role. |
Perform orderly startup of standby components outside cluster | |
9 |
If the NSP deployment includes the NFM-P, perform the following steps.
|
10 |
If the NSP deployment includes an auxiliary database, start the auxiliary database cluster in the former standby data center; see How do I start an auxiliary database cluster?. |
11 |
If the NSP deployment includes NSP Flow Collectors:
|
12 |
If the NSP deployment includes NSP analytics servers, start each analytics server in the former standby data center, as described in How do I start or stop an analytics server?. |
Perform orderly shutdown of former primary components outside NSP cluster | |
13 |
If the NSP deployment includes the NFM-P, perform the following steps.
|
14 |
If the NSP deployment includes NSP Flow Collectors:
|
15 |
If the NSP deployment includes NSP analytics servers, stop each analytics server in the standby data center, as described in How do I start or stop an analytics server?. |
Perform former primary NSP cluster maintenance | |
16 |
Stop the former active cluster, as described in How do I stop an NSP cluster?. |
17 |
Perform the required maintenance on the former active cluster. |
18 |
Start the former active cluster, as described in How do I start an NSP cluster?. |
Perform orderly startup of former primary components outside cluster | |
19 |
If the NSP deployment includes the NFM-P, perform the following steps.
|
20 |
If the NSP deployment includes an auxiliary database, start the auxiliary database cluster in the former primary data center; see How do I start an auxiliary database cluster?. |
21 |
If the NSP deployment includes NSP Flow Collectors:
|
22 |
If the NSP deployment includes NSP analytics servers, start each analytics server in the former primary data center, as described in How do I start or stop an analytics server?. |
Restore initial primary/standby NSP cluster roles | |
23 |
If required, perform an activity switch to restore the initial active and standby roles, as described in How do I perform an NSP DR switchover?. |