Super DLT 600 Configuration for IBM Tivoli Storage Manager Server

HP StorageWorks SDLT 600
Quantum SDLT 600 (also with DLTIce)
Sun StorageTek SDLT 600
Tandberg SDLT 600

1. When defining a device class for SDLT 600 drive, use

• devtype=DLT
• format=<DRIVE | SDLT600 | SDLT600C>

Example:

DEFine DEVclass devclassname DEVType= DLT FORMAT= SDLT600 .....
DEFine DEVclass devclassname DEVType= DLT FORMAT= SDLT600C .....

SDLT600 - Specifies that TSM writes data that uses the SDLT600 recording format. This format results in a cartridge capacity of 300GB when using SuperDLTtape-II media.

SDLT600C - Specifies that TSM writes data that uses the SDLT600C recording format with compression. This format results in a cartridge capacity of 600GB when using SuperDLTtape-II media.

2. 300 GB native capacity and approximately 600 GB with 2:1 compression

3. Device identification and firmware level used during validation

HP StorageWorks SDLT 600
Drive ID : HP SDLT600
Firmware : 1919

Quantum SDLT 600
Sun StorageTek SDLT 600
Tandberg SDLT 600
Drive ID : QUANTUM SDLT600
Firmware : 0A0A

4. Supported media

• SuperDLTtape II
• Read comaptible with SuperDLTtape I media
• Read comaptible with DLTtape VS1 media

5. All SDLT 600 drives report drive serial numbers.

6. Starting from TSM 5.3.1, the Host Bus Adapter (HBA) to which SDLT 600 drive is connected must support 16-byte SCSI Command Descriptor Block (CDB). On Solaris, parallel SCSI HBAs do not support 16-byte CDBs. For the Linux platforms, see the following technote for more information.

http://www-1.ibm.com/support/docview.wss?rs=663&uid=swg21239641

---

Quantum SDLT 60 0 with DLTIce

1. DLTIce offers the WORM functionality. With DLTIce, Quantum SDLT600 drives become WORM-capable drives which can be used as Read/Write or WORM drives. To use them as WORM drives, when defining a device class, use WORM=Yes.

Example:
DEFine DEVclass devclassname DEVType=DLT FORMAT=DRIVE WORM=Yes

2. To use Quantum SDLT600 DLTIce WORM-capable drives as Read/Write drives, when defining a device class, do not specify the WORM parameter, or use WORM=No.

Example:
DEFine DEVclass devclassname DEVType=DLT FORMAT=DRIVE WORM=No

3. Users are not required to convert RW media to WORM prior to checking in. The TSM server will convert a scratch RW volume to WORM when it needs to mount a scratch WORM volume and there is no scratch WORM volume in the library inventory.

4. When checking in WORM volumes, use checklabel=yes. Otherwise, they will be checked in as RW volumes.

5. Storage pools assigned to the DLT device class have a default reclamation value of 60. To prevent reclamation of WORM media, set the reclamation value to 100.

6. Quantum SDLT600 DLTIce WORM-capable drives can not be defined for use as WORM drives through the Device Configuration wizard on Windows. The drives will have to be defined through IBM Tivoli Storage Manager commands.

7. Device identification and firmware level used during validation in TSM 5.3.1

Drive ID : Quantum SDLT600
Firmware : 1E1E

8. RW and WORM media can be in the same library. However, 2 device classes--RW and WORM, must be defined. Since Quantum SDLT600 DLTIce RW drives do not recognize WORM media, all drives in the library must be WORM capable if WORM media will be used.

9. The WORM functionality on Quantum SDLT 600 is supported in TSM 5.3.1 and later on HP, Linux and Windows, and in TSM 5.3.2 and later on AIX and Solaris.

---

See " Supported Devices for AIX, HP-UX, Solaris and Windows" or " Supported Devices for Linux" for minimum supported version levels and platforms for these devices.

More information regarding device configuration is available in the Tivoli Storage Manager Administrator's Guide, which can be found in the IBM Tivoli Storage Manager information center.