> So, I'm thinking my script could run something like:
>
> nsradmin> . type: NSR group
> nsradmin> print
>
> to get a listing of all the groups and then have the script parse out
> only those with autostart enabled,
Or..
nsradmin> show name
nsradmin> print type:nsr group; autostart:enabled
To have less parsing to do ...
> and these would constitute the active
> groups, and then when I run:
>
> nsradmin> show group
> nsradmin> print name:clientname
Just to avoid namespace collisions, I would always write that as
nsradmin> print type:nsr client;name:clientname
It's unlikely that you'll have something else with the same name that's
not a client, but also having a 'group' attribute, but it avoids
problems if this section is later modified.
> I can parse out only the active ones since now I know which ones are
> active from before and then I can run:
>
> savegrp -p -c client group
>
> for each active group to get a list of all the expected savesets for the
> client.
Several steps, but yes, I don't know any way to do it that is
significantly easier.
I would watch out for problems where the client is down and your savegrp
gives different answers.
Or, if you didn't need future information and could get away with
historical records, I might use 'mminfo' instead to see what was saved
on tape recently. It might not be as accurate, but there would be fewer
steps, and it wouldn't rely on the client being up.
--
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. >
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
