none
Unable to backup to new Dell TL400 library RRS feed

  • Question

  • I recently decommissioned an old library and setup a new Dell PowerVault TL4000 unit.  I setup the unit using version 6.2.1.5 of the "non-exclusive" drivers from Dell's site, which appears as an "IBM TotalStorage 3573 Tape Library.  The tape drives (IBM ULT3580-HH5 SCSI Sequential Device) and changer bus enumerator are also using the same version.  The library has current firmware A/50/3.10e.  This unit is connected via SAS to the HP server.

     

    The problem.

    When I go to perform a backup job, the library loads the tape then shortly thereafter fails the job with a "Backup to tape failed" alert.  The alert details:

    • Description: The backup to tape job failed for the following reason: (ID 3311)
    • Detailed errors: Error Details: The operation failed because of a protection agent failure. (ID 998 Details: Incorrect function (0x80070001))
    • The alert e-mail says: Description: Backup to tape failed. The operation failed because of a protection agent failure .

    No data is making it to tape.  The library loads the tape, tags it for a protection group, but sets the label to "[No tape label. Contains no data]"

     

    I have tried going back to the original driver Windows setup when I first attached it (Unknown Medium Changer, I think), but DPM will not show the library/slots with that driver; it just shows the drives.  To make sure that DPM is not confused about the new library versus the old, I ran the pnputil to remove any traces of the old HP library from the driver store.  For what it's worth, I can inventory and erase tapes (erasing takes hours, so I have only done this once).

    Thanks for your help.

    Monday, August 15, 2011 3:04 PM

Answers

  • Hi,

    It seems we're having trouble reading barcode labels - do the tapes have barcodes ?  

    14E8 0640 08/15 16:52:56.428 30 lacommonlib.cpp(167)      NORMAL Element Type 2, Element Number 4 is in Exceptional State
    14E8 0640 08/15 16:52:56.428 30 lacommonlib.cpp(350)      NORMAL Barcode of the media could not be read

    Historically, this tape library needs to have this registry key added:

    Try adding the following registry key on the DPM server containing the tape library:

    "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent
       RSMCompatMode:REG_DWORD:0xD

    Note The RSMCompatMode registry value is used to specify multiple flags for DPM. The following are the flags that are set by this registry value:

    •1 = RSM_COMPAT_INIT_ELEMENT_STATUS
    •4 = RSM_COMPAT_IGNORE_TAPE_INVENTORY_RESULT
    •8 = RSM_COMPAT_CLEANER_EXCEPTION

    So 0xD = 13 decimal.

    In addition to that, it seems we're getting the same incorrect function error in this tool while trying to write, so there seems to be something wrong with that library, but don't know what exactly.  You may want to get in touch with Dell and have them verify things are good and maybe even try the library checker on a library in-house to verify it works OK.

    14E8 0640 08/15 17:12:17.008 30 dpmdevicelayer.cpp(1723) [000000000013F150]  NORMAL Hr: = [0x00000000] Writting Data onto tape
    14E8 0640 08/15 17:12:17.360 30 system.cpp(505)       NORMAL PrepareTape operation 4 returned 0, failing
    14E8 0640 08/15 17:12:35.795 30 system.cpp(505)       NORMAL PrepareTape operation 1 returned 0, failing
    14E8 0640 08/15 17:12:35.795 30 dpmdevicelayer.cpp(1776) [000000000013F150]  NORMAL  Read/Write test completed with hr - 0x46ba30
    14E8 0640 08/15 17:12:35.795 30 dpmdevicelayer.cpp(1629) [000000000013F150]  WARNING Failed: Hr: = [0x80070001] Read write test failed


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by SOMUM Wednesday, August 17, 2011 3:01 PM
    Tuesday, August 16, 2011 3:36 PM
    Moderator

