DS8000 Data Migration using Copy Services in Microsoft Windows Cluster Environment

Transcription

1 DS8000 Data Migration using Copy Services in Microsoft Windows Cluster Environment By Leena Kushwaha Nagaraja Hosad System and Technology Group Lab Services India Software Lab, IBM July 2013

2 Table of contents Abstract Introduction IBM DS DS8870 Hardware IBM DS8870 features Migration Scenario Storage Migration & Host Preparation Activities Data Migration using Metro Mirror feature Preparation of Windows Server 2008 Failover Cluster Activities on Storage Subsystems and Windows Hosts Summary Resources Trademarks and special notices... 12

3 Abstract This Technical Paper describes the series of steps to be followed on Windows host during storage migration from source DS8000 to target DS8000 family. The intent of this paper is to showcase Windows Server 2008 host preparation activities during storage migration in Microsoft Cluster Service (MSCS). Henceforth in this document it is referenced as Failover Cluster because the Resource Group (RG) made up of disk, network, applications, etc. works in Active/Passive mode only. The target audience includes IT professionals with an interest in the IBM storage migration solutions. 1. Introduction Microsoft Clustering feature provides the highest level of availability for business critical applications such as MS SQL, MS Exchange, Oracle Database, etc. The fault tolerant design of cluster ensures there is no single point of failure including multiple servers, multiple network connections. The Microsoft includes significant changes to the clustering architecture designed to enhance flexibility and availability in every new release of its Operating System. Say, for example Failover clustering in Microsoft Windows Server 2008 offers significant advantages over failover clustering in Windows Server 2003, including new quorum models, simplified configuration, and other enhancements that can help increase flexibility and availability. Storage is one area of Windows Failover Clusters that can drastically affect the overall stability of the cluster. Careful planning and design of the storage subsystem will ensure a smooth cluster installation, and will help with any future troubleshooting efforts. - Migrating from old storage (DS8300) to new storage (DS8870) where the windows server cluster (Microsoft Windows Server 2003 Cluster or Windows Server 2008 Failover Cluster) is still on the same servers. In this situation, where you go for new storage in the failover cluster You must perform the copying or moving of data or folders (including shared folder settings) during a migration from old storage to new storage and then assign the same drive letters to disks in the new storage that are assigned to disks in the old storage. This paper describes the various steps involved in migration of Windows Failover Cluster from one storage (DS8300) to another storage (DS8870) and how to avoid the common pitfalls that affect stability such as incompatible or inconsistent storage drivers etc.,. This guide does not include the process of creating a failover cluster and Cluster Settings migration. Recommendation: It is also recommended to establish SAN zoning to isolate the cluster I/O traffic to only include cluster servers and storage controllers. This helps to reduce I/O latencies on the SAN potentially caused by other operating systems.

4 2. IBM DS DS8870 Hardware IBM System Storage DS8000 series is designed as a high-performance, high capacity, and resilient series of disk storage system that supports continuous operations. The IBM System Storage DS8870 is the most advanced model in the IBM DS8000 lineup and is equipped with IBM POWER7 based controllers. The IBM POWER7 processor technology supports higher Performance and delivers up to three times performance improvement in I/O operations per second in transaction processing workload environments as the prior model. The IBM DS8870 Storage is equipped with high-density storage enclosures that are populated with 24small-form-factor SAS-2 drives or storage enclosures for 12 large-form-factor nearline SAS drives. The DS8870 storage subsystems also can be equipped with Solid-State Drives (SSDs). The DS8870 (as show in Figure 1-1) is IBM s fifth-generation high-end disk system in the DS8000 series. Figure1: IBM DS8870 Storage Subsystem 2.2. IBM DS8870 features The DS8000 series DS8870 offers high availability, multiplatform support, including System z, and simplified management tools to help provide a cost-effective path to an on-demand world. The DS8870 supports functions such as point-in-time copy functions with IBM FlashCopy, FlashCopy Space Efficient, and Remote Mirror and Copy functions with Metro Mirror, Global Copy, Global Mirror, Metro/Global Mirror, IBM z/os Global Mirror, and z/os Metro/Global Mirror. I/O Priority Manager and Easy Tier functions are also supported on DS8870 storage units.

