Windows Image Backup Server Error 0X807800C5

Problem :

Windows Image Backup is failing while backing up a drive. In my case, it was a "bare metal" backup scenario. You may also find the following error in the "Event Viewer" under "Applications and Services Log, Microsoft, Windows, Backup"


"The backup operation that started at '‎2014‎-‎05‎-‎13T16:49:41.618242900Z' has failed with following error code '0x807800C5'
(There was a failure in preparing the backup image of one of the volumes in the backup set.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved."

Description;

I think this is happening because of the VSS function. I couldn't find anything official but I have a feeling that when the backup tries to create a snapshot of the volume, it doesn't have enough allocated space on the drive to create the full snapshot. After a couple of blogs on the web, I cross people suggesting to shrink the drive and leave around 10GB of unallocated space.

So if you already have the full space "allocated" to the volume, your problem might just be that. You need to have a little bit of unallocated space.

Solution;

Go to "Computer Management, Storage, Disk Management" right click on the volume you want to shrink and choose "Shrink Volume". Decide how much you want to shrink the disk and apply. Be careful! Make sure you have a backup of the volume or data before you proceed with this procedure as during this process you might loose data!!! (Did it ever happened to me before?? Never! But I would rather warn you!)


A second place to look is the "limit" of the shadow copies. Right click on one of your drives in "Windows Explorer" and click on "Configure Shadow Copies". Choose the disk you want to activate the "shadow copies" and click on "settings". Check the option "No Limit". I don't know what difference this makes for the Windows Image Backup but in my case, this little option was the problem. Unfortunately, I had to dedicate a full disk for this purpose because I didn't want to make a full disk with the "No Limit" option. Have a look at these conversations at TechNet Forums for details;


http://social.technet.microsoft.com/Forums/windowsserver/en-US/fb9298fe-24c3-4ddf-9aa3-16f6b2ae3ad0/server-2012-wbadmin-backup-failing-the-mounted-backup-volume-is-inaccessible?forum=windowsbackup

Note: This procedure worked like a charm under a Windows Server 2012 R2 but it is also applicable to Windows 7, 8, 8.1 or Server 2008, 2008R2...
Location: Montreal, QC, Canada

Comments

Post a Comment

Popular posts from this blog

System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation (Public Queue create issue)

This is a weird issue that I don't fully understand why it would happen. But the symptoms are very persistent as we're able to reproduce these behavior easily. Issue: The MSMQ (Microsoft Message Queuing) fails to create Public Queues and throws  "the System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation" exception.
Read more

Veeam Backup Error : Failed to prepare guest for hot backup. Error: VSSControl

Image
Problem Description; I had this issue on one of my backup jobs recently and I was able to fix the issue with the solution explained below. After a quick google search, I realized that I'm not the only one and neither you are :) Full Error Description; Failed to prepare guest for hot backup. Error: VSSControl: Failed to prepare guest for freeze, wait tim eout 9 00 sec Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec
Read more

warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead - Chef Development Kit Update

Today, I needed to do some tests with a newer version of the Chef Client and test my cookbooks. To version 14.12.9-1 to be precise. I also upgraded my ChefDK on my workstation to the 4.2.0 version. I believe that upgrades Ruby version as well and now I have ruby version 2.6.3p62 Right after the upgrade, I tried with a basic knife node list command to see if I needed to reboot or anything was broke... Everything seems to be working fine, except I get this annoying "warning" message. As it's just a warning, I don't really care about it as it just seems to annonce something that is deprecated... Problem; You receive "warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead" warning when using ruby or chef knife commands. Solution; You need to comment out that warning message in Ruby lib scripts.
Read more