SQL HA without Shared Storage
Posted on 2014-04-05
I did a little research and found these steps on how to create a HA SQL without shared storage. Now, if you read down to step 6 it says to use a shared drive. My thought was to use two file servers that are employing DFS and NamedSpaces. Is that cool?
Here are the high-level steps to follow to deploy SQL 2012 AlwaysOn in a SQL 2012 failover cluster (without shared storage).
1. Install Windows Server 2012 in two computers or virtual machines (VMs), each with a single network interface card (NIC).
2. Create a two-node failover cluster without shared storage. You will need a cluster name and an IP address for the cluster network name.
3. Install SQL Server 2012 Enterprise on both computers as if they were going to be stand-alone SQL servers. ¿ When you install, use a domain account for the SQL server services.
¿ Open the Windows Firewall on ports TCP 1433 and TCP 5022.
4. Create a temporary "seed" database on the first SQL server using SQL Server 2012 Management Studio. This database will be used to establish the AlwaysOn cluster, and then can be deleted after the first production database is deployed.
5. Make sure the database is of the "Full" type model, and perform a SQL Backup job.
6. In the Management Studio, create an AlwaysOn Availability Group and an Availability Group Listener. (The Availability Group Listener is essentially the virtual (or clustered) SQL Server instance. There is a one-to-one relationship between availability groups and listeners.) ¿ Assign a DNS name and TCP IP address for the AlwaysOn Availability Group and an Availability Group Listener.
¿ Assign a shared network folder that is accessible to all SQL servers that will have AlwaysOn database replicas.
7. At the AlwaysOn High Availability node, right-click and select Add A Database To An Availability Group. If your database is of the Full type and has been backed up, the status will be "Meets Requirements". Click Next.
8. Select that you will perform a full synchronization, using the shared network folder you specified in step 6(b). Click Next.
9. Enter security information to access the primary database replica. Click Next, observe the validation and click Next, and then Finish.
10. Observe after a moment that new database replica on the secondary node in the SQL