Will collocate by filespace help here? Or does the data still get processed one node at a time?
>>> [EMAIL PROTECTED] 04/09/2003 9:00:33 >>> Bill, I'll let any of IBM folks correct me if I'm wrong, but yes, to the best of my knowledge, that's how TSM works. On Thursday, Sep 4, 2003, at 02:54 Australia/Sydney, Slaughter, Bill wrote: > 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 > > -- Paul Ripke Unix/OpenVMS/TSM/DBA 101 reasons why you can't find your Sysadmin: 68: It's 9AM. He/She is not working that late. -- Koos van den Hout *********************************************************************************** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipients(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipients(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. ***********************************************************************************
