Veritas NetBackup™ Replication Director Solutions Guide
- Additional configuration topics
- Creating a NetBackup storage server for snapshot replication
- Configuring disk pools for snapshot and replication
- About disk pools for snapshots and snapshot replication
- Using bpstsinfo to view the replication topology of a device
- Configuring storage units and storage unit groups for snapshots and snapshot replication
- Configuring storage lifecycle policies for snapshots and snapshot replication
- Operation types in a storage lifecycle policy
- Snapshot operation in an SLP
- Index From Snapshot operation in an SLP
- Snapshot operation in an SLP
- Retention types for storage lifecycle policy operations
- Configuring backup policies for snapshots and snapshot replication
- About NDMP support for Replication Director
- Restoring from a snapshot
- About restores from array-based snapshots of virtual machines
- OpsCenter reporting
- Using NetApp disk arrays with Replication Director
- Supported NetApp topologies
- Using NetApp Data ONTAP 7-mode with Replication Director
- About using NetApp SAN-connected storage with Replication Director
- Using NetApp Clustered Data ONTAP with Replication Director
- Using Oracle with Replication Director
- Using Virtual Machines with Replication Director
How to configure a multi-NIC environment
A NetBackup client can have multiple host names that correspond to multiple Network Interface Cards (NICs). To access the snapshots using a particular NIC, you must use the host name that corresponds to that NIC as a client name in the NetBackup backup policy.
Ensure that the route to the filer follows the same interface that is defined as the client name in backup policies.
If the NIC information is not configured correctly, backup and restore jobs may fail.
Consider an HP-UX 11.31 host with the host name hp_nas.abc.xyz.com. This host is configured as a client in a backup policy. This backup policy is intended to support the NAS volumes which are mounted on the host. The host has multiple NAS volumes mounted which are created on the filer with IP address 10.80.155.147.
Host hp_nas.abc.xyz.com has two NICs configured, as shown in Table: NICs on example host.
Table: NICs on example host
Mapped to NAS volume
The following is an example of the routing table that is defined for host hp_nas.abc.xyz.com:
netstat -nr Routing tables Destination Gateway Flags Refs Interface Pmtu 127.0.0.1 127.0.0.1 UH 0 lo0 32808 10.80.139.210 10.80.139.210 UH 0 lan1 32808 10.80.139.208 10.80.139.208 UH 0 lan0 32808 10.80.139.0 10.80.139.210 U 2 lan1 1500 10.80.136.0 10.80.139.208 U 2 lan0 1500 127.0.0.0 127.0.0.1 U 0 lo0 32808 default 10.80.136.1 UG 0 lan0 1500
Since the IP/subnet address of the filer does not fall under any routing entry defined, network communication from the host happens using the default routing entry.
As previously mentioned, the default route entry has the same interface (lan0) as that of the entry corresponding to the client name hp_nas.abc.xyz.com (lan0).
Similarly, if there is an entry defined in the routing table explicitly for the subnet of the storage system's IP address, ensure that the same interface similarity exists.