locked
Wbadmin and Hyper-V RRS feed

  • Question

  • Is it possible to run wbadmin on a host S2008 server without it killing off the running Hyper-V guests?

    Currently we have a S2008 host server that runs a variety of services. At the beginning we had not planned on using Hyper-V on this server but plans changed and 3 virtual machines were added. The scheduled backup via wbadmin that currently runs kills off the one always on virtual machine and I need to find a way to both do the backup on the host and not kill off the virtual machine.

    Eventually we will probably redo the works and move everything over to virtual machines but for now we need to come up with what ever the best possible solution is.

    I've done some checking on hyper-v and wbadmin but I'm not finding anything applicable to our situation.

    I've also done some quick checking on the possibility of scripted or scheduled shutdown/startup of the virtual machines but I've been striking out on that front as well.

    Anyone have any thoughts, advice, or direction for me to look into?
    Tuesday, January 6, 2009 6:46 PM

Answers

  • Hi,

     

    Before we go any further, I’d like to briefly explain Hyper-V guest machine backup. There are two types of backup for Hyper-V virtual machines, online backup and offline backup. An online backup can be performed with no downtime on a running virtual machine. If an online backup cannot be performed, then an offline backup is taken. This type of backup results in some degree of downtime. If the virtual machine is running or paused, it is put into a saved state as part of the offline backup process. After the backup is completed, the virtual machine is returned to its existing state. For more information, please refer to the following link:

     

    Backing Up Hyper-V Virtual Machines

    http://blogs.technet.com/virtualization/archive/2008/08/29/backing-up-hyper-v-virtual-machines.aspx

     

    As we can see from the above Hyper-V description, it should not cause guest machine unexpected shutdown. This problem may be related to the specific guest instead of Hyper-V. From your description, you received the 6008 error. Here I’d like to confirm whether the event 6008 happens on the same time when you perform backup for the guest machine. To isolate the root cause, I suggest that you perform the following tests:

     

    1.    Install the latest service pack and updates on the Windows Server 2008 guest machine.

    2.    Please build a clean Windows Server 2008 guest machine and install Integration Service on the guest to see whether the problem exists for the newly created guest. In this way, we can isolate the root cause.

    3.    Please disable “Automatically restart” option on the guest machine so that the machine will not be rebooted automatically if a blue screen error occurs.

     

    1)    Right click My Computer, and click Properties.

    2)    In the Advanced tab, click the “Settings” button,

    3)    Uncheck the “Automatically restart” option, and click OK.

     

    By the way, although the following hot fix is not directly related to this issue, I still suggest that you download and install it on the Hyper-V host machine:

    960038  You receive a "0x0000007E" Stop error on Windows Server 2008-based computers that host Hyper-V virtual machines when you use the Hyper-V writer to back up virtual machines

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;960038

     

    Best Regards,

    Vincent Hu

    Tuesday, January 13, 2009 8:35 AM

