After several weeks of trying, the backup (wbadmin) doesn't work from the task scheduler.  When I enter the WBADMIN Start Backup command directly into a command prompt, it executes perfectly and backs up everything it's supposed to, but for some reason, when that EXACT SAME COMMAND is executed from the task scheduler it starts, then immediately stops.  I opened the Task Scheduler, clicked on "Task Scheduler Library" in the left pane, and looked at the backup job in the top window of the center pane.  The "Last Run Result" column simply showed, "(0xFFFFFFFF")".  I also clicked on the job's History Tab, which showed 7 entries at the date/time the job is set to trigger, which indicated that the task started and completed, "successfully" within the same second (i.e. 01:00:00), but absolutiely nothing is backed up, nor are there any entries for the trigger date on the backup drive.

This has happened four Sundays in a row, and each time, when I subsequently execute the WBADMIN command from a command prompt, it works correctly.  Any ideas about what I'm missing and/or doing incorrectly

Hi,

From your description, it is more likely related to the issues of task schedule instead of Wbadmin command.

Check the following article for possible solution.

http://zetconsultants.com/blog/?p=44

if you want to Customize Windows Server Backup Schedule, please check the following article.

http://blogs.technet.com/b/filecab/archive/2009/04/13/customizing-windows-server-backup-schedule.aspx

Configure Automatic Backups with Task Scheduler

http://technet.microsoft.com/en-us/library/dd834883

Thanks Jeff, but unfortunately, I've already done all those things from advice in a previous thread.  The task scheduler DOES schedule the task, and my History is not disabled. But when the Task Scheduler starts, it then stops immediately with two log entries: 1) "Action Completed", and in the lower history window "Task Scheduler successfully completed the task ...", and 2) a log entry saying "Task Completed", and in the lower history window, "Task Scheduler successfully finished...", but NOTHING is backed up.  I've gone through the task scheduler settings for the task, and everything seems ok, but no dice.  Yet, I can enter the EXACT SAME wbadmin command into a command prompt, and the backup works fine.

Here's the actual "SCHTASKS" command that I entered to schedule the job:

SCHTASKS /Create /SC  WEEKLY /D SUN /TN CTServerWeeklyBackup /RL Highest /ST 01:00 /TR "WBADMIN START BACKUP -backupTarget:f: -allCritical  -include:C:\,D:\CAB\,D:\Downloads\,D:\Extracts\,D:\SSLCert\,D:\Temp\,U:\CAB\,U:\Shares\,U:\Temp\  > C:\backupLogs.txt"

The above command executed without incident, then I immediately checked the task scheduler, and the task was there, properly scheduled.  When the trigger time/day occurred, the task simply started then immediately stopped, yet when I enter just the WBADMIN command into a command prompt, it executes correctly, completely and without incident.

As your problem does not relates to Windows Server backup utility or Backing up functionality in Microsoft Windows, for better support, I recommends you to ask your question in Windows General forum at http://social.technet.microsoft.com/Forums/en-US/winservergen/threads

Thanks, I'll do that.

@creacontech I've exactly the same issue as you've described when running scheduled WBADMIN task. I was wondering if you were successful in resolving the issue.

Please send your feedback.

Yes, I was successful, in a manner of speaking.  I simply did an end run, and it worked.  I put the WBADMIN command into a .bat file and scheduled that, and it works.  Go figure.

There's another problem, with this, however.  I can't get WBADMIN to back up individual files that can be restored without having to restore the whole system image.  I tried executing a WEBADMIN command containg ONLY the files that I may need to restore individually on occasion, AND WITHOUT THE "ALL CRITICAL" parameter, but it didn't work.  I'm still trying different approaches, but so far no luck.  So to solve that problem, and least until I can find a better way, I used WinZip 16.5 to create a "JOB" that zips and backs up those files, and scheduled that from within WinZip.  It works OK, but I'm still trying to find a way to do it all with WBADMIN.

I'll have two external drives: one for system image, bare metal, etc and one for data. Everything will be tested on Wednesday and see.

Thank you

I recently came across this same Last Run Result code in combination with wbadmin and the Task Scheduler. The Task Scheduler history indicates that the task ran perfectly, but the result code, (0xFFFFFFFD), and the fact my backup VHDs do not have a new modified date, say another story.

A quick look into the Event Viewer and my suspicions were confirmed. My main OS drive only has ~35GB free and since my two backup drives are the same size as the OS drive (500GB each), they have even less free space. The error in the Event Viewer listed this as the message:

The backup operation attempted at '2013-12-23T15:48:42.188671700Z' has failed to start, error code '2155348040' (There is not enough free space on the backup storage location to back up the data.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

add -quiet parameter to the task