hp3parmanagementplug-inandrecovery manager2.4 ...h20628. · hp3parmanagementplug-inandrecovery...

HP 3PAR Management Plug-in and RecoveryManager 2.4.0 Software for VMwarevSphereUser Guide

AbstractThis guide is intended for VMware and database administrators responsible for backing up databases and provides informationhow to install, configure, and use HP 3PAR Management Plug-in and Recovery Manager 2.4.0 Software for VMware vSphere®.

HP Part Number: QL226-96665Published: January 2014

© Copyright 2014 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shallnot be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries

in the United States and other countries.

Microsoft®, Windows®, Windows® XP, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java and Oracle are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

AIX is a registered trademark of the IBM Corporation

Cygwin is a trademark of Red Hat, Inc.

HP-UX is a registered trademark of the Hewlett-Packard Company.

Linux is a registered trademark of Linus Torvalds.

Microsoft Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation.

NEMA is a registered trademark of National Electrical Manufacturers Association.

Panasonic is a registered trademark of Matsushita Electric Industrial Co., Inc.

SecureCRT is a registered trademark of VanDyke Software, Inc.

Sun, Solaris, and Java are trademarks of Sun Microsystems, Inc.

UL is a registered trademark of Underwriters Laboratories Inc.

UNIX is a registered trademark of The Open Group.

WinZip is a registered trademark of WinZip Computing, Inc.

All other trademarks and registered trademarks are owned by their respective owners.

Federal Communications Commission Radio Frequency Interference Statement

WARNING: Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user’s authorityto operate the equipment.

This device complies with Part 15 of FCC Rules. Operation is subjected to the following two conditions (1) this device may not cause harmfulinterference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules. These limitsare designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. Thisequipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, maycause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in whichcase the user will be required to correct the interference at his own expense.

Canadian Compliance Statement

This ClassA digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.

Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matérial brouilleur du Canada.

Contents1 Overview..................................................................................................6

HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere.......................6HP 3PAR Management Plug-in for VMware vCenter.......................................................................6

Virtual Volume Details..........................................................................................................6LUN Provisioning for Recovery Manager for VMware................................................................7

HP 3PAR Recovery Manager Software for VMware vSphere...........................................................7TpdVmWebService..............................................................................................................8RMWebAccess Library.........................................................................................................8RMVMware Admin Tool........................................................................................................8RMVMwareCLI....................................................................................................................8

RMVMware Create Command..........................................................................................8RMVMware InServRegister Command..............................................................................11RMVMware VCenterRegister Command...........................................................................12RMVMware Createrc Command.....................................................................................13

User Authentication.................................................................................................................14VMware vCenter Server Login for HP 3PAR Virtual Volume and Virtual Copy Management..........15HP 3PAR StoreServ Storage System Login..............................................................................15Network Ports used by HP 3PAR Management Plug-in and Recovery Manager Software for VMwarevSphere............................................................................................................................15

HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere Interface........16HP 3PAR Views in the vSphere Client........................................................................................16

Datastore View..................................................................................................................17Virtual Machine View.........................................................................................................18ESX Host View...................................................................................................................19Cluster View......................................................................................................................20Datacenter View................................................................................................................21

About Virtual Copy Management.............................................................................................22Virtual Copy Data Consistency............................................................................................22Virtual Copy Policy.............................................................................................................22Datastore Virtual Copies.....................................................................................................23Virtual Machine Virtual Copies............................................................................................23Remote Virtual Copies........................................................................................................24The Virtual Copy Browser....................................................................................................24VMFS Snapshots................................................................................................................25Scheduling Tool.................................................................................................................26

Host Explorer.........................................................................................................................26VASA Support........................................................................................................................26

2 Installing, Registering, and Uninstalling HP 3PAR Management Plug-in andRecovery Manager Software for VMware vSphere...........................................27

Supported Platforms................................................................................................................27Preinstallation Requirements and Dependencies..........................................................................27

Allowing Port Selections with Windows 2008 Installation........................................................28Installing HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere........29

Support for VMware vCenter Server Linked Mode..................................................................31Viewing and Installing HP 3PAR Management Plug-in Certificate...................................................32Registering an SMS Certificate for the VASA Provider..................................................................32

Extracting the SMS Certificate.............................................................................................33Extracting the SMS Certificate.........................................................................................33

Installing the SMS Certificate...............................................................................................33To Install the SMS Certificate Through the VASA Web Service.............................................33

Contents 3

Installing the SMS Certificate on Windows 2008..............................................................34Installing SMS certificate on Windows 2012..........................................................................34

Uninstalling HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere....35Upgrading from a Previous Version...........................................................................................35

Using Secure Service Connections........................................................................................35Refreshing Plug-in Details....................................................................................................35

3 Using the Admin Tool to Modify Configuration Settings.................................36Overview..............................................................................................................................36The RMVMware Admin Tool.....................................................................................................36vCenter Plug-in Tab.................................................................................................................36

vCenter Plug-in Configuration..............................................................................................37Plug-in Registration.............................................................................................................40vCenter Status...................................................................................................................41Remote Copy Pairs.............................................................................................................41

Host Explorer Tab...................................................................................................................43Host Explorer Configuration................................................................................................43Storage System Mapping....................................................................................................44vCenter Mapping..............................................................................................................45

The VASA Tab........................................................................................................................47VASA Configuration...........................................................................................................47Storage System Mapping....................................................................................................50

Storage System Credential Tab.................................................................................................514 Logging On and Working with Virtual Volumes............................................53

Logging On to the vSphere Client.............................................................................................53Viewing Virtual Volume Mapping.............................................................................................56

Viewing Volume Information................................................................................................57The Upper Pane............................................................................................................58The Lower Pane.............................................................................................................60

Refreshing Virtual Volume Information........................................................................................60Creating Virtual Volumes and Datastores...................................................................................61

Creating a Virtual Volume from an Existing HP 3PAR System Template......................................61Creating a Virtual Volume from Existing Datastores.................................................................65

Adding an ESX(i) Host to the vCenter Server..............................................................................675 Working with Virtual Copies......................................................................68

Viewing Virtual Copy Information.............................................................................................68Viewing Virtual Disk Details for Virtual Copies.......................................................................69Viewing Virtual Copy Event Logs..........................................................................................70

Creating New Virtual Copies...................................................................................................70Mounting Virtual Copies..........................................................................................................71Unmounting Virtual Copies......................................................................................................72Restoring Datastores by Promoting a Virtual Copy.......................................................................72Deleting Virtual Copies............................................................................................................74Modifying Virtual Copy Policies................................................................................................74Scheduling Virtual Copies........................................................................................................75Restoring Virtual Disks and Guest OS Files and Directories...........................................................80

Restoring a Virtual Disk.......................................................................................................80Restoring a Guest OS File or Directory from a Virtual Copy.....................................................81

6 Working with Host Explorer.......................................................................837 Working with VASA Provider......................................................................848 Working with Remote Copy.......................................................................87

Registering Remote Copy Pairs.................................................................................................87Updating Registered Remote Copy Pairs Information....................................................................90

4 Contents

Viewing Host Information Summary...........................................................................................90Viewing Existing and Newly Added Remote Copy Information......................................................91Creating Remote Virtual Copies................................................................................................93Setting Policy for Remote Virtual Copies.....................................................................................94Scheduling Remote Copy Virtual Copies....................................................................................95Mounting Remote Virtual Copies...............................................................................................98

Mount From Virtual Copy Table...........................................................................................98Mount From Virtual Volume Mapping Table...........................................................................99

Unmounting Remote Virtual Copies.........................................................................................100Unmount From Virtual Copy Table......................................................................................100Unmount From Virtual Volume Mapping Table.....................................................................100

Deleting Remote Virtual Copies..............................................................................................101Deleting Local Virtual Copies.................................................................................................101Importing a Virtual Machine and Reverting to a Specific Point-in-Time Virtual Copy........................102

9 Using HP 3PAR Peer Motion Manager Software with Recovery Manager.......10310 Support and Other Resources.................................................................104

Contacting HP......................................................................................................................104HP 3PAR documentation........................................................................................................104Typographic conventions.......................................................................................................107HP 3PAR branding information...............................................................................................107

11 Documentation feedback........................................................................108A Troubleshooting for VASA........................................................................109

VASA Provider Registration Related Issue..................................................................................109Inspecting VASA Provider and vCenter Server Communication....................................................109

Alarm Type Message........................................................................................................109Event Type Message.........................................................................................................118

B Troubleshooting for HP 3PAR Management Plug-in......................................124Resolving HP 3PAR Multi-tab Issue...........................................................................................124

Index.......................................................................................................125

Contents 5

1 OverviewHP 3PAR Management Plug-in and Recovery Manager Software forVMware vSphere

VMware vSphere Management Suite has two components, VMware vCenter Server and VirtualInfrastructure Client (vSphere Client). vCenter Server is a web service installed on a Windowsserver. VI Client is a Windows desktop application, and is typically downloaded from the vCenterServer.HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere is a suite ofservices designed to work with the vCenter Server. The plug-in contains a web application anddeploys as a VI Client plug-in (a VI Client plug-in is an external Web application configured withthe vCenter Server for vSphere Clients to display their pages). The application also provides aHost Explorer service to communicate and send ESX host configuration details to the HP 3PARStoreServ Storage systems. The plug-in also contains a software component that acts as a vSphereStorage API for Storage Awareness (VASA) provider in the vSphere environment. HP 3PARManagement Plug-in and Recovery Manager Software for VMware vSphere provides its own webservers.HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere includes thefollowing major components:

• HP 3PAR Management Plug-in for VMware vCenter - Displays virtual volume mapping for easyidentification of HP 3PAR volumes used by Virtual Machines and Datastores. Also allows userto provision LUNs to be used as Datastore or raw device.

• HP 3PAR Recovery Manager for VMware vSphere - Provides Virtual Copy management of HP3PAR Virtual Copies and recovery of Virtual Machines and Datastores.

• HP 3PAR Host Explorer for VMware vSphere - Discovers VMware ESX host configurations.

• HP 3PAR VASA Provider for VMware vSphere - Enables the vCenter Server to connect toobtain information about available storage topologies, capabilities, and state.

HP 3PAR Management Plug-in for VMware vCenterHP 3PAR Management Plug-in for VMware vCenter is a free vSphere Client plug-in. The plug-inenables easy identification of HP 3PAR virtual volumes used by Virtual Machines and Datastoresand displays commonly used volume properties and attributes. The plug-in also supports LUNProvisioning that enables the creation of a virtual volume and/or Datastore based on an existingconfiguration or template.

Virtual Volume DetailsHP 3PAR Management Plug-in for VMware vCenter displays virtual volume information for eachvolume used by a Virtual Machine (VM) or Datastore and Transparent Failover configuration detailsvia the HP 3PAR tab in the vSphere Client. The Transparent Failover configuration status onlydisplays when it is enabled via HP 3PAR Operating System Software.

6 Overview

Figure 1 Viewing Datastore Virtual Volumes

See “Logging On and Working with Virtual Volumes” (page 53) for additional information aboutviewing virtual volume details.

LUN Provisioning for Recovery Manager for VMwareThis feature enables you to create virtual volumes based upon a storage system template or anexisting Datastore and export the virtual volumes to the vCenter managed ESX(i) hosts.For more details about creating and managing virtual volumes and Datastores, see “Creating aVirtual Volume from an Existing HP 3PAR System Template” (page 61)

NOTE: Only TPVV and CPVV provisioning are supported for this release.

NOTE: LUN provisioning does not require an RMV license.

HP 3PAR Recovery Manager Software for VMware vSphereHP 3PAR Recovery Manager Software for VMware vSphere allows you to manage Virtual Copiesof VMs and Datastores. It is comprised of the following four components:

• TpdVmWebService

• RMWebAccess Library

• RMVMware Admin Tool

• RMVMwareCLISee “About Virtual Copy Management” (page 22) for additional information.

HP 3PAR Recovery Manager Software for VMware vSphere 7

TpdVmWebServiceTpdVmWebService is a RESTful Web service, which is deployed as a Windows Service. The majorfunctions of Recovery Manager for VMware vSphere are implemented with this module. Thesefunctions are:

• Provides a custom Web server to deliver plug-in application Web pages. The vCenter Serversare configured with the address of this Web server during plug-in registration.

• Maps Virtual Machines and Datastores to underlying HP 3PAR virtual volumes.

• Creates, browses, deletes, and mounts Virtual Copy based Virtual Copies of Virtual Machinesand Datastores.

RMWebAccess Library

NOTE: RMWebAccess Library is deployed as a Windows component dll file and is installedas part of Recovery Manager for VMware vSphere.

Similar to the HP 3PAR Command Line Interface (CLI) and HP 3PAR Management Console (IMC),the RMWebAccess Library is used for interacting with the HP 3PAR StoreServ Storage Systemarray. The RMWebAccess Library does not use HP 3PAR OS CLI but instead interacts with theInServ Tpd TCL Service directly using secure network connections.

RMVMware Admin ToolThe RMVMware Admin Tool provides a Graphical User Interface (GUI) for administering RecoveryManager for VMware vSphere registration with the vCenter server. This tool also includes HostExplorer for VMware configuration, HP 3PAR StoreServ Storage System credential management,HP 3PAR VASA Provider configuration and Remote Copy paring configuration.

RMVMwareCLIThe RMVMware CLI module is the command line interface for Recovery Manager for VMwarevSphere.

NOTE: The recommended method for creating Virtual Copies is through the Graphical UserInterface (see “Working with Virtual Copies” (page 68) for complete details).

Four commands are provided through the CLI:

• RMVMware Create

• RMVMware InServRegister

• RMVMware VCenterRegister

• RMVMware Createrc

RMVMware Create CommandThe RMVMware create command creates a Virtual Copy on a Datastore or a Virtual Machine.The syntax for the RMVMware create command is as follows:

RMVMware Create<[-ds "Datastore" [-consistency <yes/no> [-vmlist "VirtualMachine1, VirtualMachine2, ..."]]]|[-vm "VirtualMachine" [-consistency <yes/no>]]>

[-setname "VirtualCopySetName"]

<[-vcserver "vCenterServerName" [-vcuid

8 Overview

"vCenterServerUserID"] [-vcpwd "vCenterServerPassword"] | [-vcfile"VMwareCredentialStoreFileLocation"] ]>

<[-inserv "InServName"] [-inservuid "InServUserID"]>

[-inservpwd "InServPassword"]

[-expiry "VirtualCopyExpiryInHour"]

[-retention "VirtualCopyRetentionInHour"]

The options and arguments used for this command are described as follows:

• -ds <Datastore>|-vm <VirtualMachine>

Creates a Virtual Copy on the specified <Datastore> or <VirtualMachine>. By default,a VM consistent Virtual Copy is created. The VM name must be unique within vCenter Server.The vCenter Server can manage multiple ESX hosts. The VM name should be unique acrossESX hosts.The UUID of the Datastore or Virtual Machine may also be used to create a Virtual Copy withuuid-<myUUIDofDatastore> or uuid-<myUUIDofVirtualMachine> in place of theDatastore or Virtual Machine name.

• -consistency <yes/no>

(Optional) Specifies whether or not (yes/no) the Virtual Copy is to maintain Virtual Machineapplication consistency with supported data formats. If this option is not set, the default policyis applied.

• -setname <VirtualCopySetName>

(Optional) Specifies that in addition to the Virtual Copy time stamp, the Virtual Copy set namecan be used to personalize the identity of the Virtual Copy set. By default, the name is set toreflect the current time.

• -vcserver <vCenterServerName>

The VMware vCenter Server name or IP address. This option is required.

• -vcuid <vCenterServerUserID>

The VMware vCenter server login user name. This option is required.

• -vcpwd <vCenterServerPassword>

The VMware vCenter Server login password. This option is required unless -vcfile is usedto specify the credential store file.

• -vcfile <VMwareCredentialStoreFileLocation>

The VMware credential stores file location. The –vcfile option is optional when –vcpwd isspecified. For example, C:\Users\[User Name]\AppData\Roaming\VMware\credstore\vicredentials.xml.

NOTE: For VMware credential store file creation, refer to the vCenterRegister option.

NOTE: To run the RMVMware CLI command with the vCenter Credential Store File, youmust be added as a user to have permission to access the credential file.

• -inserv <InServName>

The name or IP address of the HP 3PAR storage system on which the VM or Datastore resides.This option is required.


• -inservuid <InServUserID>

The HP 3PAR StoreServ Storage system user login name.

• -inservpwd <InServPassword>

The HP 3PAR StoreServ Storage system login password. This option is not required if theStorage System name, user ID, and password have been registered.

NOTE: This option will not be supported in a future release.

• -vmlist

Optional to provide Virtual Machine names for application consistency snapshot. If not set,all Virtual Machines under the Datastore is applied. This option can only be applied if-consistency yes is specified.

• -expiry <VirtualCopyExpiryInHour>

(Optional) Sets the amount of time (in hours) before a Virtual Copy is deleted from the systemregardless of the maximum count. If an expiration time period is not specified with this option,the Virtual Copy is deleted after it reaches the oldest position in the queue beyond the maximumcount specified through the policy settings. See “Working with Virtual Copies” (page 68) formore details. If this option is not set, the default policy is applied.

• -retention <VirtualCopyRetentionInHour>

(Optional) Sets the amount of time (in hours) that Virtual Copies are retained, during whichperiod the Virtual Copy cannot be altered. The Virtual Copy is not deleted after the retentionperiod but is then available for modification and deletion. See “Working with Virtual Copies”(page 68) for more details. If this option is not set, the default policy is applied.

Examples:The following command will create an HP 3PAR Virtual Copy for the Datastore "My Datastore":

C:\> RMVMware create -ds "My Datastore" -vcserver vc365 -vcuid admin-vcpwd pass2word -inserv s124 -inservuid rmvuser -inservpwd pass3word

As an alternative to entering in all the command line options when creating a Virtual Copy of aVirtual Machine or a Datastore, you can reference the server password or credentials from a givenfile using the following command:

C:\ RMVMware create -ds "My Datastore" -vcserver vc365 -vcuid admin-vcfile C:\vicredentials.xml -inserv s124 -inservuid rmvuser

NOTE: If duplicate Datastore or Virtual Machine names exist under the same vCenter server, usethe following uuid-<myUUIDofDatastore> or uuid-<myUUIDofVirtualMachine>commands in place of Datastore or virtual name such asuuid-4220f0f6-3aec-258b-dc41-949f596c6ba8.

10 Overview

RMVMware InServRegister CommandThe RMVMware InServRegister command registers HP 3PAR StoreServ Storage systemcredentials. The syntax for the RMVMware InServRegister command is as follows:

