70.4.2 Data Pump common issues

•0x000000EA - More data is available 
Symptom:

When reading a tape the "More data is available" error message is displayed:
Etere HSM - Data Pump 1

Cause:
Data within the tape has been written using a block size bigger than the currently set.

Solution:
Enable the "Resize the read buffer if necessary" option located in the Drive tab of the Datapump parameters section:

Etere HSM - Data Pump - Parameters

•0x20000111 - Command time out (during cassette dismounting) 
Symptom:
Dismounting a cassette returns the 0x20000111 error code (Command time out):
EtHsmDataPump-x.log:
9.9.2009 18:13:57.459    547486.09 0000 dismounting drive in progress
9.9.2009 18:15:57.568    547606.12 0000 dismounting drive: 20000111  Command time out
9.9.2009 18:15:57.615    547606.13 0000 ProcMountCassette - ERROR 536871185 Command time out
That can be followed by the another errors: 0x00000057 - The parameter is incorrect:

EtHsmDataPump-x.log:
9.9.2009 18:16:34.677    547643.14 0000 mounting 001005: 00000057  The parameter is incorrect
9.9.2009 18:16:34.677    547643.14 0000 ProcMountCassette - ERROR 87 The parameter is incorrect

Cause:
Usually, the dismount command time-out is due to a need of the drive to unload the tape before dismounting the cassette.

Solution:
Enable the "Execute unload command before dismounting" option located in the Drive tab of the Datapump parameters section:
Execute unload command before dismounting

•SCSI error on Spectra Python tape library 
Symptom:
In Etere version 25, SCSI error “MEDIUM DESTINATION ELEMENT FULL” encountered in Data Pump when mounting and dismounting tapes from Spectra Python tape library.  The error persistent after restarted Spectra Python Tape Library, HSM Headquarters, and Data Pump.
Etere HSM - Data Pump 256

Cause:
There is misalignment of tape location in database and its actual position in Spectra Python tape library.

Solution:
From Etere released version 29.1 when SCSI error “MEDIUM DESTINATION ELEMENT FULL” or “MEDIUM SOURCE ELEMENT EMPTY” is triggered from the “Move” command, Etere Robotics would perform a scanning of Library content and update tape inventory to SQL database.

•Inconsistency in drive name
Scenario:
In HSM, Data Pump control the drive name correspondence between the drive in Tape Library and Tape Drive by comparing the drive’s serial number.  If Tape Library does not provide drive’s serial number to Tape drive, the drive name could be changed after reboot, as a results, operations on tapes cannot be proceed.

Possible solution:
•HSM Tape Library retrieve drive’s serial number stored in library as well as from the drive buffer.
•When Tape Library does not provide drive’s serial number information, Data Pump warn customer to set the “Persistent Binding” key value to “dword:00000001” in following Windows Registry
[HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Tape]
Nevertheless, customer can disable the device name correspondence check by disabling the "Check drive mismatch before tape read/write operations" option in Data Pump, at one’s own risk.

•Error 00000457 The bus I/O was reset unloading tape xxxxx into drive xxxxx 
Cause:
LTO tape failed to dismount from tape drive, it reveal the tape drive needs to receive a SCSI’s MOVE command upon received dismount command from host application.

Possible solution:
In LTO Tape Library manual, it revealed that the option “Library-Assisted Drive Unload” in Operations Parameters is likely the solution to the reported error.
Library-Assisted Drive Unload
In the event if Etere’s SCSI commands does not include the “dismount” command, the tape exchange would failed.  By enabling the “Library-Assisted Drive Unload” option to keep the Library default settings should the scenario occurred.

•Error 50000, Level 16, State 1, Procedure dm_updateJob, Line 40, Message: error executing mm.dm_updateJob, Message: @dest_codec param is null even on the source file"
Scenario:
In T-workflow, a Multistep Copy action was executed multiple time (> 100 times) in a day to copy files from HSM Archive to staging server, due to many codecs and devices involved customer is unable to define the source and destination codec in the copy action.  Despite the fact that the same Copy action is executed many times in a day, customer encounter the “Error 50000” occasionally without noticeable differences.

Cause:
The source file was copied from HSM Archive to HSM Cache, but the file in HSM Cache was deleted before the end of the Copy action.  As a result, Data Mover is unable to retrieve the information to update the database to set the destination file, despite the fact that the physical file has been copied correctly.

Solution:
Customer is advised to increase the available HSM Cache space to retain the file information while Copy action is still in progress.