>
> So, savegroup cannot be run from the client side?

Not directly.  You could have a script that asked the server to run a
savegroup (either via an exec in rsh/ssh, or via NSR authorization and
nsradmin to start a predefined group).  But that's not really 'running
on the client side'.

It does get nicely involved though.. :-) The client would then be
contacting the server to run 'savegrp', which runs 'nsrexec', which
talks to the client's 'nsrexecd', which launches 'save', which talks to
the servers's nsrmmd...

> I had a client who wanted a command line alternative to nwbackup.  So, I
> gave them the save command with some switches.  Somebody then told me that
> savegrp would offer the client more control.

I don't like having to use the raw 'save' because the output doesn't get
logged.  You have to deal with it on the client instead.  Also, the
'save' normally requires a timestamp to reference for incremental
updates.  The client doesn't normally keep that information.  You'd have
to keep the timestamps yourself (or determine a way of querying the
server for it).

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=