Veritas 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 performance
- 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
- 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
- Configuring deduplication to the cloud with NetBackup CloudCatalyst
- Using NetBackup CloudCatalyst to upload deduplicated data to the cloud
- Configuring a CloudCatalyst storage server for deduplication to the cloud
- 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
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting CloudCatalyst issues
- CloudCatalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- CloudCatalyst troubleshooting tools
- Appendix A. Migrating to MSDP storage
Configuring push or pull optimized duplication for CloudCatalyst
Optimized duplication requires the source storage server and the destination storage server to have at least one media server in common. For example, in a NetBackup CloudCatalyst environment that includes an MSDP media server (the source storage server) and one CloudCatalyst storage server (destination/target), either of these hosts could be the shared media server to perform optimized duplication.
The shared media server requires credentials for both the source storage server and the target storage server. (Credentials are granted in the Media Servers tab of the storage server properties for each storage server.) This point is important in determining whether your environment can support a push or a pull operation.
The media server which manages the duplication operation determines whether the operation is a push or a pull operation, as follows:
If the MSDP media server manages the duplication operation, it is push duplication. The CloudCatalyst storage server must allow access from the MSDP media server. (See Example push configuration: Source media server must be RHEL and NetBackup 8.1 or later.)
The CloudCatalyst can allow access only if the MSDP media server is RHEL (any version) and NetBackup 8.1 or later.
If the MSDP media server is not RHEL or is not at NetBackup 8.1 or later, a pull operation must be used instead.
If the CloudCatalyst media server manages the duplication operation, it is pull duplication. The MSDP media server must allow access from the CloudCatalyst media server. (See Example pull configuration: Source media storage server is not RHEL or is pre-8.1.)
The MSDP media server can be of any supported platform or NetBackup version.
See the considerations that are listed in Table: Considerations for using push or pull optimized duplication for CloudCatalyst.
Table: Considerations for using push or pull optimized duplication for CloudCatalyst
Type of optimized duplication
Advantages and disadvantages
Advantage: The NetBackup Disk Manager (bpdm) runs on the source media server, which prevents overloading the CloudCatalyst storage server during duplication jobs.
The overhead of optimized duplication does not compete with the ESFS resources. This is especially important where multiple MSDP storage servers fan-in to one CloudCatalyst storage server.
Disadvantage: Requires that the MSDP storage server be of a specific platform and NetBackup version.
Advantage: The MSDP media server can be of any supported platform or NetBackup version.
Disadvantage: The NetBackup tape manager (bptm) may run on the CloudCatalyst media server during backups. NetBackup may inadvertently use the CloudCatalyst storage server for load balancing during backups.
If there is no media server which has credentials to both storage servers, jobs fail.
If the common media server is the same host as the source MSDP storage server, it's a push operation. (Example push configuration: Source media server must be RHEL and NetBackup 8.1 or later)
If the common media server is the same host as the CloudCatalyst storage server, it's a pull operation. (Example pull configuration: Source media storage server is not RHEL or is pre-8.1)
If the media servers for both have credentials in common, the NetBackup Resource Broker (NBRB) chooses a media server at job time. Some jobs will be push operations and some will be pull operations.
In Figure: Push configuration, the source media server (the MSDP storage server) is configured for push duplication to the target. Note that the source is Red Hat Enterprise Linux and has NetBackup 8.1 installed.
Two configuration items allow for push duplication:
The target (the CloudCatalyst storage server) allows access from the source media server. The credential is granted in the storage server properties of each.
The storage unit settings on the source and the target specifically point to the source media server. (Enable Only use the following media servers and select the source media server.)
In Figure: Pull configuration, the target media server is configured for pull duplication. Note that the source is Windows and has NetBackup 8.0 installed.
Two configuration items allow for pull duplication:
The source (the MSDP storage server) allows access from the target media server. This is configured in the storage server properties of each.
The storage unit settings on the source and the target specifically point to the target media server. (Enable Only use the following media servers and select the target media server.)