HP Application Software Suite for VMware User Manual
HP 3PAR Management Plug-in and Recovery
Manager 2.3.0 Software
nl
for VMware vSphere
User Guide
Abstract
This guide is intended for VMware and database administrators responsible for backing up databases and provides information
how to install, configure, and use HP 3PAR Management Plug-in and Recovery Manager 2.3.0 Software for VMware vSphere®.
HP Part Number: QL226-96272
Published: May 2012
© Copyright 2012 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 express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not 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 authority
to 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 harmful
interference, 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 limits
are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may
cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which
case 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.
Contents
1 Overview..................................................................................................6
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere.......................6
HP 3PAR Management Plug-in for VMware vCenter.......................................................................6
Virtual Volume Details..........................................................................................................6
LUN Provisioning for Recovery Manager for VMware................................................................7
HP 3PAR Recovery Manager Software for VMware vSphere...........................................................7
TpdVmWebService..............................................................................................................8
RMWebAccess Library.........................................................................................................8
RMVMware Admin Tool........................................................................................................8
RMVMwareCLI....................................................................................................................8
RMVMware create Command...........................................................................................8
RMVMware InServRegister Command..............................................................................11
RMVMware VCenterRegister Command...........................................................................12
RMVMware createrc Command......................................................................................13
User Authentication.................................................................................................................13
VMware vCenter Server Login for HP 3PAR Virtual Volume and Virtual Copy Management..........14
HP 3PAR Storage System Login............................................................................................14
Network Ports used by HP 3PAR Management Plug-in and Recovery Manager Software for VMware
vSphere............................................................................................................................14
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere Interface........14
HP 3PAR Views in the vSphere Client........................................................................................15
Datastore View..................................................................................................................16
Virtual Machine View.........................................................................................................17
ESX Host View...................................................................................................................18
Cluster View......................................................................................................................18
Datacenter View................................................................................................................19
About Virtual Copy Management.............................................................................................20
Virtual Copy Data Consistency............................................................................................20
Virtual Copy Policy.............................................................................................................20
Datastore Virtual Copies.....................................................................................................21
Virtual Machine Virtual Copies............................................................................................21
Remote Virtual Copies........................................................................................................22
The Virtual Copy Browser....................................................................................................22
VMFS Snapshots................................................................................................................23
Scheduling Tool.................................................................................................................23
Host Explorer.........................................................................................................................23
VASA Support........................................................................................................................23
2 Installing, Registering, and Uninstalling HP 3PAR Management Plug-in and
Recovery Manager Software for VMware vSphere...........................................24
Supported Platforms................................................................................................................24
Pre-installation Requirements and Dependencies.........................................................................24
Allowing Port Selections with Windows 2008 Installation........................................................25
Installing HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere........26
Support for VMware vCenter Server Linked Mode..................................................................28
Viewing and Installing HP 3PAR Management Plug-in Certificate...................................................29
Registering an SMS Certificate for the VASA Provider..................................................................29
Extracting the SMS Certificate.............................................................................................30
Installing the SMS Certificate...............................................................................................30
To Install the SMS Certificate Through the VASA Web Service.............................................30
Installing the SMS Certificate Manually............................................................................30
Contents 3
Uninstalling HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere....31
Upgrading from a Previous Version...........................................................................................31
Using Secure Service Connections........................................................................................31
Refreshing Plug-in Details....................................................................................................31
3 Using the Admin Tool to Modify Configuration Settings.................................32
Overview..............................................................................................................................32
The RMVMware Admin Tool.....................................................................................................32
vCenter Plug-in Tab.................................................................................................................32
vCenter Plug-in Configuration..............................................................................................33
Plug-in Registration.............................................................................................................35
vCenter Status...................................................................................................................36
Remote Copy Pairs.............................................................................................................36
Host Explorer Tab...................................................................................................................38
Host Explorer Configuration................................................................................................38
Storage System Mapping....................................................................................................39
vCenter Mapping..............................................................................................................40
The VASA Tab........................................................................................................................41
VASA Configuration...........................................................................................................41
Storage System Mapping....................................................................................................43
Storage System Credential Tab.................................................................................................44
4 Logging In and Working with Virtual Volumes..............................................46
Logging In.............................................................................................................................46
Viewing Virtual Volume Mapping.............................................................................................51
Viewing Volume Information................................................................................................52
The Upper Pane............................................................................................................52
The Lower Pane.............................................................................................................54
Refreshing Virtual Volume Information........................................................................................54
Creating Virtual Volumes and Datastores...................................................................................55
Creating a Virtual Volume from an Existing HP 3PAR System Template......................................55
Creating a Virtual Volume from Existing Datastores.................................................................58
Adding an ESX(i) Host to the vCenter Server..............................................................................59
5 Working with Virtual Copies......................................................................60
Viewing Virtual Copy Information.............................................................................................60
Viewing Virtual Disk Details for Virtual Copies.......................................................................61
Viewing Virtual Copy Event Logs..........................................................................................62
Creating New Virtual Copies...................................................................................................62
Mounting Virtual Copies..........................................................................................................63
Unmounting Virtual Copies......................................................................................................64
Restoring Datastores by Promoting a Virtual Copy.......................................................................64
Deleting a Virtual Copy...........................................................................................................65
Modifying Virtual Copy Policies................................................................................................65
Scheduling Virtual Copies........................................................................................................66
Restoring Virtual Disks and Guest OS Files and Directories...........................................................71
Restoring a Virtual Disk.......................................................................................................71
Restoring a Guest OS File or Directory from a Virtual Copy.....................................................72
6 Working with Host Explorer.......................................................................74
7 Working with VASA Provider......................................................................75
8 Working with Remote Copy.......................................................................79
Registering Remote Copy Pairs.................................................................................................79
Updating Registered Remote Copy Pairs Information....................................................................81
Viewing Host Information Summary...........................................................................................81
Viewing Existing and Newly Added Remote Copy Information......................................................81
4 Contents
Creating a Remote Virtual Copy...............................................................................................82
Scheduling a Remote Copy Virtual Copy...................................................................................83
Removing Remote Virtual Copies...............................................................................................86
Removing Local Virtual Copies..................................................................................................86
Importing a Virtual Machine and Reverting to a Specific Point-in-Time Virtual Copy..........................87
Importing a Virtual Machine From a Remote Site and Reverting to a Specific Point-in-Time Virtual
Copy....................................................................................................................................87
9 Using HP 3PAR Peer Motion Manager Software with Recovery Manager.........89
10 Support and Other Resources...................................................................90
Related Documents.................................................................................................................90
Typographical Conventions......................................................................................................90
Advisories..............................................................................................................................91
A Troubleshooting for VASA..........................................................................92
VASA Provider Registration Related Issue....................................................................................92
Inspecting VASA Provider and vCenter Server Communication......................................................92
Alarm Type Message..........................................................................................................92
Event Type Message...........................................................................................................96
B Troubleshooting for HP 3PAR Management Plug-in......................................102
Resolving HP 3PAR Multi-tab Issue...........................................................................................102
Index.......................................................................................................103
Contents 5
1 Overview
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
VMware Virtual Infrastructure management suite has two components, VMware vCenter Server
and Virtual Infrastructure Client (vSphere Client). vCenter Server is a web service installed on a
Windows server. VI Client is a Windows desktop application, and is typically downloaded from
the vCenter Server.
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere is a suite of
services designed to work with the vCenter Server. The plug-in contains a web application and
deploys as a VI Client plug-in (a VI Client plug-in is an external Web application configured with
the vCenter Server for vSphere Clients to display their pages). The application also provides a
Host Explorer service to communicate and send ESX host configuration details to the HP 3PAR
Storage Systems. The plug-in also contains a software component that acts as a vSphere Storage
API for Storage Awareness (VASA) provider in the vSphere environment. HP 3PAR Management
Plug-in and Recovery Manager Software for VMware vSphere provides its own web servers.
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere includes the
following major components:
• HP 3PAR Management Plug-in for VMware vCenter - Displays virtual volume mapping for easy
identification of HP 3PAR volumes used by virtual machines and datastores. Also allows user
to provision LUNs to be used as Datastore or raw device.
• HP 3PAR Recovery Manager for VMware vSphere - Provides virtual copy management of HP
3PAR 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 to
obtain information about available storage topologies, capabilities, and state.
HP 3PAR Management Plug-in for VMware vCenter
HP 3PAR Management Plug-in for VMware vCenter is a free vSphere Client plug-in. The plug-in
enables easy identification of HP 3PAR virtual volumes used by virtual machines and datastores
and displays commonly used volume properties and attributes. The plug-in also supports LUN
Provisioning that enables the creation of a virtual volume and/or datastore based on an existing
configuration or template.
Virtual Volume Details
HP 3PAR Management Plug-in for VMware vCenter displays virtual volume information for each
volume used by a Virtual Machine (VM) or datastore via the HP 3PAR tab in the vSphere Client.
6 Overview
Figure 1 Viewing Datastore Virtual Volumes
See “Logging In and Working with Virtual Volumes” (page 46) for additional information about
viewing virtual volume details.
LUN Provisioning for Recovery Manager for VMware
This feature enables you to create virtual volumes based upon a storage system template or an
existing 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 a
Virtual Volume from an Existing HP 3PAR System Template” (page 55)
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 vSphere
HP 3PAR Recovery Manager Software for VMware vSphere allows you to manage virtual copies
of VMs and datastores. It is comprised of the following four components:
• TpdVmWebService
• RMWebAccess Library
• RMVMware Admin Tool
• RMVMwareCLI
See “About Virtual Copy Management” (page 20) for additional information.
HP 3PAR Recovery Manager Software for VMware vSphere 7
TpdVmWebService
TpdVmWebService is a restful Web service, which is deployed as a Windows Service. The major
functions of Recovery Manager for VMware vSphere are implemented with this module. These
functions are:
• Provides a custom Web server to deliver plug-in application Web pages. vCenter Servers are
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 machines
and datastores.
RMWebAccess Library
NOTE: RMWebAccess Library is deployed as a Windows component dll file and is installed
as part of Recovery Manager for VMware vSphere.
Similar to the InForm Command Line Interface (CLI) and InForm Management Console (IMC), the
RMWebAccess Library is used for interacting with the HP 3PAR Storage System array. The
RMWebAccess Library does not use InForm CLI but instead interacts with the InServ Tpd TCL Service
directly using secure network connections.
RMVMware Admin Tool
The RMVMware Admin Tool provides a Graphical User Interface (GUI) for administering Recovery
Manager for VMware vSphere registration with the vCenter server. This tool also includes Host
Explorer for VMware configuration, HP 3PAR Storage System credential management, HP 3PAR
VASA Provider configuration and Remote Copy paring configuration.
RMVMwareCLI
The RMVMware CLI module is the command line interface for Recovery Manager for VMware
vSphere.
NOTE: The recommended method for creating virtual copies is through the Graphical User
Interface (see “Working with Virtual Copies” (page 60) for complete details).
Four commands are provided through the CLI:
• RMVMware create
• RMVMware InServRegister
• RMVMware vCenterRegister
• RMVMware createrc
RMVMware create Command
The 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 across
ESX hosts.
The UUID of the datastore or virtual machine may also be used to create a virtual copy with
uuid-<myUUIDofDatastore> or uuid-<myUUIDofVirtualMachine> in place of the
Datastore or Virtual Machine name.
• -consistency <yes/no>
(Optional) Specifies whether or not (yes/no) the virtual copy is to maintain Virtual Machine
application consistency with supported data formats.
• -setname <VirtualCopySetName>
(Optional) Specifies that in addition to the virtual copy time stamp, the virtual copy set name
can be used to personalize the identity of the virtual copy set. By default, the name is set to
reflect 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 used
to specify the credential store file.
• -vcfile <VMwareCredentialStoreFileLocation>
The VMware credential stores file location. The –vcfile option is optional when –vcpwd is
specified. 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, you
must be added as a user to have permission to access the credential file.
• -inserv <InServName>
The name of the HP 3PAR Storage System on which the VM or datastore resides. This option
is required.
HP 3PAR Recovery Manager Software for VMware vSphere 9
• -inservuid <InServUserID>
The HP 3PAR Storage System user’s login name.
• -inservpwd <InServPassword>
The HP 3PAR Storage System login password. This option is not required if the Storage System
name, user ID, and password have been registered.
• -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 system
regardless 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 maximum
count specified through the policy settings. See “Working with Virtual Copies” (page 60) for
more 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 which
period the virtual copy cannot be altered. The virtual copy is not deleted after the retention
period but is then available for modification and deletion. See “Working with Virtual Copies”
(page 60) 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 a
Virtual Machine or a datastore, you can reference the server password or credentials from a given
file 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, use
the following uuid-<myUUIDofDatastore> or uuid-<myUUIDofVirtualMachine>
commands in place of datastore or virtual name such as
uuid-4220f0f6-3aec-258b-dc41-949f596c6ba8.
10 Overview
RMVMware InServRegister Command
The RMVMware InServRegister command registers HP 3PAR Storage System credentials. 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 RMVMware
Admin Tool can use the RMVMware InServRegister command to create the appropriate
registration.
The options and arguments used for this command are described as follows:
• -inserv <InServName>
Specifies the HP 3PAR Storage System’s login name to the vCenter Server. This option is
required.
• -inservuid <InServUserID>
Specifies the HP 3PAR Storage System’s login user name. This option is required.
• -inservpwd <InServPassword>
Specifies the HP 3PAR Storage System’s login password. This option is required when
registering an HP 3PAR Storage System.
• -remove
Removes a registered HP 3PAR Storage System configuration.
• -display
Displays all registered HP 3PAR Storage System credentials.
HP 3PAR Recovery Manager Software for VMware vSphere 11
Example:
The following command will add a new entry for the HP 3PAR Storage System s124:
C:\> RMVMware InServRegister -inserv s124 -inservuid root -inservpwd pass2word
RMVMware VCenterRegister Command
The RMVMware VCenterRegister command manages the vCenter credentials. The syntax for
the 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">
The options and arguments used for this command are described as follows:
• -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 Command
The RMVMware createrc command creates a remote virtual copy.
NOTE: When using the RMVMware createrc command, you must use the identical name of
the storage system registered in the HP 3PAR Storage system credential database.
The syntax for the RMVMware createrc command:
RMVMware Createrc <-rcgroup "RemoteCopyGroup"> [-consistency <yes|no>] <[-vcserver
"vCenterServerName" [-vcuid "vCenterServerUserID"] [-vcpwd "v
CenterServerPassword"] | [-vcfile "VMwareCredentialStoreFileLocation"] ]> <-remotehost
"RemoteHostName"> <[-inserv "InServName"] [-inservuid "InServUs
erID"]> [-inservpwd "InServPassword"] <[-remoteinserv "InServName"] [-remoteinservuid
"InServUserID"]> [-remoteinservpwd "InServPassword"] [-expiry "V
irtualCopyExpiryInHour"] [-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 s25
6 -inservuid root -remoteinserv s336 -remoteinservuid root -consistency yes
User Authentication
As stated earlier, HP 3PAR Management Plug-in and Recovery Manager Software for VMware
vSphere is deployed as a vSphere Client plug-in. You must first log into the vCenter Server before
accessing HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere’s
features. HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
does not ask for a user name or password. Instead, it uses a user login credentials to access
VMware inventory. This credential sharing is the VMware recommended way for transparent plug-in
authentication.
User Authentication 13
VMware vCenter Server Login for HP 3PAR Virtual Volume and Virtual Copy Management
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere creates a
new 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 check
is skipped.
NOTE: For VM access, the HP 3PAR Recovery Manager Administrator role must be assigned at
the ESX server level or the cluster server level where the VM resides. For datastore access, the HP
3PAR Recovery Manager Administrator role must be assigned at the datacenter level.
HP 3PAR Storage System Login
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere has to
connect to an HP 3PAR storage array in order to obtain volume details for mapping and virtual
copy management. You can log on to a system on an on-demand basis and HP 3PAR Management
Plug-in and Recovery Manager Software for VMware vSphere does not save any storage system
user names or passwords locally on the desktop, or centrally on the server. When HP 3PAR
Management Plug-in and Recovery Manager Software for VMware vSphere needs to access an
HP 3PAR Storage System and no connection already exists, it will display an error and provide
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” check
box when logging into a given system. In this case, the login details are stored in the Credential
database and you do not have to enter them every time you access the system. To replace the
currently saved credential, you must log out from the storage system and login again with “Remember
Me” checked for the new credential. To remove the currently saved credential, logout from the
storage system and login again with the same credential with “Remember Me” unchecked. You
can also remove the currently saved credential through the Admin Tool→Storage System Credential
tab.
NOTE: You must have a minimum of Edit level or 3PAR_RM level privileges for accessing the
Virtual Copies tab, and Browse level privileges for accessing the Virtual Volumes tab.
Network Ports used by HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere uses the
following network port:
9931 ( Recovery Manager service default port), 9997 (VASA default port), vCenter Server HTTP
port, and vCenter Server HTTPS port for secure access (between the vCenter Server, VI client, and
HP 3PAR Management Plug-in and Recovery Manager for VMware vSphere.
Firewalls, if any, must be configured to allow traffic to these ports with the outbound connections
rule set to allow (default) in order for HP 3PAR Management Plug-in and Recovery Manager for
VMware vSphere to function properly.
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere Interface
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere appears as
a tab in the vSphere Client. When the HP 3PAR tab is selected, the HP 3PAR Management Plug-in
14 Overview
and Recovery Manager for VMware vSphere interface appears as shown in Figure 2 (page 15).
The interface is divided into the following:
• Main menu navigation
• Navigation tree
• Tabs and detail pane
• Tasks and alerts pane
The interface elements are referenced later in this guide .
Figure 2 HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
Interface
HP 3PAR Views in the vSphere Client
The HP 3PAR Management Plug-in and the Recovery Manager Software for VMware vSphere adds
its own plug-in views in the vSphere Client. Each plug-in view is associated with a VMware entity
such as a VM or datastore (Virtual Volume). The details of plug-in views are defined in an XML file
URL, which is registered with the vCenter Server during plug-in registration (see “Installing HP 3PAR
Management Plug-in and Recovery Manager Software for VMware vSphere” (page 26) for
information about registering HP 3PAR Management Plug-in and Recovery Manager Software for
VMware vSphere).
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere adds the
following 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 use
Raw 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 view
displays all virtual volumes associated with every ESX host in the datacenter.
HP 3PAR Views in the vSphere Client 15
NOTE: HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
does not support a single ESX host mapped to multiple HP 3PAR Storage System host names. All
WWNs for each Fiber Channel host adaptor on the same ESX server should be used to create a
single host name on the storage system.
Datastore View
To access the datastore view:
1. Under Inventory from the vSphere Client home page, click Datastores.
Figure 3 Selecting Datastores
All datastores residing in the data center are displayed in the navigation tree.
Figure 4 Viewing Datastores in the Navigation Tree
16 Overview
2. Select a datastore and then click the HP 3PAR tab.
Information about the virtual volumes associated with the datastore are displayed.
Virtual Machine View
To access the Virtual Machine (VM) view:
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
HP 3PAR Views in the vSphere Client 17
2. Select a VM and then click the HP 3PAR tab.
Information about the virtual volumes associated with the VM is displayed.
ESX Host View
To 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 View
To access the cluster view:
18 Overview
1. Under Inventory from the vSphere Client home page, click Hosts and Clusters (see Figure 7
(page 18)).
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 View
To access the datacenter view:
1. Under Inventory from the vSphere Client home page, click Datastores, VMs and Templates,
or VMs and Templates (see Figure 3 (page 16), Figure 5 (page 17), or Figure 7 (page 18)).
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.
HP 3PAR Views in the vSphere Client 19
About Virtual Copy Management
NOTE: HP 3PAR Recovery Manager for VMware vSphere is not functional without the HP 3PAR
Recovery Manager for VMware vSphere license. Additionally, the HP 3PAR Virtual Copy license
is required for virtual copy operation and the HP 3PAR Virtual Lock license is required for using
the volume retention policy.
HP 3PAR Recovery Manager for VMware vSphere allows you to take LUN-level virtual copies of
Virtual Machines (VMs), datastores and remote copy groups. A datastore is created on one HP
3PAR 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 take
virtual copies simultaneously for all volumes to ensure consistency. Recovery Manager for VMware
vSphere manages this set of virtual copies as a single entity. Remote Copy virtual copies are based
at the Remote Copy group level (storage system), versus the virtual machine or datastore level
(VMware perspective).
NOTE: VMware Tools must be installed on the Guest OS in order for HP 3PAR Recovery Manager
for VMware vSphere to create successful VM/Application consistent virtual copies. Refer to VMware
documentation for more information about VMware Tools setup instructions.
Virtual Copy Data Consistency
Several 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 system
crash, VM and application consistent virtual copies.
• Crash Consistent - A simple virtual volume virtual copy without quiescing the memory blocks
inside the guest OS results in a crash consistent virtual copy of the VM. Data not flushed will
be 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 virtual
copy is taken. This ensures that no file system data is lost if the VM crashes. Checking of file
system (fsck) is not required after recovery. No application data is flushed from memory before
the virtual copy is taken
• Application Consistent - Application consistency is provided for HP 3PAR snapshots of Virtual
Machines for data compatibility with supported applications.
Virtual Copy Policy
Recovery Manager for VMware vSphere allows the creation of virtual copy policies for VMs and/or
datastores. Only one policy is permitted for every VM and/or datastore. Datastore and VM policies
exist independently; meaning a VM’s policy is independent of the policy of the datastore(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. Once this limit is reached, the earliest virtual copy will be deleted to allow the latest
virtual copy to be created.
• Enable expirable virtual copies - Allows you to specify that created virtual copies are removed
• Retain Virtual Copy Set - The supported number of hours, days, weeks, months, and years
20 Overview
according to a specified schedule and are not affected by the maximum count.
that a virtual copy set is retained.
NOTE: The Retain Virtual Copy Set option requires the HP 3PAR Virtual Lock license. Contact
your local service provider for additional information.
• Ensure Application Consistency - This option is used to create virtual copies that adhere to
data format standards used by Microsoft VSS for guest operating systems. This option is only
available VM policy.
Datastore Virtual Copies
A datastore is created on a Fibre Channel or iSCSI LUN. During virtual copy creation, Recovery
Manager for VMware vSphere identifies the HP 3PAR volume used and takes a virtual copy of the
volume. Recovery Manager for VMware vSphere stores the details of all virtual disks and VMs
present in the datastore.
This feature has the following restrictions:
• The datastore must be on exactly one HP 3PAR volume. A datastore that spans across more
than one LUN is not supported.
• RDM LUNs defined in the datastore are not included in the virtual copy. It is possible that a
HP 3PAR LUN is used as RDM in a guest OS, which is defined in a datastore created on
another 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 application
integrity checks must be performed in the guest OS for the crash consistent virtual copies after
restoration.
• Network File System (NFS) datastores are not supported.
• VMFS file systems spanning multiple hard disk partitions to create a single logical volume are
not supported.
• The datastore must not be on an ESX SAN boot disk. Virtual Copy operations are not supported
on datastores residing in ESX SAN boot disks.
For information about creating virtual copies, see “Creating New Virtual Copies” (page 62).
Virtual Machine Virtual Copies
A Virtual Machine (VM) configuration files are created in a datastore. VMDK virtual disks used by
VMs are created on one or more datastores. In addition, a VM can use HP 3PAR volumes directly
as RDM virtual disks. Recovery Manager for VMware vSphere identifies all of the HP 3PAR volumes
used by a VM and creates virtual copies of all of them simultaneously. A list of virtual disk names
and their type (RDM or VMDK) and configuration file name are also recorded in the repository
during virtual copy creation.
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 satisfy
the conditions mentioned in “Datastore Virtual Copies” (page 21).
• If the VM uses more than one HP 3PAR volume, all of them must be from the same HP 3PAR
storage 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 integrity
checks must be performed in the guest OS after restoration for the crash consistent virtual
copies.
About Virtual Copy Management 21
• VMs using NFS datastores are not permitted.
• VMFS file systems spanning multiple hard disk partitions to create a single logical volume are
not supported.
For information about creating VM virtual copies, see “Creating New Virtual Copies” (page 62).
Remote Virtual Copies
Remote Virtual Copies are based on the Remote Copy Group. If a VM or datastore uses virtual
volumes outside of the Remote Copy group, HP 3PAR Recovery Manager for VMware vSphere
cannot take a remote virtual copy of the group. Remote Virtual Copies require a remote host with
SAN connectivity to the target Storage System and reside on the remote 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 to
use the virtual copy browser.
In Recovery Manager for VMware vSphere, every virtual copy, VM, or datastore has its own
metadata, which is used in instances where a restoration is necessary. Metadata is kept in a local
file system of the server.
You can view virtual copy metadata at any time after it was created using the virtual copy browser
of the VM and datastore views of the plug-in.
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 Storage System where virtual copy volumes exist.
• The virtual copy set name (optional).
22 Overview
• 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 disks
and/or VM names.
All virtual copies are organized in the browser based on their creation times. The browser displays
all relevant metadata so that you can make restore decisions faster and without actually mounting
virtual copy volumes.
The data shown in the virtual copy browser comes from the metadata repository and may not
reflect the current state of HP 3PAR Storage System. It is possible that volumes shown in the browser
may not exist in the HP 3PAR Storage System; for example, if a volume is deleted.
For information about viewing the Virtual Copy browser, see Figure 41 (page 54).
VMFS Snapshots
In order to maintain a VM consistent virtual copy, a VMFS snapshot will be created before creating
an HP 3PAR virtual copy and the VMFS copy will be deleted when the HP 3PAR virtual copy is
created. HP 3PAR virtual copies and VMFS snapshots cannot coexist. HP 3PAR virtual copy creation
in VM, Datastore, or Remote Copy will fail if there are preexisting VMFS snapshots for the 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 time
limit 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 resolve
the issue.
Scheduling Tool
You can automatically have virtual copies created according to a specified schedule by using the
scheduling tool (see “Scheduling Virtual Copies” (page 66) for details). You have the option of
scheduling when (hourly, daily, weekly, monthly) the virtual copy is to be created and then specifying
how often the task is to be performed. You can also schedule a virtual copy creation task to occur
on a one-time basis.
Host Explorer
Host Explorer for VMware communicates with the storage server over a TCP/IP connection and
provides detailed host configuration information. You can start the service and configure settings
through the Host Explorer tab available from the RMVMware Admin Tool GUI interface (see “Host
Explorer Tab” (page 38) for details).
VASA Support
Support is included for vSphere Storage APIs for Storage Awareness (VASA) that allows a VMware
administrators to view information about the physical storage array as well as the virtual data
store. For instance, you can get performance statistics from within vCenter associated with a LUN
on HP 3PAR disk arrays. For more information on VASA, refer to "Storage Providers" in vCenter
Server.
Host Explorer 23
2 Installing, Registering, and Uninstalling HP 3PAR
Management Plug-in and Recovery Manager Software
for VMware vSphere
This chapter describes how to install, register, uninstall, and upgrade HP 3PAR Management Plug-in
and Recovery Manager Software for VMware vSphere.
Supported Platforms
For information about supported platforms, refer to the HP 3PAR InForm OS Configuration Matrix.
To obtain a copy of this documentation, go to http://www.hp.com/go/3par/, navigate to your
product page, click Support for your product, and then click Manuals.
Pre-installation Requirements and Dependencies
Prior to the installation of HP 3PAR Management Plug-in and Recovery Manager Software for
VMware vSphere, make sure that the following pre-installation requirements are met:
• HP 3PAR Recovery Manager Software for VMware vSphere is distributed as a Microsoft
installer MSI image, RMVMware_<platform>.msi, where <platform> can be x86 for
Windows 32 bit OS or x64 for Windows 64 bit OS.
• HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere is
supported on Microsoft Windows 2008 x86, Windows 2008 x64, and Windows 2008 R2.
It is recommended that Windows be installed on a standalone system.
• HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere supports
vCenter Server 4.1 and 5.0, 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 the
latest versions of vCenter Server and ESX. Both ESX 3.5. and vCenter Server 4.1 does not
support 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 Copy
license is required for virtual copy operation.
• The HP 3PAR Virtual Lock license is required for setting retention policies in virtual copy
creation.
• 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 copy
operations, and Browse level privilege for virtual volume operations.
• You must be an Administrator of the vCenter Server for plug-in registration.
NOTE: Silverlight is required only for the desktop. Recovery Manager for VMware vSphere server
does not require Silverlight.
• Desktops running vSphere clients (where HP 3PAR Management Plug-in and Recovery Manager
Software for VMware vSphere pages are displayed) must have the Microsoft web browser
plug-in Silverlight runtime installed. The controls of the Microsoft web browser plug-in Silverlight
are used for rendering HP 3PAR Management Plug-in and Recovery Manager Software for
VMware vSphere’s web pages. You will be prompted to download Silverlight the first time
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere’s web
pages are displayed if Silverlight is not already installed. If after you have downloaded and
24 Installing, Registering, and Uninstalling HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
installed Silverlight, the page still displays "Get Microsoft Silverlight", you can reset the page
with 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 with
application consistency. Refer to VMware documentation for more information about VMware
Tools setup instructions.
• HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere currently
only supports English localization.
Allowing Port Selections with Windows 2008 Installation
To set up HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
with the SSL port for communications, you need to grant full permission to the Administrator. Here
are 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. Left click MachineKeys and choose Properties.
The MachineKeys Properties Dialog appears (Figure 12 (page 25)).
Figure 12 MachineKeys Properties Dialog
3. Select the Security tab.
The Security Tab dialog appears (Figure 13 (page 26)).
Pre-installation Requirements and Dependencies 25
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 with
the 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 Software for VMware vSphere
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere is supported
in Windows 2008, and Windows 2008 R2. Both x86 and x64 are supported. The installation
package 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:
26 Installing, Registering, and Uninstalling HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
1. Insert the HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
disc into your CD-ROM drive.
2. Double-click the installation package appropriate for your system to launch the installation
wizard.
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 box
in order to complete the HP 3PAR Management Plug-in and Recovery Manager Software for
VMware 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 following
information:
• 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 can
be alternatively entered.
• Recovery Manager service TCP port - The default secure network port is 9931. The port
can be changed, however it cannot conflict with other usage.
NOTE: Windows 2008 installations need to grant full permissions to the Administrator
in order to be able to change port assignments. (see “Allowing Port Selections with
Windows 2008 Installation” (page 25) for details.
NOTE: VMware vCenter Server 4.1 and 5.0 are supported in this release.
5. As an option, you can select the “Skip Plug-in Registration” check box for RMV installations
on a remote site where a remote vCenter has not been installed. To manage a remote virtual
copy, the RMV server on the remote site needs to register to the vCenter during the installation
or via the Admin Tool after the installation.
Installing HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere 27
6. In the Plugin 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 Software
for VMware vSphere can be registered with multiple vCenter Servers. Use the RMVMware
Admin Tool to register HP 3PAR Management Plug-in and Recovery Manager Software for
VMware vSphere. Refer to “The RMVMware Admin Tool” (page 32) for instructions on
accessing the RMVMware Admin Tool and “Plug-in Registration” (page 35) for instructions
on 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 vSphere
does 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 Mode
The HP 3PAR Management Plug-in supports a feature of VMware known as Linked Mode and
allows 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 Mode
environment:
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 storage system(s).
a. Go to Home Page and click the HP 3PAR Management Plug-in and Recovery Manager
Software for VMware vSphere. This opens to the storage system home page for one of
the vCenters.
b. Use a valid user name and password to log on to required storage systems.
28 Installing, Registering, and Uninstalling HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
5. Repeat step 4 for the remaining vCenter servers by selecting a vCenter from the drop down
list.
Figure 15 vCenter Drop Down List
NOTE: Users may require to log on to the same storage system more than once if it is connected
to 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 102) for more details about how to resolve the issue.
Viewing and Installing HP 3PAR Management Plug-in Certificate
HP 3PAR Management Plug-in uses a self-signed certificate. If a Security Alert dialog box appears
and 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 Provider
Both the vCenter Server and VASA Provider use SSL certificates. The VASA Provider support included
with 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 manually
install the SMS certificate extracted from the vCenter server onto the VASA installed host. This
process is required for every vCenter Server you intend to register with the VASA provider. The
same process is also required if the SMS certificate has a new certificate. The SMS extraction and
installation process is provided in the following section.
Viewing and Installing HP 3PAR Management Plug-in Certificate 29
Extracting the SMS Certificate
1. On vCenter Server installed host, go 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 of your
choosing:
For Windows 2008
keytool -exportcert -v -keystore "c:\Programdata\VMware\VMware
VirtualCenter\SSL\sms.keystore" -file c:\temp\sms_new.cer -alias
sms
For Windows 2003
keytool -exportcert -v -keystore "C:\Documents and Settings\All
Users\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, you should see the following type of confirmation:
“Certificate stored in file <your file path>”
Installing the SMS Certificate
You need to install the SMS certificate on the VASA Provider host's Local Computer/Trusted Root
Certification 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 Service
Perform the following steps to install the SMS certificate through the VASA web service:
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 VASA
Provider.
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 SMS
Certificate manually as described in (“Installing the SMS Certificate” (page 30)).
Installing the SMS Certificate Manually
1. Copy the certification file to the VASA installed host.
2. Right click the certification file and select Install Certificate.
30 Installing, Registering, and Uninstalling HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
Loading...