AlwaysOn Availability Groups will replace mirroring as a disaster recovery option starting with SQL Server 2012, and where applicable should be used as the primary DR option in SQL 2012 installs. This post will cover the configuration process for Availability Groups.
SQL Server Failover Cluster Instances may be members of on Availability Group (automatic failover is not an option in that model), this document will cover the configuration using standalone instances. The configuration is nearly the same for Availability Groups involving FCIs as members.
- Windows is installed and all servers are members of the same domain
- The Windows failover cluster is build and all servers marked for installation are members of that cluster
- An AD virtual computer object and IP address have been reserved for the Listener which will control connectivity to the Availability Group.
- Install SQL Server on each node (using standard installation process, for either cluster or standalone)
- There are two options for enabling SQL AlwaysOn Availability Groups. The first is via PowerShell. Launch PowerShell (as Administrator)
Issue the following commands:
–sqlps (imports the SQL Powershell modules)
–enable-sqlalwayson -ServerInstance $Instancename -Force
Note–this causes a restart of the SQL instance. The service must be restarted for SQL AlwaysOn to be enabled.
The other option is to go into SQL Server Configuration Manager and right click on the SQL Server service. Click on the AlwaysOn High Availability tab.
Click the check box to enable AlwaysOn. The Database server is now ready for AlwaysOn configuration.
Pingback: AlwaysOn Availability Groups and SharePoint 2013 « The SQL Herald
It’s hard to come by educated people in this particular subject, but you sound like you know what you’re
talking about! Thanks