Video Screencast Help

Issue: Changing tape drive

Created: 09 Jul 2013 | 5 comments

Hello everybody!

We have a big problem when our supplier changes a tape drive damaged. In our backup enviroment we use:
 
Library SL8500
ACSLS server versión 8.0.2
Oracle-Sun server, Solaris SunOS 5.10
4 media server on aix
After the supplier change a tape drive, we have to delete all tape drive from NBU 7.5.0.4, after we have to use wizard and create again the tape drives.
 
The issue starts, when new tape drive displays messages like this:
 
Jul  8 12:49:27 master_server daemon:err|error acsd[1900722]: ACS(1) going to DOWN state, status: Timeout waiting for robotic command
Jul  8 12:49:56 master_server daemon:err|error acsd[3317880]: ACS(1) dismount failure for volume ABC123  on drive (0,0,1,5), ACS status = 29, STATUS_DRIVE_IN_USE
Jul  8 12:49:56 master_server daemon:err|error acsd[3317880]: ACS(1) waiting to resubmit dismount request (attempt 2) for volume ABC123  on drive (0,0,1,5)
Jul  8 12:50:26 master_server daemon:err|error acsd[3407982]: ACS(1) dismount failure for volume ABC456 on drive (0,3,1,8), ACS status = 29, STATUS_DRIVE_IN_USE
Jul  8 12:50:26 master_server daemon:err|error acsd[3407982]: ACS(1) waiting to resubmit dismount request (attempt 2) for volume ABC456 on drive (0,3,1,8)
Jul  8 12:57:24 master_server daemon:err|error acsd[3317880]: ACS(1) dismount failure for volume ABC123  on drive (0,0,1,5), ACS status = 29, STATUS_DRIVE_IN_USE
Jul  8 12:57:24 master_server daemon:err|error acsd[3317880]: ACS(1) waiting to resubmit dismount request (attempt 3) for volume ABC123  on drive (0,0,1,5)
Jul  8 12:58:01 master_server daemon:err|error acsd[3407982]: ACS(1) dismount failure for volume ABC456 on drive (0,3,1,8), ACS status = 29, STATUS_DRIVE_IN_USE
Jul  8 12:58:01 master_server daemon:err|error acsd[3407982]: ACS(1) waiting to resubmit dismount request (attempt 3) for volume ABC456 on drive (0,3,1,8)
 
So we don't have idea in which part of the components is the problem. I like to know if I need run some command from the media server, or from the acs server? 
Someone have any idea?
 
Regards.
 
 
 
 
Operating Systems:

Comments 5 CommentsJump to latest comment

Nagalla's picture

first.. when dirve got replaced you does not need to run the reconfiguration in netbackup.

 

Jul  8 12:58:01 master_server daemon:err|error acsd[3407982]: ACS(1) waiting to resubmit dismount request (attempt 3) for volume ABC456 on drive (0,3,1,8)

 

seems it has stuck tape.

what it output of below commad in ACSLS

q dr 0,3,1,8

if it is showing the tape in drive try to dismount the tape from the ACSLS server 

dismount <tapeid> <driveid> froce

see if you are able to dismount it or not.. if not you again need hardware support.

if you are able to dismount then try to reset and up the drive from netbackup and see how it goes

Carlos V's picture

Hi Nagalla,

What do you do when changes a tape drive on your library?.

The command do you recomends always say:

Dismount: Dismount failed, Drive identifier   0, 3, 1, 8 in use.
 
After 20 or 30 minutes the tape drive releases the cartridge, some process on the media server "capture" the drive and displays again the messages:
 
Jul  8 12:58:01 master_server daemon:err|error acsd[3407982]: ACS(1) dismount failure for volume ABC456 on drive (0,3,1,8), ACS status = 29, STATUS_DRIVE_IN_USE
Jul  8 12:58:01 master_server daemon:err|error acsd[3407982]: ACS(1) waiting to resubmit dismount request (attempt 3) for volume ABC456 on drive (0,3,1,8)

 

Nagalla's picture

does it giving the same error when you try to force unmount the drive? and no activity going on in Netbackup level.

if yes... you need to look into the ACSLS and hardware level.

try to power cycle the driver once and and if it still have the issue... check with hardware  vendor.

Marianne's picture

Was this drive deleted and re-added on all media servers?

some process on the media server "capture" the drive...

Is only one media server involved here? Do you have verbose entry in vm.conf on media servers? This should give us something to look at in /var/adm/messages (provided syslog is enabled on AIX media servers).
bptm log on media servers?
Anything in AIX errpt during this time?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Nicolai's picture

The "dismount failure for volume" indicate a hardware issues outside the control of Netbackup.

The "capture" you see is proberly the EMM device allocation. You can user nbrbutil -dump to see active allocation. Do a grep on the tape drive name. 

You can release the allocation with the parameter 

-releaseMDS ID

-releaseMedia mediaID

After tape drive replacment use this procedure to update Netbackup with the new drive serial number.

DOCUMENTATION: How to update NetBackup for a replaced tape drive without deleting and re-adding the drive

http://www.symantec.com/docs/TECH34296

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.