Windows 2012 Backup for HyperV failed with error code '0x80780049'

All replies

• 

  

  0

  Sign in to vote

  trying to backup VM run SQl server 2008 in cluster enviroment on Windows 2012 HyperV Host. Using windnows backup utility backing upda HyperV companent and VM failed wit the follwoing error: event id 517:

  The backup operation
  that started at '‎2012‎-‎10‎-‎25T22:29:46.631794000Z'
  has failed with following error code '0x80780049' (None of the items included
  in backup were backed up.). Please review the event details for a solution, and
  then rerun the backup operation once the issue is resolved.

  detail info from Windows Backup utlity:

  >>>>

  Writer Failures
  Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
  Instance Id: {4DC1EF04-0A7E-4223-91D6-2A831F52DCFE}
  Writer Name: Microsoft Hyper-V VSS Writer
  Writer State: 0
  Failure Result: 81000112
  Application Result: 0
  Application Message: (null)
     Component: Host Component
     Logical Path:
     Component Result: 8100010F
     Component Message: Component reports path on volume which has been excluded. (0x8100010F)
     Component: 692CFC20-574A-4B26-8A33-9FD4BFA767CA
     Logical Path: (null)
     Component Result: 800423F3
     Component Message: (null)
         File Spec: D:\VMLive\SQL Cluster Node Two\Virtual Machines\\692CFC20-574A-4B26-8A33-9FD4BFA767CA.xml Recursive: 0
         File Spec: D:\VMLive\SQL Cluster Node Two\\SQL Cluster Node Two.vhd Recursive: 0
  *-----------------------------*

  
  Application backup
  Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
     Component: 692CFC20-574A-4B26-8A33-9FD4BFA767CA
     Caption     : Backup Using Child Partition Snapshot\SQL Cluster Node Two
     Logical Path:
     Error           : 80780175
     Error Message   : Component was skipped from volume shadow copy.

     Detailed Error  : 800423F3
     Detailed Error Message : The writer experienced a transient error.  If the backup process is retried,
  the error may not reoccur.

  Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
     Component: Host Component
     Caption     : Host Component
     Logical Path:
     Error           : 80780175
     Error Message   : Component was skipped from volume shadow copy.

     Detailed Error  : 8100010F
     Detailed Error Message : Component reports path on volume which has been excluded.

  *-----------------------------*

  >>>>

  thanks

  Hussainn

  • Merged by Lawrence,Lu Tuesday, October 30, 2012 8:56 AM Duplicate

  Friday, October 26, 2012 2:43 AM
• 

  

  0

  Sign in to vote

  Hi!

  From your descpription, it sounds like you're trying to perform an online backup of a virtual machine that is a member of a SQL failover cluster in a guest environment.

  Online backup requires that all hard disk files specified in the VM config are NTFS formatted and online (so that the guest VSS can perform shadow copies of the drives and present to the Hyper-V VSS writer through integration services).

  If the VM has cluster storage (iScsi or fibre channel) this could become a problem, if the VM is not the current owner of the disks, they will be offline in the guest disk manager. If there are two nodes in the guest cluster, you most likely have setup a quorum disk and if there is no NTFS formatted partition on it, it will cause the entire backup operation to fail.

  Further more, the cluster disks are most likely attached to from inside the VM, so if they're not in the VM configuration, Hyper-V VSS writer will most likely not be looking for them through IS. I can't say that this is a fact, since I'm not sure.

  You can find a list of requirements in order to perform online VM backups on Robert Hedbloms blog: http://robertanddpm.blogspot.se/2011/06/offline-vs-online-backup-of-hyper-v.html

  He doesn't cover guest clustering in detail, but cluster disks have a tendency of being moved between nodes now and then, so the online requirements apply.

  Or if you mean that the Hyper-V host itself is a member of a failover cluster, then you shouldn't be using WSB for clustered VMs. You should check out DPM or another backup solution that is cluster aware.

  • Edited by Mike_Andrews Sunday, October 28, 2012 6:40 PM

  Sunday, October 28, 2012 6:37 PM