RMVMware InServRegister<-inserv "InServName"> <-inservuid "InServUserID"> <-inservpwd"InServPassword">

RMVMware InServRegister<-remove> <-inserv "InServName"> <-inservuid "InServUserID">

RMVMware InServRegister <-display>

NOTE: User’s who do not have the administrative privileges required to access the RMVMwareAdmin Tool can use the RMVMware InServRegister command to create the appropriateregistration.


• -inserv <InServName>

Specifies the HP 3PAR StoreServ Storage system login name to the vCenter Server. This optionis required.

• -inservuid <InServUserID>

Specifies the HP 3PAR StoreServ Storage system login user name. This option is required.

• -inservpwd <InServPassword>

Specifies the HP 3PAR StoreServ Storage system login password. This option is required whenregistering an HP 3PAR StoreServ Storage system.


• -remove

Removes a registered HP 3PAR StoreServ Storage system configuration.

• -display

Displays all registered HP 3PAR StoreServ Storage system credentials.


Example:The following command will add a new entry for the HP 3PAR StoreServ Storage System s124:

C:\> RMVMware InServRegister -inserv s124 -inservuid root -inservpwd pass2word

RMVMware VCenterRegister CommandThe RMVMware VCenterRegister command manages the vCenter credentials. The syntax forthe RMVMware VCenterRegister command is as follows:

RMVMware VCenterRegister<-vcserver "VCServerName"> <-vcuid "VCUserID"> <-vcpwd "VCPassword"><-vcfile "CredentialFilePath">

RMVMware VCenterRegister <-remove> <-vcserver "VCServerName"><-vcuid "VCUserID"> <-vcfile "CredentialFilePath">

RMVMware VCenterRegister <-display> <-vcfile "CredentialFilePath">


• -vcserver <VCServerName>

Specifies the vCenter name.

• -vcuid <VCUserID>

Specifies the vCenter user name.

• -vcpwd <VCPassword>

Specifies the vCenter password.

• -vcfile <CredentialFilePath>

Specifies the path to the credential file.

• -display

Displays the content of the credential file.

• -remove

Removes the registered credential.

Example:The following command will add a new entry for user Administrator on vCenter Server MyVC:

C:\> RMVMware VCenterRegister -vcserver MyVC -vcuid Administrator-vcpwd myPassword -vcfile "c:\myCred.xml"

12 Overview

RMVMware Createrc CommandThe RMVMware createrc command creates a remote Virtual Copy.

NOTE: When using the RMVMware createrc command, you must use the identical name ofthe storage system registered in the HP 3PAR StoreServ Storage system credential database.

The syntax for the RMVMware createrc command:

RMVMware Createrc <-rcgroup "RemoteCopyGroup"> [-consistency <yes|no>] <[-vcserver "vCenterServerName" [-vcuid "vCenterServerUserID"] [-vcpwd "vCenterServerPassword"] | [-vcfile "VMwareCredentialStoreFileLocation"] ]> <-remotehost "RemoteHostName"> <[-inserv "InServName"] [-inservuid "InServUserID"]> [-inservpwd "InServPassword"] <[-remoteinserv "InServName"] [-remoteinservuid "InServUserID"]> [-remoteinservpwd "InServPassword"] [-expiry "VirtualCopyExpiryInHour"] [-retention "VirtualCopyRetentionInHour"]

DESCRIPTION: Create HP 3PAR Virtual Copies based on Remote Copy groups.

OPTIONS: -rcgroup: Remote Copy group name for which the HP 3PAR remote Virtual Copy will be created (this parameter is case sensitive) -vcserver: VMware vCenter Server name or IP address -vcuid: VMware vCenter Server log in user name -vcpwd: VMware vCenter Server user password, optional when -vcfile is specified

-vcfile: Optional VMware credential store file location -remotehost: remote host where Recovery Manager for VMware vSphere is installed to take remote snapshot on. -inserv: local HP 3PAR Storage System name -inservuid: local HP 3PAR Storage System user name, required when registered -inservpwd: local HP 3PAR Storage System password, optional if -inserv is registered -remoteinserv: remote HP 3PAR Storage System name -remoteinservuid: remote HP 3PAR Storage System user name, required when registered -remoteinservpwd: remote HP 3PAR Storage System password, optional if -remoteinserv is registered -consistency: Optional to set Virtual Machine application consistency to yes or no. -expiry: Optional to set HP 3PAR Virtual Copy expiration in hours (1-43800). -retention: Optional to set HP 3PAR Virtual Copy retention in hours (1-43800).

EXAMPLE: The following command will create HP 3PAR Virtual Copy for the Remote Copy group RMV_RCGROUP_ASYNC:

C:\> RMVMware createrc -rcgroup RMV_RCGROUP_ASYNC -vcserver caracal -vcuid administrator -vcpwd ssmssm -remotehost 10.112.61.225 -inserv s256 -inservuid root -remoteinserv s336 -remoteinservuid root -consistency yes

The following options and arguments used for this command:

• -rcgroup

Remote Copy group name for which the HP 3PAR remote Virtual Copy will be created (thisparameter is case sensitive).

• -vcserver

VMware vCenter Server name or IP address.

• -vcuid

VMware vCenter Server log in user name.


• -vcpwd

VMware vCenter Server user password, optional when -vcfile is specified.

• -vcfile

Optional VMware credential store file location.

• -remotehost

Remote host where Recovery Manager for VMware vSphere is installed to take remote snapshoton.

• -inserv

Local HP 3PAR StoreServ Storage system name.

• -inservuid

Local HP 3PAR StoreServ Storage system user name, required when registered.

• -inservpwd

Local HP 3PAR StoreServ Storage system password, optional if -inserv is registered.


• -remoteinserv

Remote HP 3PAR StoreServ Storage system name.

• -remoteinservuid

Remote HP 3PAR StoreServ Storage system user name, required when registered.

• -remoteinservpwd

Remote HP 3PAR StoreServ Storage system password, optional if -remoteinserv isregistered.


• -consistency

Optional to set Virtual Machine application consistency to yes or no.

• -expiry

Optional to set HP 3PAR Virtual Copy expiration in hours (1-43800).

• -retention

Optional to set HP 3PAR Virtual Copy retention in hours (1-43800).

User AuthenticationAs stated earlier, HP 3PAR Management Plug-in and Recovery Manager Software for VMwarevSphere is deployed as a vSphere Client plug-in. You must first log into the vCenter Server beforeaccessing HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere’sfeatures. HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSpheredoes not ask for a user name or password. Instead, it uses a user login credentials to accessVMware inventory. This credential sharing is the VMware recommended way for transparent plug-inauthentication.

14 Overview

VMware vCenter Server Login for HP 3PAR Virtual Volume and Virtual CopyManagement

HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere creates anew vCenter Server role named HP 3PAR Recovery Manager Administrator upon plug-in registration.The following restrictions apply for the HP 3PAR Recovery Manager Administrator role:

• All non-administrator users must be in this role.

• If an administrator logs in as Administrator or DOMAIN\Administrator, the permission checkis skipped.

NOTE: For VM access, the HP 3PAR Recovery Manager Administrator role must be assigned atthe ESX server level or the cluster server level where the VM resides. For Datastore access, the HP3PAR Recovery Manager Administrator role must be assigned at the datacenter level.

HP 3PAR StoreServ Storage System LoginHP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere has toconnect to an HP 3PAR storage array in order to obtain volume details for mapping and VirtualCopy management. You can log on to a system on an on-demand basis and HP 3PAR ManagementPlug-in and Recovery Manager Software for VMware vSphere does not save any storage systemuser names or passwords locally on the desktop, or centrally on the server. When HP 3PARManagement Plug-in and Recovery Manager Software for VMware vSphere needs to access anHP 3PAR StoreServ Storage System and no connection already exists, it will display an error andprovide instructions for entering the storage system name, user name, and password.As a convenient option, you can use the auto login feature by selecting the “Remember me” checkbox when logging onto a given system. In this case, the login details are stored in the Credentialdatabase and you do not have to enter them every time you access the system. To replace thecurrently saved credential, you must log out from the storage system and login again with “Rememberme” checked for the new credential. To remove the currently saved credential, logout from thestorage system and login again with the same credential with “Remember me” unchecked. Youcan also remove the currently saved credential through the Admin Tool→Storage System Credentialtab.

NOTE: When the VMware Sphere client initially loads the HP 3PAR plug-in page during an avCenter session, the HP 3PAR Recovery Manager for VMware vSphere searches and identifies theassociating storage system. If the associating storage system is configured with the auto-loginoption, the storage system information is also collected simultaneously. As a result, you mayexperience an increase in time for the page to load and display the volume information. Whenthe auto-login is fully executed, all HP 3PAR pages should load according to the performance levelof the system.

NOTE: You must have a minimum of Edit level or 3PAR_RM level privileges for accessing theVirtual Copies tab, and Browse level privileges for accessing the Virtual Volumes tab.

Network Ports used by HP 3PAR Management Plug-in and Recovery Manager Softwarefor VMware vSphere

HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere uses thefollowing network port:9931 ( Recovery Manager service default port), 9997 (VASA default port), vCenter Server HTTPport, and vCenter Server HTTPS port for secure access (between the vCenter Server, VI client, andHP 3PAR Management Plug-in and Recovery Manager for VMware vSphere.

User Authentication 15

Firewalls, if any, must be configured to allow traffic to these ports with the outbound connectionsrule set to allow (default) in order for HP 3PAR Management Plug-in and Recovery Manager forVMware vSphere to function properly.

HP 3PAR Management Plug-in and Recovery Manager Software forVMware vSphere Interface

HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere appears asa tab in the vSphere Client. When the HP 3PAR tab is selected, the HP 3PAR Management Plug-inand Recovery Manager for VMware vSphere interface appears as shown in Figure 2 (page 16).The interface is divided into the following:

• Main menu navigation

• Navigation tree

• Tabs and detail pane

• Tasks and alerts paneThe interface elements are referenced later in this guide .

Figure 2 HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphereInterface

HP 3PAR Views in the vSphere ClientThe HP 3PAR Management Plug-in and the Recovery Manager Software for VMware vSphere addsits own plug-in views in the vSphere Client. Each plug-in view is associated with a VMware entitysuch as a VM or Datastore (Virtual Volume). The details of plug-in views are defined in an XMLfile URL, which is registered with the vCenter Server during plug-in registration (see “Installing HP3PAR Management Plug-in and Recovery Manager Software for VMware vSphere” (page 29) forinformation about registering HP 3PAR Management Plug-in and Recovery Manager Software forVMware vSphere).

16 Overview

HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere adds thefollowing views to the vSphere Client:

• Datastore View - Displays all virtual volumes associated with a Datastore.

• Virtual Machine View - Displays all virtual volumes associated with a VM. Volumes that useRaw Device Mapped (RDM) virtual disks are also displayed.

• ESX Host View - Displays all virtual volumes that are assigned to the ESX host.

• Cluster View - Displays all virtual volumes associated with every ESX host in the cluster.

• Datacenter View - The VMware datacenter has several ESX hosts and Clusters. This viewdisplays all virtual volumes associated with every ESX host in the datacenter.

NOTE: HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSpheredoes not support a single ESX host mapped to multiple HP 3PAR StoreServ Storage system hostnames. All WWNs for each Fiber Channel host adaptor on the same ESX server should be usedto create a single host name on the storage system.

Datastore ViewTo access the Datastore view:1. Under Inventory from the vSphere Client home page, click Datastores.

Figure 3 Selecting Datastores

HP 3PAR Views in the vSphere Client 17

All Datastores residing in the data center are displayed in the navigation tree.

Figure 4 Viewing Datastores in the Navigation Tree

2. Select a Datastore and then click the HP 3PAR tab.Information about the virtual volumes associated with the Datastore are displayed.

Virtual Machine ViewTo access the Virtual Machine (VM) view:

18 Overview

1. Under Inventory from the vSphere Client home page, click VMs and Templates.

Figure 5 Selecting VMs and Templates

All VMs in the data center are displayed in the navigation tree.

Figure 6 Viewing VMs in the Navigation Tree

2. Select a VM and then click the HP 3PAR tab.Information about the virtual volumes associated with the VM is displayed.

ESX Host ViewTo access the ESX host view:


1. Under Inventory from the vSphere Client home page, click Hosts and Clusters.

Figure 7 Selecting Hosts and Clusters

All hosts in the data center are displayed in the navigation tree.

Figure 8 Viewing Hosts in the Navigation Tree

2. Select a host and then click the HP 3PAR tab.Information about the virtual volumes associated with the host is displayed.

Cluster ViewTo access the cluster view:

20 Overview

1. Under Inventory from the vSphere Client home page, click Hosts and Clusters (see Figure 7(page 20)).All clusters in the data center are displayed in the navigation tree.

Figure 9 Viewing Clusters in the Navigation Tree

2. Select a cluster and then click the HP 3PAR tab.Information about the virtual volumes associated with the cluster is displayed.

Datacenter ViewTo access the datacenter view:1. Under Inventory from the vSphere Client home page, click Datastores, VMs and Templates,

or Hosts and Clusters (see Figure 3 (page 17), Figure 5 (page 19), or Figure 7 (page 20)).All Datacenters are displayed in the navigation tree.

Figure 10 Viewing Datacenters in the Navigation Tree

2. Select a datacenter and then click the HP 3PAR tab.Information about the virtual volumes associated with that datacenter is displayed.


About Virtual Copy ManagementNOTE: HP 3PAR Recovery Manager for VMware vSphere is not functional without the HP 3PARRecovery Manager for VMware vSphere license. Additionally, the HP 3PAR Virtual Copy licenseis required for Virtual Copy operation and the HP 3PAR Virtual Lock license is required for usingthe volume retention policy. RMV will check for an existing HP 3PAR Virtual Lock license on thestorage system when a Virtual Copy is created with retention is specified.

HP 3PAR Recovery Manager for VMware vSphere allows you to take LUN-level Virtual Copies ofVirtual Machines (VMs), Datastores and Remote Copy groups. A Datastore is created on one HP3PAR volume, and a VM is created on one or more Datastores. During VM Virtual Copy creation,Recovery Manager for VMware vSphere will identify all the underlying HP 3PAR volumes and takeVirtual Copies simultaneously for all volumes to ensure consistency. Recovery Manager for VMwarevSphere manages this set of Virtual Copies as a single entity. Remote Copy Virtual Copies arebased at the Remote Copy group level (storage system), versus the Virtual Machine or Datastorelevel (VMware perspective).

NOTE: VMware Tools must be installed on the Guest OS in order for HP 3PAR Recovery Managerfor VMware vSphere to create successful VM/Application consistent Virtual Copies. Refer toVMware documentation for more information about VMware Tools setup instructions.

Virtual Copy Data ConsistencySeveral types of data consistency are possible for VM Virtual Copies and backup.

NOTE: The current version of HP 3PAR Recovery Manager for VMware vSphere supports systemcrash, VM and application consistent Virtual Copies.

• Crash Consistent - A simple virtual volume Virtual Copy without quiescing the memory blocksinside the guest OS results in a crash consistent Virtual Copy of the VM. Data not flushed willbe lost, but all data written to the file system will be available. Sanity checking of file system(fsck) is needed after recovery.

• VM Consistent - All file system blocks are flushed from the memory of a VM before a VirtualCopy is taken. This ensures that no file system data is lost if the VM crashes. Checking of filesystem (fsck) is not required after recovery. No application data is flushed from memory beforethe Virtual Copy is taken

• Application Consistent - Application consistency is provided for HP 3PAR snapshots of VirtualMachines for data compatibility with supported applications.

NOTE: A VM consistent Virtual Copy is always attempted if VMware Tools is installed on theGuest OS. VMware must first successfully create a VMFS snapshot. For information on the bestpractices and limitations of VMware snapshots, see the VMware knowledge base http://kb.vmware.com/.

Virtual Copy PolicyRecovery Manager for VMware vSphere allows the creation of Virtual Copy policies for VMsand/or Datastores. Only one policy is permitted for every VM and/or Datastore. Datastore andVM policies exist independently; meaning a VM policy is independent of the policy of theDatastore(s) of virtual disks it is using.In Recovery Manager for VMware vSphere, the Virtual Copy policy contains the following attributes:• Maximum Number of Virtual Copy Sets - You can choose how many Virtual Copies to be

retained. When the number of Virtual Copies is at the maximum limit, the oldest Virtual Copyis deleted when a new Virtual Copy is created.

22 Overview

http://kb.vmware.com/

http://kb.vmware.com/

NOTE: RMV supports a maximum of eight VCs within a Remote Copy group.

• Enable expirable Virtual Copies - Allows you to specify that created Virtual Copies are removedaccording to a specified schedule and are not affected by the maximum count.

• Retain Virtual Copy Set - The supported number of hours and days that a Virtual Copy set isretained.

NOTE: The Retain Virtual Copy Set option requires the HP 3PAR Virtual Lock license. RMVwill check for an existing HP 3PAR Virtual Lock license on the storage system when a VirtualCopy is created with retention is specified. Contact your local service provider for additionalinformation.

• Ensure Application Consistency - This option is used to create Virtual Copies that adhere todata format standards used by Microsoft VSS for guest operating systems. This option isavailable for Virtual Machine and Datastore with Virtual Machines.

Datastore Virtual CopiesA Datastore is created on a Fibre Channel or iSCSI LUN. During Virtual Copy creation, RecoveryManager for VMware vSphere identifies the HP 3PAR volume used and takes a Virtual Copy ofthe volume. Recovery Manager for VMware vSphere stores the details of all virtual disks and VMspresent in the Datastore.This feature has the following restrictions:

• The Datastore must be on exactly one HP 3PAR volume. A Datastore that spans across morethan one LUN is not supported.

• RDM LUNs defined in the Datastore are not included in the Virtual Copy. It is possible that aHP 3PAR LUN is used as RDM in a guest OS, which is defined in a Datastore created onanother HP 3PAR LUN.

NOTE: A Virtual Copy of a Datastore does not include any RDM 3PAR LUNs.

• All Datastore Virtual Copies can be VM or crash consistent. File system and/or applicationintegrity checks must be performed in the guest OS for the crash consistent Virtual Copies afterrestoration.

• Network File System (NFS) Datastores are not supported.

• VMFS file systems spanning multiple hard disk partitions to create a single logical volume arenot supported.

• The Datastore must not be on an ESX SAN boot disk. Virtual Copy operations are not supportedon Datastores residing in ESX SAN boot disks.

For information about creating Virtual Copies, see “Creating New Virtual Copies” (page 70).

Virtual Machine Virtual CopiesA Virtual Machine (VM) configuration files are created in a Datastore. VMDK virtual disks usedby VMs are created on one or more Datastores. In addition, a VM can use HP 3PAR volumesdirectly as RDM virtual disks. Recovery Manager for VMware vSphere identifies all of the HP 3PARvolumes used by a VM and creates Virtual Copies of all of them simultaneously. A list of virtualdisk names and their type (RDM or VMDK) and configuration file name are also recorded in therepository during Virtual Copy creation.

About Virtual Copy Management 23

A VM Virtual Copy has the following restrictions:

• Virtual disks used by a VM must be from the HP 3PAR Datastore, and the latter must satisfythe conditions mentioned in “Datastore Virtual Copies” (page 23).

• If the VM uses more than one HP 3PAR volume, all of them must be from the same HP 3PARstorage array.

• VMs that use a mix of HP 3PAR LUNs and third party LUNs are not supported.

• All VM Virtual Copies can be VM or crash consistent. File system and/or application integritychecks must be performed in the guest OS after restoration for the crash consistent VirtualCopies.

• VMs using NFS Datastores are not permitted.

• VMFS file systems spanning multiple hard disk partitions to create a single logical volume arenot supported.

For information about creating VM Virtual Copies, see “Creating New Virtual Copies” (page 70).

Remote Virtual CopiesRemote Virtual Copies are based on the Remote Copy Group. If a VM or Datastore uses virtualvolumes outside of the Remote Copy group, HP 3PAR Recovery Manager for VMware vSpherecannot take a remote Virtual Copy of the group. Remote Virtual Copies require a remote host withTCP/IP connectivity to the target Storage System.

• VMs or Datastores must be contained within the Remote Copy group

• Restore processes are currently performed manually

The Virtual Copy Browser

NOTE: You must have an HP 3PAR Recovery Manager for VMware vSphere license in order touse the Virtual Copy browser.

In Recovery Manager for VMware vSphere, every Virtual Copy, VM, or Datastore has its ownmetadata, which is used in instances where a restoration is necessary. Metadata is kept in a localfile system of the server.You can view Virtual Copy metadata at any time after it was created using the Virtual Copy browserof the VM and Datastore views of the plug-in.

24 Overview

Figure 11 Virtual Copy Browser

A Virtual Copy of a VM or Datastore has the following properties:

• The Virtual Copy creation time.

• The HP 3PAR StoreServ Storage system where Virtual Copy volumes exist.

• The Virtual Copy set name (optional).

• The number of Virtual Copy volumes in the Virtual Copy.

• A list of pairs (source volume, Virtual Copy volume). Each pair can have a list of virtual disksand/or VM names.

All Virtual Copies are organized in the browser based on their creation times. The browser displaysall relevant metadata so that you can make restore decisions faster and without actually mountingVirtual Copy volumes.The data shown in the Virtual Copy browser comes from the metadata repository and may notreflect the current state of HP 3PAR StoreServ Storage system. It is possible that volumes shown inthe browser may not exist in the HP 3PAR StoreServ Storage system; for example, if a volume isdeleted.For information about viewing the Virtual Copy browser, see Figure 45 (page 60).

VMFS SnapshotsIn order to maintain a VM consistent Virtual Copy, a VMFS snapshot will be created before creatingan HP 3PAR Virtual Copy and the VMFS copy will be deleted when the HP 3PAR Virtual Copy iscreated. HP 3PAR Virtual Copies and VMFS snapshots cannot coexist. HP 3PAR Virtual Copycreation in VM, Datastore, or Remote Copy will fail if there are preexisting VMFS snapshots forthe VM.

NOTE: When creating a VMFS snapshot, VMware can fail the operation with the message:“Cannot create a quiesced snapshot because the create snapshot operation exceeded the timelimit for holding off I/O in the frozen Virtual Machine.”If this message is displayed, the VMware Tools process should be restarted, or reinstalled to resolvethe issue.

About Virtual Copy Management 25

Scheduling ToolYou can automatically have Virtual Copies created according to a specified schedule by using thescheduling tool (see “Scheduling Virtual Copies” (page 75) for details). You have the option ofscheduling when (hourly, daily, weekly, monthly) the Virtual Copy is to be created and thenspecifying how often the task is to be performed. You can also schedule a Virtual Copy creationtask to occur on a one-time basis.

Host ExplorerHost Explorer for VMware communicates with the storage server over a TCP/IP connection andprovides detailed host configuration information. You can start the service and configure settingsthrough the Host Explorer tab available from the RMVMware Admin Tool GUI interface (see “HostExplorer Tab” (page 43) for details).

VASA SupportSupport is included for vSphere Storage APIs for Storage Awareness (VASA) that allows a VMwareadministrators to view information about the physical storage array as well as the virtual datastore. For more information on VASA, refer to "Storage Providers" in vCenter Server.

26 Overview

2 Installing, Registering, and Uninstalling HP 3PARManagement Plug-in and Recovery Manager Softwarefor VMware vSphere

This chapter describes how to install, register, uninstall, and upgrade HP 3PAR Management Plug-inand Recovery Manager Software for VMware vSphere.

Supported PlatformsFor information about supported platforms, refer to the HP 3PAR OS Configuration Matrix. Forinformation about supported hardware and software platforms, refer to http://www.hp.com/go/3par/ and navigate to your product page.

Preinstallation Requirements and DependenciesPrior to the installation of HP 3PAR Management Plug-in and Recovery Manager Software forVMware vSphere, make sure that the following preinstallation requirements are met:

• HP 3PAR Recovery Manager Software for VMware vSphere is distributed as a Microsoftinstaller MSI image, RMVMware_<platform>.msi, where <platform> can be x86 forWindows 32-bit OS or x64 for Windows 64-bit OS.

• HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere issupported on Microsoft Windows 2008 x86, Windows 2008 x64, and Windows 2008 R2.HP recommends installing Microsoft Windows on a standalone system.

• HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere supportsvCenter Server 4.1, 5.0, and 5.1, ESX 4.0, ESXi 4.1 and 5.0, and vSphere 5.0.

NOTE: For full functionality and compatibility, it is recommended that you update to thelatest versions of vCenter Server and ESX. Both ESX 3.5. and vCenter Server 4.1 does notsupport VASA.

• Microsoft.NET 4.0 Runtime is required or installation fails.

• The HP 3PAR Recovery Manager for VMware vSphere license and the HP 3PAR Virtual Copylicense is required for Virtual Copy operation.

• The HP 3PAR Virtual Lock license is required for setting retention policies in Virtual Copycreation. RMV will check for an existing HP 3PAR Virtual Lock license on the storage systemwhen a Virtual Copy is created with retention is specified.

• The HP 3PAR Remote Copy license is required for remote Virtual Copy operation.

• You must have a minimum of Edit level privilege (or the 3PAR_RM role) for Virtual Copyoperations, and Browse level privilege for virtual volume operations.

• You must be an Administrator of the vCenter Server for plug-in registration.

NOTE: Microsoft Silverlight is required only for the desktop. Recovery Manager for VMwarevSphere server does not require Microsoft Silverlight.

• Desktops running vSphere clients (where HP 3PAR Management Plug-in and Recovery ManagerSoftware for VMware vSphere pages are displayed) must have the Microsoft web browserplug-in Silverlight runtime installed. The controls of the Microsoft web browser plug-in Silverlightare used for rendering HP 3PAR Management Plug-in and Recovery Manager Software forVMware vSphere’s web pages. You will be prompted to download Silverlight the first timeHP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere’s webpages are displayed if Silverlight is not already installed. If after you have downloaded and

Supported Platforms 27

http://www.hp.com/go/3par/


installed Silverlight, the page still displays "Get Microsoft Silverlight", you can reset the pagewith following steps:From the top menu bar, select Plug-ins\Manage Plug-ins to bring up the Plug-in Manager.Right click HP 3PAR Recovery Manager Software for VMware vSphere and select Disable.Right click HP 3PAR Recovery Manager Software for VMware vSphere again and select Enable.Close the VI Client and reopen it again.

• VMs must have VMware Tools installed in order to perform Virtual Copy operations withapplication consistency. Refer to VMware documentation for more information about VMwareTools setup instructions.

• The current release of Recovery Manager server is not internationalized, however it supportsinstallation on Windows server with English and Japanese locale with operations in Englishmode only.

Allowing Port Selections with Windows 2008 InstallationTo set up HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSpherewith the SSL port for communications, you need to grant full permission to the Administrator. Hereare the steps you should follow before the installation:1. Open Explorer and go to <System Drive:>\ProgramData\Microsoft\Crypto\RSA.

You must explicitly type in the path since ProgramData is a hidden directory.

2. Right-click MachineKeys and choose Properties.The MachineKeys Properties Dialog appears (Figure 12 (page 28)).

Figure 12 MachineKeys Properties Dialog

3. Select the Security tab.The Security Tab dialog appears (Figure 13 (page 29)).

28 Installing, Registering, and Uninstalling HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere

Figure 13 Security Tab Dialog

4. Under Group or user names, choose Administrators.5. Under Permissions for Administrators, grant Full control.6. Click OK.

You can now proceed with the installation if RMV is not previously installed onto the system.

For a system with RMV previously installed, complete the following steps before proceeding withthe installation:1. Click Start, type mmc in the Search programs and files box, and press Enter.2. On the File menu, click Add/Remove Snap-in.3. Under Available snap-ins, double-click Certificates.4. Select Computer account and click Next.5. Click Local computer and click Finish.6. Click OK.7. From the left pane, navigate to Console Root→Certificates (Local

Computer)→Personal→Certificates.8. Delete 3PAR Plug-in.

Installing HP 3PAR Management Plug-in and Recovery Manager Softwarefor VMware vSphere

HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere is supportedin Windows 2008, and Windows 2008 R2. Both x86 and x64 are supported. The installationpackage provides the following:

• RMVMware_x86.msi

• RMVMware_x64.msi

To install HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere,perform the following:

Installing HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere 29

1. Insert the HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSpheredisc into your CD-ROM drive.

2. Double-click the installation package appropriate for your system to launch the installationwizard.

NOTE: You must be an Administrator of the vCenter Server for plug-in registration.

NOTE: You must complete the information requested in the plug-in registration dialog boxin order to complete the HP 3PAR Management Plug-in and Recovery Manager Software forVMware vSphere installation.

3. Follow the installation wizard instructions.The plug-in registration dialog box appears.

Figure 14 Plug-in Registration Dialog

4. In the Plug-in Web Service for VMware vSphere Configuration group box, enter the followinginformation:• Recovery Manager server name - The network host name known by the vCenter Server

where Recovery Manager is installed. Defaults to the local host name. An IP address canbe alternatively entered.

• Recovery Manager service TCP port - The default secure network port is 9931. The portcan be changed, however it cannot conflict with other usage.

NOTE: Windows 2008 installations need to grant full permissions to the Administratorin order to be able to change port assignments. (see “Allowing Port Selections withWindows 2008 Installation” (page 28) for details.

NOTE: VMware vCenter Server 4.1, 5.0 and 5.1 are supported in this release.

5. As an option, you can select the “Skip Plug-in Registration” check box for RMV installationson a remote site where a remote vCenter has not been installed. To manage a remote VirtualCopy, the RMV server on the remote site needs to register to the vCenter during the installationor via the Admin Tool after the installation.


6. In the Plug-in Registration group box, enter the following information:• vCenter Server - The name of the vCenter Server.

• User name - The administrator user name.

• Password - The administrator user password.

NOTE: The same instance of HP 3PAR Management Plug-in and Recovery Manager Softwarefor VMware vSphere can be registered with multiple vCenter Servers. Use the RMVMwareAdmin Tool to register HP 3PAR Management Plug-in and Recovery Manager Software forVMware vSphere. Refer to “The RMVMware Admin Tool” (page 36) for instructions onaccessing the RMVMware Admin Tool and “Plug-in Registration” (page 40) for instructionson registering the plug-in.

7. Click Next.The VASA Provider Web Service Configuration is requested.

8. Supply the appropriate web service network port for the VASA provider, then click Next.9. Click Close.

NOTE: HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSpheredoes support VMware vCenter Linked Mode server. For more information, follow the link:https://www.vmware.com/products/vcenter-server/features.html.

Support for VMware vCenter Server Linked ModeThe HP 3PAR Management Plug-in supports a feature of VMware known as Linked Mode andallows you to create and manage a Linked Mode group during or after vCenter Server installation.Use the following instructions to install Recovery Manager for VMware in a Linked Modeenvironment:1. Verify the RMV server is associated with the same Active Directory domain as the vCenters.2. Ensure the RMV plug-in is registered with all vCenters that associate with Linked Mode

configuration.3. Log on to vSphere client using Active Domain user name.4. After logging on to vSphere client, log on to an HP 3PAR StoreServ Storage system(s).

a. Go to Home Page and click the HP 3PAR Management Plug-in and Recovery ManagerSoftware for VMware vSphere. This opens to the storage system home page for one ofthe vCenters.

b. Use a valid user name and password to log on to required storage systems.

Installing HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere 31

https://www.vmware.com/products/vcenter-server/features.html

5. Repeat step 4 for the remaining vCenter servers by selecting a vCenter from the drop downlist.

Figure 15 vCenter Drop Down List

NOTE: Users may require to log on to the same storage system more than once if it is connectedto more than one vCenter.

For more information about VMware vCenter Linked Mode, go to https://www.vmware.com/products/vcenter-server/features.html.If you are experiencing HP 3PAR multi-tab issues, refer to “Resolving HP 3PAR Multi-tab Issue”(page 124) for more details about how to resolve the issue.

Viewing and Installing HP 3PAR Management Plug-in CertificateHP 3PAR Management Plug-in uses a self-signed certificate. If a Security Alert dialog box appearsand displays the certificate is not trusted, use the following steps to install the certificate.1. Click View Certificate.2. From the Certificate dialog box, click Install Certificate.3. Continue to follow the Wizard. Select Place All certificates in the following store on Certificate

Store page and click Browse.4. From the Select Certificate Store dialog box, select Trusted Root Certification Authorities and

click OK.5. Complete the Wizard tasks.6. Click OK to exit Certificate dialog box.

Registering an SMS Certificate for the VASA ProviderBoth the vCenter Server and VASA Provider use SSL certificates. The VASA Provider support includedwith Recovery Manager for VMware uses the same certificate used by the Plug-in web service.However, before you can use the vCenter Server to register the VASA provider, you must manuallyinstall the SMS certificate extracted from the vCenter server onto the VASA installed host. Thisprocess is required for every vCenter Server you intend to register with the VASA provider. Thesame process is also required if the SMS certificate has a new certificate. The SMS extraction andinstallation process is provided in the following section.




Extracting the SMS Certificate

Extracting the SMS CertificateCreate the temp folder in the C:\ drive, before you perform the following procedure:For vCenter installed on Windows system:1. On vCenter Server installed host, navigate to the following location C:\Program Files\

VMware\Infrastructure\jre\bin.2. Enter the following command specifying the location and name for the certificate file:

For Windows 2008keytool -exportcert -v -keystore "c:\Programdata\VMware\VMwareVirtualCenter\SSL\sms.keystore" -file c:\temp\sms_new.cer -aliassms

For Windows 2003keytool -exportcert -v -keystore "C:\Documents and Settings\AllUsers\Application Data\VMware\VMware VirtualCenter\SSL\sms.keystore"-file c:\temp\sms_new.cer -alias sms

3. Press Enter when prompted to enter the keystore password.If the export is successful, the following message is displayed:

Certificate stored in file <file name>

For Virtual vCenter Appliances1. SSH to the Virtual vCenter Appliance, and navigate to the follow directory:

/etc/vmware-vpx/ssl

2. Enter the following command specifying the location and name for the certificate file of yourchoosing:

keytool -exportcert -v -keystore sms.keystore -filesms_new.cer -alias sms

3. Click Enter when prompted to enter the keystore password.If the export is successful, the following message is displayed:

Certificate stored in file <file name>

4. Download the newly created certificate file to the system where RMV is installed.

Installing the SMS CertificateYou need to install the SMS certificate on the VASA Provider host's Local Computer/Trusted RootCertification Authorities store.There are two methods to install SMS certificate:

• Using the VASA Provider web service (only applicable when the VASA web service is running).

• Manually registering the certificate through the certification store.

To Install the SMS Certificate Through the VASA Web ServicePerform the following steps to install the SMS certificate through the VASA web service:

Registering an SMS Certificate for the VASA Provider 33

1. Open the browser and enter the path for the VASA certificate registration service as follows:

<vasa web service url>/Config/Register

Here is an example:https://myvasaserver:9997/config/Register

2. If the Choose a digital certificate screen appears, click OK to continue.The HP 3PAR VASA Provider Certificate Registration screen should appear.

NOTE: If a certificate error occurs, click the Continue to this website (not recommended) link.

3. Click Browse to locate the extracted certification file, then click Submit to send it to VASAProvider.Upon submission, a message is returned indicating whether the registration was successful.If the registration was unsuccessful, try locating the required file again or try to install the SMSCertificate manually as described in (“Installing the SMS Certificate” (page 33)).

Installing the SMS Certificate on Windows 2008To manually install the SMS certificate:1. Copy the certification file to the VASA installed host.2. Right click the certification file and select Install Certificate.3. Supply the appropriate responses and information requested by the Certificate Import Wizard.4. On Certificate Store page, select the Place all certificates in the following store radio button

and click Browse.5. For the Select Certificate Store dialog, check the Show physical stores check box.6. Expand the Trusted Root Certificate Authorities tree and select Local Computer.7. Click OK.8. From the Certificate Store dialog, the certificate store path should appear as follows:

Trusted Root Certificate Authorities\Local Computer

9. Click Next and then Finish to complete the import process.

Installing SMS certificate on Windows 2012Before you install the SMS certificate on Windows 2012, you must create the following registrykey for Windows 2012 Server to send the list of Certificate Authorities that the client can chooseto pick the certificate from, and complete the client certificate request:1. Click Start→Run, enter regedit, and then click OK. The Registry Editor appears.2. Navigate to

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL.3. Click Edit→New→DWORD (32-bit) Value.4. Enter SendTrustedIssuerList in Value name, and enter 1 (numeric value one) in Value

data. Close the Registry Editor.Perform procedure similar to the steps described in “Installing the SMS Certificate on Windows2008” (page 34).


Uninstalling HP 3PAR Management Plug-in and Recovery Manager Softwarefor VMware vSphere

To uninstall HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere:1. Click Start→Control Panel→Programs and Features.2. Select HP 3PAR Management Plug-in and Recovery Manager for VMware vSphere from the

list of programs.3. Click Uninstall.4. If the secure network port is used, you need to unbind the port.

For installations on Windows 2008, run netsh http show sslcert to view port bindinginformation.

Upgrading from a Previous VersionWhen upgrading from a previous version, the installer detects whether a previous version is installedand then either performs a new install or an upgrade. Before upgrading from a previous version,consider the details provided in the following sections.

Using Secure Service ConnectionsWhen installing HP 3PAR Management Plug-in and Recovery Manager Software for VMwarevSphere 2.3.0 over an existing installation, you must first make sure that the previous version usessecure service connections. If the previous version is using port 9930 (or any other unsecured port),use the Admin Tool to enable the secure service option for the older version before performing theupgrade. An upgrade is only applicable for version 2.1.0 and 2.2.0. See“Using the Admin Toolto Modify Configuration Settings” (page 36) for details.

Refreshing Plug-in DetailsWhen upgrading from a previous version, a prompt to update an existing plug-in registrationappears at the end of the installation. if you view plug-in details from the Plug-in Manger, theversion information is not updated to reflect the latest version. Use the Plug-in Registration optionavailable through the RMVMware Admin Tool to unregister and then register the plug-in with thevCenter server (see “Plug-in Registration” (page 40) for details).

NOTE: When upgrading from a previous version, if vCenter is not responding to the upgradewithin 30 seconds, a message box displays. Click Yes to continue with upgrade.

Uninstalling HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere 35

3 Using the Admin Tool to Modify Configuration SettingsThis chapter describes the default HP 3PAR Management Plug-in and Recovery Manager Softwarefor VMware vSphere configuration, as well as how to edit configuration settings using theRMVMware Admin Tool.

OverviewHP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere is providedwith default configuration settings that are compatible with most environments. However, it isrecommended that you verify the default parameters and make appropriate changes as necessary.RMVMware Admin Tool, a Graphical User Interface (GUI), is provided for making configurationchanges.

The RMVMware Admin ToolThe RMVMware Admin Tool is used to configure HP 3PAR Management Plug-in and RecoveryManager Software for VMware vSphere, configure VASA, set the storage system credentials, andconfigure Host Explorer for VMware.

NOTE: To use the RMVMware Admin Tool, you must have Administrator privileges. If you areusing Windows 2008, and have User Account Control activated, you need right click theRMVMware Admin Tool and launch it using the Run as Administrator option.

To access the RMVMware Admin Tool click Start→All Programs→HP 3PAR→HP 3PAR ManagementPlug-in and Recovery Manager for VMware vSphere Admin Tool.The configuration options are accessed through the following tabs, which are discussed further inthe proceeding sections:

• vCenter Plug-in -- Configures the RMV plug-in for the vCenter Server.

• Host Explorer -- Configures the Host Explorer to retrieve appropriate ESX host information fromthe vCenter Server.

• VASA -- Configure VASA functionality and HP 3PAR StoreServ Storage system mapping.

• Storage System Credentials -- Configures the credential information for access to storagesystems.

vCenter Plug-in TabThe vCenter Plug-in tab allows you to edit HP 3PAR Management Plug-in parameters for optimaluse in your environment (Figure 16 (page 37)).

36 Using the Admin Tool to Modify Configuration Settings

Figure 16 vCenter Plug-in Tab

Details concerning the fields of the vCenter Plug-in tab are provided in the following sections.

vCenter Plug-in ConfigurationThe vCenter Plug-in configuration is used to specify the host name and VM service port. Debugsettings can also be configured here.To modify the information on the Configuration option:

vCenter Plug-in Tab 37

1. Click Edit.The Edit Configuration dialog box appears (Figure 17 (page 38)).

Figure 17 vCenter Plug-in Configuration

NOTE: If you wish to change the values of the Recovery Manager server name or RecoveryManager service TCP port properties under the Configuration tab, you must unregister the HP3PAR Management Plug-in and Recovery Manager Software for VMware vSphere plug-infrom all vCenter Servers prior to the change; restart HP 3PAR Management Plug-in and RecoveryManager for VMware vSphere Web Service; and reregister the vCenter Servers again afterthe change. If the HP 3PAR Recovery Manager Administrator is assigned in the vCenter server,the privilege will be lost when the plug-in is unregistered. The role will need to be reassigned.

NOTE: If you encounter the following message, Could not create port binding.SSL Certificate add failed, Error: 1312 A specified session doesnot exist. It may already have been terminated. , while changing the portnumber, refer to “Allowing Port Selections with Windows 2008 Installation” (page 28) to addpermission and remove an existing certificate. Rerun the Admin Tool to change the port number.

The fields available from the Configuration tab are shown in Table 1 (page 38).

Table 1 Configuration Tab Fields

DescriptionFieldGroup

The network host of the server where HP3PAR Management Plug-in and Recovery

Recovery Manager server nameConfiguration

Manager Software for VMware vSphere isinstalled. The vCenter Server and alldesktops running the vSphere client usingthe HP 3PAR plug-in must be able to reachthis server. The name is used whileregistering the HP 3PAR plug-in with thevCenter Server.The fully qualified name of the DNS nameof the running server is the default name.The name can be changed to any name orIP address.

The network port number that theTpdVmWebService Web service uses. The

Recovery Manager service TCP port

default port is 9931 for secure connections.This can be changed to any unused port.


Table 1 Configuration Tab Fields (continued)

DescriptionFieldGroup

HP 3PAR Management Plug-in andRecovery Manager Software for VMware

Secure service

vSphere uses a secure Web service (usingSSL certificates) securing all interactionsbetween the VMware components (vCenterServer and vSphere clients) and HP 3PARManagement Plug-in and RecoveryManager Software for VMware vSphere.The SSL certificate for HP 3PARManagement Plug-in and RecoveryManager Software for VMware vSphere(provided by HP) must be installed.

Displays the current thumbprint binded tothe TCP port.

Binded to thumbprint

This option is available for the user tochange the current SSL certificate.

Change Certificate

The trace file name. The default file nameis <system drive>:\Program Files\

Log folderDebug

3PAR\Plug-In for VmwarevSphere\Log.

Specifies the level of verbosity of the logfile. The default value is Low.

Debug level

2. Modify the fields as necessary.3. To change the certificate, click Change Certificate and select one of the following options:

a. Use Recovery Manager self-signed certificate - Select this option to use the server-specificcertificate created during installation.

b. Select from Local Computer\Personal Certificate Store - Select from the certificate(s) currentlystored in the Personal Certificate Store.

c. Import PFX file - Use this option to import from a PFX file.

Figure 18 Select Certificate for Binding


4. Click Verify.The operating environment is examined and, if no configuration errors are reported, a dialogappears indicating that the configuration has been completed successfully.

NOTE: Certificate binding to port will not be verified until you click Save.

5. Click OK.6. Click Save to save your changes.

NOTE: If the user has changed the port, they must unregister and then reregister the plug-into ensure the new port number is registered correctly in vCenter.

Plug-in RegistrationThe Plug-in Registration option is used to register and unregister the HP 3PAR plug-in with thevCenter Server is shown in (Figure 19 (page 40)).

Figure 19 Plug-in Registration

NOTE: You must be an Administrator of the vCenter Server for plug-in registration.

The fields available from the Plug-in Registration tab are shown in Table 2 (page 40).

Table 2 Plug-in Registration Option Fields

DescriptionField

The name of the vCenter Server.vCenter Server

The administrator user name.User Name

The administrator user password.Password

• If you are registering the plug-in, click Register.

• If you are unregistering the plug-in, click Unregister.


NOTE: The same instance of HP 3PAR Management Plug-in and Recovery Manager Softwarefor VMware vSphere can be registered with multiple vCenter Servers.

NOTE: The name of the vCenter Server entered during registration must be used for unregistering.For example, if you used the fully qualified domain name to register, you must use the fully qualifieddomain name to unregister.

vCenter StatusThe vCenter Status option displays a list of vCenter Servers to which the HP 3PAR ManagementPlug-in and Recovery Manager Software for VMware vSphere are registered. The vCenter Statusoption is shown in (Figure 20 (page 41)).

Figure 20 vCenter Status Option

The vCenter server, Recovery Manager Service Name and Recovery Manager Service TCP portare listed. The total number of registered vCenter Servers is also shown.

Remote Copy PairsThe Remote Copy Pairs option is used to manage the registration of Remote Copy pairs betweena local and remote system. The Remote Copy Pairs option is shown in (Figure 20 (page 41)).


Figure 21 Remote Copy Pairs

The Remote Copy Pairs list shows currently registered storage system Remote Copy pairs. The fieldsare as follows:

• Local Storage System/User - Name of the HP 3PAR StoreServ Storage system and the associateduser.

• Local Storage System Credential Windows User - Windows user credentials for the accessingthe local system.

• Remote Storage System/User - Name of the remote HP 3PAR StoreServ Storage system andassociated user.

• Remote Storage System Credential Windows User - Windows user credentials for the accessingthe remote system.

• Remote Recovery Manager Server - Remote Recovery Manager Server host identifier.To add a new Remote Copy pair registration, click the Register New button. The Register RemoteCopy Storage System Pair screen appears


Figure 22 Register Remote Copy Storage System Pair

NOTE: HP recommends using two RMV servers (a local and remote) for regular or periodic syncand a single RMV server (local) for Transparent Failover setups.

Host Explorer TabHost Explorer is a service that runs in the background and gathers ESX server information that ismanaged via the vCenter server for the HP 3PAR StoreServ Storage system. For Host Explorer tofunction properly, it needs to know which vCenter server to connect for information as well as thename of the system where the information will be sent.

Host Explorer ConfigurationThe Host Explorer configuration option is used to configure and check on the Host ExplorerConfiguration (Figure 23 (page 44)).

Host Explorer Tab 43

Figure 23 Host Explorer Configuration Option

The selections available from Host Explorer Configuration screen are described in Table 3 (page 44).

Table 3 Host Explorer Configuration Option Fields

DescriptionField

Starts the Host Explorer service.Start Service

Stops the Host Explorer service.Stop Service

Refreshes/restarts the Host Explorer service.Refresh Service

Allows you to change the refresh interval that determines how frequently the host explorerservice checks for host changes. The current state is compared with the previous state

Change Refresh Interval

and, if there have been any changes, the HP 3PAR StoreServ Storage system is updated.The default refresh interval is set to 12 hours.

Indicates whether the HP 3PAR Host Explorer service is currently running.Status

NOTE: The Host Explorer Service needs to be restarted after changing the refresh interval time.

Storage System MappingThe Storage System Mapping option is used to map existing HP 3PAR StoreServ Storage systemcredentials to be used by Host Explorer for submitting corresponding ESX host information. Thecredentials need to be created via Storage System Credential or RMVMware.exe with optionInServRegister prior to the mapping. Since Host Explorer uses the system ID obtained from ESXhost information to determine which HP 3PAR StoreServ Storage system it is connected to, onlyone mapping is allowed per storage system. The Host Explorer Storage System Mapping optionappears (Figure 24 (page 45)).


Figure 24 Host Explorer Storage System Mapping Option

The Storage System mapping list shows all the credentials that are currently defined. The fields areas follows:

• Storage System Name - Name of the registered HP 3PAR StoreServ Storage system.

• Storage System ID - System ID for the HP 3PAR StoreServ Storage system.

• Storage System User - User name associated with the HP 3PAR StoreServ Storage system.

• Windows User - Windows user who created the Storage System credential.To add a mapping:1. Click Add. The Map Registered HP 3PAR Storage System Credential dialog appears.

2. Choose the appropriate HP 3PAR StoreServ Storage System entry from the list, then click OK.You can only remove one entry at a time. Confirmation will be given during the removalprocess.If an HP 3PAR StoreServ Storage system ID already exists on the mapping list, any registeredentry that has the same Storage System ID is filtered out.

vCenter MappingThe vCenter Mapping option is used to map existing vCenter credential from a selected vCenterStore Credential file for use by Host Explorer to make inquiries about ESX host information.The vCenter mapping list shows all the credentials that are currently defined. The fields are asfollows:

• vCenter Server - Name of the vCenter server.

• User Name - User name associated with the vCenter server.

• File Path - Location of the credential store file.To add a mapping:1. Start a RMVMware CLI session and execute RMVMware VcenterRegister to generate the

XML credential file for the particular vCenter you want to map.

Host Explorer Tab 45

2. Click Add.

Figure 25 Host Explorer vCenter Mapping

The Map Registered vCenter Server Credential dialog appears.

3. Click Browse to import an existing vCenter credential store file.4. Choose the appropriate file from the list, then click Select.

You can only remove one entry at a time. Confirmation will be given during the removalprocess.

Figure 26 Map Registered vCenter Server Credential List


NOTE: The vCenter Store Credentials file should be set to allow access permission for theadministrative group and system account.

5. Click Open.6. Select vCenter name to map.7. Click Select.

The VASA TabA VASA Provider is a software component that acts as a server in the vSphere environment. AvCenter Server connects to the VASA Provider to obtain information about available storagetopology, capabilities, and state. The vCenter Server can then provide the appropriate informationto vSphere clients.

VASA ConfigurationThe VASA Configuration option is used to examine and configure VASA capabilities for yourinstallation. (Figure 27 (page 47)).

Figure 27 VASA Configuration

The selections available from VASA Configuration screen are described in Table 4 (page 47).

Table 4 VASA Configuration Options

DescriptionField

Shows the port to which the VASA web service is binding.VASA service TCP port

Shows whether secure service is selected.Secure service

Shows the URL address required to connect to VASA web service.Web service URL

Shows the folder where log files are stored.Log folder

Specifies the level of verbosity for the log file.Debug levelThe default value is Medium.

To modify the VASA configuration options:

The VASA Tab 47

1. Click the Edit button.The Edit Configuration dialog box appears.

Table 5 VASA Configuration Edit Options

DescriptionField

Specifies a numeric value for binding a specified port.VASA service TCP port

Indicates that secure communications are implemented. For security purposes, thisoption is fixed and cannot be modified.

Secure services

Displays the current thumbprint binded to the TCP port.Binded to thumbprint

This option is available for the user to change the current SSL certificate.Change Certificate

Specifies the debug level. There are three debug levels to choose from (low, medium,high). Setting the level to high will log everything including communication requestand responses between SMS and VASA.

Debug level

The location of the log folder is fixed.Log folder

Validates the port usage.Verify (button)

Saves the current configuration.Save (button)

Closes the Edit dialog.Close (button)

If the debug level is modified, changes will be updated to the VASA web service immediately.If the port number is modified, user will be prompted with a confirmation to restart the VASAweb service.

Figure 28 VASA Edit Configuration


2. To change the certificate, click Change Certificate and select one of the following options:a. Use Recovery Manager self-signed certificate - Select this option to use the server-specific

certificate created during installation.b. Select from Local Computer\Personal Certificate Store - Select from the certificate(s) currently

stored in the Personal Certificate Store.c. Import PFX file - Use this option to import from a PFX file.

Figure 29 Select Certificate for Binding

The VASA Tab 49

Storage System MappingStorage System mapping allows user to map existing HP 3PAR StoreServ Storage system credentialsto be used by VASA to gather storage information in response to a request from a vCenter. TheStorage System credentials have to be created via Storage System Credential or RMVMware.exewith InServRegister option prior to the mapping. Since VASA uses the system ID obtainedfrom the ESX host information to determine which Storage System it is connected to, only onemapping is allowed per HP 3PAR StoreServ Storage system. The Storage System Mapping optionis shown in Figure 30 (page 50).

Figure 30 VASA Storage System Mapping


The Storage System mapping list shows all the credentials that are currently defined. The fields areas follows:Storage System Name - Name of the registered HP 3PAR StoreServ Storage system.Storage System ID - HP 3PAR StoreServ Storage system ID or Storage System ID.Storage System User - HP StoreServ Storage system User Name.Windows User - Windows user who created the Storage System credential.To add a mapping:1. Click Add.

The Map Registered HP 3PAR Storage System Credential dialog appears.

2. Choose the appropriate entry from the list, then click OK.If a Storage System ID has already been mapped on the mapping list, the adding dialog filtersout any registered entry that has the same Storage System ID.You also have the option of removing a credential mapping by selecting an entry from the listand choosing the Remove button. You can only remove one entry at a time. Confirmation isrequested before the removal is performed.If you encounter a problem when working with credentials, see “Troubleshooting for VASA”(page 109) for explanations of the various error codes.

NOTE: If the changes to Storage System mapping list contains hosts that vCenter is currentlymonitoring, the existing VASA session associated with the vCenter is invalidated.

Storage System Credential TabThe Storage System Credential tab allows you to add, remove and validate Storage Systemcredentials associated with a specific Windows login account as shown in (Figure 31 (page 51)).

Figure 31 Storage System Credential Tab

Storage System Credential Tab 51

You have the option of viewing all existing Windows users that have registered credentials, or youcan select a specific user from the list shown in the pull down menu.A listing of registered credentials is shown for the selected users with fields defined as follows:

• Storage System Name - Name of the HP 3PAR StoreServ Storage system.

• Storage System ID - System ID for the HP 3PAR StoreServ Storage system.

• Storage System User - User name for accessing the HP 3PAR StoreServ Storage system.

• Windows User - Windows user that created the credentials.

• Reserved By - If available, shows the component for which the credentials are reserved. If thecredential are cashed via the Plug-in auto login feature, then credentials are valid only for thePlug-in and are not valid for accessing any other components. To create credential for autologin purpose, the “Remember Me” check box must be checked when logging onto a givenStorage System.

To specify a new Storage System credential:1. Click Add.

The HP 3PAR Storage System Credential Management dialog appears.2. Enter the appropriate credential information for the HP 3PAR StoreServ Storage system and

user including the valid password, then click OK.You also have the option of removing or validating an entry. You can only remove onecredential at a time.

3. When you have finished, click Close.When adding a new credential, it will be associated with the current Windows user loginaccount by default. The validation process returns the appropriate user privileges uponsuccessful connection and validation with the HP 3PAR StoreServ Storage system. As analternative, when performing operations (e.g., Remote Copying) from a remote system , youcan deselect the Using current Windows logon user name option, and instead supply a specificWindows user name (domain\username) associated with the user of the remote system.

CAUTION: Removing a Storage System credential that is currently used by Host Explorer,the RMVMware CLI, VASA provider, Remote Copy Pairing or the scheduler will prevent thesecomponents from operating normally.


4 Logging On and Working with Virtual VolumesThe HP 3PAR Management Plug-in for VMware vCenter is used for viewing virtual volume mapping.You can also create and expose virtual volumes to an ESX host based on a template where youfill in the details or based on the provisioning configuration of an existing Datastore. This chapterexplains how to log on to vSphere Client, view information about virtual volume mapping andTransparent Failover setup, and create new virtual volumes.

NOTE: HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSpheresupports Microsoft Internet Explorer as the Windows default browser.

NOTE: When configured with secure access to the vCenter Server, the Security Information "Thispage contains both secure and non-secure items” will be displayed.To enable the display of secure and non secure content:1. Click Start→Settings→Control Panel→Internet Options.2. On the Security tab, click Custom level→Miscellaneous.3. Enable the Display Mixed content option.4. Click OK.

Logging On to the vSphere ClientTo start the HP 3PAR Management Plug-in for VMware vCenter:1. Start the VMware vSphere Client on your desktop.

The VMware vSphere Client login screen appears (Figure 32 (page 53)).

Figure 32 Logging On to the vSphere Client

Logging On to the vSphere Client 53

2. Log on to the vSphere Client.a. Enter the IP address or name vCenter Server.b. Enter your user name and password.c. Click Login.The vCenter Server home page appears (Figure 33 (page 54)).

Figure 33 Virtual Center Home Page

3. Under Solutions and Applications, click HP 3PAR Management Plug-in and Recovery Managerfor VMware vSphere.A list of storage systems associated with the ESX(i) host displays on the left side.

Figure 34 HP 3PAR Management Plug-in

To update the entire Storage System list, right-click the HP 3PAR Storage System root-entry andselect the Refresh in the popup menu option.

54 Logging On and Working with Virtual Volumes

To manually add a storage system entry that is not on the list, right-click the HP 3PAR StorageSystem and select connect. The HP Storage System connection screen appears requesting thelogin details.

Figure 35 HP 3PAR Storage System Connection Screen

4. To connect to a specific storage system on the list, expand the list tree and click the desiredsystem to connect or right-click the desired entry to show the popup menu and select Login.

5. Enter the appropriate information In the connect dialog box:a. Enter the HP 3PAR StoreServ Storage system name or IP address.b. Enter the Storage System user name and password.c. Select the Remember Me check box to prevent having to log on each time you access

this system.6. Click Login.

The Summary tab shows detailed information about the selected system including the following:

Figure 36 Storage System Summary

Logging On to the vSphere Client 55

Table 6 Storage System Information Summary

ValueGeneral

Name of storage systemSystem name:

Model of storage systemSystem model:

Storage system serial numberSerial number:

Storage system ID numberSystem ID:

World Wide Name of storage systemSystem WWN:

Number of nodes available in storage systemNumber of nodes:

Nodes appearing onlineNodes online:

Login userLogged on as:

NOTE: You can login to a different Storage System credential by right-clicking the specificStorage System and select Logout. Logging out does not remove the cached credential forauto login. Refer “User Authentication” (page 14) for more information.

Figure 37 Logging In a Storage System

Viewing Virtual Volume MappingWhen logged in, you can view virtual volumes on the vCenter Server Virtual Machines (VMs) orDatastores.

NOTE: You can also view virtual volumes at the datacenter, cluster, and ESX host level. See “HP3PAR Views in the vSphere Client” (page 16) for details.

1. In the main menu navigation, click Home.2. Under Inventory, click VMs and Templates or Datastores (Figure 38 (page 57)).


Figure 38 Home Page

3. From the navigation tree, click the specific VM or Datastore volume to view.4. Click the HP 3PAR tab.

The information for all virtual volumes on the selected VM or Datastore is displayed.

Figure 39 Virtual Volume Mapping

Viewing Volume InformationAfter selecting a VM or Datastore, by default, all volumes on that VM or Datastore are displayedin the Virtual Volumes tab (as shown in Figure 40 (page 58)).

Viewing Virtual Volume Mapping 57

The virtual volume information is divided into an upper and lower pane in the detail pane of theinterface.

• The upper pane displays general volume information.

• The lower pane provides the following details of Virtual Volumes (default view), Paths, andAlerts.

The Upper PaneThe upper pane of the Virtual Volumes tab is displayed as shown in Figure 40 (page 58). RMVdetects whether or not there are multiple paths with different storage system serial numbers. Theplug-in displays the VM, Datastore, or Remote Copy groups using a Transparent Failover setup asactive or standby under the Storage System column.

Figure 40 Viewing the Upper Pane of the Virtual Volumes Tab

The following filtering and sorting capabilities are provided:

• To filter, click the upper right corner of the column header. The virtual volume details in thelower pane of the filtered virtual volumes are displayed. Click Clear Filter to clear the selectedfilter.

Figure 41 Filtering Virtual Volumes


NOTE: The filter operation details panel may display incorrect volume details. To update thedetails, select a volume from the grid to remove incorrect details.You must provide both values for the filtering range.Filters are applied to the set of volumes currently displayed in the grid. If you do multiple filteringoperations make sure that you clear the unwanted filter(s) before a new filter is applied. Otherwisenew filter will be applied to the previously filtered result set.

• To sort, drag a column header to group by that column. Click the selected upper right cornerof the column header to resume the default view.

Figure 42 Sorting Virtual Volumes

Viewing Virtual Volume Mapping 59

The Lower PaneThe lower pane of the Virtual Volumes tab displays information about the selected volume in theupper pane. The lower pane provides three buttons, Details, Paths, and Alerts.

• Details (default when viewing the Virtual Volumes tab) displays details about the selectedvolume in the upper pane (Figure 43 (page 60)). In addition, all the storage systems and theirpaths are also displayed. When Transparent Failover is enabled, the Virtual Volumes Detailspane label changes to Virtual Volume Details for Active Storage System. Depending on thesystem configuration, the pane provides a status of Transparent Failover setup between anactive and standby storage system. In the event of an active system failing, the host trafficdirecting to the failed or active storage system is redirected to the standby storage systemwithout any disruption to the hosts using SCSI path management configurations.

Figure 43 Viewing Virtual Volume Details

• Paths displays path information about the selected volume (Figure 44 (page 60)).

Figure 44 Viewing the Volume Paths

• Alerts displays any alerts associated with the selected volume (Figure 45 (page 60)).

Figure 45 Viewing the Alerts

Refreshing Virtual Volume InformationA Refresh button is provided to update virtual volume information displayed in the HP 3PARManagement Plug-in and Recovery Manager Software for VMware vSphere interface. The Refreshbutton provides two options, Reload Current Page and Update Recovery Manager Cache.

• Select Reload Current Page if you have logged into an HP 3PAR StoreServ Storage systemand the pages do not show volume details.

• Select Update Recovery Manager Cache if you have logged into an HP 3PAR StoreServ Storagesystem and the vCenter Server inventory has changed; such as newly added Virtual Machinesor Datastores, changed HBA path policies, or added ESX hosts.


Creating Virtual Volumes and DatastoresYou have the option of creating a new virtual volume on the HP 3PAR StoreServ Storage systemand have it exported to the vCenter managed ESX/ESX(i) host where it can be accessed.

Creating a Virtual Volume from an Existing HP 3PAR System TemplateFollow these steps to create a new virtual volume:1. In the main menu navigation, click Home→Inventory→Host and Clusters.2. Go to the HP 3PAR→Virtual Volumes.3. Click Provision New. The Provision Storage welcome screen appears with information

concerning the provisioning process.

Figure 46 Provisioning a New Virtual Volume

NOTE: To prevent the welcome screen from displaying in the future, select the “Skip thispage in the future when provisioning storage” check box.

4. Click Next to select a storage system template to be used for provisioning.

Figure 47 Provision Storage Template Selection

NOTE: Only templates configured with at least TPVV or CPVV type, size, and user CPGfrom Storage Systems associated with the selected ESX(i) host are displayed.

5. Select an appropriate template from the list based on the summary of details, then click Next.

Creating Virtual Volumes and Datastores 61

Figure 48 Virtual Volume Provisioning Parameters

6. Provide the virtual volume parameters for the virtual volume being provisioned. An option isavailable to attach to a Virtual Machine when you want to create a raw disk only. Fill in thefollowing parameters and click Next when done.

• Number of virtual volumes: - Number of virtual volumes to create (1 – 99). The defaultis 1.

• Virtual Volume name - Name for the virtual volume (1 – 31 characters for single volumecreations or 1– 26 characters for multiple volume creations). If the number of virtualvolumes to be created is set to 1, the specified name is sufficient for creating the virtualvolume. When creating multiple virtual volumes, a decimal number is automaticallyappended to the name prefix for each virtual volume that is created up to the maximumlimit (.0 - .9999).

NOTE: When choosing a name for creating virtual volumes, you must consider thefollowing:

◦ If the number of virtual volume count = 1, the virtual volume name is set to 31 andthe Datastore name is set to 42.

◦ If number of the virtual volume count > 1, the virtual volume name prefix is set to 26and the Datastore name prefix is set to 31.

• Create Datastore - Name for the Datastore (1– 42 characters for single Datastore creationsor 1– 31 characters for multiple Datastore creations). If the number of virtual volumes tobe created is set to 1, the specified name is sufficient for creating the Datastore. Whencreating multiple Datastores, a decimal number is automatically appended to the nameprefix for each Datastore that is created up to the maximum limit (.0 - .9999999).

NOTE: If the specified Datastore name already exists regardless of its name case, theoperation will not be successful. The behavior is similar to vCenter Datastore creation.


Figure 49 Datastore Parameters Review

• VMFS-5/VMFS-3 option and Block Size - Specifies whether to use VMFS or VMFS-3. Youcan optionally specify the block size. VMFS-5 is only valid for ESXi 5.0 or above hosts.

• Size (512 MB – 16 TB) - Size for the virtual volume. For VMFS-3, the VV size range is 512MB to 2 TB, For VMFS-5, the VV size range is from 512 MB to 16 TB.When specifying the size for a virtual volume, 256 MB is reserved for each node.Depending on the cluster type, the minimum virtual volume size is calculated as 256 MBtimes the number of nodes.In a two node system, 512 MB is reserved when a TPVV is created. If an 80% user limitis set for a 512 MB TPVV, only 410 MB of space can be allocated. However 512 MBis the least amount required so the creation of the virtual volume fails. In other words, Ifthe allocation limit is set, the space after the % needs to be at least 512 MB in a 2 nodecluster.VV growth increment is 256 MB (i.e., If 520 MB is selected for a virtual volume, a VVsize of 768 MB is automatically created.

• Create raw disk only - Creates a raw disk when checked. By default, this option is notchecked and a Datastore is automatically created. You can attach the disk to a VirtualMachine and choose either Physical or Virtual compatibility mode.


After you click Next and review the summary before initiating the provisioning operation.

Figure 50 Raw Disk Parameters Review

7. Review the parameters, then click Create. Click OK for each confirmation. A confirmation iseventually shown indicating that the Datastores have been created.

NOTE: If you choose “ESX Cluster”, the storage is assigned to the ESX Cluster hosts. Otherwise,the storage is only created on the selected host.

NOTE: If the selected ESX(i) host is connected to a storage system and currently does not haveLUNs exposed to the host, you need to log in to the summary page and create an entry for thestorage system. For more information, refer to “HP 3PAR StoreServ Storage System Login” (page15).


Creating a Virtual Volume from Existing DatastoresFollow these steps to create a virtual volume from an existing Datastore:1. In the main menu navigation, click Home→Inventory→Datastores and Datastore Clusters.2. Go to HP 3PAR→Virtual Volumes.3. Click Provision Similar. The Welcome page appears.

NOTE: To prevent the welcome page from displaying in the future, select the “Skip this pagein the future when provisioning storage” check box.

Figure 51 HP 3PAR Virtual Volume Entries

4. Click Next to enter the virtual volume parameters.5. Enter the appropriate parameters, then click Next.

• Number of Virtual Volumes - Number of virtual volumes to be provisioned. You can specifyfrom 1 to 99 where 1 is the default.

• Virtual Volume name - Name for the virtual volume.

NOTE: When choosing a name for creating virtual volumes, you must consider thefollowing:

◦ If the number of virtual volume count equals 1, the virtual volume name is set to 31and the Datastore name is set to 42.

◦ If number of the virtual volume count is greater than 1, the virtual volume name prefixis set to 26 and the Datastore name prefix is set to 31.

Figure 52 Virtual Volume Parameters


• Create Datastore - Create a Datastore.

Figure 53 Create Datastore Parameters

• Create raw disk only - Create a raw disk only. This parameter also allow you to attachthe Virtual Volume to a Virtual Machine and choose either Physical or Virtual compatibilitymode.

Figure 54 Create Raw Disk Only Parameters

After you click Next, a summary of the Datastore to be created is shown:

Figure 55 Virtual Volume Parameter Review


6. Review the parameters, then click Create. Click OK for each confirmation. A confirmation isshown to indicate the Datastores are created successfully.

NOTE: When creating virtual volumes from an existing Datastore, the volume allocationlimit of the original virtual volume is also be applied to the newly created volume. Currentoperation only supports TPVV or CPVV type.

Adding an ESX(i) Host to the vCenter ServerIf an ESX(i) host with connection to HP 3PAR StoreServ Storage system is added to the vCenterServer after vSphere client is launched and the storage system does not appear on the existing HP3PAR StoreServ Storage system list, you can manually add the host.To add an ESX(i) host to the vCenter Server:1. Log on to vSphere client.2. Go to Home→Solutions and Applications→HP 3PAR Management Plug-in and Recovery

Manager Software for VMware vSphere.3. Select the storage system on the node tree pane view and right-click. Select Connect from the

option menu.4. Enter the information of the storage system and click Login.5. Verify the new storage system is added to the node tree pane.6. Go to Home→Inventory→Hosts and Clusters→HP 3PAR.7. Click Refresh, select Update Recovery Manager Cache option and click Refresh. All associated

HP 3PAR StoreServ Storage system virtual volume information should display.

NOTE: Another way to refresh the internal inventory cache, close and reopen the vSphereclient.

Adding an ESX(i) Host to the vCenter Server 67

5Working with Virtual CopiesThis chapter explains how to use HP 3PAR Recovery Manager Software for VMware vSphere tomanage Virtual Copies.

NOTE: In the following sections, the type of Virtual Copy being created, mounted, or modifiedis dependent on whether a VM or Datastore is selected from the navigation tree. For example, ifyou have selected a Datastore from the navigation tree, subsequent create, mount, or modifyactions performed will affect the selected Datastore until a different Datastore or VM is selected.

NOTE: The ability to manage Virtual Copies provided by HP 3PAR Recovery Manager Softwarefor VMware vSphere requires the HP 3PAR Recovery Manager Software for VMware vSphere andVirtual Copy licenses.

NOTE: To add an ESX/ESX(i) host to the vCenter Server, refer to “Adding an ESX(i) Host to thevCenter Server” (page 67).

Viewing Virtual Copy InformationIn addition to viewing virtual volumes on the vCenter Server’s Virtual Machines (VMs) and Datastoreswhen logged in, you can also view Virtual Copies.To view a VM or Datastore Virtual Copies:1. Start the HP 3PAR Management Plug-in for VMware vCenter as described in “Logging On to

the vSphere Client” (page 53).2. Follow the instructions in “Viewing Virtual Volume Mapping” (page 56).

68 Working with Virtual Copies

3. Click the Virtual Copies tab.Information about the selected VM or Datastore Virtual Copies is displayed.

• Base Datastore/RDM LUN

• Type

• Base Volume

• Base ID

• Virtual Copy Volume

• Virtual Copy ID

• Status – Can be Available, Mounted, Missing or Mismatched.

NOTE: When a Virtual Copy set is displayed as Missing, the Virtual Copy has beendeleted from the storage system. The delete operation is only allowed to remove theVirtual Copy.When a Virtual Copy set is displayed as Mismatched, the Virtual Copy is created on adifferent storage system instead of its current connected system. The mismatch may becaused by an HP 3PAR Peer Motion operation. The delete operation is only allowed toremove the record. Manually remove the actual Virtual Copy from the originating storagesystem.

• Retention

• Expiry

• Exported Host

• LUN ID

• ESX Host

• Virtual Copy Datastore

NOTE: The Virtual Copy timestamp displayed on the Virtual Copies tab is converted to thelocal time zone of the vSphere Client. The Expiry and Retention values on the same displayare set to the time zone of the RMV server.

NOTE: If the VV(s) used are in a Transparent Failover configuration, local Virtual Copieswill be disabled. Remote Virtual Copies may be created in the Remote Copy tab. RemoteVirtual Copies will create local and remote virtual copies so when failover occurs, a remotevirtual copy (either local or remote) will exist for recovery purposes.

Viewing Virtual Disk Details for Virtual CopiesYou can view details on the virtual disk associated with a Virtual Copy.

• Virtual Disk – Shows the virtual disk name.

• Original Virtual Machine Name – Provides additional information on the Virtual Machinename associated with the VMDK. Snapshots created prior to version 2.3 will have this fieldas N/A.

• Application Consistent – Provides information on whether this VMDK is application consistent.

• VM Attached – Shows whether the VM is attached.

Viewing Virtual Copy Information 69

Viewing Virtual Copy Event LogsVirtual Copy operation event logs can be found at the vCenter Server level in the navigation tree,the Tasks & Events tab, and the Events tab. Use the keyword HP 3PAR to select all events performedby HP 3PAR Recovery Manager Software for VMware vSphere.

Figure 56 Viewing the Virtual Copy Event Log

Creating New Virtual CopiesPrior to creating a Virtual Copies, the following restrictions should be noted:

• Creating a Virtual Copy at the VM level requires available space on the Datastore where theVMDK file resides.

• Datastore creation from NFS drives is not supported from Virtual Copy operations.

• Recovery Manager for VMware vSphere requires VMFS snapshots. However, taking a VMFSsnapshot of a VM participating in disk sharing, such as Microsoft MSCS, is not supported(this is a VMFS limitation).

• The following steps only applies to Virtual Volumes that are not Transparent Failover enabled.If Transparent Failover is enabled, use the Remote Copy page to create new Virtual Copies.See “Creating Remote Virtual Copies” (page 93).

NOTE: Virtual Copy space must be available on the HP 3PAR Virtual Volume. In order to createa Virtual Copy on an HP 3PAR base volume, the volume itself must have had Virtual Copy spaceallocated during its creation.

To create a new Virtual Copy on the VM or Datastore, perform the following:1. Follow the instructions in “Viewing Virtual Copy Information” (page 68).2. Click the Virtual Copies tab.3. Click Create. You are then asked to supply the name for the Virtual Copy set.

NOTE: If you do not wish to name the Virtual Copy set, click OK. The created Virtual Copyis identified by a date and time stamp.


4. (Optional) You can either accept the default name based on the time when the Virtual Copyis created, or you can enter a name of your choosing. The Virtual Copy name cannot exceed32 characters.

5. When creating the Virtual Copy, you have the choice of changing the Ensure ApplicationConsistency option (set by default) to specify whether or not the newly created Virtual Copyshould adhere to the data standards used by supported application. Selecting this optionensures the data can be accessed with VM tools supporting these formats but may increasethe amount of data space and time required to create and access the Virtual Copy.

Figure 57 Ensure Application Consistency Option

NOTE: Application consistency is not supported on Exchange Databases that have beenconfigured using Physical Compatibility RDM LUNs. Application consistency is supported forDatastore Virtual Copy creation and you have the option to select a VM to reside on theDatastore.

6. Click OK. The Virtual Copy creation task is submitted and started.Information regarding the Virtual Copy creation process is shown under Recent Tasks in lowerportion of the screen. Once the Virtual Copy has been created, an entry is reflected in theVirtual Copy Set list.

NOTE: When working with Virtual Copies, you may need to refresh the display in order toview the most accurate volume details. See “Refreshing Virtual Volume Information” (page 60).

NOTE: If the Virtual Copy operation fails, refer to the event log to review details. See “ViewingVirtual Copy Event Logs” (page 70).

Mounting Virtual CopiesTo mount a Virtual Copy:1. Follow the instructions in “Viewing Virtual Copy Information” (page 68).2. Click the Virtual Copies tab.

Mounting Virtual Copies 71

3. Select the Virtual Copy to mount from the Virtual Copy Set list.4. Right-click the Virtual Copy in the Virtual Copy table.

A menu appears providing two mount choices:

• Mount on ESX host as Datastore on - Select from a list of ESX/ESX(i) hosts managed bythe vCenter Server that share access to the HP 3PAR StoreServ Storage system.

• Mount on Proxy Host - Select from a list of hosts not managed by the vCenter Server, butwhich have access to the HP 3PAR StoreServ Storage system.

NOTE: For ESX 3.5, the LVM.EnableResignature parameter must be set to 1 to allow mountoperations. The parameter can be found in the ESX host Configuration, Advanced Settings,and LVM options.

5. Click the mount type and then select an ESX host or Proxy Host from the menu that appears.The Confirm dialog box appears.

6. Click OK.The Virtual Copy mount task is submitted and a message indicates that the request is beingprocessed.You can check the status column to see that the Virtual Copy has been mounted.

Unmounting Virtual CopiesNOTE: Recovery Manager for VMware vSphere does not check if the volume being unmountedis in use. Ensure that the volume is inactive prior to unmounting.

To unmount a previously mounted Virtual Copy:1. Follow the instructions in “Viewing Virtual Copy Information” (page 68).2. Click the Virtual Copies tab.3. Select the Virtual Copy you wish to unmount from the Virtual Copy Set list.4. Right-click the mounted Virtual Copy in the Virtual Copy table.5. Click Unmount and then select the host.

The Confirm dialog box appears.6. Click OK. A message indicates that the request is being processed and the mounted copy is

unmounted.

Restoring Datastores by Promoting a Virtual CopyNormal restore scenarios involve restoring virtual disk images. In a VMFS Datastore, there can bemany virtual disks. Typically, you can identify the virtual disk to be restored and copy it over theold one. However, in some cases the virtual machine file system may be corrupted and all virtualdisks need to be replaced. In such scenarios, promote one of the Virtual Copies to a base volume.The HP 3PAR Operating System Software supports a non-disruptive Virtual Volume conversion froma fully to thinly-provisioned or thinly to fully-provisioned Virtual Volume. Recovery Manager forVMware limits the promotion of a Virtual Copy taken before a Virtual Volume conversion. A popupmessage box with error message displays if the action occurs. Performing any RMV Virtual Copyoperations such as creating or deleting must only occur after a Virtual Volume conversion iscompleted.

NOTE: After a Virtual Volume conversion is complete, also update the Recovery Manager Cacheto see changes if you are already logged on to the session. The RMV server does not notify theRMV plug-in for backend data changes.


NOTE: If the underlying HP 3PAR volume used by the Datastore belongs to an HP 3PAR RemoteCopy volume group, stop the Remote Copy volume group prior to running the Datastore promoteoperation.

To restore a Datastore by promoting a Virtual Copy:1. Follow the instructions in “Viewing Virtual Copy Information” (page 68). Make sure that you

are in the Datastores view as you can only promote Datastores.2. Click the Virtual Copies tab.3. Select the Virtual Copy that you wish to promote from the Virtual Copy Set list.4. Click Promote.

The Confirm dialog box appears.5. Click OK.

The Virtual Copy promote task is submitted and a message is displayed indicating that requestis being processed.

Restoring Datastores by Promoting a Virtual Copy 73

Deleting Virtual CopiesTo delete a Virtual Copy:1. Follow the instructions in “Viewing Virtual Copy Information” (page 68).2. Click the Virtual Copies tab.3. Select the Virtual Copy you wish to delete from the Virtual Copy Set list.4. Click Delete.

The Confirm dialog box appears.5. Click OK.

The Virtual Copy deletion task is submitted and started and you are asked to confirm yourintent to delete the Virtual Copy.The Virtual Copy is then removed from the Virtual Copy Set list.

Modifying Virtual Copy PoliciesThe Virtual Copy policies can be defined for a given Virtual Machine or Datastore.

NOTE: This version of RMV supports virtual copy policies for remote copy groups. The primarypolicy is enforced on both storage systems for primary and secondary sites.

To modify the policy of a Virtual Copy:1. Follow the instructions in “Viewing Virtual Copy Information” (page 68).2. Select the Virtual Machine or Datastore to apply a set of policies.3. Click the Virtual Copies tab.4. Click Policy.

The policy dialog appears.a. Select the maximum number of Virtual Copy sets. Based on the order in which they are

created, non-expirable Virtual Copies are deleted when they reach a position in the queuethat exceeds this count.

b. (Optional) Select whether to enable expirable Virtual Copies. Expirable copies areremoved according to a specified schedule and are not affected by the maximum count.When enabling the expirable Virtual Copies option, you must specify the length of time(Hours or Days) from the current time that the Virtual Copies are to expire. You can setthe expiry period up to 1825 days.

NOTE: Expirable Virtual Copies are not included in the maximum count.

When enabling expirable Virtual Copies, you also have the choice of specifying howexisting non-expirable copies are handled.

• Delete the oldest when count reaches maximum. This is the recommended setting.Select this option if you plan to create both expirable and non-expirable VirtualCopies. All non-expirable copies (new and existing) will be counted against themaximum count with the oldest being deleted as it exceeds the maximum count. TheRMVMware CLI and Scheduler have the option of overwriting the default policy.However, Virtual Copies created using the GUI interface are bound by the defaultpolicy.

• Phase out non-expirable Virtual Copies (Advanced).Select this option if you plan to mostly create expirable Virtual Copies and want toeventually phase out older non-expirable Virtual Copies. In this case, whenever anewer expirable Virtual Copy is created, the oldest non-expirable copy will be


deleted. You can still create non-expirable Virtual Copies, as long as the aggregatecount is below the policy maximum.

NOTE: If all non-expirable Virtual Copies are in valid retention and have alreadyreached the maximum count, choosing the Enable expirable Virtual Copies option withthe Phase out non-expirable Virtual Copies setting will fail. If this happens, choose theDelete the oldest when count reaches maximum option instead.

c. (Optional) Select a period of time to retain Virtual Copy sets.A dialog box prompts you for the number of days to retain the Virtual Copy set.i. Select the Retention Period.ii. Select Hours or Days.

NOTE: Setting the retention policy requires the HP 3PAR Virtual Lock license onthe HP 3PAR StoreServ Storage system. RMV will check for an existing HP 3PARVirtual Lock license on the storage system when a Virtual Copy is created withretention is specified.

NOTE: The Virtual Copy set can be retained for up to 43,800 hours or 1,825days.

NOTE: When using both the expiry and retention options, the expiry value mustbe equal to or greater than the retention value.

d. Select whether to ensure application consistency. This option is used to create snapshotsof Virtual Copy sets that adhere to data format standards used by the VMware Tools.

NOTE: If new VMs are added to a Datastore, you also need to update the policy inorder to make the VM application consistent.

NOTE: When installing or upgrading VMware tools, you must be sure to reboot VMwareon the system where it running otherwise application consistent snapshots may not bevalid even though they are reported as completed successfully. This situation can alsooccur when the VMware tools have not been upgraded on the VM system following anupgrade of the ESX server.

5. Click Save.The Virtual Copy policy modification task is submitted and started. An alert appears indicatingthat the new policy has been saved.

6. Click OK.

Scheduling Virtual CopiesYou can automatically create Virtual Copies according to a specified schedule.To view or create a scheduled Virtual Copy task:1. Follow the instructions in “Viewing Virtual Copy Information” (page 68).2. Click the Virtual Copies tab.

Scheduling Virtual Copies 75

3. Click Scheduler. The Schedule List dialog Figure 58 (page 76) appears.

Figure 58 Schedule List Dialog

From the Scheduled List dialog, you can add a scheduled Virtual Copy creation task or modifyan existing one using the Schedule Task Wizard.To add a new scheduled Virtual Copy task, follow these steps:

1. Click Add.The Select Schedule Type dialog appears.

Figure 59 Select Schedule Type Dialog

2. Select the time when the scheduled copy creation task is to be performed. You have the optionof scheduling when (hourly, daily, weekly, monthly) the Virtual Copy is to be created. Youcan also schedule a Virtual Copy creation task to occur on a one-time basis.


3. Click Next. The wizard will request the appropriate information based on the option timeframe you have chosen. As an example that shows the types of information you need to supply,if you choose Weekly, the Weekly Schedule Task dialog appears.

Figure 60 Weekly Schedule Task

4. Enter the start time of the day when the task is to be run and then indicate how often the taskis performed in weeks. You also need to select the day(s) of the week when the task is to berun.

NOTE: If the vCenter server and RMV server are in different time zones, the default dateand time are based on the RMV server and vCenter server respectively. You need to synchronizethe time differences when creating the schedule.

5. Click Next.The Schedule Credential dialog appears.

Figure 61 Schedule Credential

6. Enter a name for the scheduled task and the associated user name and password. The taskname must be unique.


7. Click Next.The Snapshot Configuration dialog appears.

Figure 62 Virtual Copy Configuration Dialog

8. Enter the appropriate vCenter server user name and location of the credential store file.9. Specify whether or not to use application consistency for the scheduled task.

If application consistency is specified when creating the Virtual Copy for a Datastore, youhave the option of applying the application consistency to all Virtual Machines by selectingthe Apply to all Virtual Machines button or specify specific machines by choosing Apply tothe following Virtual Machines and enter the name of the Virtual Machines.

NOTE: Use commas to separate the Virtual Machine names.

10. Enter the HP 3PAR StoreServ Storage system user name.11. Specify any default policy overrides.

a. Specify the amount of time (in hours or days) before the Virtual Copy expires.b. Specify the amount of time (in hours or days) to retain the Virtual Copy set.

12. Click Next. The Schedule Task Summary dialog appears.


Figure 63 Schedule Task Summary Dialog

If application consistency was specified when the Virtual Copy was created, the summaryincludes this information as shown.

NOTE: To schedule a task for a given user, an associated vCenter Credential Store File mustfirst be created using the RMVMware CLI with vCenterRegister option. To be used withthe Scheduler, the credential file must have “System” account level privileges. In addition, toschedule tasks for user’s other than yourself, you must be added as a user to have permissionto access their credential files.If the credential file is created as a domain user, specify the domain user when setting up theschedule. If a local user is to be used for the scheduler, add the local user permission to thecredential file.

NOTE: Tasks scheduled for a given HP 3PAR StoreServ Storage system must have anassociated Storage System Credential registration completed using the RMVMware AdminTool. In addition, since the Storage System credential registration is only accessible by thecreation owner and a member of administrators, the user account must have access to theStorage System registration data.


13. Click Finish to complete the scheduling of the Virtual Copy task.A message indicates whether the task has been created successfully. A listing for the scheduledtask is now shown in the Schedule List.

Figure 64 Schedule List with Task

NOTE: If a VM or Datastore is removed, the associated scheduled tasks continues to run butis no longer manageable from the HP 3PAR Management Plug-in and Recovery ManagerSoftware for VMware vSphere scheduling interface. In this case, the task needs to be manuallyremoved from the Windows Scheduler.

NOTE: If the username associated with the user that created a scheduled task changes, thedefined task is no longer operational.

NOTE: To be used in the scheduler, users must have the proper credentials created throughthe vCenter Credential Store File using RMVMware CLI with the vCenterRegister optionand have a valid Storage System Credential registration established through the Admin Tool.

NOTE: Since Storage System credential registration is only accessible by the creation ownerand members of Administrator, user accounts used in the scheduler have to have access tothe registration data.

NOTE: Any user account that is used in the scheduler requires access permission to thespecified vCenter Store file.

Restoring Virtual Disks and Guest OS Files and DirectoriesThe basic restore functionality provided in HP 3PAR Recovery Manager Software for VMwarevSphere is the ability to mount all, or some, Virtual Copy volumes on one or more ESX/ESX(i) hosts.You can perform an actual restore by copying virtual disk images, or by mounting virtual disks onVMs for guest OS level restore, by using already available VMware tools, most of which areintegrated with the VI Client. However, Recovery Manager for VMware vSphere also provides twocommands to simplify some of the commonly used restore user cases.

Restoring a Virtual DiskAfter a Datastore Virtual Copy has been mounted on an ESX/ESX(i) host (see “Mounting VirtualCopies” (page 71), the virtual disks grid displays the context menu.

NOTE: When copying or cloning a Virtual Machine (VM) to a different Datastore, the sourceVM’s Universally Unique Identifier (UUID) is retained in the target VM. When using HP 3PARManagement Plug-in and Recovery Manager Software for VMware vSphere to show the VirtualCopies on the target VM, the Virtual Copies from the source VM will be displayed. To resolve thisproblem, the target VM’s UUID should be changed. Refer to VMware documentation on how toedit the VM’s UUID.


1. Right-click the virtual disk you wish to copy to a Datastore and click Copy to Datastore.

NOTE: When using the Copy to Datastore option to copy a virtual disk to a Datastore, it isrecommended that the copy and paste functions of the Datastore browser be used in order topreserve the VMware Thin Provisioning disk feature.

2. Select a Datastore on the ESX host where the Virtual Copy is mounted.3. Specify the target location and click OK.

Figure 65 Specifying the Target Location

The copying operation is initiated.

Figure 66 Initiating the Copy Operation

Restoring a Guest OS File or Directory from a Virtual CopyThe second context menu command available in virtual disks grid allows you to attach a virtualdisk available on the selected Virtual Copy to any of the VMs currently running on the ESX/ESX(i)host where the Virtual Copy is mounted.1. Right-click the virtual disk you wish to attach and click Mount on Virtual Machine.2. Select a VM on the ESX/ESX(i) host where the Virtual Copy is mounted.3. When prompted for confirmation, click OK.4. Once the task is completed, verify that the selected VM appears under the VM Attached

column.The remainder of the restore operation must be performed on the VM. This involves re-scanningfor new disks and mounting the file system, and then manually copying the files.Once the restore is complete, the virtual disk can be unmounted from the VM.

5. Right-click the virtual disk to be unmounted and click Unmount from Virtual Machine <VMname>.

Restoring Virtual Disks and Guest OS Files and Directories 81

6. When prompted for confirmation, click OK.The unmount commences.Virtual disks created using HP 3PAR Virtual Copy can be mounted on any VM. However, ifyou try to mount the Virtual Copy virtual disk on the same VM, the VI client displays a promptedquestion message.In this case, you can choose whether to continue or not.


6Working with Host ExplorerThe Host Explorer collects the following information and sends it to the Storage System:

• ESX/ESX(i) host operating system and version.

• Fibre Channel and iSCSI HBA details.

• Multi-path driver and current multi-path configuration.

• Device and path Information.Use showhost –agent , showhost –agent -d and showhost –pathsum on the HP 3PARStoreServ Storage system to get information sent by Host Explorer.

root@enodec1ce:S159# showhost -agentId Name ReportedName OS Arch OS_Ver OS_Patch IP Multipath MPVer ClusterSW ClusterVer ClusterID ClusterName 2 per805-02 per805-02.3pardata.com VMware ESX Server5.0 vmnix-x86 5.0.0 419341 10.112.0.104 -- -- -- 5.0.0 -- PER-cluster 3 pe2950-10 pe2950-10.3pardata.com VMware ESX Server4.0 vmnix-x86 4.0.0 208167 10.112.1.76 -- -- -- -- -- -- 5 per805-05 per805-05.3pardata.com VMware ESX Server5.0 vmnix-x86 5.0.0 419341 10.112.1.144 -- -- -- -- -- -- 10 per805-01 per805-01.3pardata.com VMware ESX Server5.0 vmnix-x86 5.0.0 419341 10.112.0.103 -- -- -- 5.0.0 -- PER-cluster 16 pe2950-10-iscsi pe2950-10.3pardata.com VMware ESX Server4.0 vmnix-x86 4.0.0 208167 10.112.1.76 -- -- -- -- -- -- 18 pe2970-23-iscsi pe2970-23.3pardata.com VMware ESX Server4.0 vmnix-x86 4.1.0 260247 10.112.4.213 -- -- -- -- -- -- 21 pe2970-22 pe2970-22.3pardata.com VMware ESX Server4.0 vmnix-x86 4.1.0 260247 10.112.4.211 -- -- -- 4.1.0 -- ESX4-cluster23 pe2970-24 pe2970-24.3pardata.com VMware ESX Server4.0 vmnix-x86 4.1.0 260247 10.112.4.215 -- -- -- 4.1.0 -- ESX4-cluster

83

7Working with VASA ProviderThe communication between HP 3PAR VASA provider and vCenter server is a secure connectionbased on SSL certificate and Windows credential. Before VASA Provider can be registered byvCenter server, VASA provider requires that you extract the SMS certificate from vCenter serverand install it to the HP 3PAR Recovery Manager for VMware installed host to allow client certificatenegotiation in the Transport Layer. For instruction on how to extract and import the certificate,please refers to Chapter 3.4 Registering an SMS Certificate for the VASA Provider. After the SMScertificate has been installed, you can register the provider from the vCenter server by clicking onthe Storage Providers icon as shown below.

Figure 67 Registering the Provider

From the Storage Providers view, click the Add link to bring up the Add Vendor Provider dialog.

Figure 68 Add Vendor Provider Screen

84 Working with VASA Provider

Table 7 Add Vendor Provider Information Fields

ValueField Name

Any name to identify the VASA provider.Name

VASA Service Web URL. For example(https://<IPAddrOrHostName>:<VasaPort>/).

URL

Windows user name to Recovery Manager for VMwareinstalled host.

Login

Windows Password.Password

Once registration is successful, the provider status is available online.

NOTE: To register VASA Provider, the user must have the StorageViews Configure privilege.

VASA provider for HP 3PAR StoreServ Storage system supports the Storage Capabilities profileas defined by the VASA Specification.

• Provision type

• Virtual Volume type

• Drive type

• RAID type

• Whether or not the volume is in a Remote Copy groupThe name and description of all HP 3PAR storage capabilities can be viewed from the ManageStorage Capabilities pop-up from vCenter. To access the Manage Storage Capabilities window,start from Home and then click VM storage Profiles from the Management tab. Click ManageStorage Capabilities.

Figure 69 Manage Storage Capabilities Screen

The name of an HP 3PAR storage capability has five parts and each identifies the value of one ofthe volume attributes. The following table shows the volume attributes and possible values. (Pleaserefer to HP 3PAR documentation for details of these attributes)

85

Table 8 VASA Storage Capability Volume Attributes

Storage Capability Name SegmentValueVolume Attribute

FullFully ProvisionedProvisioning Type

ThinThin Provisioned

BaseBase VolumeVolume Type

VCpyVirtual Copy Volume

FCFibre Channel DriveDrive Type

NLNear Line Drive

SSDSolid State Drive

MxMixed Drive

R0RAID 0RAID Type

R1RAID 1

R5RAID 5

R6RAID 6

RCRemote Copy Volume is inRemotecopy

Remote Copy

NoRCVolume is not in Remotecopy

NOTE: Consult the appropriate VMware documentation for more details.

86 Working with VASA Provider

8Working with Remote CopyA Remote Copy feature is now available for you to create and manage both Synchronous orPeriodic Virtual Copies at the RC Group level. In addition, the Remote Copy feature provides aGUI interface and basic CLI command functionality to register, create, schedule, update and removeRemote Copy pairings.HP 3PAR Recovery Manager for VMware software supports VMware Transparent Failover betweenmultiple servers through synchronized Remote Copy. The existing Remote Copy disaster recoveryfunctionality compliments a transparent failover setup by including an automatic volume creationon the secondary array when a primary volume is added to a group. Both the primary andsecondary clusters provide a path to an ESX host virtual volume with the same world-wide-number.The primary Remote Copy group provides the active path while the secondary Remote Copy groupprovides a passive path to targeted virtual volume.When Virtual Volumes are using Transparent Failover, RMV blocks the local Virtual Volume creationfor Virtual Machines and Datastores while allowing the creation of remote Virtual Copies on RemoteCopy Groups. As a result, when an active path failovers to a different storage system, the virtualcopies become available on either storage systems for restoration.For more information about establishing Transparent Failover setup, refer to the HP 3PAR RemoteCopy User Guide.Use the Admin tool to register and configure Remote Copy Pairs before launching the vCenterplug-in feature to create a snapshot of your system.Ensure the following requirements are satisfied before registering a Remote Copy pair:

• Remote Copy configuration already exists on the storage systems. Use the HP 3PAR OS CLIor IMC GUI to create the Remote Copy configuration if they do not exists.

• Recovery Manager Software for VMware is already installed on the remote host situated ina remote site.

• Establish IP access to the remote host.

• You can configure the Remote Copy volume group for synchronization in one of the followingmodes:

◦ synchronous mode

◦ asynchronous periodic mode with replication period value set to zero

CAUTION: If you set the replication period value to zero, then the Remote Copyreplication is dependent on the RMV scheduler. So you must ensure that the RMV serviceis available all the time.

Registering Remote Copy Pairs1. Launch Recovery Manager Software for VMware vSphere Admin Tool and click the HP 3PAR

Management Plug-in and Recovery Manager Software for VMware vSphere AdminTool→vCenter Plug-in.

NOTE: If you have a single RMV server, HP recommends that you register the remote copypairs in both directions. If you are using two RMV servers, register each direction just onceon each RMV server.

2. Under the vCenter Plug-in tab, click Remote Copy Pairs tab.

Registering Remote Copy Pairs 87

Figure 70 Registering Remote Copy Pairs

3. Click Register New.

88 Working with Remote Copy

4. Enter the required information into the following fields for both Local and Remote systems.Click Register.

Figure 71 Specifying Remote Copy Pair Details

Table 9 Register Remote Copy Storage System Pair Fields

ValueLocal

Name of local storage systemStorage system:

Name of user for local storage systemStorage System username:

Name of user for Microsoft WindowsWindows user name:

ValueRemote

Name of remote storage systemStorage system:

Name of user for remote storage systemStorage system username:

Name of user for Microsoft WindowsWindows user name:

Name of remote Recovery Manager server on remote siteRecovery Manager server name:

TCP port number of remote Recovery Manager serviceRecovery Manager service TCP port:

When the registration is successful, the Plug-in displays HP 3PAR StoreServ Storage system pairingin the Remote Copy Pairs tab.

Registering Remote Copy Pairs 89

Updating Registered Remote Copy Pairs Information1. Launch Recovery Manager Software for VMware vSphere Admin Tool and click the HP 3PAR

Management Plug-in and Recovery Manager Software for VMware vSphere.2. Click Remote Copy Pairs tab.3. Select a Remote Copy pair from the list and click Update.4. Select the new system information from the Local and Remote drop-down menus. If applicable,

enter another RMV host name.5. Click Update.

Viewing Host Information SummaryFrom the vSphere Plug-in Storage System tree pane, select a storage system, and click the Summaryin the detail pane to view the information of the storage system.

NOTE: If Transparent Failover is enabled, the local Virtual Copies are disabled because VCsnapshots are taken both locally and remotely using Virtual Copy creation.

Figure 72 Storage System Summary

Table 10 Storage System Summary Information

ValueGeneral

Name of storage systemSystem name:

Model of storage systemSystem model:

Storage system serial numberSerial number:

Storage system ID numberSystem ID:

World Wide Name of storage systemSystem WWN:

Number of nodes available in storage systemNumber of nodes:

Nodes appearing onlineNodes online:

Login userLogged on as:


Viewing Existing and Newly Added Remote Copy InformationUse the vSphere Client to navigate and view registered storage system Remote Copy pairs andRemote Copy groups for local and remote systems.Launch vSphere Client, select Home at the top of navigation bar and click HP 3PAR ManagementPlug-in... From the HP 3PAR StoreServ Storage system tree pane, select a storage system and clickthe Remote Copy tab.

NOTE: HP recommends setting your screen resolution height to at least 1024 pixels to view allthe information. If some information cannot be seen, you can move the vertical split bar to the leftor hide the Recent Task panel at the bottom.

To view details of the Remote Copy Groups associated with specific storage systems, click thefollowing tabs:• Summary: The tab provides details of the Source and Target Remote Copy group name, role,

Transparent Failover status, mode and operating status, and link type.

Figure 73 Remote Copy Pair Summary

• Virtual Volumes/Machines: The tab lists the source Virtual Volumes and the correspondingtarget Virtual Volumes name along with Transparent Failover and Sync status in the RemoteCopy Group.A Transparent Failover column lists the Transparent Failover setup status of all Virtual Volumesassociated with the Remote Copy Groups for Source and Target storage systems.

Viewing Existing and Newly Added Remote Copy Information 91

Figure 74 Virtual Volumes/Machines

• Virtual Copies On: The tab displays remote Virtual Copies creation and expiration dates,retention, mode, and application consistent status. The Remote Virtual Copies Mapping displaysif you select a Remote Virtual Copy.

Figure 75 Remote Virtual Copies On

• Virtual Copies On: The tab displays the details of the Remote Copy group(s) associated withSource storage system and Remote Copy Group; Target Storage System and Remote CopyGroup; creation and expiration dates; and retention and application consistent status. The


Virtual Volume Mapping for Virtual Copy Timestamp displays the Status, Exported Host, LUNID, and Virtual Copy Datastore information if you select a Local Virtual Copy.You can also click the available hyperlink within the Virtual Copy table to Mount, Unmount,or Delete existing Virtual Copies of Virtual Volumes.

Figure 76 Local Virtual Copies On

Creating Remote Virtual CopiesYou can create either synchronous and periodic Remote Virtual Copy for Remote Copy groupsassociated with a specific ESX server. Other VMs from other ESX hosts are not shown. Whencreating synchronous Remote Virtual Copies, Recovery Manager creates a copy on both the localand remote array. For periodic Remote Virtual Copies, a Remote Virtual Copy is only created onthe remote array.1. Select the desired storage system in the left pane.2. Select the Remote Copy tab.

a. From the upper right window, select the Remote Copy pair.b. From the bottom right window, select the Remote Copy group.c. Click Create Remote Virtual Copy.

3. Select the desired options for the Remote Virtual Copy.• Enable expirable Virtual Copies

• Retain Virtual Copies

• Create remote Virtual Copy with application consistency

NOTE: If the Remote Virtual Copy for the Remote Copy group is set, the user will see themaximum number of Virtual Copies in Policy in the dialog box.

Creating Remote Virtual Copies 93

Figure 77 Create Remote Copy Virtual Copy

4. Click Create.5. Click Yes to confirm.6. Review the creation of the Virtual Copy in the Recent Tasks box at the bottom of the vSphere

client. Click OK to complete.

Setting Policy for Remote Virtual CopiesTo manage remote VCs, you can set specific expirable and retention policies for each Virtual Copysets. Any policies set on a local storage system are also be applied to the virtual copy on remotestorage system during creation time.

:When the number of Virtual Copies is at the maximum limit, the oldest Virtual Copy is deletedwhen a new Virtual Copy is created.

To set a policy for a Remote Virtual Copy:1. From the Remote Copy tab, click Remote Virtual Copy Creation Policy.2. Choose the maximum number of Virtual Copy sets. Use the arrows to adjust the number of

sets.


3. Check the applicable policy options:

• Enable expirable Virtual CopiesSpecify the expiration period. Click the appropriate option button relating to the handlingof existing non-expirable Virtual Copies.

• Retain Virtual Copy SetSpecify the expiration period.

Figure 78 Policy Dialog

4. Ensure application consistency.5. Click Save.

NOTE: After clicking Save, the process may take up to 15 minutes to complete dependingon the number Virtual Copy Sets specified.

Scheduling Remote Copy Virtual CopiesYou can schedule a Remote Copy creation task or the selected Remote Copy group systems.1. From the Remote Copy Summary tab, click Scheduler.2. Click Add.

Scheduling Remote Copy Virtual Copies 95

Figure 79 Adding Create Remote Copy Virtual Copy

3. Choose the scheduling options for performing Virtual Copy creation tasks. Set the parametersof the selected schedule option.• Hourly Start time, Hour

• Daily Start time, Day

• Weekly Start time, Week, Day of the Week

• Monthly Start time, Day of Every Month

• One time only Start Date, Start Time

Figure 80 Setting Scheduled Type for Performing Virtual Copy Creation Task

4. Click Next to continue.5. Enter the credentials to complete the scheduled tasks.

• Schedule task name

• User name

• Password


Figure 81 Entering Schedule Credential

6. Click Next to continue.7. Select the schedule task settings.

• vCenter server user

• vCenter credential store file

• Enable expirable Virtual Copies

• Retain Virtual Copies

• Create Remote Copy Virtual Copy with application consistency

Figure 82 Setting RC Virtual Copy Configuration

8. Click Next to continue.9. Review the Scheduled Task Summary before continuing.

Scheduling Remote Copy Virtual Copies 97

Figure 83 Reviewing Scheduled Task Summary

10. Click Finish to exit.

Mounting Remote Virtual Copies

Mount From Virtual Copy TableTo mount a Remote Virtual Copy:1. Click the Remote Copy tab.2. Choose the appropriate Remote Copy Group system.3. Click the Virtual Copies On tab to display the list of Remote Virtual Copies.4. Select the appropriate remote VC from the Remote VC Groups table.

NOTE: If the selected Remote VC has any unmounted VVs, the Mount above the VC tableis enabled.

NOTE: Only remote Virtual Copies existing on the current array selected can be mounted.To mount a remote Virtual Copy onto another array, select the specific array located in theleft pane.

5. Click the Mount.6. Choose a mounting option:

• Mount on ESX host as Datastore

• Mount on Proxy hostChoose a specific Proxy host.


Figure 84 Remote VC Mounting Options

7. Click Mount.8. Click Yes to confirm. Click No to cancel action.9. Click Ok to complete action.

Figure 85 Mount Local Virtual Copy Complete

Mount From Virtual Volume Mapping Table1. Click the Remote Copy tab.2. Choose the appropriate Remote Copy Group system.3. Click the Virtual Copies On tab to display the list of Remote Virtual Copy.4. Select the appropriate remote VC from the Virtual Volume Mapping table.

NOTE: If one or more selected Remote VC has any unmounted VVs, the Mount above theVV table is enabled.

5. Click the Mount.

Mounting Remote Virtual Copies 99

6. Choose a mounting option:• Mount on ESX host as Datastore

• Mount on Proxy hostChoose a specific Proxy host.

Figure 86 Remote VC Mounting Options

7. Click Mount.8. Click Yes to confirm. Click No to cancel action.9. Click OK to complete action.

Unmounting Remote Virtual Copies

Unmount From Virtual Copy TableTo unmount a Remote Virtual Copy:1. Click the Remote Copy tab.2. Choose the appropriate Remote Copy Group system.3. Click the Virtual Copies On tab to display the list of Remote Virtual Copy.4. Select the appropriate mounted remote VC from the Remote VC Groups table.

NOTE: If the selected Remote VC has any mounted VVs, the Unmount above the VC tableis enabled. You may select multiple VCs to unmount.

5. Click Unmount.

Unmount From Virtual Volume Mapping Table1. Click the Remote Copy tab.2. Choose the appropriate Remote Copy Group system.3. Click the Virtual Copies On tab to display the list of Remote Virtual Copy.4. Select the appropriate mounted remote VC from the Virtual Volume Mapping table.

NOTE: If the selected Remote VC has any mounted VVs, the Unmount above the VV tableis enabled. You may select multiple VCs to unmount.


5. Click the Unmount.

Deleting Remote Virtual CopiesWhen a remote RC Group Virtual Copy under the Remote Virtual Copies tab is no longer required,the tabs can be removed.1. Click Remote Virtual Copies tab.2. Select the specific remote Virtual Copy. To select multiple Remote Virtual Copies, press Ctrl

and click.3. Click Delete.

Deleting Local Virtual CopiesWhen a local RC Group Virtual Copy under the Local Virtual Copies tab is no longer required, thetabs can be removed.1. Click Local Virtual Copies tab.2. Select the specific local Virtual Copy. To select multiple Local Virtual Copies, press Ctrl and

click.3. Click Delete.

NOTE: Only unmounted Virtual Copies can be deleted.

Deleting Remote Virtual Copies 101

Importing a Virtual Machine and Reverting to a Specific Point-in-Time VirtualCopy

1. Issue setcopygroup failover to Failover the desired Remote Copy group from thesecondary site. Verify the Remote Copy group displays Primary-Rev.

2. (Optional) Select a desired Virtual Machine Virtual Copy and issue promotesv to theappropriate Virtual Volume(s) to revert.

NOTE: Issuing promotesv promotes the entire data of the virtual volume to a specificpoint-in-time Virtual Copy. HP recommends creating a Virtual Copy as a recovery point fromthe base volume before proceeding with the optional step.

3. Issue createvlun to expose the virtual volume to the ESX/ESX(i) host.4. Connect to the vCenter Server and issue Rescan for Datastores... command to scan

for LUN exposed to the ESX/ESX(i) host.5. Select the ESX/ESX(i) host from vCenter and click Configuration tab.6. From Hardware located in left pane, click Storage to retrieve Datastores view.7. From the Datastore browser, add the Virtual Machine to the vCenter Inventory.

a. Right-click the VMX file and select Add to Inventory.b. Continue to follow the wizard.

8. Right-click the newly imported Virtual Machine and select Snapshot\Snapshot Manager.

NOTE: If Step 2 is not performed and the Virtual Copy is not application consistent, continueon to Step 10.

9. From the Snapshot dialog, select the base Virtual Copy. Click Go to revert to the time theVirtual Copy is created.a. (Optional) When revert of snapshot is complete, click Delete All to remove all Virtual

Copies.b. Click Close.

10. Update the network setting for the Virtual Machine.11. Turn Virtual Machine power on. If you see a question mark, right-click the Virtual Machine

and select Guest\Answer Questions. Complete the questions to begin using the Virtual Machine.12. Answer the following promoted questions to begin using the VM.


9 Using HP 3PAR Peer Motion Manager Software withRecovery Manager

HP 3PAR Peer Motion Manager is a feature of the HP 3PAR Operating System Software andmanages the migration of data in between existing storage systems or third party storage arrays.HP 3PAR Recovery Manager now supports HP 3PAR Peer Motion Manager data migration activitieswithout any impact on host operations while monitoring the primary storage system.If the virtual volume is already in use by an ESX/ESX(i) host before initiating migration, the followingconditions applies:• You must remove any Virtual Copies created and managed by Recover Manager for VMware.

The Virtual Copies created by a potential migrating virtual volume cannot migrate with itsvirtual volume during an active Peer Motion migration operation.

• You must remove all Virtual Copy scheduler tasks associated with the Datastore or VirtualMachines using the potential migrating virtual volume before migrating data. If the tasks arenot removed and occurs during migration, the following error message may display duringor after the migration operation, "Could not create HP 3PAR snapshot. Object Id:vm:uuid-4208b1f5-e2ca-1061-c44c-19cf67bee619. Please login into Storage System 014DMethod: CliCreateNewSnapshot."

• Previously created Virtual Copies will display Mismatched status. You cannot use Virtual Copieswith Mismatched status for mounting or restoring operations.

• You must remove the mismatched Virtual Copies records from the interface. Note, this doesnot remove the physical Virtual Copies from the original storage system. You must perform amanual cleanup of the files.

For more information about performing Peer Motion data migration, refer to the HP 3PAR PeerMotion User Guide. Go to http://www.hp.com/go/3par/, navigate to your product page, clickSupport, and then click Manuals.

103


10 Support and Other ResourcesContacting HP

For worldwide technical support information, see the HP support website:http://www.hp.com/support

Before contacting HP, collect the following information:

• Product model names and numbers

• Technical support registration number (if applicable)

• Product serial numbers

• Error messages

• Operating system type and revision level

• Detailed questionsSpecify the type of support you are requesting:

Support requestHP 3PAR storage system

StoreServ 7000 StorageHP 3PAR StoreServ 7200, 7400, and 7450 Storagesystems

3PAR or 3PAR StorageHP 3PAR StoreServ 10000 Storage systemsHP 3PAR T-Class storage systemsHP 3PAR F-Class storage systems

HP 3PAR documentation

See:For information about:

The Single Point of Connectivity Knowledge for HPStorage Products (SPOCK) website:

Supported hardware and software platforms

http://www.hp.com/storage/spock

The HP 3PAR StoreServ Storage site:Locating HP 3PAR documentshttp://www.hp.com/go/3parTo access HP 3PAR documents, click the Support link foryour product.

HP 3PAR storage system software

HP 3PAR StoreServ Storage Concepts GuideStorage concepts and terminology

HP 3PAR Management Console User's GuideUsing the HP 3PAR Management Console (GUI) to configureand administer HP 3PAR storage systems

HP 3PAR Command Line Interface Administrator’sManual

Using the HP 3PAR CLI to configure and administer storagesystems

HP 3PAR Command Line Interface ReferenceCLI commands

HP 3PAR System Reporter Software User's GuideAnalyzing system performance

HP 3PAR Host Explorer User’s GuideInstalling and maintaining the Host Explorer agent in orderto manage host configuration and connectivity information

HP 3PAR CIM API Programming ReferenceCreating applications compliant with the Common InformationModel (CIM) to manage HP 3PAR storage systems

104 Support and Other Resources

http://www.hp.com/support

http://www.hp.com/storage/spock

http://www.hp.com/go/3par


HP 3PAR-to-3PAR Storage Peer Motion GuideMigrating data from one HP 3PAR storage system to another

HP 3PAR Secure Service Custodian Configuration UtilityReference

Configuring the Secure Service Custodian server in order tomonitor and control HP 3PAR storage systems

HP 3PAR Remote Copy Software User’s GuideUsing the CLI to configure and manage HP 3PAR RemoteCopy

HP 3PAR Upgrade Pre-Planning GuideUpdating HP 3PAR operating systems

HP 3PAR F-Class, T-Class, and StoreServ 10000 StorageTroubleshooting Guide

Identifying storage system components, troubleshootinginformation, and detailed alert information

HP 3PAR Policy Server Installation and Setup GuideInstalling, configuring, and maintaining the HP 3PAR PolicyServer HP 3PAR Policy Server Administration Guide

HP 3PAR documentation 105


Planning for HP 3PAR storage system setupHardware specifications, installation considerations, power requirements, networking options, and cabling information

for HP 3PAR storage systems

HP 3PAR StoreServ 7000 Storage Site Planning ManualHP 3PAR 7200, 7400, and 7450 storage systemsHP 3PAR StoreServ 7450 Storage Site Planning Manual

HP 3PAR StoreServ 10000 Storage Physical PlanningManual

HP 3PAR 10000 storage systems

HP 3PAR StoreServ 10000 Storage Third-Party RackPhysical Planning Manual

Installing and maintaining HP 3PAR 7200, 7400, and 7450 storage systems

HP 3PAR StoreServ 7000 Storage Installation GuideInstalling 7200, 7400, and 7450 storage systems andinitializing the Service Processor HP 3PAR StoreServ 7450 Storage Installation Guide

HP 3PAR StoreServ 7000 Storage SmartStart SoftwareUser’s Guide

HP 3PAR StoreServ 7000 Storage Service GuideMaintaining, servicing, and upgrading 7200, 7400, and7450 storage systems HP 3PAR StoreServ 7450 Storage Service Guide

HP 3PAR StoreServ 7000 Storage Troubleshooting GuideTroubleshooting 7200, 7400, and 7450 storage systemsHP 3PAR StoreServ 7450 Storage Troubleshooting Guide

HP 3PAR Service Processor Software User GuideMaintaining the Service ProcessorHP 3PAR Service Processor Onsite Customer Care(SPOCC) User's Guide

HP 3PAR host application solutions

HP 3PAR Recovery Manager Software for Oracle User'sGuide

Backing up Oracle databases and using backups for disasterrecovery

HP 3PAR Recovery Manager Software for MicrosoftExchange 2007 and 2010 User's Guide

Backing up Exchange databases and using backups fordisaster recovery

HP 3PAR Recovery Manager Software for Microsoft SQLServer User’s Guide

Backing up SQL databases and using backups for disasterrecovery

HP 3PAR Management Plug-in and Recovery ManagerSoftware for VMware vSphere User's Guide

Backing up VMware databases and using backups fordisaster recovery

HP 3PAR VSS Provider Software for Microsoft WindowsUser's Guide

Installing and using the HP 3PAR VSS (Volume Shadow CopyService) Provider software for Microsoft Windows

HP 3PAR Storage Replication Adapter for VMwarevCenter Site Recovery Manager Implementation Guide

Best practices for setting up the Storage Replication Adapterfor VMware vCenter

HP 3PAR Storage Replication Adapter for VMwarevCenter Site Recovery Manager Troubleshooting Guide

Troubleshooting the Storage Replication Adapter for VMwarevCenter Site Recovery Manager

HP 3PAR VAAI Plug-in Software for VMware vSphereUser's Guide

Installing and using vSphere Storage APIs for ArrayIntegration (VAAI) plug-in software for VMware vSphere

106 Support and Other Resources

Typographic conventionsTable 11 Document conventions

ElementConvention

Bold text • Keys that you press

• Text you typed into a GUI element, such as a text box

• GUI elements that you click or select, such as menu items, buttons,and so on

Monospace text • File and directory names

• System output

• Code

• Commands, their arguments, and argument values

<Monospace text in angle brackets> • Code variables

• Command variables

Bold monospace text • Commands you enter into a command line interface

• System output emphasized for scannability

WARNING! Indicates that failure to follow directions could result in bodily harm or death, or inirreversible damage to data or to the operating system.

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

NOTE: Provides additional information.

RequiredIndicates that a procedure must be followed as directed in order to achieve a functional andsupported implementation based on testing at HP.

HP 3PAR branding information• The server previously referred to as the "InServ" is now referred to as the "HP 3PAR StoreServ

Storage system."• The operating system previously referred to as the "InForm OS" is now referred to as the "HP

3PAR OS."• The user interface previously referred to as the "InForm Management Console (IMC)" is now

referred to as the "HP 3PAR Management Console."• All products previously referred to as “3PAR” products are now referred to as "HP 3PAR"

products.

Typographic conventions 107

11 Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, suggestions, or comments to Documentation Feedback([email protected]). Include the document title and part number, version number, or the URLwhen submitting your feedback.

108 Documentation feedback

mailto:[email protected]

A Troubleshooting for VASAFor information about system alerts, go to http://www.hp.com/support/hpgt/3par and selectyour server platform.

NOTE: If you are using HP 3PAR OS Software version 3.1.1 or lower, refer to HP 3PAR InFormOS 3.1.1 Messages and Operators Guide for information about system alerts.

VASA Provider Registration Related IssueIf an error occurs during the VASA Provider registration process on the vCenter server, it might becaused by one of the following issues:• The port used by Recovery Manager for the VMware installed host is being blocked by firewall

or antivirus software. By default, the VASA Web service uses port 9997 for communications.The current port number can be obtained through the Admin Tool interface.

• A proper SMS certificate has not been properly installed on the Recovery Manager for VMwarehost prior to the VASA provider registration. Refer to “Registering an SMS Certificate for theVASA Provider” (page 32) for complete details.

Inspecting VASA Provider and vCenter Server CommunicationVASA provider and vCenter server communications can be inspected by setting the log level to"High" from the Configuration option from the VASA tab available from the Admin Tools. Whenthe log level is set to "High", the received soap requests and replied responses will be written tothe log file. Following are descriptions of the alarm and event messages that might be generatedand suggested actions for each.

Alarm Type Message

MESSAGE(ID:300de) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0x300de in HP 3PAR InForm OS Message and Operator's Guide.

MESSAGE(ID:300fa) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0x300fa in HP 3PAR InForm OS Message and Operator's Guide.



MESSAGE(ID:e0001) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0xe0001 in HP 3PAR InForm OS Message and Operator's Guide.

VASA Provider Registration Related Issue 109

http://www.hp.com/support/hpgt/3par





MESSAGE(ID:110004) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0x110004 in HP 3PAR InForm OS Message and Operator's Guide.



MESSAGE(ID:15000c) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0x15000c in HP 3PAR InForm OS Message and Operator's Guide.

MESSAGE(ID:1a0002) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0x1a0002 in HP 3PAR InForm OS Message and Operator's Guide.

MESSAGE(ID:1a00de) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0x1a00de in HP 3PAR InForm OS Message and Operator's Guide.

MESSAGE(ID:1a00fa) -{Info}}

SUGGESTED ACTIONRefer to Alert Code 0x1a00fa in HP 3PAR InForm OS Message and Operator's Guide.


110 Troubleshooting for VASA


















Inspecting VASA Provider and vCenter Server Communication 111






Message(ID:150004) -{Info}

Suggested ActionRefer to Alert Code 0x0150004 in HP 3PAR InForm OS Message and Operator's Guide.






Suggested ActionNo action required.








Message(ID:1a000a) -{Info}

Suggested ActionRefer to Alert Code 0x01a000a in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:1a000b) -{Info}

Suggested ActionRefer to Alert Code 0x01a000b in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:1a000c) -{Info}

Suggested ActionRefer to Alert Code 0x01a000c in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:1a000d) -{Info}

Suggested ActionRefer to Alert Code 0x01a000d in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:1a000e) -{Info}

