HP MSA Storage Replication Adapter Software User Guide Abstract The HP MSA Storage Replication Adapter (SRA) Software for VMware® vCenter Site Recovery Manager (SRM) enables full-featured use of the VMware SRM with HP MSA 2040 and HP MSA P2000 G3 storage systems. Combining the HP MSA storage system’s Remote Snap functionality with VMware SRM, the SRA provides an automated solution for implementing and testing disaster recovery between geographically separated sites.
© Copyright 2012-2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Installing and configuring the SRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 What’s new in this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About VMware Site Recovery Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planned migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 1 Typical SRM configuration showing a protected site and recovery site .........................
Figures
Tables 1 SRA error messages and suggested actions ...............................................................17 1 Document conventions.............................................................................................
Tables
1 Installing and configuring the SRA The HP MSA Storage Replication Adapter (SRA) for VMware® SRM enables full-featured use of VMware Site Recovery Manager 5.0 or greater. Combining the HP MSA storage system’s Remote Snap functionality with VMware SRM, the SRA provides an automated solution for implementing and testing disaster recovery between geographically separated sites. It also enables you to use SRM for planned migrations between two sites. What’s new in this release • Added support for MSA 2040.
NOTE: Because the HP MSA SRA connects VMware SRM with MSA Remote Snap functionality, you might encounter different terminology that has similar meanings. For example, the VMware user interface and documentation typically refer to protected and recovery sites. The MSA SMU user interface and Remote Snap documentation refer to primary and secondary volumes and sites.
Using SMU’s Replication Setup Wizard 1. Use the Replication Setup Wizard in SMU to configure Remote Snap software, following the instructions in Chapter 6, “Using Remote Snap to replicate volumes” of the HP MSA 2040 SMU Reference Guide or HP P2000 G3 MSA System SMU Reference Guide, to perform these steps: a. Select the primary volume, which is an existing volume or snapshot to replicate. b. Specify whether the replication mode will be local or remote.
2. Run hp-msa-sra/setup.exe to install the SRA. The installation process is simple and straightforward. Once the SRA is installed at each site you can configure SRM, which enables it to discover the volumes replicated between the sites. Configuring SRM Once you have both SRM and the SRA installed, the Getting Started tab of the main SRM window guides you through the steps necessary to configure it. For detailed SRM configuration instructions, see the Site Recovery Manager Administration Guide.
2 Using SRM for disaster recovery Once MSA Remote Snap software and VMware SRM software are configured and licensed at local and remote sites and you have configured at least one replication set, use SMU to schedule replications. Then use SRM to create and test one or more recovery plans. At this point, SRM is able to provide disaster recovery, failover and failback, and reprotect operations.
makes changes at both sites that require significant time and effort to reverse. Because of this, the privilege to test a recovery plan and the privilege to run a recovery plan must be separately assigned. When SRM test failovers to the recovery site are requested, the SRA will perform the steps listed. 1. Select the replicated volumes. 2. Identify the latest complete Remote Copy snapshot. 3. Delete any temporary writable space on that snapshot to ensure an unedited snapshot is presented to ESX hosts. 4.
Reprotection After a recovery plan or planned migration is executed, there are often cases where the environment must continue to be protected against failure in order to ensure its resilience or to meet all disaster recovery objectives. With SRM 5.0 or greater, reprotection is a new extension to recovery plans for use only with array-based replication. It enables the environment at the recovery site to establish synchronized replication and protection of the original environment.
Using SRM for disaster recovery
3 Troubleshooting VMware vCenter Server uses the SRA to present a detailed error message each time a recovery step fails. The SRA also creates a log file called sra.log that shows each SRM event and each CLI command that occurs on the MSA storage systems. Examining the error messages and this log file will often provide enough information to rectify errors. Table 1 SRA error messages and suggested actions Message number Message Suggested action 1002 VMware Site Recovery Manager version 5.
Table 1 SRA error messages and suggested actions 1022 Invalid or unknown ArrayId '{ArrayId}' in {cmd} request. Ensure that the array management controller system names and IP addresses have not been reconfigured since SRM was configured. 1023 Failed to open lock file {filename}. Check file and directory permissions for the specified filename. 1024 Unknown or missing DeviceId parameter '{DeviceId}' in {command} request. Verify that SRM and the SRA are configured correctly.
Table 1 SRA error messages and suggested actions 1104 Response from array at {ipAddr} did not include status indication. Check the health of the array and restart the management controller if necessary. 1105 Failed to run command "{cmd}" on array at {system}: {err} Verify the IP address configuration on the array and on the host, and check network connectivity. 2001 Volume {volume}({name}) is already unmapped.
Troubleshooting
4 Best practice recommendations Specific recommendations for using HP MSA SRA 5.0 or later and Remote Snap software in conjunction with the VMware SRM disaster recovery solution include the following: • Prepare a plan ahead of time for how you will re-establish replication schedules in the event of a site failover.
Best practice recommendations
5 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
• • • • • HP MSA 2040 I/O Module Replacement Instructions HP MSA Power and Cooling Module Replacement Instructions HP MSA Bezel Ears Replacement Instructions HP Transceiver Replacement Instructions HP MSA Drive Module Replacement Instructions You can find these documents on the HP MSA Storage user documents page: http://www.hp.com/support/msa2040/Manuals NOTE: Similar documents can be found for HP P2000 G3 systems at: http://www.hp.com/go/p2000/manuals Websites • HP MSA 2040 home page: http://www.hp.
Table 1 Document conventions (continued) Convention Element Blue, bold, underlined text Email addresses Blue, underlined text: http://www.hp.
Support and other resources
6 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Documentation feedback
Glossary chunk size The amount of contiguous data that is written to a vdisk member before moving to the next member of the vdisk. compatible disk A disk that has enough capacity to replace a failed disk and is the same type (SAS or SATA). dedicated spare A disk that is reserved for use by a specific vdisk to replace a failed disk. See compatible disk.
primary site A primary site is a production environment that provides business-critical datacenter services. In a replication environment, the primary site can be any site where HP MSA Remote Snap replication software supports a critical business need. Another term for protected site. See also primary volume. primary volume The volume that is the source of data in a replication set and that can be mapped to hosts.
secondary volume The volume that is the destination for data in a replication set and that is not accessible to hosts. For disaster recovery purposes, if the primary volume goes offline, a secondary volume can be designated as the primary volume. The secondary volume exists in a secondary vdisk in a secondary (or remote) storage system. The contents of a secondary volume are in a constant state of flux and are not in a consistent state while a replication is in process.
Glossary
Index A array discovery 13 automated failback 15 automatic failover 14 C creating a recovery plan 13 D disaster recovery, using SRM for 13 discovering arrays and volumes 13 VMware Site Recovery Manager Administration Guide 11, 13 VMware software download site 11 VMware vCenter Site Recovery Manager Release Notes 11 volume discovery 13 volumes recognized by SRM 13 W wizard, replication setup 11 E ESX server 10 F failback 14 failback, automated 15 failover 14 failover, automatic 14 failover, testing 14
Index
