none
Unable to create backup on VM Guest using Data Protection Manager 2010 RRS feed

  • Question

  • I’m unable to create a backup of VM Guest after configuring our Cisco Switch and Router to VLAN. I noticed that on the VM Host, it can back up the Systems State and Bare Metal except for the 5 VM Guest.  

    Here’s the error message I encountered from a VM Guest.

    The replica of Microsoft Hyper-V \Backup Using Child Partition Snapshot\VM-Guest on <Server> is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

    For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)

    The DPM service was unable to communicate with the protection agent on <Server> .(ID 65 Details: The specified network name is no longer available (0x80070040)).

    And for the error logs on the DPM Server.

    WARNING Error polling: Microsoft.Internal.EnterpriseStorage.Dls.EventManagement.EventManagerException: Failed to invoke ICoreServices

    1250 104C 07/04 03:21:53.293 02 EventManager.cs(479) WARNING   at Microsoft.Internal.EnterpriseStorage.Dls.Engine.EventManagerServicesProxy.CheckError(Int32 hr, tagSAFEARRAY* exception)
    1250 104C 07/04 03:21:53.293 02 EventManager.cs(479) WARNING   at Microsoft.Internal.EnterpriseStorage.Dls.Engine.EventManagerServicesProxy.EventGetEvents(Guid& subscriberID, String serverName)
    1250 104C 07/04 03:21:53.293 02 EventManager.cs(479) WARNING   at Microsoft.Internal.EnterpriseStorage.Dls.EventManagement.EventManager.GetEvents(String serverName)
    1250 104C 07/04 03:21:53.293 02 EventManager.cs(479) WARNING *** Mojito error was: UIEventsFailure; -2147417848; WindowsHResult

    Thanks,




    Friday, December 21, 2012 11:24 AM

All replies

  • If the problem only started after the VLAN tagging was enabled you might want to verify that the correct VLAN ID is configured for the VM's in Hyper-V Manager.

    There may be some confusion around what each checkbox for enable VLAN Identification actually does.

    If you are viewing the Virtual Switch in Hyper-V Manager, the checkbox you see here ONLY affects the virtual adapter that we created in the parent partition. You only
    need to check this box if the parent connection thru the virtual switch requires a VLAN Tag. This is NOT required for VM Adapters to support VLAN IDs.

    If you view the properties of each Network Adapter in a VM, you will also notice a checkbox to enable VLAN Identification. This checkbox only affects that specific adapter. Each Adapter in a VM could have a separate VLAN ID if required.


    -------------------- Regards, Michael V [MSFT] - This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, January 16, 2013 11:11 PM
    Moderator