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
Migrating from standard authentication to token-based authentication for Recovery Vault
If you have already configured Veritas Alta Recovery Vault with an older version of NetBackup, you must upgrade to a newer version. To make use of the token-based authentication for enhanced security, you must upgrade the primary and the media server to the following version to use this feature.
NetBackup 10.2 release for Azure.
NetBackup 10.3.1 release for Amazon.
To migrate the credentials
- Contact NetBackup Technical Support and ask for new credentials for Veritas Alta Recovery Vault Azure or Veritas Alta Recovery Vault Amazon.
- Log into NetBackup web UI and add the new credentials to Credential management.
On the left, click Credential management.
On the Named credentials tab, click Add and provide the following properties:
Credential name
Tag
Description
Click Next.
In the drop-down, select Veritas Alta Recovery vault.
Click Veritas Alta Recovery Vault Azure or Veritas Alta Recovery Vault Amazon.
Add the Storage account and Refresh token.
Select or add a role that can access this credential.
Review the information and click Finish.
- Update the -ntr option with the csconfig cldinstance command.
Example:
/usr/openv/netbackup/bin/admincmd/csconfig cldinstance -us -in <instance name> -sts <alias name> -ntr 1
Confirm the change by making sure that the need token renew option -ntr is set to 1 for enabling this option on the storage server:
<install path>/netbackup/bin/admincmd/csconfig cldinstance -i
- Update the credentials using nbdevconfig.
Create a configuration file with
cmsCredName
as the credential name that you created using the Credential management.Example of the configuration file:
V7.5 "operation" "update-lsu-cloud" string V7.5 "lsuName" "myvolume" string V7.5 "cmsCredName" "RVLT-creds" string V7.5 "lsuCloudBucketName" "mybucket" string V7.5 "lsuCloudBucketSubName" "myvolume" string
- Use the new configuration file to update the credentials.
<install path>/netbackup/bin/admincmd/nbdevconfig -setconfig -stype PureDisk -storage_server <storage_server> -configlist <config file path>
Restart the services on the primary server and the media server for the changes to take effect.
- Verify the restore of the old backup and run a new backup. Restore the new backup.