Most of the time, the creating an ADSM Service to do the backups is
best... for all the wonderful reasons below.


However, using NT's AT can give you more flexibility.  For example,
shutting down a database before backup, restarting it afterwards.  For
a task that makes a snap shot of a directory using PKZIP and having
ADSM back the ZIP file (why?  it was deemed better that way for that
data set.)

While you can set up these tasks to be done by the ADM client
"PRESCHEDLECMD" and "POSTSCHEDULECMD" options, these apply to every
scheduled event.

So if someone decided to use ADSM to schedule a restore or an
immediate event PRE and POST would be run, with possibly disastrous
consquences.

Another good use would be multiple, parallel streams.  I think the
list has done this one recently.


Or to provide deterministic scheduling to one client, but the majority
of your client base can happily use randomisation.


Russell



> When using the NT Scheduler (AT command), to do a nightly incremental
> backup the command is originating from the client.
>
> If you set up an NT Service, you can take advantage of client polling,
> centralized scheduling, and randomization of clients during a given window
> ... the server contacts the client as to when to start backing up.
>
>
> :)
> Ilona Kersey
> Siemens Westinghouse Power Corporation
> ilona.j.kersey AT swpc.siemens DOT com
>
>
>
> From:   Diana Cline [SMTP:Diana.Cline AT ROSSNUTRITION DOT COM]
> Sent:   Tuesday, November 17, 1998 1:42 PM
> To:     ADSM-L AT VM.MARIST DOT EDU
> Subject:        NT Scheduler vs. Service
> Can someone please tell me why I would use the NT Scheduler vs an NT
> Service to
> complete my nightly backups?
> -Diana