About the disaster recovery for cloud LSU

If the disk on which the NetBackup software resides or the disk on which the deduplicated data resides fails, you can use the following steps to recover the system and data depending on different scenarios.

After recovery, your NetBackup deduplication environment functions normally. Any valid backup images on the cloud LSU storage are available for restores.

Before you start disaster recovery, ensure that:

Media server on which the MSDP service resides still works. If media server does not work, you must reinstall the media server. Refer to the NetBackup Installation Guide for reinstalling media server software.
KMS server is ready if KMS encryption is used by cloud LSU.
If you reuse a cloud LSU in a different domain, ensure that you add the correct cloud credentials with the same name using the Credential Management in web UI.

After disaster recovery for cloud LSU, importing backup images is needed with following cases:

The primary server has no catalog of images in MSDP storage. For example, when the primary server is reinstalled and catalog in the primary is lost. The catalog is needed to import backup images. Refer section "About importing backup images" in NetBackup Administrator's Guide, Volume I for more information.
The primary server has an incorrect catalog record about the MSDP storage. The catalog in the primary server is not correct any more as the storage server is moved to a new media server after the disaster recovery. To correct the catalog on the primary server, run the bpimage command. The new media server here means a newly added media server or other existing media server.
When the primary has catalog of images in MSDP storage and the same media server is used to do disaster recovery, it's not needed to do backup images importing.
Imports are not supported for backups stored on Amazon S3 Glacier, Deep Archive, and Microsoft Azure Archive cloud LSUs if they were previously migrated from Cloud Catalyst.

You can do the disaster recovery for cloud LSU with the following three steps:

Set up the MSDP storage server with local storage.
Add a cloud LSU to reuse existing cloud data.
Perform backup images importing if the catalog is not available in the primary server.

Scenario 1: The MSDP server name has not changed, the local storage is lost, and the NetBackup catalog is present

Step	Task	Procedure
1	Create an empty local LSU	See Configure/Reconfigure MSDP local storage.
2	Reuse Cloud LSU	See Reuse cloud LSU.

Step

Task

Procedure

Create an empty local LSU

See Configure/Reconfigure MSDP local storage.

Reuse Cloud LSU

See Reuse cloud LSU.

Scenario 2: The MSDP server name has not changed, the local storage is lost, and the NetBackup catalog is not present

Step	Task	Procedure
1	Delete old storage server-related configurations	Perform the following steps from Recovering from an MSDP storage server failure topic.See Recovering from an MSDP storage server failure. Delete the storage units that use the disk pool. Delete the disk pool. Delete the deduplication storage server. Delete the deduplication host configuration file. Delete the credentials on deduplication servers.
2	Configure the new storage server.	Run the following command on the primary server: /usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server "storage server" -stype PureDisk -media_server "media server" -st 9 Note: You can also create the storage server from the NetBackup web UI.
3	Create an empty local LSU.	See Configure/Reconfigure MSDP local storage. Note: Skip these steps if the storage server was created using the NetBackup web UI.
4	Reuse cloud LSU.	See Reuse cloud LSU.
5	Create disk pool for cloud LSUs.	Run the following commands on the primary server: /usr/openv/netbackup/bin/admincmd/nbdevconfig -previewdv -storage_servers <storage server name> -stype PureDisk \| grep <LSU name> > /tmp/dvlist /usr/openv/netbackup/bin/admincmd/nbdevconfig -createdp -dp <disk pool name> -stype PureDisk -dvlist /tmp/dvlist -storage_servers <storage server name> Note: You can also create the disk pool from the NetBackup web UI.
6	Prepare images for import on high-latency storage.	If the source version is 11.0 or later, MSDP automatically prepares images for import in the background. Wait for images to be ready for the import. Run the following command to check the status: /usr/openv/pdde/pdcr/bin/tiermover --status --lsu <LSU name> [--client <client>] [--policy <policy>] [--backupid <backup ID>] [--sobins] [--active] [--lsulist] [--debug] [--verbose] If the source version is earlier than 11.0 or the source server is down and did not finish pre-import operations, run the following command to prepare the images for import: /usr/openv/pdde/pdcr/bin/tiermover --start --lsu <LSU name> --client <client> --policy <policy> [--backupid <backup ID>] [--retrieval Bulk\|Standard\|Expedited] [--verbose] [--debug] Note: Import fails if the images are not ready for the import.
7	Import the images back.	Do two-phase import. See NetBackup Administrator's Guide, Volume I For the high-latency storage when the source is 11.0 or later: If import job for high-latency storage fails, it may be because the source storage did not finish preparing the images for the import before the disaster occurred. In that case, perform the step 6 again to prepare the images for import.

