03-21-2012 06:10 AM
Hello,
I am facing this strange issue with the netbackup 6.5.
Only Hot catalog backup is failing with media write error but usual solaris backup is working fine.
I did raised this concern with IBM but they suggested to use new medias.
I did procured new medias.
While labeling them I selected volume pool as Catalog but labeling job too failed with same media write error for new media.
is there any different procedure for media read/ write for catalog than usual backups in Netbackup?
03-21-2012 06:26 AM
share output of
bppllist <<< catalog_policy >> -U and
bppllist <<< policy name for which it is working fine >> -U
03-21-2012 06:31 AM
03-21-2012 07:48 AM
Hmm, strange it is only catalog backups. However, we have some good info:
"While labeling them I selected volume pool as Catalog but labeling job too failed with same media write error for new media."
Can you supply the details from the Activity Monitor job for the failing media label operation. What details are there in the system mesaages file (or event viewer if windows)
For info, NBU does NOT write to the tapes, the write operation is carried out by the operating system, so a write failure will almost certainly be due to the drive/ media /firmware or SAN
Martin
03-21-2012 08:20 AM
Did you do the label from the GUI or command line
I am assuming you mean CatalogBackup pool rather then catalog pool?
I could understand if they were used tapes as you could only label one of those from the command line as you need to answer the prompt to overwrite a catalog tape but new tapes should be OK (although there was something i heard about the catalog pool being protected so may want to try the commad line)
Only other thought is if the right protect tab is on
If everything else is OK i would be surprised if it was a tape or hardware issue
As a test drop it into another pool (but not a scratch pool) and label it from the command line to see if that works
03-21-2012 09:38 AM
Out put for bppllist:
03-21-2012 09:41 AM
Hello All,
Thanks alot for your suggestions.
I want to add 1 more thing here that I have standalone drive configured and not a robotic library.
As per my understanding if this is a hardware related issue it should affect normal backups as well.
But normal OS backups are working fine and the issue is only with the catalog backups rather catalog medias.
Regards
03-21-2012 09:56 AM
I agree, but, the overriding factor, is that NBU does not write to tape. Write operations are carried out by the OS.
We need to see if there is anything in the system event log showing the error
bptm log might show something.
What is in the details tab of the failing job from activity monitor ?
Martin
03-21-2012 11:12 AM
Replacing every bit of info that we are looking for with ##### does not help.
Give us SOMETHING to look at. If you do not want to share names, please replace them with something more meaningful than #####.
Use names like master, media1, client1, etc.
We need to see if anything is different about the STU (residence), local or remote backup.
Please ensure that you have bptm log enabled on the media server doing the backups as well as VERBOSE entry in /usr/openv/volmgr/vm.conf.
Restart NBU after adding VERBOSE entry. This will ensure that device-type errors are logged in /var/adm/messages.
03-22-2012 08:23 AM
Is storage unit of Working policy and catalog policy is same?
If not change the catlog policy storage unit as working policy.
03-23-2012 12:49 AM
Hi Marianne,
Sorry for the inconvenience..
I have only 1 server which is master server itself and backs ups itself.
So whatever i replace are the same things..
03-23-2012 12:49 AM
Hi Twinkle,
Bothe are same..
03-23-2012 02:27 AM
As well as the other suggestions i have made please set up the bptm logs (\usr\openv\netbackup\logs\bptm\) and then re-run the catalog backup and attach the bptm log file.
As Marianne says also enable the verbose logging.
We need to see something that can give us a clue to help you
Thanks
#EDIT#
One other thought - what media types are you using and what drives types are you using (so for example LTO5 drives and LTO4 catalog tapes - just wondering if your catalog tapes are not compatible with you tape drives)