The estimated capacity shown in Q STGPOOL output is pretty much
useless/misleading for sequential pools, as it's based on the MAXSCRATCH value
for the pool, plus other factors.
See the admin ref pages for Q STGPOOL output field descriptions.
W
-Original Message-
From: ADSM: Dist Sto
. This
storage pool only contains the Windows DIRM MC management class data.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Grigori Solonovitch
Sent: Wednesday, August 06, 2014 9:39 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Wrong estimation for
Thank you very much for response.
I agree with you totally, but estimated capacity is wrong in TSM for many
primary pools allocated on Data Domain VTL. For example, for 128 tapes with
size 64GB (max 8192GB) it gives "Estimated Capacity: 18,191 G".
Any comments?
Grigori Solonovitch, Senior System
One note to consider with DataDomain. The tape has no compression from the TSM
perspective. If you create 100GB tapes, the estimated capacity in TSM should
be 100GB. TSM will store 100GB on a tape.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST
Thank you very much for RFE and information. I will try to modify device
classes.
Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait,
www.ahliunited.com.kw
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Grant
Street
S
The following is how TSM handles tapes, I assume VTL would be the same.
Essentially the estimated capacity is assigned to the tape when it is
allocated to a stgpool and loaded into the drive.
This value is determined from the device class"Est/Max Capacity (MB)"
TSM will not update the capaci
