SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
LTO4 Tape Volumes with diferent Estimated Capacity
Author Message
Post 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_SRV_T TS3310 629.5 G
95.4 Full

A00039L4 WIN_SRV_T TS3310 1.1 T
98.2 Full

A00101L4 WIN_SRV_T TS3310 884.8 G
84.4 Full

A00113L4 WIN_SRV_T TS3310 1.0 T
93.7 Full

A00118L4 WIN_SRV_T TS3310 1.0 T
73.6 Full

A00128L4 WIN_SRV_T TS3310 1.0 T
99.2 Full

A00129L4 WIN_SRV_T TS3310 969.1 G
93.7 Full

A00133L4 WIN_SRV_T TS3310 934.8 G
96.1 Full





All tapes and Drives are LTO4, TSM Server 553 for AIX.



The devc are configured as:



Device Class Name: TS3310

Device Access Strategy: Sequential

Storage Pool Count: 16

Device Type: LTO

Format: ULTRIUM4C

Est/Max Capacity (MB):

Mount Limit: DRIVES

Mount Wait (min): 60

Mount Retention (min): 60

Label Prefix: ADSM

Library: TS3310

Directory:

Server Name:

Retry Period:

Retry Interval:

Shared:

High-level Address:

Minimum Capacity:

WORM: No

Drive Encryption: Off

Scaled Capacity:

Last Update by (administrator): ADM

Last Update Date/Time: 07/27/09 17:32:05



Cumprimentos / Best regards

Tiago Botelho

Post LTO4 Tape Volumes with diferent Estimated Capacity 
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 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 Full

A00101L4 WIN_SRV_T TS3310 884.8 G
84.4 Full

A00113L4 WIN_SRV_T TS3310 1.0 T
93.7 Full

A00118L4 WIN_SRV_T TS3310 1.0 T
73.6 Full

A00128L4 WIN_SRV_T TS3310 1.0 T
99.2 Full

A00129L4 WIN_SRV_T TS3310 969.1 G
93.7 Full

A00133L4 WIN_SRV_T TS3310 934.8 G
96.1 Full





All tapes and Drives are LTO4, TSM Server 553 for AIX.



The devc are configured as:



Device Class Name: TS3310

Device Access Strategy: Sequential

Storage Pool Count: 16

Device Type: LTO

Format: ULTRIUM4C

Est/Max Capacity (MB):

Mount Limit: DRIVES

Mount Wait (min): 60

Mount Retention (min): 60

Label Prefix: ADSM

Library: TS3310

Directory:

Server Name:

Retry Period:

Retry Interval:

Shared:

High-level Address:

Minimum Capacity:

WORM: No

Drive Encryption: Off

Scaled Capacity:

Last Update by (administrator): ADM

Last Update Date/Time: 07/27/09 17:32:05



Cumprimentos / Best regards

Tiago Botelho





