Administration of an Availability Group (SQL Server)
Managing an existing AlwaysOn availability group in SQL Server 2012 involves one or more of the following tasks:
Altering the properties of an existing availability replica, for example to change client connection access (for configuring readable secondary replicas), changing its failover mode, availability mode, or session timeout setting.
Adding or removing secondary replicas.
Adding or removing a database.
Suspending or resuming a database.
Performing a planned manual failover (a manual failover) or a forced manual failover (a forced failover).
Creating or configuring an availability group listener.
Managing readable secondary replicas for a given availability group. This involves configuring one or more replicas to read-only access when running under the secondary role, and configuring read-only routing.
Managing backups on secondary replicas for a given availability group. This involves configuring where you prefer that backup jobs run and then scripting backup jobs to implement your backup preference. you need to script backup jobs for every database in the availability group on every instance of SQL Server that hosts an availability replica.
Deleting an availability group.
Cross-cluster migration of AlwaysOn Availability Groups for OS upgrade
In This Topic:
To configure an existing availability group
To manage an availability group
To manage an availability replica
To manage an availability database
To monitor an availability group
To support migrating availability groups to a new WSFC cluster (cross-cluster migration)
**White papers: **