This monitor checks the state of data movement of the database replica. The monitor is unhealthy when the data movement is suspended. The monitor is healthy otherwise.
This monitor checks the state of data movement of the database replica. The monitor is unhealthy when the data movement is suspended. The monitor is healthy otherwise.
Either a database administrator or the system has suspended data synchronization on this availability database.
The system might have suspended the data movement due to an error.
User might have suspended the data movement for a maintenance purpose.
Resume the data movement. If the issue persists, check the event log for the availability group and diagnose the reason why the system has suspended data movement.
Name | Description | Default Value |
Enabled | Enables or disables the workflow. | Yes |
Generates Alerts | Defines whether the workflow generates an Alert. | No |
Interval (seconds) | The recurring interval of time in seconds in which to run the workflow. | 900 |
Synchronization Time | The synchronization time specified by using a 24-hour format. May be omitted. |
|
Timeout (seconds) | Specifies the time the workflow is allowed to run before being closed and marked as failed. | 300 |
Timeout for database connection (seconds) | The workflow will fail and register an event, if it cannot access the database during the specified period. | 15 |
| Target | Microsoft.SQLServer.2017.AlwaysOn.Windows.DatabaseReplica |
| Parent Monitor | System.Health.AvailabilityState |
| Category | AvailabilityHealth |
| Enabled | True |
| Alert Generate | False |
| Alert Auto Resolve | False |
| Monitor Type | Microsoft.SQLServer.2017.AlwaysOn.Windows.MonitorType.SystemPolicy |
| Remotable | True |
| Accessibility | Public |
| RunAs | Default |
Home<UnitMonitor ID="Microsoft.SQLServer.2017.AlwaysOn.Windows.Monitor.DatabaseReplica.SuspendState" Accessibility="Public" Enabled="true" Target="SQL2017AWD!Microsoft.SQLServer.2017.AlwaysOn.Windows.DatabaseReplica" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Microsoft.SQLServer.2017.AlwaysOn.Windows.MonitorType.SystemPolicy" ConfirmDelivery="false">
<Category>AvailabilityHealth</Category>
<OperationalStates>
<OperationalState ID="Success" MonitorTypeStateID="HealthState" HealthState="Success"/>
<OperationalState ID="Critical" MonitorTypeStateID="ErrorState" HealthState="Warning"/>
</OperationalStates>
<Configuration>
<MachineName>$Target/Host/Host/Property[Type="SQL2017L!Microsoft.SQLServer.2017.Library.DBEngine"]/MachineName$</MachineName>
<InstanceName>$Target/Host/Host/Property[Type="SQL2017L!Microsoft.SQLServer.2017.Library.DBEngine"]/InstanceName$</InstanceName>
<ConnectionString>$Target/Host/Host/Property[Type="SQL2017L!Microsoft.SQLServer.2017.Library.DBEngine"]/ConnectionString$</ConnectionString>
<MonitoringType>$Target/Host/Host/Property[Type="SQL2017WD!Microsoft.SQLServer.2017.Windows.DBEngine"]/MonitoringType$</MonitoringType>
<PolicyName>AlwaysOnDbrSuspendStatePolicy</PolicyName>
<BagKey>3-$Target/Property[Type="SQL2017AG!Microsoft.SQLServer.2017.AlwaysOn.Library.DatabaseReplica"]/AvailabilityDatabaseName$</BagKey>
<SqlTimeoutSeconds>15</SqlTimeoutSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<IntervalSeconds>900</IntervalSeconds>
<SyncTime/>
</Configuration>
</UnitMonitor>