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
Managing an isolated recovery environment on a storage server
Once you have configured an isolated recovery environment (IRE) on a storage server, you can manage it from the MSDP restricted shell with a local user with administrator role (same user that was used for Access Appliance CLISH login). Use the following commands.
To view the SLP windows from the primary server to the server:
setting ire-network-control show-slp-windows production_primary_server=<production domain> production_primary_server_username=<production username> ire_primary_server=<IRE domain> ire_primary_server_username=<IRE username>
Where:
<production domain> is the fully qualified domain name (FQDN) of the primary server in your production environment.
<production username> is the username of a NetBackup primary user with permission to list SLPs and SLP windows in the production environment. For Windows users, enter the username in the format <domain name>\<username>. For other users, enter the username only.
<IRE domain> is the FQDN of the primary server in the IRE. Use the same hostname that you used for the target primary server when you configured the SLPs in the production environment.
<IRE username> is the username of a IRE NetBackup primary user with permission to list SLPs and storage units in the IRE. For Windows users, enter the username in the format <domain name>\<username>. For other users, enter the username only.
For example:
production_primary_server=examplePrimary.domain.com production_primary_server_username=example_user ire_primary_server=exampleIREPrimary.domain.com ire_primary_server_username=example_user1
Note:
The SLP replication window on the production domain must be configured to be open at the same time as the IRE schedule.
To list the MSDP reverse connections:
setting ire-network-control list-reverse-connections
To add an MSDP reverse connection:
setting ire-network-control add-reverse-connection remote_storage_server=<production MSDP server> [remote_primary_server=<production primary server>] [local_storage_server=<IRE network interface>]
Where:
<production MSDP server> is the FQDN of the MSDP server in your production environment.
[remote_primary_server=<production primary server>] is an optional parameter for the FQDN of the primary server in your production environment. This parameter is required if the IRE domain uses an alternative name to access the production primary server. This scenario usually occurs if the production primary server runs on multiple networks with multiple hostnames.
[local_storage_server=<IRE network interface>] is an optional parameter for the hostname of the network interface to use for image replication on the IRE storage server. This parameter is required if the network interface for replication is different than the IRE storage server name.
To verify that a reverse connection works:
setting ire-network-control validate-reverse-connection remote_storage_server=<production MSDP server> [remote_primary_server=<production primary server>] [local_storage_server=<IRE network interface>]
To remove an MSDP reverse connection:
setting ire-network-control remove-reverse-connection remote_storage_server=<production MSDP server>
To view the allowed IP addresses and subnets:
setting ire-network-control show-allows
To add IP addresses and subnets to the allowed list:
setting ire-network-control allow-subnets subnets=<CIDR subnets or IP addresses>
Where <CIDR subnets or IP addresses> is a comma-separated list of the allowed IP addresses and subnets, in CIDR notation.
For example:
setting ire-network-control allow-subnets subnets=10.80.120.208,10.84.48.0/20
Note:
The IRE primary server, the IRE media servers, and the DNS server for the IRE must be included in the allowed list. If all of these servers are in the same subnet, only the subnet is required to be in the allowed list.
To remove the IP addresses and subnets from the allowed list:
setting ire-network-control allow-subnets subnets=,
To view the daily air gap schedule:
setting ire-network-control show-schedule
To change the air gap schedule:
setting ire-network-control set-schedule start_time=<time> duration=<duration>
For example:
setting ire-network-control set-schedule start_time=10:00:00 duration=03:00:00
To stop the air gap schedule:
setting ire-network-control delete-schedule
To view the current network status and check whether the external network is open or closed:
setting ire-network-control external-network-status
To manually open the external network:
setting ire-network-control external-network-open
To manually close the external network and resume the air gap schedule:
setting ire-network-control resume-schedule
Note:
The commands may take a few minutes to take effect.