You are on page 1of 29

WHITE PAPER

FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA® STORCENTER™ px SERIES
Configuration Guide

INTRODUCTION Audience Scope Related documents REQUIREMENTS Prerequisites Hardware requirements Software requirements CREATING iSCSI LUNS CONNECTING TO THE ISCSI LUNS FORMATTING THE iSCSI LUNS

2 2 2 3 3 3 3 4 4 7 10

CREATING A FAILOVER CLUSTER Adding the failover cluster feature Validating the failover cluster configuration Creating a failover cluster CREATING A HIGHLY AVAILABLE VIRTUAL MACHINE Virtual machine creation and operating system installation Making a virtual machine highly available TESTING PLANNED FAILOVER TESTING UNPLANNED FAILOVER CONCLUSION

11 12 13 16 20 20 24 27 28 29

AUGUST 2011

FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES

INTRODUCTION
In 2008, Microsoft released Hyper-V, its first bare-metal hypervisor-based technology, built into Windows Server 2008.With the Hyper-V architecture, hardware-assisted, x64-based systems can run independent, virtual environments with different operating systems and resource requirements within the same physical server. In 2009, the release of Windows Server 2008 R2 introduced more advanced features for Hyper-V, including Live Migration and Cluster Shared Volume (CSV). These features work in a Windows failover clustering environment and, additionally, can leverage iSCSI logical unit numbers (LUNs) as a storage option to create virtual machines and virtual disks. The inclusion of the Microsoft iSCSI Software Initiator in Windows Server 2008 provides ubiquitous SAN connectivity for customers using existing Ethernet infrastructure. This cost-effective, highly scalable, virtualization platform offers advanced resource management capabilities. Hyper-V minimizes Total Cost of Ownership (TCO) for your environment by increasing resource utilization, decreasing the number of servers and all associated costs, and maximizing server manageability. Using shared storage along with a Hyper-V infrastructure offers the additional benefits of higher availability, simple server migration and improved recovery. The Iomega® StorCenter™ px series network storage array offers versatile storage provisioning, advanced protocol capabilities, expandability, and affordability in an easy-to-use product ideal for small businesses, workgroups, and departments. Based on enterprise-class EMC™ storage technology, the StorCenter px series provides multiple gigabit Ethernet connections, easy file sharing, iSCSI block access, flexible RAID configurations for optimized data protection, and storage pools for application flexibility and expandability to match your budget. The Iomega StorCenter px series can present iSCSI LUNs for Microsoft Hyper-V Server as well as failover cluster to create virtual machines and virtual disks, and the px series is Microsoft Windows Server 2008 and 2008 R2 (Hyper-V) certified for iSCSI. This white paper provides information on the installation, deployment and configuration requirements and procedures of the failover clustering feature of Microsoft Hyper-V on the Iomega StorCenter px series using iSCSI storage. Detailed step-by-step instructions with screenshots are included for illustration purposes. Audience Information contained in this white paper is intended for Iomega customers, partners, and service personnel involved in planning, architecting, or administering a Microsoft Hyper-V failover clustering environment with Iomega StorCenter px series as the storage device. The readers are expected to have experience with Microsoft Hyper-V Server and an Iomega StorCenter network storage device that runs EMC Lifeline software. SCOPE This document summarizes the experiences and methods followed while installing, deploying and configuring Microsoft Hyper-V failover clustering on Iomega StorCenter px series. The objectives of this document are as follows: • Provide a material for reference, to be used while performing similar installation, deployment and configuration. • Provide details on the possible areas of risks and the identified best practices while installing, deploying and configuring the described component or system.

White Paper

2

