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 KMS 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
- 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 immutable object support for AWS S3 compatible platforms
- About immutable storage support for Azure blob storage
- About immutable storage support for Google Cloud Storage
- 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
- Monitoring deduplication activity
- 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
- Using the ingest mode
- Enabling a universal share with object store
- Configuring isolated recovery environment (IRE)
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- 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 installation issues
- 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
Importing certificates from the deduplication shell
Use the following procedures to import NetBackup or external certificates from the deduplication shell.
To import a NetBackup certificate
- Open an SSH session to the server as the msdpadm user, or for NetBackup Flex Scale, as an appliance administrator.
- Run one of the following commands:
To request the NetBackup CA certificate from the primary server:
setting certificate get-CA-certificate
By default, the command uses the first primary server entry in the NetBackup configuration file. You can specify an alternate primary server with the primary_server parameter. For example:
setting certificate get-CA-certificate primary_server=<alternate primary server hostname>
To request a host certificate from the primary server:
setting certificate get-certificate [force=true]
Where [force=true] is an optional parameter that overwrites the existing certificate if it already exists.
By default, the command uses the first primary server entry in the NetBackup configuration file. You can specify an alternate primary server with the primary_server parameter. For example:
setting certificate get-certificate primary_server=<alternate primary server hostname>
Depending on the primary server security level, the host may require an authorization or a reissue token. If the command prompts that a token is required for the request, enter the command again with the token for the host ID-based certificate. For example:
setting certificate get-certificate primary_server=<alternate primary server hostname> token=<certificate token> force=true
To import external certificates
- Open an SSH session to the server as the msdpadm user, or for NetBackup Flex Scale, as an appliance administrator.
- Run one of the following commands:
To download and install both the external CA certificate and the host certificate:
setting certificate install-external-certificates cacert=<trust store> cert=<host certificate> private_key=<key> [passphrase=<passphrase>] scp_host=<host> scp_port=<port>
Where:
<trust store> is the trust store in PEM format.
<host certificate> is the X.509 certificate of the host in PEM format.
<key> is the RSA private key in PEM format.
[passphrase=<passphrase>] is an optional parameter for the passphrase of the private key. This parameter is required if the key is encrypted.
<host> is the hostname of the host that stores the external certificates.
<port> is the port to connect to on the remote host.
To download and install the external CA certificate:
setting certificate get-external-CA-certificate cacert=<trust store> scp_host=<host> scp_port=<port>
Where:
<trust store> is the trust store in PEM format.
<host> is the hostname of the host that stores the external certificates.
<port> is the port to connect to on the remote host.
To download and install the external host certificate:
setting certificate get-external-certificates cert=<host certificate> private_key=<key> [passphrase=<passphrase>] scp_host=<host> scp_port=<port>
Where:
<host certificate> is the X.509 certificate of the host in PEM format.
<key> is the RSA private key in PEM format.
[passphrase=<passphrase>] is an optional parameter for the passphrase of the private key. This parameter is required if the key is encrypted.
<host> is the hostname of the host that stores the external certificates.
<port> is the port to connect to on the remote host.
Note:
If an external host certificate already exists on the server, it is overwritten.
- (Optional) Run the following command to specify the revocation check level for the external certificates:
setting certificate set-CRL-check-level check_level=<DISABLE, LEAF, or CHAIN>
The check levels are as follows:
DISABLE: The revocation check is disabled. The revocation status of the certificate is not validated against the CRL during host communication.
LEAF: The revocation status of the leaf certificate is validated against the CRL. LEAF is the default value.
CHAIN: The revocation status of all certificates from the certificate chain is validated against the CRL.