Ensure that the Veritas Product Authentication Service is installed and configured.

For complete installation instructions, see theNetBackup Security and Encryption Guide.

Check that both parties have a valid certificate. Examine the expiry date that is listed from a bpnbat -WhoAmI. For example:

bpnbat -WhoAmI
Name: JDOG
Domain: MYCOMPANY
Issued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx
Expiry Date: Sep 19 12:51:55 2009 GMT
Authentication method: Microsoft Windows

Operation completed successfully.

Shows an expiry date of September 19th, 2009. After 12:51:55 GMT this credential is no longer valid and a new credential is required.

If you run from the NetBackup Administration Console, close and reopen the console. The console automatically obtains a credential for the currently logged in identity, if possible. By default, these certificates are valid for 24 hours. The following is an example of how to extend the credential beyond 24 hours to 30 days (2592000 seconds):

Windows: <install path>\veritas\netbackup\sec\at\bin\vssat setexpiryintervals -p <plugin_name> -t <user> -e 2592000

UNIX: usr/openv/netbackup/sec/at/bin/vssat setexpiryintervals -p <plugin_name> -t <user> -e 2592000

Ensure that the certificates for both sides use the same broker or are children of the same root broker and that trusts are established between them.

See the NetBackup Security and Encryption Guide for more information on broker hierarchies and how to establish trust relationships between brokers.

Ensure that connectivity between the physical systems in question is possible. If general sockets cannot connect between the computers (such as ping and telnet), issues within the network unrelated to NetBackup can cause this problem.

Ensure that the system has sufficient swap space and the following directories are not full: