Non-IBM Ultrium Generation 4 (LTO-4) Drive Configuration Information for IBM Tivoli Storage Manager Server

Preventive Service Planning


Abstract

Configuration Information for HP Ultrium 1760, HP Ultrium 1840, Quantum LTO-4 HH, Sun StorageTek Ultrium 1840, and Tandberg LTO-4 HH drives

Content


HP Ultrium 1760
HP Ultrium 1840
Quantum LTO-4 HH
Sun StorageTek Ultrium 1840
Tandberg LTO-4 HH

1. When defining a device class for LTO-4 drive, use

    o devtype=LTO
    o format=<DRIVE | ULTRIUM4 | ULTRIUM4C>

Example:

DEFine DEVclass devclassname DEVType=LTO FORMAT= DRIVE .....
DEFine DEVclass devclassname DEVType=LTO FORMAT= ULTRIUM4 .....
DEFine DEVclass devclassname DEVType=LTO FORMAT= ULTRIUM4C .....

ULTRIUM4 - Specifies that IBM Tivoli Storage Manager writes data that uses the ULTRIUM4 recording format. This format results in a cartridge capacity of 800 GB when using Ultrium 4 media.

ULTRIUM4C - Specifies that IBM Tivoli Storage Manager writes data that uses the ULTRIUM4 recording format with compression. This format results in a cartridge capacity of 1.6 TB when using Ultrium 4 media.

2. All LTO-4 drives in this technote have a data compression ratio of 2:1

3. Quantum LTO-4 HH drives with firmware revision ending in F require the following Tivoli Storage Manager Server versions.
  • Tivoli Storage Manager Server version 5.5 - maintenance level 5.5.5 or later
  • Tivoli Storage Manager Server version 6.1 - currently not supported
  • Tivoli Storage Manager Server version 6.2 - maintenance level 6.2.2 or later

4. Device identification and firmware levels
    HP Ultrium 1760 (SCSI interface)
    Drive ID: HP Ultrium 4-SCSI
    Firmware: W22D (validated with TSM 5.4.4)

    HP Ultrium 1760 ( FC interface)
    Drive ID: HP Ultrium 4-SCSI
    Firmware: V22D (validated with TSM 5.4.4)

    HP Ultrium 1760 ( SAS interface)
    ** Supported on Windows and Linux only. TSM version 5.5.2 or later is required. **
    Drive ID: HP Ultrium 4-SCSI
    Firmware: U24V (validated with TSM 6.1.0)

    HP Ultrium 1840 ( FC interface)
    Drive ID: HP Ultrium 4-SCSI
    Firmware: H13D (validated with TSM 5.4.1.2)

    Quantum LTO-4 HH (SAS interface)
    ** Supported on Windows and Linux only. TSM version 5.5.2 or later is required. **
    Drive ID: QUANTUM ULTRIUM 4
    Firmware: 2104 (validated with TSM 5.5.2)

    Quantum LTO-4 HH (SCSI interface)
    Drive ID: QUANTUM ULTRIUM 4
    Firmware: W52F (validated with TSM 5.5.5, 6.1.5, and 6.2.2)

    Sun StorageTek Ultrium 1840
    Drive ID: HP Ultrium 4-SCSI
    Firmware: H2BS

    Tandberg LTO-4 HH
    Drive ID: TANDBERG LTO-4 HH
    Firmware: W229 (validated with TSM 5.5.2)

5. Supported media
    o LTO4 data cartridge ( Read/Write )
    o LTO3 data cartridge ( Read/Write )
    o LTO2 data cartridge ( Read Only )

6. All LTO-4 drives in this technote report drive serial number.

7. To mix LTO-3 and LTO-4 media in a library that does not have mixed media support, all drives in the library must be LTO-4 and device class format must be set to DRIVE.

8. For drive encryption support, Tivoli Storage Manager version 5.4.2 or later is required. The data encryption feature is currently not supported on Sun StorageTek Ultrium 1840 drives.

9. Automatic cleaning via the CLEANFREQuency=ASNEEDED option is supported for HP Ultrium 1760, HP Ultrium 1840, Quantum LTO-4 HH, Sun StorageTek Ultrium 1840 drives, and Tandberg LTO-4 HH drives.

10. Mixing LTO3 and LTO4 media in a library with a drive that is setup for Application Managed Encryption is not supported.


LTO-4 Drive Encryption Support

Encrypting Data

It is often critical to secure client data, especially when that data may be of a sensitive nature. To ensure that data for off-site volumes is protected, TSM Server can utilize T-10 Encryption protocols to encrypt and decrypt data sent to tape drives which can support T-10 Security protocols. This protocol utilizes a stronger level of encryption by requiring 256-bit Advanced Encryption Standard (AES) encryption keys. Keys are passed to the drive by a key manager in order to encrypt and decrypt data.

