Post reply

Validating backup set

  • February 23, 2016 at 12:03 am

    #316245

    Hi All,

    We are using native SQL backup in SQL 2008r2. We have more than 20 databases in one instance.

    We are taking backup to network share. Usually it will complete in 10 min. Some times the backup job failing. I know in which database the backup job failed but I can't trust the backups that completed successfully. Is there any script that available to validate the backup files that run in that job?

    Thanks in advance

  • February 23, 2016 at 1:50 am

    #1860301

    Try to restore them: that's the only way to know for sure. Find a test server (your workstation will do as well) and restore those backups.

    -- Gianluca Sartori

  • February 23, 2016 at 5:36 am

    #1860359

    The best way is to restore the database, but there are some other checks you can run. I have an article that lays it all out here[/url].

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • February 23, 2016 at 10:20 am

    #1860488

    Try upping your session timeout for your backup failures to network storage:

    http://technet.microsoft.com/en-us/library/cc938292.aspx

  • February 24, 2016 at 11:35 am

    #1860838

    This should be modified on the server where backup job is scheduled right (Production).

    Is there any affects due to this change? It is happening once in a month.

  • February 24, 2016 at 11:42 am

    #1860842

    I've used it on many servers to resolve timeouts when backing up to network storage without any negative side effects.

    ...and yes you would implement on your prod box.

Viewing 6 posts - 1 through 5 (of 5 total)

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