microsoft. and we recommend that you use Gigabit Ethernet or higher. The reader can find more technical information about Microsoft Hyper-V by visiting http://technet. The network you use for iSCSI cannot be used for network communication. HARDWARE REQUIREMENTS Table 1 lists the identified hardware requirements: Hardware Iomega® StorCenter™ px12-350r network storage Quantity One Configuration • • • • Intel Core 2 Duo E8400 3.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES RELATED DOCUMENTS The documents Using Iomega StorCenter ix12-300r/px12-350r with Windows Server 2008 R2 Hyper-V over iSCSI and EMC Virtual Infrastructure for SMB – Enabled by Iomega StorCenter ix12-300r Network Storage and Microsoft Hyper-V are located on http://www.0GHz CPU 4GB RAM 12 7200 rpm SATA-II disks Intel Pro/1000 Quad ports NIC Windows Server 2008 R2 Two • Intel VT or AMD AMD-V support • Minimum two GbE NICs Table 1 Hardware resources White Paper 3 . configured at the hardware level for a two-node failover cluster.iomega. • For iSCSI each clustered server must have one or more network adapters or host bus adapters that are dedicated to the cluster storage. In all clustered servers.com and provide additional. • The storage should contain at least two separate volumes (LUNs).com. The volume serves as the shared storage on which you will create virtual machines and virtual hard disks. relevant information about how to configure and deploy Microsoft Hyper-V Server with an Iomega StorCenter network storage device. the network adapters you use to connect to the iSCSI storage should be identical. • The clustered volumes should not be exposed to servers that are not in the cluster. One volume will contain the files that are being shared between the cluster nodes. REQUIREMENTS This section includes the prerequisites and requirements for a successful deployment. PREREQUISITES The following are the prerequisites for a successful deployment: • The shared storage to be used must be compatible with Microsoft Windows Server 2008 R2. • One volume will function as the witness disk (described later in this document).

The iSNS server allows automated discovery. The initiator also needs to provide the initiator CHAP secret for mutual CHAP authentication if the global mutual CHAP setting is enabled on the Iomega device. White Paper 4 . When CHAP is enabled and an iSCSI LUN is secured. The SendTargets command technique requires that an initiator know the IP address and port number of the target. if the LUN is not secured. The Microsoft Software iSCSI Initiator supports both discovery mechanisms. It is the simple and default discovery method. Iomega recommends that customers use secure iSCSI LUNs.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES SOFTWARE REQUIREMENTS Table 2 lists the identified software requirements Software EMC Lifeline 3. and the Internet Storage Name Service (iSNS) server. After target discovery. An iSCSI LUN can be protected by setting user access controls and iSCSI authentication methods. The Iomega px series supports two methods of target discovery: the SendTargets command.1. management and configuration of iSCSI devices over a TCP/IP network. The Iomega px series supports the CHAP authentication method.12 Windows Server 2008 R2 Quantity One Two Configuration EMC software that runs the Iomega px12-350r network storage array Hyper-V Server role Failover Clustering feature The servers in the cluster must be using domain name system (DNS) for name resolution Cluster servers should be members of a recommended domain DNS Server One Domain controller One Table 2 Software resources CREATING ISCSI LUNS When using iSCSI storage. an initiator needs to provide the target CHAP secret to log on. no authentication is required even if the global mutual CHAP setting is enabled. you must create one or more iSCSI LUNs on an Iomega StorCenter storage device. However. an iSCSI initiator can log on with or without authentication.

FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES This section discusses the steps for creating iSCSI LUNs on an Iomega StorCenter px series storage device. 1. Figure 2. Click Add an iSCSI drive to create a new LUN. Click On to turn on iSCSI if not enabled already. Create a new LUN • If multiple Storage Pools exist on the Iomega storage device. Otherwise. 3. no selection is available. The size cannot exceed the free space of the pool. • Enter the size of the LUN in GB. you need to select a Storage Pool where the LUN will be created. White Paper 5 . Go to Storage > iSCSI to create iSCSI LUNs. 2. Configure iSCSI settings 4. Figure 1. Click Settings to configure iSNS and/or Mutual CHAP if needed.

When a LUN is first created. Figure 3. Modify LUN access permissions 7. which means that everyone on your network can connect to the LUN then read and write content. Click Add access permissions to grant access to specific users. click Access Permissions. 6. The LUN is not secure and open to all users. To secure the LUN. Click Create to have the LUN created.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 5. Grant user access to a LUN White Paper 6 . everyone has read and write access to it by default. Figure 4.

