ADSM-L

Re: Help please with collocation

2001-11-19 09:45:28
Subject: Re: Help please with collocation
From: Zlatko Krastev/ACIT <acit AT ATTGLOBAL DOT NET>
Date: Mon, 19 Nov 2001 16:44:35 +0200
Farren,

1. Collocation is made to speed up the restores. So it is a really good
idea.
2. You can define two primary pools, lets name them COLLPOOL and NOCOLLPOOL
over the same device class. Then clients you want to collocate send their
data to the former and the others to the latter. Later you can backup both
pools on same copy pool (artifically decided to be COPYPOOL ;-) or define
two separate pools COLLCOPY and NOCOLLCOPY.
And usually there is no need to collocate copy pool but it is your right.
3. Reclamation of copy pool is going other way than primary pool
reclamation.
If you want to get answers to many of your questions (even unasked ones) I
would recommend you the download from http://www.redbooks.ibm.com the nice
redbook SG24-5416-01 "Getting Started with Tivoli Storage Manager:
Implementation Guide".

Zlatko Krastev
IT Consultant





Farren Minns <fminns AT WILEY.CO DOT UK> on 19.11.2001 13:34:57
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Help please with collocation

Hello again TSMers

I have some another questions, this time regarding collocation.

At present we are backing up 21 client nodes and have a backup pool made up
of DISKPOOL and TAPEPOOL. Then we have our off-site volumes, imaginatively
entitled COPYPOOL. I am thinking that we do not necessarily need to use
collocation for all of our nodes; maybe just for five or six of our more
important ones (we do backup sets for these as well).

The questions are as follows:-

1)   What are peoples thoughts on collocation in the first place. Is it
generally a good idea? Any thoughts really?
2)   Secondly, can someone tell me a good, clean, simple way of achieving
only collocating certain clients.
3)   Also, baring in mind that at present, we back up all clients to one
COPYPOOL, what would be the implications of a) moving some clients to a new
backup COPYPOOL (what happens to all the data currently stored on the
original COPYPOOL and b) turning off collocation for the original COPYPOOL
(i.e. would this lead to a very long reclamation run).

There is probably a lot more inf. that I should have included here, but I
am relatively new and probably don't know the questions to ask.

Thanks again and I look forward to any help you can all give me.

All the best

Farren Minns
<Prev in Thread] Current Thread [Next in Thread>