The Archive Log got to 80% full, so it triggered a full TSM DB backup. So far, so good.
However, as the first one was finishing, and before it could empty the Archive Log, a second full TSM DB backup was triggered. For a short while, there were two full TSM DB backups running. This second backup was a pointless duplicate, and may possibly be corrupted. It appears there is a window where the trigger does not know that a full DB backup has just been run. TSM Server 6.2.2.30 on AIX 5.3. Roger Deschner University of Illinois at Chicago rog...@uic.edu ======I have not lost my mind -- it is backed up on tape somewhere.=====
