none
SQL Server Restore Failing with Error Read on "M:\MSSQL\My_FULL_Backup_20190924_010558.bak" failed: 1101(A tape access reached a filemark RRS feed

  • Question

  • I have been trying to restore one of our db for the past few days without any luck. I keep getting the below error. I tried the restore during peak hours, off peak hours both by accessing the backup via network and then moving the file to local server. 

    I have also run Restorefilelistonly and restoreheaderonly on the backup and all seems to be fine. There is no permissions issue. 

    Please see the error below and the screenshot from SQL Logs. I did not much help googling this issue. 

    1 percent processed.
    2 percent processed.
    3 percent processed.
    4 percent processed.
    5 percent processed.
    6 percent processed.
    7 percent processed.
    8 percent processed.
    9 percent processed.
    10 percent processed.
    11 percent processed.
    12 percent processed.
    13 percent processed.
    14 percent processed.
    15 percent processed.
    16 percent processed.
    17 percent processed.
    18 percent processed.
    19 percent processed.
    20 percent processed.
    21 percent processed.
    22 percent processed.
    23 percent processed.
    24 percent processed.
    25 percent processed.
    26 percent processed.
    27 percent processed.
    28 percent processed.
    29 percent processed.
    30 percent processed.
    31 percent processed.
    32 percent processed.
    33 percent processed.
    34 percent processed.
    35 percent processed.
    36 percent processed.
    37 percent processed.
    38 percent processed.
    39 percent processed.
    40 percent processed.
    41 percent processed.
    42 percent processed.
    43 percent processed.
    44 percent processed.
    45 percent processed.
    46 percent processed.
    47 percent processed.
    48 percent processed.
    49 percent processed.
    50 percent processed.
    51 percent processed.
    52 percent processed.
    53 percent processed.
    54 percent processed.
    55 percent processed.
    56 percent processed.
    57 percent processed.
    58 percent processed.
    59 percent processed.
    60 percent processed.
    61 percent processed.
    62 percent processed.
    63 percent processed.
    64 percent processed.
    65 percent processed.
    66 percent processed.
    67 percent processed.
    68 percent processed.
    69 percent processed.
    70 percent processed.
    71 percent processed.
    72 percent processed.
    73 percent processed.
    74 percent processed.
    75 percent processed.
    76 percent processed.
    77 percent processed.
    78 percent processed.
    79 percent processed.
    80 percent processed.
    81 percent processed.
    82 percent processed.
    83 percent processed.
    84 percent processed.
    85 percent processed.
    86 percent processed.
    87 percent processed.
    88 percent processed.
    89 percent processed.
    90 percent processed.
    91 percent processed.
    92 percent processed.
    93 percent processed.
    94 percent processed.
    95 percent processed.
    96 percent processed.
    97 percent processed.
    98 percent processed.
    Msg 3203, Level 16, State 1, Line 2
    Read on "M:\MSSQL\My_FULL_Backup_20190924_010558.bak" failed: 1101(A tape access reached a filemark.)
    Msg 3013, Level 16, State 1, Line 2
    RESTORE DATABASE is terminating abnormally.

    Wednesday, September 25, 2019 1:11 PM

All replies

  • I will have to admit never seen that error message before, and I don't have much idea of what is going on.

    Tape access? You are not reading the back from a tape, are you?

    Those messages in the errorlog, do they relate to the database you trying to restore?

    Have you tried restoring the database on a different instance?

    What does "SELECT @@version" report? On which version was the backup taken.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Wednesday, September 25, 2019 9:12 PM
  • Hi Erland,

    1. No the backup is on local disk.
    2. Yes the error messages are related to the DB in question. 
    3. I am working on restoring the backup to another server let's see if it makes any difference.
    4. Version:
        Source: Microsoft SQL Server 2017 (RTM-CU12) (KB4464082) - 14.0.3045.24 (X64)   Oct 18 2018 23:11:05   Copyright (C) 2017 Microsoft Corporation  Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor) 

        Target:Microsoft SQL Server 2017 (RTM-CU16) (KB4508218) - 14.0.3223.3 (X64)   Jul 12 2019 17:43:08   Copyright (C) 2017 Microsoft Corporation  Developer Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor) 

    Thursday, September 26, 2019 3:13 AM
  • May this applies to your issue? https://www.veritas.com/content/support/en_US/article.100019281.html => error 3 "MAXTRANSFERSIZE"

    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Thursday, September 26, 2019 5:57 AM
    Moderator
  • Shaddy_1

    Are you getting any error like: Msg 3013, Level 16, State 1, Line 1 VERIFY DATABASE is terminating abnormally.?

    Thursday, September 26, 2019 6:57 AM
  • Hi Shaddy_1,

    Could you please try to create a new database backup and try to restore the new backup file?

    To allow SQL Server to perform new backups to the backup device, you must manually delete or erase the device.

    You could try to recreate a new backup with the following command

    BACKUP DATABASE mydatabase TO DISK='C:\MyDatabase.bak' with FORMAT

    Hope this could help you.

    Best Regards,

    Amelia Gu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, September 26, 2019 8:43 AM
  • I have indeed looked at that and tried the solution of matching the maxtransfersize from my backup script but it did not helped. 
    Thursday, September 26, 2019 12:30 PM
  • You have a problem with one or more disks - where those disks were not formatted correctly.  The general rule is to format with 64K allocation units - but that setting should be confirmed with the storage vendor to insure the appropriate offsets are configured for their system.

    Most likely - the problem with your restore is this mis-configuration which is causing a problem trying to read the data.


    Jeff Williams

    Tuesday, October 1, 2019 10:01 PM