Suggested ActionRefer to Alert Code 0x01a000e in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:1a000f) -{Info}

Suggested ActionRefer to Alert Code 0x01a000f in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:1a0010) -{Info}

Suggested ActionRefer to Alert Code 0x01a0010 in HP 3PAR InForm OS Message and Operator's Guide.








Message(ID:1a001a) -{Info}

Suggested ActionRefer to Alert Code 0x01a001a in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:1a001b) -{Info}

Suggested ActionRefer to Alert Code 0x01a001b in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:1a001c) -{Info}

Suggested ActionRefer to Alert Code 0x01a001c in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:1a001f) -{Info}

Suggested ActionRefer to Alert Code 0x01a001f in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:2a00de) -{Info}

Suggested ActionRefer to Alert Code 0x02a00de in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:2a00fa) -{Info}

Suggested ActionRefer to Alert Code 0x02a00fa in HP 3PAR InForm OS Message and Operator's Guide.


Message(ID:3b0002) -{Info}

Suggested ActionContact HP Technical Support.













MESSAGE(ID:3a00fa) -{Info}





Message(ID:a0004) -{Info}


Message(ID:e0016) -{Info}

Suggested ActionRefer to Alert Code 0x00e0016 in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:e0017) -{Info}

Suggested ActionRefer to Alert Code 0x00e0017 in HP 3PAR InForm OS Message and Operator's Guide.

