cancel
Showing results for 
Search instead for 
Did you mean: 

Status core: 52 on NBU 6.5

aduran
Level 3
Partner Accredited

Hi guys

I'm getting problems with NBU 6.5, because some job showing status code:52. and I can't complete the backup job.

 

 
The master is HPUX 11:31
 
I really apreciated your help ASAP
5 REPLIES 5

revarooo
Level 6
Employee

52 - media mount timeout.

What are the robot and drive models?

Have you tried deleting and re-adding the drives?

 

Check these technotes: 

http://www.symantec.com/business/support/index?page=content&id=TECH29145

http://www.symantec.com/business/support/index?page=content&id=HOWTO34938

http://www.symantec.com/business/support/index?page=content&id=TECH31854

aduran
Level 3
Partner Accredited

Is a StorageTeck, but I don't have the model

revarooo
Level 6
Employee

Have you checked the technotes and even tried deleting and re-adding the drives? I would.

Also NetBackup 6.x is out of support from October 3rd!!!

aduran
Level 3
Partner Accredited

 

I was thinking to do it, but I wasn't so sure. I'll follow your suggestion.
We know the  EOS 6.5 will be soon, but We're working in a upgrade to 7.x 
 
Thanks alot for your support

Marianne
Level 6
Partner    VIP    Accredited Certified

I agree with delete and re-add, but please verify that Persistent Binding is done at hba level before you do so.

Incorrect device mappings is known for causing status 52. Persistent Binding will keep device mappings the same across reboots.