19
October 10, 2014 By Tech Note Microsoft® Hyper-V® Failover Clustering with Hitachi Virtual Storage Platform G1000 Using Global-active Device Rick Andersen
October 10, 2014
By
Tech Note
Microsoft® Hyper-V® Failover Clustering with Hitachi Virtual Storage Platform G1000 Using Global-active Device
Rick Andersen
FeedbackHitachi Data Systems welcomes your feedback. Please share your thoughts by sending an email message to [email protected]. To assist the routing of this message, use the paper number in the subject and the title of this white paper in the text.
Table of ContentsTest Configuration Overview..............................................................................3
Tested Components........................ ....................................................................9
Test Case Scenarios .........................................................................................11
Conclusion........................ .................................................................................14
1
1
Microsoft® Hyper-V® Failover Clustering with Hitachi Virtual Storage Platform G1000 Using Global-active DeviceTech Note
A new global-active device capability within Hitachi Storage Virtualization Operating System (SVOS) and Hitachi Virtual Storage Platform G1000 (VSP G1000) is now available. This feature enables a virtual device to be presented as a single LUN between two VSP G1000 storage systems that are separated by up to 100 KM for load balancing and active/passive availability. This enables an application from either site A or site B to access a shared device through either VSP G1000 and continue operations if one of them should become unavailable. Cluster applications like SQL Server and Hyper-V Failover Clustering can access the device through either site as well as through either VSP G1000 for greater availability.
Hyper-V Failover clustering can utilize global-active device to quickly move virtual machines between sites with zero RTO/RPO.
A combination of software and hardware products from Hitachi Data Systems provides the following key functions to a Microsoft Hyper-V infrastructure:
Host multipathing using Hitachi Dynamic Link Manager
Internal and external storage provisioning
Synchronous bidirectional data movement across metro cluster distances
Transparent storage failover
The global-active device solution was tested with Microsoft Hyper-V Failover Clustering and SQL Server® guest clustering for this Tech Note. Global-active device allows for the rapid failover of virtual machines between two geographically separated sites using global-active device mirroring technologies, and also provides for seamless workload failover by implementing cross-site connections between servers in geographically separated sites.
This Tech Note documents the high level requirements to set up and utilize global-active device in Microsoft Hyper-V Failover Cluster environments. This Tech Note also provides test results of migrating virtual machines (VMs) between storage arrays and the results of failover actions within the cluster. An SQL I/O tool was used to provide load on the VMs being migrated with various I/O profiles to ensure that stress was placed on both the storage and server.
2
2
This document provides the following:
A proof point of the basic functionality of this solution
High level technical reference for considering this solution
High level reference of the use case implementation
This document does not cover the following:
Performance measurement at the server and storage level
Sizing information
Best practice
Implementation details
For implementation details, contact your Hitachi Data Systems representative.
Note — Testing of this configuration was in a lab environment. Many things affect production environments beyond prediction or duplication in a lab environment. Follow the recommended practice of conducting proof-of-concept testing for acceptable results in a non-production, isolated test environment that otherwise matches your production environment before your production implementation of this solution.
3
3
Test Configuration OverviewFigure 1 illustrates the high-level logical design of the test configuration for Hitachi Virtual Storage Platform G1000 using global-active device, Hitachi Compute Blade 500 (CB 500), and Hitachi Unified Storage 150 (HUS 150).
Figure 1
Using global-active device allows virtual machines to failover between the Hitachi Virtual Storage Platform G1000 storage systems in the event of an I/O failure to the local storage system. The combination of global-active device with Hitachi Dynamic Link Manager (HDLM) enables Hyper-V hosts to see the primary volume (P-VOL) and secondary volume (S-VOL) as a single LUN. If a host is unable to access the production volume on the local storage system, I/O from the Hyper-V hosts redirects to the secondary volume on the remote storage system.
4
4
Global-active device users create a synchronous remote copy of a production volume. Prior to creating a global-active device pair, use the Hitachi Command Suite (HCS) quorum disk operation graphical user interface to configure a LUN from the Hitachi Unified Storage 150 storage system as a quorum disk. Configure the primary storage system and the secondary storage system the same way.
Virtual Storage MachineGlobal-active device introduces the concept of a virtual storage machine that is created in the secondary G1000 storage system. A virtual storage machine is created in the secondary array that mimics the G1000 primary array serial number. Volumes (S-VOLs) are created in the virtual storage machine on the secondary array to match those defined in the primary array (P-VOLs). The attached servers see the combination of the physical G1000 at the primary site and virtual storage machine in the G1000 at the secondary site as a single physical system accessible over multiple Fibre Channel paths..
Hitachi Dynamic Link ManagerHitachi Dynamic Link Manager provides the following:
Load balancing by distributing loads across multiple paths
Path failover by automatically switching to another path if there is a failure in the path that is currently being used
Path failback by manually or automatically bringing a path back online after recovering from an error
Use of Dynamic Link Manager with Host Mode Option 78 gives you the option to specify non-preferred paths to a certain storage array. You can prevent I/O traffic from traveling across long distances from the Hyper-V host to the non-local storage. This minimizes response time and the cost of WAN traffic.
Hitachi Dynamic Link Manager is recommended for single server global-active device configurations and cross-path global-active device configurations.
There are multiple global-active device configurations that can be implemented based on availability and recovery requirements. These are described in the sections that follow.
5
5
Single Server Configuration In this scenario, a Microsoft Windows Server® 2012 R2 server is connected to Hitachi Virtual Storage Platform G1000 at the primary site and secondary site. Hitachi Dynamic Link Manager multipath software is used to enable automatic failover if storage fails at the primary or secondary site. This configuration is shown in Figure 2.
Figure 2
6
6
Microsoft Hyper-V Failover Cluster ConfigurationIn this scenario, a server is connected to the Hitachi storage system at the primary site and a server is also connected to a storage system at the secondary site. Both servers are part of the same Hyper-V failover cluster configuration. In this configuration, Hyper-V failover clusters can seamlessly fail over between sites with no interruption to applications running within the failover cluster. This configuration is shown in Figure 3.
Figure 3
7
7
Cross-Path ConfigurationIn this scenario a primary server and a secondary server are both connected to VSP G1000 storage at the primary site and VSP G1000 at the secondary site. If a failure occurs in one of the storage systems, the multipath software can switch the server I/O to the other site. Microsoft Hyper-V Failover clusters are implemented to allow failover and fail back between the servers. This configuration is used for all test scenarios in this Tech Note and is shown in Figure 4.
Figure 4
8
8
The high level steps required to implement this solution are:
1. Configure Fibre Channel connections between the Microsoft Windows Server 2012 R2 Hyper-V servers at the primary and secondary sites to VSP G1000 storage arrays. Ensure that cross connections are in place as shown in Figure 4.
2. Configure replication Fibre Channel connections between VSP G1000 at the primary site and VSP G1000 at the secondary site.
3. Create quorum devices on the primary VSP G1000, the secondary VSP G1000, and the storage that will be used as an external device. In this solution, a Hitachi Unified Storage 150 was externalized from each VSP G1000 using Hitachi Universal Volume Manager.
Note — Following recommended practice, connect Hitachi Unified Storage 150 to each Hitachi Virtual Storage Platform G1000 from a third site within metro distance from each site to ensure the quorum disk is accessible from at least one site during a site-wide failure.
4. Install Hitachi Dynamic Link Manager on all nodes and enable host mode option 78 in the Host Storage Group for all servers that are connected via the secondary paths. Do not set this option on the primary path.
5. Create a virtual storage machine on secondary storage. Then, define the S-VOLs that are a part of the copy pairs between the two Virtual Storage Platform G1000 storage systems. The S-VOL volume configuration looks exactly like the P-VOL volume configuration. This means that the servers at the secondary site communicate with the secondary subsystem the same way as servers at the primary site communicate with the primary subsystem.
6. Create global-active device pairs.
7. Activate secondary paths
8. Add SAN secondary paths
9. Confirm secondary paths on application servers
9
9
T
Tested ComponentsThese are descriptions of the key hardware and software components used to test this solution.
Table 1 lists information about the hardware components used in this solution. Table 2 lists information about the software components used in this solution.
able 1. Hardware Components
Hardware Description Version Quantity
Hitachi Virtual Storage Platform G1000
Dual controllers
16 × 8 Gb/sec Fibre Channel ports
1 TB cache memory
8 × 900 GB 10k RPM SAS disks, 2.5 inch SFF (Replicated LUNs and CSVs)
4 x 900 GB 10k RPM SAS disks, 2.5 inch SFF (Command Device)
80-01-42 2
Hitachi Unified Storage 150 Dual controllers
16 x 8 Gb/sec Fibre Channel ports
32 GB cache memory
8 x 600 GB 10k RPM SAS disks, 2.5 inch SFF (Quorum Device)
0977/H 1
Hitachi Compute Blade 500 chassis
8-blade chassis
2 Brocade 5460 Fibre Channel switch modules, each with 6 × 8 Gb/sec uplink ports
2 Brocade VDX 6746 Ethernet switch modules, each with 8 × 10 Gb/sec uplink ports
2 management modules
6 cooling fan modules
4 power supply modules
SVP: A0215-E-9403
5460: FOS 7.0.2c
VDX6746: NOS 4.1.2
2
10
10
T
T
520H B2 server blade Half blade
2 × 12-core Intel Xeon E5-2697v2 processors, 2.70 GHz
256 GB RAM
16 × 16 GB DIMMs
Firmware: 01-89
BMC/EFI: 01-89/07-50
4
Brocade 6510 Switch SAN switch with 48 × 8 Gb/sec Fibre Channel ports
FOS 7.1.1 4
Brocade VDX 6740 Switch Ethernet switch with 48 × 10 Gb/sec ports
NOS 4.1.2 4
able 2. Software Components
Software Version
Hitachi Dynamic Provisioning Microcode Dependent
Microsoft® Windows Server® 2012 Datacenter edition, R2
Microsoft Windows Server 2012 (for Hitachi Command Suite) Standard edition, R2
Microsoft Windows Server 2012 (for pair management server) Datacenter edition, R2
Microsoft SQL Server® 2012
Hitachi Command Suite
Hitachi Device Manager
Hitachi Replication Manager
8.0.1
Hitachi Dynamic Link Manager 8.0.1
Command control interface Microcode Dependent
able 1. Hardware Components (Continued)
Hardware Description Version Quantity
11
11
Test Case Scenarios For testing purposes, the following test cases were run to validate the Microsoft Hyper-V Failover cluster and SQL failover results.
Microsoft Windows Server 2012 R2 Hyper-V test cases
Use Hyper-V Live Migration to migrate virtual machines between Site 1 and Site 2
Use Hyper-V to failover virtual machines from Site 1 to Site 2
Failover of a SQL Server clustered instance under Hyper-V using virtual Fibre Channel
Failover of a standalone SQL Server virtual machine under Hyper-V using standard VHDx disks and cluster shared volumes
Failure test cases
Single storage path failure
Site 1 storage failure
All active paths to local storage system fail for a single host on either site
All paths down occurs in any Hyper-V host in the cluster
Quorum disk failure
Storage replication link failure
Site 1 failure/Site 2 failure
Recovering from storage failover (failback)
12
12
T
UMmS
UmS
Af
S
AsH
Table 3 summarizes the results of the tested scenarios:
able 3. Tested Scenario Results Summary
Scenario Global-Active Device and Hitachi Dynamic Link Manager Behavior
Observed Hyper-V behavior
sing Microsoft® Hyper-V® Live igration to migrate virtual achines between Site 1 and ite 2.
No impact Virtual machine migrates to Site 2 hosts and I/O is directed to the local storage S-VOL on Site 2.
sing Hyper-V to failover virtual achines between ite 1 and Site 2.
No impact Virtual machine fails over to Site 2 hosts and I/O is directed to the local storage S-VOL on Site 2.
n active path in a single host ails.
Host I/O is redirected to an available active path via Hitachi Dynamic Link Manager PSP
Another active path is used
No disruption to virtual machines
ite 1 storage system fails. Storage failover
Global-active device verifies data integrity with the quorum disk before failover
Global-active device splits the pair replication and S-VOL is converted to SSWS (S Local)
Host I/O is redirected via Dynamic Link Manager SATP to the standby S-VOL paths on the Site 2 storage system.
Active paths to P-VOL are reported dead
Standby paths to S-VOL become active
No disruption to virtual machines
ll active paths to the local torage system fail for any yper-V host in the cluster.
Host I/O in each Site is redirected to available standby (non-preferred) paths on the remote storage system via Dynamic Link Manager PSP.
Active paths to the local storage system are reported dead
Standby paths to the remote storage system become active
No disruption to virtual machines
13
13
AH
S
T
ll paths down occurs in any yper-V host in the cluster.
Storage failover does not occur.
Hyper-V will restart virtual machines on the other hosts.
uorum disk fails or all paths to uorum disk removed.
Replication between P-VOL and S-VOL stop with both P-VOL and S-VOL in PSUE state. All access to S-VOL is blocked and is failed over to P-VOL (P Local).
Host I/O in Site 2 is redirected to standby paths to P-VOL on remote storage in Site 1.
Storage failover occurs.
Active paths to S-VOL are reported dead
Standby paths to P-VOL become active
No disruption to virtual machines
torage replication link failure. Global-active device verifies the data integrity with quorum disk and determines that one of two (P-VOL and S-VOL) is as local I/O mode (the other is as block I/O. The decision depends on the state of both volumes which is notified and written to quorum disk.
When the volume (for example, P-VOL) is chosen to continue to perform host I/O, all access to the other (S-VOL) is blocked and is failed over to P-VOL (P Local).
Host I/O in Site 2 is redirected to standby paths to P-VOL on remote storage in Site 1.
Active paths to S-VOL are reported dead
Standby paths to P-VOL become active
No disruption to virtual machines
able 3. Tested Scenario Results Summary (Continued)
Scenario Global-Active Device and Hitachi Dynamic Link Manager Behavior
Observed Hyper-V behavior
14
14
ConclusionThis Tech Note documents the high level design of a Microsoft Hyper-V failover cluster and SQL Server cluster with global-access device on Hitachi Virtual Storage Platform G1000. Multiple components work together to provide an infrastructure with continuous availability:
Hitachi Dynamic Link Manager provides host multipathing with deep storage integration.
Global-active device permits you to use host-based applications to failover between Hitachi Virtual Storage Platform G1000 systems with no disruption.
These components are tightly integrated with Microsoft Windows Server 2012 R2 Hyper-V virtual infrastructures to protect the data center from various failure scenarios. You can leverage the benefits of synchronous data replication beyond traditional disaster recovery protection to include workload balancing across sites and coordinated site-wide maintenance with no downtime.
For More InformationHitachi Data Systems Global Services offers experienced storage consultants, proven methodologies and a comprehensive services portfolio to assist you in implementing Hitachi products and solutions in your environment. For more information, see the Hitachi Data Systems Global Services website.
Live and recorded product demonstrations are available for many Hitachi products. To schedule a live demonstration, contact a sales representative. To view a recorded demonstration, see the Hitachi Data Systems Corporate Resources website. Click the Product Demos tab for a list of available recorded demonstrations.
Hitachi Data Systems Academy provides best-in-class training on Hitachi products, technology, solutions and certifications. Hitachi Data Systems Academy delivers on-demand web-based training (WBT), classroom-based instructor-led training (ILT) and virtual instructor-led training (vILT) courses. For more information, see the Hitachi Data Systems Services Education website.
For more information about Hitachi products and services, contact your sales representative or channel partner or visit the Hitachi Data Systems website.
Corporate Headquarters2845 Lafayette Street, Santa Clara, California 95050-2627 USAwww.HDS.com
Regional Contact InformationAmericas: +1 408 970 1000 or [email protected], Middle East and Africa: +44 (0) 1753 618000 or [email protected] Asia-Pacific: +852 3189 7900 or [email protected]
© Hitachi Data Systems Corporation 2014. All rights reserved. HITACHI is a trademark or registered trademark of Hitachi, Ltd. “Innovate with Information” is a trademark or registered trademark of Hitachi Data Systems Corporation. Microsoft, Hyper-V, SQL Server, and Windows Server are trademarks or registered trademarks of Microsoft Corporation. All other trademarks, service marks, and company names are properties of their respective owners.
Notice: This document is for informational purposes only, and does not set forth any warranty, expressed or implied, concerning any equipment or service offered or to be offered by Hitachi Data Systems Corporation.
AS-331-00, October 2014
