VTL - Can't export to physical tape due to "incompatible media type"

Asset ID:	1-72-1127825.1
Update Date:	2012-07-13
Keywords:

Solution Type Problem Resolution Sure

Solution 1127825.1 : VTL - Can't export to physical tape due to "incompatible media type"

Applies to:

Sun StorageTek VTL Plus Storage Appliance - Version 1.0 - Build 1323 to 2.0 - Build 1656 [Release 1.0 to 2.0]
Sun StorageTek VTL Storage Appliance - Version 4.0 - Build 1221 to 4.0 - Build 1221 [Release 4.0]
Information in this document applies to any platform.

Symptoms

Virtual tape (Vtape) is mounted for tape caching into the incorrect physical library (Plib) or ACSLS pool with different drive type and VTL attempts export to that incorrect drive and fails with "STATUS_INCOMPATIBLE_MEDIA_TYPE" , VTL will record that incorrect Plib in the Vtape header (this is primarily for incremental exports to remember last Plib used) and keep attempting to use that Plib for future exports.

Example messages from VTL messages file:
============================
Barcode H07673 (Tape VID 10001543) originally in Plib 377:

Dec 30 18:17:51 water-VTL-Node1 genunix: [ID 459543 kern.notice] <6>[ffffffff984b4720] TLE_INFO: 377:10001543[H07673]

When barcode H07673 (Tape VID 10001543) was attempted to be exported to wrong Plib/drive, it updated the PTL VID for the migration job to 279, and the migration job failed due to "STATUS_INCOMPATIBLE_MEDIA_TYPE"

Jan 7 16:40:24 water-VTL-Node1 genunix: [ID 459543 kern.notice] <6>[ffffffff9cbcd3e0] TLE_INFO: CreateTapeCachingJob: Job 1308 created successfully on tape [H07673] 10001543
Jan 7 16:40:30 water-VTL-Node1 sanidmgr[7771]: [ID 702911 daemon.notice] IPSTOR||0||E||0x00009c8a||ExportJob failed||1308||104||H07673||H07673
Jan 7 21:41:05 water-VTL-Node1 tleupd_32bit[8000]: [ID 889572 daemon.notice] [43232_mount 192.168.165.21|0|100|0|0||H07673|0.3.1.0] mount acs_response() failed in getting final response. Status: STATUS_INCOMPATIBLE_MEDIA_TYPE

Changes

N/A

Cause

Physical tape entered/mounted into incorrect physical library and/or incorrect ACSLS pool.

Solution

The reason the incorrect Plib is used, is due to a user error, where physical tape (Ptape) is re-inserted into the physical library and assigning it to the wrong tape pool via ACSLS. The only way to change the Plib variable back to the correct Plib setting in the Vtape header, is to either let the data expire and relabel the Vtape OR re-insert into correct ACSLS pool and use the VTL util "tlecli.1656.setplib" to
change Plib variable back to correct setting.

The following shows how to execute and what the input is for the "tlecli.1656.setplib" utility in order to change the Vtape header to contain the correct Plib setting.

Contact VTL Backline Support to obtain the setplib utility. Once utility is downloaded to the VTL server, to execute enter:

# tlecli.1656.setplib -- interactive
# 99

Use the VTL Console or Xray to get the VID of each virtual resource needed below:
# TapeVID: 'enter vid of Vtape here'
# nnnnnn
# VlibVID: 'enter vid of Vlib here'
# nnnnnn
# PlibVID: 'enter vid of Plib here'
# 345678
# 0 (to exit)

Attachments

This solution has no attachment