01-23-2013 10:35 AM
Team
Need solution on the below issue
Netbackup CATALOG_DRIVEN_BACKUP is failing with status 87 using datadomain but same time normal backups using same DD storage unit is completing successfully
Master server : Netbackup 7.1.0.4 on Windows 2003
Media server : Master server act as media server itself as this is remote master server
Please let me know how to proceed with the above
Regards,
Kumar
01-23-2013 12:15 PM
The writing part of the catalog backup is not really any different than a normal backup, the 'clever' bit of the catalog backup is performed before the write is made.
There is one difference however which you probably don't have sent on you regular backups, and that is the TIR option is set.
I would suggest enabling the TIR option on a regulat policy (set on the attributes screen) and run a test - this will narrow the issue down, if the regular backup than fails.
Additionally, we would need the logs from the catalog backup - bptm, bpdm, bpbrm, bpbkar and bpcd
M
01-23-2013 12:58 PM
01-23-2013 01:16 PM
Can you also look at the logs on the datadomain - I suspect it might log something (apologies, I am not too famliar with DD so cannot really advise on which logs).
01-23-2013 01:50 PM
Missing the bptm log (and bpdm was empty, though there might not be anything logged in here).
Can you create the bptm dir, set the verbose level to 5 and general to 2, and repost the logs.
One really important question - did this ever work ?
Is this a big catalog - how long do you think the catalog backup should run for - are we taking a 1 or so or many hours ? Just need an estimate.
Thanks,
Martin
01-23-2013 01:56 PM
01-23-2013 02:02 PM
Hmm, seems that there can be many causes of 87 on disk - I've been looking through a few previous cases.
Network issues seem quite common
Time out issues (but this was on a netapp)
Disk failure
However, the one over riding factor, which is making this a bit confusing is you only report the issue on catalog backups, so it would appear something that is different about this type of backup.
The only thing I can think of (as mentioned) that is probably different is that TIR is always enabled for a catalog backup (hence my request to test a 'normal' backup with this enabled.
The other possibe difference of a catalog backup, is that it is backing up (part of the master) (other backups are probably of different clients) and the length of the catlog backup could be very long compared to others.
These are just a few ideas, and odd as it seems, sometimes these sort of things are a cause or contributing factor.
Is there anything on the datadomain that is unique for the catalog backup - apologies, not familar with these, but my thoughts are if the catalog backups use a different 'location' of the DD (if this is possible ?).
M
01-23-2013 11:27 PM
Yep, bptm also writes to disk ...
TBH, I'm not convinced that we going to get much more info than we have from the details you have posted, but we should look.
Most imporantly are the questions I asked.
Has this worked in the past
If it did work previously, what has been changed
What happens if you enable TIR on a regular policy
How big is the catalog backup
Anything special on the DD
Thanks,
Martin
01-24-2013 12:24 AM
Can you post the detailed job text from the activitry monitor ?
Have you tried to delete the catalog backup policy and re-create it ?
01-24-2013 01:21 PM
Right I've got my brain in gear tonight re datadomains ... The DD has luns mapped to diskpools in NBU, are you using a separate diskpool for the catalog backup ?
Thanks,
Martin
01-24-2013 01:45 PM
01-24-2013 02:03 PM
You can't turm TIR off on Catalog backups, it's always on.
M
01-24-2013 08:50 PM
01-24-2013 09:18 PM
As from NBU 6.5, ALL backups log to bptm - disk and tape.
bpdm only logs disk cleanup info.
So, yes - we need bptm log.