Scenario 3: The MSDP server name has changed, the local storage is not lost, and the NetBackup catalog is present

Step	Task	Procedure
1	Ensure that the old MSDP server is stopped if recovering from an old MSDP server to a new MSDP server.	Run the following commands on the old MSDP server: /usr/openv/netbackup/bin/bp.kill_all
2	Configure the new storage server.	Run the following command on the primary server: /usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server "storage server" -stype PureDisk -media_server "media server" -st 9 Note: You can also create the storage server from the NetBackup web UI.
3	Reuse an existing local storage path.	See Configure/Reconfigure MSDP local storage. Note: Skip these steps if the storage server was created using the NetBackup web UI.
4	Restart the storage server.	Run the following commands on the primary server: /usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all
5	Create disk pool for cloud LSUs.	Run the following commands on the primary server: /usr/openv/netbackup/bin/admincmd/nbdevconfig -previewdv -storage_servers <storage server name> -stype PureDisk \| grep <LSU name> > /tmp/dvlist /usr/openv/netbackup/bin/admincmd/nbdevconfig -createdp -dp <disk pool name> -stype PureDisk -dvlist /tmp/dvlist -storage_servers <storage server name> Note: You can also create the disk pool from the NetBackup web UI.
6	Update the catalog images.	Run the following command on the primary server: /usr/openv/netbackup/bin/admincmd/bpimage -newserver "new storage server" -oldserver "old storage server" -newdiskpool "new disk pool name" -olddiskpool "old disk pool name"
7	Delete old storage server-related configurations.	Run the following command on the old MSDP server. /usr/openv/netbackup/bin/bp.start_all Perform the following steps from Recovering from an MSDP storage server failure topic.See Recovering from an MSDP storage server failure. Delete the storage units that use the disk pool. Delete the disk pool. Delete the deduplication storage server. Delete the deduplication host configuration file. Delete the credentials on deduplication servers.

Scenario 4: The MSDP server name has changed, the local storage is not lost, and the NetBackup catalog is not present

Step	Task	Procedure
1	Delete old storage server-related configurations.	Perform the following steps from Recovering from an MSDP storage server failure topic.See Recovering from an MSDP storage server failure. Delete the storage units that use the disk pool. Delete the disk pool. Delete the deduplication storage server. Delete the deduplication host configuration file. Delete the credentials on deduplication servers.
2	Configure the new storage server.	Run the following command on the primary server: /usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server "storage server" -stype PureDisk -media_server "media server" -st 9 Note: You can also create the storage server from the NetBackup web UI.
3	Reuse an existing local storage path	See Configure/Reconfigure MSDP local storage. Note: Skip these steps if the storage server was created using the NetBackup web UI.
4	Restart the storage server.	Run the following commands on the new MSDP server: /usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all
5	Create disk pool for cloud LSUs.	Run the following commands on the primary server: /usr/openv/netbackup/bin/admincmd/nbdevconfig -previewdv -storage_servers <storage server name> -stype PureDisk \| grep <LSU name> > /tmp/dvlist /usr/openv/netbackup/bin/admincmd/nbdevconfig -createdp -dp <disk pool name> -stype PureDisk -dvlist /tmp/dvlist -storage_servers <storage server name> Note: You can also create the disk pool from the NetBackup web UI.
6	Prepare images for import on high-latency storage.	If the source version is 11.0 or later, MSDP automatically prepares images for import in the background. Wait for images to be ready for the import. Run the following command to check the status: /usr/openv/pdde/pdcr/bin/tiermover --status --lsu <LSU name> [--client <client>] [--policy <policy>] [--backupid <backup ID>] [--sobins] [--active] [--lsulist] [--debug] [--verbose] If the source version is earlier than 11.0 or the source server is down and did not finish pre-import operations, run the following command to prepare the images for import: /usr/openv/pdde/pdcr/bin/tiermover --start --lsu <LSU name> --client <client> --policy <policy> [--backupid <backup ID>] [--retrieval Bulk\|Standard\|Expedited] [--verbose] [--debug] Note: Import fails if the images are not ready for the import.
7	Import the images back.	Do two-phase import. See NetBackup Administrator's Guide, Volume I For the high-latency storage when the source is 11.0 or later: If import job for high-latency storage fails, it may be because the source storage did not finish preparing the images for the import before the disaster occurred. In that case, perform the step 6 again to prepare the images for import.

