NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- 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 stream handlers
- MSDP deployment best practices
- Provisioning the storage
- Configuring deduplication
- About the MSDP Deduplication Multi-Threaded Agent
- About MSDP fingerprinting
- Enabling 400 TB support for MSDP
- Configuring a storage server for a Media Server Deduplication Pool
- About disk pools for NetBackup deduplication
- Configuring a Media Server Deduplication Pool storage unit
- Configuring client attributes for MSDP client-side deduplication
- About MSDP encryption
- About MSDP Encryption using NetBackup Key Management Server service
- About a separate network path for MSDP duplication and replication
- About MSDP optimized duplication within the same domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- About storage lifecycle policies
- Resilient network properties
- About variable-length deduplication on NetBackup clients
- About the MSDP pd.conf configuration file
- About saving the MSDP storage server configuration
- About protecting the MSDP catalog
- About NetBackup WORM storage support for immutable and indelible data
- Running MSDP services with the non-root user
- Running MSDP commands with the non-root user
- MSDP volume group (MVG)
- About the MSDP volume group
- Configuring the MSDP volume group
- 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 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
- About the cloud direct
- 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
- About MSDP data integrity checking
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Configuring and managing universal shares
- Introduction to universal shares
- Prerequisites to configure universal shares
- Managing universal shares
- Restoring data using universal shares
- Advanced features of universal shares
- Direct universal share data to object store
- Universal share accelerator for data deduplication
- Configure a universal share accelerator
- About the universal share accelerator quota
- Load backup data to a universal share with the ingest mode
- Universal share scale out
- Managing universal share services
- Troubleshooting issues related to universal shares
- 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
Instant access for MSDP object store
You can create instant access buckets for MSDP object store using NetBackup images.
The MSDP object store instant access is only applicable for Red Hat MSDP storage servers with Build-Your-Own (BYO) and NetBackup Flex Appliance environment.
You must generate at least one backup image for MSDP object store on the MSDP S3 bucket.
MSDP S3 interface must be configured on MSDP storage where the NetBackup images are located.
Note the following about the instant access MSDP object store features:
The instant access target storage server must have the MSDP S3 interface configured.
Versioning must be disabled on the instant access target bucket. If you specify a new bucket, by default versioning is disabled. If you specify an existing bucket where versioning is enabled, instant access fails.
The instant access target bucket must be located on the storage where the backup image is stored. If you specify a new bucket, by default it is created on the same storage where the backup image is stored. If you specify an existing bucket that is on a storage server that is different from where the backup image is stored, instant access fails.
For the source MSDP S3 buckets, if the backup images are generated in the earlier NetBackup releases, they may not be identified for instant access. You must generate backup images from the latest release to use MSDP object store instant access.
It is not recommended to use MSDP object store backup and instant access at the same time on the same MSDP storage server.
You must use the MSDP-Object-Store policy to create a NetBackup backup image.
You can create an instant access MSDP object store from a NetBackup image. The Buckets tab displays the source buckets and the Instant access MSDP object store tab displays all the target buckets that you create.
Note:
The instant access for MSDP object store feature only supports BYO and NetBackup Flex media platform.
Things to consider before you use the instant access feature
To create an instant access MSDP object store
- On the left, click Workloads > MSDP object store.
- Locate the bucket on the Buckets tab and click on it.
- Click the Recovery points tab, then click the date on which the backup occurred.
The available images appear in rows with the backup timestamp for each image.
- On the image or the copy of the image that has the option to recover using instant access, click Recover.
On the Create an instant access MSDP object store page, the MSDP object storage server name is displayed.
- In the Target bucket name field enter the name of the bucket where you want to create the instant access MSDP object store, and then click Save.
The target bucket name must be between 3 and 63 characters, must begin and end with a letter or number, and can contain only lowercase letters, numbers dots, and hyphens.
- After the instant access job starts, you can click the Restore activity tab to view the progress.
- For details about the target bucket, click on the bucket display name under the Instant access MSDP object store tab.
You must run the following command line options on the MSDP storage server where the instant access target bucket is located. This operation is not supported for the NetBackup web UI.
aws --cli-read-timeout 0 --endpoint <endpoint url> s3 rm s3://<bucket name> --recursive (empty the bucket)
aws --endpoint <endpoint url> s3 rb s3://<bucket name> (remove the bucket)
rm -f <storage dir>/s3_ia_instances/<bucketname>.json