and LUN CLUSTER is used as the cluster shared storage. White Paper 7 . On the Windows Server 2008 R2 cluster node. and enter either the DNS name or the IP address of the iSCSI target. Click the Discover Portal button. Use the default port 3260. Failover cluster iSCSI storage CONNECTING TO THE ISCSI LUNS Windows Server 2008 R2 installs the Microsoft iSCSI Software Initiator by default. and the LUN is secured to only specified users. Repeat the above procedure to create another LUN. The iSCSI LUNs created from the previous section can be accessed using the Microsoft iSCSI Software Initiator. Figure 6. The LUNs need to be connected on all failover cluster nodes. 1.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 8. After clicking Apply. 3. LUN with secured access 9. go to iSCSI Initiator Properties. Click the Discovery tab. Figure 5. LUN WITNESS is used as the cluster witness (also known as quorum) disk. In this white paper. 2. the read/write permission for everyone is automatically removed.

FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 4. Click the Targets tab. Figure 7. This will list the iSCSI qualified target names discovered through the target portal. and click Connect to set up the iSCSI connection. Figure 8. Select the appropriate target. Connect to target White Paper 8 . Also. Check the Add this connection to the list of Favorite Targets option so that the server automatically attempts to restore the connection every time the server restarts. check the Enable multi-path option to allow multipathing to the target. List of iSCSI targets 5.

a. Choose IP addresses from the Initiator IP and Target portal IP drop-down lists. Also repeat the process on the other cluster node to connect to both LUNs. iSCSI connection advanced settings 7. and the target secret is the user password. c. 8. the status of the target is changed from Inactive to Connected. White Paper 9 .FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 6. If the user password is less than 12 characters long. Select Microsoft iSCSI Initiator from the Local Adapter drop-down list. Click the Advanced button to configure more connection settings. After the connection is established. you need to pad it with * to make it 12 characters long. and enter CHAP information for authentication to the secured LUN. The CHAP name is a user name that has been granted read/write access to the LUN on the Iomega device. Figure 9. Check Enable CHAP log on. Repeat the above process to connect to the other iSCSI LUN. b. which will be used to create virtual machines and virtual hard disks.

Open Disk Management and right-click the newly added drive to initialize it using the MBR (Master Boot Record) partition style. Create a partition on an iSCSI drive White Paper 10 .FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES FORMATTING THE ISCSI LUNS After the iSCSI initiator has logged on successfully. Figure 10. Right-click the new disk to create a simple volume using the wizard. Assign a drive letter. provide a volume label. you can use the Microsoft Disk Management snap-in to locate an iSCSI drive presented by the target and manage the drive. 1. Initialize an iSCSI drive 2. Figure 11. and perform a quick NTFS format.

Disk management 4. Figure 12. Repeat the above process to format the iSCSI drives on the other cluster node.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 3. and make sure the drive letters match on both nodes. The clustered servers (called nodes) are connected by physical cables and by software. CREATING A FAILOVER CLUSTER This section explains the steps for adding the failover clustering feature and creating a failover cluster using iSCSI storage. This paper assumes the Microsoft Hyper-V role has already been enabled on the cluster nodes. Repeat the above process to format the other iSCSI drive. Both drives appear in Disk Management and are available for use. A failover cluster groups independent servers together to increase the availability of applications and services. Microsoft HyperV Server can leverage the failover clustering feature to create a highly available virtualization environment for virtual machines. White Paper 11 .

select the checkbox for Failover Clustering.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES ADDING THE FAILOVER CLUSTER FEATURE 1. Open Server Manager and click Features in the left pane and then Add Features on the right. Figure 14. Add a server feature 2. Figure 13. In the Add Features wizard. Add the Failover Clustering feature White Paper 12 .

Click Next and then Install. Figure 16. Feature installation status 4. On either cluster node. go to Start > Administrative Tools > Failover Cluster Manager to open the failover cluster snap-in. Follow the instructions in the wizard to complete the installation.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 3. Failover Cluster Manager White Paper 13 . The wizard reports an installation status. VALIDATING THE FAILOVER CLUSTER CONFIGURATION 1. Repeat the process for the second cluster node. Figure 15.

Follow the instructions in the wizard to specify the two servers. Enter failover cluster nodes name 3. Click Validate a Configuration in the center pane under Management. Figure 18.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 2. Run all validation tests White Paper 14 . Run all tests to fully validate the cluster before creating a cluster. Figure 17.

and click Next. Validation progress is reported with a progress bar. Confirm the test selection. Figure 19.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 4. Validation progress White Paper 15 . Confirm test selection 5. Figure 20.

