Need to run NBCC and fix the issue with catalog

Run ./NBCC Current directory (.) is not by default part of PATH variable.

Thanks Andy and Marianne for your speedy respose! I completely forgot that it's not in the $PATH.

BTW, there are few more questions have before running NBCC.

       1. Does NBU need to be stopped on master and all media servers?

       2. What sould be the switch to run NBCC with? Does this output need to go to any file?

       3. Do i need to run NBCCR after NBCC, if so, with what switch?

       4. Any additional information or guidance would be appreciated. Like steps,etc.

Thanks Again!

Been a **long** time since I ran NBCC (& I have **never** run NBCCR).

Think you can go without any options, although last time I believe I did the -nozip & -nocleanup just to see what the output actually was - had a bit of time on my hands obviously. The -help does explain these options quite clearly & which you use may depend upon your environment.

The -help also explains what needs to be running & if NB is 'active' then you may get false positives so best to run when quiet. I think we also got false positives when it was "between cleanups" - images had expired but tapes waiting to be unassigned.

 

Probably best to run in conjunction with Support - I presume you have a call logged for your catalog issue?

Regarding the latter - why exactly is the catalog backup partially complete? What errors are you getting in job details?

 

 

Run NBCC without any options. It will produce a compressed/zip file with output that needs to be submitted to Veritas Support as part of a Support call. This is not necessarily going to fix the catalog status 1. Show us all output in the parent job and all of the child jobs. And tell us NBU version and patch level.

Netbackup 6.5.6 and we don't have support.
Since Netbackup is now seperated and is with VERITAS, we have a plan to start a fresh discussion with Veritas for NBU upgrade with Support.

There is one parent and 3 child jobs out of which two completes and one complete with partial success. PFA the job details.

BTW, any idea how long does this NBCC take so that i can schedule the downtime accordingly.

 

Seems you found this TN: http://www.veritas.com/docs/000011088 ?

No point in running NBCC if you cannot log a Support call for assistance.

Rather run bpdbm -consistency and check resulting bpdbm log for errors.

See : https://www-secure.symantec.com/connect/forums/bpdbm-consistency-checks 
and https://www-secure.symantec.com/connect/forums/how-use-bpdbm-consitency 

You can identify corrupt image headers yourself and remove it.

See this TN:

DOCUMENTATION: How to manually identify and remove zero-byte or corrupt image header files ......
http://www.veritas.com/docs/000034008 

Scroll down to  
Alternative Method:
and follow steps suggested in this section.

Just for reference, you don't need to stop NBU jobs to run NBCC.

The documantation says to stop them, but it doesn't actually matter - you may get 16_4 errors with it running, but we just ignore these anyway as they will have cleared when the backup completes, and in the very unlikely event they don't, you'll pick them up on the next run of nbcc.

The other mis-conception is that you have to run NBCC for an upgrade, again, totally untrue - there are no NBCC errors that will cause an upgrade to fail, PROVIDING, you are not upgrading from 5.x

Once on 6.x or 7.x, any nbcc errors before an upgrade will just be carried across and still be there after the upgrade.

Thanks Marianne!
I'm going with your suggestion first with the steps mentioned under 'Alternative Method' TN.

@mph999 - Awesome and thanks for clearing the mis-conceptions about NBCC.
Second option is to go with running NBCC. I'll keep you posted with the result and updates.

I'm also planning in parallel to have a cold catalog copy to be on safe side.