DOC

StatusCode59

By Gloria Smith,2014-05-23 05:06
9 views 0
statuscode getstatuscode http status code status http status 500 status code 200 status code 791 http status 404 marital status status quo

    Status Code: 59

    Access to the client was not allowed

    The “access to the client was not allowed” error indicates that the Master or Media server is trying to access the client, but is not recognized by that client as a valid server.

When a backup starts, the client’s bpcd process performs a gethostbyaddr() on the incoming

    connection's remote IP address, which retrieves the server name. This returned name is then compared against the hostname(s) specified in the client’s Server list. If there is a match, the remote

    host is seen as a valid server. If the hostnames don't match, the host connecting to the client is not viewed as a valid NetBackup server and isn’t allowed to start the backup (Status 59). This document reviews the 2 cases in which this error can occur.

    Status 59

     Enable/view the following logs:

     Unix: /usr/openv/netbackup/logs/bpcd

     Windows: <install_path>\NetBackup\logs\bpcd

    Is the Server

    listed in the Client’s YESNO

    Server list?

    Name Resolution Server List IssuesIssuesGo to Section 1Go to Section 2

Table of Contents

    1 Server is not listed within the Client’s 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

Status Code: 59 Access to client was not allowed Page 2 of 6

    1 Server is not listed within the Client’s Server list

Verify that the NetBackup Master and Media Server’s hostname is in the Server list on the client.

    The Master and Media Servers can be the same host. Follow the appropriate platform-specific instructions to verify the Master or Media Server name(s) in the Client’s Server list.

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 client’s server list, followed by an entry for whatever Media Servers will

    connect to the client.

Example bp.conf excerpt:

SERVER = NBUMASTER

    SERVER = NBUMEDIA01

NetWare and OS/2 Clients

    The instructions for Netware and OS/2 are nearly the same. Add a SERVER entry in the Sys\openv\netback\bp.ini file as needed.

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.

    Status Code: 59 Access to client was not allowed Page 3 of 6

    2 Name Resolution

    Name resolution should be closely analyzed if the requesting server appears in the client’s 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 NetBackup’s 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.

    2.1 Multiple Nics

    If a NetBackup Master or Media Server has multiple interface cards, add the name of each network interface to the server list on the NetBackup client. Also, verify that the client can resolve the name and IP address for each functioning NIC on the Master/Media Server(s).

    Status Code: 59 Access to client was not allowed Page 4 of 6

2.2 Fully Qualified Domain Names

    In some cases, an IP is translated to the correct host, but the Fully Qualified Domain Name of the

    host. If a server connects to a client and the client translates the incoming ip to the Fully

    Qualified Domain Name (FQDN), then that FQDN host name must also be added to the server

    list.

    For example, suppose a machine called “media-bk” is trying to connect to a client for backup. On

    the backup request, the client translates the Server’s IP to “media-bk.mydomain.com”. In this

    instance, if only “media-bk” is added to the server list, the backup will likely fail with a status 59.

    Both “media-bk” and “media-bk.mydomain.com” should be added to the server list.

    Hostname comparisons can be seen from within the bpcd log.

     14:21:50.014 [3812.892] <2> bpcd main: offset to GMT 18000 14:21:50.014 [3812.892] <2> bpcd main: Got socket for input 336 14:21:50.024 [3812.892] <2> logconnections: BPCD ACCEPT FROM 10.66.16.116.2153 TO 10.66.14.22.13724 14:21:50.024 [3812.892] <2> bpcd main: setup_sockopts complete 14:21:50.064 [3812.892] <2> bpcd peer_hostname: Connection from host media-bk.mydomain.com (192.168.111.25) port 955 14:21:50.064 [3812.892] <2> bpcd valid_server: comparing media-bk and media-bk.mydomain.com 14:21:50.134 [3812.892] <4> bpcd valid_server: media-bk.mydomain.com is not a server 14:21:50.134 [3812.892] <16> bpcd valid_server: media-bk.mydomain.com is not a either 14:21:50.134 [3812.892] <2> bpcd main: output socket port number = 1 14:21:50.294 [3812.892] <2> bpcd main: Duplicated vnetd socket on stderr 14:21:50.294 [3812.892] <2> bpcd main: <---- NetBackup 6.0CA 0 ------------initiated 14:21:50.294 [3812.892] <2> bpcd exit_bpcd: exit status 46 ----------->exiting 14:21:50.294 [3812.892] <4> bpcd exit_bpcd: FTL - BPCD EXIT STATUS 46 14:21:50.294 [3812.892] <16> bpcd main: Server access denied

    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.Status Code: 59 Access to client was not allowed Page 5 of 6

3 Further Log Examination

If the Media Server name is in the client’s server list and name resolution appears to be correct,

    enable logging on the client for further error detail.

    Increase logging verbosity

    UNIX Clients

     Increase the debug or log level by adding VERBOSE on a separate line at the end of the

    /usr/openv/netbackup/bp.conf file on the client.

    Windows clients

    Set the debug level on the Troubleshooting tab of the NetBackup Client properties dialog. To

    Open this dialog, start the Backup, Archive, and Restore interface and click NetBackup Client

    Properties on the File menu.

    Retry the backup and examine the resulting logs to determine the cause of the failure.

4 Links

    Click here to Search for other documents on Status Code 59

Status Code: 59 Access to client was not allowed Page 6 of 6

Report this document

For any questions or suggestions please email
cust-service@docsford.com