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 protection policy for the MSDP object store
The MSDP-Object-Store policy type protects the data that is put in MSDP S3 storage.
Following are the limitations about MSDP object store backups:
The media server must be a Red Hat operating system.
If bucket versioning is enabled, only the latest object versions can be backed up.
Only supports the MSDP S3 configured using NBCA and ECA.
You can provide multiple backup selections in one backup policy. However, these backup selections must belong to a same bucket.
If the MSDP S3 path you provide matches both an object and a prefix, the backup job fails.
For example, if the path is provided as
/bucket1/obj1
and the following object structure exists, the backup job fails: /bucket1/obj1, /bucket1/obj1/obj2.When MSDP object store backup job is running, the objects that are being backed up cannot be deleted or overwrote (non-versioning bucket) until the backup jobs finishes.
To create a protection policy for the MSDP object store
- Create a policy using the NetBackup web UI.
- On the Attributes tab, select MSDP-Object-Store from the policy type list.
- Under Destination, select storage unit from the policy storage list.
The storage unit for MSDP-Object-Store policy must be in the same disk pool volume where the MSDP S3 bucket is created.
See Policy storage (policy attribute) in the NetBackup Administrator's Guide Volume I for more information about policy storage setting.
- On the Schedules tab, select Full backup, Differential incremental backup, or Cumulative incremental backup.
- On the Backup Selections tab, click Add. Enter the path of the MSDP S3 bucket prefix in Pathname. Format: /<BucketName>/<Prefix>. Click Add to list.
The client name of the MSDP-Object-Store policy is generated automatically using the format MSDP_<StorageServerName>_<BucketName>.
- Run the MSDP-Object-Store policy.
After the backups are created, you can manage the backups with NetBackup features, such as restore, duplication, Auto Image Replication, and so on.