Overview Interoperability Technology and capabilities Quickstart Getting started Prerequisites, restrictions, and recommendations Creation and configuration Wizard Dialog Transact-SQL PowerShell Azure virtual machines Listener Concepts Automatic seeding for secondary replicas Availability group policies Availability modes Backup on secondary Basic availability groups Client connection Client connectivity Distributed availability groups Domain independent availability groups Enhanced Database Failover Database health detection Failover clustering and availability groups Failover and failover modes Flexible failover policy for automatic failover Interoperability with other features Change tracking and change data capture Configure replication Contained databases Database snapshots Distributed transactions Cluster DTC Encrypted databases Failover cluster instances FILESTREAM and FileTable Migrating from log shipping Remote blob store (RBS) Publication database Subscribers Reporting Services Service Broker Listeners, clients, and failover Logins and jobs Possible failures during sessions between replicas Read-scale only Readable secondary How-to guides Configure availability group Change replica availability Change replica failover mode Configure automatic seeding Configure backup on replicas Configure flexible failover policy Configure backup on replicas Configure distributed availability groups Configure for distributed transactions Configure read-only access replica Configure read-only routing Remove listener Join a secondary database Start data movement Manually prepare secondary database Specify the endpoint URL when adding or modifying a replica Join secondary replica Tune compression Troubleshoot configuration Configure instance Enable and disable Create database mirroring endpoint (PowerShell) Create clustered DTC Monitoring Transact-SQL SQL Server Management Studio View availability group properties View replica properties View listener properties Operation Add Database Dialog Wizard Add replica - wizard Add secondary replica Change session-timeout period Change the HADR cluster context Fail over - wizard Forced manual failover Planned manual failover Remove availability group Remove primary database Remove replica Remove secondary database Resume availability database Suspend availability database Take availability group offline Troubleshoot failed add-file Upgrading replica instances View health with policies References PowerShell Cmdlets Transact-SQL Resources Dialogs and Wizards Add IP Address Dialog Box Configure Read-Only Routing for an Availability Group Remove Availability Group Listener Specify Availability Group Options Page (New Availability Group Wizard/Add Database Wizard) Select Databases Page (New Availability Group Wizard and Add Database Wizard) Specify Replicas Page (New Availability Group Wizard: Add Replica Wizard) Enter Passwords Page (Add Replica Wizard) Select Initial Data Synchronization Page (Always On Availability Group Wizards) Validation Page (Always On Availability Group Wizards) Summary Page (Always On Availability Group Wizards) Progress Page (Always On Availability Group Wizards) Results Page (Always On Availability Group Wizards) Availability Group - Connect Existing Secondary Replicas Page Use the Always On Dashboard (SQL Server Management Studio) Options (SQL Server Always On, Dashboard Page) Policy Evaluation Result (Always On) Availability Replica Properties (General Page) Availability Group Properties: New Availability Group (General Page) Availability Group Properties: New Availability Group (Backup Preferences Page) Policies Availability database is suspended Availability group is offline Availability group is not ready for automatic failover Availability replica does not have a healthy role Availability replica is disconnected Availability replica is not joined Data synchronization state of availability database is not healthy Data synchronization state of some availability database is not healthy Secondary database is not joined Some availability replicas are disconnected Some availability replicas are not synchronizing data Some availability replicas do not have a healthy role Some synchronous replicas are not synchronized WSFC cluster service is offline