To cancel the backup:
on the servers administrative command line, issue a "q session", the
node name
of the client that is backing up should be listed with a session number.
issue "cancel session #" (replace the # with the session number)

To start where you left off (sort of)
When you resume the backup, make sure that you are doing an incremental.
The
backup will first go through the files that have already been backed up,
and
only copy those that have changed. Unless you have an unusually large
ammount of
change, this process shouldn't take too long. Once the process reaches
the point
that you canceled the backup, everything will be backed up. We have used
this
method for our first backup on each large client we have added to our
system.


Ann Courchaine wrote:
>
> Hi ADSM'ers
>      I have 2 client schedules that have been running for almost 24 hours.
> Is there a way to stop them with so that it picks up where it left off?
> This is causing a great deal of network traffic and it would be better to
> run the backups only at night
>
> Ann cpurchaine