Dell High Availability and Disaster Recovery Solutions Using Microsoft SQL Server 2012 AlwaysOnAvailability Groups10Limitations: Limits on storage scalability. No enhanced SAN capabilities.AVG deployments on shared storageIn addition to the failover capability provided by AlwaysOn Availability Group, we may also set up asecondary layer of availability at the server instance level. This is done by implementing SQL Server FCItogether with the underlying WSFC cluster. FCI is configured with shared storage to host the SQL serverinstances.FCIs are basically designed to provide High Availability at instance level whereas AlwaysOn AvailabilityGroup (AVG) is designed to provide HA and DR capabilities at database level.- Consider the following when you plan to combine the FCI with AVG. AVG alone does not require shared storage, but when we use FCI to host one or moreavailability replicas, each of the nodes which are part of FCIs will require shared storage as perstandard SQL Server failover instance installation. An FCI may be used together with an availability group to enhance the availability of anavailability replica. However, to prevent potential race conditions in the WSFC cluster,automatic failover of the availability group is not supported to or from an availability replicathat is hosted on a FCI. Since SQL Server FCIs do not support automatic failover by availability groups, any availabilityreplica that is hosted by an FCI can only be configured for manual failover. All the prerequisites and restrictions that need to be addressed before proceeding with AVGdeployment may be found at http://msdn.microsoft.com/en-us/library/ff878487.aspx#FciArLimitations. Care should be taken to make sure all the specifiedhotfixes are installed on the appropriate nodes.Figure 3 shows the typical AVG deployment along with SQL Server FCI.