ADSM-L

Re: [ADSM-L] Wrong estimation for VTL

2014-08-06 02:32:12
Subject: Re: [ADSM-L] Wrong estimation for VTL
From: Grant Street <grants AT AL.COM DOT AU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 6 Aug 2014 16:30:16 +1000
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 capacity again untill it has reached the End Of
Tape.

I have put in an rfe 31662 so that TSM would (better) estimate tape
capacity.
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=31662

The best solution would be to align the estimated capacity for the
device class with the actual data size you expect to fit on a tape.

Grant

On 06/08/14 15:37, Grigori Solonovitch wrote:
TSM 6.3.3.100
VTL on Data Domain
I have found wrong "Estimated Capacity:" for primary storage pools on VTL ( for example, 
for pool with 128 * 64 = 8192GB it gives estimated capacity 18,191 GB in "query stg", but 
it is impossible).
As a result storage pool utilization is calculated wrongly as well.
What is the source of problem?
Data Domain deduplication or something else?
Shall I ignore this problem?

Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, 
www.ahliunited.com.kw


________________________________

CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail 
message and any attachments hereto may be legally privileged and confidential. 
The information is intended only for the recipient(s) named in this message. If 
you are not the intended recipient you are notified that any use, disclosure, 
copying or distribution is prohibited. If you have received this in error 
please contact the sender and delete this message and any attachments from your 
computer system. We do not guarantee that this message or any attachment to it 
is secure or free from errors, computer viruses or other conditions that may 
damage or interfere with data, hardware or software.


Please consider the environment before printing this Email.

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