HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere Client User Guide

Transcription

1 HP 3PAR Management Plug-in and Recovery Manager 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 Software for VMware vsphere. HP Part Number: QL Published: December 2014

2 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.

3 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...7 HP 3PAR Recovery Manager Software for VMware vsphere...8 TpdVmWebService...8 RMWebAccess Library...8 RMVMware Admin Tool...8 RMVMwareCLI...8 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...21 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 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 Installing and removing HP 3PAR Management plug-in and Recovery Manager Software for VMware vsphere...30 Upgrading from a previous version...31 Using secure service connections Modifying configuration settings using HP 3PAR RMV Admin Tool...33 Overview...33 HP 3PAR RMV Admin Tool...33 vcenter Plug-in tab...33 Contents 3

4 vcenter Plug-in configuration...34 Plug-in registration...36 Remote Copy pairs...37 StoreServ Credential tab Logging on and working with Virtual Volumes...42 Logging on to the vsphere Client...42 Viewing Virtual Volume mapping...45 Viewing Volume information...46 The Upper pane...46 The Lower pane...48 Refreshing Virtual Volume information...48 Creating Virtual Volumes and Datastores...49 Creating a Virtual Volume from an existing HP 3PAR StoreServ template...49 Creating a Virtual Volume from existing Datastores...53 Adding an ESXi host to the vcenter Server Working with Virtual Copies...55 Viewing Virtual Copy information...55 Viewing Virtual Disk Details for Virtual Copies...56 Viewing Virtual Copy event logs...57 Creating New Virtual Copies...57 Mounting Virtual Copies...59 Unmounting Virtual Copies...59 Restoring Datastores by promoting a Virtual Copy...60 Deleting Virtual Copies...61 Modifying Virtual Copy policies...61 Scheduling Virtual Copies...63 Restoring Virtual Disks, Guest OS Files, and Directories...67 Restoring a Virtual Disk...67 Restoring a Guest OS File or Directory from a Virtual Copy Working with Remote Copy...70 Registering Remote Copy Pairs...71 Updating Registered Remote Copy Pairs information...73 Viewing host information summary...73 Viewing existing and newly added Remote Copy information...74 Creating Remote Virtual Copies...76 Setting Policy for Remote Virtual Copies...77 Scheduling Remote Copy Virtual Copies...78 Mounting Remote Virtual Copies...81 Mounting from Virtual Copy table...81 Mounting from Virtual Volume mapping table...82 Unmounting Remote Virtual Copies...83 Unmounting from Virtual Copy table...83 Unmounting from Virtual Volume Mapping table...83 Deleting Remote Virtual Copies...83 Deleting Local Virtual Copies...84 Importing a Virtual Machine and reverting to a specific point-in-time Virtual Copy Using HP 3PAR Peer Motion Manager Software with Recovery Manager Support and Other Resources...87 Contacting HP...87 HP 3PAR documentation...87 Typographic conventions...90 HP 3PAR branding information Contents

5 9 Documentation feedback...91 A Troubleshooting for HP 3PAR Management plug-in...92 Resolving HP 3PAR multi-tab issue...92 Index...93 Contents 5

6 1 Overview HP OneView for VMware vcenter (formerly HP Insight Control for VMware vcenter Server) is a single integrated application that you use to manage ProLiant servers and HP storage systems. The application consists of the following modules: HP OneView for VMware vcenter Includes support for the following components: HP OneView for VMware vcenter Server Module Adds HP ProLiant and HP BladeSystem hardware monitoring into the HP OneView for vcenter 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. The Server module is not required for RMV installation. HP OneView for VMware vcenter StoreFront Module Provides storage configuration and status information for mapping VMs, datastores, and hosts to LUNs on HP storage arrays. The StoreFront Module enables you to register HP Storage arrays and use the VASA provider. Supports provisioning on HP 3PAR StoreServ, HP StoreVirtual, HP MSA, 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. Deploys the following virtual appliances: HP StoreOnce VSA HP StoreVirtual VSA HP 3PAR Recovery Manager for vcenter Installs RMV plugin with vsphere Client and vsphere Web Client integration. HP 3PAR RMV Remote Service Installs RMV target server for managing remote recovery sets. The HP OneView for vcenter software is installed on a server or a VM and is then configured to connect and register with a vcenter server. After HP OneView for vcenter is registered with a vcenter server, all vcenter clients connected to the vcenter server can access the HP OneView for vcenter software. For more information on HP OneView for VMware vcenter, see HP OneView 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. HP 3PAR Management Plug-in and 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). HP 6 Overview

7 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 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 See Logging on and working with Virtual Volumes (page 42) 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 49) HP 3PAR Management Plug-in for VMware vcenter 7

8 NOTE: NOTE: Only TPVV and CPVV provisioning are supported for this release. 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, and Remote Copy paring configuration. NOTE: Host Explorer is not associated with RMV from version 2.5 onwards. However, if you need it, you can install Host Explorer as a separate package. 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 55) for more details). 8 Overview

9 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

10 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

11 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

12 -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 55) 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 55) 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

13 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

14 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 ( ). -retention: Optional to set HP 3PAR Virtual Copy retention in hours ( ). 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 inserv s25 6 -inservuid root -remoteinserv s336 -remoteinservuid root -consistency yes 14 Overview The following options and arguments used for this command: -rcgroup Remote Copy group name for which the HP 3PAR remote Virtual Copy will be created (this parameter is case sensitive). -vcserver VMware vcenter Server name or IP address. -vcuid VMware vcenter Server log in user name.

15 -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 ( ). -retention User authentication Optional to set HP 3PAR Virtual Copy retention in hours ( ). 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

16 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 MU5 P35, MU3 P27, 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

17 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 OneView 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 OneView 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

18 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

19 1. Under Inventory from the vsphere Client home page, click Datastores. Figure 3 Selecting Datastores HP 3PAR Views in the vsphere Client 19

20 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

21 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. ESXi host view To access the ESXi host view: HP 3PAR Views in the vsphere Client 21

22 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 Cluster view 2. Select a host and then click the HP 3PAR tab. Information about the virtual volumes associated with the host is displayed. To access the cluster view: 22 Overview

23 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. Datacenter view Information about the virtual volumes associated with the cluster is displayed. 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

24 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 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

25 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 57). 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

26 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 57). 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

27 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 31 (page 48). 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

