As far as I Know, the system can't be set to allert, but if run from the
backup-archive client, the GIU gives you an option to view failures.
When run from a schedule, you also have two files on the client to check
in the baclient subdirectory on the client (Suggest that you share the
ADSM directory so that you can connect to the clients from a
workstation)
1.dsmsched.log (List all files backed up, errors, and backup results)
2.dsmerror.log (List all failures and error codes)
  Note: these files can get really large, you can set a prunning option
to prevent them from filling up your disk.

The clients use a password, just don't give the password to the users.
You can also share the client with your workstation or the server. You
can access their client by running your backup-archive client selecting
"display drives for node" from the utilities menu.

To control backups from the server, you can use the backup-archive
client on your server (See above) or use either server prompted or
client poling scheduling. Either way, you set the schedules at the
server. Just look up Schedule in the documentations. (It's kind of hard
to find what you want in the printd documentation, The online books are
handy for this because you can use the search feature to find what you
want)
Hope this helps-
Doug Thorneycroft



Rafael Goldschmidt wrote:
>
> Dear Adsmers,
> I have some questions.
> In a Windows NT server, does the system alert if it could not save an
> object because it was blocked or occupied by other program? By what
> means does it alert?
> Can the system administrator inhibit the clients to start a backup
> themselves? In other words, a company wants to launch the backups only
> from the server and never from the clients.  How is this done?
> Many thanks!
> Rafael J. Goldschmidt
> Buenos Aires, Argentina
> rafagold AT cano.com DOT ar