• 

  

  0

  Sign in to vote

  thanks Mike,

  HyperV host is not in the cluster enviornment.  The VM is on the 2012 HyperV Host on the second RAid spindle which is using the new ReFS format.  Is that would cause the issue as you mentioned it has to be on NTFS partition???

  thanks

  Monday, October 29, 2012 3:07 PM
• 

  

  0

  Sign in to vote

  No, I don't think that is the issue. I haven't come across any documentation on backing up VMs residing on ReFS partitions, but what's important is that the partitions inside the vhd files are NTFS formatted.

  I think the real issue is how the VM connects to the disk, since it's in a guest cluster and probably not specified in the VM configuration. Please confirm if this is the case. Hyper-V is unaware of the extra disks inside the VM since it has no record on vhd file GUIDs.

  Monday, October 29, 2012 4:38 PM
• 

  

  0

  Sign in to vote

  I think i have found the issue.

  the server was running low on the memory. Only 3 GB memory was avaiable to the Host (it has GUI component installed).

  I am plannig to run the backup again and will update you.

  thanks

  Monday, October 29, 2012 8:05 PM
• 

  

  0

  Sign in to vote

  Sorry. NO luck. It failed. If the SQL node is passive (none of the serivces are running) VM backup is sucessfull.

  Planning to contact Microsoft support team on the issue.

  thanks

  Wednesday, October 31, 2012 5:44 PM
• 

  

  0

  Sign in to vote

  found the issue.  as the vm was moved from HyperV Host 2008 R2, it never prompt to update the HyperV integration service.

  Updating the 2012 HyperV Host Inegration service resolve the issue.

  thanks

  husssain

  • Marked as answer by hlakhani Thursday, November 1, 2012 2:01 AM

  Thursday, November 1, 2012 2:01 AM
• 

  

  1

  Sign in to vote

  Hi everyone, 

  In my case I am running Windows Server 2012 Hyper-V and backup was being done using Windows Server Backup. Solution in my case was to recreate the backup job - nothing else I tried worked up to this step. Completely removing and recreating the scheduled job fixed the issue without rebooting or restarting anything. 

  I suspect that adding a new VM to the stand-alone hypervisor (in my case) messed up the VSS writer registrations somehow. You can read more about this here: http://www.flexecom.com/hyper-v-2012-vss-backup-failing-with-error-code-0x80780049/

  Cheers, 

  Dennis Suhanovs

  
  

  • Edited by Dennis Suhanovs Tuesday, February 12, 2013 6:26 PM added link

  Tuesday, February 12, 2013 6:25 PM
• 

  

  0

  Sign in to vote

  Hello Dennis,

  first of all thank you very much for posting your solution on flexecom.com. This saved my a**. We use 2 Hyper-V 2012 to replicate their machines to each other. Every Hyper-V has a private iSCSI LUN for its VMs. I can reproduce the backup failure arbitrarily:

  1. Perform a planned failover to the second machine, e.g. for maintenance purposes.
  2. Failback to the original machine
  3. Start the backup of the original machine.

  -> ERROR

  Since this so easily to produce, has anybody else this problem? Has anybody (you Dennis?) reported this bug to Microsoft?

  Sunday, March 24, 2013 1:20 PM
• 

  

  0

  Sign in to vote

  Hello all,

  I am experiencing the same problems. Using a Synology NAS providing an iSCSI lun as a backup device, however the VM's are running on a local SSD raid device. Whenever the host is rebooted the backup fails. The only way to solve this is remove the backup definition and create a new one. So that makes me think there is nothing wrong in the VM, but in the connection of the lun for backup.

  Remco Bosman

  Wednesday, April 10, 2013 2:45 PM
• 

  

  0

  Sign in to vote

  It seems problem with HP Provisioning , I shrink C:drive by 100MB and re run the backup. it worked for me

  Sunday, September 17, 2017 7:45 AM