Scenario 5: The MSDP server name has changed, the local storage is lost, and the NetBackup catalog is present

Step	Task	Procedure
1	Configure the new storage server.	Run the following command on the primary server: /usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server "storage server" -stype PureDisk -media_server "media server" -st 9 Note: You can also create the storage server from the NetBackup web UI.
2	Create an empty local LSU.	See Configure/Reconfigure MSDP local storage. Note: Skip these steps if the storage server was created using the NetBackup web UI.
3	Reuse cloud LSU.	See Reuse cloud LSU.
4	Create disk pool for cloud LSUs.	Run the following commands on the primary server: /usr/openv/netbackup/bin/admincmd/nbdevconfig -previewdv -storage_servers <storage server name> -stype PureDisk \| grep <LSU name> > /tmp/dvlist /usr/openv/netbackup/bin/admincmd/nbdevconfig -createdp -dp <disk pool name> -stype PureDisk -dvlist /tmp/dvlist -storage_servers <storage server name> Note: You can also create the disk pool from the NetBackup web UI.
5	Update the catalog images.	Run the following command on the primary server: /usr/openv/netbackup/bin/admincmd/bpimage -newserver "new storage server" -oldserver "old storage server" -newdiskpool "new disk pool name" -olddiskpool "old disk pool name"
6	Delete old storage server-related configurations.	Run the following command on the old MSDP server. /usr/openv/netbackup/bin/bp.start_all Perform the following steps from Recovering from an MSDP storage server failure topic.See Recovering from an MSDP storage server failure. Delete the storage units that use the disk pool. Delete the disk pool. Delete the deduplication storage server. Delete the deduplication host configuration file. Delete the credentials on deduplication servers.

Scenario 6: The MSDP server name has changed, the local storage is lost, and the NetBackup catalog is not present

Step	Task	Procedure
1	Delete old storage server-related configurations.	Perform the following steps from Recovering from an MSDP storage server failure topic.See Recovering from an MSDP storage server failure. Delete the storage units that use the disk pool. Delete the disk pool. Delete the deduplication storage server. Delete the deduplication host configuration file. Delete the credentials on deduplication servers.
2	Configure the new storage server.	Run the following command on the primary server: /usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server "storage server" -stype PureDisk -media_server "media server" -st 9 Note: You can also create the storage server from the NetBackup web UI.
3	Create an empty local LSU.	See Configure/Reconfigure MSDP local storage. Note: Skip these steps if the storage server was created using the NetBackup web UI.
4	Reuse cloud LSU.	See Reuse cloud LSU.
5	Create disk pool for cloud LSUs.	Run the following commands on the primary server: /usr/openv/netbackup/bin/admincmd/nbdevconfig -previewdv -storage_servers <storage server name> -stype PureDisk \| grep <LSU name> > /tmp/dvlist /usr/openv/netbackup/bin/admincmd/nbdevconfig -createdp -dp <disk pool name> -stype PureDisk -dvlist /tmp/dvlist -storage_servers <storage server name> Note: You can also create the disk pool from the NetBackup web UI.
6	Prepare images for import on high-latency storage.	If the source version is 11.0 or later, MSDP automatically prepares images for import in the background. Wait for images to be ready for the import. Run the following command to check the status: /usr/openv/pdde/pdcr/bin/tiermover --status --lsu <LSU name> [--client <client>] [--policy <policy>] [--backupid <backup ID>] [--sobins] [--active] [--lsulist] [--debug] [--verbose] If the source version is earlier than 11.0 or the source server is down and did not finish pre-import operations, run the following command to prepare the images for import: /usr/openv/pdde/pdcr/bin/tiermover --start --lsu <LSU name> --client <client> --policy <policy> [--backupid <backup ID>] [--retrieval Bulk\|Standard\|Expedited] [--verbose] [--debug] Note: Import fails if the images are not ready for the import.
7	Import the images back.	Do two-phase import. See NetBackup Administrator's Guide, Volume I For the high-latency storage when the source is 11.0 or later: If import job for high-latency storage fails, it may be because the source storage did not finish preparing the images for the import before the disaster occurred. In that case, perform the step 6 again to prepare the images for import.

About the disaster recovery for cloud LSU

Feedback

Feedback