Bill,
1. I think 1 tape pool is a bad idea. Not every machine needs a fast recovery and big
database backups won't benefit much from it. Split your nodes into different domains
and don't collocate the tape stgpool of one of them.
2. Insert your new collocated tape pool between disk and the current tapepool. Use
maxscr as others have indicated. In the unlikely event that you ever completely fill
up the collocated pool it wil automatically flow into the non-collocated one and no
data will be lost.
HTH
Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia
>>> [EMAIL PROTECTED] 30/07/2003 1:22:53 >>>
Hi TSM'ers
Has anybody out there gone from 3 years of nocollocation and then
changed to collocation for better restores. We are currently at 2-3+ TB of
info on 540 tapes (this is all in our 1 TAPEPOOL). We have about 410
scratch tapes and the uppers are worried about making the global switch to
collocate will cause TSM to crash due to no scratch tapes. Also if there
are any other gotcha's I would be greatly appreciated. Maybe even send
you, some of our greatest pizza haha.
Thank You,
Bill Rosette
Data Center/IS/Papa Johns International
WWJD
***********************************************************************************
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.
***********************************************************************************