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
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring the MSDP fingerprint cache behavior
- Configuring MSDP fingerprint cache seeding on the storage server
- About MSDP Encryption using NetBackup Key Management Server service
- Configuring a storage server for a Media Server Deduplication Pool
- Configuring a disk pool for deduplication
- Configuring a Media Server Deduplication Pool storage unit
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- Creating a storage lifecycle policy
- Resilient network properties
- Editing the MSDP pd.conf file
- About protecting the MSDP catalog
- Configuring an MSDP catalog backup
- About NetBackup WORM storage support for immutable and indelible data
- Running MSDP services with the non-root user
- 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
- 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 using universal shares
- Configuring universal share user authentication
- Using the ingest mode
- Enabling a universal share with object store
- Configure a universal share accelerator
- About the universal share accelerator quota
- 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
Configuring A.I.R. for replicating backup images from production environment to IRE BYO environment
Once IRE configuration is completed, the production NetBackup hosts are no longer able to access the IRE MSDP storage server. You need to enable MSDP reverse connection to allow the data transmission between the production MSDP server and the IRE MSDP server.
Note:
A.I.R. configuration operations can be performed when the external network is open by IRE air gap. All the given operations are performed on the IRE MSDP server.
Before you configure A.I.R. for replicating backup images from production environment to IRE BYO environment, ensure the following:
In the case of NetBackup certificate authority (CA), get the CA certificate and host certificate for the IRE MSDP storage server from the production primary server.
Create a token on the production primary server.
To configure A.I.R. for replicating backup images from production environment to IRE BYO environment
- Run the following commands:
NetBackup certificate:
/usr/openv/netbackup/bin/nbcertcmd -getCACertificate -server <production primary server>
/usr/openv/netbackup/bin/nbcertcmd -getCertificate -server <production primary server> -token <token>
External certificate:
/usr/openv/netbackup/bin/nbcertcmd -enrollCertificate -server <production primary server>
- Run the following command to enable MSDP reverse connection.
/usr/openv/pdde/shell/bin/ire_network_control reverse_connection --add production msdp server
- This step is not required if you have not configured any IRE schedule. That is because if the IRE schedule is not configured, MSDP reverse connection is enabled for 24 hours on all days. The production primary server can configure the SLP replication operation with any SLP window.
Once the MSDP reverse connection is configured, copy the IRE schedule to the NetBackup production domain as an SLP window. Use the following command:
/usr/openv/pdde/shell/bin/sync_ire_window --production_primary_server production primary server name --production_primary_server_username production primary server username [--slp_window_name slp_window_name ]
Where:
The production primary server name is the fully qualified domain name (FQDN) of the primary server in your production environment.
The production primary server username is the username of a NetBackup user with permission to list SLPs and SLP windows in the production environment.
The production primary server username must be in domain_name\user_name format on Windows.
The slp_window_name is the name of the SLP window to be synced with the IRE window. It is an optional parameter. If the SLP window is not specified, an SLP window with the name IRE_DEFAULT_WINDOW is created on the production primary server.
- You can then add the IRE MSDP storage server as a replication target of the production NetBackup domain. Then add the replication operation to an existing SLP to replicate from production NetBackup domain to IRE MSDP storage server using the following command:
/usr/openv/pdde/shell/bin/add_replication_op --production_primary_server production primary server name --production_primary_server_username production primary server username --source_slp_name source slp name --target_import_slp_name target import slp name --production_storage_server production storage server name --ire_primary_server_username ire primary server username --target_storage_server target storage server name --target_storage_server_username target storage server username --production_storage_unit msdp storage unit name used in source SLP [--slp_window_name slp window name]
Where:
The production primary server name is the fully qualified domain name (FQDN) of the primary server in your production environment.
The production primary server username is the username of a NetBackup user with permission to list SLPs and SLP windows in the production environment.
The production primary server username must be in domain_name\user_name format on Windows.
The production storage server name is the fully qualified domain name (FQDN) of the production storage server in your production environment.
The ire primary server username is the username for administrator user of IRE primary server.
The ire primary server username must be in domain_name\user_name format on Windows.
The source slp name is the SLP name on the production primary server against which a replication operation is added.
The target import slp name is the import SLP name from IRE primary server.
The target storage server name is the fully qualified domain name (FQDN) of the target MSDP storage server.
The target storage server username is the username of the target MSDP storage server.
The slp_window_name is the name of the SLP window that is synced with the IRE window. Alternatively, it is created on the production primary server before the operation. It is an optional parameter. If the SLP window is not specified, an SLP window with the name IRE_DEFAULT_WINDOW is used that must be created using the sync_ire_window command before the operation.
The production_storage_unit is the storage unit name of type PureDisk used in source SLP.
Note:
The source SLP and target import SLP need to be created before the operation.