Netbackup job failing but not in policy

[fordpony65]

Hello!

I have a bit of a weird situation, I have a couple of netbackup jobs that are failing but they are not in the policy.

Any thoughts?

Thanks!

Fred

[Mark_Solutions]

Please tell us more - a lot more ...

NBU Version

O/S of Master, Media, Clients

Type of backup

Status codes

Detailed status of the job.

Logs

etc. etc..

As much as you can please

[fordpony65]

The NBU Version is 6.5,

OS of Master/Meadia is Solaris,  Client is Linux

Standard Backup

I am getting code 48 and 58's

02/29/2012 23:30:28 - Error bpbrm (pid=13018) cannot connect to xxxxxxx, Operation now in progress (150)
02/29/2012 23:30:28 - end writing
can't connect to client (58)

02/29/2012 22:55:18 - Error bpbrm (pid=8071) bpcd on xxxxxxx exited with status 48: client hostname could not be found
client hostname could not be found (48)

Which logs would be benificial?

Thanks!

Fred

[Mark_Solutions]

So are you saying that client xxxxxxx (obviously edited?) does not actually exist in any of your policies?

Did it ever exist in a policy?

[fordpony65]

Yes it is edited

Yes at one time it did

[Mark_Solutions]

OK - two possibilities then that come to mind ...

1. The policies have not bee re-read since it was removed - run: nbpemreq -updatepolicies

2. When no jobs are running check all media servers for bpbrm or bptm processes running - better still down NetBackup on all Master and Media Servers and check for any NetBackup processes till running (bpps -a) and kill them off the re-start NetBackup

3. Make sure you are all up to date (6.5.6) as there were many bugs in 6.5 - and 6.5.x goes end of life in October so consider upgrading as soon as you can

[fordpony65 · Accepted solution]

Thanks Mark will look all of that over!

Fred

[fordpony65]

Hi Everyone!

THank you all so much for all the help.  I ened up stopping and restarting the Master and Media server Netbackup clients and this did the trick. 

Thank you again to all who posted to help!

Fred

[jchuang]

Hello, sorry for reviving an old issue.

We have a similar case here. A job fails every 5 minutes and the policy of the job does not exist.

My NBU Version is 7.7.3.

Type of backup is blank, Status code is 96 (EMM status: No media is available)

The job policy is SLP_SLP_1w2m, and we do not have a policy named SLP_SLP_1w2m. 

We do have an active Storage Lifecycle Policy named SLP_1w2m though.

Thank you for any advice.

[StefanosM]

The prefix SLP_ is added automatically to SLP secondary operations.
So your problem is not the policy name but that you do not have tapes to support the secondary operation of the SLP named "SLP_1w2m"

[jchuang]

Thank you for the reply. I'll try to resolve the secondary operation problem.

[L_BR]

Is it an SLP that is actually in use? If not you can just use nbstlutil cancel -lifecycle <name> to terminate the secondary operations. 

[jchuang]

Yes. I'm afraid that the SLP is in use.