MSDP volume group disaster recovery
You can protect the MSDP catalog of an MVG server as a regular MSDP server. You can use an MSDP catalog backup policy.
Scenario 1: MSDP catalog can be recovered
If the MSDP catalog can be recovered, you can follow the same steps to reconfigure the MSDP server with the recovered catalog.
We recommend that you protect the MSDP catalog of an MVG server as a regular MSDP server. One way is to use an MSDP catalog backup policy.
Scenario 2: MSDP catalog cannot be recovered from MVG server catalog backup
For some reason, the MSDP catalog cannot be recovered because there is no backup or the backup data cannot be used. You can rebuild the MSDP volume group configuration data and reconfigure the MVG server.
Table:
No | Step | Description |
|---|---|---|
1 | Reassemble the MSDP volume group configuration. | Find out the MVG volumes that MVG server had and the physical volumes each MVG volume used. Use one of the following ways to find out the information.
|
2 | Reconfigure an MVG server. | You can configure the MSDP server with MVG option selected like an MSDP server. Using the previous host name is recommended but is not necessary. If NetBackup lost the configuration of the storage server for the MVG server, use NetBackup web UI to configure it. If NetBackup still has the configuration of the storage server for the MVG server, use nbdevconfig -setconfig command. The configuration list file has no difference with that for a regular MSDP server, except we need to enable MVG by adding: V7.5 "mvgenabled" "1" string For more information, See Configuring an MVG server using the command-line. |
3 | Add back the MVG volumes one by one. | If NetBackup still has the disk pool configured with the MVG volumes, run NetBackup command nbdevconfig -setconfig with add-virtual-volume option to add back the MVG volumes one by one, with the information collected in Step 1. See Creating an MVG volume using the command-line. In case the disk pool configuration with the MVG volumes was lost, use NetBackup web UI to recreate the corresponding disk pools and MVG volumes with the information collected in Step 1. In this case, NetBackup catalog also most likely lost the backup image records, which are associated with the MVG volumes. Thus, like recovering a regular MSDP server for the physical volumes, NetBackup image 2-phase import is also needed after the MVG server and MVG volumes are reconfigured. |
4 | (Optional) Adjust the client and policy assignment table. | The client and policy assignment table is rebuilt in the step 3. If a client and policy combination were taken by multiple MSDP servers before disaster, the information can be rebuilt but the primary one may be different than the one before the disaster. Run the following MSDP commands to check and adjust the primary MSDP server of a client and policy combination if required: cacontrol --cluster get-cp-assignment <dsid-of-mvg-volume> [<client> [<policy>]] cacontrol --cluster set-cp-assignment <dsid-of-mvg-volume> <client> <policy> <msdp-server> The MSDP server which has more data for the client and policy is usually set as the primary one. |