I'd like to hear from a *SM guru from IBM on this one. We had the same
situation where we added some new volumes in a new directory to our disk
storage pool and forgot to add an exclude statement to the inclexcl file.
Lo and behold, the next incremental backup for the TSM server node created
136GB of useless backup data, not to mention filling up our disk pool and
kicking off migration, right in the middle of the busiest backup period!
Was there an amendment to the Backup/Archive Client manual for shared
dynamic serializationor are we mis-interpreting the text. The manual states
that if a file is in use during the first backup or archive attempt, the
operation is attempted again the number of times you specified with the
changingretries parameter. The backup or archive operation occurs during
the last attempt whether the file is in use or not. Does this not imply
that only one copy of the file is sent to the *SM server? Please clarify.