28 Scheduling tool You can automatically have Virtual Copies created according to a specified schedule by using the scheduling tool (see Scheduling Virtual Copies (page 63) 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. 28 Overview

29 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 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. vsphere Client must be installed using VMware vsphere. For more information on installation, registration, removal, and upgradation, see the HP OneView 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. 2. Ensure that the RMV plug-in is registered with all vcenters associated with the Linked Mode configuration. Supported platforms 29

30 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 products/vcenter-server/features.html. To resolve HP 3PAR multi-tab issues, see Resolving HP 3PAR multi-tab issue (page 92). 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. Installing and removing HP 3PAR Management plug-in and Recovery Manager Software for VMware vsphere The vsphere Client is installed using VMware vsphere. 30 Installing and removing HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere

31 Upgrading from a previous version When upgrading from a previous version, the installer detects whether a previous version is installed and then either performs a new install or an upgrade. Before upgrading from a previous version, consider the details provided in the following sections. You can upgrade to RMV from the versions 2.5.x and 2.6. To upgrade, follow the instructions of the Installer. For more information on installation, see the HP OneView for VMware vcenter Server Installation Guide version When upgrading from a previous version, you are prompted with the message The installer has detected that RMV 2.x is installed in this environment. Click Next to proceed further, and upgrade to RMV When HP OneView for VMware vcenter is installed, the RMV module is upgraded to version The existing data for the previous version is migrated during the upgrade. Using secure service connections RMV uses secure connections for web service and StoreServ communications. The Certificate column in the StoreServ Credential tab of Admin Tool displays the SSL certificate status for HP 3PAR StoreServ. If the displayed status is No, then you must reregister the HP 3PAR StoreServ, using the Validate option in Admin Tool. Upgrading from a previous version 31

32 CAUTION: RMV has an additional security enhancement that requires StoreServ certificate to be accepted to establish a successful connection. You are required to validate the StoreServ credentials registered through Admin Tool to accept the certificate; otherwise connections to the StoreServ will fail. NOTE: The Port number used by RMV will change as part of the upgrade and integration with HP OneView for VMware vcenter Server installation. To ensure that the same port number is used for RMV operation, you need to edit the required port numbers during installation. You can get the port numbers from the Configuration tab of vcenter Plug-in in Admin Tool. 32 Installing and removing HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere

33 3 Modifying configuration settings using HP 3PAR RMV Admin Tool Overview This chapter describes the default HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere configuration, as well as how to edit configuration settings using the HP 3PAR RMV Admin Tool. HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere is provided with default configuration settings that are compatible with most environments. However, it is recommended that you verify the default parameters and make appropriate changes as necessary. HP 3PAR RMV Admin Tool, a GUI, is provided for making the configuration changes. HP 3PAR RMV Admin Tool The HP 3PAR RMV Admin Tool is used to configure HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere, and set the storage system credentials. NOTE: To use the HP 3PAR RMV Admin Tool, you must have Administrator privileges. If you are using Windows 2008, and have User Account Control activated, then you need to right click the HP 3PAR RMV Admin Tool and launch it using the Run as Administrator option. To access the HP 3PAR RMV Admin Tool, click Start All Programs HP OneView for VMware vcenter HP 3PAR RMV Admin Tool. The configuration options are accessed through the following tabs, which are discussed in the proceeding sections: vcenter Plug-in Configures the RMV plug-in for the vcenter Server. StoreServ Credential Configures the credential information to access HP 3PAR StoreServ storage systems. vcenter Plug-in tab The vcenter Plug-in tab allows you to edit HP 3PAR Management Plug-in parameters for optimal use in your environment. You can also edit the log levels using the Admin Tool. Overview 33

34 Figure 12 vcenter Plug-in tab Details concerning the fields of the vcenter Plug-in tab are provided in the following sections. vcenter Plug-in configuration The vcenter Plug-in configuration is used to view the host name and VM service port. You can configure the debug settings here. To modify the Debug setting on the Configuration option: 34 Modifying configuration settings using HP 3PAR RMV Admin Tool

35 1. Click Edit. The Edit Configuration dialog box appears. Figure 13 vcenter Plug-in configuration NOTE: You can change the Debug level. However, to change the Recovery Manager server name or the Recovery Manager service TCP port, you must run the HP OneView for VMware vcenter installation again, to modify the settings. The Configuration tab fields are shown in Table 1 (page 35). Table 1 Configuration tab fields Group Configuration Field Recovery Manager server name Recovery Manager Server TCP port Secure service Description The network host of the server where HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere is installed. The vcenter Server and all desktops running the vsphere client using the HP 3PAR plug-in must be able to reach this server. The name is used while registering the HP 3PAR plug-in with the vcenter Server. The fully qualified name of the DNS name of the running server is the default name. The name can be changed to any name or IP address during the installation. The network port number that the TpdVmWebService Web service uses. for secure connections. This can be changed to any unused port. The TCP port numbers change based on the modules that you have selected during installation of HP OneView for VMware vcenter. HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere uses a secure Web service (using SSL certificates) securing all interactions vcenter Plug-in tab 35

36 Table 1 Configuration tab fields (continued) Group Debug Field Binded to thumbprint Debug level Log folder Description between the VMware components (vcenter Server and vsphere clients) and HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere. The SSL certificate for HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere (provided by HP) must be installed. Displays the current thumbprint binded to the TCP port. Specifies the level of verbosity of the log file. The default value is Low. The trace file name. The default file name is <system drive>:\program Files\ <HP OneView for VMware vcenter installed folder>\rmv\log. 2. Modify the fields as necessary. 3. Click Save, to save the changes. NOTE: Changing the Debug settings requires restart of the RMV service for the changed Debug settings to become effective. Plug-in registration The Plug-in Registration is used to view the current registration of the HP 3PAR plug-in with the vcenter Server. 36 Modifying configuration settings using HP 3PAR RMV Admin Tool

37 Figure 14 Plug-in registration The fields available from the Plug-in Registration tab are shown in Table 2 (page 37). Table 2 Plug-in registration fields Field vcenter Server Recovery Manager Server Name Service TCP Port Type Description The name of the vcenter Server. The name of the Recovery Manager server. The TCP port number. vsphere Client or VMware Web Client NOTE: Use HP OneView for VMware vcenter Server Administrator Portal for vcenter to register or unregister the Plug-in. Remote Copy pairs The Remote Copy Pairs option is used to manage the registration of Remote Copy pairs between a local and remote system. vcenter Plug-in tab 37

38 Figure 15 Remote Copy pairs The Remote Copy Pairs list shows currently registered storage system Remote Copy pairs. The following fields are displayed: Local StoreServ/User Name of the HP 3PAR StoreServ Storage system and the associated user. Local StoreServ Credential Windows User Windows user credentials for the accessing the local system. Remote StoreServ User Name of the remote HP 3PAR StoreServ Storage system and associated user. Remote StoreServ Credential Windows User Windows user credentials for the accessing the remote system. Remote Recovery Manager Server Remote Recovery Manager Server host identifier. To add a new Remote Copy pair registration, click Register New. The Register Remote Copy StoreServ Pair screen appears 38 Modifying configuration settings using HP 3PAR RMV Admin Tool

39 Figure 16 Register Remote Copy StoreServ pair NOTE: See the information displayed for verifying the TCP Port while Remote Copy StoreServ Pair. HP recommends to use two RMV servers (local and remote) for regular Remote Copy groups, and one RMV server (local) if the Remote Copy group is configured in Peer Persistence setup. StoreServ Credential tab The StoreServ Credential tab allows you to add, remove, and validate HP 3PAR StoreServ credentials associated with a specific Windows login account. Figure 17 StoreServ credential tab StoreServ Credential tab 39

40 You have the option of viewing all existing Windows users that have registered credentials, or you can select a specific user from the list shown in the pull down menu. A listing of registered credentials is shown for the selected users with fields defined as follows: StoreServ Name Name of the HP 3PAR StoreServ Storage system. StoreServ ID System ID for the HP 3PAR StoreServ Storage system. StoreServ User User name for accessing the HP 3PAR StoreServ Storage system. Windows User Windows user that created the credentials. Reserved By If available, displays the component for which the credentials are reserved. If the credential are cashed via the Plug-in auto login feature, then credentials are valid only for the Plug-in and are not valid for accessing any other components. To create credential for auto login purpose, the Remember Me check box must be checked when logging onto a given Storage System. Certificate If the certificate is available, then Yes is displayed, else, No. To specify a new Storage System credential: 1. Click Add. The HP 3PAR StoreServ Credential Management dialog appears. Figure 18 HP 3PAR StoreServ credential management 2. Enter the appropriate credential information for the HP 3PAR StoreServ Storage system and user including the valid password, then click OK. NOTE: When you add an HP 3PAR StoreServ with IP address, the IP address is translated to the StoreServ Name and is displayed in the StoreServ List. You can also remove or validate an entry. However, you can remove only one credential at a time. 40 Modifying configuration settings using HP 3PAR RMV Admin Tool

41 Figure 19 Accepting certificate You must accept the certificate to perform any tasks on the HP 3PAR StoreServ. However, if you do not accept the certificate, access to the HP 3PAR StoreServ is denied. 3. Click Close, to close the close the dialog box. When you add a new credential, it is associated with the current Windows user login account by default. The validation process returns the appropriate user privileges on successful connection and validation with the HP 3PAR StoreServ Storage system. When performing operations like Remote Copying from a remote system, you can deselect the Using current Windows logon user name option, and provide a specific Windows user name (domain\username) associated with the user of the remote system. CAUTION: Removing a HP 3PAR StoreServ Storage system credential that is currently used by the RMVMware CLI, Remote Copy Pairing, or the scheduler will prevent these components from operating normally. StoreServ Credential tab 41

42 4 Logging on and working with Virtual Volumes The HP 3PAR Management Plug-in for VMware vcenter is used for viewing virtual volume mapping. You can also create and expose virtual volumes to an ESXi host based on a template where you fill in the details or based on the provisioning configuration of an existing Datastore. This chapter explains how to log on to vsphere Client, view information about virtual volume mapping and Transparent Failover setup, and create new virtual volumes. NOTE: HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere supports Microsoft Internet Explorer as the Windows default browser. NOTE: When configured with secure access to the vcenter Server, the Security Information "This page contains both secure and non-secure items will be displayed. To enable the display of secure and non secure content: 1. Click Start Settings Control Panel Internet Options. 2. On the Security tab, click Custom level Miscellaneous. 3. Enable the Display Mixed content option. 4. Click OK. Logging on to the vsphere Client To start the HP 3PAR Management Plug-in for VMware vcenter: 1. Start the VMware vsphere Client on your desktop. The VMware vsphere Client login screen appears (Figure 20 (page 42)). Figure 20 Logging On to the vsphere Client 42 Logging on and working with Virtual Volumes

43 2. Log on to the vsphere Client. a. Enter the IP address or name vcenter Server. b. Enter your user name and password. c. Click Login. The vcenter Server home page appears (Figure 21 (page 43)). Figure 21 Virtual Center Home Page 3. Under Solutions and Applications, click HP 3PAR Management Plug-in and Recovery Manager for VMware vsphere. A list of storage systems associated with the ESXi host displays on the left side. Figure 22 HP 3PAR Management plug-in To update the entire Storage System list, right-click the HP 3PAR StoreServ root-entry and select the Refresh in the popup menu option. To manually add a storage system entry that is not on the list, right-click the HP 3PAR StoreServ and select connect. The HP 3PAR StoreServ connection screen appears requesting the login details. Logging on to the vsphere Client 43

44 Figure 23 HP 3PAR StoreServ connection screen 4. To connect to a specific storage system on the list, expand the list tree and click the desired system to connect or right-click the desired entry to show the popup menu and select Login. 5. Enter the appropriate information In the connect dialog box: a. Enter the HP 3PAR StoreServ system name or IP address. b. Enter the StoreServ user name and password. c. Select the Remember Me check box to prevent having to log on each time you access this system. 6. Click Login. The Summary tab shows detailed information about the selected system including the following: Figure 24 StoreServ summary 44 Logging on and working with Virtual Volumes

45 Table 3 StoreServ Information Summary General System name System model Serial number System ID System WWN Number of nodes Nodes online Logged on as Value Name of storage system Model of storage system Storage system serial number Storage system ID number World Wide Name of storage system Number of nodes available in storage system Nodes appearing online Login user NOTE: You can login to a different StoreServ credential by right-clicking the specific StoreServ, and select Logout. Logging out does not remove the cached credential for auto login. Refer User authentication (page 15) for more information. Viewing Virtual Volume mapping When logged in, you can view virtual volumes on the vcenter Server Virtual Machines (VMs) or Datastores. NOTE: You can also view virtual volumes at the datacenter, cluster, and ESXi host level. See HP 3PAR Views in the vsphere Client (page 18) for details. 1. In the main menu navigation, click Home. 2. Under Inventory, click VMs and Templates or Datastores. 3. From the navigation tree, click the specific VM or Datastore volume to view. Viewing Virtual Volume mapping 45

46 4. Click the HP 3PAR tab. The information for all virtual volumes on the selected VM or Datastore is displayed. Figure 25 Virtual Volume mapping Viewing Volume information The Upper pane After selecting a VM or Datastore, by default, all volumes on that VM or Datastore are displayed in the Virtual Volumes tab (as shown in Figure 26 (page 46)). The virtual volume information is divided into an upper and lower pane in the detail pane of the interface. The upper pane displays general volume information. The lower pane provides the following details of Virtual Volumes (default view), Paths, and Alerts. The upper pane of the Virtual Volumes tab is displayed as shown in Figure 26 (page 46). RMV detects whether or not there are multiple paths with different storage system serial numbers. The plug-in displays the VM, Datastore, or Remote Copy groups using a Peer Persistence setup as active or standby under the StoreServ column. Figure 26 Viewing the upper pane of the Virtual Volumes tab 46 Logging on and working with Virtual Volumes

47 The following filtering and sorting capabilities are provided: To filter, click the upper right corner of the column header. The virtual volume details in the lower pane of the filtered virtual volumes are displayed. Click Clear Filter to clear the selected filter. Figure 27 Filtering Virtual Volumes NOTE: The filter operation details panel may display incorrect volume details. To update the details, select a volume from the grid to remove incorrect details. You must provide both values for the filtering range. Filters are applied to the set of volumes currently displayed in the grid. If you do multiple filtering operations make sure that you clear the unwanted filter(s) before a new filter is applied. Otherwise new filter will be applied to the previously filtered result set. To sort, drag a column header to group by that column. Click the selected upper right corner of the column header to resume the default view. Figure 28 Sorting Virtual Volumes Viewing Virtual Volume mapping 47

48 The Lower pane The lower pane of the Virtual Volumes tab displays information about the selected volume in the upper pane. The lower pane provides three buttons, Details, Paths, and Alerts. Details (default when viewing the Virtual Volumes tab) displays details about the selected volume in the upper pane (Figure 29 (page 48)). In addition, all the storage systems and their paths are also displayed. When Peer Persistence is enabled, the Virtual Volumes Details pane label changes to Virtual Volume Details for Active StoreServ. Depending on the system configuration, the pane provides a status of Peer Persistence setup between an active and standby storage system. In the event of an active system failing, the host traffic directing to the failed or active storage system is redirected to the standby storage system without any disruption to the hosts using SCSI path management configurations. Figure 29 Viewing Virtual Volume details Paths displays path information about the selected volume (Figure 30 (page 48)). Figure 30 Viewing Volume Paths Alerts displays any alerts associated with the selected volume (Figure 31 (page 48)). Figure 31 Viewing alerts Refreshing Virtual Volume information A Refresh button is provided to update virtual volume information displayed in the HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere interface. The Refresh button provides two options, Reload Current Page and Update Recovery Manager Cache. Select Reload Current Page if you have logged into an HP 3PAR StoreServ Storage system and the pages do not show volume details. Select Update Recovery Manager Cache if you have logged into an HP 3PAR StoreServ Storage system and the vcenter Server inventory has changed; such as newly added Virtual Machines or Datastores, changed HBA path policies, or added ESXi hosts. 48 Logging on and working with Virtual Volumes

49 Creating Virtual Volumes and Datastores You have the option of creating a new virtual volume on the HP 3PAR StoreServ Storage system and have it exported to the vcenter managed ESXi host where it can be accessed. Creating a Virtual Volume from an existing HP 3PAR StoreServ template Follow these steps to create a new virtual volume: 1. In the main menu navigation, click Home Inventory Host and Clusters. 2. Go to the HP 3PAR Virtual Volumes. 3. Click Provision New. The Provision Storage welcome screen appears with information concerning the provisioning process. NOTE: To prevent the welcome screen from displaying in the future, select the Skip this page in the future when provisioning storage check box. 4. Click Next to select a storage system template to be used for provisioning. Figure 32 Provision Storage template selection NOTE: Only templates configured with at least TPVV or CPVV type, size, user CPG, and copy CPG from Storage Systems associated with the selected ESXi host are displayed. 5. Select an appropriate template from the list based on the summary of details, and then click Next. Creating Virtual Volumes and Datastores 49

50 Figure 33 Virtual Volume provisioning parameters 6. Provide the virtual volume parameters for the virtual volume being provisioned. An option is available to attach to a Virtual Machine when you want to create a raw disk only. Fill in the following parameters and click Next when done. Number of virtual volumes: - Number of virtual volumes to create (1 99). The default is 1. Virtual Volume name - Name for the virtual volume (1 31 characters for single volume creations or 1 26 characters for multiple volume creations). If the number of virtual volumes to be created is set to 1, the specified name is sufficient for creating the virtual volume. When creating multiple virtual volumes, a decimal number is automatically appended to the name prefix for each virtual volume that is created up to the maximum limit ( ). NOTE: When choosing a name for creating virtual volumes, you must consider the following: If the number of virtual volume count = 1, the virtual volume name is set to 31 and the Datastore name is set to 42. If number of the virtual volume count > 1, the virtual volume name prefix is set to 26 and the Datastore name prefix is set to 31. Create Datastore - Name for the Datastore (1 42 characters for single Datastore creations or 1 31 characters for multiple Datastore creations). If the number of virtual volumes to be created is set to 1, the specified name is sufficient for creating the Datastore. When creating multiple Datastores, a decimal number is automatically appended to the name prefix for each Datastore that is created up to the maximum limit ( ). NOTE: If the specified Datastore name already exists regardless of its name case, the operation will not be successful. The behavior is similar to vcenter Datastore creation. 50 Logging on and working with Virtual Volumes

51 Figure 34 Datastore parameters review VMFS-5/VMFS-3 option and Block Size - Specifies whether to use VMFS or VMFS-3. You can optionally specify the block size. VMFS-5 is only valid for ESXi 5.0 or above hosts. Size (512 MB 16 TB) - Size for the virtual volume. For VMFS-3, the VV size range is 512 MB to 2 TB, For VMFS-5, the VV size range is from 512 MB to 16 TB. When specifying the size for a virtual volume, 256 MB is reserved for each node. Depending on the cluster type, the minimum virtual volume size is calculated as 256 MB times the number of nodes. In a two node system, 512 MB is reserved when a TPVV is created. If an 80% user limit is set for a 512 MB TPVV, only 410 MB of space can be allocated. However 512 MB is the least amount required so the creation of the virtual volume fails. In other words, If the allocation limit is set, the space after the % needs to be at least 512 MB in a 2 node cluster. VV growth increment is 256 MB (i.e., If 520 MB is selected for a virtual volume, a VV size of 768 MB is automatically created. Create raw disk only Creates a raw disk when checked. By default, this option is not checked and a Datastore is automatically created. You can attach the disk to a Virtual Machine and choose either Physical or Virtual compatibility mode. Enable zero detection Select to create a zero-detect enabled VV. You can enable zero-detect when provisioning new TPVV type of virtual volumes. By default, the check box is cleared, and is visible only if you have selected a template of TPVV type in the previous screen. This feature enables HP 3PAR StoreServ to scan for zeros in the incoming write data. NOTE: The zero detection status is either Enable or Disable, depending on whether the Virtual Volume was created with or without zero-detect enabled, respectively. This status is displayed in the Virtual Volume page. Creating Virtual Volumes and Datastores 51

52 Click Next. 7. Review the parameters, then click Create. Click OK for confirmation. A confirmation is displayed indicating that the Datastore is created. NOTE: If you choose ESXi Cluster, the storage is assigned to the ESXi Cluster hosts. Otherwise, the storage is only created on the selected host. NOTE: If the selected ESXi host is connected to a storage system and currently does not have LUNs exposed to the host, you need to log in to the summary page and create an entry for the storage system. For more information, refer to HP 3PAR StoreServ Storage System login (page 16). 52 Logging on and working with Virtual Volumes

53 Creating a Virtual Volume from existing Datastores Follow these steps to create a virtual volume from an existing Datastore: 1. In the main menu navigation, click Home Inventory Datastores and Datastore Clusters. 2. Go to HP 3PAR Virtual Volumes. 3. Click Provision Similar. The Welcome page appears. NOTE: To prevent the welcome page from displaying in the future, select the Skip this page in the future when provisioning storage check box. 4. Click Next to enter the virtual volume parameters. 5. Enter the appropriate parameters, then click Next. Number of Virtual Volumes - Number of virtual volumes to be provisioned. You can specify from 1 to 99 where 1 is the default. Virtual Volume name - Name for the virtual volume. NOTE: When choosing a name for creating virtual volumes, you must consider the following: If the number of virtual volume count equals 1, the virtual volume name is set to 31 and the Datastore name is set to 42. If number of the virtual volume count is greater than 1, the virtual volume name prefix is set to 26 and the Datastore name prefix is set to 31. Create Datastore - Create a Datastore. Create raw disk only - Create a raw disk only. This parameter also allow you to attach the Virtual Volume to a Virtual Machine and choose either Physical or Virtual compatibility mode. Enable zero detection Check to create zero-detect enabled Virtual Volumes. This check box is displayed only if the Datastore selected for Provision Similar uses the TPVV type of Virtual Volume. NOTE: The zero detection status is either Enable or Disable, depending on whether the Virtual Volume was created with or without zero-detect enabled, respectively. This status is displayed in the Virtual Volume page. After you click Next, a summary of the Datastore to be created is shown: 6. Review the parameters, then click Create. Click OK for each confirmation. A confirmation is shown to indicate the Datastores are created successfully. NOTE: When creating virtual volumes from an existing Datastore, the volume allocation limit of the original virtual volume is also be applied to the newly created volume. Current operation only supports TPVV or CPVV type. Adding an ESXi host to the vcenter Server If an ESXi host with connection to HP 3PAR StoreServ Storage system is added to the vcenter Server after vsphere client is launched and the storage system does not appear on the existing HP 3PAR StoreServ Storage system list, you can manually add the StoreServ. To add a new StoreServ to the RMV cache: 1. Log on to vsphere client. 2. Go to Home Solutions and Applications HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere. Adding an ESXi host to the vcenter Server 53

54 3. Select the storage system on the node tree pane view and right-click. Select Connect from the option menu. 4. Enter the information of the storage system and click Login. 5. Verify the new storage system is added to the node tree pane. 6. Go to Home Inventory Hosts and Clusters HP 3PAR. 7. Click Refresh, select Update Recovery Manager Cache option and click Refresh. All associated HP 3PAR StoreServ Storage system virtual volume information should display. NOTE: client. Another way to refresh the internal inventory cache, close and reopen the vsphere 54 Logging on and working with Virtual Volumes

55 5 Working with Virtual Copies This chapter explains how to use HP 3PAR Recovery Manager Software for VMware vsphere to manage Virtual Copies. NOTE: In the following sections, the type of Virtual Copy being created, mounted, or modified is dependent on whether a VM or Datastore is selected from the navigation tree. For example, if you have selected a Datastore from the navigation tree, subsequent create, mount, or modify actions performed will affect the selected Datastore until a different Datastore or VM is selected. NOTE: The ability to manage Virtual Copies provided by HP 3PAR Recovery Manager Software for VMware vsphere requires the HP 3PAR Recovery Manager Software for VMware vsphere and Virtual Copy licenses. Viewing Virtual Copy information In addition to viewing virtual volumes on the vcenter Server s Virtual Machines (VMs) and Datastores when logged in, you can also view Virtual Copies. To view a VM or Datastore Virtual Copies: 1. Start the HP 3PAR Management Plug-in for VMware vcenter as described in Logging on to the vsphere Client (page 42). 2. Follow the instructions in Viewing Virtual Volume mapping (page 45). Viewing Virtual Copy information 55

56 3. Click the Virtual Copies tab. Information about the selected VM or Datastore Virtual Copies is displayed. Base Datastore/RDM LUN Type Base Volume Base ID Virtual Copy Volume Virtual Copy ID Status Can be Available, Mounted, Missing or Mismatched. NOTE: When a Virtual Copy set is displayed as Missing, the Virtual Copy has been deleted from the storage system. The delete operation is only allowed to remove the Virtual Copy. When a Virtual Copy set is displayed as Mismatched, the Virtual Copy is created on a different storage system instead of its current connected system. The mismatch may be caused by an HP 3PAR Peer Motion operation. The delete operation is only allowed to remove the record. Manually remove the actual Virtual Copy from the originating storage system. Retention Expiry Exported Host LUN ID ESXi Host Virtual Copy Datastore NOTE: The Virtual Copy timestamp displayed on the Virtual Copies tab is converted to the local time zone of the vsphere Client. The Expiry and Retention values on the same display are set to the time zone of the RMV server. NOTE: If the VV(s) used are in a Peer Persistence configuration, local Virtual Copies will be disabled. Remote Virtual Copies may be created in the Remote Copy tab. Remote Virtual Copies will create local and remote virtual copies so when failover occurs, a remote virtual copy (either local or remote) will exist for recovery purposes. Viewing Virtual Disk Details for Virtual Copies You can view details on the virtual disk associated with a Virtual Copy. Virtual Disk Shows the virtual disk name. Original Virtual Machine Name Provides additional information on the Virtual Machine name associated with the VMDK. Snapshots created prior to version 2.3 will have this field as N/A. Application Consistent Provides information on whether this VMDK is application consistent. VM Attached Shows whether the VM is attached. 56 Working with Virtual Copies

57 Viewing Virtual Copy event logs Virtual Copy operation event logs can be found at the vcenter Server level in the navigation tree, the Tasks & Events tab, and the Events tab. Use the keyword HP 3PAR to select all events performed by HP 3PAR Recovery Manager Software for VMware vsphere. Figure 35 Viewing the Virtual Copy event logs Creating New Virtual Copies Prior to creating a Virtual Copies, the following restrictions should be noted: Creating a Virtual Copy at the VM level requires available space on the Datastore where the VMDK file resides. Datastore creation from NFS drives is not supported from Virtual Copy operations. Recovery Manager for VMware vsphere requires VMFS snapshots. However, taking a VMFS snapshot of a VM participating in disk sharing, such as Microsoft MSCS, is not supported. This is a VMFS limitation. The following steps only applies to Virtual Volumes that are not Peer Persistence enabled. If Transparent Failover is enabled, use the Remote Copy page to create new Virtual Copies. See Creating Remote Virtual Copies (page 76). NOTE: Virtual Copy space must be available on the HP 3PAR Virtual Volume. In order to create a Virtual Copy on an HP 3PAR base volume, the volume must have the Virtual Copy space allocated during its creation. To create a new Virtual Copy on the VM or Datastore, perform the following: 1. Follow the instructions in Viewing Virtual Copy information (page 55). 2. Click the Virtual Copies tab. 3. Click Create. You are then asked to supply the name for the Virtual Copy set. NOTE: If you do not wish to name the Virtual Copy set, click OK. The created Virtual Copy is identified by a date and time stamp. Creating New Virtual Copies 57

58 4. (Optional) You can either accept the default name based on the time when the Virtual Copy is created, or you can enter a name of your choosing. The Virtual Copy name cannot exceed 32 characters. 5. When creating the Virtual Copy, you have the choice of changing the Ensure Application Consistency option (set by default) to specify whether or not the newly created Virtual Copy should adhere to the data standards used by supported application. Selecting this option ensures the data can be accessed with VM tools supporting these formats but may increase the amount of data space and time required to create and access the Virtual Copy. Figure 36 Ensure Application Consistency option NOTE: Application consistency is not supported on Databases that are configured using Physical Compatibility RDM LUNs. Application consistency is supported for Datastore Virtual Copy creation and you have the option to select a VM to reside on the Datastore. 6. Click OK. The Virtual Copy creation task is submitted and started. Information regarding the Virtual Copy creation process is shown under Recent Tasks in lower portion of the screen. Once the Virtual Copy has been created, an entry is reflected in the Virtual Copy Set list. NOTE: When working with Virtual Copies, you may need to refresh the display in order to view the most accurate volume details. See Refreshing Virtual Volume information (page 48). NOTE: If the Virtual Copy operation fails, refer to the event log to review details. See Viewing Virtual Copy event logs (page 57). NOTE: The system allows snapshots to be taken for more than eight VMs for application consistent Local or Remote Copy snapshots. However, if you select more than 8 VMs, a warning message is displayed and the Recovery Set creation for application consistency might fail due to the time required to quiesce the VMs. 58 Working with Virtual Copies

59 Mounting Virtual Copies To mount a Virtual Copy: 1. Follow the instructions in Viewing Virtual Copy information (page 55). 2. Click the Virtual Copies tab. 3. Select the Virtual Copy to mount from the Virtual Copy Set list. 4. Right-click the Virtual Copy in the Virtual Copy table. A menu appears providing two mount choices: Mount on ESX host as Datastore on Select from the list of ESX/ESXi hosts managed by the vcenter Server that share access to the HP 3PAR StoreServ Storage system. Mount on Proxy Host Select from a list of hosts not managed by the vcenter Server, but which have access to the HP 3PAR StoreServ Storage system. Figure 37 Mount Virtual Copies 5. Click the mount type and then select an ESX/ESXi host or Proxy Host from the menu that appears. The Confirm dialog box appears. 6. Click OK. The Virtual Copy mount task is submitted and a message indicates that the request is being processed. You can check the status column to see that the Virtual Copy has been mounted. Unmounting Virtual Copies NOTE: Recovery Manager for VMware vsphere does not check if the volume being unmounted is in use. Ensure that the volume is inactive prior to unmounting. To unmount a previously mounted Virtual Copy: 1. Follow the instructions in Viewing Virtual Copy information (page 55). 2. Click the Virtual Copies tab. 3. Select the Virtual Copy you wish to unmount from the Virtual Copy Set list. 4. Right-click the mounted Virtual Copy in the Virtual Copy table. 5. Click Unmount and then select the host. Mounting Virtual Copies 59

60 Figure 38 Unmounting Virtual Copies The Confirm dialog box appears. 6. Click OK. A message indicates that the request is being processed and the mounted copy is unmounted. Restoring Datastores by promoting a Virtual Copy Normal restore scenarios involve restoring virtual disk images. In a VMFS Datastore, there can be many virtual disks. Typically, you can identify the virtual disk to be restored and copy it over the old one. However, in some cases the virtual machine file system may be corrupted and all virtual disks need to be replaced. In such scenarios, promote one of the Virtual Copies to a base volume. The HP 3PAR Operating System Software supports a non-disruptive Virtual Volume conversion from a fully to thinly-provisioned or thinly to fully-provisioned Virtual Volume. Recovery Manager for VMware limits the promotion of a Virtual Copy taken before a Virtual Volume conversion. A popup message box with error message displays if the action occurs. Performing any RMV Virtual Copy operations such as creating or deleting must only occur after a Virtual Volume conversion is completed. NOTE: After a Virtual Volume conversion is complete, also update the Recovery Manager Cache to see changes if you are already logged on to the session. The RMV server does not notify the RMV plug-in for backend data changes. NOTE: If the underlying HP 3PAR volume used by the Datastore belongs to an HP 3PAR Remote Copy volume group, stop the Remote Copy volume group prior to running the Datastore promote operation. To restore a Datastore by promoting a Virtual Copy: 1. Follow the instructions in Viewing Virtual Copy information (page 55). Make sure that you are in the Datastores view as you can only promote Datastores. 2. Click the Virtual Copies tab. 3. Select the Virtual Copy that you wish to promote from the Virtual Copy Set list. 4. Click Promote. The Confirm dialog box appears. 5. Click OK. The Virtual Copy promote task is submitted and a message is displayed indicating that request is being processed. 60 Working with Virtual Copies

61 Deleting Virtual Copies To delete a Virtual Copy: 1. Follow the instructions in Viewing Virtual Copy information (page 55). 2. Click the Virtual Copies tab. 3. Select the Virtual Copy you wish to delete from the Virtual Copy Set list. 4. Click Delete. The Confirm dialog box appears. 5. Click OK. The Virtual Copy deletion task is submitted and started and you are asked to confirm your intent to delete the Virtual Copy. The Virtual Copy is then removed from the Virtual Copy Set list. Modifying Virtual Copy policies The Virtual Copy policies can be defined for a given Virtual Machine or Datastore. NOTE: This version of RMV supports virtual copy policies for remote copy groups. The primary policy is enforced on both storage systems for the primary and secondary sites. To modify the policy of a Virtual Copy: NOTE: This version supports maximum Virtual Copy creation VMs on a Datastore. However, if you create more than the maximum Virtual Copy Creation for Application-Consistency, then the following warning message appears: 1. Follow the instructions in Viewing Virtual Copy information (page 55). 2. Select the Virtual Machine or Datastore to apply a set of policies. 3. Click the Virtual Copies tab. 4. Click Policy. The policy dialog appears. a. Select the maximum number of Virtual Copy sets. Based on the order in which they are created, non-expirable Virtual Copies are deleted when they reach a position in the queue that exceeds this count. Deleting Virtual Copies 61

62 b. (Optional) Select whether to enable expirable Virtual Copies. Expirable copies are removed according to a specified schedule and are not affected by the maximum count. When enabling the expirable Virtual Copies option, you must specify the length of time (Hours or Days) from the current time that the Virtual Copies are to expire. You can set the expiry period up to 1825 days. NOTE: Expirable Virtual Copies are not included in the maximum count. When enabling expirable Virtual Copies, you also have the choice of specifying how existing non-expirable copies are handled. Delete the oldest when count reaches maximum. This is the recommended setting. Select this option if you plan to create both expirable and non-expirable Virtual Copies. All non-expirable copies (new and existing) will be counted against the maximum count with the oldest being deleted as it exceeds the maximum count. The RMVMware CLI and Scheduler have the option of overwriting the default policy. However, Virtual Copies created using the GUI interface are bound by the default policy. Phase out non-expirable Virtual Copies (Advanced). Select this option if you plan to mostly create expirable Virtual Copies and want to eventually phase out older non-expirable Virtual Copies. In this case, whenever a newer expirable Virtual Copy is created, the oldest non-expirable copy will be deleted. You can still create non-expirable Virtual Copies, as long as the aggregate count is below the policy maximum. NOTE: If all non-expirable Virtual Copies are in valid retention and have already reached the maximum count, choosing the Enable expirable Virtual Copies option with the Phase out non-expirable Virtual Copies setting will fail. If this happens, choose the Delete the oldest when count reaches maximum option instead. c. (Optional) Select a period of time to retain Virtual Copy sets. A dialog box prompts you for the number of days to retain the Virtual Copy set. i. Select the Retention Period. ii. Select Hours or Days. NOTE: Setting the retention policy requires the HP 3PAR Virtual Lock license on the HP 3PAR StoreServ Storage system. 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. NOTE: The Virtual Copy set can be retained for up to 43,800 hours or 1,825 days. NOTE: When using both the expiry and retention options, the expiry value must be equal to or greater than the retention value. 62 Working with Virtual Copies

63 d. Select whether to ensure application consistency. This option is used to create snapshots of Virtual Copy sets that adhere to data format standards used by the VMware Tools. 5. Click Save. NOTE: If new VMs are added to a Datastore, you also need to update the policy in order to make the VM application consistent. NOTE: When installing or upgrading VMware tools, you must be sure to reboot VMware on the system where it running otherwise application consistent snapshots may not be valid even though they are reported as completed successfully. This situation can also occur when the VMware tools have not been upgraded on the VM system following an upgrade of the ESXi server. The Virtual Copy policy modification task is submitted and started. An alert appears indicating that the new policy has been saved. 6. Click OK. Scheduling Virtual Copies You can automatically create Virtual Copies according to a specified schedule. To view or create a scheduled Virtual Copy task: 1. Follow the instructions in Viewing Virtual Copy information (page 55). 2. Click the Virtual Copies tab. 3. Click Scheduler. The Schedule List dialog Figure 39 (page 63) appears. Figure 39 Schedule List dialog From the Scheduled List dialog, you can add a scheduled Virtual Copy creation task or modify an existing one using the Schedule Task Wizard. To add a new scheduled Virtual Copy task, follow these steps: Scheduling Virtual Copies 63

64 1. Click Add. The Select Schedule Type dialog appears. Figure 40 Select Schedule Type dialog 2. Select the time when the scheduled copy creation task is to be performed. You have the option of scheduling when (hourly, daily, weekly, monthly) the Virtual Copy is to be created. You can also schedule a Virtual Copy creation task to occur on a one-time basis. 3. Click Next. The wizard will request the appropriate information based on the option time frame you have chosen. As an example that shows the types of information you need to supply, if you choose Weekly, the Weekly Schedule Task dialog appears. Figure 41 Weekly Schedule Task 4. Enter the start time of the day when the task is to be run and then indicate how often the task is performed in weeks. You also need to select the day(s) of the week when the task is to be run. NOTE: If the vcenter server and RMV server are in different time zones, the default date and time are based on the RMV server and vcenter server respectively. You need to synchronize the time differences when creating the schedule. 64 Working with Virtual Copies

65 5. Click Next. The Schedule Credential dialog appears. Figure 42 Schedule Credential 6. Enter a name for the scheduled task and the associated user name and password. The task name must be unique. 7. Click Next. The Snapshot Configuration dialog appears. Figure 43 Virtual Copy Configuration dialog 8. Enter the appropriate vcenter server user name and location of the credential store file. 9. Specify whether or not to use application consistency for the scheduled task. If application consistency is specified when creating the Virtual Copy for a Datastore, you have the option of applying the application consistency to all Virtual Machines by selecting the Apply to all Virtual Machines button or specify specific machines by choosing Apply to the following Virtual Machines and enter the name of the Virtual Machines. Scheduling Virtual Copies 65

66 NOTE: Use commas to separate the Virtual Machine names. 10. Enter the HP 3PAR StoreServ Storage system user name. 11. Specify any default policy overrides. a. Specify the amount of time (in hours or days) before the Virtual Copy expires. b. Specify the amount of time (in hours or days) to retain the Virtual Copy set. 12. Click Next. The Schedule Task Summary dialog appears. Figure 44 Schedule Task Summary Dialog If application consistency was specified when the Virtual Copy was created, the summary includes this information as shown. NOTE: To schedule a task for a given user, an associated vcenter Credential Store File must first be created using the RMVMware CLI with vcenterregister option. To be used with the Scheduler, the credential file must have System account level privileges. In addition, to schedule tasks for user s other than yourself, you must be added as a user to have permission to access their credential files. If the credential file is created as a domain user, specify the domain user when setting up the schedule. If a local user is to be used for the scheduler, add the local user permission to the credential file. NOTE: Tasks scheduled for a given HP 3PAR StoreServ Storage system must have an associated Storage System Credential registration completed using the RMVMware Admin Tool. In addition, since the Storage System credential registration is only accessible by the creation owner and a member of administrators, the user account must have access to the Storage System registration data. 66 Working with Virtual Copies

67 13. Click Finish to complete the scheduling of the Virtual Copy task. A message indicates whether the task has been created successfully. A listing for the scheduled task is now shown in the Schedule List. Figure 45 Schedule list with task NOTE: If a VM or Datastore is removed, the associated scheduled tasks continues to run but is no longer manageable from the HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere scheduling interface. In this case, the task needs to be manually removed from the Windows Scheduler. NOTE: If the username associated with the user that created a scheduled task changes, the defined task is no longer operational. NOTE: To be used in the scheduler, users must have the proper credentials created through the vcenter Credential Store File using RMVMware CLI with the vcenterregister option and have a valid Storage System Credential registration established through the Admin Tool. NOTE: Since Storage System credential registration is only accessible by the creation owner and members of Administrator, user accounts used in the scheduler have to have access to the registration data. NOTE: Any user account that is used in the scheduler requires access permission to the specified vcenter Store file. Restoring Virtual Disks, Guest OS Files, and Directories The basic restore functionality provided in HP 3PAR Recovery Manager Software for VMware vsphere is the ability to mount all, or some, Virtual Copy volumes on one or more ESXi hosts. You can perform an actual restore by copying virtual disk images, or by mounting virtual disks on VMs for guest OS level restore, by using already available VMware tools, most of which are integrated with the vsphere Client. However, Recovery Manager for VMware vsphere also provides two commands to simplify some of the commonly used restore user cases. Restoring a Virtual Disk After a Datastore Virtual Copy has been mounted on an ESXi host (see Mounting Virtual Copies (page 59), the virtual disks grid displays the context menu. NOTE: When copying or cloning a Virtual Machine (VM) to a different Datastore, the source VM s Universally Unique Identifier (UUID) is retained in the target VM. When using HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere to show the Virtual Copies on the target VM, the Virtual Copies from the source VM will be displayed. To resolve this problem, the target VM s UUID should be changed. Refer to VMware documentation on how to edit the VM s UUID. Restoring Virtual Disks, Guest OS Files, and Directories 67

68 1. Right-click the virtual disk you wish to copy to a Datastore and click Copy to Datastore. NOTE: When using the Copy to Datastore option to copy a virtual disk to a Datastore, it is recommended that the copy and paste functions of the Datastore browser be used in order to preserve the VMware Thin Provisioning disk feature. 2. Select a Datastore on the ESXi host where the Virtual Copy is mounted. 3. Specify the target location and click OK. Figure 46 Specifying the target location The copying operation is initiated. Figure 47 Initiating the Copy Operation Restoring a Guest OS File or Directory from a Virtual Copy The second context menu command available in virtual disks grid allows you to attach a virtual disk available on the selected Virtual Copy to any of the VMs currently running on the ESXi host where the Virtual Copy is mounted. 1. Right-click the virtual disk you wish to attach and click Mount on Virtual Machine. 2. Select a VM on the ESXi host where the Virtual Copy is mounted. 3. When prompted for confirmation, click OK. 4. Once the task is completed, verify that the selected VM appears under the VM Attached column. The remainder of the restore operation must be performed on the VM. This involves re-scanning for new disks and mounting the file system, and then manually copying the files. Once the restore is complete, the virtual disk can be unmounted from the VM. 5. Right-click the virtual disk to be unmounted and click Unmount from Virtual Machine <VM name>. 68 Working with Virtual Copies

69 6. When prompted for confirmation, click OK. The unmount commences. Virtual disks created using HP 3PAR Virtual Copy can be mounted on any VM. However, if you try to mount the Virtual Copy virtual disk on the same VM, the vsphere Client displays a prompted question message. In this case, you can choose whether to continue or not. Restoring Virtual Disks, Guest OS Files, and Directories 69

70 6 Working with Remote Copy A Remote Copy feature is now available for you to create and manage both Synchronous or Periodic Virtual Copies at the RC Group level. In addition, the Remote Copy feature provides a GUI interface and basic CLI command functionality to register, create, schedule, update and remove Remote Copy pairings. NOTE: The system allows snapshots to be taken for more than eight VMs for application consistent Local or Remote Copy snapshots. However, if you select more than 8 VMs, a warning message is displayed and the Recovery Set creation for application consistency might fail due to the time required to quiesce the VMs. HP 3PAR Recovery Manager for VMware software supports Peer Persistence between multiple servers through synchronized Remote Copy. The existing Remote Copy disaster recovery functionality in synchronous mode compliments a Peer Persistence setup by including an automatic volume creation on the secondary array when a primary volume is added to a group. Both the primary and secondary clusters provide a path to an ESXi host virtual volume with the same world-wide-name. The primary Remote Copy group provides the active path while the secondary Remote Copy group provides a passive path to targeted virtual volume. When Virtual Volumes are using Peer Persistence, RMV blocks the local Virtual Volume creation for Virtual Machines and Datastores while allowing the creation of remote Virtual Copies on Remote Copy Groups. As a result, when an active path failovers to a different storage system, the virtual copies become available on either storage systems for restoration. For more information about establishing Peer Persistence setup, refer to the HP 3PAR Remote Copy User Guide. Use the Admin tool to register and configure Remote Copy Pairs before launching the vcenter plug-in feature to create a snapshot of your system. Ensure the following requirements are satisfied before registering a Remote Copy pair: Remote Copy configuration already exists on the storage systems. Use the HP 3PAR OS CLI or IMC GUI to create the Remote Copy configuration if they do not exists. Recovery Manager Software for VMware is already installed on the remote host situated in a remote site. Establish IP access to the remote host. You can configure the Remote Copy volume group for synchronization in one of the following modes: synchronous mode asynchronous periodic mode with replication period value set to zero CAUTION: If you set the replication period value to zero, then the Remote Copy replication is dependent on the RMV scheduler. So you must ensure that the RMV service is available all the time. 70 Working with Remote Copy

71 Registering Remote Copy Pairs 1. Launch Recovery Manager Software for VMware vsphere Admin Tool and click the HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere Admin Tool vcenter Plug-in. NOTE: If you have a single RMV server, HP recommends that you register the remote copy pairs in both directions. If you are using two RMV servers, register each direction just once on each RMV server. 2. Under the vcenter Plug-in tab, click Remote Copy Pairs tab. Figure 48 Registering Remote Copy pairs 3. Click Register New. 4. Enter the required information into the following fields for both Local and Remote systems. Click Register. Figure 49 Specifying Remote Copy pair details Registering Remote Copy Pairs 71

72 Table 4 Register Remote Copy Storage System Pair fields Local StoreServ: StoreServ username: Windows user name: Value Name of local storage system Name of user for local storage system Name of user for Microsoft Windows Remote StoreServ: StoreServ username: Windows user name: Recovery Manager server name: Recovery Manager service TCP port: Value Name of remote storage system Name of user for remote storage system Name of user for Microsoft Windows Name of remote Recovery Manager server on remote site TCP port number of remote Recovery Manager service When the registration is successful, the Plug-in displays HP 3PAR StoreServ Storage system pairing in the Remote Copy Pairs tab. NOTE: To verify the Recover Manager Service TCP port number, navigate to the Configuration tab of the vcenter Plug-in, in the Admin tool. When you upgrade the existing HP 3PAR CLI/HP 3PAR OS to a version that supports SSL certificate, then the Admin Tool fails to retrieve the information of the HP 3PAR StoreServs that are already registered. For the Admin Tool to display the HP 3PAR StoreServ details, navigate to the StoreServ Credential tab, and click Add to add the HP 3PAR StoreServ again. Also, you must add the HP 3PAR StoreServ again if the HP 3PAR StoreServ SSL certificate is changed or upgraded. 72 Working with Remote Copy

73 Updating Registered Remote Copy Pairs information 1. Launch Recovery Manager Software for VMware vsphere Admin Tool and click the HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere. 2. Click Remote Copy Pairs tab. 3. Select a Remote Copy pair from the list and click Update. 4. Select the new system information from the Local and Remote drop-down menus. If applicable, enter another RMV host name. 5. Click Update. Viewing host information summary From the vsphere Plug-in StoreServ tree pane, select a storage system, and click the Summary in the detail pane to view the information of the storage system. NOTE: If Peer Persistence is enabled, the local Virtual Copies are disabled because VC snapshots are taken both locally and remotely using Virtual Copy creation. Table 5 Storage System summary information General System name: System model: Serial number: System ID: System WWN: Number of nodes: Nodes online: Logged on as: Value Name of storage system Model of storage system Storage system serial number Storage system ID number World Wide Name of storage system Number of nodes available in storage system Nodes appearing online Login user Updating Registered Remote Copy Pairs information 73

74 Viewing existing and newly added Remote Copy information Use the vsphere Client to navigate and view registered storage system Remote Copy pairs and Remote Copy groups for local and remote systems. Launch vsphere Client, select Home at the top of navigation bar and click HP 3PAR Management Plug-in... From the HP 3PAR StoreServ Storage system tree pane, select a storage system and click the Remote Copy tab. NOTE: HP recommends setting your screen resolution height to at least 1024 pixels to view all the information. If some information cannot be seen, you can move the vertical split bar to the left or hide the Recent Task panel at the bottom. To view details of the Remote Copy Groups associated with specific storage systems, click the following tabs: Summary: The tab provides details of the Source and Target Remote Copy group name, role, Transparent Failover status, mode and operating status, and link type. Figure 50 Remote Copy Pair summary Virtual Volumes/Machines: The tab lists the source Virtual Volumes and the corresponding target Virtual Volumes name along with Peer Persistence and Sync status in the Remote Copy Group. A Peer Persistence column lists the Peer Persistence setup status of all Virtual Volumes associated with the Remote Copy Groups for Source and Target storage systems. 74 Working with Remote Copy

75 Figure 51 Virtual Volumes/Machines Virtual Copies On: The tab displays remote Virtual Copies creation and expiration dates, retention, mode, and application consistent status. The Remote Virtual Copies Mapping displays if you select a Remote Virtual Copy. Figure 52 Remote Virtual Copies On Virtual Copies On: The tab displays the details of the Remote Copy group(s) associated with Source storage system and Remote Copy Group; Target Storage System and Remote Copy Group; creation and expiration dates; and retention and application consistent status. The Virtual Volume Mapping for Virtual Copy Timestamp displays the Status, Exported Host, LUN ID, and Virtual Copy Datastore information if you select a Local Virtual Copy. You can also click the available hyperlink within the Virtual Copy table to Mount, Unmount, or Delete existing Virtual Copies of Virtual Volumes. Viewing existing and newly added Remote Copy information 75

76 Figure 53 Local Virtual Copies On Creating Remote Virtual Copies You can create either synchronous and periodic Remote Virtual Copy for Remote Copy groups associated with a specific ESXi server. Other VMs from other ESXi hosts are not shown. When creating synchronous Remote Virtual Copies, Recovery Manager creates a copy on both the local and remote array. For periodic Remote Virtual Copies, a Remote Virtual Copy is only created on the remote array. 1. Select the desired storage system in the left pane. 2. Select the Remote Copy tab. a. From the upper right window, select the Remote Copy pair. b. From the bottom right window, select the Remote Copy group. c. Click Create Remote Virtual Copy. 3. Select the desired options for the Remote Virtual Copy. Enable expirable Virtual Copies Retain Virtual Copies Create remote Virtual Copy with application consistency NOTE: If the Remote Virtual Copy for the Remote Copy group is set, the user will see the maximum number of Virtual Copies in Policy in the dialog box. 76 Working with Remote Copy

77 Figure 54 Create Remote Copy Virtual Copy 4. Click Create. 5. Click Yes to confirm. 6. Review the creation of the Virtual Copy in the Recent Tasks box at the bottom of the vsphere client. Click OK to complete. Setting Policy for Remote Virtual Copies To manage remote VCs, you can set specific expirable and retention policies for each Virtual Copy sets. Any policies set on a local storage system are also be applied to the virtual copy on remote storage system during creation time. NOTE: When the number of Virtual Copies is at the maximum limit, the oldest Virtual Copy is deleted when a new Virtual Copy is created. To set a policy for a Remote Virtual Copy: 1. From the Remote Copy tab, click Remote Virtual Copy Creation Policy. 2. Choose the maximum number of Virtual Copy sets. Use the arrows to adjust the number of sets. Setting Policy for Remote Virtual Copies 77

78 3. Check the applicable policy options: Enable expirable Virtual Copies Specify the expiration period. Click the appropriate option button relating to the handling of existing non-expirable Virtual Copies. Retain Virtual Copy Set Specify the expiration period. Figure 55 Policy dialog 4. Ensure application consistency. 5. Click Save. NOTE: After clicking Save, the process may take up to 15 minutes to complete depending on the number Virtual Copy Sets specified. Scheduling Remote Copy Virtual Copies You can schedule a Remote Copy creation task or the selected Remote Copy group systems. 1. From the Remote Copy Summary tab, click Scheduler. 2. Click Add. Figure 56 Adding Create Remote Copy Virtual Copy 78 Working with Remote Copy

79 3. Choose the scheduling options for performing Virtual Copy creation tasks. Set the parameters of the selected schedule option. Hourly Start time, Hour Daily Start time, Day Weekly Start time, Week, Day of the Week Monthly Start time, Day of Every Month One time only Start Date, Start Time Figure 57 Setting scheduled type for performing Virtual Copy creation task 4. Click Next to continue. 5. Enter the credentials to complete the scheduled tasks. Schedule task name User name Password Figure 58 Entering Schedule credential 6. Click Next to continue. Scheduling Remote Copy Virtual Copies 79

80 7. Select the schedule task settings. vcenter server user vcenter credential store file Enable expirable Virtual Copies Retain Virtual Copies Create Remote Copy Virtual Copy with application consistency Figure 59 Setting RC Virtual Copy configuration 8. Click Next to continue. 9. Review the Scheduled Task Summary before continuing. Figure 60 Reviewing Scheduled Task summary 80 Working with Remote Copy

81 10. Click Finish to exit. Mounting Remote Virtual Copies Mounting from Virtual Copy table To mount a Remote Virtual Copy: 1. Click the Remote Copy tab. 2. Choose the appropriate Remote Copy Group system. 3. Click the Virtual Copies On tab to display the list of Remote Virtual Copies. 4. Select the appropriate remote VC from the Remote VC Groups table. NOTE: If the selected Remote VC has any unmounted VVs, the Mount above the VC table is enabled. NOTE: Only remote Virtual Copies existing on the current array selected can be mounted. To mount a remote Virtual Copy onto another array, select the specific array located in the left pane. 5. Click the Mount. 6. Choose a mounting option: Mount on ESX host as Datastore Mount on Proxy host Choose a specific Proxy host. Figure 61 Remote VC Mounting options 7. Click Mount. 8. Click Yes to confirm. Click No to cancel action. Mounting Remote Virtual Copies 81

82 9. Click Ok to complete action. Figure 62 Mount Local Virtual Copy complete Mounting from Virtual Volume mapping table 1. Click the Remote Copy tab. 2. Choose the appropriate Remote Copy Group system. 3. Click the Virtual Copies On tab to display the list of Remote Virtual Copy. 4. Select the appropriate remote VC from the Virtual Volume Mapping table. NOTE: If one or more selected Remote VC has any unmounted VVs, the Mount above the VV table is enabled. 5. Click the Mount. 6. Choose a mounting option: Mount on ESX host as Datastore Mount on Proxy host Choose a specific Proxy host. 82 Working with Remote Copy