09-15-2011 09:11 PM
Anyone knows why invalid drive type/density usually tape?.
Solved! Go to Solution.
10-25-2011 12:48 AM
Yesterday I was applied device mapping http://www.symantec.com/business/support/index?page=content&id=TECH170162&cat=PATCHES&key=15143&base...
then restart the netbackup service.
09-16-2011 03:52 AM
'tpconfig -l' usually displays more info that that - it also includes the devices paths on the media server as well as the NAS server, e.g:
drive - 6 hcart2 18 UP - Drive18_L700 /dev/rmt/27cbn
drive - 6 hcart2 18 UP - Drive18_L700 c752t0l0
Verify that device access is healthy at OS level.
Wat does 'vmdareq' output on master look like?
And 'vmoprcmd -d' ?
The extract from bptm contains no errors.
Which OS on media server AAAAA? Which NBU version? Which NAS device?
09-19-2011 07:02 PM
Marianne,
I was cut the output tpconfig -l
09-19-2011 11:00 PM
I wouldn't spend too much energy on the 'invalid drive type...' message. NBU needs to issue a reset/release at OS level. Because the NDMP drive is configured on the media server, the 'crawlrelease' is probably getting its 'knickers in a knot' when it gets to the NDMP drive.
From your last output, it seems that the problem is on the HP-UX server since the drive is now UP on NDMP but DOWN on the media server. For increased logging as far as device management is concerned, add VERBOSE entry in /usr/openv/volmgr/vm.conf and restart NBU. Device type errors will now be logged to syslog (/var/adm/syslog/syslog.log).
09-20-2011 07:36 PM
Thanks Marianne,
Ya I will trace message from OS.
10-21-2011 10:32 AM
Any feedback/progress on this?
10-25-2011 12:48 AM
Yesterday I was applied device mapping http://www.symantec.com/business/support/index?page=content&id=TECH170162&cat=PATCHES&key=15143&base...
then restart the netbackup service.
10-25-2011 01:06 AM
Since you found the solution yourself, I am happy to mark your post as Solution.