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
- About MSDP Encryption using KMS 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
- 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
- Troubleshooting
- 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 a separate network path for MSDP duplication and replication
You can use a different network for MSDP duplication and replication traffic rather than the one you use for MSDP backups. Both the duplication and the replication data traffic and the control traffic travel over the separate network.
This procedure describes how to use the storage servers hosts
files to route the traffic onto the separate network.
The following are the prerequisites:
Both the source and the destination storage servers must have a network interface card that is dedicated to the other network.
The separate network must be operational and using the dedicated network interface cards on the source and the destination storage servers.
On UNIX MSDP storage servers, ensure that the Name Service Switch first checks the local
hosts
file for before querying the Domain Name System (DNS). See the operating system documentation for information about the Name Service Switch.
To configure a separate network path for MSDP duplication and replication
- On the source storage server, add the destination storage servers's dedicated network interface to the operating system
hosts
file. If TargetStorageServer is the name of the destination host on the network that is dedicated for duplication, the following is an example of thehosts
entry in IPv4 notation:10.10.10.1 TargetStorageServer.example.com TargetStorageServer
Veritas recommends that you always use the fully qualified domain name when you specify hosts.
- On the destination storage server, add the source storage servers's dedicated network interface to the operating system
hosts
file. If SourceStorageServer is the name of the source host on the network that is dedicated for duplication, the following is an example of thehosts
entry in IPv4 notation:10.80.25.66 SourceStorageServer.example.com SourceStorageServer
Veritas recommends that you always use the fully qualified domain name when specifying hosts.
- To force the changes to take effect immediately, flush the DNS cache. See the operating system documentation for how to flush the DNS cache.
- From each host, use the ping command to verify that each host resolves the name of the other host.
SourceStorageServer.example.com> ping TargetStorageServer.example.com TargetStorageServer.example.com> ping SourceStorageServer.example.com
If the ping command returns positive results, the hosts are configured for duplication and replication over the separate network.
- When you configure the target storage server, ensure that you select the host name that represents the alternate network path.