Message(ID:e001a) -{Info}

Suggested ActionRefer to Alert Code 0x00e001a in HP 3PAR InForm OS Message and Operator's Guide.


SUGGESTED ACTIONThis is an indication that a particular LUN has a change in its capability profile as the result ofbeing added to a Remote Copy group. Contact your storage administrator if this is not an intendedchange.


SUGGESTED ACTIONThis is an indication that a particular LUN has a change in its capability profile as the result ofbeing removed from a Remote Copy group. Please contact your storage administrator if this is notan intended change.

MESSAGE(ID:1000000b) -Node status has been changed. Additional information: {Info}

SUGGESTED ACTIONThis is an indication that a node has property or configuration changes. If this is not an intendedaction, contact your storage administrator for assistance.


Event Type Message











MESSAGE(ID:a0001) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0xa0001 in HP 3PAR InForm OS Message and Operator's Guide.

MESSAGE(ID:a0002) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0xa0002 in HP 3PAR InForm OS Message and Operator's Guide.








MESSAGE(ID:1a0002) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0x1a0002 in HP 3PAR InForm OS Message and Operator's Guide.



MESSAGE(ID:1a00fa) -{Info}













MESSAGE(ID:27000e) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0x27000e in HP 3PAR InForm OS Message and Operator's Guide.