--
-- Skylar Thompson (skylar2 < at > u.washington.edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S048, (206)-685-7354
-- University of Washington School of Medicine

Post LTO4 Tape Volumes with diferent Estimated Capacity 
Seems like a case of over-optimism. Smile
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.
The mailing list archives hold past discussions on many topics, where http://adsm.org/forum/showthread.php?16498-ESTIMATED-CAPACITY-OF-LTO4-s is like this one.

Richard Sims

Post LTO4 Tape Volumes with diferent Estimated Capacity 
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 result of some tapes having more
compressible data than the others.

Regards,
Shawn
________________________________________________
Shawn Drew





Internet
Tiago.Botelho < at > VOLKSWAGEN.PT

Sent by: ADSM-L < at > VM.MARIST.EDU
01/18/2012 10:27 AM
Please respond to
ADSM-L < at > VM.MARIST.EDU


To
ADSM-L
cc

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_SRV_T TS3310 629.5 G
95.4 Full

A00039L4 WIN_SRV_T TS3310 1.1 T
98.2 Full

A00101L4 WIN_SRV_T TS3310 884.8 G
84.4 Full

A00113L4 WIN_SRV_T TS3310 1.0 T
93.7 Full

A00118L4 WIN_SRV_T TS3310 1.0 T
73.6 Full

A00128L4 WIN_SRV_T TS3310 1.0 T
99.2 Full

A00129L4 WIN_SRV_T TS3310 969.1 G
93.7 Full

A00133L4 WIN_SRV_T TS3310 934.8 G
96.1 Full





All tapes and Drives are LTO4, TSM Server 553 for AIX.



The devc are configured as:



Device Class Name: TS3310

Device Access Strategy: Sequential

Storage Pool Count: 16

Device Type: LTO

Format: ULTRIUM4C

Est/Max Capacity (MB):

Mount Limit: DRIVES

Mount Wait (min): 60

Mount Retention (min): 60

Label Prefix: ADSM

Library: TS3310

Directory:

Server Name:

Retry Period:

Retry Interval:

Shared:

High-level Address:

Minimum Capacity:

WORM: No

Drive Encryption: Off

Scaled Capacity:

Last Update by (administrator): ADM

Last Update Date/Time: 07/27/09 17:32:05



Cumprimentos / Best regards

Tiago Botelho







This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.

Post 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 / Best regards

Tiago Botelho


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Botelho, Tiago (External)
Sent: quarta-feira, 18 de Janeiro de 2012 15:27
To: ADSM-L < at > 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_SRV_T TS3310 629.5 G
95.4 Full

A00039L4 WIN_SRV_T TS3310 1.1 T
98.2 Full

A00101L4 WIN_SRV_T TS3310 884.8 G
84.4 Full

A00113L4 WIN_SRV_T TS3310 1.0 T
93.7 Full

A00118L4 WIN_SRV_T TS3310 1.0 T
73.6 Full

A00128L4 WIN_SRV_T TS3310 1.0 T
99.2 Full

A00129L4 WIN_SRV_T TS3310 969.1 G
93.7 Full

A00133L4 WIN_SRV_T TS3310 934.8 G
96.1 Full





All tapes and Drives are LTO4, TSM Server 553 for AIX.



The devc are configured as:



Device Class Name: TS3310

Device Access Strategy: Sequential

Storage Pool Count: 16

Device Type: LTO

Format: ULTRIUM4C

Est/Max Capacity (MB):

Mount Limit: DRIVES

Mount Wait (min): 60

Mount Retention (min): 60

Label Prefix: ADSM

Library: TS3310

Directory:

Server Name:

Retry Period:

Retry Interval:

Shared:

High-level Address:

Minimum Capacity:

WORM: No

Drive Encryption: Off

Scaled Capacity:

Last Update by (administrator): ADM

Last Update Date/Time: 07/27/09 17:32:05



Cumprimentos / Best regards

Tiago Botelho

Post LTO4 Tape Volumes with diferent Estimated Capacity 
Tiago,
Generally speaking hardware compression (tape drive) will always yield
better results than software based compression.

I would only use the client compression when bandwidth issues come into
play, like remote offices with limited WAN bandwidth or a slow congested
LAN segment. In these cases compressing at the client would reduce the
data that has to traverse the network.



~Rick

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Botelho, Tiago (External)
Sent: Thursday, January 19, 2012 4:57 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [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 / Best regards

Tiago Botelho


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Botelho, Tiago (External)
Sent: quarta-feira, 18 de Janeiro de 2012 15:27
To: ADSM-L < at > 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_SRV_T TS3310 629.5 G
95.4 Full

A00039L4 WIN_SRV_T TS3310 1.1 T
98.2 Full

A00101L4 WIN_SRV_T TS3310 884.8 G
84.4 Full

A00113L4 WIN_SRV_T TS3310 1.0 T
93.7 Full

A00118L4 WIN_SRV_T TS3310 1.0 T
73.6 Full

A00128L4 WIN_SRV_T TS3310 1.0 T
99.2 Full

A00129L4 WIN_SRV_T TS3310 969.1 G
93.7 Full

A00133L4 WIN_SRV_T TS3310 934.8 G
96.1 Full





All tapes and Drives are LTO4, TSM Server 553 for AIX.



The devc are configured as:



Device Class Name: TS3310

Device Access Strategy: Sequential

Storage Pool Count: 16

Device Type: LTO

Format: ULTRIUM4C

Est/Max Capacity (MB):

Mount Limit: DRIVES

Mount Wait (min): 60

Mount Retention (min): 60

Label Prefix: ADSM

Library: TS3310

Directory:

Server Name:

Retry Period:

Retry Interval:

Shared:

High-level Address:

Minimum Capacity:

WORM: No

Drive Encryption: Off

Scaled Capacity:

Last Update by (administrator): ADM

Last Update Date/Time: 07/27/09 17:32:05



Cumprimentos / Best regards

Tiago Botelho

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB