Ensuring an Always-Available SQL Server Cloud Deployment

Email     |     Share  
1 | 2 | 3 | 4 | 5 | 6 | 7
Next Next

HA and DR Protection

Get high-availability and disaster recovery in the cloud with cost-efficient SQL Standard Edition.

To provide high-availability and disaster protection for SQL Server in the cloud, you may want to configure a failover cluster with redundant application instances in different cloud-availability zones, each configured on different IP networks (subnets). To support failover across these availability zones, you are required to purchase SQL Server Enterprise Edition, which can be cost prohibitive for simple two-node deployments in this configuration.

In these cases, SANless software can be used to provide high-availability failover across availability zones with low-cost SQL Standard Edition.

Companies are moving more business operations to cloud and hybrid cloud configurations. Others are adding cloud failover instances to their physical server environments for disaster recovery without the cost of building out a disaster recovery site. Yet, misperceptions and concerns about high availability and disaster protection have made decision making difficult for companies moving their mission-critical applications (i.e., SQL Server, Oracle, and SAP) to the cloud, where traditional shared-storage clusters are impractical or impossible. To fully leverage the benefits of cloud and hybrid cloud environments, companies need to separate myths from facts and consider a new approach to HA and DR.

In this slideshow, Jerry Melnick, president and CEO of SIOS Technology, takes a closer look at five common misconceptions surrounding high availability in the cloud and how SANless clusters can help overcome some of the obstacles.

  1. Public cloud deployments are automatically high-availability environments where application downtime is negligible. This is not true. Clouds are not high-availability environments unless you add HA protection.
  2. You cannot protect business-critical applications in a public or private cloud by using a cluster. The truth is, HA is a physical deployment with a failover cluster using shared storage (SAN). Public clouds (e.g., Amazon EC2, Azure) have no concept of a cluster-aware shared storage.
  3. Applications and data are protected from disasters in the cloud without additional configuration. The reality is that cloud providers experience downtime and regional disasters like any other organization.
  4. You can either run your application in the cloud or in your on-premise data center, but not both. In truth, you can have both. You can use your on-premise data center as your primary site and the cloud as your hot standby DR site. On-premise servers can be SAN-based or SANless clusters or a single server not participating in a cluster.
  5. Creating an HA environment in a cloud requires complex scripting, specialized skills or added complexity. The opposite is actually true. HA cluster in a cloud is very easy without adding another SAN with SANless clusters.
 

Related Topics : IBM Looks to Redefine Industry Standard Servers, APC, Brocade, Citrix Systems, Data Center

 
More Slideshows

RKONITGrowthFlexibility0x Building High-Growth IT: 5 Things to Know Now

Five factors IT pros need to consider when strategizing and constructing a computing platform built for growth and flexibility. ...  More >>

DataCtr11-290x195 5 Essential Elements in Building an Agile Data Center

Five key areas that are critical for successful data center modernization efforts include speed, quality of service (QoS), disaster recovery, predictive data analytics and manageability at scale. ...  More >>

cloud47-290x195 Multi-Cloud 101: 7 Things You Need to Know

Many organizations are beginning to consider use of a multi-cloud strategy, in which multiple cloud solutions are leveraged for a more complete and purpose-built cloud architecture. ...  More >>

Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.