MESSAGE(ID:27000f) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0x27000f in HP 3PAR InForm OS Message and Operator's Guide.


















MESSAGE(ID:27001a) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0x27001a in HP 3PAR InForm OS Message and Operator's Guide.

MESSAGE(ID:27001b) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0x27001b in HP 3PAR InForm OS Message and Operator's Guide.

MESSAGE(ID:27001c) -{Info}

SUGGESTED ACTIONRefer to Alert Code 0x27001c in HP 3PAR InForm OS Message and Operator's Guide.


SUGGESTED ACTIONRefer to Alert Code 0x2900de in HP 3PAR InForm OS Message and Operator’s Guide.



MESSAGE(ID:10000001) - New LUN is created. Additional information: {Info}

SUGGESTED ACTIONNo action is required. This indicates that a LUN is exposed to one of the monitored ESX host.


MESSAGE(ID:10000002) - Existing LUN in 3PAR Storage Server has been removed. Additional information:{Info}

SUGGESTED ACTIONThis indicates that an existing exposure to the monitored ESX host has been removed. Please contactyour storage administrator if this is not an intended operation.

MESSAGE(ID:10000005) - Existing LUN in 3PAR Storage Server has been renamed. Additional information:{Info}

SUGGESTED ACTIONNo action is required. This indicates that an already exposed LUN has a name change in thestorage system.

