Post reply

sheduled network backup fails

  • July 1, 2006 at 7:18 am

    #118534

    Hi

    I have scheduled network backup on one of the client pc in LAN but when the this pc dosent respond due to any of the reason and scheduled backup run at that time then scheduled back strats failing every time and I have to delete the backup plan and recreate the plan.

    Thanks

    Brij

  • July 1, 2006 at 8:41 pm

    #647110

    Couple of questions:

    1) You are writing to a UNC path I assume

    2) Are you using a SQL Server Maintenance Plan

    3) This is SQL 2000 I assume?

    4) Are you using a backup device vs explicitly typing in the UNC path?

    Those being asked, what's probably happening is that once the network connection is broken, SQL is continuing to try to connect to the previous handle.

    Now from the soapbox: I would backup directly over the network like that. I better idea would be to back it up locally on the server, then have a separate job step to copy the backup files across the network. The longer it takes any process to run, the more chances there are for some sort of failure.

    My 2 cents, hope it helps.

  • July 3, 2006 at 12:38 am

    #647145

    HI

    1) Yes I am writing to UNC path

    2) Not using maintenance plan

    3) I am using sql server 2000 Ent. Edition

    4) Yes I have created backup device and file location is on network

    my problem is once the schduled network backup fails then it contineously keeps failing untill new schduled is created, even though the network is up.

    Regards & Thanks

    Brij

  • July 3, 2006 at 4:58 am

    #647161

    If this is a scheduled backup, you have to make sure that SQL Server Agent is running under an accoutn which is priviledged to access ressources (especially the ressource you are using) on the network. Otherwise it will throw an security exception.

    HTH, Jens Suessmeyer.

    ---

    http://www.sqlserver2005.de

    ---

  • July 4, 2006 at 1:11 pm

    #647384

    If I'm understanding the issue, the scheduled process runs fine until there's a disconnection in the network. Is that correct? That should rule out security issues (should...).

    One thing you may want to try - instead of a backup device that references the location, specify the file directly in the backup statement, not the device. It sounds very much like SQL is trying to retain a handle on a network session of some sort that doesn't exist, similar to what can happen with SQL Mail when you loose the connection to Exchange.

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

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