I have been reading the documentation and would like "The List" to confirm
my readings that there is no way around this "feature" (shy of splitting the
nodes data up). Please refrain and HOLD back any "You Should Upgrade Your
Hardware" comments since I am looking for an interim solution till I can
make that purchase.



If I run a backup storage pool (Disk Pool to Tape Pool) on a storage pool
that contains (roughly) 200 GB of backup data that TSM will only allocate 1
process per NODE no matter how much data is in the DISK pool to be backed up
(up to the amount of processes specified by MAXPROCESS=).



Given the following DISK storage pool contents:



            1 Node contains 100GB of Data (50 File Systems)

            1 Node contains 70GB of Data (40 File Systems)

            1 Node contains 30GB of Backup Data (1 File System)



If I run the following command:



            TSM> backup stgp DISK_POOL TAPE_POOL maxprocess=4



At most 3 processes start backing up data (1 per Node) and the longest
running process is the one with 100GB but it only uses 1 tape drive at a
time. This means to me that the other drives are not being used by the
backup storage pool processing.





Environment:

TSM Server 4.2.3.2  (Testing 5.1.7.2)

HP V2500 32 CPU - HP-UX 11.0

STK 9710 DLT7000 (8 Drives)





Bill Slaughter

Tupperware

407-826-4580