Please help !!! URGENTLY<br><br>could someone tells me what should I do, here is the error message I get: <br><br>May 1 09:22:45 2000: Backup Server: 4.4.2.1: Device dev/rmt/0n does not belong to session <52>. Notification failed.<br><br>Because of this error, I redo the backup, and it comes the worse, here is another message:<br><br>1> dump database master to tapedump with init<br>2> go<br>WARNING: In order to LOAD the master database, the SQL Server must run in single-user mode. If the master database dump uses multiple volumes, you must execute sp_volchanged on another SQL Server at LOAD time in order to signal volume changes.<br>Backup Server session id is: 64. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.<br>Backup Server: 4.55.2.1: Device validation error: couldn't open raw device /dev/rmt/0n, error: Device busy<br>Msg 8009, Level 16, State 1:<br>Server 'WRDBQ1', Line 1:<br>Error encountered by Backup Server. Please refer to Backup Server messages for details.<br><br>thanks<br>
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Device Busy message
- Thread starter babeo
- Start date
Try running (as root):<br><FONT FACE=monospace><br>/etc/fuser -u /dev/rmt/0n<br></font><br>This should identify the process that is holding the drive open. It's very possible that it's another Backup Server process that's holding the tape drive open. ie, when you tun <FONT FACE=monospace>ps</font> and <FONT FACE=monospace>grep</font> for the PID number returned by <FONT FACE=monospace>fuser</font>, the program name begins with "nsr".<br><br>If this is the case then you can shutdown the Backup Server and restart it. Login as root, then:<br><FONT FACE=monospace><br>sh /etc/init.d/networker stop<br>ps -efa ¦ grep nsr<br></font><br>Manually kill any "nsr" processes that are still hanging around. Then:<br><FONT FACE=monospace><br>sh /etc/init.d/networker start<br></font><br>It may be that the "nsr" processes will not die. If this is the case, I'm afraid you'll have to reboot the system 
<br><br>Hope this helps.
<br><br>Hope this helps. Oops - forgot to say - if <FONT FACE=monospace>fuser</font> returns a non-"nsr" process (for example, a tar command), just try killing the command. It's still possible, though, that the process won't die and you'll need to reboot if this is the case.
- Thread starter
- #4
Thank Andy<br><br>I think your last message matches with my DBA's decision. She finally has to reboot all the servers related to that backup server and now everything seems fine.<br><br>Thanks anyway, hope that I have a chance to try your solution next time.<br><br>(in fact, I kill the ps of backup and when I check the device - mt status - I still get message of 'Device busy' and that is why I consider unload all tapes, power cycle the tape drive, and I still get 'Device busy' ! but according to the message, I already think about reboot the backup server, but I don't have power to do that yet !!! and I never do that before to experience it ! So I end up here )<br><br>CT
)<br><br>CT Ah, well, there's a few processes that will be running that could still be hanging on to the tape device.<br><br>The Backup Server software is Legato Backup Manager licensed to Sun. We've been using Backup Manager for a couple of years now, and we back up 50 servers (Unix, Novell, and NT) to a single Unix server connected to two DLT drives. The normal processes we see are:<br><br>/bmanager/nsrd <br>/bmanager/nsrexecd <br>/bmanager/nsrexecd <br>/backup/sbin/nsrindexd <br>/backup/sbin/nsrmmd -n 2<br>/backup/sbin/nsrmmdbd <br>/backup/sbin/nsrmmd -n 1<br><br>(Path names are a little different to the Solaris version.)<br><br>So, you might kill off, for example, nsrexecd, but nsrmmd is still there hanging on to the tape drive.<br><br>You can restart the Backup Server in two ways. The way I described above ("sh /etc/init.d/networker stop", kill any left over processes, "sh /etc/init.d/networker start", or you can just run "sh /etc/init.d/networker restart".<br><br>We've found that the "stop, kill, start" sequence works best though, but your mileage may vary <br><br>Glad to be of help, and hope this helps in the future.
, or you can just run "sh /etc/init.d/networker restart".<br><br>We've found that the "stop, kill, start" sequence works best though, but your mileage may vary <br><br>Glad to be of help, and hope this helps in the future. - Thread starter
- #6
- Status