5 3. Migration Scenario The objective of this solution implementation, is to showcase, Windows host preparation activities during storage migration. This solution is applicable for Windows Server 2008 Failover Cluster. This paper demonstrates the approach followed for below listed activities: 1. Storage Migration ( Migration from DS8300 to Storage DS8870 using Metro Mirroring Feature) 2. Windows Host Preparation ( Activities during Pre & Post Storage Migration) Figure 2: Remote Copy Services Solution Setup: The environment setup includes the below mentioned hardware and software. Hardware Components Model No : Operating System / Firmware Levels Servers IBM System X3650 M3 2 Windows Server 2008 R2 Enterprise Edition SAN Switch B40 SAN Switches 2 FW: 66.1 Storage DS8300 (Old Storage) 1 R4.3(Bundle ) DS8870 (New Storage) 1 R7 (Bundle ) In the example, Microsoft Cluster has been configured on IBM X-series hardware that runs Windows Server 2008 R2 Enterprise Edition. This setup has Cluster aware application MS SQL Database Server This SQL Database Server was hosted on two LUNs a Database LUN and a Transaction Log LUN provisioned to each of the two nodes in the Cluster from external storage DS8300. The requirement is to move the data from the Storage DS8300 to the storage DS8870, which is achieved by DS8000 Metro Mirroring feature.

6 4. Storage Migration & Host Preparation Activities 4.1. Data Migration using Metro Mirror feature Pre-Requisite: Metro Mirror License is required on both the Storage boxes Step-By-Step Procedure for Migration: Step-1: Identify LUNs on DS8300 which needs to be migrated to DS8870 dscli> lsfbvol -l -volgrp v38 Date/Time: July 7, :23:36 AM IST IBM DSCLI Version: DS: IBM LH461 Name ID accstate datastate configstate devicemtm datatype extpool sam captype cap (2^30B) cap (10^9B) cap (blocks) volgrp reqcap (blocks) eam ============================================================================= ============================================================================= ======================== SQL_Vol1 2A07 Online Normal Normal FB 512 P18 Standard DS V rotatevols LOG_Vol2 2A08 Online Normal Normal FB 512 P18 Standard DS V rotatevols

7 Quorum_Vol3 2A09 Online Normal Normal FB 512 P18 Standard DS V rotatevols - Step-2: Create New LUNs on DS8870 with Equal Size mkfbvol -dev IBM BLG51 -extpool P3 -cap 250 -name SQL_ mkfbvol -dev IBM BLG51 -extpool P3 -cap 100 -name LOG_ mkfbvol -dev IBM BLG51 -extpool P2 -cap 1 -name Quorum_ Step 3: Configure Zone between source Storage (DS8300) and Target Storage (DS8870) zonecreate "TMP_MM_DS8300_DS8870_100","DS8300_100;DS8870_100" Zonecreate "TMP_MM_DS8300_DS8870_104","DS8300_100;DS8870_104" Step 4: Configure PPRC path between DS8300 and DS8870 mkpprcpath -dev IBM LH461 -remotedev IBM BLG51 -remotewwnn FFD48C -srclss 18 -tgtlss 14 I0632:I0101 I0702:I0100 mkpprcpath -dev IBM LH461 -remotedev IBM BLG51 -remotewwnn FFD48C -srclss 19 -tgtlss 15 I0632:I0101 I0702:I0100 Step-3: Configure Metro Mirror between source and target LUNs mkpprc -dev IBM LH461 -remotedev IBM BLG51 -type mmir 2A07:0100 mkpprc -dev IBM LH461 -remotedev IBM BLG51 -type mmir 2A08:0101 mkpprc -dev IBM LH461 -remotedev IBM BLG51 -type mmir 2A09: Preparation of Windows Server 2008 Failover Cluster Step-By-Step Procedure for Activities on Windows Hosts: Pre-requisites prior to Storage Migration: Take Backup of Windows Server 2008 along with System State Capture Cluster configuration parameters Verify that the HBA firmware and Multipath Software on Windows Server 2008 Server is compatible with DS8870 at the link give below, else need to install the appropriate packages. STEP-4: Cluster Health Check- Sanity Check on Cluster Resource Movement and Cluster Services To verify cluster resource movement, Move the Cluster Resources between each of the nodes, using the Failover Cluster Management. The testing must be successful without any errors. To verify the Cluster state-move all resources from Node B to Node A and then shut down Node B. Now Stop the Cluster Services on Node A and shut down Node A. To bring the cluster up, Power on

8 Node A, start the Cluster services on Node A, bring up the cluster one Single Node first, Now power on Node B, bring up database and application - Confirm the services are up with no issue STEP-5: Install Multipath software SDDDSM and verify the status of multipath Download the Appropriate SDDDSM package suitable for Windows Server 2008 R2 Enterprise Edition (SDDDSM_x64_2.4.3_3_5). Move all the Cluster Resources to Node 1. And on Node 2, run SDDDSM setup followed with a reboot. Do health Check -Failover all resources to Node 2 and verify no errors are logged in cluster events and system logs. Now Run the SDDDSM setup on Node 1 and once complete, reboot Node 1. Repeat STEP-1 to ensure the Cluster state is fine as shown below: Figure 2: Cluster Services and Application Status is Online Execute the below commands to check the status of Multipath #datapath query device #datapath query essmap Captured the Drive Letter and Volume Name as shown below: Figure 3: Drive letter and Volume Name

