Yes, that's the way to do it. I would also define another non-collocated
tape storage pool and point the original pool at that one and set the
migration threshold to 98%. That way, if your first pool gets close to
filling, TSM will consume a scratch tape in the new pool and keep on going
avoiding the dreaded server out of data storage space. When you detect that
this has happened you can simply issue a move data on the volume in the
second pool: move data secondpoolvolume stg=firstpool, to get it back in the
correct pool.
Set N to the maximum number of tapes you want consumed by this pool in the
library.
Then, contemplate getting a bigger library! ;')
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (240) 539-7175
Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com
www.storserver.com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Eric Tang
Sent: Friday, January 12, 2001 7:58 AM
To: [EMAIL PROTECTED]
Subject: Question on Collocation with 7337 library
Hi All,
Environment:
- TSM v3.7.3
- IBM7337 library (15 slots) with around 10 tapes for onsite tape pool
status full, a cleaning tape and 3 to 4 scratch tapes
- Currently there are around 40 nodes defined in TSM
- a few more nodes are coming and backup data volume on existing nodes is
expected to grow, so there will be move media operation soon
- there is only one onsite tape storage pool defined and that is having
collocation off
To improve restore performance, I am thinking of turning on collocation for
onsite tape pool. But there are more nodes than number
of slot in library, should I define maxscratch=N and let TSM to collocate
data on the 40 nodes within the N tapes. Keep monitoring tape usage and
adjust N whenever necessary. Any suggestion on the setup and the number N?
Thanks in advance.
Regards,
Eric Tang
