Adventures in Backup – continued

Adventures in Backup – continued

  • Comments 25

Two weeks ago I discussed some bad experiences I had with Hyper-V + backup.  Since then I have spent a bunch of time setting up Hyper-V + backup on a couple of systems – and none were as problematic as my first attempt.  I have also setup my home Hyper-V server to perform nightly backups – which have been proceeding without a hick up:

image

However a lot of you let me know that you too had seen issues with backup and Hyper-V.  As such I would like to invite anyone who sees a failed Hyper-V backup to come here and let me know in the comments what the cause of the failure was – you can usually figure this out by looking in the Hyper-V event log (as I did in my original blog) – so that we can try to help each other out here.

Cheers,
Ben

Leave a Comment
  • Please add 6 and 3 and type the answer here:
  • Post
  • Has anyone been able to resolve this issue?  I have a server that took three hours to boot and seems to be related to this issue.  Microsoft tech that I worked with had no info about this problem.

  • Sorry for the radio silence - we have reproduced the "growing registry / slow boot" problem and are looking into what we can do to fix it.

    Tom - feel free to tell the support engineer to contact me (BenArm) and I will get him the right information.

    Cheers,

    Ben

  • Hi All,

    We have just released a hot fix for the "large registry / slow boot" problem:

    blogs.msdn.com/.../hotfix-hyper-v-backup-can-cause-slow-system-boot-large-registry-files.aspx

    Cheers,

    Ben

  • Thanks for the news.

    Unfortunatly, my saga of migrating my working environments physical Win7 x86 and virtual Win2k under Windows Virtual PC to Hyper-V is far from over. Win7's system image doesn't boot as Hyper-V guest (famous STOP 7B), continously and unsuccessfully trying to repair Windows installation. Win2k VHD doesn't boot with STOP 1E. Also I've used Paragon Virtualization 2009 Personal to create Win7 VHD from working machine - the same STOP 7B.

    There is trouble even with VHD from some other server created for it's bare-metal recovery. Connected VHD image silently blinks cursor on the screen and eat 8-10% CPU and that is all.

    Moreover any attempt to do a system image recovery from Windows Recovery Environment on Hyper-V guest is failing with message:

    "The system image restore failed

    No disk that can be used for recovering  the system disk can be found (0x80042412)"

    And I haven't found useful info about restoring of system image to other or virtual hardware on the net. It seems that noone have even tried.

    Did I miss something? What else should I try to move to Hyper-V? May be try capture from SCVMM?

  • i had the following in the application log on a VM which would not backup, this turned out to be a Integration tools version issue after moving the Vm from a 2008 to 2008 r2 host.

    logname: application       source: VSS           Event ID: 8193

    Volume shadow copy service rerror: Unexpected error calling routine IVssbackupcomponents;;;;setcontextinternal. hr = 0x80042301

    operation:add a volume to a shadow copy set           context: execution content:requestor

  • [Written based off of reading the original article, not considering other comments]

    It is because of the new disk configuration (and different accompanying Disk Controller Hardware) that causes the restore to fail.  Doing this with with Windows Server Backup is really no different than imaging the whole thing with something like Ghost and then applying the image to the new Drive Setup and expecting it to boot up.

    You need to backup all the VMs and any other needed material.  Then Load the OS clean from scratch on the new Drive Setup,...then restore all the VM and the material.  Basically this is the same thing as dealing with a failed machine when you are forced to restore on to Dissimilar Hardware (which just is another way of saying that you can not restore).  In fact the Drive Controllers and Drive Arrangement is the primary thing that causes hardware to be considered "dissimilar" or "incompatible".

    phillip.windell@wandtv.com

    phillip.windell@live.com

  • My issue is we have a remote virtual machine, lets call it VS-SERVER2 which is running Linux, so doesn't have the option of using Windows Server Backup. I've tried to backup this server remotely from our main virtual server - VS-SERVER1 - using the same commands as you use to backup the local drive, but with the remote c drive: wbadmin.exe start backup -quiet -backuptarget:E: -include:\\VS-SERVER2\c: -allcritical -vssFull but the error:

    ERROR - The path specified by '\\VS-SERVER2\C:' was not found.

    The specified file path does not exist or is not on a locally attached disk.

    I also tried mapping the C:\ of VS-SERVER2 to E:\ on the local machine, but the same error occurs.

    Is there a way around this? or an alternative way top backup a virtual machine on a Linux box?

  • So, following Ben's advice, after receiving error 0x80042336 (VSS error, WBADMIN backup failed) I checked Hyper-V's logs (Event Viewer / Custom Views / Server Roles / Hyper-V) which had an error listed (ID in source column: Hyper-V-VMMS) that indeed indicated a failure inside a VM at the time of the backup attempt.

    Now, obviously, the particular problem could be different for everyone. Fortunately, in my case it turned out to be something easily managable:

    After logging into the particular VM, immediately a pop-up welcomed me saying that the VM's memory swap file had problems. Turned out the VM had no free space left. Freed up some space, recreated the swap file and had no problems afterwards backing up the whole server along with the VMs. All my attempts before this correction have failed to start a backup process (scripted WBADMIN).

  • I get this on multiple servers over and over on Server 2012 (not R2, although that's my next step):

      Error           : 80780176

      Error Message   : The specified component was not reported by the VSS writer.

    Someone suggested ensuring integration services are up to date on all VMs.

  • Alistair -

    It sounds like this error comes from Windows Server Backup if you create a backup job for all of the VMs and then latter add or remove a VM.  Solution is to recreate the backup job.

    Cheers,

    Ben

Page 2 of 2 (25 items) 12