1) ROT: If you are planning to back up to disk and migrate to tape, your disk
pool should be large enough to hold at least one complete night's backup.
(That way if you have tape drive problems in the middle of the night, your
backups will continue to run and you can kick the robot in the morning.)
2) One, until you have a really good reason to make more. If you have all your
space in 1 pool, TSM can make the most flexible use of it. (If you have it
divided into 2 pools, Murphy will insure that one pool will run out of space on
the day the other is only 10% used.) An example of needing 2 disk pools: you
are creating 2 tape pools, one which will be copied to go offsite and the other
not copied to go offsite. If you want to migrate to 2 separate tape pools, you
have to start with 2 separate disk pools.
Backing up different types of OS, having different domains with different
retention times, etc. do not require any type of pool separation. Use 1 as
long as you can, let TSM do the work for you..
W
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Dana Holland
Sent: Wednesday, August 04, 2010 5:32 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] guide for sizing storage pools
A typical newbie question, I'm sure - but is there a guide to help
determine how to size storage pools? And how many storage pools you
should create? I found a Redbook from 2006, but is there anything more
recent?
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5341 (20100804) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
|