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.
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 has an incorrect catalog of images in MSDP storage. MSDP storage server resides on media server. When disable recovery is done by using a new media server, the new MSDP storage server resides on the new media server. At that case the catalog in the primary is incorrect, for the catalog still refer to old MSDP storage server which is not available. To correct the catalog in the primary, delete the old catalog and import backup images from the new MSDP storage server. The new media server here means a new 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.
Backup images importing is not supported when the cloud LSU is based on Amazon S3 Glacier, Deep Archive, and Microsoft Azure Archive.
Cloud LSU of Amazon S3 Glacier, Deep Archive, and Microsoft Azure Archive supports cloud disaster recovery only in Scenario 1 and Scenario 3.
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.
Step | Task | Procedure |
|---|---|---|
1 | Create an empty local LSU | |
2 | Reuse Cloud LSU | See Reuse cloud LSU |
Step | Task | Procedure |
|---|---|---|
1 | Expire the backup images | Expire all backup images that reside on the deduplication disk storage. Warning: Do not delete the images. They are imported back into NetBackup later in this process. If you use the bpexpdate command to expire the backup images, use the -nodelete parameter. |
2 | Delete old storage server-related configurations | 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. |
3 | Configure new storage server. | /usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server "storage server" -stype PureDisk -media_server "media server" -st 9 |
4 | Create an empty local LSU. | |
5 | Reuse cloud LSU. | See Reuse cloud LSU |
6 | Create disk pool for cloud LSUs. | /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. |
7 | Import the images back. | Do two-phase import. |
Step | Task | Procedure |
|---|---|---|
1 | Reuse existing local storage path | |
2 | Restart storage server. | /usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all |
Step | Task | Procedure |
|---|---|---|
1 | Expire the backup images. | Expire all backup images that reside on the deduplication disk storage. Warning: Do not delete the images. They are imported back into NetBackup later in this process. If you use the bpexpdate command to expire the backup images, use the -nodelete parameter. |
2 | Delete old storage server-related configurations. | 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. |
3 | Configure new storage server. | /usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server "storage server" -stype PureDisk -media_server "media server" -st 9 |
4 | Reuse existing local storage path | |
5 | Restart storage server. | /usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all |
6 | Create disk pool for cloud LSUs. | /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. |
7 | Import the images back. | Do two-phase import. |