Maintaining high availability of SQL Server virtual machines

Since the release of Hyper-V, Microsoft has continued its commitment to server virtualization by releasing new software products that are optimized for just that. This is the case for SQL Server 2008 among other Microsoft products.

When previously discussing fault-tolerant virtual installations, the Microsoft SQL Server support team has published specific strategies for virtualizing SQL Server installations. These strategies include different guidelines for SQL Server virtualization, but the most interesting being those used to achieve fault tolerance.

The SQL Server support team does not support the creation of a cluster at the virtual machine level. This means you cannot create a fault-tolerant virtual machine by creating a SQL Server cluster. You can, however, create a fault-tolerant VM by creating a cluster at the host server level.

It basically works like this. Since each host server in a server virtualization resource pool will run several virtual machines at once, most organizations will create fault-tolerant host server configurations to protect these VMs. Then once the hosts are made redundant through a host cluster, each and every one of the virtual machines running on these hosts will become a protected application and thus gain a certain level of fault tolerance. In the event of a host failure, the VMs running on this host will also fail, but will automatically be restarted on another host in the cluster.

This is one strategy that can be used to create SQL Server virtual machines and ensure highly availability. The process is simple:

1. Prepare the physical server nodes as well as the shared storage component they require to join a cluster.
2. Install the hypervisor. For example, with Windows Server 2008, you must first install the operating system and then enable the Hyper-V role.
3. Create a host cluster. This means installing the Failover Clustering feature on both nodes in Windows Server 2008. In Hyper-V, you need to perform two additional actions:

        a. Create a virtual network. This is performed in the Hyper-V Manager      through the Virtual Network Manager. You must add a new external      network adapter linked to a physical adapter, and this action must be      performed on all nodes of the cluster. In addition, the name of the new      virtual adapter must be identical on each cluster node in order for VM      failover to work.

        b. Validate the cluster configuration and create the cluster. This will      ensure that all of the components required for cluster operation are in ...
   

   To continue reading for free, register below or login

   Requires Membership to View

   To gain access to this and all member only content, please provide the following information:

   Email Address:
   
   
   

   By joining SearchSQLServer.com you agree to receive email updates from the TechTarget network of sites, including updates on new content, magazine or event notifications, new site launches and market research surveys. Please verify all information and selections above. You may unsubscribe at any time from one or more of the services you have selected by editing your profile or unsubscribing via email.
   
   TechTarget cares about your privacy. Read our Privacy Policy
   To read more you must become a member of SearchSQLServer.com

   As an existing member of the TechTarget network please activate your SearchSQLServer.com account 

   By joining SearchSQLServer.com you agree to receive email updates from the TechTarget network of sites, including updates on new content, magazine or event notifications, new site launches and market research surveys. Please verify all information and selections above. You may unsubscribe at any time from one or more of the services you have selected by editing your profile or unsubscribing via email.
   
   TechTarget cares about your privacy. Read our Privacy Policy
   
   
   

   Digg This!     StumbleUpon     Del.icio.us

   
   
   
   

   RELATED CONTENT SQL Server High Availability, Scalability and Reliability Are data warehouses made for the cloud? Top load balancing methods for SQL Server Creating fault-tolerant SQL Server installations Scaling up vs. scaling out with SQL Server 2008 How to configure storage in SQL Server database with more writes than reads SQL Server database replication tutorial Licensing a standby server for SQL Server replication Get SQL Server log shipping functionality without Enterprise Edition Monitor database mirroring and replication after a SQL Server upgrade Upgrade live applications to SQL Server 2005 for high availability SQL Server High Availability, Scalability and Reliability Research Microsoft SQL Server Consolidation and Virtualization Q&A: SQL Server 2008 a better fit for consolidation Deploying a SQL Server virtual appliance for Microsoft Hyper-V How to create SQL Server virtual appliances for Hyper-V Protect virtual databases through SQL Server database mirroring Creating fault-tolerant SQL Server installations Using Microsoft Hyper-V for SQL Server consolidation The challenges of SQL Server consolidation SQL Server Consolidation Fast Guide SQL Server consolidation strategies and best practices SQL Server virtualization pros and cons: Weigh the performance impact Microsoft SQL Server Consolidation and Virtualization Research Database Management and Administration Hardening the network and OS for SQL Server security Securing the server and database in SQL Server How SQL Server 2008 components impact SharePoint implementations Troubleshooting Distributed Transaction Coordinator errors in SQL Server Achieving high availability and disaster recovery with SharePoint databases Clearing the Windows page file and its effect on server performance Deploying a SQL Server virtual appliance for Microsoft Hyper-V How to create SQL Server virtual appliances for Hyper-V Push vs. pull: Configuring SQL Server replication Protect virtual databases through SQL Server database mirroring

   RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

   
   
        place before you actually create the cluster.

4. Once the cluster is created, you can then create a VM that will host SQL Server and set it up for high availability. First create or copy the VM to the cluster, then use the Failover Clustering Management console to make the VM highly available.

You will then have a fault-tolerant SQL Server virtual machine. When and if the host node running the SQL Server VM fails, the VM will automatically be restarted on another node of the cluster. While this does not make SQL Server aware of the failover, it does ensure that the virtual machine is always running (see Figure 1).

Figure 1
[IMAGE]

[IMAGE]
[IMAGE] SQL SERVER AND MICROSOFT HYPER-V
[IMAGE] Part 1: Creating fault tolerant installations
[IMAGE] Part 2: Maintaining high availability
[IMAGE] Part 3: Protecting virtual databases
[IMAGE] Part 4: Creating virtual appliances
[IMAGE] Part 5: Deploying virtual appliances

[IMAGE][IMAGE]Danielle Ruest and Nelson Ruest are IT professionals specializing in systems administration, migration planning, software management and architecture design. Danielle is Microsoft MVP in Virtualization and Nelson is Microsoft MVP in Windows Server. They are authors of multiple books, including the free Definitive Guide to Vista Migration for Realtime Publishers and Windows Server 2008: The Complete Reference for McGraw-Hill Osborne. For more tips, write to them at info@reso-net.com.