locked
How to take log backup if job fails RRS feed

  • Question

  • Hi MSDN,  I have a log backup job which is failing regularly due to unexpected network error(59), and it is failing for some databases and failing on the next scheduled run too. There is no HA configured in this instance.

    Could you suggest the best possible way to resolve the above issue. Shall I take log backups manually or copy only log backups or should I leave as it is until it is successful in its next scheduled runs.

    Thanks.

    Saturday, March 30, 2019 8:53 AM

Answers

All replies

  • first try to troubleshoot for why failing for some database.

    try to take backup on local system

    share errorlog


    https://social.technet.microsoft.com/wiki/contents/articles/37872.sql-server-installation-on-centos-linux.aspx

    Saturday, March 30, 2019 12:20 PM
  • Are you sending log backups to local or third party backup tools? 

    you should work with your network team, so they can trace while backup is running and try to figure out what exactly causing network error. 

    please post detailed error from the job history. 

    https://dba.stackexchange.com/questions/203499/full-back-up-over-to-network-failed-due-to-unknown-network-error-59


    Thank you very much for your time and effort to answer this post. Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach Best -Ankit

    Saturday, March 30, 2019 11:50 PM
    1. Talk  to your network ADMIN
    2. Change the backup to the local SQL Server system, assuming there is adequate space. Then copy the backup to the network share, still see the error?

    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    Sunday, March 31, 2019 8:45 AM
    Answerer
  • Hi Kit, the full,diff and log backups are scheduled to go directly to UNC path(AWS). Previously it was configured to local system, As said by Uri and no issues observed till.

    We are facing 2 issues very frequently. One is Unexpected network error and second is 'Write on //UNC path' failed due to error ACCESS IS DENIED.

    And sometimes, the backup is success but job fails with the either of above errors.

    In instance with 10 databases, it is failing randomly for 2-3 databases each time when full or diff or log backup job runs.

    Is there any possibilities with issues in UNC path so that we can troubleshoot further?

    Wednesday, April 3, 2019 3:36 AM
  • If you have network issue, then you can not fix anything on SQL Server side; you have to fix the Network issues.

    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Wednesday, April 3, 2019 6:06 AM
  • make sure 445 port open so data copy happen.check with nw person.

    https://social.technet.microsoft.com/wiki/contents/articles/37872.sql-server-installation-on-centos-linux.aspx

    Wednesday, April 3, 2019 9:40 AM