Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Deduplication Guide
  3. Configuring deduplication
  4. Configuring a separate network path for MSDP duplication and replication
Veritas NetBackup™ Deduplication Guide

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

  1. 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 the hosts 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.

  2. 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 the hosts 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.

  3. To force the changes to take effect immediately, flush the DNS cache. See the operating system documentation for how to flush the DNS cache.
  4. 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.

  5. When you configure the target storage server, ensure that you select the host name that represents the alternate network path.

More Information

About a separate network path for MSDP duplication and replication

Feedback

Was this page helpful?
Previous

About a separate network path for MSDP duplication and replication

Next

About MSDP optimized duplication within the same domain

Feedback

Was this page helpful?