Veritas Access Appliance 8.2 Solutions Guide for NetBackup
- Access Appliance integration with NetBackup
- System requirements
- Configuring Veritas Data Deduplication with Access Appliance
- About Veritas Data Deduplication
- Benefits of using Veritas Data Deduplication with Access Appliance
- Supported features with different versions of Veritas Data Deduplication
- Configuring Veritas Data Deduplication without WORM
- Configuring Veritas Data Deduplication with WORM
- Managing Veritas Data Deduplication using the Access CLISH
- Managing Veritas Data Deduplication using GUI
- Viewing information about Veritas Data Deduplication
- Starting or stopping the Veritas Data Deduplication service
- Increasing storage for Veritas Data Deduplication
- Unconfiguring Veritas Data Deduplication
- Adding secondary IP for Veritas Data Deduplication
- Deleting secondary IP for Veritas Data Deduplication
- Changing the primary IP for Veritas Data Deduplication
- Upgrade the deduplication version for Veritas Data Deduplication
- Setting affinity node for Veritas Data Deduplication
- Accessing Access Appliance storage shell for management tasks
- Support for multiple domains across networks for Veritas Data Deduplication
- Veritas Data Deduplication storage layout
- Configuring a Veritas Data Deduplication storage unit on NetBackup
- Configuring global deduplication using the Veritas Data Deduplication storage server across the domain
- Enabling Veritas Data Deduplication encryption
- Support for bandwidth throttling during duplication
- Setting up secure communication between Veritas Data Deduplication on Access Appliance and the NetBackup primary server
- About MSDP encryption using NetBackup KMS service
- Support for NetBackup Auto Image Replication
- Setting up Auto Image Replication (AIR) between two Access Appliances which have secure communication enabled
- NetBackup Dedupe Direct for Oracle
- Configuring MSDP-C with Access Appliance
- Migrating the NetBackup images from existing storage to Veritas Access storage
- Configuring Access Appliance with the NetBackup client
- Configuring Access Appliance for NetBackup client
- Installing the NetBackup client add-on packages
- Prerequisites for configuring the NetBackup client
- Configuring the NetBackup client
- Adding an optional media server
- Adding multiple primary servers
- Adding file systems to the backup configuration
- Removing file systems from backup configuration
- Changing the virtual IP address used by the NetBackup client
- Upgrade the NetBackup client
- Unconfiguring the NetBackup client
- Enabling Veritas Data Deduplication catalog backup with NetBackup client
- Disabling Veritas Data Deduplication catalog backup from NetBackup client
- Displaying the status of NetBackup services
- Configuring backup operations using NetBackup or other third-party backup applications
- Restoring filesystems backed up with NetBackup client
- Configuring isolated recovery environment (IRE)
- Requirements
- Configuring the network isolation
- Configuring an isolated recovery environment using the command line
- Configuring an isolated recovery environment on a storage server
- Managing an isolated recovery environment on a storage server
- Configuring data transmission between a production environment and an IRE storage server
- Troubleshooting
- Index
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> [config_name]
Example:
On the source cluster:
dedupe> addip 10.10.10.13 source-engine
On target: cluster:
dedupe> addip 10.10.10.14 target-engine
- Add the mapping of the target virtual IP to the target deduplication primary FQDN on the source deduplication instance.
On the source cluster:
dedupe> fqdn add <target_vip> <target_primary_fqdn> [config_name]
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.
config_name
Source deduplication instance's configuration name.
Example:
dedupe> fqdn add 10.10.10.14 primary2.access.com source-engine
- 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.
On the target cluster:
dedupe> fqdn add 10.10.10.13 primary1.access.com target-engine