All replies

  • Hi,

    Please download and run the dpm library checker tool from here: https://skydrive.live.com/?cid=885774776d4f197a&sc=documents&id=885774776D4F197A%21128  to see if it identifies any problems.

     

    Also, For DPM 2010 you can enable shorterase: http://technet.microsoft.com/en-us/library/ff634195.aspx

    Enabling Short Erase

    If your tape drive supports short erase, you can enable it on the DPM server by creating the DWORD UseShortErase under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent.

    Set the value of the DWORD to 00000000.

    After this value is set, all erase operations on the DPM server will be short erases. To revert to long erases, remove this registry key.

     


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, August 15, 2011 3:41 PM
    Moderator
  • I downloaded and ran the tool with all tests (DPMLibraryTest.exe /CERTIFY /TL \\.\Changer0 /AT). The bulk of the wrrors in the log file were from the cleaner media stage.  I have a cleaner in slot 45 and have it reserved by the library, and DPM is only shown 44 slots.  There are some warnings at the top of the file regarding QueryServiceStatus and GetServiceStatus and toward the end for Read Write tests.

    Could I send you the file or post it somewhere since I'm not quite sure what to look for?

    Monday, August 15, 2011 5:58 PM
  • Hi

    Please zip up the log file and upload it to:

    Workspace: https://sftus.one.microsoft.com/choosetransfer.aspx?key=733216de-cc53-4e36-80c7-b2167bbf3d15
    Password: TTe)4Kc#eBP$  


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, August 15, 2011 7:35 PM
    Moderator
  • The file has been uploaded.

     

    Thank you for your assistance.

    Tuesday, August 16, 2011 11:43 AM
  • Hi,

    It seems we're having trouble reading barcode labels - do the tapes have barcodes ?  

    14E8 0640 08/15 16:52:56.428 30 lacommonlib.cpp(167)      NORMAL Element Type 2, Element Number 4 is in Exceptional State
    14E8 0640 08/15 16:52:56.428 30 lacommonlib.cpp(350)      NORMAL Barcode of the media could not be read

    Historically, this tape library needs to have this registry key added:

    Try adding the following registry key on the DPM server containing the tape library:

    "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent
       RSMCompatMode:REG_DWORD:0xD

    Note The RSMCompatMode registry value is used to specify multiple flags for DPM. The following are the flags that are set by this registry value:

    •1 = RSM_COMPAT_INIT_ELEMENT_STATUS
    •4 = RSM_COMPAT_IGNORE_TAPE_INVENTORY_RESULT
    •8 = RSM_COMPAT_CLEANER_EXCEPTION

    So 0xD = 13 decimal.

    In addition to that, it seems we're getting the same incorrect function error in this tool while trying to write, so there seems to be something wrong with that library, but don't know what exactly.  You may want to get in touch with Dell and have them verify things are good and maybe even try the library checker on a library in-house to verify it works OK.

    14E8 0640 08/15 17:12:17.008 30 dpmdevicelayer.cpp(1723) [000000000013F150]  NORMAL Hr: = [0x00000000] Writting Data onto tape
    14E8 0640 08/15 17:12:17.360 30 system.cpp(505)       NORMAL PrepareTape operation 4 returned 0, failing
    14E8 0640 08/15 17:12:35.795 30 system.cpp(505)       NORMAL PrepareTape operation 1 returned 0, failing
    14E8 0640 08/15 17:12:35.795 30 dpmdevicelayer.cpp(1776) [000000000013F150]  NORMAL  Read/Write test completed with hr - 0x46ba30
    14E8 0640 08/15 17:12:35.795 30 dpmdevicelayer.cpp(1629) [000000000013F150]  WARNING Failed: Hr: = [0x80070001] Read write test failed


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by SOMUM Wednesday, August 17, 2011 3:01 PM
    Tuesday, August 16, 2011 3:36 PM
    Moderator
  • I had the RSMCompatMode in registry, but with different data (bad info from some other site).  It has been changed to "13" now.

    The web GUI for the library is now showing 7 out of 25 tapes with unknown volume serial numbers (bar codes).  That's strange, because they have always shown up on the libraries GUI.

    As for the write errors, I have the hardware encryption module in the library running.  I have turned it off in the past to run a test job in DPM, but got the same results.  The RSMCompatMode was set incorrectly at that time, though. 

    The hardware encryption module has now been turned off, the registry key has been added, the library will be rebooted in a few moments, and once that is back up, I will reboot the DPM server to get the registry key to kick in.

    Tuesday, August 16, 2011 4:11 PM