Preventive Service Planning
Abstract
Configuration information for the IBM TS1160 (0359260F) tape drive and associated tape media
Content
NOTE: For IBM TS1160 (0359260F) drive support information in a library, consult the technote pertaining to the perspective library
IBM TS1160 Model 60F Fiber Channel interface version is supported.
IBM TS1160 Model 60S SAS drive is only supported on Linux & Windows.
IBM TS1160 drive is supported with the following features and formats:
- IBM Spectrum Protect application-managed encryption
- Logical Block Protection(LBP)
- Append-only mode
Required Spectrum Protect versions:
- IBM TS1160 drive support requires IBM Spectrum Protect version 8.1.6.100 or subsequent maintenance release
- Write Once Read Many (WORM) is not supported with IBM Spectrum Protect version 8.1.6.100
Device Class Information:
When defining a device class for the IBM TS1160, use the following values:
DEVTYPE=3592
FORMAT=<DRIVE | 3592-6 | 3592-6C | 3592-5A | 3592-5AC | 3592-5 | 3592-5C>
where 3592-6 is the uncompressed format and 3592-6C is the compressed format.
Generational Compatibility:
For optimal performance, do not mix generations of 3592 drives in a single logical library. Media problems can result when different drive generations are mixed. For example, the IBM Spectrum Protect server might not be able to read a volume's label. The following table shows read-and-write interoperability for several generations.
where 3592-6 is the uncompressed format and 3592-6C is the compressed format.
Generational Compatibility:
For optimal performance, do not mix generations of 3592 drives in a single logical library. Media problems can result when different drive generations are mixed. For example, the IBM Spectrum Protect server might not be able to read a volume's label. The following table shows read-and-write interoperability for several generations.
|
Drives
|
Generation 1 format
|
Generation 2 format
|
Generation 3 format
|
Generation 4 format
|
Generation 5 format
|
Generation 5 Archive format
|
Generation 6 format |
|
Generation 1
3592-J1A
|
Read & write | - |
-
|
- | - | - | - |
|
Generation 2
3592-E05
|
Read & write | Read & write |
-
|
- | - | - | - |
|
Generation 3
3592-E06
|
Read only | Read & write |
Read & write
|
- | - | - | - |
|
Generation 4
3592-E07
|
Read only | Read only |
Read & write
|
Read & write | - | - | - |
|
Generation 5
3592-E08
|
- | - | - | Read & write | Read & write | - | - |
|
Generation 5
Archive 3592-55F
|
- | - | - |
Read only
|
Read & write | Read & write | - |
|
Generation 6
3592-60F
|
- | - | - | Read only | Read & write | Read & write | Read & write |
|
- Not Supported
Note: Devices with updated firmware may support reformatting media written with unsupported formats to a supported format based on media type.
|
|||||||
Native capacities:
|
IBM TS1160 Native Capacities with Associated 3592 Media
|
||
|
3592 Type E (Economy) - JM
|
3592 Type E - JE/JV | |
| Native Capacity |
5.0 TB
|
20.0 TB |
| Tip: Compressed capacity is not estimated for the IBM TS1160 . Use the ESTCAPACITY parameter when you define or update the device class to tune the compressed capacity to match the actual data compression ratio. | ||
If you mix generations of drives within the same library partition, use one of the following methods to prevent or minimize potential problems:
Open systems and Windows:
If your library contains two drive generations, all drives should use the format of the earlier generation. For example, if your library contains Generation 6 and Generation 5 Archive drives, all the Generation 6 drives should use the Generation 5 archive drive format. The result is that all the drives can read from and write to all of the media.
Remember: If both drive generations write in the format of an earlier drive generation, both drive generations can verify labels and read media written in the format of the earlier drive generation. For example, if your library contains Generation 6 and Generation 5 Archive drives, both drive generations can verify labels and read media written in the Generation 5 Archive format. However, this configuration does not allow the Generation 6 drives to read or write in their optimal format.
349X and ACSLS libraries only:
Remember: If both drive generations write in the format of an earlier drive generation, both drive generations can verify labels and read media written in the format of the earlier drive generation. For example, if your library contains Generation 6 and Generation 5 Archive drives, both drive generations can verify labels and read media written in the Generation 5 Archive format. However, this configuration does not allow the Generation 6 drives to read or write in their optimal format.
349X and ACSLS libraries only:
This method is a simple way to logically partition the generations without partitioning the hardware. Define two or three new library objects for each drive generation that the physical library contains. For example, if you have a physical library with 3592-60F drives and 3592-55F drives, define two new library objects.
Specify a path with the same special file name for each new library object. In addition, for 349X libraries, specify disjointed scratch categories (including the WORMSCRATCH category, if applicable) for each library object. Specify a new device class and a new storage pool that points to each new library object.
Specify a path with the same special file name for each new library object. In addition, for 349X libraries, specify disjointed scratch categories (including the WORMSCRATCH category, if applicable) for each library object. Specify a new device class and a new storage pool that points to each new library object.
Example for a new 349X library object with a set of 3592-6 drives:
Example for a new 349X library object with a set of 3592-5A drives:
DEFINE LIBRARY libgen6 LIBTYPE=349X SCRATCHCAT=400 PRIVATECAT=401
DEFINE PATH server1 libgen6 SRCT=SERVER DESTT=LIBR DEVI=devlib
DEFINE DRIVE libgen6 dr1
DEFINE PATH server1 dr1 SRCT=SERVER DESTT=DRIVE LIBR=libgen6 DEVI=deva
DEFINE DRIVE libgen6 dr2
DEFINE PATH server1 dr2 SRCT=SERVER DESTT=DRIVE LIBR=libgen6 DEVI=devb....Example for a new 349X library object with a set of 3592-5A drives:
DEFINE LIBRARY libgen5A LIBTYPE=349X SCRATCHCAT=500 PRIVATECAT=501
DEFINE PATH server1 libgen5 SRCT=SERVER DESTT=LIBR DEVI=devlib
DEFINE DRIVE libgen5A dr1
DEFINE PATH server1 dr1 SRCT=SERVER DESTT=DRIVE LIBR=libgen5A DEVI=devc
DEFINE DRIVE libgen5A dr2
DEFINE PATH server1 dr2 SRCT=SERVER DESTT=DRIVE LIBR=libgen5A DEVI=devd
....TIP: The DEVICE value for the path definition in both library objects is the same because both library objects refer to the same physical library. However, drives should be unique to each library. Thus, in the example, all 3592-60F drives would be defined to libgen6 and all 3592-55F drives would be define to libgen5A.
SCSI only: Define a new storage pool and device class for the Generation 6 drives. Set the FORMAT parameter to 3592-6 or 3592-6C (not DRIVE). The original device class will have a FORMAT parameter set to 3592-5A or 3592-5AC (not DRIVE). Update the MAXSCRATCH parameter to 0 for the storage pool that will contain all the media written in Generation 5A format, for example:
UPDATE STGPOOL<gen5Apool> MaxSCRatch=0
This method allows both generations to use their optimal format and minimizes potential media problems that can result from mixing generations. However, it does not resolve all media issues. For example, competition for mount points and mount failures might result. The following known media issues also remain:
1. CHECKIN LIBVOL: The problem resides with using the CHECKLABEL=YES option. If the label is written in a Generation 5A format, drives of previous generations fail this command for this media type. As a best practice, use CHECKLABEL=BARCODE to circumvent this issue.
2. LABEL LIBVOL: The problem also results when the server tries to use drives of a previous generation to read the label written in a Generation 5A format. In this case, the LABEL LIBVOL command fails unless OVERWRITE=YES is specified. Verify that the media being labeled with OVERWRITE=YES does not have any active data.
3. CHECKOUT LIBVOL: As with the previous two commands, the same problem arises when IBM Spectrum Protect verifies the label (CHECKLABEL=YES) if it is written in a Generation 6 format and the operation uses drives of previous generations to read the label. Thus, the preferred method is to specify CHECKLABEL=NO to circumvent this issue.
2. LABEL LIBVOL: The problem also results when the server tries to use drives of a previous generation to read the label written in a Generation 5A format. In this case, the LABEL LIBVOL command fails unless OVERWRITE=YES is specified. Verify that the media being labeled with OVERWRITE=YES does not have any active data.
3. CHECKOUT LIBVOL: As with the previous two commands, the same problem arises when IBM Spectrum Protect verifies the label (CHECKLABEL=YES) if it is written in a Generation 6 format and the operation uses drives of previous generations to read the label. Thus, the preferred method is to specify CHECKLABEL=NO to circumvent this issue.
IBM Device Driver:
The IBM device driver is required for the IBM TS1160 (3592-60F) drive. IBM device drivers are available at IBM Fix Central . Choose the following options from the drop-down menus.
- Product Group -> System Storage
- System Storage -> Tape systems
- Tape systems -> Tape drivers and software
- Tape drivers and software -> Tape device drivers
- Platform -> Select the platform for the device driver
IBM device driver level and firmware level requirements:
- IBM AIX Atape driver 13.0.33.0 or newer
- IBM Linux lin_tape driver 3.0.39-1 or newer
- IBM Windows drivers 6.2.6.8 or newer
- IBM TS1160 (3592-60F) firmware rev 5450 or newer
Device identifications and firmware levels used during validation process:
(TS1160 Model 70F FC Drive: Validated with IBM Spectrum Protect Server 8.1.6.100)
- Library ID: IBM 3584L22 --- Firmware: 1501
- Drive ID: IBM 0359260F --- Firmware: 5450
(TS1160 Model 70S SAS Drive: Validated with IBM Spectrum Protect Server 8.1.10)
- Library ID: IBM 03584L22 --- Firmware: 1710
- Drive ID: IBM 0359260F --- Firmware: 5625
SCSI Reference:
IBM System Storage Tape Drive 3592 SCSI Reference. This reference guide provides detailed information about the IBM System Storage Tape Drive 3592 SCSI command support. This highly technical document is of interest to device driver developers, application developers, systems administrators, and software installers.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEQVQ","label":"IBM Spectrum Protect"},"Component":"Server","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"8.1.6.100","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Was this topic helpful?
Document Information
Modified date:
29 August 2023
UID
ibm10794579