I have many clients that are getting caught in my 'cancel ses all' that we
run at 6:55AM.

09/24/2004 06:55:30 Total number of objects inspected:   36,281
09/24/2004 06:55:30 Total number of objects backed up:    3,028
09/24/2004 06:55:30 Total number of objects updated:          1
09/24/2004 06:55:30 Total number of objects rebound:          0
09/24/2004 06:55:30 Total number of objects deleted:          0
09/24/2004 06:55:30 Total number of objects expired:         70
09/24/2004 06:55:30 Total number of objects failed:           0
09/24/2004 06:55:30 Total number of bytes transferred:    354.96 MB
<<<<<<<<---------- 350 Meg
09/24/2004 06:55:30 Data transfer time:                21,637.18 sec
09/24/2004 06:55:30 Network data transfer rate:           16.79 KB/sec
09/24/2004 06:55:30 Aggregate data transfer rate:          9.71 KB/sec
09/24/2004 06:55:30 Objects compressed by:                   50%
09/24/2004 06:55:30 Elapsed processing time:           10:23:29
<<<<<<<<<---------- 10 hours

Most of the data is really backed up early in the period.  This particular
client is basically the only user on a T1 circuit!

Why are these being 'hanging on' for 10+ Hours??????
Even more important, how can I get them to 'hang up' gracefully when they
are really done?

RTFM answers are OK, just please let me know WHERE to read it?

... TIA ... Jack

(environment is mainly Windows, client is 5.1.6, server is Windows 2000 with
TSM 4.2.3.1)