Separating the duplication and replication network

You can separate the duplication and replication network by performing an AIR from the source Access Appliance MSDP server to the target Access Appliance MSDP server. With the default configuration, the AIR traffic follows the same network route as the duplication traffic (eth4). You can separate both the traffic by running the following steps on the Access Appliance cluster.

Consider the following scenario:

The deduplication server is configured on source Access Appliance cluster (NBU1) with primary IP as 10.10.10.11 and FQDN as primary1.access.com.
The deduplication server is configured on the target cluster (NBU2) with primary IP as 10.10.10.12 and FQDN as primary2.access.com.
The primary IPs are online on device eth4.
The storage server is configured with primary1.access.com on (NBU1) and primary2.access.com on (NBU1).
10.10.10.13 and 10.10.10.14 are unused IPs with FQDNs as vip1.access.com and vip2.access.com respectively.

To separate the duplication and replication network

Log on to source Access Appliance cluster with management console IP.
On the source cluster, add a virtual IP. Select a device other than the one already used for deduplication of the primary IP.
```
network> ip addr add <virtual_ip> <netmask> [device] [nodename] [fqdns]
```
Example:
```
network> ip addr add 10.10.10.13 255.255.240.0 eth5 
```
Repeat step 2 with the other IP on the target Access Appliance cluster.
Example:
```
network> ip addr add 10.10.10.14 255.255.255.0 eth5 
```

On the source cluster, add a route to the new target virtual IP.

network ip route add all <target_vip> 255.255.255.255 via 
<source_gateway> dev <device_name> scope=global

Where

target_vip	Newly added virtual IP on target Access Appliance cluster.
source_gateway	Gateway IP of the source cluster
device_name	Device on which the newly added virtual IP is present on the source cluster.

Example:

network> ip route add all 10.10.10.14 255.255.255.255 via 10.10.10.1 
dev eth5

Add the virtual IP to Access Appliance MSDP server on both the source and target cluster with the respectively added virtual IPs.
```
dedupe> addip <virtual_ip> 
```
Example:
On the source cluster:
```
dedupe> addip 10.10.10.13 
```
On target: cluster:
```
dedupe> addip 10.10.10.14 
```
Add the mapping of the target virtual IP to the target deduplication primary FQDN on the source deduplication instance.
If you have an instance of WORM-enabled Veritas Data Deduplication, run the following command on the source cluster.
```
dedupe> fqdn add <target_vip> <target_primary_fqdn> 
```
Where
target_vip
Newly added virtual IP on the target Access Appliance cluster.
target_primary_fqdn
FQDN with which the storage server has been added to the target NetBackup primary server.
Example:
```
dedupe> fqdn add 10.10.10.14 primary2.access.com 
```
If the instance of Veritas Data Deduplication is not WORM-enabled, add the IP/FQDN to the /etc/hosts file of each node.
If you want to replicate from the target cluster to the source cluster, you can perform the same steps on the target cluster with the source cluster IP.
If you have an instance of WORM-enabled Veritas Data Deduplication, run the following command on the target cluster.
```
dedupe> fqdn add 10.10.10.13 primary1.access.com 
```
If the instance of Veritas Data Deduplication is not WORM-enabled, add the IP/FQDN to the /etc/hosts file of each node.

Separating the duplication and replication network

Feedback

Feedback

target_vip	Newly added virtual IP on the target Access Appliance cluster.
target_primary_fqdn	FQDN with which the storage server has been added to the target NetBackup primary server.