frank412 wrote:With regards to the first cause, this could be fix by restarting/rebooting the Host according to Veeam Support. I saw this website("http://www.2020media.com/blog/2011/06/notes-on-hyper-v-backups/") which says restarting the Hyper-V Virtual Machine Management could fix this error. I just wanna make sure if doing so couldn't affect the entire operation of the Host and the VMs that resides. Please advice.
frank412 wrote:With regards to the latter, I found this MS Forum("http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/95f2ad6a-5354-4b6a-aa01-c912ecb390ac") but unfortunately, it is only applicable to Windows XP. What I need is for Windows 7 and MS Server 2008 R2. I hope some of you guys which has the technical expertise/knowledge related to this issue could advice other solution based on your experience.
foggy wrote:Restarting the Hyper-V Virtual Machine Management service would not cause any issues to the running VMs (though it seems that this thread is discussing not exactly the same error).
foggy wrote:My search shows that the given instructions apply not only to WinXP, I think you can try them, if applicable. Also, you could check whether the Hyper-V Data Exchange Service is running within the VM.
Users browsing this forum: Exabot [Bot], Google [Bot] and 4 guests