All replies

  • Hi,

     

    In your description, you mentioned that running guest machines are “killed off” when wbadmin is run. Here I’d like to confirm the exact symptom. Do you mean that during these virtual machines go into Saved state when Windows Server Backup is run. If I have misunderstood your concern, please feel free to let me know.

     

    Based on my research, a running guest machine will go into Saved state in the following situations:

     

    1, The guest operating system doesn't support VSS. Windows operating system which before Windows Server 2003 do not support VSS (including Windows Server 2000 and Windows XP).

    2, If the operation system support VSS, you haven't installed the Integration Services in the virtual machine or, you didn't enable it.

    3, The guest operating system has some Dynamic Disks (not to be confused with Dynamically expanding disk).

     

    Please perform the following steps to check if the guest operating system supports VSS:

     

    1. Install Integration Services on the guest machine if it is not installed.

     

    2. If you have installed Integration Services in the virtual machine, please check if you have enabled the related Integration Services as follows:

     

    2.1 Right-click the File menu in the VM Connection interface and click Settings….

    2.2 Select the Integration Services under Management area and in the right hand pane, see if the "Backup (volume snapshot)" has been checked.

    2.3 In the virtual machine, open the Services console, see if the "Hyper-V Volume Shadow Copy Service" has been Started.

     

    3. Check whether the guest operating system contains any Dynamic Disks (compared with Dynamically expanding disk which you can add as a VHD to the virtual machine). Please note that there is a limitation of LDM database that dynamic disks don't support VSS. Please refer to the following document for general information on this:

     

    http://download.microsoft.com/download/2/e/7/2e7387d3-1391-4176-abe8-44e481100694/relnotes.htm

     

    By the way, we don’t recommend that you run other applications on the Hyper-V machine. This will provide a clean environment for Hyper-V. Because some applications may cause unexpected error.

     

     

    Best Regards,

    Vincent Hu

    • Marked as answer by Vincent Hu Monday, January 12, 2009 2:03 AM
    • Unmarked as answer by Nchow Monday, January 12, 2009 2:20 PM
    Thursday, January 8, 2009 3:52 AM
  • 1. Server 2008 Standard is the OS - support for VSS, check
    2. Integration Services installed and enabled (everything is checked), check
    3. Disk is basic and fixed, check

    I should have been more specific in my initial post. On the VM, in the System event log, an error occurs directly after the host server backup is initiated. In the guest VM, in the System event log, an error 6008 occurs for a unexpected shutdown.

    I assume an unexpected shutdown is not a graceful shutdown? I see no other errors.

    Where would it tell me if it is being put into a saved state? I assumed the backup would save the state, backup and then resume from where it saved its state but this error has me thinking its actually restarting. Which is what I don't understand. Also in the Security log and event id 1101 occurs saying "Audit events have beend ropped by the transport. The real tiem backup file was corrupt due to improper shutdown". Which makes me believe the system is being shutdown in a non-graceful manner.
    Monday, January 12, 2009 2:20 PM
  • Hi,

     

    Before we go any further, I’d like to briefly explain Hyper-V guest machine backup. There are two types of backup for Hyper-V virtual machines, online backup and offline backup. An online backup can be performed with no downtime on a running virtual machine. If an online backup cannot be performed, then an offline backup is taken. This type of backup results in some degree of downtime. If the virtual machine is running or paused, it is put into a saved state as part of the offline backup process. After the backup is completed, the virtual machine is returned to its existing state. For more information, please refer to the following link:

     

    Backing Up Hyper-V Virtual Machines

    http://blogs.technet.com/virtualization/archive/2008/08/29/backing-up-hyper-v-virtual-machines.aspx

     

    As we can see from the above Hyper-V description, it should not cause guest machine unexpected shutdown. This problem may be related to the specific guest instead of Hyper-V. From your description, you received the 6008 error. Here I’d like to confirm whether the event 6008 happens on the same time when you perform backup for the guest machine. To isolate the root cause, I suggest that you perform the following tests:

     

    1.    Install the latest service pack and updates on the Windows Server 2008 guest machine.

    2.    Please build a clean Windows Server 2008 guest machine and install Integration Service on the guest to see whether the problem exists for the newly created guest. In this way, we can isolate the root cause.

    3.    Please disable “Automatically restart” option on the guest machine so that the machine will not be rebooted automatically if a blue screen error occurs.

     

    1)    Right click My Computer, and click Properties.

    2)    In the Advanced tab, click the “Settings” button,

    3)    Uncheck the “Automatically restart” option, and click OK.

     

    By the way, although the following hot fix is not directly related to this issue, I still suggest that you download and install it on the Hyper-V host machine:

    960038  You receive a "0x0000007E" Stop error on Windows Server 2008-based computers that host Hyper-V virtual machines when you use the Hyper-V writer to back up virtual machines

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;960038

     

    Best Regards,

    Vincent Hu

    Tuesday, January 13, 2009 8:35 AM