access to the client was not allowed(59)

Dear All,

I newly configured the NAS server into my backup server, and am able to take a backup for 3 servers without any issues... for one NAS server its giving me an error ""access to the client was not allowed(59)""..... Host entries are pefectly added in the client.... can any1 help to resolve this issue...

Details : 9/24/2012 4:57:51 PM - requesting resource PMCRB-MED01-TLD-4-ESL-1 9/24/2012 4:57:51 PM - requesting resource pmcrabkupmst02.NBU_CLIENT.MAXJOBS.PMCRBXFS04B 9/24/2012 4:57:51 PM - requesting resource pmcrabkupmst02.NBU_POLICY.MAXJOBS.MCRB-NAS-Ibrixcfg-Wkly 9/24/2012 4:57:51 PM - granted resource pmcrabkupmst02.NBU_CLIENT.MAXJOBS.PMCRBXFS04B 9/24/2012 4:57:51 PM - granted resource pmcrabkupmst02.NBU_POLICY.MAXJOBS.MCRB-NAS-Ibrixcfg-Wkly 9/24/2012 4:57:51 PM - granted resource HYB819 9/24/2012 4:57:51 PM - granted resource Drive084 9/24/2012 4:57:51 PM - granted resource PMCRB-MED01-TLD-4-ESL-1 9/24/2012 4:57:51 PM - estimated 0 Kbytes needed 9/24/2012 4:57:53 PM - started process bpbrm (1548) 9/24/2012 4:57:54 PM - Error bpbrm(pid=1548) bpcd on PMCRBXFS04B exited with status 59: access to the client was not allowed 9/24/2012 4:57:54 PM - end writing access to the client was not allowed(59)

Regards,

Karthik.

Marianne
13 years ago
This is not a NDMP backup. Policy type of Standard means that this is normal filesystem backup of local /usr/local/ibrix folder on all of these clients.

Please confirm that there is /etc/hosts entry for PMCRB-MED01 on client PMCRBXFS04B.

Please also confirm that there is a SERVER entry in /usr/openv/netbackup/bp.conf for PMCRB-MED01 on client PMCRBXFS04B.

Create bpcd log folder under /usr/openv/netbackup/logs on the client.

If backup still fails after checking all of the above, please copy log file in bpcd folder to bpcd.txt and post as File attachment.

6 Replies

sksujeet
Level 6
13 years ago
The master server entries are in lower case but PMCRBXFS04B is in upper case. As a first step please make it lower case or add it in the host entries.

Are you able to resolve the hostname and able to ping it.?
Will_Restore
Level 6
13 years ago
multiple NICs?

Solution

Ensure that the client host can resolve the source IP address from which the master and media servers will connect and has a SERVER entry for each of the returned hostnames. E.g.

Note that the best solution may not be adding/changing IP address lookup or adding server entries on the client host. Other solutions my be more appropriate:

Are the servers using the correct hostname for the client? If no correct the client name in the policy.

Are the server hosts resolving the hostname of the client to the correct IP address for the remote network interface to reach on the client host? If not correct name resolution on the server hosts.

Are the server hosts connecting outbound from the correct local network interface? If not correct the binding order or routing table on the server hosts.

Do the server hosts have an [inappropriate] REQUIRED_INTERFACE setting that resolves to an IP address that should not be used for connection to the client? Either remove or correct the setting or the IP address to which that hostname resolves

Article URL http://www.symantec.com/docs/TECH195139
Marianne
Level 6
13 years ago
How did you configure NAS backup?

NDMP or network share?

Please show us policy config:

bppllist <policy-name> -U

Where does PMCRBXFS04B fit in the picture?
NAS server? (NDMP backup)
Media server or client? (network backup)

It seems that PMCRBXFS04B is missing a SERVER entry for media server PMCRB-MED01.
want2learn
Level 3
13 years ago
Dear Sazz,

I dont think case sentitive will be a problem, because totally i configured 4 NAS server in that only one is giving problem. Also am able to ping. Anyhw i changed to lower case.

Dear Marianne,

NAS share backup we are taking through NDMP only, but here am trying to take NAS server configuration file in the server (LINUX OS). Also entries are added in media and master server, all the 3 host are working and this is the only host giving this error.

------------------------------------------------------------

Policy Name:       MCRB-NAS-Ibrixcfg-Wkly

Policy Type:         Standard
Active:              yes
Effective date:      09/18/2012 12:53:11
Client Compress:     no
Follow NFS Mounts:   no
Cross Mount Points: no
Collect TIR info:    no
Block Incremental:   no
Mult. Data Streams: no
Client Encrypt:      no
Checkpoint:          no
Policy Priority:     0
Max Jobs/Policy:     Unlimited
Disaster Recovery:   0
Collect BMR info:    no
Residence:           PMCRB-MED01-TLD-4-ESL-1
Volume Pool:         ESL-B-Lin-FS-Dly-Wly
Server Group:        *ANY*
Keyword:             (none specified)
Data Classification:       -
Residence is Storage Lifecycle Policy:    no

Granular Restore Info: no
Ignore Client Direct: no
HW/OS/Client: Linux         RedHat2.6     PMCRBXFS01B
                 Linux         RedHat2.6     PMCRBXFS02B
                 Linux         RedHat2.6     PMCRBXFS03B
                 Linux         RedHat2.6     PMCRBXFS04B

Include: /usr/local/ibrix

Schedule:          Fullbackup
    Type:            Full Backup
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 3 (1 month)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Calendar sched: Enabled
      Wednesday, Week 1
      Wednesday, Week 2
      Wednesday, Week 3
      Wednesday, Week 4
      Wednesday, Week 5
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Wednesday 20:00:00 --> Wednesday 21:00:00

Regards,

Karthik.
Marianne
Level 6
13 years ago
This is not a NDMP backup. Policy type of Standard means that this is normal filesystem backup of local /usr/local/ibrix folder on all of these clients.

Please confirm that there is /etc/hosts entry for PMCRB-MED01 on client PMCRBXFS04B.

Please also confirm that there is a SERVER entry in /usr/openv/netbackup/bp.conf for PMCRB-MED01 on client PMCRBXFS04B.

Create bpcd log folder under /usr/openv/netbackup/logs on the client.

If backup still fails after checking all of the above, please copy log file in bpcd folder to bpcd.txt and post as File attachment.
want2learn
Level 3
13 years ago
Hello Marianne,

Thank you so much for you help, i added the server entries in bp.conf and now am able to take a backup.

Dear Friends,

Thanks to everyone.

Regards,

Karthikeyan E

Forum Discussion

access to the client was not allowed(59)

6 Replies

Solution

Related Content

Status Code 59 - Access to the Client was not Allowed

Status 59 “access to the client was not allowed”

access to the client was not allowed(59)

Netbackup RAC Restore - error 59 access to client not allowed

Restore job has error. Status 59: access to the client was not allowed