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
- About the MSDP Deduplication Multi-Threaded Agent
- About MSDP fingerprinting
- Enabling 400 TB support for MSDP
- About MSDP Encryption using NetBackup Key Management Server service
- 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 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
- 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 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
- 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
- Configuring MSDP data integrity checking behavior
- 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
- 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
Creating a protection point for a universal share
You can create a protection point for the data in a universal share that lets you manage and protect the data in the share. Creating a protection point is accomplished by creating a Universal-Share backup policy.
If an MSDP storage server is configured with multiple universal shares, a single policy can be created for some or all of the shares. You can also create individual policies, one for each share. If multiple storage servers are configured with universal shares, each storage server should be configured with its own specific policy to protect the universal shares on that storage server.
See Overview of universal shares.
Any data that is initially ingested into a universal share resides in the MSDP located on the appliance-based media server that hosts the universal share. This data is not referenced in the NetBackup Catalog and no retention enforcement is enabled. Therefore, the data that resides in the universal share is not searchable and cannot be restored using NetBackup. Control of the data in the share is managed only by the host where that share is mounted.
The protection point feature supports direct integration with NetBackup. A protection point is a point-in-time copy of the data that exists in a universal share. Creation and management of a protection point is accomplished through a NetBackup policy, which defines all scheduling and retention of the protection point. The protection point uses the Universal-Share policy, which can be configured through NetBackup web UI. After a protection point for the data in the universal share is created, that point-in-time copy of the universal share data can be managed like any other protected data in NetBackup. Protection point data can be replicated to other NetBackup Domains or migrated to other storage types like tape or cloud, using storage lifecycle policies. Each protection point copy is referenced to the name of the associated universal share.
To create a protection point policy for a universal share
- Create a policy using with the NetBackup Administration Console or the NetBackup web UI.
- On the Attributes tab, select Universal-Share from the Policy type list.
For the Policy storage, you must use the storage unit that hosts the universal share. You must create one if one does not exist.
If multiple storage servers are configured with universal shares, each of the storage servers should be configured with its own specific policy. This configuration ensures that the universal shares on that storage server are protected.
- Under Destination, select storage unit from the Policy storage list.
See Policy storage (policy attribute) in NetBackup Administrator's Guide Volume I for more information about policy storage setting.
The storage unit for universal share policy must be in the same disk pool volume where the universal share is created.
- On the Schedules tab, select either FULL or INCR.
- On the Clients tab, enter the name of the desired client.
Universal share is an agentless technology, so the client name that is specified is used only for cataloging purposes. You can enter a NetBackup Appliance, NetBackup Virtual Appliance, Flex Appliance media server application instance, or MSDP BYO server name or a host where universal share is mounted. The client name can be a short name, Fully Qualified Domain Name (FQDN), or IP address.
- On the Backup Selections tab, enter the path of the universal share.
You can find the export path from the Universal share details page NetBackup web UI: Storage > Storage Configuration > Universal Share.
For example:
/mnt/vpfs_shares/3cc7/3cc77559-64f8-4ceb-be90-3e242b89f5e9
You can use the NEW_STREAM directive if you require multistream backups.
You can also use the BACKUP X USING Y directive, which allows cataloging under a different directory than the universal share path. For example:
BACKUP /database1 USING /mnt/vpfs_shares/3cc7/3cc77559-64f8-4ceb-be90-3e242b89f5e9
. In this example, the backup is cataloged under/demo/database1
. - Run the Universal-Share policy.
After the backups are created, you can manage the backups with NetBackup features, such as restore, duplication, Auto Image Replication, and others.
You can instantly access backup copies from local LSU or cloud LSU with web UI or NetBackup Instant Access APIs.
For more information about instant access for cloud LSU:
See About instant access for object storage .
For information about NetBackup APIs, see the following website:
https://sort.veritas.com/documents
Select NetBackup and then the version at the bottom of the page.