| > My Customer has 12+ NSR Servers & 350+ NSR clients, spread across the
> country. Each Server backups up a specific list of files for each of
> it's clients. This list is the same for each client. My customer now
> wants to modify this list & wants to know if there is a quick way to
> modify the saveset info without having to run nwadmin and manually
> enter the saveset info for each client.
nsradmin is the command line admin interface. You could use it
in a script that lists the clients then modifies the saveset for
each of the clients. Unfortunately, I don't have an example for
you.
> Do both the client & the Server need to be updated?
For backups that are initiated by the server, modifying the
saveset specs in the client definitions at the server is
sufficient. If backups are initiated by the client, then you'll
have to modify whatever scripts are launching these ad-hoc
backups.
> If backups are initiated by the client, will the index info be stored
> on the client or the server?
Index information is always stored on the server.
Wes
|
| Hi,
> My Customer has 12+ NSR Servers & 350+ NSR clients, spread across the
> country. Each Server backups up a specific list of files for each of
> it's clients. This list is the same for each client. My customer now
> wants to modify this list & wants to know if there is a quick way to
> modify the saveset info without having to run nwadmin and manually
> enter the saveset info for each client.
There is a way that Engineering surely will NOT advice: It consists of
editing the nsr.res file ...
> Do both the client & the Server need to be updated?
No, the client resources are stored in the Server.
> If backups are initiated by the client, will the index info be
> stored on the client or the server?
The "client" is only storing a few executable to read the files and
send them to the server. So all the "indexes" (for the clients or for
the tape) are ALWAYS stored in /nsr of the SERVER
Regards, Manu.
|