Status Code: 59: Access To The Client Was Not Allowed
Status Code: 59: Access To The Client Was Not Allowed
Status 59
Enable/view the following logs : Unix: /usr/openv /netbackup /logs/bpcd Windows: <install_path>\NetBackup\logs\bpcd
NO
YES
Table of Contents
1 Server is not listed within the Clients Server list.......................................................................................3 2 Name Resolution......................................................................................................................................4 2.1 Multiple Nics.......................................................................................................................................4 2.2 Fully Qualified Domain Names .................................................................................................................................................................5 3 Further Log Examination.........................................................................................................................6 4 Links.......................................................................................................................................................6
Page 2 of 6
UNIX Clients
Edit /usr/openv/netbackup/bp.conf file and ensure that there is a SERVER= line for any Master and Media Servers that connect to the client. The Master Server name should be the first SERVER entry in the clients server list, followed by an entry for whatever Media Servers will connect to the client. Example bp.conf excerpt: SERVER = NBUMASTER SERVER = NBUMEDIA01
Windows Clients
Add server entries on Windows clients by doing the following: 1. Open the Backup, Archive, and Restore interface. 2. Select File > Specify NetBackup Machines and Policy Type. 3. Select the Servers tab. 4. Verify that the Master/Media Server(s) are added to this server list, and that the Master Server is set as current. 5. Click OK after adding any needed servers and exit Backup, Archive and Restore. Note: If server entries are modified on a NetBackup Master Server, it is necessary to stop and restart NetBackup services/processes. Services/processes do not need to be restarted on a Media Server or Client after updating the server list.
Page 3 of 6
2 Name Resolution
Name resolution should be closely analyzed if the requesting server appears in the clients server list, but the Status 59 is still seen. In this case, the hostname comparisons made on the client between the server list and resolved host name are not matching.
Using bpclntcmd
bpclntcmd is a useful utility that can be run from any Client. It will help determine if name resolution is working properly from NetBackups perspective. Windows command location: %install_path%\VERITAS\NetBackup\bin\ UNIX command location: /usr/openv/netbackup/bin Switches and variations:
bpclntcmd -pn bpclntcmd -self bpclntcmd -hn <hostname_of_masterserver> bpclntcmd -hn <hostname_of_mediaserver> bpclntcmd -hn <hostname_of_client> bpclntcmd -ip <ip_of_masterserver> bpclntcmd -ip <ip_of_mediaserver> bpclntcmd -ip <ip_of_client>
The goal of these commands is to make sure the hostname is consistently seen the same way after each command. Below is an explanation of what each switch does: -pn - The client process on the host connects to the Master Server and asks the question "Who am I?". The second line of the output is the result. This is how the client process on the host is being seen by the Master Server. -self - Checks how this host can be resolved. Ideally, there should be only 1 unique hostname and 1 unique IP address. -hn - Checks the given hostname and returns an IP. -ip - Checks the given IP and returns a hostname. If there is any inconsistency in the results of these commands, correct the hostname to IP resolution by either editing the local hosts table or by updating the DNS database.
Page 4 of 6
In the above situation, the Client was resolving the fully qualified name of the Media Server. This fully qualified hostname must be added to the server list for the backup to work.
Page 5 of 6
4 Links
Click here to Search for other documents on Status Code 59
Page 6 of 6