Networker

Re: [Networker] adjusting to NW 7.4.x

2009-02-18 10:43:39
Subject: Re: [Networker] adjusting to NW 7.4.x
From: "Goslin, Paul" <pgoslin AT CINCOM DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 18 Feb 2009 10:40:56 -0500
You failed to mention what OS platform you are running on....

Sounds like you are managing networker at such a low granular level (per
process), where things are possible that simply are not feasible via the
GUI....

I don't think there is a one-to-one process/save-session relationship in
7.4.x and above... Except maybe for client save-sessions, you should see
a save process on the client for each client session... 
I currently have 11 sessions running, but cannot find 11 processes that
share the same process name (we're on Windows server 2003). I normally
see one nsrmmd.exe process for each tape drive when the server is idle
(we have 5 LTO-2 drives). I currently see 7 nsrmmd.exe processes
currently and 6 nsrindexd.exe processes, as well as the normal
nsrexecd.exe, nsrd.exe, nsrjobd.exe (jobs), nsrlcpd.exe (library mgr),
nsrmmdbd.exe, and nsrmmgd.exe I currently have an index group running
saving only indexes, I see a save.exe for each session there since the
server is its own client and two savegrp.exe processes for the two
save-groups I have running. ... No way to tell which process goes with
which session or group though .. How is that done ??

As far as my experience, there is no way to kill a single session via
the GUI. You can only stop/abort the group the session is running
under... You can restart it, and it should only re-attempt the failed
save-sets.

> -----Original Message-----
> From: EMC NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Teresa Biehler
> Sent: Wednesday, February 18, 2009 10:03 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] adjusting to NW 7.4.x
> 
> We've taken the plunge and upgraded from v7.2.x to 7.4.x.  
> We're still getting used to the new interface, etc., that 
> came with the new version and figuring out how to "translate" 
> common tasks (or troubleshooting
> tasks) to the new way of interacting with the NetWorker 
> server.  In the old version, there used to be nsrexec 
> processes on the NW for each saveset that was backing up.  If 
> there was a problem, these processes could be killed.  How do 
> we do the equivalent in the new version?  How do we 
> kill/cancel a single session with the new version?
> 
>  
> 
> Thanks.
> 
> Teresa
> 
> 
> 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 with 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 with 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

<Prev in Thread] Current Thread [Next in Thread>