Backups failed with 59, now with invalid error code

[Balaji_RT]

For a particular client prdchub , backups failed with 59, I had checked

1. all the entries of the master and media,

2. Tried deleting the bp.conf and adding it back.

Still got the below response:-

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

04/02/12 18:36:36 - Error bpbrm(pid=11810) bpcd on prdchub exited with status 59: access to the client was not allowed

04/02/12 18:36:35 - granted resource XXXXXX.NBU_CLIENT.MAXJOBS.prdchub

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

So wanted to check if the NB is responding, removed the bp.conf entries totally and ran the backup 

Now got this

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

04/04/12 03:28:48 - Error bpbrm(pid=10216) bpcd on prdchub exited with status 30062: invalid error number

04/04/12 03:28:48 - end writing

04/04/12 03:31:48 - Error bpbrm(pid=10216) cannot send mail because BPCD on prdchub exited with status 30062: invalid error number

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

The client version is 5.0 (SunOS ) and master is 7.1 (SunOS )

Will a upgrade fix the issue. ?

[revarooo · Accepted solution]

Firstly you mention:

The client version is 5.0 (SunOS ) and master is 7.1 (SunOS)

If it is the Master backing up the client that is not supported with the versions this far apart.

NetBackup 5.0 and 5.1 are no longer supported. Upgrade the client!!

If the issue still occurs:

On the client, ensure that in the bp.conf file the media server is added as

SERVER = <media_server_hostname>

Basically the client is denying the media server access to the bpcd port.

If you believe you had it added correctly, then create the bpcd log on the client

mkdir /usr/openv/netbackup/logs/bpcd/

add VERBOSE = 5 into the /usr/openv/netbackup/bp.conf file on the client

reproduce the issue. Check the bpcd log, you should see an incoming IP address. Resolve that IP on the client to it's hostname and check if that matches the correct SERVER entry in bp.conf :)

[Mark_Solutions]

The above is excellent advice to to find out exactly what is going on create the /usr/openv/netbackup/logs/bpcd directory on the client

When you try and connect (via host properties or by running a backup) the decisions it makes will be logged to this file and you will see why it will not allow it access

It may be a FQDN thing in which case you will just need to add an extra line to the bp.conf or sort out your hosts files

[Balaji_RT]

Will work on the same and keep you posted