Veritas Access Appliance 8.1 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
- 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
- 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
- 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
- Troubleshooting
- Index
Setting up secure communication between Veritas Data Deduplication on Access Appliance and the NetBackup primary server
You can setup secure communication between Veritas Data Deduplication on Access Appliance and the NetBackup primary server.
Prerequisites:
The
/usr/openv/netbackup/bp.conffile on the NetBackup primary server should have MSDP_SERVER entry for the MSDP server's FQDN.After adding the entry in the
bp.conf, run the /usr/openv/netbackup/bin/admincmd/bprdreq -rereadconfig command.
For clusters where DNS is not configured, the container's host name is created internally using the catalog file system name. For example, if the catalog file system name is catfs1, the container's host name is set to catfs1.vdd.com. For such setups, the MSDP_SERVER entry on the primary server's bp.conf file should point to the container's host name. To query the container's host name, use the support software show-OS-version command in the MSDP restricted shell. Or if you have access to the host running the container, you can log on to the host and run the docker exec <container_name> hostname command.
You can enable secure communication between the deduplication server and NetBackup primary server using the securecomm nbca enable command. The securecomm nbca enable command enables Host ID certificate based secure communication between the deduplication server and the NetBackup primary, which is also the Certificate Authority. The authorization token should be generated on the NetBackup primary. A reissue token is required if the certificate is to be regenerated. This command only supports secure communication using a NetBackup Certificate Authority.
dedupe> securecomm nbca enable primary_server token config_name
primary_server | FQDN of the NetBackup primary server which is also the KMS server. |
token | Token which is to be generated on the NetBackup primary. |
config_name | Name for the deduplication service. Note: This is an optional parameter when only one deduplication server is present in the cluster. It is mandatory if more than one deduplication servers are present. |