Re: 3590 tape compress question

2000-10-24 Thread Andy Raibeck 

When client compression is turned on, the data is already
arriving to the TSM server in a compressed state. The 3590
may indeed be trying to compress this data again, but
compressed data does not compress very well, so this is why
you see the misleading utilization.

Keep in mind though, that the data is *still* compressed.
It's just a matter of who is doing the compression (software
or hardware). The 40 - 50 GB on cartridge that you were seeing
may very well represent 100 or more GB of uncompressed data.
So your cartridge that shows 50 GB used is still actually
housing 100 GB. So either way, you are getting the benefits of
compression.

Now the question becomes who you want to do the compression.
Choosing to use or not use client compression can have an
impact on your entire network. In general, client compression
requires more overhead on the client system, but can help save
on network bandwidth... but you may get misleading stats on
your tape utilization. It's a matter of understanding that the
40 - 50 GB you see on the tape represents 100 GB or more of
real client data. And don't forget to test restore performance,
because restores may be slower if the client has to decompress
the data before putting it back to disk.

On the other hand, if network bandwidth is not an issue, then
let the hardware do the work of compression.

I am sure others can convey their experiences with client vs.
hardware compression. My main point is that just because you
see lower cartridge utilization does not necessarily mean you
are not gaining the benefits of compression; it's just a matter
of where the compression is happening. Also, and perhaps more
important, is to understand the potential impact to your
network of turning client compression on or off.

Regards,

Andy

Andy Raibeck
IBM/Tivoli
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."

This is an update to a post I made some 10 days ago. I was looking for 3590
extended length cartridges to show capacity numbers indicating decent
compression was going on. ...

What I found was a ClientOptionSet that indicated Compression=Yes.
Therefore, the data I was receiving was already compressed and TSM could not
store more than 40-50GB on a cartridge. I turned this option off and voila!
This morning I have a cartridge that shows a capacity of 107GB. Decent
compression indeed!!!

Thanks to all who responded,
John Talafous
Information Systems Technical Principal
Global Software Support - Data Management
telephone:  (330)-471-3390
e-mail:   [EMAIL PROTECTED]
http://www.ctnvm.inside.tkr/~talafous/
http://www.cis.corp.inside.tkr/networkstorage/

Re: 3590 tape compress question

2000-10-13 Thread Phillip Guan 

Hi Tom and all,

Our AIX is 4.3.3.0 and TSM server is 3.7.3.0.
I have concerned about changing the tape device format setting, does anybody
have such experience?
Appreciated your help!

Thanks,
Phillip

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Tom Melton
Sent: Thursday, October 12, 2000 7:49 PM
To: [EMAIL PROTECTED]
Subject: Re: 3590 tape compress question


DRIVE is supposed to work the same as 3590E-C  (I said below 3590-C, but
3590E-C is the correct value).

What level of ADSM are you using?  I think it was 3.1.2.30 or .40 that
added support for the 3590E drives.

-Tom

 [EMAIL PROTECTED] 10/12/00 07:52PM 
Hi Tom and all,

Cool! I'll change it to get big capacity.
What will happen if I change the setting? It is a production system and
have
about 1TB data on it.

Thanks,
Phillip

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf
Of
Tom Melton
Sent: Thursday, October 12, 2000 6:32 PM
To: [EMAIL PROTECTED]
Subject: Re: 3590 tape compress question


Hi Phillip (and all),

We use 3590E model drives in a 3494 ATL, and the vollowing is a Q VOL
from my system:


ANS8000I Server command: 'q vol stgpool=off2'

Volume Name   Storage  Device  EstimatedPct
Volume
  Pool NameClass Name   Capacity   Util
Status
(MB)
  ---  --  -  -

A00049OFF2 3590E-25630,933.1   88.1
Filling
A00056OFF2 3590E-25692,626.5   49.9
Full
A00060OFF2 3590E-256 0.00.0
Empty
A00061OFF2 3590E-25680,586.3   48.3
Full
A00062OFF2 3590E-25640,597.2   72.3
Full
A00125OFF2 3590E-256 0.00.0
Empty
A00126OFF2 3590E-256   116,093.3   96.4
Full
A00127OFF2 3590E-25664,248.3   88.3
Full
A00129OFF2 3590E-25648,621.5   81.1
Full
A00131OFF2 3590E-25642,052.1   79.6
Full
A00132OFF2 3590E-25666,512.8   75.5
Filling
A00133OFF2 3590E-25620,000.0   44.6
Filling
A00134OFF2 3590E-25684,387.7   72.2
Full
A00139OFF2 3590E-256   143,692.8  100.0
Full
A00142OFF2 3590E-25626,646.1   99.7
Filling
A00143OFF2 3590E-25620,000.0   40.2
Filling