where SystemRoot is the folder in which the operation system is installed (for example. see SystemRoot\Cluster\Reports\Validation Report date and time. To view the results of the tests after you close the wizard. and select Create a Cluster. This will start the cluster creation wizard. While still on the Summary page. The Summary page appears after the tests are run. Figure 22. Validation test report CREATING A FAILOVER CLUSTER 1.htm. Type the name of each cluster node in the Enter server name textbox. click View Report and read the test results. Figure 21. and click Add to add them one at a time to the list of Selected servers.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 6. Correct any errors before proceeding to create the cluster. Add cluster nodes White Paper 16 . 2. C:\Windows). Right-click Failover Cluster Manager.

Confirm creation of the cluster. If DHCP is not utilized in the environment to automatically configure the administrative access point for the cluster. Figure 23. Figure 24. Specify cluster access point 4. Enter the Cluster Name. Confirmation cluster creation White Paper 17 .FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 3. you need to specify an IP address to be used as the cluster access point.

A status bar is displayed during creation. a summary page displays all the cluster information. The Failover Cluster Manager is updated after a successful cluster creation. Failover cluster White Paper 18 . Figure 26. Proceed to cluster creation. Upon completion. Cluster creation summary 6. Figure 25.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 5.

Figure 29.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 7. Cluster Shared Volumes management 9. A new Cluster Shared Volumes folder is displayed in the cluster manager. On a failover cluster that uses Cluster Shared Volumes. Figure 28. Click Enable Cluster Shared Volumes in the center pane under Configure. multiple clustered virtual machines that are distributed across multiple cluster nodes can all access their Virtual Hard Disk (VHD) files at the same time. Click Add storage in the right pane to add a cluster shared volume. Add a cluster shared volume White Paper 19 . even if the VHD files are on a single disk (LUN) in the storage. Enable Cluster Shared Volumes 8. Figure 27. The cluster manager updates the volume information accordingly upon completion.

Right-click Services and applications in the left pane of the Failover Cluster Manager. Specify a name and storage location for the virtual machine. During creation. The virtual machine can be migrated to another cluster node if the preferred host fails. Specify virtual machine name and storage location White Paper 20 . select Virtual Machines > New Virtual Machine > Node to open the virtual machine creation wizard. VIRTUAL MACHINE CREATION AND OPERATING SYSTEM INSTALLATION 1.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES CREATING A HIGHLY AVAILABLE VIRTUAL MACHINE It is important that you choose the cluster shared volume as the location to store the virtual machine and the virtual hard disk in order to achieve high availability of the virtual machine. a virtual machine needs to be assigned to a cluster node as the preferred host on which the virtual machine runs. Figure 31. where Node is one of the available cluster nodes. Create a new virtual machine 2. Figure 30.

Change virtual machine storage location 4. Figure 32. Check Store the virtual machine in a different location. Assign the amount of memory to allocate to this virtual machine. Figure 33. and click Browse to select a cluster shared volume as the storage location. Assign virtual machine memory White Paper 21 . A cluster shared volume is typically named C:\ClusterStorage\Volume# on the cluster nodes.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 3.

Configure a virtual network for the virtual machine using the network adapter created for the virtual machine. Figure 34. Specify storage for the virtual machine so that an operating system can be installed. Configure virtual machine network 6.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 5. Figure 35. Specify virtual machine storage White Paper 22 .

However. when a virtual machine is made highly available. Reconfigure automatic start action for the virtual machine. Figure 36. Review summary of the virtual machine and proceed to creation. White Paper 23 . 10. 9. OS installation options 8. the management of virtual machine state should be controlled through the cluster service. In general. automatic actions will allow users to automatically manage the state of the virtual machine when the Hyper-V Virtual Machine Management service starts or stops. Connect the operating system installation media appropriately and power up the virtual machine to install OS on the virtual machine.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 7. Decide when and how to install an operating system on the virtual machine.

