Database Backup Failure SQL Server 2012 Enterprise

  • I am running a split disk backup such as:

    BACKUP DATABASE [At] TO

    DISK = N'O:\sql_bak\At_full1.bak',

    DISK = N'M:\sql_bak\At_full2.bak',

    DISK = N'L:\sql_bak\At_full3.bak' WITH NOFORMAT,

    INIT,

    NAME = N'At-Full Database Backup',

    SKIP,

    NOREWIND,

    NOUNLOAD,

    STATS = 10

    GO

    It is failing with the below error:

    Executed as user: DOMAIN\sqlserviceaccount. Processed 257856 pages for database 'At', file 'At' on file 1. [SQLSTATE 01000] (Message 4035) 10 percent processed. [SQLSTATE 01000] (Message 3211) 20 percent processed. [SQLSTATE 01000] (Message 3211) 30 percent processed. [SQLSTATE 01000] (Message 3211) 40 percent processed. [SQLSTATE 01000] (Message 3211) 50 percent processed. [SQLSTATE 01000] (Message 3211) 60 percent processed. [SQLSTATE 01000] (Message 3211) 70 percent processed. [SQLSTATE 01000] (Message 3211) 80 percent processed. [SQLSTATE 01000] (Message 3211) Write on "O:\sql_bak\At_full1.bak" failed: 112(There is not enough space on the disk.) [SQLSTATE 42000] (Error 3202) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.

    The database At is of 4TB size and the drives L,M and O are of 2TB each. These drives are completely free. It ran successfully once and since then it has been failing. Please suggest. 🙂

  • Anandita Sharma (3/24/2015)


    I am running a split disk backup such as:

    BACKUP DATABASE [At] TO

    DISK = N'O:\sql_bak\At_full1.bak',

    DISK = N'M:\sql_bak\At_full2.bak',

    DISK = N'L:\sql_bak\At_full3.bak' WITH NOFORMAT,

    INIT,

    NAME = N'At-Full Database Backup',

    SKIP,

    NOREWIND,

    NOUNLOAD,

    STATS = 10

    GO

    [SQLSTATE 01000] (Message 3211) Write on "O:\sql_bak\At_full1.bak" failed: 112(There is not enough space on the disk.) [SQLSTATE 42000] (Error 3202) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013).

    At the point the backup fails you don't have enough disk space on the O volume. Double check to make sure your backup is truly set to stripe to 3 different volumes. With the backup failing at almost 50%, and the db being 4tb and the O volume being 2tb, it seems like the actual backup is most likely just trying to go to O.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • Anandita Sharma (3/24/2015)


    I am running a split disk backup such as:

    BACKUP DATABASE [At] TO

    DISK = N'O:\sql_bak\At_full1.bak',

    DISK = N'M:\sql_bak\At_full2.bak',

    DISK = N'L:\sql_bak\At_full3.bak' WITH NOFORMAT,

    INIT,

    NAME = N'At-Full Database Backup',

    SKIP,

    NOREWIND,

    NOUNLOAD,

    STATS = 10

    GO

    It is failing with the below error:

    Executed as user: DOMAIN\sqlserviceaccount. Processed 257856 pages for database 'At', file 'At' on file 1. [SQLSTATE 01000] (Message 4035) 10 percent processed. [SQLSTATE 01000] (Message 3211) 20 percent processed. [SQLSTATE 01000] (Message 3211) 30 percent processed. [SQLSTATE 01000] (Message 3211) 40 percent processed. [SQLSTATE 01000] (Message 3211) 50 percent processed. [SQLSTATE 01000] (Message 3211) 60 percent processed. [SQLSTATE 01000] (Message 3211) 70 percent processed. [SQLSTATE 01000] (Message 3211) 80 percent processed. [SQLSTATE 01000] (Message 3211) Write on "O:\sql_bak\At_full1.bak" failed: 112(There is not enough space on the disk.) [SQLSTATE 42000] (Error 3202) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.

    The database At is of 4TB size and the drives L,M and O are of 2TB each. These drives are completely free. It ran successfully once and since then it has been failing. Please suggest. 🙂

    You could add compression to your backup script if your edition supports.

    Second, I had a similar issue long back , the issue was underlying Volume where the pool volume was filled with some snaps but not sure if that is the exact issue you had but I would check with system admin to see if any of the issues under the hood.

    [font="Tahoma"]
    --SQLFRNDZ[/url]
    [/font]

  • Anandita Sharma (3/24/2015)


    Write on "O:\sql_bak\At_full1.bak" failed: 112(There is not enough space on the disk.)

    The above message is pretty clear, as already suggested you could try using compression

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply