Windows Server Backup Fails On Scheduled Task

Posted on 2012-08-13
Last Modified: 2013-01-23

We have a 64bit 2008 Std Server (SP2) running a scheduled backup to a virtual hdd, the backup is just over 60gb.

Recently the backup fails with two messages

C: System cannot find the path specified
Other Drives: The backup of the volume was stopped before the backup started running

If the backup runs on the schedule then it will only backup 1.63gb of data on drive C: then stop.
However, if we run a onetime backup using the same configuration as the schedule then the backup will complete perfectly.

We have recreated eth backup job but still receive the same results all round.

We are currently receiving the following error in the logs:

EVENT: 517

<Event xmlns="">
- <System>
<Provider Name="Microsoft-Windows-Backup" Guid="{1db28f2e-8f80-4027-8c5a-a11f7f10f62d}" />
<TimeCreated SystemTime="2012-08-13T13:53:46.262Z" />
<Correlation />
<Execution ProcessID="8080" ThreadID="8196" />
<Security UserID="S-1-5-18" />
- <EventData>
<Data Name="BackupTime">2012-08-13T13:17:43.830Z</Data>
<Data Name="ErrorCode">2147942402</Data>
<Data Name="ErrorMessage">%%2147942402</Data>

Any help would be greatly appreciated.
Question by:diles
    LVL 13

    Expert Comment

    is it a virtual server?

    Maybe some of the steps in this EventID can help isolate the cause:

    Author Comment

    The server itself isn't virtual, it just backs up to a virtual drive.

    Thanks for the reply, I'll take a look.

    Author Comment

    Update: The Backup is now failing on a "Backup once" although it did back up 12.36gb compared to the 1.63gb during the scheduled backup

    I've made the change to the registry as suggested in the link provided and will report back the results.

    Author Comment

    Backup failed again, at least it's getting to about 11.34gb now but then failing with the same error as before.

    Expert Comment

    I ran into this issue with a batch file running as a scheduled task. It would run perfectly fine if I executed it manually but when I tried to run it as a schedule task it would fail instantly.  The batch file I was running was a simple Robocopy command.  I had created mapped drive letters to make it simple to write.  Come to find out when executing the command manually it recognized the mapped drive and performed the function flawlessly.  However when executing the command from a scheduled task the task could not recognize the drive mapping and therefore fail.  I used the full UNC name in the command and the task ran correctly. (ie robocopy \\server_name\share_name\path d:\local_path)

    I assume that when any executable file is run via a scheduled task it takes on a different personality or is not simply running the executable as you would from a command line.  Bottom line DO NOT run executables that include mapped drive letters...stick with the UNC name and the task will behave properly

    Accepted Solution

    no solution was found

    Author Closing Comment

    No answer worked

    Featured Post

    What Is Threat Intelligence?

    Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

    Join & Write a Comment

    VM backup deduplication is a method of reducing the amount of storage space needed to save VM backups. In most organizations, VMs contain many duplicate copies of data, such as VMs deployed from the same template, VMs with the same OS, or VMs that h…
    The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
    To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

    745 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now