IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager: An overview of disaster recovery preparation and workload migration for multisite VMware vSphere clouds using IBM NAS and vSphere host-based replication solutions
Upcoming SlideShare
Loading in...5
×
 

IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager: An overview of disaster recovery preparation and workload migration for multisite VMware vSphere clouds using IBM NAS and vSphere host-based replication solutions

on

  • 2,705 views

The purpose of this paper is to set appropriate expectations for customers with regard to disaster recovery and workload migration options when using IBM NAS solutions with VMware vCenter Site ...

The purpose of this paper is to set appropriate expectations for customers with regard to disaster recovery and workload migration options when using IBM NAS solutions with VMware vCenter Site Recovery Manager host-based replication. To know more about VMware, visit http://ibm.co/SOUdWO.

Statistics

Views

Total Views
2,705
Views on SlideShare
2,705
Embed Views
0

Actions

Likes
0
Downloads
18
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager: An overview of disaster recovery preparation and workload migration for multisite VMware vSphere clouds using IBM NAS and vSphere host-based replication solutions IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager: An overview of disaster recovery preparation and workload migration for multisite VMware vSphere clouds using IBM NAS and vSphere host-based replication solutions Document Transcript

  • IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery ManagerAn overview of disaster recovery preparation and workload migration formultisite VMware vSphere clouds using IBM NAS and vSphere host-based replication solutions Benton Gallun IBM Systems and Technology Group ISV Enablement June 2012 © Copyright IBM Corporation, 2012
  • Table of contentsAbstract........................................................................................................................................1Introduction .................................................................................................................................1Intended audience.......................................................................................................................1Overview of a disaster recovery solution .................................................................................1IBM Storwize V7000 Unified NAS...............................................................................................2 Storwize V7000 Unified overview ............................................................................................................ 3 Block hardware and concepts ........................................................................................... 3 Storwize V7000 Unified for SRM ............................................................................................................. 5 File hardware and concepts .............................................................................................. 5IBM SONAS..................................................................................................................................6 Overview of VMware vCenter Site Recovery Manager with IBM SONAS............................................... 7 Common NAS features of Storwize V7000 Unified and SONAS ............................................................ 7VMware overview ......................................................................................................................10 VMware vSphere ESXi 5.0 .................................................................................................................... 10 VMware vCenter Server......................................................................................................................... 11 VMware vSphere Client ......................................................................................................................... 12 vCenter Site Recovery Manager............................................................................................................ 12 Protected and recovery sites ................................................................................................................. 12 Host-based replication ........................................................................................................................... 13 Database................................................................................................................................................ 13Installation of SRM and vSphere Replication components...................................................14 Database preparation ............................................................................................................................ 14 SRM Server installation on vCenter Server ........................................................................................... 14 Connect the sites ................................................................................................................................... 16 Resource mappings......................................................................................................... 21 Folder mappings.............................................................................................................. 22 Network mappings........................................................................................................... 23Configuring vSphere Replication ............................................................................................23 Deploy the VRM Server ......................................................................................................................... 24 Configure the VMRS connection ........................................................................................................... 27 Deploy a VR server................................................................................................................................ 28 Registering a VR server with the VRM server ....................................................................................... 28Configuring VM Replication .....................................................................................................28Protecting workloads................................................................................................................30Testing workloads.....................................................................................................................41Migrating workloads .................................................................................................................43Reprotecting workloads ...........................................................................................................45Scaling / Improving replication times .....................................................................................45 Deploy multiple VRS appliances and multiple vCenters........................................................................ 45 Prepopulating virtual disks..................................................................................................................... 46 IBM Storwize V7000 Unified, SONAS, and VMware Site Recovery Manager
  • Best practices............................................................................................................................47Summary....................................................................................................................................48Appendix A: Glossary...............................................................................................................49Appendix B: Resources............................................................................................................50About the author .......................................................................................................................51Trademarks and special notices..............................................................................................52 IBM Storwize V7000 Unified, SONAS, and VMware Site Recovery Manager
  • Abstract This paper offers configuration information regarding the IBM Storwize V7000 Unified network- attached storage (NAS) system and IBM Scale Out Network Attached Storage (SONAS) solutions in an ESX environment with VMware vCenter Site Recovery Manager using VMware vSphere host based replication. The purpose of this paper is to set appropriate expectations for customers with regard to disaster recovery (DR) and workload migration options when using IBM NAS solutions with VMware vCenter Site Recovery Manager (SRM) host-based replication.IntroductionUntil recently VMware SRM required the use of site recovery adapter (SRA) specific to the storagesolution being used. SRAs from multiple vendors / solutions could not be used together. VMware host-based replication, released with VMware vSphere 5.0 for SRM 5.0 support now enables customers toprotect vSphere workloads on any VMware certified vSphere datastore opening new flexibility in thedeployment of new data centers for disaster recovery preparation.Intended audienceThis paper is intended for anyone interested in using VMware SRM with IBM® Storwize® V7000 Unifiedand IBM SONAS for business continuity. This paper assumes that the user has some background in bothIBM scale out NAS and VMware products, specifically Storwize V7000 Unified, SONAS, and VMwarevCenter server. In addition, the reader must have sufficient knowledge about DR solutions and the workflow required in a DR scenario.Overview of a disaster recovery solutionAs IT systems have become increasingly critical to the smooth operation of enterprises, the importance ofensuring their continued operation, including rapid recovery when subsystems fail, has increased. Beforeselecting a disaster recovery strategy, a disaster recovery planner must refer to their organizationsbusiness continuity plan, which indicates the key metrics of recovery point objective (RPO) and recoverytime objective (RTO) for various business processes. The metrics specified for the business processesmust then be mapped to the underlying IT systems and infrastructure that supports those processes.After mapping the RTO and RPO metrics to IT infrastructure, the DR planner can determine the mostsuitable recovery strategy for each system.RPO – This refers to the point in time to which data must be recovered as defined by the organization.This is generally a definition of what an organization determines as an acceptable loss in a disastersituation.RTO – This refers to the duration of time and a service level within which a business process must berestored, following a disaster or disruption, in order to avoid unacceptable consequences associated witha break in business continuity. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 1
  • The ideal solution will have both: a low RPO (in minutes) and RTO (ranges from minutes to hours). It isimportant to test a DR solution to find whether it is suitable and efficient for business continuity.IBM Storwize V7000 Unified NASThe IBM Storwize V7000 Unified builds upon the proven IBM Storwize V7000 storage to offer both blockand file storage services in a single unified storage array. It has been certified for virtualization usingVMware vSphere 5.0 for comprehensive server and storage virtualization. The highly scalable storagecapacity of Storwize V7000 Unified can be used to start with smaller capacities and then grow toconsolidate data from multiple servers and storage systems for more efficient infrastructure utilization(particularly storage efficiency) and ease of management and administration.You can find certification information about Storwize V7000 (block) and Storwize V7000 Unified (NFS) onthe VMware Storage HCL at the following links:Block (SAN):http://partnerweb.vmware.com/comp_guide2/detail.php?deviceCategory=san&productid=18864&vcl=trueNFS (NAS):http://partnerweb.vmware.com/comp_guide2/detail.php?deviceCategory=san&productid=20569&vcl=trueThe Storwize V7000 is a modular storage system built from the IBM System Storage® SAN VolumeController technology base and utilizing Redundant Array of Independent Disks (RAID) technology fromthe IBM System Storage DS8000® family to deliver a virtualized, enterprise-ready, mid-range storagesolution. The IBM Storwize V7000 storage system enables customers to improve application flexibility,responsiveness, and availability, while reducing storage usage and complexity through storagevirtualization and the following features:  Metro Mirror and Global Mirror perform synchronous and asynchronous data replication between IBM Storwize V7000 systems at varying distances to protect data and keep services online in downtime situations.  IBM Tivoli® Storage FlashCopy® Manager functionality enables for the creation of instant volume copies for data protection and flexibility  Virtualization enables volume migration and mirroring to any storage managed by the IBM Storwize V7000 system.  IBM System Storage Easy Tier® automatically manages the efficient usage of solid-state drives (SSDs) and increases application performance by promoting frequently-accessed data to SSDs.The IBM Storwize V7000 Unified storage system builds upon the proven IBM Storwize V7000 storagesystem by including two file modules, which adds the following features and functions:  File replication and file-level snapshots for business continuity and disaster recovery.  Support for Network File System (NFS), Common Internet File System (CIFS), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), and Secure Copy Protocol (SCP) file protocols in addition to the existing Fibre Channel (FC) and iSCSI block functions provided by the Storwize V7000 system. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 2
  •  Intuitive, easy-to-use GUI which tightly integrates management for block and file capabilities.  IBM Active Cloud Engine™ technology delivers automated storage efficiency capabilities including user-definable policy-based file management.  Integrated IBM Tivoli Storage Manager client for simplified backup to Tivoli Storage Manager servers and support for other third-party NDMP backup clients.The subsequent sections describe the IBM Storwize V7000 Unified hardware and concepts.Storwize V7000 Unified overviewThe IBM Storwize V7000 Unified system is the first IBM-developed midrange unified storage offering thatpresents both file and block interfaces from the same storage system. It is built on the proven StorwizeV7000 storage system and therefore all block storage features and functions are available. Block hardware and concepts A Storwize V7000 system is made up of 2U drive enclosures. One control enclosure with the option to add up to nine expansion controllers is required for additional capacity. All enclosures have the option of 12-drive slots (as shown in Figure 1) or 24-drive slots (as shown in Figure 2). Figure 1: Storwize V7000 12-disk enclosure Figure 2: Storwize V7000 24-disk enclosure Within the control enclosure are two node canisters, also known as an I/O group (which form an active-active processing unit), act as the management point for the storage system and service all I/O to host systems. Storwize V7000 can have between one to nine expansion enclosures, which are connected to the control enclosure through redundant serial-attached SCSI (SAS) connections and form the system’s internal storage capacity. The control and expansion controllers support a wide range of drives: 2.5-inch drive support  146 GB, 300 GB 15,000 rpm SAS disk  300 GB, 450 GB, 600 GB 10,000 rpm SAS disk  200 GB, 300 GB, 400 GB enterprise-grade multilevel cell (E-MLC) SSD  1 TB 7,200 rpm nearline SAS disk IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 3
  • 3.5-inch drive support 2 TB, 3 TB 7,200 rpm nearline SAS diskDrive types can be intermixed between enclosures. The maximum number of internal drivessupported by the Storwize V7000 system is 240. Figure 3 shows a Storwize V7000 system withmixed enclosure and drive types.Figure 3: Storwize V7000 system with 10 enclosuresIn addition to managing internal storage, one major feature of the Storwize V7000 system is the abilityto manage storage provided by the external storage systems. The Storwize V7000 system acts as thevirtualization layer between the host and external storage system. Up to 32 PB of external storagecan be managed by a single Storwize V7000 system, and as the storage is virtualized, volumes canbe non-disruptively moved between external and internal storage capacity. Figure 4 shows arepresentation of this technology. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 4
  • Figure 4: IBM Storwize V7000 virtualizing external and internal storageStorwize V7000 Unified for SRMStorwize V7000 Unified offers a fully array of VMware integration options including an SRA for vSphereVM protection between two Storwize V7000 block sites.Testing for this paper was focused on Storwize V7000 Unified and SONAS file-based vSpheredeployment for use with vSphere replication. As vSphere snaps into vSphere at the datastore level, it canalso be used with existing Storwize V7000 block deployments or other VMware certified storage forprotection by SONAS or Storwize V7000 files. File hardware and concepts A Storwize V7000 Unified system is made up of a Storwize V7000 storage system and two Storwize V7000 file modules. The Storwize V7000 storage system provides block storage volumes to hosts and is also used by the Storwize V7000 file modules, which in turn provides file storage to hosts. Because of this architecture, the Storwize V7000 Unified provides the proven block storage capabilities of the Storwize V7000 system, including all features and functions mentioned in the “Block hardware and concepts” section, but also adds file storage capabilities. The Storwize V7000 Unified file modules are built upon the IBM System x®3650 M3 server running the IBM NAS stack developed originally for SONAS, and include the following specifications:  Processor – Single six core Intel® Xeon® X5650, 2.66 GHz, 8 MB L2 cache, 80W  Memory – 72 GB DDR3 RAM IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 5
  •  Storage – Two 500 GB 10K SAS disk drives  Network interfaces: − Four 1 GbE ports, two for host access and two for management − Two 10 GbE ports for host access  Host bus adapter (HBA) – Two 8 Gbps FC ports for disk access only The minimum footprint of a Storwize V7000 Unified system is 6U. Figure 5 shows the minimum Storwize 7000 Unified configuration consisting of the two file modules and the Storwize V7000 control enclosure. V7000 Unified asdf V7000 UnifiedFigure 5: Minimum footprint of a Storwize V7000 Unified system The Storwize V7000 Unified file modules run a common IBM network-attached storage (NAS) software stack which originates from the IBM SONAS product.IBM SONASThe IBM SONAS provides extreme scale out capability, a globally clustered NAS file system build uponIBM General Parallel File System (IBMGPFS™). The global namespace is maintained across the clusterof multiple storage pods and multiple interface nodes. All interface nodes and all storage nodes shareequally in the cluster to balance workloads dynamically and provide parallel performance to all users andstorage, while also assuring high availability (HA) and automated failover.The IBM SONAS is a scalable virtual file storage platform that grows as data grows. It meets demandingperformance requirements as new processors can be added independently or as storage capacity isadded, eliminating a choke point found in traditional scale-up systems. SONAS is designed for high-availability 24x7 environments with a clustered architecture that is inherently available and, whencombined with the global namespace, allows for much higher utilization rates than found in scale-upenvironments.The IBM SONAS storage system offers the following features:  Provides extreme scalability to accommodate capacity growth for up to 21 petabytes IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 6
  •  Manages multiple petabytes of storage and billions of files in a single file system  Provides excellent performance for a single file system  Enables ubiquitous access to files from across the globe quickly and cost effectively with IBM Active Cloud Engine  Achieves operational efficiency with automated, policy-driven tiered storage  Lowers TCO by up to 40 percent with automated lifecycle management and migration to tape  Satisfies bandwidth hungry applications with scale-out performance  Supports both random access and streaming workloads  Enables disaster recovery and business continuity with asynchronous replication  Allows file set snapshots and file cloning for increased availability  Offers ease of use and manageabilityOverview of VMware vCenter Site Recovery Manager with IBM SONASThe SONAS advanced architecture virtualizes and consolidates hundreds to thousands of spinning disksinto an enterprise-wide file system, and can scale I/O and capacity dynamically as storage nodes areadded. SONAS scales up to 21 petabytes of storage managed in a single pane of glass. SONAS storagecan be provisioned as a single datastore or hundreds as needed. No consideration needs to be given toSCSI reservation issues when choosing SONAS NFS datastore sizes resulting in larger datastores forimproved manageability. SONAS GPFS performance improves as disks are added to GPFS pools andstorage and infrastructure nodes scale out the deployment. IBM SONAS translates into reduced total costof administration, reduced capital expenditure, and enhanced operational efficiency, making it anexcellent choice for DR sties protecting multiple data centers with VMware Site Recovery Manager andvSphere Replication.Common NAS features of Storwize V7000 Unified and SONASData can be accessed using a variety of protocols, including: CIFS, NFS, FTP, HTTPS, and SCP.Internally, the NAS uses the IBM GPFS to store data.GPFS is an IBM developed file system that has been in development since 1995 and is highly scalablewhile providing the simplicity of a single flat file system. The GPFS spans multiple physical disks, alsoknown as Network Shared Disks (NSDs).Inherited in GPFS is the ability to perform policy-based snapshots of the file system. There can be amaximum of 256 snapshots per file system. Thirty-two snapshots are reserved for services such asNetwork Data Management Protocol (NDMP), which leaves 224 snapshots for customer use. Snapshotscan be named and scheduled, and policies can be defined, which control retention of snapshots. Figure 6shows a screen capture of the snapshot rules from the GUI. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 7
  • Figure 6: Examples of snapshot rules from the NAS GUIIBM NAS also includes the IBM Active Cloud Engine, which is a policy-driven engine that helps improvestorage efficiency by automatically:  Placing files when they are created on the appropriate storage.  Moving files during their life to the right tier of storage, including tapes in an IBM Tivoli Storage Manager hierarchy.  Deleting expired or unwanted files.  Identifying files for backup or replication to a DR location.IBM Active Cloud Engine is designed for high performance and can scan a large number of files veryrapidly. Figure 7 shows an example of the IBM Active Cloud Engine, migrating a file between differenttiers of storage based on time policies. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 8
  • Figure 7: Example of IBM Active Cloud Engine file migrationThe system also has the ability to asynchronous replicate one or more file systems through file-basedreplication to a secondary site. Replication is performed by the rsync tool which efficiently replicates onlythe changed portions of files to the destination, and uses Secure Shell (SSH) to provide an encryptionmechanism to replicated data.The well-received management GUI was updated to include the management of file objects, whichmeans customers use a unified management GUI to administer both block and file storage, as shown inFigure 8.Figure 8: IBM Storwize V7000 Unified user interface IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 9
  • VMware overviewVMware is one of the largest providers of virtualization and cloud solutions with solutions ranging fromapplication and desktop PC virtualization to enterprise clouds with up to 10,000 servers linked pervSphere environment.VMware vSphere ESXi 5.0VMware ESXi 5.0 is installed directly on the hardware and does not require any operating system. It is avirtualization platform used to create the virtual machines (VMs) as a set of configuration and disk filesthat together perform all the functions of a physical machine. Through ESX, you can run virtual machines,install operating systems, run applications, and configure virtual machines. Configuration includesidentifying virtual machine resources, such as storage devices.Each ESX host has a vSphere Client available for management use. If the ESX host is registered with thevCenter Server, a vSphere Client that accommodates the vCenter Server features is available. An ESXsystem has the following key components:  Virtualization layer - This layer provides the idealized hardware environment and virtualization of underlying physical resources to the virtual machines. This layer includes the virtual machine monitor (VMM), which is responsible for virtualization, and the VMkernel. The VMkernel manages most of the physical resources on the hardware, including memory, physical processors, storage, and networking controllers. The virtualization layer schedules the virtual machine operating systems and, if you are running an ESX host, the service console. The virtualization layer manages the access to physical resources by operating systems. The VMkernel must have its own drivers to provide access to the physical devices.  Hardware interface components - The virtual machine communicates with hardware, such as processors or disk by using the hardware interface components. These components include device drivers, which enable hardware-specific service delivery while hiding hardware differences from other parts of the system.  User interface - Administrators can view and manage ESX hosts and virtual machines in several ways. A VMware vSphere Client can connect directly to the ESX host. This setup is appropriate if your environment has only one host. A vSphere Client can also connect to the vCenter Server and interact with all ESX hosts that the vCenter Server manages.Figure 9 shows how the components interact. The ESX host has four virtual machines configured. Eachvirtual machine runs its own guest operating system and applications. Administrators monitor the hostand the virtual machines in the following ways:  Using a vSphere Client to connect to an ESX host directly.  Using a vSphere Client to connect to a vCenter Server. The vCenter Server can manage a number of ESX hosts. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 10
  • Figure 9: VMware components interactingVMware vCenter ServerVMware vCenter Server is a service that acts as a central administration point for ESX hosts connected toa network, their virtual machines, and connected resources. Multiple vCenter Server systems can bejoined to a Linked Mode group allowing logon to any single instance of vCenter Server to view andmanage the inventories of all linked vCenter servers. vCenter Linked Mode supports up to 10,000 livevirtual machines.With vCenter, an administrator can manage components of a virtual infrastructure: ESX servers, VMs,and extended functions such as Distributed Resource Scheduler (DRS), VMware vMotion, datastores,virtual switches, and virtual machines.vCenter requires a database to store its information. You can find a list of supported databases in the“Database” section.To connect to the vCenter service, the VMware vSphere Client is used. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 11
  • VMware vSphere ClientThe vSphere Client software can be installed on a Microsoft® Windows® host and is the primary methodof interacting with VMware vSphere. The vSphere Client acts as a console to operate virtual machinesand as an administration interface to the vCenter Server systems and ESX hosts. You can download thevSphere Client from the vCenter Server system and ESX hosts.When using SRM, a SRM plug-in for the vSphere Client is required. It can be installed with the SRMservice itself.vCenter Site Recovery ManagerVMware vCenter Site Recovery Manager is a business continuity and disaster recovery solution thathelps you plan, test, and run a scheduled migration or emergency failover of data center services fromone site to another.SRM is an extension to VMware vCenter that enables integration with vSphere host-based replication formanagement of virtual machine replication, testing disaster recovery preparedness, and migratingworkloads from one vCenter to another. SRM servers coordinate the replication operations with vCenterservers at multiple sites so that when virtual machines at a protected site become unavailable, virtualmachines at the recovery site can be started using the data replicated from the protected site. Transfer ofservices from one site to the other is controlled by a recovery plan that specifies allocation of vSphereresources and the order in which virtual machines are shut down and started up. SRM recovery plantesting dynamically mounts storage for non-persistent disk writes and starts VMs with no virtual networkconnectivity so that testing can occur without disruption of live operations or replication integrity.Figure 10 shows the Site Recovery Manager host-based architecture.Protected and recovery sitesIn a typical SRM installation, the protected site provides business-critical data center services, and therecovery site provides an alternative facility to which these services can be migrated. The protected sitecan be any site where virtual infrastructure supports a critical business need. The recovery site can belocated thousands of miles away, or the same campus. In the typical case, the recovery site is located ina facility that is unlikely to be affected by any environmental, infrastructural, or other disturbances thataffect the protected site. SRM has several requirements for the vSphere configurations at each site:  Each site must include at least one vSphere data center.  The recovery site must have hardware and network resources that can support the same virtual machines and workloads to be recovered or migrated.  The protected and recovery sites must be connected by a reliable IP network with sufficient bandwidth for the scheduled replication.  The recovery site must have access to the same public and private networks as the protected site, though not necessarily the same range of network addresses. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 12
  • Figure 10: Site Recovery Manager host-based architectureHost-based replicationvSphere Replication (VR) is conducted by vSphere Replication Management Server (VRMS) virtualmachines at both protected and recovery sites. The VRMS relies on a vSphere Replication Agent (VRA),which is dynamically deployed in virtual machines and a vSphere Replication Server (VRS), which isdeployed at the recovery site.DatabaseBoth vCenter and SRM require a database for storing information. Numerous popular versions of IBMDB2®, Microsoft SQL, and Oracle are supported. Consult the VMware product interoperability matrix (athttp://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php?) to confirm that your preferreddatabase is supported.VMware vCenter Server requires its own database to store data. SRM server stores recovery plans,inventory information, and other associated data in another database, and VRMS also requires its owndatabase.Before installing the vCenter and SRM server, vCenter and the SRM database must be configured.The SRM database at each site holds information about virtual machine configurations, protection groups,and recovery plans. SRM is unable to share the vCenter database as it uses an alternative databaseschema, though you may use the vCenter database server to create and support the SRM database andVRMS database instances.For testing purposes, SQL Server 2008 was used to host each site’s required databases. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 13
  • Installation of SRM and vSphere Replication componentsTwo full vSpehre vCenter deployments are required for starting an SRM deployment. For moreinformation refer to the following IBM and VMware documentation on setup:  IBM Storwize V7000 Unified: A feature-rich environment for VMware vSphere 5.0 ibm.com/support/techdocs/atsmastr.nsf/5cb5ed706d254a8186256c71006d2e0a/8f65843 79d62c9728525797d005efc6f/$FILE/IBM%20V7000%20Unified_vSphere5_v7.pdf  IBM SONAS and VMware vSphere 5 scale-out cloud foundation ibm.com/partnerworld/wps/servlet/ContentHandler/stg_ast_sto_wp_ibm_sonas_vmware _vsphere_cloud  vSphere Installation and Setup http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi- vcenter-server-50-installation-setup-guide.pdfDatabase preparationBefore SRM installation can begin, an SRM database must be configured at each site. The VRSdatabase must also be configured at this time. SQL 2008 on Windows 2008 with SQL authentication wasused for testing.For details, refer to the following guide :  Site Recovery Manager Administration Guide http://www.vmware.com/pdf/srm_admin_5_0.pdf Refer to page 28 for the topic, Configuring the SRM Database. Refer to page 29 for the topic, Configure the VRM Database.SRM Server installation on vCenter ServerBefore SRM installation begins, a DSN for the local SRM database is created on both the vCenterservers.The SRM installation executable is run on both the vCenter servers. A fully qualified domain name(FQDN) for both the sites is required for installation. It is important that the DNS name for each site beavailable at both the sites and that the corresponding IP reverse lookup record resolves to the FQDN.After installation, the SRM plug-in is available in vCenter and this need to be downloaded and installed inthe vCenter Client, which will be used in managing the SRM operations. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 14
  • Figure 11: vCenter Plug-In ManagerAfter downloading and installing the SRM plug-in, navigate to the vCenter Client home page and clickSite Recovery. SRM then displays the Getting started page, as shown in Figure 10. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 15
  • Figure 12: SRM Getting Started page, displaying the next steps to deploy and test SRM.Connect the sitesWith SRM installed at both the sites, click Configure Connection, and populate the resulting dialogs withFQDNs and authentication information for SRM partner site. After completing this step, log on to therecovery site vCenter and repeat the steps for creating the reverse connection.Note: It is useful to think of SRM protected and recovery sites. However, it is common for all sites to beprotected or primary and recovery or secondary in different operations. In this testing, vctr100 isconsidered as the primary (protected) site and vctr200 as the recovery site unless otherwise noted. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 16
  • Figure 13: Connecting SRM connection IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 17
  • Figure 14: FQDN for SRM remote vCenter IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 18
  • Figure 15: Authenticating remote SRM vCenter IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 19
  • Figure 16: SRM vCenter Server authentication IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 20
  • Figure 17: Connection completedAfter the connection has been completed at both the sites, inventory mappings must be set up forResource, Folder, and Network. Resource mappings Resource mappings will generally be made on a cluster to cluster level. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 21
  • Figure 18: Resource mappings Folder mappingsFigure 19: Folder mappings Folder mappings are administratively useful for keeping track of the preferred protected site and recovery site vSphere folders. It is recommended that you use folder names that clearly indicate the purpose of the VMs they contain when using SRM. The preferred protected and recovery site mappings will be dynamically populated by default in the GUI when creating jobs. It is easy to change these settings globally or on a job-by-job basis. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 22
  • Network mappingsFigure 20: Network mappings Default network mappings are similar to folder mappings and are used to define the default network in the recovery data center to use based on the vSphere network used in the source data center. These names may map perfectly by name or may have very different names depending on the way vSphere is administered in the two data centers.Configuring vSphere ReplicationAfter setting up SRM, a replication mechanism is required for SRM to be useful. In order to facilitatecross-storage replication, the test team used the vSphere host-based replication.In the left pane of the Site-Recovery module, navigate to vSphere Replication. The Getting started page(as shown in Figure 21) is displayed, identifying the steps to configure vSphere Replication. Once againthe steps must be completed at both the sites. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 23
  • Figure 21: Getting started with configuring vSphere ReplicationDeploy the VRM ServerPerform the following steps to deploy the VRM Server. 1. Click Deploy the VRM server on the Getting started page and then click Next. Then enter the appropriate data for the name, cluster, host, disk target, network, IP configuration fields that would be relevant to your environment. 2. Validate the appropriateness of data on the Ready to Complete page and click Finish. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 24
  • Figure 22: The Ready to Complete page displaying the deployment settings 3. After receiving the Deployment Completed Successfully message, click Configure the VRM Server on the Getting Started page. 4. Log in with the root credentials provided during template deployment, and click Configuration page on the Getting Started with vSphere Replication Management page. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 25
  • Figure 23: Getting started with vSphere Replication Management (VRM) 5. Populate the configuration tab with IP and authentication data for the VRMS database for the site being configured. 6. Click Save and Restart Service.The message stating that VRM service is stopped should change to started after DB attachment iscomplete. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 26
  • Figure 24: Configuration tabFigure 25: VRM service runningConfigure the VMRS connectionAfter the VRMS is deployed and configured at both the sites, connectionbetween them is established.Figure 26: VRMS connection succeeded IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 27
  • Deploy a VR serverA VR server is required at every recovery site. As protected sites become recovery sites when re-protecting workloads, it is recommended that a VR virtual machine be deployed at both the sites tosupport two-way SRM.Click Deploy a VR Server and fill in the necessary information in the resulting dialogs to deploy the VM.Registering a VR server with the VRM serverTo register a VR server with the VRM server, click Register a VR Server and then click the VR server toregister, and confirm.Figure 27: Confirming the registrationConfiguring VM ReplicationAfter the vCenter, SRM, VR, and VRM servers are properly set up at both the sites, virtual machinereplication can be configured for a virtual machine by right-clicking its display name and clickingReplicate. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 28
  • Figure 28: Configuring replication IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 29
  • Figure 29: Configuration of replication succeededProtecting workloadsAfter scheduling replication, replication progress can be verified by opening the SRM plug-in and clickingvSphere Replication in the left pane. Workloads being replicated for the first time, displays the status asInitial Full Sync along with progress indicator (in percentage) during first replication. When the replicationis completed, the status changes to Success. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 30
  • Figure 30: vSphere replication shows VMs nat1 and Veeam have replicated successfully, srm100_2k8-1and 2 are stillundergoing initial full disk synchronization.Before testing can begin for a group of VMs, they must be placed in a protection group. A protectiongroup is generally used to protect all the required VMs for a particular application or solution.By separating VMs into multiple protection groups, VM migration or failover can be done on anapplication-by-application basis, allowing an SRM administrator to start the most critical businessapplications first during a disaster scenario.Click Protection Groups in the left pane and then click Create a Protection Group in the All protectionGroups pane. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 31
  • Select vSphere Replication (VR) and then click Next.Figure 31: Selecting virtual machines for protection groupNote: A protection group can be created with synchronization pending, but VMs cannot be migrated orrecovered until the first synchronization is completed. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 32
  • Figure 32: Naming the protection group IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 33
  • Figure 33: Ready to complete the protection groupAs soon as the protection group is in place, a recovery plan can be created for testing, migration, ordisaster response.To create your recovery plan, perform the following steps. 1. Click Recovery Plans in the left pane and then click Create Recovery Plan in the All Recovery Plans pane. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 34
  • Figure 34: All Recovery Plans pane, with the Create Recovery Plane option IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 35
  • Figure 35: Selecting the recovery site 2. Select the appropriate site for recovery and click Next. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 36
  • Figure 36: Selecting the recovery groups for recovery 3. Select the recovery groups to be included in the plan and click Next. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 37
  • Figure 37: Selecting the network to use at the recovery site 4. Select the appropriate recovery network and click Next. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 38
  • Figure 38: Naming the recovery plan 5. Enter an appropriate name for the recovery plan, clearly identifying its purpose. Use the optional description field to include further description, if needed, and then click Next. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 39
  • Figure 39: Completing recovery plan creation 6. Review the recovery plan details and click Back if corrections are necessary or click Finish to complete. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 40
  • Figure 40: Configure restore customizationTesting workloadsAs soon as the recovery plan is in place and VM replication is complete, right-click the recovery plan inthe Recovery Plans pane and click Test. Then click Next and wait until you see the Test Completemessage. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 41
  • Figure 41: Test execution on a recovery planFigure 42: Recovery plan test successfulThe VMs should be running at the recovery site with non persistent writes and no network connectivity. Itmight be necessary to click Refresh to update the recovery status to Success after the message TestComplete is reported. After validating the integrity of the VMs at the recovery site, click Cleanup, thenNext, and then Start. SRM will shut down the VMs and resume protection of the VMs. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 42
  • Migrating workloadsAfter a successful test, you can confidently proceed with migrating a workload to the protected datacenter by right-clicking the recovery plan.Figure 43: Selecting the Recovery option IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 43
  • Figure 44: Recovery confirmation pageIt is necessary to select the check box in the Recovery Confirmation section clicking Next. In the event ofa disaster failover, select Disaster Recovery to fail over to the last complete replication. Retain thePlanned Migration option selected for failover to take place gracefully after completing one more datareplication. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 44
  • Figure 45: Recovery review pageReprotecting workloadsAfter workloads have been migrated, their recovery plan and protection groups must be re-createdin-reverse. As earlier, a properly configured virtual replication server is required at the former protectedsite which will become the recovery site for the operation. Create a protection group and a recovery plancontaining the virtual machines to reprotect, test the plan, and migrate as before.Scaling / Improving replication timesWhile testing for this paper, two vSphere 5.0 vCenter environments were deployed. A protected SRMenvironment was build hosting virtual machines on a Storwize V7000 Unified NFS share, and a vCenterand SRM environment for recovery was built hosting virtual machines on a SONAS NFS share. Both siteshad a single VRS to enable replication in either direction.Deploy multiple VRS appliances and multiple vCentersAssuming sufficient bandwidth exists between sites, deploying multiple virtual replication servers is theeasiest way to improve throughput. The Site Recovery Manager Administration Guide (at: IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 45
  • https://www.vmware.com/pdf/srm_admin_5_0.pdf) lists a limit of one VRMS and five VRS appliances pervCenter Server instance (refer to page 25, Table 1-8 in the guide). Use of multiple vCenter servers, eachwith multiple VRS might be required to reach the replication capacity required for protecting largeworkloads.Prepopulating virtual disksVMware recommends prepopulating the recovery site virtual disks for a VM before configuring the VMsreplication to reduce the time required to protect a VM for the first time.Popular strategies for prepopulation include:  Couriering backup media to recovery DC for restore  Mounting datastore across high bandwidth WAN, cloning VM in vCenter, and unregistering clone before configuring SRM replication  Using deduplicated backup tool across high bandwidth WAN to restore virtual disks at recovery site before first SRM configured replication  Using SONAS / Storwize V7000 Unified asynchronous replication of snapshot across high bandwidth WANFor more information about backup and asynchronous replication with IBM NAS, refer to the followingwebsites:  IBM SONAS and VMware vSphere 5 scale-out cloud foundation, pg. 28 Backup and restore of VM images stored in SONAS ibm.com/partnerworld/wps/servlet/ContentHandler/stg_ast_sto_wp_ibm_sonas_vmware_vsp here_cloud  IBM Storwize V7000 Unified: A feature-rich environment for VMware vSphere 5.0, pg. 37 VMware vSphere / View backup ibm.com/partnerworld/wps/servlet/ContentHandler/stg_ast_sto_wp_sonas_storwize_v7000_ unified_vmware_vsphere  DR solution for IBM SONAS hosted VMware virtual environment using Veeam ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102052  IBM SONAS business continuity solution with SONAS asynchronous replication and VMware vSphere 4.1 ibm.com/partnerworld/wps/servlet/ContentHandler/stg_ast_sys_wp_sonas_asynchronous_re plication_vmware_vsphere  Replicate Virtual Machine Using Physical Couriering pg 64 SRM Administrators Guide https://www.vmware.com/pdf/srm_admin_5_0.pdf IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 46
  • Best practicesAlways test your recovery plan before considering the plan to be in production.Most recovery plans intended for production use must be customized to suit specific needs. For example,a recovery plan for an emergency at the protected site is likely to be different from a planned migration ofservices from one site to another.A recovery plan can be customized to run commands, display messages that require a response, andchange the recovery priority of protected virtual machines. In the protection group, it is important to setcritical infrastructure virtual machines at high priority and make sure that they are recovered first. Also,consider inserting a message step into the recovery plan, after the step that recovers the high-priorityvirtual machines. This causes the execution of the recovery plan to be paused at this point. During a DRtest or true DR scenario, verify that the infrastructure services are available before the other servers withdependencies are recovered.Always perform a realistic test. Do not depend on any infrastructure or services that will not beavailable during a real DR scenario.Some recovery plan steps are run during all recoveries, some are run only during test recoveries, andsome are always skipped during test recoveries. Understanding these steps, their order, and the contextin which they run is important when customizing a recovery plan. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 47
  • SummaryThis paper provides and overview of the steps required to implement a disaster recovery solutionbetween IBM Storwize V7000 Unified and IBM SONAS using VMware SRM host-based replications anddemonstrates that SRM helps to manage disaster recovery preparation and workload migration inVMware vSphere clouds. The methodologies presented can be used to protect any VMware datastorewith a Storwize V7000 Unified or SONAS based SRM deployment utilizing vSphere replication. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 48
  • Appendix A: Glossary  IBM Scale Out Network Attached Storage (SONAS) - Build on IBM high-performance computing experience and based upon IBM GPFS, scale out network-attached storage (NAS) solution provides the performance, clustered scalability, high availability, and functionality that are essential to meet strategic Petabyte Age and cloud-storage requirements.  VMware vSphere – Formerly developed as VMware Virtual Infrastructure, it is VMware’s first cloud operating system that can manage large pools of virtualized computing infrastructure, including software and hardware.  VMware ESXi - VMware ESXi is bare-metal embedded hypervisor, which runs directly on server hardware without requiring an additional underlying operating system. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 49
  • Appendix B: ResourcesThe following websites provide useful references to supplement the information contained in this paper:  IBM Systems on IBM PartnerWorld® ibm.com/partnerworld/systems  IBM Redbooks® ibm.com/redbooks  IBM Publications Center www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi?CTY=US  IBM SONAS on PartnerWorld ibm.com/partnerworld/systems/sonasIBM SONAS documentation  IBM Scale Out Network Attached Storage Concepts ibm.com/redbooks/redpieces/abstracts/sg247874.html?Open  IBM SONAS Introduction and Planning Guide (GA32-0716): http://publib.boulder.ibm.com/infocenter/sonasic/sonas1ic/topic/com.ibm.sonas.doc/sonas_ipg.pdf  IBM SONAS administration and user documentation: http://publib.boulder.ibm.com/infocenter/sonasic/sonas1ic/index.jsp  IBM Scale Out Network Attached Storage Administrators Guide (GA32-0713): http://publib.boulder.ibm.com/infocenter/sonasic/sonas1ic/topic/com.ibm.sonas.doc/sonas_admin _guide.pdf  IBM SONAS Users Guide (GA32-0714): http://publib.boulder.ibm.com/infocenter/sonasic/sonas1ic/topic/com.ibm.sonas.doc/sonas_user_ guide.pdf  IBM SONAS Configuration Guide (GA32-0718): http://publib.boulder.ibm.com/infocenter/sonasic/sonas1ic/topic/com.ibm.sonas.doc/configuration _guide.pdf  IBM SONAS Troubleshooting Guide (GA32-0717): http://publib.boulder.ibm.com/infocenter/sonasic/sonas1ic/topic/com.ibm.sonas.doc/sonas_pd_gui de.pdfVMware documentation  vSphere FAQ http://www.vmware.com/products/site-recovery-manager/faqs.html  VMware vCenter Site Recovery Manager Documentation http://www.vmware.com/support/pubs/srm_pubs.html  Site Recovery Manager Administration Guide https://www.vmware.com/pdf/srm_admin_5_0.pdf IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 50
  •  vSphere PowerCLI Administration Guide http://www.vmware.com/support/developer/PowerCLI/PowerCLI41U1/doc/viwin_admg.pdf  VMware Virtual Networking Concepts http://www.vmware.com/files/pdf/virtual_networking_concepts.pdfAbout the authorBenton Gallun is a Systems Architect in ISV Enablement Group for IBM NAS. He has 15 years ofexperience working with thin client, virtualization, and storage technologies. His focus is on servervirtualization, Virtual Dekstop Infrastructure (VDI), and cloud solutions from ISVs which use the power ofscale out NAS.You can contact Benton at bgallun@us.ibm.com. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 51
  • Trademarks and special notices© Copyright IBM Corporation 2012.References in this document to IBM products or services do not imply that IBM intends to make themavailable in every country.IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. If these and other IBM trademarkedterms are marked on their first occurrence in this information with a trademark symbol (® or ™), thesesymbols indicate U.S. registered or common law trademarks owned by IBM at the time this informationwas published. Such trademarks may also be registered or common law trademarks in other countries. Acurrent list of IBM trademarks is available on the Web at "Copyright and trademark information" atwww.ibm.com/legal/copytrade.shtml.Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States,other countries, or both.UNIX is a registered trademark of The Open Group in the United States and other countries.Linux is a trademark of Linus Torvalds in the United States, other countries, or both.SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC.Other company, product, or service names may be trademarks or service marks of others.Information is provided "AS IS" without warranty of any kind.All customer examples described are presented as illustrations of how those customers have used IBMproducts and the results they may have achieved. Actual environmental costs and performancecharacteristics may vary by customer.Information concerning non-IBM products was obtained from a supplier of these products, publishedannouncement material, or other publicly available sources and does not constitute an endorsement ofsuch products by IBM. Sources for non-IBM list prices and performance numbers are taken from publiclyavailable information, including vendor announcements and vendor worldwide homepages. IBM has nottested these products and cannot confirm the accuracy of performance, capability, or any other claimsrelated to non-IBM products. Questions on the capability of non-IBM products should be addressed to thesupplier of those products.All statements regarding IBM future direction and intent are subject to change or withdrawal withoutnotice, and represent goals and objectives only. Contact your local IBM office or IBM authorized resellerfor the full text of the specific Statement of Direction.Some information addresses anticipated future capabilities. Such information is not intended as adefinitive statement of a commitment to specific levels of performance, function or delivery schedules withrespect to any future products. Such commitments are only made in IBM product announcements. The IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 52
  • information is presented here to communicate IBMs current investment and development activities as agood faith effort to help with our customers future planning.Performance is based on measurements and projections using standard IBM benchmarks in a controlledenvironment. The actual throughput or performance that any user will experience will vary dependingupon considerations such as the amount of multiprogramming in the users job stream, the I/Oconfiguration, the storage configuration, and the workload processed. Therefore, no assurance can begiven that an individual user will achieve throughput or performance improvements equivalent to theratios stated here.Photographs shown are of engineering prototypes. Changes may be incorporated in production models.Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk. IBM Storwize 7000 Unified, SONAS, and VMware Site Recovery Manager 53