I have that problem occasional. My server is running RedHat ES 3.0. What
I do is to use the command fuser /dev/xxx(the device that is idle) and
then kill -9 the process that's using the device. That restart the
nsrmmd for the device and the drive is ready.
Kind regards
Carl Bergmann
Risoe Nat. Lab
Dk
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Faidherbe, Thierry
Sent: Saturday, March 11, 2006 5:28 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Killing active sessions?
Darren,
Todd,
I worked also on same kind of problem a while ago. The problem is
the nsrmmd to wrongly keep the session(s) opened, resulting the drive
to stay in "writing, idle" mode.
Fujitsu Siemens nsr 7.2 has a great feature that allows to reset the
nsrmmd corresponding to the device from nwadmin GUI and it is
resolved within afew minutes (nsrmmd check and restart timeouts)
As other Networker version to not have yet that great feature,
the workaround is to go on the node that is handling the nsrmmd
writing to the device, using fuser, retrieve the right nsrmmd pid
and kill it and then wait servers default polling intervals to
restart the missing daemons.
Another workaround being, on storage node only, to stop the nsrexecd
service and then wait servers default polling intervals to restart the
missing daemons. This only if no other activity is being performed.
If you wait and keep the sessions as it, when next backup will request
a volume, as a volume is already mounted, then Networker will reuse
the device until the volume becomes full. At that stage, nsrmmd will
die by itself and the sessions will disappear as by magic.
HTH,
Th
Kind regards - Bien cordialement - Vriendelijke groeten,
Thierry FAIDHERBE
HP Services - Storage Division
Tru64 Unix and Legato Enterprise Backup Solutions Consultant
********* ********* HEWLETT - PACKARD
******* h ******* 1 Rue de l'aeronef/Luchtschipstraat
****** h ****** 1140 Bruxelles/Brussel/Brussels
***** hhhh pppp *****
***** h h p p ***** 100/102 Blv de la Woluwe/Woluwedal
***** h h pppp ***** 1200 Bruxelles/Brussel/Brussels
****** p ****** BELGIUM
******* p *******
********* ********* Phone : +32 (0)2 / 729.85.42
Mobile : +32 (0)498/ 94.60.85
Fax : +32 (0)2 / 729.88.30
I N V E N T Email/MSN : thierry.faidherbe(at)hp.com
Internet : http://www.hp.com/
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Willeat, Todd
Sent: Saturday, March 11, 2006 5:05 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Killing active sessions?
I'm working on a similar problem with Legato support right now. The only
way
I have found to kill it is to put my drives into service mode until the
"check storage nodes..." message is displayed...
-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]On Behalf Of Darren Dunham
Sent: Friday, March 10, 2006 4:28 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Killing active sessions?
I've recently seen an issue pop up on one server. One client does
oracle RMAN (nsrnmo instead of savefs) backups. If we stop the
backups, all the processes die (no more nsrexec, no more rman, etc.).
But the session remains active on the server (visible in nwadmin).
The sessions don't write any more data, but they don't die. I would
have assumed the 'nsrmmd' would eventually kill an idle session like
this.
Any idea how that timeout could be reported or tweaked? Or any way to
kill the session other than restarting all of networker?
The server is 7.1.1 on Solaris. Thanks!
--
Darren Dunham ddunham AT taos DOT com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if
you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
