Degraded Replication Group
The causes and resolutions refer to the Dell Modular Disk Storage Manager recovery guru. Launch Dell Modular Disk Storage Manager to diagnose and fix the recovery failure as follows:
Open Start >> Programs >> Dell >> MD Storage Manager >> Modular Disk Storage Manager Client.
If the MD Storage Array is already being managed by MDSM, you can proceed with the Causes and Resolution sections.
From Edit -> Add Storage Array, provide the IP address of the MD Storage Array and Add it to the discovered devices configuration in order to manage it.
Select the MD Storage Array and follow the steps specified in this recovery guru.
A replication group is Degraded. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
This problem occurs when the age of the recovery point on the secondary side of the replication group exceeds the recovery point warning threshold set for the replication group. This parameter is set on each replication group.
The replication group is still functional; however, this problem may indicate any of the following underlying conditions:
The network performance between this (local) storage array and the remote storage array is degraded.
The recovery point warning threshold is too low for the current bandwidth between this storage array and the remote storage array. If the threshold is set too low, the replication group will not be able to handle the amount of data that must be synchronized.
If this problem is occurring frequently, it is recommended to execute a communication test to diagnose potential network problems between this storage array and the remote storage array. The recovery point warning threshold associated with the replication group should also be evaluated to determine if the setting is appropriate for the remote replication configuration. If the remote replication configuration is designed to be used in a failover situation, repeatedly getting this problem may indicate that the remote replication configuration is not within the design objectives for how the configuration should operate in a failover situation.
This is a 'notification' condition such that there are no specific recovery steps to fix the problem. The recovery steps below are provided suggestions for how to diagnose problems that may be triggering this condition. The Clear button will remove this occurrence of the notification from the Recovery Guru.
1 | To diagnose potential problems with the remote replication configuration, it is recommended to do the following:
| ||||||||||||||||||||
2 | Click the Clear button to clear this notification. | ||||||||||||||||||||
3 | Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, reevaluate the network settings and warning thresholds for the replication group. If you feel the remote replication configuration is functioning properly, contact your Technical Support Representative. |
Target | Microsoft.SystemCenter.ManagementServer | ||
Category | Alert | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
|
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.ScriptGenerated.EventProvider | Default |
Alert | WriteAction | System.Health.GenerateAlert | Default |
WriteToDW | WriteAction | Microsoft.SystemCenter.DataWarehouse.PublishEventData | Default |
<Rule ID="Dell.MDStorageArray.ABBXMLEvent412" Enabled="onEssentialMonitoring" Target="SystemCenter!Microsoft.SystemCenter.ManagementServer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.ScriptGenerated.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<ScriptName>RBODEventGenerator</ScriptName>
<EventNumber>412</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent412.StringResource"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/EventDisplayNumber$</SuppressionValue>
<SuppressionValue>$Data/Channel$</SuppressionValue>
<SuppressionValue>$Data/PublisherName$</SuppressionValue>
<SuppressionValue>$Data/LoggingComputer$</SuppressionValue>
<SuppressionValue>$Data/EventCategory$</SuppressionValue>
<SuppressionValue>$Data/EventLevel$</SuppressionValue>
<SuppressionValue>$Data/UserName$</SuppressionValue>
<SuppressionValue>$Data/EventNumber$</SuppressionValue>
<SuppressionValue>$Data/EventDescription$</SuppressionValue>
</Suppression>
<Custom1/>
<Custom2/>
<Custom3/>
<Custom4/>
<Custom5/>
<Custom6/>
<Custom7/>
<Custom8/>
<Custom9/>
<Custom10/>
</WriteAction>
<WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>
</WriteActions>
</Rule>