MESSAGE(ID:10000007) - Existing LUN property has been updated due to changes to host. Additionalinformation: {Info}

SUGGESTED ACTIONNo action is required. This indicates that there is a name change to the monitored ESX host in thestorage system.

MESSAGE(ID:10000006) - Existing LUN property has been updated due to changes to CPG. Additionalinformation: {Info}

SUGGESTED ACTIONNo action is required. This indicates that there is a name change to the corresponding CPG in thestorage system.

MESSAGE(ID:10000008) -License key information in the storage system has been updated.

SUGGESTED ACTIONThis indicates that there is a license change in the Storage System. This might be the result of licenseexpiring or changes to an existing license.

MESSAGE(ID:10000009) -Storage system name has been changed. Additional information: {Info}

SUGGESTED ACTIONNo action is required. This indicates that there is a name change to the storage system.

MESSAGE(ID:1000000a) -Node attribute has been changed. Additional information: {Info}

SUGGESTED ACTIONThis indicates that the status of associated port under the node has been changed. Check yourstorage system to make sure port is in good status.


MESSAGE(ID:1000000b) -Node status has been changed. Additional information: {Info}

SUGGESTED ACTIONThis indicates that there is a node status change. This might be caused by node shutdown orrecovery. Please check your storage system for more information.


B Troubleshooting for HP 3PAR Management Plug-inResolving HP 3PAR Multi-tab Issue

