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 Veritas Alta Recovery Vault Amazon and Amazon Government using the CLI
Use the following procedure to configure Veritas Alta Recovery Vault for Amazon and Amazon Government using the CLI.
Table: Steps for configuring Alta Recovery Vault for Amazon and Amazon Government with the CLI
Steps | Task | Instructions |
---|---|---|
Step 1 | Retrieve credentials. | Retrieve Veritas Alta Recovery Vault credentials from your Veritas NetBackup account manager. |
Step 2 | Add credentials using the option. | Log into NetBackup web UI and perform the following:
|
Step 3 | Create an MSDP storage server. | |
Step 4 | Create a cloud instance alias. | Use the following examples depending on your environment:
The cloud alias name is <storage server>_<lsu name>, and is used to create a bucket. |
Step 6 | Create a configuration file, then run nbdevconfig command. | Configuration file content for adding a new cloud LSU (configuration setting and description):
For an example of a configuration file with encryption disabled, refer to the Azure section. See Configuring Veritas Alta Recovery Vault Azure and Azure Government using the CLI. Note: All encrypted LSUs in one storage server must use the same After you create the configuration file, run the nbdevconfig command: /usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server <storage server> -stype PureDisk -configlist <configuration file path> Note: The parameter <storage server> must be the same as the parameter <storage server> in Step 4. |
Step 7 | Create disk pool. | Create disk pool by running the nbdevconfig command. The following are examples of using the nbdevconfig command: Example 1: /usr/openv/netbackup/bin/admincmd/nbdevconfig -previewdv -storage_servers <storage server name> -stype PureDisk | grep <LSU name> > /tmp/dvlist Example 2: /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 or NetBackup Administration Console. |
Step 8 | Create storage unit. | Create storage unit by using bpstuadd command. The following are examples of using the bpstuadd command: /usr/openv/netbackup/bin/admincmd/bpstuadd -label <storage unit name> -odo 0 -dt 6 -dp <disk pool name> -nodevhost Note: You can also create the storage server from the NetBackup web UI or NetBackup Administration Console. |
Note:
Use the web UI and update the refresh token within Credential management.
The csconfig cldinstance command displays the Need Token Renew
flag that retrieves alias information (Yes/No). When Yes
, the Recovery Vault expects the storage account and refresh token credentials instead of storage account and access key.
The cloud instance has an option to disable (0) or enable (1) the need token renew (-ntr) option which has a default value of yes (1) for Veritas-Alta-Recovery-Vault-Amazon
and Veritas-Alta-Recovery-Vault- Amazon-Gov
.
Example usage of csconfig cldinstance with -ntr:
csconfig cldinstance -us -in <instance name> -sts <alias name> -ntr <0,1>
Note:
When you add the cloud LSU on a back-level media server using the CLI, the -ntr option must be set to No (0). You must set the option to No because older versions of the media server don't have support for token based credentials. When you use a NetBackup storage server version 10.3.1 or newer, the cloud alias instance must have the -ntr option set to Yes. The setting cannot be set to No.
Starting with NetBackup 10.3.1, the nbcldutil command does not support -validatecreds options when you configure Veritas Alta Recovery Vault for Amazon and Amazon Government.
To use this utility, you must create a credential name using the NetBackup web UI and also create a cloud alias using the csconfig command similar to the following example:
/usr/openv/netbackup/bin/admincmd/csconfig cldinstance -as -in Veritas-Alta-Recovery-Vault-Amazon -sts <storage_server_name> -stype PureDisk -lsu_name test1 Successfully added storage server(s): <storage_server_name>_test1
Added the --enable_sts option to use for Veritas Alta Recovery Vault Amazon. Additionally, if the --enable _sts option is used you must export the following environment variables:
MSDPC_MASTER_SERVER - This option is name of the NetBackup primary server.
MSDPC_ALIAS - This option is the cloud alias created using csconfig.
MSDPC_ACCESS_KEY - A credential name and MSDPC_SECRET_KEY is a dummy string.
In addition to access key and secret key, NetBackup supports the MSDPC_CMS_CRED_NAME variable.
MSDPC_CMS_CRED_NAME - This is a credential name.
Example output
export MSDPC_PROVIDER=vamazon export MSDPC_REGION="us-east-1" export MSDPC_CMS_CRED_NAME=<credential name> export MSDPC_MASTER_SERVER=<primary server> export MSDPC_ALIAS=<storage_server_name>_testnew /usr/openv/pdde/pdcr/bin/msdpcldutil create -b rv-worm1 -v dv-worm --mode GOVERNANCE --min 1D --max 3D --live 2023-12-31 --enable_sts
Alternatively, you can provide an access token that you receive from Veritas to create the WORM bucket or volume. This option is not recommended because the media server must connect to the Recovery Vault web server and Veritas has to provide the Recovery Vault web server URI.
MSDPC_RVLT_API_URI - A new environment parameter for use when Veritas provides a different endpoint.
MSDPC_ACCESS_TOKEN - An access token which is part of the credentials that Veritas provides.