NetBackup status code: 59
Message: access to the client was not allowed
Explanation: The master or the media server tries to access the client, but the client does not recognize the server as a valid server.
For the Enterprise Vault Agent: The names of all of the media servers among the Enterprise Vault servers are not specified in the client configuration.
Recommended Action: Do the following, as appropriate:
If the server is a valid server, verify that it is in the server list on the client. If necessary add it as follows:
On Windows clients: Add the server on the drop-down in the Specify NetBackup Machines and Policy Type dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client. Then click on the File menu.
On UNIX clients: Add a SERVER entry in the
bp.conffile.
If you change the server list on a UNIX or Linux master server, do the following for the changes to take effect: Stop and then restart the NetBackup Request Daemon (bprd) and NetBackup Database Manager Daemon (bpdbm). On Windows, stop and restart the NetBackup Request Manager and NetBackup Database Manager services.
On Windows clients, enable bpinetd debug logging as follows:
Create a bpinetd debug log directory on the client.
Increase the debug or log level.
See "Changing the logging level on Windows clients" in the NetBackup Logging Reference Guide.
Retry the backup and examine the resulting logs to determine the cause of the failure.
On all clients, enable bpcd debug logging as follows:
Create a bpcd debug log directory on the client.
On a UNIX or Linux client, add the VERBOSE option to the
/usr/openv/netbackup/bp.conffile.On PC clients, increase the debug or log level as explained in the debug log topics in Chapter 3.
Retry the backup and examine the resulting logs to determine the cause of the failure.
Check the bpcd debug log to determine the server's peer name and what comparisons are made.
The bpcd process compares NetBackup server list entries to the peer name of the server that tries the connection. It rejects the connection if the names are different. If necessary, change the server list entry on the client to match the peer name.
On Windows clients, check the following:
Verify that NetBackup for Windows software was installed under a Windows administrator account.
If NetBackup is under another type of account, reinstall it under an administrator account. The installation completes successfully under a non-administrator account except for the following: The NetBackup Client service is not added to Windows and the NetBackup server cannot access the client.
Verify that the Windows TCP/IP service specifies the domain server that resolves names for the subnet that contains the NetBackup servers.
UNIX, Linux, and Windows clients are frequently not on the same subnet and use different domain servers. When this condition exists, NetBackup servers and Windows clients may be able to ping one another, but the server still cannot access the Windows client.
The preceding items may not resolve this problem.
See "Resolving network communication problems" in the NetBackup Troubleshooting Guide.
If NetBackup use multiple network interfaces with media servers, make sure that the interface names appear in the client's
/usr/openv/netbackup/bp.conffile.For the Enterprise Vault Agent: See the Troubleshooting section of the NetBackup for Enterprise Vault Agent Administrator's Guide.
Be sure that all name resolution services (primary, load-balancing, and secondary) are properly configured for consistent forward and reverse name resolution of NetBackup hosts.
More information is available in the following technical article:
Click here to view technical notes and other information on the Veritas Technical Support website about this status code.