Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Verified Answer
  • Replies replies
    5
  • Subscribers subscribers
    12
  • Views views
    637
  • Users 0 members are here
  • +1 person also asked this people also asked this
Related
Options

Data Protector - Restore / possible block size issue

Michael Bailey

Hi,

I’m after some advice on the following issue,

Due to migration activities of DP we need to restore data to another backup solution. During this process a multipathing driver needed to be installed onto the media agent server which appears to have caused problems with backing up and restoring.

After some testing it appears that when performing a new backup and restore it now only works with 64(kb) block size configured on the drive whereas before the driver install it was 256(kb), this means all existing restores are failing to run with the following error message:    (I’m assuming the driver install possibly changed something to lock DP to work with 64(kb) block size maximum)

[Major] From: RMA@*************  "HP:Ultrium 6-SCSI_4"  Time: 18/01/2024 10:21:31

[90:52]     Tape5:1:0:7:0C

      Cannot read from device ([87] The parameter is incorrect. )

[Major] From: RMA@*************  "HP:Ultrium 6-SCSI_4"  Time: 18/01/2024 10:21:31

[90:53]     Tape5:1:0:7:0C

      Cannot seek to requested position (Details unknown.)

[Critical] From: RMA@************* ""  Time: 18/01/2024 10:21:31

[61:17112] Medium header verification failed on drive HP:Ultrium 6-SCSI_4.

      All objects on this medium will be marked as failed.

 Data Protector version: 10.60 / Server windows 2012

Any suggestions on what could fix this issue?

  • 0  

    If only 64k works then the installd driver must be causing this and that is a real concern. If you confirm that even trying to read with 256k from a tape which was written with that blocksize is failing then my suggestion would be to use  another media agent which does not have that driver installed. Hopefully you have another system which can be used for that purpose?

    Koen Verbelen

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.
    You may also be interested in my Data Protector Support Tips listed per category

  • 0

    unfortunately we don't have a spare media agent server, after checking driver install dates, the tape drives and medium changer drivers have the install date the same day the multipathing driver was installed although the drivers are still from 2013. And yes its failing to read 256k even though the tapes were originally 256k, it only works if we use 64k now. 

  • Verified Answer

    +1

    Issue resolved, had to modify registry setting for the emulex LimTransferSize (parameter) service from 1 (64kb) to 3 (256kb).

  • 0   in reply to 

    Can you please post the registry you have modified, please ?

    I am having the same issue with an HPE qlogic HBA on a windows server and in the past I simply set the registry key:

    \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ql2300\Parameters\Device

    setting MaximumSGList to 257 to set a 1024k block size but unfortunaltely this time it is not working so I want to try your solution.

    Thaks a lot

    Dionisio Sciascia
    Micro Focus (now OpenText) Professional Services Senior Technical Consultant
    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

  • 0 in reply to   

    Not sure if it will help, I got the information from this page > windows_manual_elx.book (broadcom.com) on page 37

    you might not have the same options for the driver/service, for me its \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\elxfc\parameters\10000000C9908A87 and 10000000C9908A86 modifying the parameter LimTransferSize=3

    I tried the maximumSGList first with no luck then came across the above.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.