We are supplementing our existing ATL with a 6TB SATA. Clients will
continue to backup directly to the TSM server's local SCSI disk which
will get migrated to the SATA stgpool which will migrate to the ATL.

Since our W2K TSM server is limited to 2TB file systems we will be
allocating 3 filesystems for the 6TB of space. Because of the single
path issue when using dynamically allocated scratch volumes in the SATA
pool I intend to define the pool with maxscratch of 0 and preallocate
all the the vols with the dsmfmt command and then define all the vols to
the SATA pool. So far so good.

In the case of dynamically allocated vols TSM allocates and then
increments the size of the vol as needed up to the max size specified.
When no longer needed the vol is then deleted so the space can be reused.

When using predefined 20GB vols will TSM append to the end of the vol if
it is not completely full just as it does for tape vols or does it go to
the next available volume in scratch status? I suspect and hope the
answer is the latter but what's the real answer?

TIA

--

Steve Bennett, (907) 465-5783
State of Alaska, Enterprise Technology Services, Technical Services Section