Last week, I upgraded my server to TSM V3R7.  The client had been TSM for
months and seems to have had no problem with the exclude file, which looks like

EXclude  /adsmdb/.../*
EXclude  /adsmlog/.../*
EXclude  /adsmstgpool1/.../*
EXclude  /adsmstgpool2/.../*

       ...

EXclude  /adsmarch/.../*

I'd done an incremental before the upgrade and the occupancy for V3R1 was
about 4Gb.  After the upgrade, I started another incremental.  I waited a
reasonable length of time and I checked: 4Gb and still going.  It kept
going all afternoon, and the q sess showed 10Gb, 15Gb, etc.  It was still
run when I got home and it ran all night.  The next morning, q sess showed
100Gb and counting.  Q fi showed that it had processed a 30Gb and a 18Gb
storagepool.  What led me to cancel was the q occ of the node, which showed
that the process had backedup both storage pools and was starting on the
DB.  The pattern of the excludes has been working since V2R1, but suddenly
something seems to have gone wrong.  Have I missed something?


Fred Johanson
System Administrator, ADSM
S.E.A.
University of Chicago
773-702-8464