9 4.3. Activities on Storage Subsystems and Windows Hosts Step-By-Step Procedure for Storage Failover: Step 4: Un-mount the disks by removing the drive letter Step 5: Bring down the servers STEP-6: Removing Data LUNs from Old Storage DS8300 Unmap the LUNs from DS8300 dscli> chvolgrp action remove volume 2A07 v38 dscli> chvolgrp action remove volume 2A08 v38 dscli> chvolgrp action remove volume 2A09 v38 Check all pairs are in Full Duplex lspprc -dev IBM LH461 -remotedev IBM BLG51 2A07:0100 lspprc -dev IBM LH461 -remotedev IBM BLG51 2A08:0101 lspprc -dev IBM LH461 -remotedev IBM BLG51 2A09:0000 Remove the Replication Relationship rmpprc -dev IBM LH461 -remotedev IBM BLG51 2A07:0100 rmpprc -dev IBM LH461 -remotedev IBM BLG51 2A08:0101 rmpprc -dev IBM LH461 -remotedev IBM BLG51 2A09:0000 STEP-7: Perform Zoning Activities Remove zoning between DS8300 and Windows Hosts (SMMABT_1 and SMMABT_2) Create New Zones between Windows Servers and DS8870 STEP-8: Assign the Data LUNs from New Storage DS8870 to Hosts Create a Volgrp V3 and add the volumes to it. chvolgrp -dev IBM BLG51 -action add -volume 0100 V3 chvolgrp -dev IBM BLG51 -action add -volume 0101 V3 chvolgrp -dev IBM BLG51 -action add -volume 0000 V3 Now add the host to the Volgrp V3 mkhostconnect -wwpn 50060B0000C2621A -hosttype Win2008 -volgrp V3 SMABT1_hba0 mkhostconnect -wwpn 50060B0000C hosttype Win2008 -volgrp V3 SMABT1_hba1 mkhostconnect -wwpn 50060B0000C2621E -hosttype Win2008 -volgrp V3 SMABT2_hba0 mkhostconnect -wwpn 50060B0000C2621C -hosttype Win2008 -volgrp V3 SMABT2_hba1 STEP-8: Scan the New LUNs on Windows Hosts Power on Node 1 (SMMABT_1) And from Windows Disk Manager Management Console, re-scan the New LUNs that were assigned from the Storage DS8870. Verify the LUNs are detected by executing the following commands

10 #datapath query device #datapath query essmap Once LUNs detected, initialize the new LUNs without formatting Assign the same Drive letter and Volume Name as Captured in STEP-5 Perform the Above Steps on Node 2 (SMMABT_2) STEP-9: Bringing Cluster and application online Open the Failover Cluster Management Console and Start the Cluster Services Start the appropriate services such as the SQL services. Do a health check of the critical events, services and cluster state Once all the statuses are a green, Failover the resources to Node 2 and do a health check of the critical events, services and cluster state. Verified the Application - SQL Migration Success was successful. STEP-10: Delete OLD LUNs on DS8370 Deleted the OLD LUNs on DS8300 Deleted the Old Volgrp V38 on DS Summary The IBM System Storage DS8870 is designed to manage a broad scope of storage workloads that exist in today s complex data center, doing it effectively and efficiently. The integration of flexible and reliable Storage DS8870 with Microsoft Failover Cluster not only aids capacity but will also ensure that users can have nearly constant access to important server-based resources. The copy services functions make the DS8000 series a key component for disaster recovery solutions, data migration activities and for data duplication and backup solutions. The migrations steps described in this paper allows a seamless migration to the IBM System Storage DS8870 which is the most advanced model in the IBM DS8000 lineup.

11 Resources These Web sites provide useful references to supplement the information contained in this document: IBM System Storage DS8000 Series Overview: - IBM System Storage DS8870 Architecture and Implementation - IBM System Storage DS8000 Host Attachment Guide - Microsoft Failover Clustering Overview - Configure a Two Node Microsoft Failover Cluster - Windows Server Failover Clustering (WSFC) with SQL Server -

12 Trademarks and special notices Copyright IBM Corporation All rights Reserved. References in this document to IBM products or services do not imply that IBM intends to make them available in every country. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at