We use the following definition for the device class:

ANS8000I Server command: 'q devclass 3590*'

Device   DeviceStorageDevice   Format Est/Max
  Mount
ClassAccess   PoolType   Capacity
  Limit
Name StrategyCount   (MB)
---------
 --
3590E-256Sequential  53590 3590E- 0.0
 DRIVES
-C

So instead of "DRIVE" I specified 3590-C and as you can see, one tape
above has 143 GB (compressed) data on it.

Tom Melton
Emory University
Emory HealthCare

 [EMAIL PROTECTED] 10/12/00 02:10PM 
Hi all,

We have a 3494 tape library installed with 2 3590 tape drivers. We use
40GB
tape cartridges ( compressed to 120GB). Here is the info:

tsm: q dev

DeviceDevice Storage DeviceFormat
Est/Max
Mount
Class AccessPool Type
Capacity
Limit
Name  Strategy Count
(MB)
- -- --- - --

   --
DISK  Random   3
IBM3494D- Sequential   2 3590  DRIVE
0.0
DRIVES
 EV

tsm: q vol

Volume Name  Storage Device Estimated
Pct  Volume
 Pool Name   Class Name  Capacity
Util  Status
 (MB)
 --- -- -
  --
--- 
/tsm/data1/tsmdata.001   BACKUPPOOL  DISK15,360.0
69.4 On-Line
/tsm/data1/tsmdata.002   BACKUPPOOL  DISK15,360.0
59.7 On-Line
/tsm/data1/tsmdata.003   BACKUPPOOL  DISK15,360.0
55.7 On-Line
/tsm/data1/tsmdata.004   BACKUPPOOL  DISK15,360.0
68.7 On-Line
/tsm/data1/tsmdata.005   BACKUPPOOL  DISK15,360.0
62.4 On-Line
/tsm/data1/tsmdata.006   BACKUPPOOL  DISK15,360.0
69.1 On-Line
/tsm/data1/tsmdata.007   BACKUPPOOL  DISK15,360.0
65.5 On-Line
/tsm/data1/tsmdata.008   BACKUPPOOL  DISK15,

Re: 3590 tape compress question

2000-10-13 Thread Talafous, John G. 

We have a 3466-C00, AIX 4.3.2 and TSM 3.7.1. We have a 3494 library with
3590E1A drives with extended length capability. I changed the DEVCLASS for
the tapes to 3590E-C. I then performed an EXPIRE INVENTORY and lowered
reclamation thresholds   The first scratch tape mounted for reclamation
just reached EOV. After dismounting, I queried the tape with these results:


tsm: FSPHNSM1q volume k20511 f=d

   Volume Name: K20511
 Storage Pool Name: SERVER_COPY
 Device Class Name: 3590-E1A
   Estimated Capacity (MB): 38,756.9
  Pct Util: 100.0
 Volume Status: Full
Access: Read/Write
Pct. Reclaimable Space: 0.0
   Scratch Volume?: Yes
   In Error State?: No
  Number of Writable Sides: 1
   Number of Times Mounted: 1
 Write Pass Number: 1
 Approx. Date Last Written: 10/13/2000 12:01:10
Approx. Date Last Read: 10/13/2000 10:30:17
   Date Became Pending:
Number of Write Errors: 0
 Number of Read Errors: 0
   Volume Location:
Last Update by (administrator):
 Last Update Date/Time: 10/13/2000 10:30:02

more...   (ENTER to continue, 'C' to cancel)

I may be dealing with the wrong type of data, but I see no compression here.
I guess if I don't see any compression results this weekend, it's time to
call support. Any other ideas?

John G. Talafous  IS Technical Principal
The Timken CompanyPhone: (330)-471-3390
P.O. Box 6927 Fax  : (330)-471-4034
1835 Dueber Ave. S.W.
Canton, Ohio USA  44706-0927
[EMAIL PROTECTED]  http://www.timken.com/

