Unsolved
This post is more than 5 years old
24 Posts
0
2753
Tape Drive stuck in Verify Label condition
Hi,
I had a hardware issue with a tape drive in my jukebox. I was able to fix the tape drive and remove the tape. However, networker will not let me use this drive while it is still in verifying label mode. I know that I could stop and start networker to fix it. But, I don't want to interrupt the backups that are currently running. I tried changing the drive status via nsradmin, but that didn't work.
So, I'm wondering if I kill the appropriate nsrmmd process, would it regenerate itself fixing my problem? If so, how do I map the daemon number (i.e. nsrmmd -n #) to a drive?
If this doesn't work, short of stopping and starting Networker, how do I fix this?
Thanks,
Jim
I had a hardware issue with a tape drive in my jukebox. I was able to fix the tape drive and remove the tape. However, networker will not let me use this drive while it is still in verifying label mode. I know that I could stop and start networker to fix it. But, I don't want to interrupt the backups that are currently running. I tried changing the drive status via nsradmin, but that didn't work.
So, I'm wondering if I kill the appropriate nsrmmd process, would it regenerate itself fixing my problem? If so, how do I map the daemon number (i.e. nsrmmd -n #) to a drive?
If this doesn't work, short of stopping and starting Networker, how do I fix this?
Thanks,
Jim
japgar
24 Posts
0
November 18th, 2008 13:00
Hari5
443 Posts
0
November 18th, 2008 19:00
japgar
24 Posts
0
November 19th, 2008 08:00
japgar
24 Posts
0
November 19th, 2008 10:00
Hari5
443 Posts
0
November 19th, 2008 15:00
Can2
100 Posts
0
October 18th, 2010 06:00
Hi,
Could you share fuser usage for mapping mmd processes.
Thanks.
ble1
2 Intern
2 Intern
•
14.3K Posts
0
October 25th, 2010 01:00
# fuser /dev/rmt/0cbn
/dev/rmt/5cbn: 10249o
# ps -ef | grep 10249
root 10249 11204 0 16:09:00 ? 128:22 /usr/sbin/nsrmmd -n 5
On some systems you may wish to use fuser -u
or fuser -cu
. On some systems it won't work (like HPUX 11.31).
Anyway, once you know the process id (eventually, lsof can be used too), you can use kill command against process. Where fuser works fine, fuser -ku
will kill it too.
Can2
100 Posts
0
December 23rd, 2010 01:00
thank you but seems that we cant apply it.There are nearly 500 tape devices in environment.
ble1
2 Intern
2 Intern
•
14.3K Posts
0
December 26th, 2010 06:00
Why? You see the path and you just query against the path in question...
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 15th, 2011 13:00
If this happens frequently, this may be due to authentication issues. The latest cumulative fixes corrects this problem especially on Data Domain devices.
Can2
100 Posts
0
March 16th, 2011 04:00
No we are using 7.5.3.2. Which cumulative fix do you advice ?
Can2
100 Posts
0
March 16th, 2011 05:00
Thanks
ble1
2 Intern
2 Intern
•
14.3K Posts
0
March 16th, 2011 05:00
7.5.3.5. There are newer, but my experience is that 7.5.3.5 should be ok (even 7.5.2.4 was even better - at least in my env).
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 18th, 2011 13:00
The issues that I worked on (mainly related to DataDomain devices, along with Solaris needing latest cluster patches) were fixed in 7.5.4.2 and 7.6.1.4.
The issue was related to heavy load on weekends, and errors logged such as application id=0. This was related to nsrmmd not getting proper application credentials. We only saw it in couple of environments both with DataDomain.
We didn't see it on any of the physical libraries.
vineshpandit87
3 Posts
0
August 2nd, 2011 06:00
Hi,
If tape drive stuck in verify Label condition, Please follow the below mentioned steps.
1 Login to client server (if it is storage node) or backup server if it is physical drive.
2 Right click on "My computer" then click on "manage".
3 Click on "device manager"
4 Click on "Tape drives"
5 Right click on the tape drives which is visible on Tape drives (OS) and click on properties
6 Check for the "Tape Symbolic Name" tab.. If it is visible on the tape drive then fine.
7 If it is not visible on the tape drive properties..Right click on tape drive and click on "Update driver". Then install the driver.
The above mentioned steps will resolve the issue.
Thanks