Backups fail with a status code 59: "access to the client was not allowed."

Problem

Backups fail with a status code 59: "access to the client was not allowed."

Error Message

status code 59: access to client was not allowed

Solution

NOTE: The contents of this article are not relevant in an environment where the VERITAS NetBackup master or media server has the "REQUIRED_INTERFACE" directive specified in the bp.conf file.

A status code of 59 commonly occurs when the client does not have the NetBackup master or media server properly defined in the /usr/openv/netbackup/bp.conf file. There are a number of well-documented and effective ways to troubleshoot this problem, (e.g., creating a bpcd log on the client and then re-attempting the backup) but the UNIX last command is a quick and simple way to clearly establish the cause of this problem.

Connecting to the NetBackup client from the NetBackup server (using any of the standard terminal connection commands: telnet, ssh, rlogin, etc) and immediately running the last command displays the host name that must match a SERVER entry in the client's bp.conf file in order to avoid the status 59 failure.

For example, consider a scenario in which a status 59 failure is occurring when attempting a backup of a UNIX NetBackup client named "NBUClient."  The NetBackup media server (or the NetBackup master server, in a single-server or NetBackup BusinessServer environment) involved in this backup is named "NBUServer".

The captured terminal output below demonstrates the use of the UNIX last command to reveal that the NBUClient does not have the necessary entry in the bp.conf file:

 
anyuser@NBUServer% uname -n
 
NBUServer
 
anyuser@NBUServer%
 
anyuser@NBUServer% telnet NBUClient
 
Trying 10.1.1.10...
 
Connected to NBUClient.
 
Escape character is '^]'.
 

 
SunOS 5.8
 

 
login: anyuser
 
Password: *******
 
Last login: Thu Feb 14 09:45:57 from 10.1.1.10
 
Sun Microsystems Inc.   SunOS 5.8       Generic February 2000
 
anyuser@NBUClient% last -1
 
anyuser   pts/7        BUServer Thu Feb 21 12:33   still logged in
 
anyuser@NBUClient%
 
anyuser@NBUClient%  cat /usr/openv/netbackup/bp.conf
 
SERVER = NBUMaster
 
SERVER = NBUServer
 
CLIENT_NAME = NBUClient
 

The output above leads to the conclusion that the back ups of NBUClient are failing because NBUClient detects the incoming backup request coming from the hostname "BUServer" and that particular host name is not listed in NBUClient's bp.conf file as a valid server.  

The resolution to the above sample problem is now clear. One of the following actions will resolve the status 59 failure:

1. If this is not a name resolution problem, add a "SERVER = BUServer" entry to bp.conf on NBUClient

OR

2. If this is a name resolution problem, correct the name resolution configuration (/etc/hosts file, DNS or NIS maps) on NBUClient so that the above scenario would show NBUServer being returned in the output of the last command

 3. In addition If the NetBackup Client being backed up is virtual (vmware).  The policy must be set as "Vmware policy type" if NetBackup is accessing the vsphere server to backup the server.  The other option is the NetBackup client needs to be installed on the virtual server being backed up.

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)