Home
  •  

Synchronization failed with shadow copy area full

Microsoft.SystemCenter.DataProtectionManager.2011.Discovery.SyncFailed_SCAreaFull (UnitMonitor)

Synchronization failed because shadow copy area is full.

Knowledge Base article:

Summary

This is a consolidated backup failure alert (root cause) that represents one or more backup failures which have occurred on the DPM server because one of the infrastructure objects, such as the protection agent, DPM disk, DPM library, is in an unhealthy state. In this alert, failed backups share the same root cause. After the root cause is fixed, backups can be run for all the affected data sources. 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 and resolved, resume the backups using the Resume DPM Backup action.

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 (root cause) and how you can use the DPM tools to troubleshoot and resolve issues, see Working with Consolidated Backup Failure Alerts (Root Cause) (http://go.microsoft.com/fwlink/?LinkId=226790).

Element properties:

TargetMicrosoft.SystemCenter.DataProtectionManager.2011.Library.ReplicaVolume
Parent MonitorSystem.Health.ConfigurationState
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.SystemCenter.DataProtectionManager.2011.Discovery.SyncFailed_with_SCAreaFull
RemotableTrue
AccessibilityPublic
Alert Message
DPM: Synchronization failed - Shadow copy area full

Synchronization failed with shadow copy area full, for some of the data sources associated with the replica volume ID: {0}

Resolution steps:
{1}

Recommended action:
{2}
RunAsDefault

Source Code:

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

  <Category>Custom</Category>

  <AlertSettings AlertMessage="Microsoft.SystemCenter.DataProtectionManager.2011.Discovery.SyncFailed_SCAreaFull_AlertMessageResourceID">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Warning</AlertSeverity>

    <AlertParameters>

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

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

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

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="UIGeneratedOpStateIdeda14fa1ab0045eeaedec3391ebc1f9b" MonitorTypeStateID="UnHealthy" HealthState="Warning"/>

    <OperationalState ID="UIGeneratedOpStateId79bcc68c8a9e4f5082f9e2cfb8d3bd30" 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>