Veritas NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Quick start
- Planning your deployment
- Planning your MSDP deployment
- NetBackup naming conventions
- About MSDP deduplication nodes
- About the NetBackup deduplication destinations
- About MSDP storage capacity
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About the NetBackup Deduplication Engine credentials
- About the network interface for MSDP
- About MSDP port usage
- About MSDP optimized synthetic backups
- About MSDP and SAN Client
- About MSDP optimized duplication and replication
- About MSDP performance
- About MSDP stream handlers
- MSDP deployment best practices
- Use fully qualified domain names
- About scaling MSDP
- Send initial full backups to the storage server
- Increase the number of MSDP jobs gradually
- Introduce MSDP load balancing servers gradually
- Implement MSDP client deduplication gradually
- Use MSDP compression and encryption
- About the optimal number of backup streams for MSDP
- About storage unit groups for MSDP
- About protecting the MSDP data
- Save the MSDP storage server configuration
- Plan for disk write caching
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- Configuring MSDP server-side deduplication
- Configuring MSDP client-side deduplication
- About the MSDP Deduplication Multi-Threaded Agent
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring deduplication plug-in interaction with the Multi-Threaded Agent
- About MSDP fingerprinting
- About the MSDP fingerprint cache
- Configuring the MSDP fingerprint cache behavior
- About seeding the MSDP fingerprint cache for remote client deduplication
- Configuring MSDP fingerprint cache seeding on the client
- Configuring MSDP fingerprint cache seeding on the storage server
- Enabling 250-TB support for MSDP
- About MSDP Encryption using NetBackup KMS service
- About MSDP Encryption using external KMS server
- Configuring a storage server for a Media Server Deduplication Pool
- Configuring a storage server for a PureDisk Deduplication Pool
- About disk pools for NetBackup deduplication
- Configuring a disk pool for deduplication
- Creating the data directories for 250-TB MSDP support
- Adding volumes to a 250-TB Media Server Deduplication Pool
- Configuring a Media Server Deduplication Pool storage unit
- Configuring client attributes for MSDP client-side deduplication
- Disabling MSDP client-side deduplication for a client
- About MSDP compression
- About MSDP encryption
- MSDP compression and encryption settings matrix
- Configuring encryption for MSDP backups
- Configuring encryption for MSDP optimized duplication and replication
- About the rolling data conversion mechanism for MSDP
- Modes of rolling data conversion
- MSDP encryption behavior and compatibilities
- Configuring optimized synthetic backups for MSDP
- About a separate network path for MSDP duplication and replication
- Configuring a separate network path for MSDP duplication and replication
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- About MSDP replication to a different domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- About trusted master servers for Auto Image Replication
- About the certificate to be used for adding a trusted master server
- Adding a trusted master server using a NetBackup CA-signed (host ID-based) certificate
- Adding a trusted master server using external CA-signed certificate
- Removing a trusted master server
- Enabling NetBackup clustered master server inter-node authentication
- Configuring NetBackup CA and NetBackup host ID-based certificate for secure communication between the source and the target MSDP storage servers
- Configuring external CA for secure communication between the source MSDP storage server and the target MSDP storage server
- Configuring a target for MSDP replication to a remote domain
- About configuring MSDP optimized duplication and replication bandwidth
- About performance tuning of optimized duplication and replication for MSDP cloud
- About storage lifecycle policies
- About the storage lifecycle policies required for Auto Image Replication
- Creating a storage lifecycle policy
- About MSDP backup policy configuration
- Creating a backup policy
- Resilient Network properties
- Specifying resilient connections
- Adding an MSDP load balancing server
- About variable-length deduplication on NetBackup clients
- About the MSDP pd.conf configuration file
- Editing the MSDP pd.conf file
- About the MSDP contentrouter.cfg file
- About saving the MSDP storage server configuration
- Saving the MSDP storage server configuration
- Editing an MSDP storage server configuration file
- Setting the MSDP storage server configuration
- About the MSDP host configuration file
- Deleting an MSDP host configuration file
- Resetting the MSDP registry
- About protecting the MSDP catalog
- Changing the MSDP shadow catalog path
- Changing the MSDP shadow catalog schedule
- Changing the number of MSDP catalog shadow copies
- Configuring an MSDP catalog backup
- Updating an MSDP catalog backup policy
- About MSDP FIPS compliance
- Configuring the NetBackup client-side deduplication to support multiple interfaces of MSDP
- About MSDP multi-domain support
- About MSDP mutli-domain VLAN Support
- About NetBackup WORM storage support for immutable and indelible data
- Configuring deduplication to the cloud with NetBackup Cloud Catalyst
- Using NetBackup Cloud Catalyst to upload deduplicated data to the cloud
- Cloud Catalyst requirements and limitations
- Configuring a Linux media server as a Cloud Catalyst storage server
- Configuring a Cloud Catalyst storage server for deduplication to the cloud
- How to configure a NetBackup Cloud Catalyst Appliance
- How to configure a Linux media server as a Cloud Catalyst storage server
- Configuring a Cloud Catalyst storage server as the target for the deduplications from MSDP storage servers
- Certificate validation using Online Certificate Status Protocol (OCSP)
- Managing Cloud Catalyst storage server with IAM Role or CREDS_CAPS credential broker type
- Configuring a storage lifecycle policy for NetBackup Cloud Catalyst
- About the Cloud Catalyst esfs.json configuration file
- About the Cloud Catalyst cache
- Controlling data traffic to the cloud when using Cloud Catalyst
- Configuring source control or target control optimized duplication for Cloud Catalyst
- Configuring a Cloud Catalyst storage server as the source for optimized duplication
- Decommissioning Cloud Catalyst cloud storage
- NetBackup Cloud Catalyst workflow processes
- Disaster recovery for Cloud Catalyst
- MSDP cloud support
- About MSDP cloud support
- Creating a cloud storage unit
- Updating cloud credentials for a cloud LSU
- Updating encryption configurations for a cloud LSU
- Deleting a cloud LSU
- Backup data to cloud by using cloud LSU
- Duplicate data cloud by using cloud LSU
- Configuring AIR to use cloud LSU
- About backward compatibility support
- About the configuration items in cloud.json, contentrouter.cfg and spa.cfg
- About the tool updates for cloud support
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About restore from a backup in Microsoft Azure Archive
- Monitoring deduplication activity
- Monitoring the MSDP deduplication and compression rates
- Viewing MSDP job details
- About MSDP storage capacity and usage reporting
- About MSDP container files
- Viewing storage usage within MSDP container files
- Viewing MSDP disk reports
- About monitoring MSDP processes
- Reporting on Auto Image Replication jobs
- Managing deduplication
- Managing MSDP servers
- Viewing MSDP storage servers
- Determining the MSDP storage server state
- Viewing MSDP storage server attributes
- Setting MSDP storage server attributes
- Changing MSDP storage server properties
- Clearing MSDP storage server attributes
- About changing the MSDP storage server name or storage path
- Changing the MSDP storage server name or storage path
- Removing an MSDP load balancing server
- Deleting an MSDP storage server
- Deleting the MSDP storage server configuration
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Viewing Media Server Deduplication Pools
- Determining the Media Server Deduplication Pool state
- Changing Media Server Deduplication Pool state
- Viewing Media Server Deduplication Pool attributes
- Setting a Media Server Deduplication Pool attribute
- Changing a Media Server Deduplication Pool properties
- Clearing a Media Server Deduplication Pool attribute
- Determining the MSDP disk volume state
- Changing the MSDP disk volume state
- Inventorying a NetBackup disk pool
- Deleting a Media Server Deduplication Pool
- Deleting backup images
- About MSDP queue processing
- Processing the MSDP transaction queue manually
- About MSDP data integrity checking
- Configuring MSDP data integrity checking behavior
- About managing MSDP storage read performance
- About MSDP storage rebasing
- About the MSDP data removal process
- Resizing the MSDP storage partition
- How MSDP restores work
- Configuring MSDP restores directly to a client
- About restoring files at a remote site
- About restoring from a backup at a target master domain
- Specifying the restore server
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Configuring and using universal shares
- About Universal Shares
- Configuring and using an MSDP build-your-own (BYO) server for Universal Shares
- MSDP build-your-own (BYO) server prerequisites and hardware requirements to configure Universal Shares
- Mounting a Universal Share created from the NetBackup web UI
- Creating a Protection Point for a Universal Share
- Troubleshooting
- About unified logging
- About legacy logging
- NetBackup MSDP log files
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Verify that the MSDP server has sufficient memory
- MSDP backup or duplication job fails
- MSDP client deduplication fails
- MSDP volume state changes to DOWN when volume is unmounted
- MSDP errors, delayed response, hangs
- Cannot delete an MSDP disk pool
- MSDP media open error (83)
- MSDP media write error (84)
- MSDP no images successfully processed (191)
- MSDP storage full conditions
- Troubleshooting MSDP catalog backup
- Storage Platform Web Service (spws) does not start
- Disk volume API or command line option does not work
- Viewing MSDP disk errors and events
- MSDP event codes and messages
- Troubleshooting Cloud Catalyst issues
- Cloud Catalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- Status 191: No images were successfully processed
- Media write error (84) if due to a full local cache directory
- Troubleshooting restarting ESFS after the Cloud Catalyst storage server is down
- Restarting the vxesfsd process
- Problems restarting vxesfsd
- Unable to create CloudCatalyst with a media server that has version earlier to 8.2
- Cloud Catalyst troubleshooting tools
- Unable to obtain the administrator password to use an AWS EC2 instance that has a Windows OS
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
- Index
About Universal Shares
The Universal Share feature provides data ingest into an existing NetBackup deduplication pool (MSDP) or a NetBackup appliance using an NFS or a CIFS (SMB) share. Space efficiency is achieved by storing this data directly into an existing NetBackup-based media server deduplication pool.
The following information provides a brief description of the advantages for using Universal Shares:
As a NAS-based storage target
Unlike traditional NAS-based storage targets, Universal Shares offer all of the data protection and management capabilities that are provided by NetBackup.
As a DB dump location
Universal Shares offer a space saving (deduplicated) dump location, along with direct integration with NetBackup technologies including data retention, replication, and direct integration with cloud technologies.
Financial and time savings
Universal Shares eliminate the need to purchase and maintain third-party intermediary storage, which typically doubles the required I/O throughput since the data must be moved twice. Universal Shares also cut in half the time it takes to protect valuable application or DB data.
Protection Points
The Universal Share Protection Point offers a fast point in time copy of all data that exists in the share. This copy of the data can be retained like any other data that is protected within NetBackup. All advanced NetBackup data management facilities such as Auto Image Replication, Storage Lifecycle Policies, Optimized Duplication, cloud, and tape are all available with any data in the Universal Share.
Copy Data Management (CDM)
The Universal Share Protection Point also offers powerful CDM tools. A read/write copy of any Protection Point can be "provisioned" or made available through a NAS (CIFS/NFS) based share. A provisioned copy of any Protection Point can be used for common CPD activities, including instant recovery or access of data in the provisioned Protection Point. For example, a DB that has been previously dumped to the Universal Share can be run directly from the provisioned Protection Point.
Backup and restore without client software
Client software is not required for Universal Share backups or restores. Universal Shares work with any POSIX-compliant operating system that supports NFS or CIFS.
The Universal Share feature provides a network-attached storage (NAS) option for NetBackup appliances as well as the software-only deployment of NetBackup. Traditional NAS offerings store data in conventional, non-deduplicated disk locations. Data in a Universal Share is placed on highly redundant storage in a space efficient, deduplicated state. The deduplication technology that is used for this repository is the same MSDP location used by standard client-based backups.
Any data that is stored in a Universal Share is automatically placed in the MSDP, where it is deduplicated automatically. This data is then deduplicated against all other data that was previously ingested into the media server's MSDP location. Since a typical MSDP location stores data across a broad scope of data types, the Universal Share offers significant deduplication efficiency. The Protection Point feature lets you create a point in time copy of the data that exists in the specified Universal Share. Once a Protection Point is created, NetBackup automatically catalogs the data as a specific point in time copy of that data and manages it like any other data that is ingested into NetBackup. Since the Protection Point only catalogs the Universal Share data that already resides in the MSDP, no data movement occurs. Therefore, the process of creating a Protection Point can be extremely fast.
The Universal Share feature supports a wide array of clients and data types. NetBackup software is not required on the client where the share is mounted. Any operating system that uses a POSIX compliant file system and can mount a CIFS or an NFS network share can write data to a Universal Share. As the data comes in to the appliance, it is written directly into the Media Server Deduplication Pool (MSDP). No additional step or process of writing the data to a standard disk partition and then moving it to the deduplication pool is necessary.
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 same "Universal-Share" policy type that is used for UNIX/Linux systems. Once 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.
See Creating a Protection Point for a Universal Share.
Restoring data from a Protection Point is exactly the same as restoring data from a standard client backup. The standard Backup Archive and Restore interface is used. The client name that is referenced for the restore is the Universal Share name that was used when creating the Universal-Share policy type. Alternate client restores are fully supported. However, to restore to the system where the Universal Share was originally mounted, NetBackup Client software must be installed on that system. This is necessary since a NetBackup Client is not required to initially place data into the Universal Share.
NetBackup also supports a wide variety of APIs, including an API that can be used to provision or create an NFS share that is based on any Protection Point point in time copy. This point in time copy can be mounted on the originating system where the Universal Share was previously mounted. It can be provisioned on any other system that supports the mounting of network share. NetBackup Client software is not required on the system where the provisioned share is mounted.