HP StorageWorks P9000 Virtualization Adapter Administrator Guide This guide contains detailed instructions for installing and removing the P9000 Virtualization Adapter. The intended audience has independent knowledge of related OS software and of HP disk arrays and software.
Legal and notice information © Copyright 2009-2010 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 Overview of the P9000 Virtualization Adapter ....................................... 7 Discovery of disk arrays and LUNs ................................................................................................ 7 Failover testing ........................................................................................................................... 8 Failover recovery ........................................................................................................................
RAID Manager command errors in rmsra.exe ............................................................................... Configuration and status errors ................................................................................................... Troubleshooting information for technical support .......................................................................... Error code for multiple errors ......................................................................................................
Figures 1 Configuration using local connection ......................................................................... 10 2 Configuration using remote connection ...................................................................... 11 3 RAID Manager configuration for the P9000 Virtualization Adapter ................................ 13 4 horcmX.conf on protection site .................................................................................. 14 5 horcmX.conf on recovery site ......................
Tables 1 Document conventions .............................................................................................
1 Overview of the P9000 Virtualization Adapter HP StorageWorks P9000 Virtualization Adapter (P9000 Virtualization Adapter) is a Perl interface between VMware Site Recovery Manager (SRM) and HP StorageWorks P9000 and XP disk arrays. The interface enables SRM to provide automatic access to remote data copies when virtual machines become unavailable locally.
• • • • • • Model: for example, 60-03-20/FF Product: P9000_RAID Storage Port ID: Port WWN Replicated LUNs and IDs: LDEV number and LUN WWN Remote Storage Array IDs: serial number Remote LUN IDs: LDEV number NOTE: Remote S-VOL is available to the groups through RAID Manager horcm.conf, and are replicated between protected and recovery P9000 or XP disk arrays using Continuous Access and Continuous Access Journal software.
Failover recovery During recovery, SRM executes a recovery plan. When SRM reaches the Prepare Storage step in the recovery plan, it provides the LUN information needed for failover to the P9000 Virtualization Adapter. The failover sequence is: • SRM makes a request to the P9000 Virtualization Adapter to do failover to replicated LUNs on a remote (recovery) array. • The P9000 Virtualization Adapter connects to an RAID Manager instance and requests replicated Continuous Access S-VOLs on the recovery array.
Figure 1 Configuration using local connection . Remote configuration using Telnet Figure 2 shows the Telnet configuration for the P9000 Virtualization Adapter on a Windows machine. The Virtual Center server (VIC), SRM, and P9000 Virtualization Adapter are configured on Windows 2003. RAID Manager is on a remote host (for example, Linux, Solaris, or HP-UX). The P9000 Virtualization Adapter is configured using the command.pl Perl script file (see command.
Figure 2 Configuration using remote connection .
command.pl example #!/usr/bin/perl use Net::Telnet; my @stdinput = ; my $input; my $output; my $out; my $host; my $user; my $pass; my $local = 1; my $cmd; : : : my $telnet = Net::Telnet->new(Host=>$host,Cmd_remove_mode=>1,Timeout=>180); $telnet->login($user,$pass); if ($ENV{'HORCMROOT'} ne "") { $cmd = "echo \"" . $input . "\" | " . $ENV{'HORCMROOT'} . "\\HORCM\\etc\\rmsra -auto timeout=" . $ENV{RMSRATOV} . " testMU=" . $ENV{'RMSRATMU'} . " -XMLSTDOUT"; } else { $cmd = "rm -f " .
RAID Manager and array configurations HORCM instances To use the P9000 Virtualization Adapter, HORCM instances X are needed on both sites (primary and secondary), but remote communications are not needed between the instances. However, if Continuous Access paired volumes are created using RAID Manager, remote communications are needed. For failover testing, HORCM instance X+1 is needed. If HORCM X is not running, the P9000 Virtualization Adapter uses the auto option (-auto) to start it.
RAID Manager configuration files The examples shown in Figure 4 on page 14 and Figure 5 on page 15 assume the following instance number and the target port: • X is the RAID Manager instance number • 0 is the LUN number for failover testing • CL4-G-1 is the target port for ESX Server Figure 4 horcmX.conf on protection site .
Figure 5 horcmX.conf on recovery site . NOTE: 1 - MU# must NOT be specified for registering as Continuous Access group. 2 - MU# must be specified for registering Business Copy group. HP recommends that you specify either MU#0,1.2 for Business Copy or Snapshot. Business Copy can be specified either MU#0,1.2. Snapshot can be specified either MU#0,1.2…63. If MU# (except MU#0) is specified, it is needed to set the P9000 Virtualization Adapter variable. (see “Environment variables” on page 22).
Figure 6 horcmX+1.conf on recovery site . The examples shown in Figure 7 on page 16 and Figure 8 on page 17 assume the following instance number and the target port: • X is the RAID Manager instance number • Business Copy or Snapshot is not used for failover testing • CL4-G-1 is the target port for ESX Server Figure 7 horcmX.conf on primary site .
Figure 8 horcmX.conf on secondary site . NOTE: For failover testing on Continuous Access and Continuous Access Journal S-VOL: • If the Business Copy licence is not installed, SRM requires that SplitReplication is set to true. • If the Business Copy licence is installed, SRM requires that SplitReplication is set to true and the MU number except 0 is specified as $RMSRATMU variable. • Establish communication between the HORCM of the primary site and the HORCM of the recovery site.
Protection groups using Continuous Access Synchronous or Continuous Access Synchronous CTG If the disk pairs for a protection group are Continuous Access Synchronous, use a fence level of DATA. If the fence level of NEVER is used, the internal horctakeover command fails (horctakeover returns EX_VOLCUR). A fence level of NEVER cannot guarantee data consistency among all disks in a device group when a single disk fails (because I/O is not fenced).
Starting HORCM as a service in Windows RAID Manager provides the svcexe.exe command and a sample script file (HORCM0_run.txt), so RAID Manager (HORCM) can be started automatically from the services. See the HP StorageWorks P9000 RAID Manager User Guide. Starting HORCM as a service in Windows 2000/2003 RAID Manager commands and the HORCMgr process normally have the same privileges. However, if the HORCM has Local System privileges, any RAID Manager commands are unable to attach to the HORCMgr process.
Overview of the P9000 Virtualization Adapter
2 rmsra command and environmental variables rmsra command Configures the P9000 Virtualization Adapter parameters Description Use the rmsra command to modify the P9000 Virtualization Adapter parameters. Syntax rmsra {–h | –XMLSTDOUT | –XMLSTDERR [sralog=path_name] | –auto | —loglvl= [quiet] [error] [warning] [info] [verbose] [trivia] | —timeout=value | —testMU=value} Arguments –h Displays command usage.
• verbose • trivia —timeout=value This option is used to specify the timeout value for failover using for Continuous Access Journal. If the timeout value is specified using the $RMSRATOV variable, then this variable is ignored. The default is 60 seconds. —testMU=value This option is used to specify MU number of the Business Copy or Snapshot volume for failover tests. If the MU number value is specified using the $RMSRATMU variable, this variable is ignored. The default MU is 0.
$RMSRATMU This environment variable specifies the MU number of a Business Copy or Snapshot volume for failover testing. If the MU number value is specified through the P9000 Virtualization Adapter command option [testMU=value], this variable is ignored. The default is MU number 0. The following examples specify 1 as the MU number. Windows example: setx RMSRATMU 1 /m UNIX example (bash): export RMSRATMU=1 NOTE: You must restart the Windows server to complete any changes.
5. If RAID Manager is installed to another drive, such as the E drive, use the HORCMROOT variable: setx HORCMROOT E: /m The default timeout value for failover using Continuous Access Journal or XP Continuous Access Asynchronous is 60 seconds. To can change the timeout value, use the RMSRATOV variable: setx RMSRATOV 120 /m If RAID Manager is installed on the SRM host, no more changes are required.
Figure 10 Environment variables .
rmsra command and environmental variables
3 Installing and removing the P9000 Virtualization Adapter This chapter explains how to install, configure, and remove the P9000 Virtualization Adapter. IMPORTANT: A successful installation depends on using compatible versions of the OS and all installed software. See P9000 Virtualization Adapter Release Notes for version requirements.
3. Restart the SRM service using the vmware-dr command: C:\>net STOP vmware-dr The VMware Site Recovery Manager Service service is stopping. The VMware Site Recovery Manager Service service was stopped successfully. C:\>net START vmware-dr The VMware Site Recovery Manager Service service is starting. The VMware Site Recovery Manager Service service was started successfully. 4. Set any environment variables. See “Environment variables” on page 22.
To upgrade the product: 1. Confirm that SRM is enabled and that the EventLog, vpxd and vmware-dr startup types are set to automatic. 2. Download rmxpsra.exe from the HP web page (http://www.hp.com/go/storage/vmware) and save it in a temporary folder. 3. Browse to the temporary folder and run rmxpsra.exe. 4. Restart the SRM service using the vmware-dr command: C:\>net STOP vmware-dr The VMware Site Recovery Manager Service service is stopping.
Installing and removing the P9000 Virtualization Adapter
4 Configuring SRM and the disk array This chapter summarizes the steps to set up SRM and the disk array for use with the P9000 Virtualization Adapter. The following procedures assume that the LUNs for ESX Server are already assigned on the protected and recovery sites, and the assigned LUNs for ESX Server are known as Ports, Port WWN, LUN number. For detailed information on these steps, see the documents listed in “Related documentation” on page 49. To configure the P9000 Virtualization Adapter with SRM: 1.
Configuring SRM to communicate with the P9000 Virtualization Adapter To configure SRM to communicate with the P9000 Virtualization Adapter: 1. Configure Array Manager. When the protected and recovery SRM servers have been paired, click Configure to configure Array Manager to use the P9000 Virtualization Adapter. 2. Add the P9000 Virtualization Adapter to SRM on the protected site. From the Configure Array Managers window, click Add to add connection information for the P9000 Virtualization Adapter.
• Connecting to RAID Manager on remote UNIX Host: HORCMINST=X@Host-name This connects to HORCMINST=X on the Remote UNIX Host without %HORCMROOT%. $HORCMINST@Host-name This connects to $HORCMINST setting on a remote login environment on a UNIX Host without %HORCMROOT%. • Connect to RAID Manager on remote windows Host: HORCMINST=X@Host-name This connects to HORCMINST=X on the Remote Windows Host by specifying %HORCMROOT%.
• Connecting to RAID Manager on the Windows host: HORCMINST=X This connects to HORCMINST=X on Windows host. $HORCMINST This connects to %HORCMINST% setting on this Windows host. Enter the username and password as dummy. After you enter the username and password, click Connect and then click OK to discover PVOL LUNs on the protected array. Verify that the array managers are discovered the following information.
3. Add the P9000 Virtualization Adapter to SRM on the recovery array. From the Configure Array Managers window, click Add to add connection information for the P9000 Virtualization Adapter. • Configuration using a remote connection: • Select the P9000 Virtualization Adapter from Manager Type that is connected to the P9000 Virtualization Adapter. • Enter the Alias to connect to an RAID Manager instance via the P9000 Virtualization Adapter.
• Connecting to RAID Manager on remote UNIX Host: HORCMINST=X@Host-name This connects to HORCMINST=X on the Remote UNIX Host without %HORCMROOT%. $HORCMINST@Host-name This connects to $HORCMINST setting on a remote login environment on a UNIX Host without %HORCMROOT%. • Connecting to RAID Manager on remote windows Host: HORCMINST=X@Host-name This connects to HORCMINST=X on the Remote Windows Host by specifying %HORCMROOT%.
• Connecting to RAID Manager on Windows: HORCMINST=X This connects to HORCMINST=X on this Windows Host. $HORCMINST This connects to %HORCMINST% setting to this Windows Host. Enter the username and password as dummy. After entering the username and password, click Connect and then OK to discover P-VOL LUNs on the protected array. Verify that the protection array managers are discovered the remote Array ID as following information.
4. Verify Replicated Datastore. Verify the array managers are configured for both protected and recovery sites, and replicated datastores in the Review Replicated Datastores window. 5. End Array Manager. Verify that SRM is configured in Array Manager for both protected and recovery sites.
Create protection groups You are ready to create protection groups in the protected site using SRM. Protection groups (containing virtual machines) fail over together to the recovery site during test and recovery. For more information on creating protection groups, see the VMware Site Recovery Manager Administration Guide. Create recovery plans Create recovery plans on the recovery site.
Configuring SRM and the disk array
5 Failover and failback with SRM This chapter discusses failover and failback with SRM. It also provides a scenario as a guide for the manual failback process. Failover Failover occurs when an SRM recovery plan is executed, and the SRM recovery plan is configured to fail over SRM protection groups that use replicated P-VOLs and S-VOLs on a disk array as a datastore. During normal operation, the replication path is from a protected site (local site) to a recovery site (remote site).
5. 6. 7. 8. 9. Configure array replication from the recovery site (Site B) to the protected site (Site A) for datastores containing recovered virtual machines. Create any protection groups (P2) at the recovery site (Site B) to protect the recovered virtual machines at the protected site (Site A). On the protected machine (Site A), create a recovery plan (R2) for the protection groups (P2).
6 Troubleshooting General troubleshooting Use the following solutions to troubleshoot general issues: • Disk arrays do not appear in Site Recovery Manager. Solutions: • If the disk arrays are not appearing in Site Recovery Manager, make sure that Site Recovery Manager has been restarted (see step 3 in “Installation procedures” on page 27). • Make sure that the array manager that SRM is connected to is actively managing arrays. • The P9000 Virtualization Adapter does not install.
Cause–A parameter in XML was entered from SRM to the P9000 Virtualization Adapter, but it could not be found in any parameters. Action to be taken–Confirm that SRM has passed appropriate parameters in XML from its own SRM log message. • [P9000 Virtualization Adapter] [Time]: [command_discoverLuns] : NO arrayId in XML. Cause–A parameter in XML (discoverLuns) was entered from SRM to the P9000 Virtualization Adapter, but it could not find the Array ID.
• [P9000 Virtualization Adapter] [Time]: [ ] : malloc : “system error message” Cause–Could not retain the memory for executing the P9000 Virtualization Adapter. Action to be taken–Increase the capacity of virtual memory of the whole system or terminate unnecessary programs or Daemon processes running simultaneously. • [P9000 Virtualization Adapter] [Time]: [ ] : “Command line” failed with RC=XXX. Cause–The RAID Manager command Command line has failed with RC=XXX.
Action to be taken–Confirm that volume status is appropriate status (Continuous Access is S-VOL and PAIR) using the pairdisplay command. • [P9000 Virtualization Adapter] [Time]: [failover_chk] : The output of “Command line” is missing. Cause–Could not find the correct format in the output of Command line command via failover. Action to be taken–Confirm that RAID Manager is a version supported by the P9000 Virtualization Adapter.
%HORCMROOT%\HORCM\etc\raidscan −IH −p port(i.e. cl1-a-0) −CLI (port where connecting to ESX server) If Business Copy is installed: %HORCMROOT%\HORCM\etc\pairdisplay −g ??? −CLI −l −few −m cas (where ??? is a group name shown by “raidqry −g”) • For SRM and the P9000 Virtualization Adapter remote configuration: On Windows where SRM is performing and on UNIX where RAID Manager is performing: 1. Collect the SRM log file on Windows on both the protection and recovery sites.
Error Code Reason 0x00002000 The volume has NO CTgroup. 0x00004000 Undefined. 0x00008000 Undefined. 0x00010000 The pairdisplay command has NO PWWN. 0x00020000 The pairdisplay command has NO LUN WWN. 0x00040000 The pairdisplay command has NO support for the P9000 Virtualization Adapter 0x00080000 Undefined. 0x00100000 Memory allocation error. 0x00200000 Popen() function of the system was returned with ERROR. 0x00400000 System() function of the system was returned with ERROR.
7 Support and other resources Related documentation The following documents provide related information: • • • • • • HP HP HP HP HP HP StorageWorks StorageWorks StorageWorks StorageWorks StorageWorks StorageWorks P9000 P9000 P9000 P9000 P9000 P9000 Virtualization Adapter Release Notes RAID Manager User Guide Business Copy User Guide Continuous Access Synchronous User Guide Continuous Access Journal User Guide Snapshot User Guide • • • • HP HP HP HP StorageWorks StorageWorks StorageWorks StorageWorks
After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. HP websites For additional information, see the following HP websites: • • • • • http://www.hp.com http://www.hp.com/go/storage http://www.hp.com/service_locator http://www.hp.com/support/manuals http://www.hp.com/support/downloads Documentation feedback HP welcomes your feedback.
WARNING! Indicates that failure to follow directions could result in bodily harm or death. CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: Provides clarifying information or specific instructions. NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts.
Support and other resources
Glossary This glossary defines acronyms and terms used in this guide or related to this product and is not a comprehensive glossary of computer terms. disk array Two or more hard drives combined as a single logical unit for increased capacity, speed, and fault-tolerant operation. Disk arrays are logically grouped into a storage pool. Disk Group A named group of disks selected from all the available disks in a disk array. One or more virtual disks can be created from a disk group.
P-VOL Primary volume. point-in-time copy A generic term meaning a static point-in-time copy of a volume, typically used for backup. RAID Redundant array of independent disks. A RAID level is one of the ways that disk drives are grouped together to improve performance, data availability, or reliability, or both. RAID levels are defined from RAID0 to RAID6. HP StorageWorks Disk Arrays support RAID1, RAID5 and RAID6.
Index D disk arrays supported models, 7 documentation providing feedback, 50 related, 49 documentation, HP website, 49 E error messages, 43 F Failback overview, 41 scenario, 41 Failover overview, 41 Failover recovery overview, 9 Failover testing overview, 8 G glossary, 53 H R RAID Manager P9000 Virtualization Adapter installation directory, 27 installation prerequisites, 27 related documentation, 49 rmsra command, 21 S Site Recovery Manager (SRM) discovery process, 7 Subscriber's Choice, HP, 49 T tec