NetBackup job fails because of apparent network error
A job may fail with network error 23, 25, 59, or perhaps other network error.
The host certificate of a NetBackup client or the media server that backs it up may be revoked. Also, the CRL on the client or the media server may be out-of-date, missing, or corrupt. Therefore, the client or the media server cannot determine that a host certificate is revoked. The job runs but communication fails and appears as a network error.
Determine if the client or the media server certificate was revoked.
Optionally, verify the cause by doing one of the following:
Log onto the revoked host and examine the vnetd proxy log file. Look for the message strings that contain the following:
PEER_HOST_PROTOCOL_ERROR
certificate revocation list
CRL and missing or corrupted
Use the NetBackup bptestbpcd command to see if a host certificate is revoked.
Resolve the issue:
If the CRL on a host is missing or corrupt, refresh the CRL on that host.
How to refresh a host's CRL is documented in the NetBackup Security and Encryption Guide.
If an external CA-signed certificate is used, refer to the external certificate section.
See Troubleshooting issues with external CA-signed certificate revocation.
If NetBackup CA-signed host certificate is revoked, resolve the security issue and then reissue the certificate.
How to reissue a certificate is documented in the NetBackup Security and Encryption Guide.