Solved

Hyper-V guest vm backup

Posted on 2014-03-20
1
744 Views
Last Modified: 2014-11-12
I'm having an issue backing up a few guest vm's in our Hyper-V infrastructure.   We are running Server 2008 R2 SP1 on the host side.  The vm's that we are having issues with are all server 2012 R2 guests.  The vm's are on different clusters and hosts.  Some even standalone.  We're using netapp SnapManager for Hyper-V as our backup solution.  Thus is basically a vss aware backup solution.   The software can only backup up the 2012 r2 servers via saved state instead of online.   When I run diskshadow and list writers it shows saved state instead of child partition for the 2012 r2 servers.  I'm trying to find documentation on if server 2012 r2 is a viable guest os on 2008 r2 but can't find anything conclusive.  My only thought some kind of issue with integration services between host os and guest os.  On 2012 r2 host os I have no issues with newly created vm's.  I haven't tried moving the vm's with this issue to our 2012 r2 cluster yet go see if the issue persists.

I also have a windows 2003 r2 I believe that was working and has stopped with the same issue.  A reboot sometimes fixes the issue.  I suspect a performance issue on the gues vm's since when I run vss admin list writers it can take as long as 5-10 minutes for results to come back.  This may be the reason with this server.
0
Comment
Question by:georgedschneider
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 58

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 39943998
In order to leverage VSS backups on running VMs, the integration components must indeed match up and 2012 R2 does not play well in 2008 R2. As a general rule, no guest OS higher than the host plays well. This was true with 2008 R2 guests in the 2008 RTM of Hyper-V, and has persisted with each new release. Hyper-V will happily run those guests, but not all integration services (and certainly not VSS passthrough) would work. If you want that stuff, your host (management, parent, etc) should be at least as high as the highest guest.

As far as the 2003 R2 server, it could be an integration components issue or a resource issue. Since rebooting seems to fix it, I would think resource issue as you've already speculated. Just wanted to let you know I don't think you are off-base with that idea.
0

Featured Post

Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

724 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question