IBM Support

IT28056: MICROSOFT SQL LOG BACKUPS STOP WITH THE ERROR "FILE IS TOO LONG"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Transaction Log backups for Microsoft SQL can stop with the
    message :
    ERROR|Failed to move the file from [C:\Program Files\Microsoft
    SQL
    Server\MSSQL14.MSSQLSERVER\MSSQL\Backup\<Hostname>_<DBName>_log_
    z_<ID>.trn] to
    [\\<vSnapHostIP>\vpool<x>_fs<yy>\<Hostname>_<DBName>\<Hostname>_
    <DBName>_log_z_<ID>.trn]. Last exception: System.IO.IOException:
    The file is too long. This operation is currently limited to
    supporting files less than 2 gigabytes in size.
    
    As seen by the SQL server, the log backup will be successful
    when the *.trn file is created successfully in the local staging
    directory.
    The next step, copying the *.trn file to the CIFS share on the
    vSnap server does also complete.
    Removing the *.trn file from the staging directory does not
    happen because of the way the consistency check is done before
    the local file deletion.
    
    As additional consequence of the above issue, these left over
    *.trn files can add up over time and fill up the local staging
    filesystem.
    
    IBM Spectrum Protect Plus Versions Affected: 10.1.x
    
    
    Initial Impact: High
    
    Additional Keywords: SPP, SPPLUS, TS001874935, MSSQL, log,
    backup
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Spectrum Protect Plus Level 10.1.2 and 10.1.3            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in level 10.1.2.350, 10.1.3 patch 1    *
    * and 10.1.4. Note that this is subject to change at the       *
    * discretion of IBM                                            *
    ****************************************************************
    

Problem conclusion

  • The problem has been fixed by changing a method that had a
    maximum limit of 2GB
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT28056

  • Reported component name

    SP PLUS

  • Reported component ID

    5737SPLUS

  • Reported release

    A12

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-11

  • Closed date

    2019-04-11

  • Last modified date

    2023-03-06

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • sql
    

Fix information

  • Fixed component name

    SP PLUS

  • Fixed component ID

    5737SPLUS

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNQFQ","label":"IBM Spectrum Protect Plus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A12","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
30 January 2024