-Original Message-
From: Phillip Guan [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 13, 2000 11:54 AM
To: [EMAIL PROTECTED]
Subject: Re: 3590 tape compress question


Hi Tom and all,

Our AIX is 4.3.3.0 and TSM server is 3.7.3.0.
I have concerned about changing the tape device format setting, does anybody
have such experience?
Appreciated your help!

Thanks,
Phillip

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Tom Melton
Sent: Thursday, October 12, 2000 7:49 PM
To: [EMAIL PROTECTED]
Subject: Re: 3590 tape compress question


DRIVE is supposed to work the same as 3590E-C  (I said below 3590-C, but
3590E-C is the correct value).

What level of ADSM are you using?  I think it was 3.1.2.30 or .40 that
added support for the 3590E drives.

-Tom

 [EMAIL PROTECTED] 10/12/00 07:52PM 
Hi Tom and all,

Cool! I'll change it to get big capacity.
What will happen if I change the setting? It is a production system and
have
about 1TB data on it.

Thanks,
Phillip

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf
Of
Tom Melton
Sent: Thursday, October 12, 2000 6:32 PM
To: [EMAIL PROTECTED]
Subject: Re: 3590 tape compress question


Hi Phillip (and all),

We use 3590E model drives in a 3494 ATL, and the vollowing is a Q VOL
from my system:


ANS8000I Server command: 'q vol stgpool=off2'

Volume Name   Storage  Device  EstimatedPct
Volume
  Pool NameClass Name   Capacity   Util
Status
(MB)
  ---  --  -  -

A00049OFF2 3590E-25630,933.1   88.1
Filling
A00056OFF2 3590E-25692,626.5   49.9
Full
A00060OFF2 3590E-256 0.00.0
Empty
A00061OFF2 3590E-25680,586.3   48.3
Full
A00062OFF2 3590E-25640,597.2   72.3
Full
A00125OFF2 3590E-256 0.00.0
Empty
A00126OFF2 3590E-256   116,093.3   96.4
Full
A00127OFF2 3590E-25664,248.3   88.3
Full
A00129OFF2 3590E-25648,621.5   81.1
Full
A00131OFF2 3590E-25642,052.1   79.6
Full
A00132OFF2 3590E-25666,512.8   75.5
Filling
A00133OFF2 3590E-25620,000.0   44.6
Filling
A00134OFF2 3590E-25684,387.7   72.2
Full
A00139OFF2 3590E-256   143,692.8  100.0
Full
A00142OFF2 3590E-25626,646.1   99.7
Filling
A00143OFF2 3590E-25620,000.0   40.2
Filling


We use the following definition for the device class:

ANS8000I Server command: 'q devclass 3590*'

Device   DeviceStorageDevice   Format Est/Max
  Mount
ClassAccess   PoolType   Capacity
  Limit
Name StrategyCount   (MB)
---------
 --
3590E-256Sequential

3590 tape compress question

2000-10-12 Thread Phillip Guan 

Hi all,

We have a 3494 tape library installed with 2 3590 tape drivers. We use 40GB
tape cartridges ( compressed to 120GB). Here is the info:

tsm: q dev

DeviceDevice Storage DeviceFormat  Est/Max
Mount
Class AccessPool Type Capacity
Limit
Name  Strategy Count  (MB)
- -- --- - -- 
   --
DISK  Random   3
IBM3494D- Sequential   2 3590  DRIVE   0.0
DRIVES
 EV

tsm: q vol

Volume Name  Storage Device Estimated
Pct  Volume
 Pool Name   Class Name  Capacity
Util  Status
 (MB)
 --- -- - --
--- 
/tsm/data1/tsmdata.001   BACKUPPOOL  DISK15,360.0
69.4 On-Line
/tsm/data1/tsmdata.002   BACKUPPOOL  DISK15,360.0
59.7 On-Line
/tsm/data1/tsmdata.003   BACKUPPOOL  DISK15,360.0
55.7 On-Line
/tsm/data1/tsmdata.004   BACKUPPOOL  DISK15,360.0
68.7 On-Line
/tsm/data1/tsmdata.005   BACKUPPOOL  DISK15,360.0
62.4 On-Line
/tsm/data1/tsmdata.006   BACKUPPOOL  DISK15,360.0
69.1 On-Line
/tsm/data1/tsmdata.007   BACKUPPOOL  DISK15,360.0
65.5 On-Line
/tsm/data1/tsmdata.008   BACKUPPOOL  DISK15,360.0
62.5 On-Line
/tsm/data1/tsmdata.009   BACKUPPOOL  DISK15,360.0
59.5 On-Line
/tsm/data1/tsmdata.010   BACKUPPOOL  DISK15,360.0
69.7 On-Line
/tsm/data1/tsmdata.011   BACKUPPOOL  DISK15,360.0
62.5 On-Line
/tsm/data1/tsmdata.012   BACKUPPOOL  DISK15,360.0
70.3 On-Line
/tsm/data1/tsmdata.013   BACKUPPOOL  DISK15,360.0
58.4 On-Line
000503   TAPEPOOLIBM3494DEV  37,084.1
80.9   Full
000504   TAPEPOOLIBM3494DEV  20,000.0
64.9 Filling
000506   RECLAIMPOOL IBM3494DEV  23,361.6
0.0 Filling
000508   TAPEPOOLIBM3494DEV  36,269.8
100.0   Full
000509   TAPEPOOLIBM3494DEV  36,024.0
100.0   Full
000510   TAPEPOOLIBM3494DEV  20,000.0
49.1 Filling
000511   TAPEPOOLIBM3494DEV  20,000.0
54.8 Filling
000512   TAPEPOOLIBM3494DEV  20,000.0
51.7 Filling
000513   TAPEPOOLIBM3494DEV  35,239.2
100.0 Filling
000514   TAPEPOOLIBM3494DEV  35,988.0
100.0   Full
000516   TAPEPOOLIBM3494DEV  35,978.1
100.0   Full
000517   TAPEPOOLIBM3494DEV  35,905.2
100.0   Full
000518   TAPEPOOLIBM3494DEV  36,028.3
100.0   Full
000520   TAPEPOOLIBM3494DEV  20,000.0
47.3 Filling
000521   TAPEPOOLIBM3494DEV  20,000.0
79.2 Filling
000522   TAPEPOOLIBM3494DEV  20,000.0
58.7 Filling
000523   TAPEPOOLIBM3494DEV  20,000.0
36.1 Filling
000526   TAPEPOOLIBM3494DEV  20,000.0
47.7 Filling
000527   TAPEPOOLIBM3494DEV  20,000.0
83.0 Filling
000528   TAPEPOOLIBM3494DEV  20,000.0
41.0 Filling
000529   TAPEPOOLIBM3494DEV  20,000.0
34.3 Filling

Question: We set the device fromat to be 'DRIVE' which means use the highest
format that it supports, does it mean it uses HW compress? Form the 'q vol'
output, it seems it uses as 40GB. How do we 'turn on' the HW compress if it
is not compressed? Thanks in advance for your help.

Best regards,
Phillip Guan

Re: 3590 tape compress question

2000-10-12 Thread Phillip Guan 

Hi Maria/Richard,

No, we didn't turned on compress on the client. Thanks for the info.

Phillip

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Maria Paz Gimeno
Sent: Thursday, October 12, 2000 1:43 PM
To: [EMAIL PROTECTED]
Subject: RV: 3590 tape compress question


Do you have compresion turned on in the client?
In that case the hardware can not compress more.
Regards
Maria

Re: 3590 tape compress question

2000-10-12 Thread Tom Melton 

Hi Phillip (and all),

We use 3590E model drives in a 3494 ATL, and the vollowing is a Q VOL
from my system:


ANS8000I Server command: 'q vol stgpool=off2'

Volume Name   Storage  Device  EstimatedPct
Volume
  Pool NameClass Name   Capacity   Util
Status
(MB)
  ---  --  -  -

A00049OFF2 3590E-25630,933.1   88.1
Filling
A00056OFF2 3590E-25692,626.5   49.9
Full
A00060OFF2 3590E-256 0.00.0
Empty
A00061OFF2 3590E-25680,586.3   48.3
Full
A00062OFF2 3590E-25640,597.2   72.3
Full
A00125OFF2 3590E-256 0.00.0
Empty
A00126OFF2 3590E-256   116,093.3   96.4
Full
A00127OFF2 3590E-25664,248.3   88.3
Full
A00129OFF2 3590E-25648,621.5   81.1
Full
A00131OFF2 3590E-25642,052.1   79.6
Full
A00132OFF2 3590E-25666,512.8   75.5
Filling
A00133OFF2 3590E-25620,000.0   44.6
Filling
A00134OFF2 3590E-25684,387.7   72.2
Full
A00139OFF2 3590E-256   143,692.8  100.0
Full
A00142OFF2 3590E-25626,646.1   99.7
Filling
A00143OFF2 3590E-25620,000.0   40.2
Filling


We use the following definition for the device class:

ANS8000I Server command: 'q devclass 3590*'

Device   DeviceStorageDevice   Format Est/Max
  Mount
ClassAccess   PoolType   Capacity
  Limit
Name StrategyCount   (MB)
---------
 --
3590E-256Sequential  53590 3590E- 0.0
 DRIVES
-C

So instead of "DRIVE" I specified 3590-C and as you can see, one tape
above has 143 GB (compressed) data on it.

Tom Melton
Emory University
Emory HealthCare

 [EMAIL PROTECTED] 10/12/00 02:10PM 
Hi all,

We have a 3494 tape library installed with 2 3590 tape drivers. We use
40GB
tape cartridges ( compressed to 120GB). Here is the info:

tsm: q dev

DeviceDevice Storage DeviceFormat
Est/Max
Mount
Class AccessPool Type
Capacity
Limit
Name  Strategy Count
(MB)
- -- --- - --

   --
DISK  Random   3
IBM3494D- Sequential   2 3590  DRIVE
0.0
DRIVES
 EV

tsm: q vol

Volume Name  Storage Device Estimated
Pct  Volume
 Pool Name   Class Name  Capacity
Util  Status
 (MB)
 --- -- -
  --
--- 
/tsm/data1/tsmdata.001   BACKUPPOOL  DISK15,360.0
69.4 On-Line
/tsm/data1/tsmdata.002   BACKUPPOOL  DISK15,360.0
59.7 On-Line
/tsm/data1/tsmdata.003   BACKUPPOOL  DISK15,360.0
55.7 On-Line
/tsm/data1/tsmdata.004   BACKUPPOOL  DISK15,360.0
68.7 On-Line
/tsm/data1/tsmdata.005   BACKUPPOOL  DISK15,360.0
62.4 On-Line
/tsm/data1/tsmdata.006   BACKUPPOOL  DISK15,360.0
69.1 On-Line
/tsm/data1/tsmdata.007   BACKUPPOOL  DISK15,360.0
65.5 On-Line
/tsm/data1/tsmdata.008   BACKUPPOOL  DISK15,360.0
62.5 On-Line
/tsm/data1/tsmdata.009   BACKUPPOOL  DISK15,360.0
59.5 On-Line
/tsm/data1/tsmdata.010   BACKUPPOOL  DISK15,360.0
69.7 On-Line
/tsm/data1/tsmdata.011   BACKUPPOOL  DISK15,360.0
62.5 On-Line
/tsm/data1/tsmdata.012   BACKUPPOOL  DISK15,360.0
70.3 On-Line
/tsm/data1/tsmdata.013   BACKUPPOOL  DISK15,360.0
58.4 On-Line
000503   TAPEPOOLIBM3494DEV  37,084.1
80.9   Full
000504   TAPEPOOLIBM3494DEV  20,000.0
64.9 Filling
000506   RECLAIMPOOL IBM3494DEV  23,361.6
0.0 Filling
000508   TAPEPOOLIBM3494DEV  36,269.8
100.0   Full
000509   TAPEPOOLIBM3494DEV  36,024.0
100.0   Full
000510   TAPEPOOLIBM3494DEV  20,000.0
49.1 Filling
000511   TAPEPOOLIBM3494DEV  20,000.0
54.8 Filling
000512

Re: 3590 tape compress question

2000-10-12 Thread Phillip Guan 

Hi Tom and all,

Cool! I'll change it to get big capacity.
What will happen if I change the setting? It is a production system and have
about 1TB data on it.

Thanks,
Phillip

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Tom Melton
Sent: Thursday, October 12, 2000 6:32 PM
To: [EMAIL PROTECTED]
Subject: Re: 3590 tape compress question


Hi Phillip (and all),

We use 3590E model drives in a 3494 ATL, and the vollowing is a Q VOL
from my system:


ANS8000I Server command: 'q vol stgpool=off2'

Volume Name   Storage  Device  EstimatedPct
Volume
  Pool NameClass Name   Capacity   Util
Status
(MB)
  ---  --  -  -

A00049OFF2 3590E-25630,933.1   88.1
Filling
A00056OFF2 3590E-25692,626.5   49.9
Full
A00060OFF2 3590E-256 0.00.0
Empty
A00061OFF2 3590E-25680,586.3   48.3
Full
A00062OFF2 3590E-25640,597.2   72.3
Full
A00125OFF2 3590E-256 0.00.0
Empty
A00126OFF2 3590E-256   116,093.3   96.4
Full
A00127OFF2 3590E-25664,248.3   88.3
Full
A00129OFF2 3590E-25648,621.5   81.1
Full
A00131OFF2 3590E-25642,052.1   79.6
Full
A00132OFF2 3590E-25666,512.8   75.5
Filling
A00133OFF2 3590E-25620,000.0   44.6
Filling
A00134OFF2 3590E-25684,387.7   72.2
Full
A00139OFF2 3590E-256   143,692.8  100.0
Full
A00142OFF2 3590E-25626,646.1   99.7
Filling
A00143OFF2 3590E-25620,000.0   40.2
Filling


We use the following definition for the device class:

ANS8000I Server command: 'q devclass 3590*'

Device   DeviceStorageDevice   Format Est/Max
  Mount
ClassAccess   PoolType   Capacity
  Limit
Name StrategyCount   (MB)
---------
 --
3590E-256Sequential  53590 3590E- 0.0
 DRIVES
-C

So instead of "DRIVE" I specified 3590-C and as you can see, one tape
above has 143 GB (compressed) data on it.

Tom Melton
Emory University
Emory HealthCare

 [EMAIL PROTECTED] 10/12/00 02:10PM 
Hi all,

We have a 3494 tape library installed with 2 3590 tape drivers. We use
40GB
tape cartridges ( compressed to 120GB). Here is the info:

tsm: q dev

DeviceDevice Storage DeviceFormat
Est/Max
Mount
Class AccessPool Type
Capacity
Limit
Name  Strategy Count
(MB)
- -- --- - --

   --
DISK  Random   3
IBM3494D- Sequential   2 3590  DRIVE
0.0
DRIVES
 EV

tsm: q vol

Volume Name  Storage Device Estimated
Pct  Volume
 Pool Name   Class Name  Capacity
Util  Status
 (MB)
 --- -- -
  --
--- 
/tsm/data1/tsmdata.001   BACKUPPOOL  DISK15,360.0
69.4 On-Line
/tsm/data1/tsmdata.002   BACKUPPOOL  DISK15,360.0
59.7 On-Line
/tsm/data1/tsmdata.003   BACKUPPOOL  DISK15,360.0
55.7 On-Line
/tsm/data1/tsmdata.004   BACKUPPOOL  DISK15,360.0
68.7 On-Line
/tsm/data1/tsmdata.005   BACKUPPOOL  DISK15,360.0
62.4 On-Line
/tsm/data1/tsmdata.006   BACKUPPOOL  DISK15,360.0
69.1 On-Line
/tsm/data1/tsmdata.007   BACKUPPOOL  DISK15,360.0
65.5 On-Line
/tsm/data1/tsmdata.008   BACKUPPOOL  DISK15,360.0
62.5 On-Line
/tsm/data1/tsmdata.009   BACKUPPOOL  DISK15,360.0
59.5 On-Line
/tsm/data1/tsmdata.010   BACKUPPOOL  DISK15,360.0
69.7 On-Line
/tsm/data1/tsmdata.011   BACKUPPOOL  DISK15,360.0
62.5 On-Line
/tsm/data1/tsmdata.012   BACKUPPOOL  DISK15,360.0
70.3 On-Line
/tsm/data1/tsmdata.013   BACKUPPOOL  DISK15,360.0
58.4 On-Line
000503   TAPEPOOLIBM3494DEV  37,084.1
80.9   Full
000504   TAPEPOOLIBM3494DEV  20,000.0
64.9 Filling
000506   RECLAIMPOOL

Re: 3590 tape compress question

2000-10-12 Thread Tom Melton 

DRIVE is supposed to work the same as 3590E-C  (I said below 3590-C, but
3590E-C is the correct value).

What level of ADSM are you using?  I think it was 3.1.2.30 or .40 that
added support for the 3590E drives.

-Tom

 [EMAIL PROTECTED] 10/12/00 07:52PM 
Hi Tom and all,

Cool! I'll change it to get big capacity.
What will happen if I change the setting? It is a production system and
have
about 1TB data on it.

Thanks,
Phillip

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf
Of
Tom Melton
Sent: Thursday, October 12, 2000 6:32 PM
To: [EMAIL PROTECTED]
Subject: Re: 3590 tape compress question


Hi Phillip (and all),

We use 3590E model drives in a 3494 ATL, and the vollowing is a Q VOL
from my system:


ANS8000I Server command: 'q vol stgpool=off2'

Volume Name   Storage  Device  EstimatedPct
Volume
  Pool NameClass Name   Capacity   Util
Status
(MB)
  ---  --  -  -

A00049OFF2 3590E-25630,933.1   88.1
Filling
A00056OFF2 3590E-25692,626.5   49.9
Full
A00060OFF2 3590E-256 0.00.0
Empty
A00061OFF2 3590E-25680,586.3   48.3
Full
A00062OFF2 3590E-25640,597.2   72.3
Full
A00125OFF2 3590E-256 0.00.0
Empty
A00126OFF2 3590E-256   116,093.3   96.4
Full
A00127OFF2 3590E-25664,248.3   88.3
Full
A00129OFF2 3590E-25648,621.5   81.1
Full
A00131OFF2 3590E-25642,052.1   79.6
Full
A00132OFF2 3590E-25666,512.8   75.5
Filling
A00133OFF2 3590E-25620,000.0   44.6
Filling
A00134OFF2 3590E-25684,387.7   72.2
Full
A00139OFF2 3590E-256   143,692.8  100.0
Full
A00142OFF2 3590E-25626,646.1   99.7
Filling
A00143OFF2 3590E-25620,000.0   40.2
Filling


We use the following definition for the device class:

ANS8000I Server command: 'q devclass 3590*'

Device   DeviceStorageDevice   Format Est/Max
  Mount
ClassAccess   PoolType   Capacity
  Limit
Name StrategyCount   (MB)
---------
 --
3590E-256Sequential  53590 3590E- 0.0
 DRIVES
-C

So instead of "DRIVE" I specified 3590-C and as you can see, one tape
above has 143 GB (compressed) data on it.

Tom Melton
Emory University
Emory HealthCare

 [EMAIL PROTECTED] 10/12/00 02:10PM 
Hi all,

We have a 3494 tape library installed with 2 3590 tape drivers. We use
40GB
tape cartridges ( compressed to 120GB). Here is the info:

tsm: q dev

DeviceDevice Storage DeviceFormat
Est/Max
Mount
Class AccessPool Type
Capacity
Limit
Name  Strategy Count
(MB)
- -- --- - --

   --
DISK  Random   3
IBM3494D- Sequential   2 3590  DRIVE
0.0
DRIVES
 EV

tsm: q vol

Volume Name  Storage Device Estimated
Pct  Volume
 Pool Name   Class Name  Capacity
Util  Status
 (MB)
 --- -- -
  --
--- 
/tsm/data1/tsmdata.001   BACKUPPOOL  DISK15,360.0
69.4 On-Line
/tsm/data1/tsmdata.002   BACKUPPOOL  DISK15,360.0
59.7 On-Line
/tsm/data1/tsmdata.003   BACKUPPOOL  DISK15,360.0
55.7 On-Line
/tsm/data1/tsmdata.004   BACKUPPOOL  DISK15,360.0
68.7 On-Line
/tsm/data1/tsmdata.005   BACKUPPOOL  DISK15,360.0
62.4 On-Line
/tsm/data1/tsmdata.006   BACKUPPOOL  DISK15,360.0
69.1 On-Line
/tsm/data1/tsmdata.007   BACKUPPOOL  DISK15,360.0
65.5 On-Line
/tsm/data1/tsmdata.008   BACKUPPOOL  DISK15,360.0
62.5 On-Line
/tsm/data1/tsmdata.009   BACKUPPOOL  DISK15,360.0
59.5 On-Line
/tsm/data1/tsmdata.010   BACKUPPOOL  DISK15,360.0
69.7 On-Line
/tsm/data1/tsmdata.011   BACKUPPOOL  DISK15,360.0
62.5 On-Line
/tsm/data1/tsmdata.012   BACKUPPOOL  DISK15,360.0
70.3 On-Line
/tsm/data1/tsmdata.013   BACKUPPOOL