HP Application Software Suite for VMware Licenses User Manual
HP 3PAR Management Plug-in and Recovery Manager 2.5.0 Software for VMware® vSphere™ Client 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.5.0 Software for VMware®
vSphere™.
HP Part Number: QL226-96913
Published: June 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 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
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.
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.......................................................................7
Virtual Volume Details..........................................................................................................7
LUN Provisioning for Recovery Manager for VMware................................................................8
HP 3PAR Recovery Manager Software for VMware vSphere...........................................................8
TpdVmWebService..............................................................................................................8
RMWebAccess Library.........................................................................................................8
RMVMware Admin Tool........................................................................................................8
RMVMwareCLI....................................................................................................................9
RMVMware InServRegister command.................................................................................9
RMVMware vCenterRegister command............................................................................10
RMVMware Create command.........................................................................................11
RMVMware Createrc command......................................................................................14
User authentication.................................................................................................................15
VMware vCenter Server Login for HP 3PAR Virtual Volume and Virtual Copy management..........16
HP 3PAR StoreServ Storage System login..............................................................................16
HP 3PAR StoreServ Storage certificate..................................................................................16
Network ports used by HP 3PAR Management Plug-in and Recovery Manager Software for VMware
vSphere............................................................................................................................17
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere interface........17
HP 3PAR Views in the vSphere Client........................................................................................18
Datastore view...................................................................................................................18
Virtual Machine view..........................................................................................................20
ESXi host view...................................................................................................................22
Cluster view......................................................................................................................22
Datacenter view.................................................................................................................23
Virtual Copy management.......................................................................................................24
Virtual Copy data consistency.............................................................................................24
Virtual Copy policy............................................................................................................24
Datastore Virtual Copies.....................................................................................................25
Virtual Machine Virtual Copies............................................................................................25
Remote Virtual Copies........................................................................................................26
The Virtual Copy browser....................................................................................................26
VMFS snapshots................................................................................................................27
Scheduling tool..................................................................................................................28
VASA support........................................................................................................................28
2 Installing and removing HP 3PAR Management Plug-in and Recovery Manager
Software for VMware vSphere.......................................................................29
Supported platforms................................................................................................................29
Installation dependencies.........................................................................................................29
Support for VMware vCenter Server Linked mode.......................................................................29
Viewing and installing HP 3PAR Management plug-in certificate...................................................30
Registering an SMS Certificate for the VASA Provider..................................................................30
Extracting the SMS Certificate.............................................................................................31
Installing the SMS certificate................................................................................................32
Installing the SMS certificate through the VASA Web Service..............................................32
Installing SMS certificate on Windows 2008....................................................................32
Installing SMS certificate on Windows 2012/2012 R2.......................................................32
Extracting and saving certificates....................................................................................33
Contents 3
Installing and removing HP 3PAR Management plug-in and Recovery Manager Software for VMware
vSphere.................................................................................................................................33
Upgrading from a previous version...........................................................................................33
Using secure service connections.........................................................................................34
3 Modifying configuration settings using HP 3PAR RMV Admin Tool...................36
Overview..............................................................................................................................36
HP 3PAR RMV Admin Tool.......................................................................................................36
vCenter Plug-in tab..................................................................................................................36
vCenter Plug-in configuration...............................................................................................37
Plug-in registration..............................................................................................................39
Remote Copy pairs............................................................................................................40
The VASA tab........................................................................................................................41
The VASA configuration......................................................................................................41
StoreServ Credential tab..........................................................................................................43
4 Logging on and working with Virtual Volumes..............................................47
Logging on to the vSphere Client..............................................................................................47
Viewing Virtual Volume mapping..............................................................................................50
Viewing Volume information................................................................................................51
The Upper pane............................................................................................................51
The Lower pane............................................................................................................53
Refreshing Virtual Volume information........................................................................................53
Creating Virtual Volumes and Datastores...................................................................................54
Creating a Virtual Volume from an existing HP 3PAR StoreServ template...................................54
Creating a Virtual Volume from existing Datastores.................................................................58
Adding an ESXi host to the vCenter Server.................................................................................58
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..........................................................................................................64
Unmounting Virtual Copies......................................................................................................64
Restoring Datastores by promoting a Virtual Copy.......................................................................65
Deleting Virtual Copies............................................................................................................66
Modifying Virtual Copy policies...............................................................................................66
Scheduling Virtual Copies........................................................................................................68
Restoring Virtual Disks, Guest OS Files, and Directories................................................................72
Restoring a Virtual Disk.......................................................................................................72
Restoring a Guest OS File or Directory from a Virtual Copy.....................................................73
6 Working with VASA Provider......................................................................75
7 Working with Remote Copy.......................................................................78
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.......................................................82
Creating Remote Virtual Copies................................................................................................84
Setting Policy for Remote Virtual Copies.....................................................................................85
Scheduling Remote Copy Virtual Copies....................................................................................86
Mounting Remote Virtual Copies...............................................................................................89
Mounting from Virtual Copy table........................................................................................89
Mounting from Virtual Volume mapping table........................................................................90
Unmounting Remote Virtual Copies...........................................................................................91
4 Contents
Unmounting from Virtual Copy table.....................................................................................91
Unmounting from Virtual Volume Mapping table....................................................................91
Deleting Remote Virtual Copies................................................................................................91
Deleting Local Virtual Copies...................................................................................................92
Importing a Virtual Machine and reverting to a specific point-in-time Virtual Copy...........................93
8 Using HP 3PAR Peer Motion Manager Software with Recovery Manager.........94
9 Support and Other Resources.....................................................................95
Contacting HP........................................................................................................................95
HP 3PAR documentation..........................................................................................................95
Typographic conventions.........................................................................................................98
HP 3PAR branding information.................................................................................................98
10 Documentation feedback.........................................................................99
A Troubleshooting VASA Provider................................................................100
VASA Provider registration issue.............................................................................................100
Inspecting VASA Provider and vCenter Server communication.....................................................100
Alarm Type Message........................................................................................................100
Event Type Message.........................................................................................................109
B Troubleshooting for HP 3PAR Management plug-in......................................115
Resolving HP 3PAR multi-tab issue...........................................................................................115
Index.......................................................................................................116
Contents 5
1 Overview
HP Insight Control for VMware vCenter Server (Insight Control for vCenter) is a single integrated
application that you use to manage ProLiant servers and/or HP Storage Systems. The application
consists of four modules. The core module is required along with at least one of the three optional
components.
• Server Module for vCenter—Adds HP Proliant and HP BladeSystem hardware monitoring into
the vCenter Server console. Provides server hardware management capabilities, including
comprehensive monitoring, firmware update, vSphere 5.x/ESXi 5.x image deployment, remote
control, end-to-end monitoring for Virtual Connect, and power optimization for HP servers in
the VMware environment.
• Storage Module for vCenter—Provides storage configuration and status information for mapping
VMs, datastores, and hosts to LUNs on HP storage arrays.
Supports provisioning on HP 3PAR StoreServ, HP StoreVirtual, HP MSA P2000 G3, and HP
EVA Storage Systems. Supported provisioning tasks include creating, expanding, or deleting
a datastore, and creating or cloning a VM. Displays view-only information for the HP StoreOnce
Backup systems.
NOTE: If you require VASA Provider, then you must select this option.
• Recovery Manager for HP 3PAR StoreServ—The following two installation options are provided:
RMV with Plug-in integration—Installs the vSphere Client and the Web Client to perform
◦
the RMV Plug-in functionality.
◦ RMV service only—Installs the RMV target server to handle Remote Copy operations.
NOTE: Core Module provides the framework required by Server Module for vCenter and
Storage Module for vCenter. This module is mandatory and is installed by default. Therefore,
no GUI option is provided to select this Module.
Insight Control for vCenter is integrated with the vCenter management server (also known as vCenter
Server) and the vSphere Client software from VMware. VMware vCenter is used as the single point
of management for VMware virtual environments, which can consist of many standalone or clustered
vSphere configurations. The virtual environment administrator accesses the vCenter management
capabilities using the vSphere Client software.
The Insight Control for vCenter software is installed on a server or a VM and is then configured to
connect and register with a vCenter server. After Insight Control for vCenter is registered with a
vCenter Server, all vSphere Clients connected to the vCenter Server can access the Insight Control
for vCenter software.
For more information on Insight Control for vCenter, see HP Insight Control for VMware vCenter
Server User Guide.
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
VMware vSphere Management Suite has three components, VMware vCenter Server, vSphere
Client, and Web Client. vCenter Server is a web service installed on a Windows server. vSphere
Client is a Windows desktop application, and is typically downloaded from the vCenter Server.
vSphere Web Client is a web based application that can be installed using VMware vSphere. You
can perform the various functionalities using either the vSphere Client or vSphere Web Client.
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
6 Overview
Recovery Manager Software for VMware vSphere provides its own web servers. For more
information on Web Client, see the HP 3PAR Management Plug-in and Recovery Manager Software
for VMware vSphere Web Client User Guide.
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 Web client and a vSphere Client plug-in (a vSphere Client plug-in is an external Web
application configured with the vCenter Server for vSphere Clients to display their pages). 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 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 and Transparent Failover configuration details
via the HP 3PAR tab in the vSphere Client. The Transparent Failover configuration status only
displays when it is enabled via HP 3PAR Operating System Software.
Figure 1 Viewing Datastore Virtual Volumes
HP 3PAR Management Plug-in for VMware vCenter 7
See “Logging on and working with Virtual Volumes” (page 47) 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 ESXi hosts.
For more details about creating and managing virtual volumes and Datastores, see “Creating a
Virtual Volume from an existing HP 3PAR StoreServ template” (page 54)
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 “Virtual Copy management” (page 24) for additional information.
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. The 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 Copies created on 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 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 System
array. The RMWebAccess Library does not use HP 3PAR OS 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 HP 3PAR
StoreServ Storage System credential management, HP 3PAR VASA Provider configuration, and
Remote Copy paring configuration.
NOTE: Host Explorer is not associated with RMV from version 2.5 onwards. If required, you can
install Host Explorer as a separate package.
8 Overview
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 more details).
Four commands are provided through the CLI:
• RMVMware InServRegister
• RMVMware vCenterRegister
• RMVMware Create
• RMVMware Createrc
RMVMware InServRegister command
The RMVMware InServRegister command registers HP 3PAR StoreServ 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 StoreServ Storage system login name to the vCenter Server. This option
is 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 when
registering an HP 3PAR StoreServ Storage system.
NOTE: This option will not be supported in a future release.
• -remove
Removes a registered HP 3PAR StoreServ Storage system configuration.
• -display
Displays all registered HP 3PAR StoreServ Storage system credentials.
HP 3PAR Recovery Manager Software for VMware vSphere 9
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 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"
10 Overview
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
"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 ESXi hosts. The VM name should be unique across
ESXi 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. If this option is not set, the default policy
is applied.
• -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.
HP 3PAR Recovery Manager Software for VMware vSphere 11
• -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\myCred.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 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 the
Storage 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 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
12 Overview
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:\myCred.xml -inserv s124 -inservuid rmvuser
For information about creating a credential file in xml format, see “RMVMware vCenterRegister
command” (page 10).
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.
HP 3PAR Recovery Manager Software for VMware vSphere 13
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 StoreServ 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
The following options and arguments used for this command:
• -rcgroup
• -vcserver
• -vcuid
14 Overview
Remote Copy group name for which the HP 3PAR remote Virtual Copy will be created (this
parameter is case sensitive).
VMware vCenter Server name or IP address.
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 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.
NOTE: This option will not be supported in a future release.
• -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 is
registered.
NOTE: This option will not be supported in a future release.
• -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 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 15
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 provided
with access to all the domains. For Datastore access, the HP 3PAR Recovery Manager Administrator
role must be assigned at the datacenter level.
HP 3PAR StoreServ 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 StoreServ 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 onto 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→StoreServ Credential tab.
NOTE: When the VMware Sphere client initially loads the HP 3PAR plug-in page during an a
vCenter session, HP 3PAR Recovery Manager for VMware vSphere searches and identifies the
associating storage system. If the associating storage system is configured with the auto-login
option, the storage system information is also collected simultaneously. As a result, you may
experience an increase in time for the page to load and display the volume information. When
the auto-login is fully executed, all HP 3PAR pages should load according to the performance level
of the system.
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.
HP 3PAR StoreServ Storage certificate
HP 3PAR StoreServ Storage enables management of SSL certificate, and enforces certificate
validation by the host and client applications to establish a secure connection.
HP 3PAR CLI and HP 3PAR OS versions 2.3.1 MU5 P35, 3.1.1 MU3 P27, 3.1.2 MU3 P16, or
later, supports a self-signed 2048-bit RSA SSL certificate for HP 3PAR StoreServ Storage. You must
upgrade to one of these versions to enforce certificate validation. To use the SSL certificate, you
must upgrade to one of the HP 3PAR CLI and HP 3PAR OS versions that supports SSL certificate.
When the RMV web service receives a request, such as, a login request to connect to an HP 3PAR
StoreServ, it establishes a connection with the HP 3PAR StoreServ on behalf of the client. Before
establishing the connection, the RMV web service checks if a server certificate is available in the
RMV database for the HP 3PAR StoreServ. If a certificate is available, then the RMV web service
16 Overview
retrieves the saved certificate, and sends a connection request to HP 3PAR StoreServ with the
certificate details. If the HP 3PAR StoreServ certificate is the same as the one specified in the request,
and if there are no other connection issues, then a connection is successfully established.
However, if there are no saved certificates in the RMV database, then the RMV web service sends
a connect request to HP 3PAR StoreServ without the server certificate. If HP 3PAR StoreServ has a
CA (Certificate Authority) signed certificate installed on the server, then a connection is successfully
established. However, if the connection fails due to SSL certificate issue, then the RMV web service
passes the server certificate to RMV. This certificate is also displayed in the GUI. You must verify
the certificate and respond to the server by accepting or rejecting the certificate. If you reject the
certificate, then the connection process stops with an invalid server certificate error message. Else,
the RMV web service re-sends a connect request using the certificate accepted by you. If there are
no other connection issues, then the connection is successfully established. You can also save this
accepted certificate in the RMV server database. If the server certificate is not changed and is not
expired, then the connection is directly established, without any verification, when you login the
next time.
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:
The network ports used by the HP 3PAR Management Plug-in and Recovery Manager Software for
VMware vSphere are selected during installation of HP Insight Control for VMware vCenter Server.
To ensure that the same port number is used for RMV operation, you need to edit the required port
numbers during installation. For more information on the port numbers, see the HP Insight Control
for VMware vCenter Server Installation Guide.
NOTE: The TCP port numbers change based on the modules that you have selected during
installation.
Firewalls, if any, must be configured to allow traffic to these ports with the outbound connections
rule set to allow (default) 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
and Recovery Manager for VMware vSphere interface appears as shown in Figure 2 (page 18).
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.
HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere interface 17
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.
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.
• ESXi Host View - Displays all virtual volumes that are assigned to the ESXi host.
• Cluster View - Displays all virtual volumes associated with every ESXi host in the cluster.
• Datacenter View - The VMware datacenter has several ESXi hosts and Clusters. This view
displays all virtual volumes associated with every ESXi host in the datacenter.
NOTE: HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
does not support a single ESXi host mapped to multiple HP 3PAR StoreServ Storage system host
names. All WWNs for each Fiber Channel host adaptor on the same ESXi server should be used
to create a single host name on the storage system.
Datastore view
To access the Datastore view:
18 Overview
1. Under Inventory from the vSphere Client home page, click Datastores.
Figure 3 Selecting Datastores
HP 3PAR Views in the vSphere Client 19
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 view
To access the Virtual Machine (VM) view:
20 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.
HP 3PAR Views in the vSphere Client 21
ESXi host view
To access the ESXi host view:
1. Under Inventory from the vSphere Client home page, click Hosts and Clusters.
Figure 7 Selecting Hosts and Clusters
2. Select a host and then click the HP 3PAR tab.
Cluster view
To access the cluster view:
All hosts in the data center are displayed in the navigation tree.
Figure 8 Viewing Hosts in the navigation tree
Information about the virtual volumes associated with the host is displayed.
22 Overview
1. Under Inventory from the vSphere Client home page, click Hosts and Clusters (see Figure 7
(page 22)).
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 Hosts and Clusters (see Figure 3 (page 19), Figure 5 (page 21), or Figure 7 (page 22)).
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 23
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. RMV will check for an existing HP 3PAR Virtual Lock license on the
storage 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 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.
NOTE: A VM consistent Virtual Copy is always attempted if VMware Tools is installed on the
Guest OS. VMware must first successfully create a VMFS snapshot. For information on the best
practices and limitations of VMware snapshots, see the VMware knowledge base http://
kb.vmware.com/.
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 policy is independent of the policy of the
Datastore(s) of virtual disks it is using.
24 Overview
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 Copy
is deleted when a new Virtual Copy is created.
• Enable expirable Virtual Copies - Allows you to specify that created Virtual Copies are removed
according 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 is
retained.
NOTE: The Retain Virtual Copy Set option requires the HP 3PAR Virtual Lock license. RMV
will check for an existing HP 3PAR Virtual Lock license on the storage system when a Virtual
Copy is created with retention is specified. 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
available for Virtual Machine and Datastore with Virtual Machines.
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 ESXi SAN boot disk. Virtual Copy operations are not supported
on Datastores residing in ESXi 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.
Virtual Copy management 25
NOTE: A VM with a Physical RDM mapped to it is not supported for taking Application Consistent
Virtual Copy. Instead, you can take Crash Consistent Virtual Copy. However, the Virtual Copy is
not taken for the Physical RDM.
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 25).
• 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.
• 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
TCP/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 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.
26 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 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 StoreServ Storage system. It is possible that volumes shown in
the browser may not exist in the HP 3PAR StoreServ Storage system; for example, if a volume is
deleted.
For information about viewing the Virtual Copy browser, see Figure 33 (page 53).
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.
Virtual Copy management 27
Scheduling tool
You can automatically have Virtual Copies created according to a specified schedule by using the
scheduling tool (see “Scheduling Virtual Copies” (page 68) 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.
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 Datastore.
For more information on VASA, see "Storage Providers" in vCenter Server.
NOTE: The VASA support is available, only if you have selected the Storage Module during the
HP Insight Control for VMware vCenter Server installation.
28 Overview
2 Installing and removing HP 3PAR Management Plug-in
and Recovery Manager Software for VMware vSphere
This chapter describes how to install, register, remove, 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 OS Configuration Matrix. For
information about supported hardware and software platforms, refer to http://www.hp.com/go/
3par/
Installation dependencies
Ensure that the following requirements are met, before you install HP 3PAR Management Plug-in
and Recovery Manager Software for VMware vSphere:
• The HP 3PAR Recovery Manager for VMware vSphere license and the HP 3PAR Virtual Copy
license is required for Virtual Copy operation. It is mandatory that you have these license
components on the StoreServ.
• The HP 3PAR Virtual Lock license is required for setting retention policies in Virtual Copy
creation. RMV will check for an existing HP 3PAR Virtual Lock license on the Storage System
when a Virtual Copy is created with retention. However, it is not mandatory to have a Virtual
Lock licence.
• The HP 3PAR Remote Copy license is required for remote Virtual Copy operation. However,
it is not mandatory to have a HP 3PAR Remote Copy licence.
• You must have the following minimum privileges:
Edit level privilege with access to all domains (or the 3PAR_RM role)—For Virtual Copy
◦
Set operations.
◦ Browse level privilege—For Virtual Volume operations.
◦ Administrator privilege—For vCenter Server plug-in registration.
• The Virtual Machines must have VMware Tools installed to perform the Virtual Copy Set
operations with application consistency. For more information on instructions about VMware
Tools setup, see the VMware documentation.
NOTE: The current release of Recovery Manager server is not internationalized, however it
supports installation on Windows server with English, Chinese, and Japanese locale. However
operations are supported only in English.
VASA is silently installed as part of HP Insight Control for VMware vCenter Server installer. vSphere
Client must be installed using VMware vSphere. For more information on installation, registration,
removal, and upgradation, see the HP Insight Control for VMware vCenter Server Installation
Guide.
Support for VMware vCenter Server Linked mode
The HP 3PAR Management Plug-in supports the Linked Mode feature of VMware that allows you
to create and manage a Linked Mode group during or after the vCenter Server installation.
To install Recovery Manager for VMware in a Linked Mode environment, do the following:
1. Verify that the RMV server is associated with the same Active Directory domain as the vCenters.
Supported platforms 29
2. Ensure that the RMV plug-in is registered with all vCenters associated with the Linked Mode
configuration.
3. Log on to vSphere client using Active Domain user name.
4. Log on to an HP 3PAR StoreServ Storage system.
a. Navigate to the home page, and click HP 3PAR Management Plug-in and Recovery
Manager Software for VMware vSphere. The StoreServ home page for the vCenter
appears.
b. Use a valid user name and password to log on to the required StoreServ.
5. Select a vCenter from the drop-down list and repeat step 4 for the remaining vCenter servers.
NOTE: You may need to log on to the same storage system more than once if that particular
storage system 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.
To resolve HP 3PAR multi-tab issues, see “Resolving HP 3PAR multi-tab issue” (page 115).
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 a message that the certificate is not trusted, do the following to install the certificate:
1. Click View Certificate. The Certificate dialog box appears.
2. Click Install Certificate.
3. Continue to follow the Wizard instructions. Select Place All certificates in the following store
on Certificate Store page, and click Browse.
4. Select Trusted Root Certification Authorities on the Select Certificate Store dialog box, and
click OK.
5. Complete the Wizard instructions.
6. Click OK to exit the 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
30 Installing and removing HP 3PAR Management Plug-in and Recovery Manager Software for VMware vSphere
Loading...