Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+LTO4\s+and\s+compression\s*$/: 8 ]

Total 8 documents matching your query.

1. [ADSM-L] LTO4 and compression (score: 1)
Author: Lars-Erik Öhman <larsa.ohman AT CARNEGIE DOT SE>
Date: Thu, 27 Aug 2009 12:24:54 +0200
Where do I enable compression for LTO4 tapes/drives in a 3584 library? The tapes only fill up to 800 GB. A00000L4 TAPEPOOL1 LTO4CLASS 771.2 G 98.4 Full A00001L4 TAPEPOOL1 LTO4CLASS 783.7 G 96.6 Full
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-08/msg00317.html (13,395 bytes)

2. Re: [ADSM-L] LTO4 and compression (score: 1)
Author: Stefan Folkerts <stefan.folkerts AT ITAA DOT NL>
Date: Thu, 27 Aug 2009 12:29:17 +0200
You do this in the device class, the format option can be set to ULTRIUM4C to force compression. --Oorspronkelijk bericht-- Van: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Namens La
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-08/msg00318.html (13,741 bytes)

3. Re: [ADSM-L] LTO4 and compression (score: 1)
Author: David McClelland <david.mcclelland AT NETWORKC.CO DOT UK>
Date: Thu, 27 Aug 2009 11:30:05 +0100
What are your device class settings for the 'LTO4CLASS' device class? `q devcl LTO4CLASS f=d` might show that your device class configuration isn't enabling compression at the moment. It also depends
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-08/msg00319.html (14,094 bytes)

4. Re: [ADSM-L] LTO4 and compression (score: 1)
Author: "Bos, Karel" <Karel.Bos AT ATOSORIGIN DOT COM>
Date: Thu, 27 Aug 2009 12:32:37 +0200
Hi, Its on you device class definitions. Device Class Name: LTO_PRIM Device Type: LTO Format: DRIVE You can change the default from "drive" to ultrium 4c for forced compression. This will only help i
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-08/msg00320.html (15,187 bytes)

5. Re: [ADSM-L] LTO4 and compression (score: 1)
Author: Lars-Erik Öhman <larsa.ohman AT CARNEGIE DOT SE>
Date: Thu, 27 Aug 2009 12:35:01 +0200
Thanks all. It was set to ULTRIUM4 and not ULTRIUM4C. Hi, Its on you device class definitions. Device Class Name: LTO_PRIM Device Type: LTO Format: DRIVE You can change the default from "drive" to ul
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-08/msg00321.html (16,100 bytes)

6. Re: [ADSM-L] LTO4 and compression (score: 1)
Author: Lars-Erik Öhman <larsa.ohman AT CARNEGIE DOT SE>
Date: Thu, 27 Aug 2009 12:42:49 +0200
What is the best to use, ULTRIUM4C or DRIVE? Hi, Its on you device class definitions. Device Class Name: LTO_PRIM Device Type: LTO Format: DRIVE You can change the default from "drive" to ultrium 4c
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-08/msg00322.html (16,101 bytes)

7. Re: [ADSM-L] LTO4 and compression (score: 1)
Author: Steven Langdale <Steven.Langdale AT CAT DOT COM>
Date: Thu, 27 Aug 2009 11:50:29 +0100
FWIW on my TSM servers they are all set to "DRIVE" Steven Langdale Global Information Services EAME SAN/Storage Planning and Implementation ( Phone : +44 (0)1733 584175 ( Mob: +44 (0)7876 216782 ü Co
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-08/msg00323.html (16,618 bytes)

8. Re: [ADSM-L] LTO4 and compression (score: 1)
Author: Richard Sims <rbs AT BU DOT EDU>
Date: Thu, 27 Aug 2009 06:52:41 -0400
What is the best to use, ULTRIUM4C or DRIVE? In computer work, the more explicit you are to the system as to what you want, the more likely you are to get it. There have been IBM advisories in the p
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-08/msg00324.html (11,920 bytes)


This search system is powered by Namazu