locked
No snapshots to revert were found for virtual machine 'VMNAME'. (Virtual machine ID VMID) RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I have windows server 2008 r2 with hyper-v installed

    When i try to take backup using windows server backup getting following error

    No snapshots to revert were found for virtual machine 'VMNAME'. (Virtual machine ID VMID)

    I have 5 vms, 4 using dynamic vhds and 1 using iscsi passthrough drive.

    For all 4 dynamic vhd vms i am getting above error.

    There is no snapshot taken for any of this vms

    Also server 2008 r2 is upgrade from 2008 fyi


    Anyone could please help me figureout what's wrong in there?


    • Edited by mamu001 Tuesday, September 8, 2009 12:51 AM
    Monday, September 7, 2009 6:01 PM

Answers

  • Question
    Sign in to vote
    4
    Sign in to vote

    Vincent et al,

    Preliminary findings demonstrate that when automatic mounting of new volumes is disabled on Windows 2008 Hyper-V Host systems, then online backups of (capable) Guest systems will fail.   Automatic fallback to an offline Guest backup is not attempted.  Planning for Backup: http://technet.microsoft.com/en-us/library/dd252619(WS.10).aspx.

     

    How to obtain and change the Mount Manager setting for automatic mounting of new volumes:

     

    DISKPART

    * Automount         - reports the current setting for automatic mounting

    * Automount Enable  - enables automatic mounting

    * Automount Disable - disables automatic mounting

     

    MOUNTVOL

    * MOUNTVOL /N - disables automatic mounting

    * MOUNTVOL /E - enables automatic mounting

     

    REGISTRY

    * HKLM\SYSTEM\CurrentControlSet\Services\MountMgr\NoAutoMount

    * 0 - enables automatic mounting

    * 1 - disables automatic mounting

    Hope this is helpful,
    Mark.

    • Proposed as answer by marcusolini Saturday, September 26, 2009 8:16 PM
    • Marked as answer by mamu001 Monday, September 28, 2009 10:52 PM
    Saturday, September 26, 2009 8:16 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Do you have the integration components installed and what are the guest VM's?  Also are the VM's up and running at the time of backup?

    Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP Managing Consultant VSD Technologies
    Monday, September 7, 2009 6:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, integration components are installed and all gues vm's are server 2008. 
    Yes, all VM's are up and running at time of backup.

    For try i had turned off all VM's and tried backup but had same result.
    Tuesday, September 8, 2009 12:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    By any chance did you look at this KB?  there is a change that needs to take place in the registry to register the VSS service with windows backup.

    http://support.microsoft.com/kb/958662

    EDIT Nevermind.. Does not apply to R2.

    Where are you backing up to a remote share?  If so do you have permissions on that share?
    Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP Managing Consultant VSD Technologies
    Tuesday, September 8, 2009 1:39 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

     

    Did you upgrade from RTM to R2? This is a known issue with Windows Server backup on systems that have been upgraded from RTM to R2. Our product group is working on this.

     

     

    Best Regards,

    Vincent Hu

     

    • Marked as answer by Vincent Hu Monday, September 14, 2009 10:59 AM
    • Unmarked as answer by mamu001 Wednesday, September 16, 2009 4:02 AM
    Tuesday, September 8, 2009 9:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have tried backup to share as well as dedicated disk, both fails.
    Tuesday, September 8, 2009 2:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Please reinstall you Hyper-V host machine and then test whether it works. 

     

    Best Regards,

    Vincent Hu

    Thursday, September 10, 2009 2:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    That is not an option, i can't reinstall host as it's on production. 

    Any idea what is the problem area here? 
    Thursday, September 10, 2009 2:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    I understand that it will be inconvenient for you to reinstall the Hyper-V host machine. However, this issue will be fixed in next version of Windwos Server. So, if possible, it is recommend that you have a reinstallation of the Hyper-V host machine.

    Best Regards,

    Vincent Hu

    • Marked as answer by Vincent Hu Monday, September 14, 2009 10:59 AM
    • Unmarked as answer by mamu001 Wednesday, September 16, 2009 4:02 AM
    Friday, September 11, 2009 8:10 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Do i need to restall host os or just hyper-v will do the work?
    Friday, September 11, 2009 7:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Do i need to restall host os or just hyper-v will do the work?

     

    >>> You have to reinstall the Hyper-V host machine.

     

    Best Regards,

    Vincent Hu

     

     

    Monday, September 14, 2009 10:58 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    OK I have made little progress here

    I followed following steps

    Deleted all vms 
    Uninstalled Hyper-v
    Tried backup - IT WORKED
    Installed Hyper-v
    Tried backup - IT WORKED
    Created all vms again using old vhds but new virtual machines from scratch
    Tried backup - It failed with same error as thread header
    Shutdown all vms
    Tried backup - IT WORKED(It wasn't working with this state before)


    All VMs are server 2008
    I wanted to verify that latest integration service is installed in guests so tried to reinstall it and it prompted i have previous version of integration service.
    Although i had installed latest before, but i tried again it completed(No reboot prompt). 
    Then i tried again just to make sure what it says, it still says i have previous version of integration service. 
    I tried few times but it keep telling me i have previous version.

    Is it issue with r2? How can i uninstall hyper-v integration service completly? I am clueless what could be wrong here, any help is appreciated.

    I tried setup.exe /uninstall to uninstall, it does not unstall but just prompts for upgrade or repair integration service.

    Vincent, As backup is working with guest shutdown, I think there is nothing wrong with host now so not thinking about reinstalling Hyper-v host machine.



    Wednesday, September 16, 2009 4:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Vincent,

    Can you please elaborate on this limitation that affects Windows Server backup and also affects other 3rd Party Backup Software?

    Is there an existing article that describes this issue?

    When and how would a fix be provided?

    Are there any alternate workarounds or solutions?
    * Especially, besides re-installing.
    * Besides manually or scripting Turn Off of the Guest.
    * Besides manually or scripting Save State of the Guest.
    * Besides automatic Save State of the Guest (by removing Integration Services - Backup) (or legacy Registry Key).

    Appreciate any details and help you can provide.

    Regards,
    Mark.

    Wednesday, September 23, 2009 11:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    This issue was confirmed by our product team. If you use Windows Server Backup to backup the VMs, you may encountered this issue mentioned in this post. Unfortunately, there is no information about the limitation affects other third party backup software.

     

    As far as I know, this is no plan to develop a hot fix for this, this issue will be resolved in next version of Windows Server. Thanks for your understanding.

     

     

    Best Regards,

    Vincent Hu

     

    Thursday, September 24, 2009 3:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Wait a minute Vincent ...

    We use DPM2007 to protect our RTM Hyper-V virtual machines.

    I upgraded two test Hyper-V servers to R2 and put some Hyper-V virtual machines on them to test DPM, and I'm getting this issue on one of the servers. You're saying the only resolution is to rebuild our production servers using R2, rather than a simple upgrade? In whose mind is that acceptable and therefore doesn't need a fix before the next edition of Windows Server??

    Incredulously,

    Tony

    Thursday, September 24, 2009 4:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Tony,

     

    Thanks for you posting.

    This is a known issue with Windows Server backup on systems that have been upgraded from Windows Server 2008 RTM to Windows Server 2008 R2 RTM. However, as we mainly focus on the General question about Windows Server system so I don’t know whether the DPM has been involved. As your issue is more related to DPM, it is recommend you to get further support in the corresponding community so that you can get the most qualified pool of respondents. Thanks for your understanding.

     

    For your convenience, I have list the related link as followed.

     

    Virtual Machine Manager – PRO/SC integration

    http://social.technet.microsoft.com/Forums/en-US/virtualmachinemgrproscintegration/threads

     

     

    Best Regards,

    Vincent Hu

     

    Friday, September 25, 2009 3:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Vincent,

    Thanks for the link, but this is a Windows 2008 R2 issue, not a DPM issue - DPM merely leverages VSS on the 2008 R2 server. One interesting thing is that I have two R2 Hyper-V hosts, but only one of the two has this VSS error - the other one has no problems.

    Any advice on how to troubleshoot VSS further to see where the difference might be?

    Thanks
    Tony
    Friday, September 25, 2009 9:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Vincent,

     

    Firstly, just want to thank you and the other posters for the continued interest and willingness to discuss this important concern.

     

    Without getting into all the details, we are experiencing this failure on new installations of Windows Server 2008 R2 (6.1.7600) Hyper-V Hosts with new Guest installations, such as, Windows 7 Ultimate with updated integration components.  So this does not appear to be limited to Windows 2008 upgrades to Windows 2008 R2 as is being characterized.

     

    Additionally, the VSS command-line tool VSHADOW.EXE can be used to independently reproduce the failure on affected systems (http://msdn.microsoft.com/en-us/library/bb530725(VS.85).aspx?ppud=4).

     

    Regards,

    Mark.

    • Proposed as answer by marcusolini Saturday, September 26, 2009 8:15 PM
    Friday, September 25, 2009 9:37 PM
  • Question
    Sign in to vote
    4
    Sign in to vote

    Vincent et al,

    Preliminary findings demonstrate that when automatic mounting of new volumes is disabled on Windows 2008 Hyper-V Host systems, then online backups of (capable) Guest systems will fail.   Automatic fallback to an offline Guest backup is not attempted.  Planning for Backup: http://technet.microsoft.com/en-us/library/dd252619(WS.10).aspx.

     

    How to obtain and change the Mount Manager setting for automatic mounting of new volumes:

     

    DISKPART

    * Automount         - reports the current setting for automatic mounting

    * Automount Enable  - enables automatic mounting

    * Automount Disable - disables automatic mounting

     

    MOUNTVOL

    * MOUNTVOL /N - disables automatic mounting

    * MOUNTVOL /E - enables automatic mounting

     

    REGISTRY

    * HKLM\SYSTEM\CurrentControlSet\Services\MountMgr\NoAutoMount

    * 0 - enables automatic mounting

    * 1 - disables automatic mounting

    Hope this is helpful,
    Mark.

    • Proposed as answer by marcusolini Saturday, September 26, 2009 8:16 PM
    • Marked as answer by mamu001 Monday, September 28, 2009 10:52 PM
    Saturday, September 26, 2009 8:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I can verify Mark's findings - the 2008 R2 server successfully backing up had Automount enabled, and the one that was failing had Automount disabled. Enabled it, and both servers now back up successfully.

    Thanks Mark - Great job!

    Tony
    Monday, September 28, 2009 2:22 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Enabled automount as per mark's finding and it is backing it up now. Thanks all for contributing into this thread and get to the solution. Thanks a lot

    • Proposed as answer by Thomas M.T. _ Wednesday, October 14, 2009 4:54 PM
    Monday, September 28, 2009 10:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This fixed it for me.

    Make sure to do all three steps (Diskpart, Mountvol, and Registry).

    Thanks!
    Thursday, January 28, 2010 11:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We seem to have a similar issue with our 2008 boxes (non r2). Two of our servers had automount enabled and 2 didn't, the 2 enabled servers VSS backups worked.

    I've enabled automount as per the intructions,  did you need to reboot the host in order to get VSS working properly again?

    Friday, May 21, 2010 9:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We had 2 R2 servers upgraded from RTM (R1) with this problem.

    Followed the instructions from marcusolini with success.

    No reboot required.

    // Alexander

    Thursday, June 3, 2010 11:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    thanks - this worked for me

    Thursday, April 5, 2012 1:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    We had same errors with DPM, this as well fixed it for us also.
    Saturday, April 21, 2012 7:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This same issue appeared after upgrading the Hyper-V host box from 2008 to 2012. Tried removing an re-adding hyper-v role first, but the three steps above fixed the issue.
    Wednesday, October 31, 2012 2:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Vincent: This also affects R2 machines (that are not upgrades from 2008 RTM). The backups were successful for 6 of 7 days. The issue is ongoing and but does not always occur. Bob
    Monday, January 7, 2013 1:22 PM