The Application method of encryption is supported for LTO-4 tape with HP LTO-4, Quantum LTO-4 HH, and Tandberg LTO-4 HH drives. With this method, encryption keys are managed by the application, in this case, Tivoli Storage Manger. Tivoli Storage Manager generates and stores the keys in the server database. Data is encrypted during WRITE operations, when the encryption key is passed from the server to the drive. Data is decrypted on READ operations.

    Warning: When using Application encryption, you must take extra care to secure database backups since the encryption keys used to encrypt and decrypt data are stored in the server database. In order to restore your data, you must have the correct database backup and corresponding encryption keys to access your information. Ensure that you back up the database frequently and safeguard the backups to prevent data loss or theft. Anyone who has access to both the database backup and the encryption keys has access to your data.
Application managed encryption is only supported for storage pool volumes. Other volumes such as backupset tapes, export volumes, and database backups will not be encrypted using the Application method.

Tivoli Storage Manager can turn encryption on or off depending on the DRIVEENCRYPTION value on the device class. Tivoli Storage Manager server will not display a warning message if the DRIVEENCRYPTION parameter is set to ON for drives that do not support encryption even though no encryption occurs.

Using Drive Encryption
In order to utilize drive encryption, your Tivoli Storage Manager environment should be set up so that all drives in a library support the new encryption format. In addition, all drives within a logical library must use the same method of encryption. Tivoli Storage Manager does not support an environment in which some drives use the Application method and some drives use another method of encryption.

When using encryption-capable drives with the Application method, a new format will be used to write encrypted data to tapes. If data is written to volumes using the new format and if the volumes are then returned to scratch, they will contain labels that are only readable by encryption-enabled drives. To use these scratch volumes in a drive that is not enabled for encryption, either because the hardware is not capable of encryption or because the encryption method is set to OFF, you must relabel them.

Specifying the DRIVEENCRYPTION Parameter
The DRIVEENCRYPTION parameter is only supported for LTO-4 (ULTRIUM4 and ULTRIUM4C) formats. It specifies whether or not drive encryption is enabled or can be enabled. Application encryption is supported with LTO-4 drives.

To utilize this method, the parameter must be set to ON. This permits the encryption of data for empty storage pool volumes. When the parameter is set to ON, backup operations will fail if the hardware is configured for another encryption method.

To disable encryption on new volumes, the parameter should be set to OFF. If the hardware is configured to encrypt data through a method other than Application encryption, and DRIVEENCRYPTION is set to OFF, backup operations will fail.

The DRIVEENCRYPTION parameter is optional. The default value is to allow another method of encryption.

Setting up Encrypted Storage Pools
You can set up encrypted storage pools to protect tapes that contain critical or sensitive data. This is particularly beneficial for tapes that are removed from the Tivoli Storage Manager server environment to an off-site location. Tapes that contain sensitive security or financial information can become an exposure if data is not encrypted and tapes are lost.

Example

Define an encrypted storage pool so that Tivoli Storage Manager is the encryption key manager. This method is defined through the device class. Complete the following steps:
    1. First, define your library:
    define library HPLTO4 libtype=SCSI

    2. Next, define a device class LTO_ENCRYPT such that storage pool volumes will be encrypted:
    define devclass LTO_encrypt library=HPLTO4 devt=lto format=ultrium4c drivee=on

    3. Now define a storage pool named LTO_ENCRYPT_POOL with a MAXSCRATCH value of 10:
    define stgpool LTO_encrypt_pool LTO_encrypt maxscr=10


Command Updates:

DEFINE DEVCLASS


DRIVEEncryption
Specifies whether drive encryption will be permitted. This parameter is optional. The default is ALLOW.

ON
Specifies that Tivoli Storage Manager is the key manager for drive encryption and will permit drive encryption for empty storage pool volumes only if the Application method is enabled through the hardware. (Other volumes, for example, backup sets, export volumes, and database backup volumes will not be encrypted.) If you specify ON and enable another method of encryption, drive encryption will not be permitted and backup operations will fail.

Notes:
o For LTO-4 drives, DRIVEEncryption=ON is supported only with LTO-4 media.
o DRIVEEncryption=ON is not supported for WORM media.

ALLOW
Specifies that Tivoli Storage Manager does not manage the keys for drive encryption. However, drive encryption for empty volumes is permitted if another method of encryption is enabled.

OFF
Specifies that drive encryption will not be permitted. If you enable another method of encryption, backups will fail. If you enable the Application method, Tivoli Storage Manager will disable encryption and backups will be attempted.



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.

Related information

IBM Ultrium Generation 4 (LTO-4) drive and drive encryp

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager
Server

Software version:

All Supported Versions

Operating system(s):

Platform Independent

Reference #:

1264284

Modified date:

2011-04-12

Translate my page

Machine Translation

Content navigation