overestimating MAXSCRATCH. There is only one storage pool in
this devclass. In fact, changing the MAXSCRATCH value does not change
Estimated Capacity, despite what the manuals say.
The Q DIRSPACE and Unix df commands both show the same true status.
This situation is making setting migration and reclamation
: [ADSM-L] LTO4 Tape Volumes with diferent Estimated Capacity
Hello all
Thank you for your all answers.
Regarding to your experience what is more efficiency regarding to tape
usage capacity (increase tape amount of data stored)? Compression on
client or compression on Drive(HW)?
Cumprimentos
-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Botelho, Tiago (External)
Sent: quarta-feira, 18 de Janeiro de 2012 15:27
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] LTO4 Tape Volumes with diferent Estimated Capacity
Hello
I have several tape volumes (LTO4) with
ercentages used, but all should have the same estimated capacity. Meaning they
have not been filled yet.
Regards,
Duane
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Botelho, Tiago (External)
Sent: Wednesday, January 18, 2012 9:27 AM
I believe the "estimated capacity" of a full volume is the actual amount
of data written to the volume when it became full, so it's not really
estimated anymore.
On 01/18/2012 07:27 AM, Botelho, Tiago (External) wrote:
>
>
> Hello
>
>
>
> I have severa
] On Behalf Of
Botelho, Tiago (External)
Sent: Wednesday, January 18, 2012 9:27 AM
To: ADSM-L@VM.MARIST.EDU
Subject: LTO4 Tape Volumes with diferent Estimated Capacity
Hello
I have several tape volumes (LTO4) with different Estimated Capacity.
What can cause this situation?
Ex
When the tape is "Filling" , it will use the value in the device class
for estimated capacity.
Once the tape is marked Full, it will change to the actual amount of data
on the tape (before compression) since it doesn't need to estimate anymore
The different numbers are the resul
Seems like a case of over-optimism. :-)
LTO4 physical capacity is a maximum of 800 GB. You may not get that or much
more depending upon data compressibility, physical file sizes, and tape block
sizes. You could reduce your Estimated Capacity value if the 1.0 T results in
annoying reporting
Sent: Wednesday, January 18, 2012 9:27 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] LTO4 Tape Volumes with diferent Estimated Capacity
Hello
I have several tape volumes (LTO4) with different Estimated Capacity.
What can cause this situation?
Ex:
A00035L4 WIN_
Hello
I have several tape volumes (LTO4) with different Estimated Capacity.
What can cause this situation?
Ex:
A00035L4 WIN_SRV_T TS3310 629.5 G
95.4 Full
A00039L4 WIN_SRV_T TS3310 1.1 T
98.2
Just analysing our TSM install today as tapes have been getting chewed up quicker then
normal, despite no confuration changes being made at server or client side. We have
client-side compression turned on (hardware off) and we were getting about 140-180Gb
of data on each tape before they being m
Thanks to all for the comments and advice ..
Regards
Robert Ouzen
age-
From: Robert Ouzen [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 22, 2004 11:46 AM
To: [EMAIL PROTECTED]
Subject: Cartridge Estimated capacity
Hi to all
Can anybody tell me why the huge difference between the numbers of
Estimated Capacity of a full cartidge DLT8000 (40/80 G). The form
e see this or comment.
Tks
Charlie H
Tecsys Inc.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
David Longo
Sent: Thursday, January 22, 2004 11:56 AM
To: [EMAIL PROTECTED]
Subject: Re: Cartridge Estimated capacity
Relatively simple. The "EST C
4 16:46
To: [EMAIL PROTECTED]
Subject: Cartridge Estimated capacity
Hi to all
Can anybody tell me why the huge difference between the numbers of
Estimated Capacity of a full cartidge DLT8000 (40/80 G). The format of the
devclass was configure to DRIVE.
The nodes are backup without compression .
ence between the numbers of
Estimated Capacity of a full cartidge DLT8000 (40/80 G). The format of the
devclass was configure to DRIVE.
The nodes are backup without compression .
Here the output of the q vol.
Volume Name Storage Device EstimatedPct Volume
Hi to all
Can anybody tell me why the huge difference between the numbers of
Estimated Capacity of a full cartidge DLT8000 (40/80 G). The format of the
devclass was configure to DRIVE.
The nodes are backup without compression .
Here the output of the q vol.
Volume Name Storage
Wolfgang,
The Estimated capacity of 3590 Cartridges depends on the following:
Are you using 3590J or 3590K cartridges (K has factor 2 more capacity)
Are you using B of E drives (128 or 256 tracks, E drives have also factor 2
more capacity)
Do you use compression (factor 3 more capacity if you
Hi *SM'ers,
I have one Question about the estimated capacity for deviceclass definition.
TSM V4 R1 on OS390 2.8 with 3494 tapelibrary and 3590 Magstar Cartridge.
As far as I know the normal capacity of one 3590 Magstar cratridge is 10 GB. With
compaction the capacity is 30 GB.
The compa
To the best of my knowlege it will. Estimated capasity is only used
untill the tape is filled the first time so that you can get a estimate of
the storage pools capacity. (number of volumes x estimated capacity per
volume = estimated capacity of the storage pool)
Actual capacity is a function
3590DEV2 35,803.7 98.6
Filling
The estimated capacity for the devclass is 30 gig, the tape is still
filling, but showing a % utilized of 98.6. I thought that it should show
100% utilized as soon as it reached the estimated capacity, but still be
'filling' until it reached the end of th
Yes :-)
The estimated capacity is set per devclass and is just an indication of
what you expect for tapes/volumes used in that devclass. This then gets
used to 'estimate' the % utilized per volume and to reflect the total size
of a storage pool (based on the number of scratch tapes t
If you set the estimated capacity at some number, will it fill the tape
beyond that capacity? I am under the impression that it won't.
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (240) 539-7175
Email: [EMAIL PROTECTE
Don't do anything. As long as you don't define an estimated capacity TSM
will use the whole tape. Your capacity stuff looks a little funny, but over
time, as more and more tapes become full, the estimated capacity on the pool
(not each tape) will increase. I think you will probably
> adsm> upd devclass 3590tape format=3590E-C
> > adsm> del drive 3494lib tapedrive1
> > adsm> def drive 3494lib tapedrive1 device=/dev/rmt1
> >
> > The old 3590-J tapes are now showing an Estimated Capacity of 20GB. However,
> > the new 3590-K tapes also show
ing to redefine the drives:
>
> rmdev -l rmt1 -d
> cfgmgr
> adsm> upd devclass 3590tape format=3590E-C
> adsm> del drive 3494lib tapedrive1
> adsm> def drive 3494lib tapedrive1 device=/dev/rmt1
>
> The old 3590-J tapes are now showing an Estimated Capacity of 20G
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Eliza Lau
> Sent: Monday, December 18, 2000 14:45
> To: [EMAIL PROTECTED]
> Subject: Estimated Capacity of 3590-K tapes
>
>
> Hi All,
>
> We just upgraded all the 3590B1A d
def drive 3494lib tapedrive1 device=/dev/rmt1
The old 3590-J tapes are now showing an Estimated Capacity of 20GB. However,
the new 3590-K tapes also show an Estimated Capacity of 20GB. Since the
K tapes have twice as much tape as the J tapes, they should be 40GB.
What do I need to do to make th
On Tue, 7 Nov 2000, Jacques Butcher wrote:
> Can anyone tell me what the estimated capacity (estcap parameter on the
> device class level) of an IBM 3570 library with two 3570E drives on an
> AS/400 should be?
I think you probably mean 3570-C drives? Actually, the difference between
3
Can anyone tell me what the estimated capacity (estcap parameter on the
device class level) of an IBM 3570 library with two 3570E drives on an
AS/400 should be?
30 matches
Mail list logo
