With ADSM 3.1 (no idea if this behavior has changed in TSM v4), when
we back up a busy UNIX application server, the app server is invariably
writing multiple log file entries to its app logs per second.

ADSM seems to be making an attempt to back up the files, sees it's changed
mid-transmit to ADSM server, then retries the backup of the file, sees
it's changed yet again, and so forth until X number of attempts... then it
gives up and moves on to the next file.

The implications of this is not good... that:

        a) backups of busy app servers will stall on the logfiles

        b) logfiles are least likely to ever get backed up if on a busy server

Is there any way to deal with this in a reasonable way, short of quiescing
the application? (Quiescing = downtime, which we can't quite do...)

-Dan Foster
IP Systems Engineering (IPSE)
IP Systems Engineering (IPSE)
Global Crossing Telecommunications