This information is more of the preventiave steps than fixes, but it might help some people that few this thread from having these problems in the future.
Did you by any chance get to use the NCVU utility before upgrading to 6.0? This utility is very helpful in finding configuration problems that can cause problems during the upgrade.
Also to note, during our upgrades we also ran a catalog consistency check (bpdbm �consistency) before the upgrade to find and resolve any problems with the netbackup catalog and volume database.
I believe both the NCVU utility and the catalog consistency check are suggested to be used by the Netbackup Instillation Guide before an upgrade. We also did due diligence and ran the Netbackup nbsupport script before the upgrade to hand over to support if needed.
As for recovery, is your catalog data in binary or ACSII? It is highly suggested to convert any NetBackup ACSII catalog information to binary mode using the cat_convert utility before upgrading to 6.0. Netbackup 6.0 does not support writing to ACSII catalog data. It is however noted that it should be able to read the data, however I do not know many people who have ACSII catalog data configured.
If you upgraded the box from 3.4 or 4.5 to 5.1, then this might be an issue. Default behavior on 5.1 is to use Binary catalog data.
Do you see the directories of your clients in "../NetBackup/db/images" ? Are there directories and files in the "images/
//" folders?
The files will be in the format of "__" and you should see many that end in ".f"
If these files are present, then your catalog data is intact and there is a software problem. If the data is missing, then your catalog has been wiped during the upgrade of netbackup somehow and will need to be recovered from tape.
I wish you much luck.