NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Quick start
- Planning your deployment
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About MSDP performance
- About MSDP stream handlers
- MSDP deployment best practices
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- About the MSDP Deduplication Multi-Threaded Agent
- About MSDP fingerprinting
- Enabling 400 TB support for MSDP
- About MSDP Encryption using NetBackup Key Management Server service
- Configuring a storage server for a Media Server Deduplication Pool
- About disk pools for NetBackup deduplication
- Configuring a Media Server Deduplication Pool storage unit
- Configuring client attributes for MSDP client-side deduplication
- About MSDP encryption
- About a separate network path for MSDP duplication and replication
- About MSDP optimized duplication within the same domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- About storage lifecycle policies
- Resilient network properties
- About variable-length deduplication on NetBackup clients
- About the MSDP pd.conf configuration file
- About saving the MSDP storage server configuration
- About protecting the MSDP catalog
- About NetBackup WORM storage support for immutable and indelible data
- Running MSDP services with the non-root user
- MSDP volume group (MVG)
- About the MSDP volume group
- Configuring the MSDP volume group
- MSDP cloud support
- About MSDP cloud support
- Cloud space reclamation
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- About immutable object support for AWS S3
- About bucket-level immutable storage support for Google Cloud Storage
- About object-level immutable storage support for Google Cloud Storage
- About AWS IAM Role Anywhere support
- About Azure service principal support
- About NetBackup support for AWS Snowball Edge
- About the cloud direct
- S3 Interface for MSDP
- Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
- Identity and Access Management (IAM) for S3 interface for MSDP
- S3 APIs for S3 interface for MSDP
- Disaster recovery in S3 interface for MSDP
- Monitoring deduplication activity
- Viewing MSDP job details
- Managing deduplication
- Managing MSDP servers
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Changing a Media Server Deduplication Pool properties
- Configuring MSDP data integrity checking behavior
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Configuring and managing universal shares
- Introduction to universal shares
- Prerequisites to configure universal shares
- Managing universal shares
- Restoring data using universal shares
- Advanced features of universal shares
- Direct universal share data to object store
- Universal share accelerator for data deduplication
- Configure a universal share accelerator
- About the universal share accelerator quota
- Load backup data to a universal share with the ingest mode
- Managing universal share services
- Troubleshooting issues related to universal shares
- Configuring isolated recovery environment (IRE)
- Configuring an isolated recovery environment using the web UI
- Configuring an isolated recovery environment using the command line
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- About the external MSDP catalog backup
- Managing certificates from the deduplication shell
- Managing NetBackup services from the deduplication shell
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing S3 service from the deduplication shell
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
- Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
- About direct migration from Cloud Catalyst to MSDP direct cloud tiering
- Appendix C. Encryption Crawler
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 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.
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 | 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.
|
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. | |
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 | Import the images back. | Do two-phase import. |
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. | |
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: 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.
|
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.
|
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 | |
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 | Import the images back. | Do two-phase import. |
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. | |
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: 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.
|
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.
|
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. | |
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 | Import the images back. | Do two-phase import. |