| title | Availability database is suspended for an availability group | |
|---|---|---|
| description | Identify possible causes for why a database in an Always On availability group might be suspended. | |
| author | MashaMSFT | |
| ms.author | mathoma | |
| ms.date | 05/17/2016 | |
| ms.service | sql | |
| ms.subservice | availability-groups | |
| ms.topic | reference | |
| f1_keywords |
|
|
| helpviewer_keywords |
|
[!INCLUDE SQL Server]
- Policy Name: Availability Database Suspension State
- Issue: Availability database is suspended.
- Category: Warning
- Facet: Availability database
This policy checks the state of data movement of the secondary database (also known as a "secondary database replica"). The policy is in an unhealthy state when the data movement is suspended. The policy is otherwise in a healthy state.
Data synchronization on this availability database might have been suspended because of the following:
-
Due to an error, the system might have suspended data synchronization.
-
The database administrator might have suspended data synchronization for maintenance purposes.
Resume data synchronization by right-clicking the availability group and selecting Resume Data Movement. If the issue persists, check the availability group in the Event log, and then diagnose why the system suspended data movement.
Overview of Always On Availability Groups (SQL Server)
Use the Always On Dashboard (SQL Server Management Studio)