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:

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