f024afb0-c4dd-4160-ac6c-dcd28af3e47c Posted July 4, 2011 Report Share Posted July 4, 2011 (edited) Hello, I have got a problem when using Retrospect in combination with Hyper-V. I have installed the Retropect client on the Virtual servers, including an Exchange 2007 server with Windows Server 2003 OS. The other servers use Windows Server 2008. The servers consist of a primary vhd for OS and a secundary vhd for data. When Retropect backups these servers the backup proces stops sometimes (with the Exchange server always) and the server loses its connection with the network. The problem seems to occur when Retrospect tries to access the second vhd. After restarting the Virtual server the network connection is restablished and everything works fine again (with the exception of Retropect). Has somebody experienced the same problems ? And is there pherhaps a sollution for this problem ? Thanks for your replies. Kind regards, Ron Bouwmeester Edited July 6, 2011 by Ron Bouwmeester Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 4, 2011 Report Share Posted July 4, 2011 Retrospect 7.6 works fine for us on virtual servers, but that's under VMWare, not Hyper-V. Check to see if you have installed the latest Hyper-V updates (and also the latest Retrospect updates for 7.6.) Quote Link to comment Share on other sites More sharing options...
jotrago Posted July 12, 2011 Report Share Posted July 12, 2011 Do your Guest OS perhaps have the Data drive configured as Dynamic. From some research I have been doing in anticipation of a couple of my Retrospect customers moving to HyperV, it seems that using Dynamic disks in Guest OS, is not well supported and results in some issues. Primarily a requirement to shut the VM down in order to back it up, if using WIndows own Backup utility. Given that all the disk flexibility you would need is provided in the hypervisor there should really be no disadvantage in sticking to basic disks in the VM. Just a thought Quote Link to comment Share on other sites More sharing options...
johnnymacgo Posted July 15, 2011 Report Share Posted July 15, 2011 We had a similar problem with Hyper-V VM's running Exchange 2010 and this has seemed to fix it: http://support.microsoft.com/kb/2263829/en-us Quote Link to comment Share on other sites More sharing options...
f024afb0-c4dd-4160-ac6c-dcd28af3e47c Posted July 21, 2011 Author Report Share Posted July 21, 2011 We had a similar problem with Hyper-V VM's running Exchange 2010 and this has seemed to fix it: http://support.microsoft.com/kb/2263829/en-us Thank you very much for this reply. The patch solved the problem. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.