Home
  •  

Replica is inconsistent because the VMM server is unreachable

Microsoft.SystemCenter.DataProtectionManager.2012.Discovery.ReplicaInvalid_UnableToReachVMMServer (UnitMonitor)

Knowledge Base article:

Summary

This is a consolidated backup failure alert (logical consolidation) that represents one or more backup failures that have happened on the DPM server. The data sources affected may not share the same root cause. Since the failures have similar symptoms and resolution steps, they are logically consolidated under this alert. To view the data sources affected by this issue, click on the action View Affected Items.

Causes

See the alert details pane for more information about the cause of this alert.

Resolutions

See the alert details pane for steps to resolve this alert. After the root cause is understood, resolve the root cause for each affected item and then resume the backups using the action Resume DPM Backups.

Additional

Additional information for this failure is available on the DPM website. To view this, select the alert in the alert view and click on the action Get more information

External

To learn more about consolidated backup failure alerts (logical consolidation) and how you can use the DPM tools to troubleshoot and resolve issues, see Working with Consolidated Backup Failure Alerts (Logical Consolidation) (http://go.microsoft.com/fwlink/?LinkId=226791).

Element properties:

TargetMicrosoft.SystemCenter.DataProtectionManager.2011.Library.ProtectionGroup
Parent MonitorSystem.Health.ConfigurationState
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.SystemCenter.DataProtectionManager.2012.Discovery.ReplicaInvalid_with_UnableToReachVMMServer
RemotableTrue
AccessibilityPublic
Alert Message
DPM: Replica is inconsistent - VMM server is unreachable
Replica is inconsistent because the VMM could not be reached for some of the data sources under the protection group: {0}

Resolution steps:
{1}

Recommended action:
{2}
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.SystemCenter.DataProtectionManager.2012.Discovery.ReplicaInvalid_UnableToReachVMMServer" Accessibility="Public" Enabled="true" Target="SCDPM!Microsoft.SystemCenter.DataProtectionManager.2011.Library.ProtectionGroup" ParentMonitorID="Health!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="Microsoft.SystemCenter.DataProtectionManager.2012.Discovery.ReplicaInvalid_with_UnableToReachVMMServer" ConfirmDelivery="true">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="Microsoft.SystemCenter.DataProtectionManager.2012.Discovery.ReplicaInvalid_UnableToReachVMMServer_AlertMessageResourceID">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Target/Property[Type="SCDPM!Microsoft.SystemCenter.DataProtectionManager.2011.Library.ProtectionGroup"]/PGName$</AlertParameter1>

      <AlertParameter2>$Data/Context/Params/Param[29]$</AlertParameter2>

      <AlertParameter3>$Data/Context/Params/Param[30]$</AlertParameter3>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="UIGeneratedOpStateId267f144463a243d0b0d28d736f356544" MonitorTypeStateID="UnHealthy" HealthState="Error"/>

    <OperationalState ID="UIGeneratedOpStateId1951b3e9af0a49ff9b4fbab40be33fa8" MonitorTypeStateID="Healthy" HealthState="Success"/>

  </OperationalStates>

  <Configuration>

    <FileSystemSLA>0.01</FileSystemSLA>

    <SQLSLA>0.01</SQLSLA>

    <SharePointSLA>0.01</SharePointSLA>

    <ExchangeSLA>0.01</ExchangeSLA>

    <HyperVSLA>0.01</HyperVSLA>

    <SystemStateSLA>0.01</SystemStateSLA>

    <VirtualServerSLA>0.01</VirtualServerSLA>

    <GenericDatasourceSLA>0.01</GenericDatasourceSLA>

  </Configuration>

</UnitMonitor>