[Networker] RE : [Networker] No of Session server is actively busy with

Query using nsradmin like :
 
nsradmin -s server
nsradmin> show session statistics
nsradmin> print type:nsr
          session statistics: id = 102010, name = secunda, mode = saving,
                              pool = M1R1 OTHE, volume = 001397,
                              rate kb = 2000, amount kb = 37680252,
                              total kb = 0, amount files = 0, total files = 0,
                              connect time = 35924, num volumes = 0,
                              used volumes = 3, completion = running,
             ......
 
and count for amount of "id=" or "name=" instances.
 
Above sample describe 1 save session.
 
 
 
You could put nsradmin cmds in a file and execute it like
"nsradmin -s server -i <cmdfile>" and redirect the output to a file.
 
Following sample should do that you want :
 
nsradmin -s server -i <cmdfile>"  |grep "name=" |wc -l
 
If you look at my networker reporter, you will get same kind of info in gantt 
charts.
 
HTH,
 
Thierry

________________________________

De: Legato NetWorker discussion de la part de Stan Horwitz
Date: mer. 27/07/2005 12:39
À: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Objet : Re: [Networker] No of Session server is actively busy with



On Jul 27, 2005, at 6:29 AM, Riaan Louwrens wrote:

> Hi All,
>
> I am trying to (for the life of me) figure out an "easy" way to see 
> (via
> nsradmin query) the number of sessions a backup server is currently 
> busy
> with.
>
> We have a Solaris server that seems to have performance degradation at
> some point and the normal Solaris tools shows that the server itself
> isn't very busy.
>
> I would like to cron a job that does some stats as well as what Legato
> is actually busy with at the moment.
>
> It is quite a large server and sitting there manually counting 
> savesets
> (or trying to go through them one by one if you use the "session" 
> or any
> of the session related resources / options with nsradmin) just doesn't
> work.
>
> Any Suggestions?

Yes. Look in the daemon.log instead. If your suspicion is correct 
that NSR is busy, it may actually be too busy to return results from 
nsradmin. Calling nsradmin will also cause additional load on your 
server.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=