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
Replicating the backup images from the IRE domain to the production domain
If the backup images at the production domain are lost for some reasons, you may need to replicate the backup images from the IRE domain back to the production domain. You can also replicate these backup images to a new domain.
To replicate the backup images from the IRE domain to the production domain
- Ensure that NetBackup certificate authority (NBCA) or an external certificate authority (ECA) are configured on the IRE storage server.
For BYO media server: See the step 1 of the Configuring A.I.R. for replicating backup images from production environment to IRE BYO environment topic.
See Configuring A.I.R. for replicating backup images from production environment to IRE BYO environment.
For WORM storage server, Flex Scale, and Access Appliance: See the step 2 of the Configuring data transmission between a production environment and an IRE WORM storage server topic.
See Configuring data transmission between a production environment and an IRE WORM storage server.
- On the IRE primary server, configure replication target using a command line.
Create a configuration file for adding a replication target with the following information:
V7.5 "operation" " " string
The value must be set-replication to add a new replication target.
V7.5 " rephostname" " " string
Specifies the replication target host name.
V7.5 "replogin" " " string
Specifies the replication target storage server username.
V7.5 "reppasswd" " " string
Specifies the replication target storage server password.
V7.5 "repsourcevolume" " " string
Specifies the replication source volume name.
V7.5 "reptargetvolume" " " string
Specifies the replication target volume name.
Run the following command to apply the configuration file to add replication target:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server <IRE storage server name> -stype PureDisk -configlist <config file name>
Run the following command to update the disk pool information on the primary server:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -updatedp -stype PureDisk -dp <IRE disk pool name>
Sample:
[admin@ire-primary ~]# cat add-replication.txt V7.5 "operation" "set-replication" string V7.5 "rephostname" "msdp-prod.example.com" string V7.5 "replogin" "pduser" string V7.5 "reppasswd" "pdpass" string V7.5 "repsourcevolume" "PureDiskVolume" string V7.5 "reptargetvolume" "PureDiskVolume" string [admin@ire-primary ~]# /usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server msdp-ire.example.com -stype PureDisk -configlist add-replication.txt Storage server msdp-ire.example.com has been successfully updated [admin@ire-primary ~]# /usr/openv/netbackup/bin/admincmd/nbdevconfig -updatedp -stype PureDisk -dp dp-ire The following replication properties have been added to the disk pool : ReplicationSource Replication sources and/or targets have changed for disk volumes: PureDiskVolume Update of disk pool replication properties succeeded
- Ensure that the production primary server has one import SLP that targets the relevant MSDP storage unit. Create it if it does not exist.
- Run the following command on the IRE primary server to manually replicate the backup images to the production domain.
/usr/openv/netbackup/bin/admincmd/nbreplicate -backupid <backup id> -cn <local copy number> -rcn <copy number plus 101> -slp_name reverse-air -target_sts <production MSDP storage server name>
For example,
/usr/openv/netbackup/bin/admincmd/nbreplicate -backupid client1_1234567890 -cn 1 -rcn 102 -slp_name reverse-air -target_sts msdp-prod.example.com
Note:
Before you start the replication, ensure that the backup image with the same backup ID does not exist in the production domain. If it exists, you must expire the image at the production domain first. Otherwise, the new replicated image will not get automatically imported by the import SLP at the production primary server.