Right-click the virtual machine and select Manage virtual machine to open the Hyper-V Manager. right-click the virtual machine and select Settings. Right-click Services and applications in the left pane of the Failover Cluster Manager. 1. c. and choose Nothing in the right pane. Figure 37. However. if a virtual machine is created using some other Microsoft management consoles. b. another node in the cluster automatically resumes the virtual machine (a process known as failover).FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES a. the virtual machine must be manually made highly available in the cluster. In Hyper-V Manager. Modify Automatic Start Action settings for a virtual machine MAKING A VIRTUAL MACHINE HIGHLY AVAILABLE Virtual machines that are created using the Failover Cluster Manager are automatically made highly available in the cluster. such as Hyper-V Manager or System Center Virtual Machine Manager. Click Automatic Start Action in the left pane. White Paper 24 . select Configure a Service or Application. If a clustered server fails while running this virtual machine.

Figure 38.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES 2. High Availability Wizard 4. 3. The High Availability Wizard will open. Click Next. select Virtual Machine from the list. On the Select Virtual Machine page. The virtual machine must be offline before it can be made highly available. White Paper 25 . On the Select Service or Application page. check the name of the virtual machine to make highly available.

The virtual machine should be listed there. Confirm the selection and proceed to making the virtual machine highly available. Make a virtual machine highly available 5. 6.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES Figure 39. To verify that the virtual machine is now highly available. Figure 40. White Paper 26 . Expand Nodes. Verify virtual machine high availability– service view b. Expand Services and Applications. Select the node on which you created the virtual machine. you can check in either one of two places in the console tree: a.

Planned failover 4. Click the name of the other node. Figure 42. Right-click the virtual machine and select Move virtual machine(s) to another node.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES Figure 41. Verify virtual machine high availability – node view TESTING PLANNED FAILOVER During a planned failover. 3. 2. the status of a virtual machine is briefly changed from online to pending while the virtual machine is being saved on the original node and being restored on the other node. From the Failover Cluster Manager console tree. expand Services and Application under the cluster name. White Paper 27 . The Current Owner remains the same during this process. 1. The failover process starts by saving the virtual machine state.

Restore virtual machine state TESTING UNPLANNED FAILOVER 1. and click Stop Cluster Service to simulate a server failure. Figure 44. The failover process then restores the virtual machine on the other cluster node. 2. From the Failover Cluster Manager console tree. Save virtual machine state 5. and then right-click the node that runs the virtual machine. Select More Actions.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES Figure 43. White Paper 28 . select Nodes. The Current Owner is changed to be the other node.

000 Bytes. ©2011 Iomega Corporation. and the stylized “i” logo are either registered trademarks or trademarks of Iomega Corporation in the United States and/or other countries. To obtain information about Iomega’s current policies please visit Iomega at www. brand names and company names may be trademarks or designations or their respective owners. ease-of-use. Customers’ total infrastructure costs are further reduced by using an existing Ethernet infrastructure. where 1GB = 1. 4.000.FAILOVER CLUSTERING WITH MICROSOFT HYPER-V ON IOMEGA STORCENTER px SERIES Figure 45. The Iomega® StorCenter™ px series network storage array is certified iSCSI storage array for Windows Server 2008 R2 server.000.com or call 1-888-4iomega (1-888-446-6342). The virtual machine is now in a failed state. All rights reserved. Product in photos may vary slightly from product in package. Stop cluster service 3.iomega. Hyper-V customers enjoy reduced TCO on overall IT costs by lowering both capital and operational costs and improving operational efficiency and flexibility. the predominant way of utilizing IP storage by the Microsoft Hyper-V Server. and/or other countries. WINWP-0811-01 . The virtual machine is moved to the other node automatically. but can be brought online on the other node. This is especially important to small businesses that normally have a very limited IT budget. Unplanned failover CONCLUSION Microsoft Hyper-V dramatically improves the efficiency and availability of resources and applications in organizations of any sizes. Confirm to stop the cluster service on the node. Certain other product names. and highly reliable storage dev ice specifically designed to meet the storage challenges that small businesses face daily. Iomega's specific customer support policies (including fees for services) and procedures change as technology and market conditions dictate. The device supports the iSCSI protocol. Figure 46.S. StorCenter. Product capacities are specified in gigabytes (GB). It provides reliable and proven storage solution to small businesses that plan to deploy Microsoft Hyper-V in a failover cluster. EMC and Lifeline are registered trademarks of EMC Corporation in the U. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The Iomega® StorCenter™ px series network storage array is a high-performance. Iomega.