HyperV Backup: error 'AllowMacSpoofing'
new installation, new error message.
HyperV Host Server 2008
Acronis 12.5 Update1 HF1
Error when backing up any VM:
Backup ist fehlgeschlagen
Windows-Fehler: (0x80041002) Erhalten der Eigenschaft 'AllowMacSpoofing' fehlgeschlagen
How can we solve this?
The error is thrown from WMI (see details of the error) when Acronis Backup tries to read configuration of the Hyper-V VM on particular host - the failure occurs when reading the virtual network configuration and in particular the MAC Spoofing option: https://technet.microsoft.com/en-us/library/ff458341.aspx?f=255&MSPPError=-2147217396
You should check the virtual switch properties in Hyper-V manager and make sure it is shown properly.
Most likely re-creating the virtual network switch and connecting VMs to it would also help.
thank you for your reply.
I re-created the virtual switch, but unfortunately nothing changed.
The error stays the same.
This hypervisor is "Server 2008" (NOT R2).
If I read correctly this version does not yet have this "mac spoofing" function.
I realized that I can backup a VM successfully if I disconnect it from the virtual switch.
But obviously that is no solution.
What can I do?
Looks like the issue has to be processed through our support team. The problem looks like a bug related to specific Hyper-V version (2008 without R2) and particular MAC spoofing option in network switch. There are no workarounds that I can suggest right now - the problem needs to be investigated first (with help from our support team).
We were able to reproduce the problem in our QA lab. As it turned out the problem is specific to the following combination: Windows Server 2008 with Hyper-V role _without_ R2 AND static MAC addresses used in VM configuration defined from Hyper-V manager (internal bug ID: ABR-139974). This means that there is no such issue with default dynamic MAC address assignment for VMs AND there is no such problem with static MACs on Windows Server 2008 R2 with Hyper-V role.
The fix for this problem is planned for the next update for Acronis Backup 12.5 (Update 2, planned for the end of this year).
Thank you for the note - we'll check with our QA team to further localize the issue (probably there is some additional factor, which we haven't revealed yet). In either case please continue working with our support team to properly track the final resolution.
The temporary solution would be to install Agent for Windows/Linux inside the VMs which need to be protected, e.g. instead of agent-less backup (via Agent for Hyper-V) use agent-based approach which will be free from such problem. Another (more complicated) option is to update the server OS to 2008 R2.