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
Creating a cloud storage unit
Use the NetBackup web UI or the command line to create a cloud storage unit.
To create a cloud storage unit by using the NetBackup web UI see the following topic.
See Configuring the MSDP node cloud tier.
The following steps describe the method to create a cloud storage unit using the command line:
- Create an MSDP storage server.
- Create a cloud instance alias.
For example:
Example 1: Creating an Amazon S3 cloud instance alias
# /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -as -in amazon.com -sts <storage server> -lsu_name <lsu name>
Example 2: Creating an Amazon Glacier cloud instance alias
# /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -as -in amazon.com -sts <storage server> -lsu_name <lsu name> -storage_class GLACIER
Example 3: Creating a Microsoft Azure Archive cloud instance alias
# /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -as -in my -azure -sts <storage server> -lsu_name <lsu name> -storage_tier ARCHIVE -post_rehydration_period 3
The cloud alias name is <storage server>_<lsu name>, and is used to create a bucket.
- Create a new bucket (Optional)
For example:
# /usr/openv/netbackup/bin/nbcldutil -createbucket -storage_server <storage server>_<lsu name> -username <cloud user> -bucket_name <bucket name>
- Create a configuration file, then run nbdevconfig command.
Configuration file content for adding a new cloud LSU:
Configuration setting
Description
V7.5 "operation" "add-lsu-cloud" string
Specifies the value "add-lsu-cloud" for adding a new cloud LSU.
V7.5 "lsuName" " " string
Specifies the LSU name.
V7.5 "cmsCredName" " " string
Specifies the credential name.
V7.5 "lsuCloudBucketName" " " string
Specifies the cloud bucket name.
V7.5 "lsuCloudBucketSubName" " " string
Multiple cloud LSUs can use the same cloud bucket, this value distinguishes different cloud LSUs.
V7.5 "lsuEncryption" " " string
Optional value, default is NO.
Sets the encryption property for current LSU.
V7.5 "lsuKmsEnable" " " string
Optional value, default is NO.
Enables KMS for current LSU.
V7.5 "lsuKmsKeyGroupName" " " string
Optional value.
A Key group name is shared among all LSUs.
A Key group name must have valid characters: A-Z, a-z, 0-9, _ (underscore), - (hyphen), : (colon), . (period), and space.
V7.5 "lsuKmsServerName" " " string
Optional value.
The KMS server name is shared among all LSUs.
V7.5 "lsuKmsServerType" " " string
Optional value.
V7.5 "requestCloudCacheCapacity" "" string
Optional value.
Specifies the disk cache size. If there is no input, a default of 1017 GB is used.
Example 1: Configuration file with encryption disabled
V7.5 "operation" "add-lsu-cloud" string V7.5 "lsuName" "s3amazon1" string V7.5 "cmsCredName" "cpcp" string V7.5 "lsuCloudBucketName" "bucket1" string V7.5 "lsuCloudBucketSubName" "sub1" string
Example 2: Configuration file with encryption enabled
V7.5 "operation" "add-lsu-cloud" string V7.5 "lsuName" "s3amazon2" string V7.5 "cmsCredName" "cpcp" string V7.5 "lsuCloudBucketName" "bucket1" string V7.5 "lsuCloudBucketSubName" "sub2" string V7.5 "lsuEncryption" "YES" string V7.5 "lsuKmsEnable" "YES" string V7.5 "lsuKmsKeyGroupName" "test" string V7.5 "lsuKmsServerName" "test" string
Note:
All encrypted LSUs in one storage server must use the same keygroupname and kmsservername. If you use the nbdevconfig command to add a new encrypted cloud logical storage unit (LSU) and an encrypted LSU exists in this MSDP, the keygroupname must be the same as the keygroupname in the previous encrypted LSU.
See About MSDP Encryption using NetBackup Key Management Server service.
Create a configuration file and then run the following 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 2.
- Create a disk pool by using the nbdevconfig command.
For example:
# /usr/openv/netbackup/bin/admincmd/nbdevconfig -previewdv -storage_servers <storage server name> -stype PureDisk | grep <LSU name> > /tmp/dvlist
# /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.
- Create a storage unit by using bpstuadd command.
For example:
# /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 unit from the NetBackup web UI.