Ensuring an Always-Available SQL Server Cloud Deployment

1 | 2 | 3 | 4 | 5 | 6 | 7
Previous Ensuring an Always-Available SQL Server Cloud Deployment-1 Next

High Availability Cloud Deployments

Click through for a closer look at how organizations can ensure high-availability SQL Server cloud deployments by using SANless clusters, as identified by Jerry Melnick, president and CEO of SIOS Technology.

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

HCI 10 Reasons Why the Enterprise Is Turning to Hyperconverged Infrastructure

While HCI is certainly innovative in design, its true measure lies in the practical benefits it brings to data center management and operations. ...  More >>

DataM63-290x195 Data Storage Today: Key Takeaways from VMworld 2016

Survey findings include pain points for secondary storage, average restore times, the growth of hyperconvergence and rate of cloud adoption in enterprises.  ...  More >>

cloud51-190x128 5 Best Practices for Managing Zombie Cloud Infrastructure

IT administrators need to identify zombie assets, verify idle status and shut off anything that is unused. Here's how to get your dormant infrastructure back in shape. ...  More >>

Subscribe Daily Edge Newsletters

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