You need to install HP 3PAR Plug-in certificate and all vCenter servers certificate that involves inlinked mode configuration while prompted for the certificate warnings or security alert when loggingon to vSphere client.Click HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere underSolutions and Applications.1. Click View Certificate.2. On Certificate dialog, click Install Certificate.3. Follow the Wizard and select Place all certificates in the following store on Certificate Store

page and click Browse.4. On the Select Certificate Store dialog, check the Show physical stores check box.5. Expand the Trusted Root Certification Authorities tree and select Local Computer.6. Click OK.7. From the Certificate Store dialog, the certificate store path appears as Trusted Root

Certification Authorities\Local Computer. ClickNext and then Finish to completethe import process.

8. Complete the Wizard and click Ok to exit the Certificate dialog.9. Repeat steps 1 through 5 for the remaining vCenters by selecting a vCenter from the drop

down list.10. Log off the vSphere client after installing certificate for each vCenter server.11. Log on to vSphere client.

124 Troubleshooting for HP 3PAR Management Plug-in

Index

Symbols3PAR, 15

CCLI, 8Cluster viewaccessing, 20

configurationediting, 37

Configuration tab, 36configuring, 36conventionstext symbols, 107

credential sharing, 14

Ddata consistency, 22data store Virtual Copiesrestrictions, 23

datacenter viewaccessing, 21

Datastore viewaccessing, 17

Datastore Virtual Copies, 23default configuration, 36deinstallation, 35deinstalling, 35deleting Virtual Copies, 74documentationproviding feedback on, 108

Eediting the plug-in configuration, 37editing Virtual Copies, 75ensuring volume consistency, 22ESX host viewaccessing, 19

expirable Virtual Copiesenabling, 74

Ffirewalls, 16

HHP 3PAR Host ExplorerESX host discovery, 6

HP 3PAR Management Plug-Incomponents, 6deinstallation, 35installation, 27interface, 16overview, 6plug-in views, 16ports, 15tabs, 16

HP 3PAR Management Plug-In for VMwarevirtual volume mapping, 6

HP 3PAR Recovery Manager Administratoradministrator log in, 15restrictions, 15

HP 3PAR Recovery Manager for VMware vSphereinterface, 16plug-in views, 16ports, 15tabs, 16Virtual Copy management, 6

HP 3PAR Recovery Manager Software for VMware vSphereusing, 68

HP 3PAR VASA ProvidervCenter Server information, 6

Iinstallation, 27installation package contents, 29installation requirements, 27interface overview, 16

Llicense, 27

Mmanaging Virtual Copies, 68metadata, 24mounting Virtual Copies, 71

Pplug-inediting the configuration, 37registration, 40unregistering, 40

Plug-in Registration tabidentification of fields, 40

promoting Virtual Copies, 72

RRecovery Manager for VMware vSpherecomponents, 6registration, 8

Recovery Manager Software for VMware vSphereinstallation, 27overview, 6

registering the plug-in, 40registration, 31requirements for installation, 27restore functionality, 80restoring Datastores, 72restoring guest files and directories, 80restoring virtual disks, 80retaining Virtual Copy sets, 75RMVMware CLI, 8RMVMware create command, 8

125

RMVMware InServRegister command, 11RMVMwareAdminTool, 8RMWebAccess Library, 8

Ssnapshot operationsminimum privilege level, 15

starting HP 3PAR Management Plug-In for VMwarevCenter, 53

Status tab, 41Storage System login, 15supported platforms, 27symbols in text, 107

Ttext symbols, 107TpdVmWebService, 8

Uunmounting Virtual Copies, 72unregistering the plug-in, 40user authentication, 14

Vviewing Virtual Copies, 68viewing Virtual Copy metadata, 24viewing volume information, 57Virtual Copies

ensuring application consistency, 71restrictions, 70

creating, 70deleting, 74editing, 75mounting, 71promoting, 72unmount, 72viewing, 68

Virtual CopyDatastore, 23organization, 25properties, 25viewing metadata, 24Virtual Machine, 23VM consistent, 25

Virtual Copy browser, 24Virtual Copy data consistencysupported types, 22

Virtual Copy management, 15Virtual Copy policiesmodifying, 74

Virtual Copy policyattributes, 22

virtual disksrestoring, 80

Virtual Machine viewaccessing, 18

Virtual Machine Virtual Copiesrestrictions, 24

virtual volume mapping, 56

Virtual Volumes tabdisplay, 58

VM consistent Virtual Copy, 25VMFS snapshots, 25VMware Tools, 22VMware vCenter Server, 6VMware vSphere, 6vSphere Clientlogging in, 54

126 Index