Hi,

we have the same issue.

1x Windows Server 2008 R2 (Management-Server, HP ML330)
1x Windows Server 2008 R2 (HyperV host, 4 guests, HP ML 350)

Plain Windows Installations.
HyperV host is domain-member, mgmt-server is domain-member.
Fresh installation of BE 2010 on mgmt-server and fresh installation on HyperV-server.
Installation of 3 Hotfixes on mgmt-server and installing RA again on HyperV-Server:
http://entsupport.symantec.com/umi/V-373-00003
http://entsupport.symantec.com/umi/V-373-00006
http://entsupport.symantec.com/umi/V-373-00005

Reboot. 

Simple backup-job - just backing up 1 guest remote.
When the backup starts, it hangs during "snapshot..." and hyper-v server reboots :-(

help is very aprecciated.

Daniel

http://support.microsoft.com/kb/955076/en-us

Thank you STeve O for your help, but the Hotfix does not work nor install on 2008 R2.

The Eventlog says (german):
Der Computer wurde nach einem schwerwiegenden Fehler neu gestartet. Der Fehlercode war: 0x000000ca (0x0000000000000002, 0xfffffa80175f5bc0, 0x0000000000000000, 0x0000000000000000). Ein volles Abbild wurde gespeichert in: C:\Windows\MEMORY.DMP. Berichts-ID: 030810-13977-01

Source: Fehlercode
Ereignis-ID: 1001

The bluescreen says something about "Plug and Play detected an error most likely caused by a faulty driver"
 
I'm doing now some research in that direction.

Further help would be appreciated.

Regards
Daniel

a new status:

The HV 2008 R2 Host who gets the bluescren while backing up via BE2010 Remoteagent just gets teh Bluescreen, while -> System Recovery 2010 - is also installed.

We liked to use both products, but it seems, that those Symantec products don't like each other.

When deinstalling System Recovery 2010 the backup works fine ... but that's no kind of solution.

Regards
Daniel

I have the same issue on an Intel System.  On a fresh install of Server 2008 R2 x64 which IS a Hyper-V host with 1 VM, which also has the BE 2010 installed (latest 9.0.1.36527)

The hyper-v VM backs up perfectly, the host gets a bsod and reboots, before it ever starts writing the .v2i file.  Is there anyone working on fixing this, or a fix available?

Joe

Last week I received Mail from a Symantec technican.
He told me, that this issue is acknowledged but there is no fix for it yet. :-(

It seems so, we bought again some kind of "banana-software" that is not ready to release but yet released.

Regards
Daniel

Hello Hans,
hello all.

The solution for the mentioned problem that worked for us: http://go.microsoft.com/fwlink/?LinkId=193215 *1
You can read more at: http://technet.microsoft.com/en-us/library/ff394763(WS.10).aspx

How we got it to work:
1. HV 2008 R2 has BE 2010 RA installed (everything is fine, BESR 2010 is *not* installed)
2. Installing "Windows6.1-KB980856-x64.msu"  *1
3. Restart
4. Installing BESR 2010

Regards
Daniel