Windows Server Backup Fails On Scheduled Task


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.
Who is Participating?
dilesAuthor Commented:
no solution was found
is it a virtual server?

Maybe some of the steps in this EventID can help isolate the cause:
dilesAuthor Commented:
The server itself isn't virtual, it just backs up to a virtual drive.

Thanks for the reply, I'll take a look.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

dilesAuthor Commented:
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.
dilesAuthor Commented:
Backup failed again, at least it's getting to about 11.34gb now but then failing with the same error as before.
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
dilesAuthor Commented:
No answer worked
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.