cancel
Showing results for 
Search instead for 
Did you mean: 

Issues with upgrade from NBU5.1 to NBU6.0 MP2

Russell_Manaois
Level 4
I have encountered a couple of issues after upgrading to NBU6.0 MP2.

1) When examining the Robot Contents, NBU reports only 64 slots; our robot library is a Quantum PX506 LTO, which has 100 slots

2) When performing disk to tape relocation, the load operation on the robot fails on each of our two drives. The library tried to load every piece of media in the same fashion, with the same results.

05/04/2006 12:50:45 - begin Duplicate
05/04/2006 12:50:48 - started process bptm (pid=22386)
05/04/2006 12:50:51 - started process bpdm (pid=22394)
05/04/2006 12:50:51 - begin reading
05/04/2006 12:50:52 - started process bptm (pid=22386)
05/04/2006 12:50:52 - mounting 003045
05/04/2006 12:50:45 - requesting resource atlantis-hcart3-robot-tld-0
05/04/2006 12:50:46 - granted resource 003045
05/04/2006 12:50:46 - granted resource HPUltrium3-SCSI0
05/04/2006 12:50:46 - granted resource atlantis-hcart3-robot-tld-0
05/04/2006 12:50:53 - Error bptm (pid=22386) error requesting media, TpErrno = Robot operation failed
05/04/2006 12:50:53 - Warning bptm (pid=22386) media id 003045 load operation reported an error
05/04/2006 12:50:53 - current media 003045 complete, requesting next media Any
05/04/2006 12:51:16 - started process bptm (pid=22386)
05/04/2006 12:51:16 - mounting 003045
05/04/2006 12:51:17 - Error bptm (pid=22386) error requesting media, TpErrno = Robot operation failed
05/04/2006 12:51:17 - Warning bptm (pid=22386) media id 003045 load operation reported an error
05/04/2006 12:51:14 - granted resource 003045
05/04/2006 12:51:14 - granted resource HPUltrium3-SCSI1
05/04/2006 12:51:14 - granted resource atlantis-hcart3-robot-tld-0
05/04/2006 12:51:17 - current media 003045 complete, requesting next media Any

Also, catalog backups to tape fail as well, with status 164.

5/05/2006 08:33:22 - begin Catalog Backup
05/05/2006 08:33:27 - mounting KUT561
05/05/2006 08:33:29 - Error bptm (pid=19041) error requesting media, TpErrno = Robot operation failed
05/05/2006 08:33:51 - mounting KUT561
05/05/2006 08:33:52 - Error bptm (pid=19041) error requesting media, TpErrno = Robot operation failed
05/05/2006 08:34:15 - Error bpbackupdb (pid=19031) jmcomm_getMediaOpStatus failed with stat = 0, error = 164
05/05/2006 08:34:15 - end Catalog Backup; elapsed time 0:00:53
05/05/2006 08:34:15 - Error bpbackupdb (pid=19031) Offline catalog backup to media id KUT561 FAILED

Before the upgrade, the disk staging and catalog backups worked fine.

--Russell
7 REPLIES 7

AKopel
Level 6
Did you run nbpushdata after the upgrade?

Russell_Manaois
Level 4
According to my DBA, Veritas Support had him run NBPUSHDATA after the upgrade. After that, I was tasked with checking that all was functioning OK; this is when I found these discrepancies.

AKopel
Level 6
I would recommend re-scanning your robots with the "Configure Storage Devices"

Russell_Manaois
Level 4
After re-scanning the storage devices, I am still unable to see the remaining slots or successfully complete backups to tape.

AKopel
Level 6
At this point, you might want to call support. I looks like possibly a robot problem.

Russell_Manaois
Level 4
After consulting with Quantum, the NetBackup issue was caused by the configuration of the PX506 library LOAD PORTS. The LOAD PORTS were assigned to 2 of the four tape library magazines, causing them to be designated as 36 mail slots instead of primary slots.

After disabling the LOAD PORTS on the library, NetBackup can now see all 100 slots and tape backups are now functioning as they were with v5.1.

Anonymous
Not applicable
A long shot but try looking into the unified logs. I found interesting flags had somehow been set, and decided to remove them and I was able to see my new media servers devices in Device Configuration. It all hung around the EMM database.
And a key set called NBPUSHDATA_G_GLOBDB_HOST

Repeat problem, then On the MASTER: Check the Unified Logging logs for the nbemm daemon (111) for the last 10 minutes since running the config wizard or backup
# vxlogview -o 111 -t 00:10:00

I also used this document to help out http://support.veritas.com/docs/283176