HP StoreOnce Recovery Manager Central for VMware User Guide

Size: px
Start display at page:

Download "HP StoreOnce Recovery Manager Central for VMware User Guide"

Transcription

1 HP StoreOnce Recovery Manager Central for VMware User Guide Abstract The guide is intended for VMware and database administrators who are responsible for backing up databases. This guide provides information about how to install, configure, and use HP StoreOnce Recovery Manager Central for VMware vsphere Web Client with HP 3PAR StoreServ Storage system and HP Express Protect. HP Part Number: Published: October 2015 Edition: 1.0

2 Copyright 2014, 2015 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. Links to third-party websites take you outside the HP website. HP has no control over and is not responsible for information outside HP.com. Acknowledgments Microsoft and Windows are trademarks of the Microsoft group of companies. VMware, vcenter Server, and vsphere Web Client are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Java and Oracle are registered trademarks of Oracle and/or its affiliates. All other trademarks and registered trademarks are owned by their respective owners.

3 Contents 1 Overview...6 HP StoreOnce Recovery Manager Central for VMware...6 HP StoreOnce Recovery Manager Central...6 Supported environments...7 HP OneView for VMware vcenter...7 VMware vsphere Management suite...7 User authentication...8 HP 3PAR StoreServ Storage system certificate...8 Recovery Set management...8 Recovery Set data consistency...8 Recovery Set policy...8 Datastore Recovery Sets...9 Virtual Machine Recovery Sets...10 Recovery Set browser...10 VMFS snapshots...11 Scheduling options...11 Launching RMC-V Online Help System requirements Installing HP StoreOnce RMC-V for VMware...14 Prerequisites...14 Installing the RMC-V plug-in...14 Removing the RMC-V plug-in Deploying RMC...15 Deployment dependencies...15 Prerequisites for selecting a host or cluster location to deploy an RMC instance...15 Deploying RMC using vsphere Client...16 Deploying RMC using HP OneView for VMware vcenter...16 Registering RMC Appliances...20 Modifying RMC Appliance registration details...22 Unregistering RMC Appliance...23 Re-registering RMC Appliance after changing the IP address...23 Adding network interface cards Upgrading RMC Appliances...25 Prerequisites...25 Upgrading RMC Appliance...25 Verifying the upgrade Upgrading RMV to RMC-V...27 Prerequisites...27 Importing Recovery Sets from RMV to an RMC Appliance...28 Importing Remote Recovery Set Configurations to Remote RMC Appliance...29 Importing RMV to RMC-V at Primary Site...30 Importing RMV database...31 Policy status after import Storage Administrator Portal...39 Using Storage Administrator Portal for VMware vcenter...39 Adding HP 3PAR StoreServ Storage systems...39 Adding HP Backup systems...41 Contents 3

4 8 Working with vsphere Web Client...42 Supported browsers...42 Logging on to the vsphere Web Client and viewing HP 3PAR StoreServ information Working with Recovery Sets Snapshots...48 Getting started...48 Prerequisites...49 Creating default Recovery Set policy...49 Modifying Recovery Set policies...53 Creating Recovery Sets...57 Viewing Recovery Set information...59 Viewing Virtual Disk details...60 Viewing Recovery Set event logs...61 Mounting Recovery Sets...61 Unmounting Recovery Sets...63 Attaching Recovery Sets...63 Detaching Recovery Sets...65 Restoring Virtual Machines...66 Restoring VVOL Virtual Machines...66 Deleting Recovery Sets...67 Viewing Recovery Sets...67 Scheduling Recovery Sets...68 Editing schedules...71 Removing schedules...72 Updating Recovery Manager Cache Working with Remote Recovery Sets Configurations...73 Getting started...73 Prerequisites...74 Workflow...75 RMC Remote Copy Configurations Topologies...76 Registering Remote RMC Appliances...79 Viewing Remote Recovery configurations...81 Viewing Remote Recovery Configuration information details...81 Creating policies...83 Creating Remote Recovery Sets...85 Viewing Remote Recovery Sets group details...87 Managing Remote Recovery Sets schedules...88 Adding schedules...88 Editing schedules...90 Deleting schedules...90 Viewing Source and Target StoreServ Recovery Sets...91 Managing Remote Recovery Sets...91 Mounting Remote Recovery Sets...93 Unmounting Remote Recovery Sets...95 Attaching Remote Recovery Sets...95 Detaching Remote Recovery Sets...97 Managing Remote Recovery Sets in various configurations...97 Managing Remote Recovery Sets in Peer Persistence...98 Deleting Remote Recovery Sets...98 Updating Recovery Manager Cache...99 Peer Persistence...99 Express Protect for Remote Recovery Sets Multiple RMC Appliance support for Remote Copy configurations Contents

5 11 Working with Recovery Sets Express Protect Prerequisites Types of Backups HP StoreOnce multi-node configuration Adding Express Protect systems Creating Express Protect policies Creating default Express Protect policies Creating new Express Protect policies Creating Express Protects Creating one-click Express Protect Creating VC-level Express Protect Scheduling Express Protects Modifying Express Protect schedules Viewing Express Protect details Element Recovery Technology Configuring ERT Mounting Express Protect objects Unmounting Express Protect objects Copying VMDK files to datastores Attaching VMDK files to Virtual Machines Detaching VMDK files from Virtual Machines Additional vcenter operations Managing concurrent Express Protects Types of restores Restoring from Express Protects Licensing Overview License models supported by RMC-V Licensing scenarios Using HP 3PAR Peer Motion Manager Software with RMC-V Troubleshooting Support and Other Resources Contacting HP New and changed information in this edition Typographic conventions HP 3PAR branding information Documentation feedback Glossary Index Contents 5

6 1 Overview This section provides an overview to the software applications and concepts that are used with RMC-V (HP StoreOnce Recovery Manager Central for VMware). HP StoreOnce Recovery Manager Central for VMware RMC-V for VMware is a software management plug-in designed to work with VMware vcenter Server. HP StoreOnce Recovery Manager Central Software combines the simplicity of snapshots with the reliability and cost effective retention of Express Protects. Native integration of HP 3PAR StoreServ and HP StoreOnce in a seamless, converged data protection solution removes the dependency on traditional backup software. HP RMC-V enables you to protect VMware virtual machine disks and datastores using consistent snapshots for rapid online recovery. The Express Protect feature offers data protection by facilitating Express Protect of snapshots from HP 3PAR StoreServ to HP StoreOnce. Express Protects on HP StoreOnce are self-contained volumes, deduplicated to save space, and can be used to recover back to the original or a different HP 3PAR StoreServ Storage system based on the options chosen. Administrators can access all the functionality from within the VMware vcenter Web Client. HP StoreOnce Recovery Manager Central The RMC (HP StoreOnce Recovery Manager Central) software integrates HP 3PAR StoreServ primary storage with HP StoreOnce Express Protect systems to provide a converged availability and backup service that offers an alternative to the traditional backup software. Combining the performance of StoreServ snapshots with the protection of Express Protect on StoreOnce, Recovery Manager Central enables fast, efficient, reliable, and simple protection for applications. Architecture RMC leverages HP 3PAR StoreServ snapshot technology and HP StoreOnce Catalyst to provide a scalable backup system. This backup feature facilitates direct backup of HP 3PAR StoreServ snapshots to HP StoreOnce Express Protect System without the need for third-party backup software. Snapshots backed up on StoreOnce are self-contained volumes that can be restored back to the original or different HP 3PAR StoreServ Storage system in the event of a disaster. Data protection cannot be achieved with snapshots alone. All Express Protects are deduplicated using HP StoreOnce technology. The RMC for VMware scheduler feature provides automated snapshot creation on HP 3PAR StoreServ and automated snapshot backup direct to HP StoreOnce. For more information on RMC, see the HP StoreOnce Recovery Manager Central User Guide. 6 Overview

7 Supported environments For more information on the supported hardware and software platforms, see the SPOCK for HP Storage Products (Single Point of Connectivity Knowledge) HP OneView for VMware vcenter HP OneView for VMware vcenter 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 Server Module Adds HP ProLiant and HP BladeSystem hardware monitoring into the HP OneView for VMware vcenter console. Provides server hardware management capabilities, including comprehensive monitoring, firmware update, vsphere/esxi 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. IMPORTANT: The HP OneView for VMware vcenter Server Module and the HP OneView for VMware vcenter StoreFront Module are no longer a separate installation. However, the HP OneView for VMware vcenter Server Module services do not activate unless credentials are provided. 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 for supported HP storage systems, including HP 3PAR StoreServ systems. 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. HP OneView for VMware vcenter StoreFront Module deploys the following virtual appliances: HP StoreOnce VSA HP StoreVirtual VSA HP StoreOnce Recovery Manager Central Installs the HP 3PAR plug-in for HP OneView for VMware vcenter and the Recovery Manager client. This needs a connection to the HP StoreOnce Recovery Manager Central instance. For installation instructions, see the HP OneView for VMware vcenter Installation Guide. VMware vsphere Management suite VMware vsphere Management Suite has the following components: VMware vcenter Server The VMware vcenter Server is a centralized management tool for the VMware vsphere suite. vcenter Server (VMware vcenter Server) allows management of multiple ESXi servers and also VMs (Virtual Machines) from different ESXi servers through a single console application. This can be installed on a Windows or Linux server. vsphere Client The vsphere Client is the principal interface for administering the vcenter Server and ESXi host. vsphere Web Client The vsphere Web Client is a web-based application that enables you to connect to a vcenter Server system to manage an ESXi host through a browser. This is installed during the installation of vcenter Server. You can perform the various functionalities using either the vsphere Client or vsphere Web Client. NOTE: Plug-in integration for RMC-V is available only with the vsphere Web Client. Supported environments 7

8 User authentication RMC-V is deployed as a Web Client plug-in. You must first logon to the vcenter Server before accessing the RMC-V features. VMware recommends this credential sharing for the transparent plug-in authentication. A vcenter user with system, datastore, and virtual machine administrator privileges are allowed to perform RMC-V operations. HP 3PAR StoreServ Storage system certificate HP 3PAR StoreServ Storage systems enable management of SSL certificate and enforces certificate validation by the host and client applications to establish a secure connection. For information on managing SSL certificates, see HP OneView for VMware vcenter User Guide. Recovery Set management RMC-V allows you to take virtual volume-level Recovery Sets of VMs and datastores. A datastore is created on one HP 3PAR StoreServ Storage volume. A VM can have multiple disks from one or more datastores. During VM Recovery Set creation, RMC-V identifies all the underlying HP 3PAR StoreServ Storage volumes and take Recovery Sets simultaneously for all volumes to ensure consistency. RMC-V manages this set of Recovery Sets as a single entity. Recovery Set data consistency You can create the following types of consistent recovery sets and backups from RMC-V: Crash Consistent A simple virtual volume Recovery Set without quiescing the memory blocks inside the guest OS results in a crash consistent Recovery Set of the VM. Data that is not flushed is lost, however all data written to the file system is available. Sanity checking of file system (fsck) is needed after recovery. Application Consistent Application consistency is provided for HP 3PAR snapshots of VMs for data compatibility with supported applications. To quiesce I/O on Virtual Machine, ensure that: The latest Windows updates are installed. If you have additional disks to be configured, then configure the SCSI bus per VMware KB article ( NOTE: An App consistent Recovery Set is attempted only if VMware Tools is installed on the Guest OS. VMware must first successfully create a VMFS (Virtual Machine File System) snapshot. For information on the best practices and limitations of VMware snapshots, see the VMware knowledge base Recovery Set policy RMC-V allows the creation of Recovery Set policies for VMs and datastores. Only one policy is permitted for every VM and datastore. VM and datastore policies exist independently; implying that a VM policy is independent of the policy of the datastore(s) of virtual disks it is using. RMC-V allows you to deploy multiple RMC instances on the vcenter Server. NOTE: RMC-V supports maximum eight RMC instances on a vcenter Server. 8 Overview

9 In RMC-V, the Recovery Set policy contains the following attributes: Select RMC Host Name By default this field displays the first RMC instance registered on the vcenter Server. All RMC instances registered with the vcenter Server are listed in the drop-down list. If multiple RMC Appliances are configured, it is mandatory that you first save a snapshot policy and perform other operations. When you select an RMC host name and save the snapshot policy for a VM or a datastore, the selected RMC host name becomes the active RMC instance for that VMware object. For a VM or datastore, only one RMC instance acts as an active RMC instance. Create Recovery Set (both, Backup and Snapshot) is allowed only on the active RMC instance. Recovery Sets are listed for both active and passive RMC instances. Numeric Recovery Set You can choose the number of Recovery Sets to be retained. When the number of Recovery Sets is at the maximum limit, the oldest Recovery Set is deleted automatically when a new Recovery Set is created. NOTE: The maximum number of VM or datastore Snapshots that you can create is 500. If you create more than 500 snapshots, then the oldest snapshot get deleted. However, if the oldest snapshot is mounted, then the create operation fails until the oldest snapshot is unmounted. Expiration and retain expirable Recovery Sets Enable expirable Recovery Sets Allows you to specify that the created Recovery Sets are removed according to a specified schedule and are not affected by the number of Recovery Sets created. Retain Recovery Set The supported number of hours and days that a Recovery Set is retained. NOTE: The Retain Recovery Set option requires the HP 3PAR Virtual Lock license. RMC-V will check for an existing HP 3PAR Virtual Lock license on the storage system when a Recovery Set is created with the specified retention. You can select expiration time or retention time or both. However, if you select both expiration time and retention time, then expiration time must be greater than or equal to retention time. Otherwise, the retention time is defaulted to the expiration time. Numeric and Expiration/Retention policies are mutually exclusive. For a numeric policy, if the oldest snapshot is mounted, then it cannot be deleted and the snapshot creation operation fails. Create Recovery Sets with VSS-aware application consistency This option is used to create Recovery Sets that adhere to data format standards used by Microsoft VSS for guest operating systems. This option is available for VMs and datastores. Datastore Recovery Sets A datastore is created on a fibre channel or iscsi virtual volume. During Recovery Set creation, RMC-V identifies the HP 3PAR volume used and takes a Recovery Set of the volume. RMC-V stores the details of all virtual disks and VMs available in the datastore. Recovery Set management 9

10 This feature has the following restrictions: The datastore must be exactly on one HP 3PAR StoreServ volume. A datastore that spans across more than one virtual volume is not supported. RDM virtual volumes defined in the datastore are not included in the Recovery Set. It is possible that a HP 3PAR virtual volume is used as RDM in a guest OS, which is defined in a datastore created on another HP 3PAR virtual volume. NOTE: A Recovery Set of a datastore does not include any RDM 3PAR virtual volumes. All datastore Recovery sets can be application or crash consistent. File system and/or application integrity checks must be performed in the guest OS for the crash consistent Recovery Sets after restoration. NFS (Network File System) 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. Recovery Set operations are not supported on datastores residing in ESXi SAN boot disks. Virtual Machine Recovery Sets VM configuration files are created in a datastore. Virtual disks (VMDKs) used by VMs are created on one or more datastores. In addition, a VM can use HP 3PAR volumes directly as RDM virtual disks. RMC-V identifies all HP 3PAR volumes used by a VM and creates Recovery Sets simultaneously. A list of virtual disk names and their type (RDM or VMDK) and configuration file name are also recorded in the repository during Recovery Set creation. A VM Recovery Set 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 Recovery Sets (page 9). 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 virtual volumes and third-party virtual volumes are not supported. All VM Recovery set can be application or crash consistent. File system and/or application integrity checks must be performed in the guest OS after restoration for the crash consistent Recovery Sets. VMs using NFS datastores are not permitted. VMFS file systems spanning multiple hard disk partitions to create a single logical volume are not supported. Recovery Set browser In RMC-V, every Recovery Set, VM, or datastore has its own metadata, which is used in instances where a restoration is necessary. 10 Overview

11 Figure 1 Recovery Set browser A Recovery Set of a VM or datastore has the following properties: The Recovery Set creation time. The HP 3PAR StoreServ Storage system details where Recovery Set volumes exist. The Recovery Set name (optional). The number of Recovery Set volumes in the Recovery Set. A list of pairs (source volume, Recovery Set volume). Each pair can have a list of virtual disks and/or VM names. All Recovery Sets 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 Recovery Set volumes. The data shown in the Recovery Set 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 more information on the Recovery Set browser, see the VMware documentation. VMFS snapshots To maintain an application consistent Recovery Set, a VMFS snapshot is created before creating an HP 3PAR Recovery Set and the VMFS copy is deleted after the HP 3PAR Recovery Set is created. HP 3PAR Recovery Sets and VMFS snapshots cannot coexist. HP 3PAR Recovery Set creation in VM or datastore fails if there are pre-existing VMFS snapshots for the VM. Scheduling options You can automatically have snapshots and Express Protects created according to a specific schedule by using the scheduler. You have the options to define various frequencies to schedule Recovery Set and Express Protect creation and also specify when the task needs to be performed. You can also schedule a Recovery Set and Express Protect creation task to occur on a one-time basis. Launching RMC-V Online Help To launch the RMC-V Online Help, click Administration StoreOnce RMC Configuration. The StoreOnce RMC Configuration page appears. Launching RMC-V Online Help 11

12 Figure 2 Launching RMC-V Online Help Click Help. The RMC-V Online Help appears. 12 Overview

13 2 System requirements For more information on the supported hardware and software platforms, see the SPOCK for HP Storage Products (Single Point of Connectivity Knowledge) 13

14 3 Installing HP StoreOnce RMC-V for VMware The HP StoreOnce RMC-V for VMware installer installs the RMC-V plug-in v1.2.0 in an existing installation of HP OneView for VMware vcenter. Prerequisites Be sure that HP OneView for VMware vcenter v7.7.1 is installed on the system. For installation instructions, see the HP OneView for VMware vcenter Installation Guide. Installing the RMC-V plug-in The HP StoreOnce RMC-V for VMware installer installs the RMC-V plug-in v1.2.0 and registers the plug-in with the vcenter Server. To install the RMC-V plug-in: 1. Navigate to the folder that contains the HP StoreOnce RMC-V for VMware installer and double-click it. The Introduction window of the installer appears. 2. Read the instructions on the Introduction window and click Next. 3. The Pre-installation Summary window appears. Read the instructions provided on this window and click Next. NOTE: The installer replaces any previous version of RMC-V plug-in, if any, that is already installed on the system. 4. The Final Note window appears. Click Done. NOTE: After the installation is complete, log out and log in again to the vsphere Web Client. Otherwise, vsphere Web Client continues to display the previously installed version of RMC-V plug-in. Removing the RMC-V plug-in To remove the RMC-V plug-in: 1. Click Start Control Panel Uninstall a program. All installed programs are listed. 2. Select HP StoreOnce RMCV for VMware and click Uninstall. 3. Click OK to confirm removal of RMC-V plug-in. 14 Installing HP StoreOnce RMC-V for VMware

15 4 Deploying RMC RMC is available as an OVF package for deployment. This section describes how to deploy RMC. You can perform deployment using any one of the following methods: RMC OVF package can be downloaded and deployed using vsphere Web Client or vsphere Client. NOTE: For information on downloading and deploying RMC OVF package, see the HP StoreOnce Recovery Manager Central User Guide. Be sure that you install HP OneView for VMware vcenter v7.7.1 and RMC-V Plug-in with vsphere Web Client. After installing HP OneView for VMware vcenter and installing RMC-V plug-in you must register the RMC instance. For information on registering an RMC instance, see Registering RMC Appliances (page 20). RMC OVF package can also be deployed using HP OneView for VMware vcenter. IMPORTANT: While using VMware VMDirectPath feature on ESXi Servers, issues might occur with certain HP ProLiant servers. For more information, click the customer advisory link. For information on the VMware patch that you must apply on the ESXi Server, see SPOCK. Before deploying the RMC appliance using HP OneView for VMware vcenter or using vsphere Client, make sure that the ESXi host time zone is appropriately set and synced. For more information, see Troubleshooting (page 133). Deployment dependencies Ensure that the following requirements are met before you deploy RMC: The HP StoreOnce Recovery Manager Central Base license is required to take crash-consistent snapshots of any application. This license also enables you to use the RMC REST APIs, that you can leverage to create your own application-consistent plug-ins. This license is supported across all the HP 3PAR StoreServ Storage models. The HP StoreOnce Recovery Manager Central with VMware license is required for taking VMware application-consistent snapshots. There are array-specific variants of this license. The RMC base license is not required if the application consistent license is available, since the base functionality is included within this license. If you are currently using RMV (HP 3PAR Recovery Manager for VMware vsphere) and have a valid license, you do not need to purchase any of the new RMC licenses mentioned above. Your existing RMV license is automatically detected and used with RMC-V. The HP 3PAR Virtual Lock license is required for setting retention policies in Recovery Set creation. RMC will check for an existing HP 3PAR Virtual Lock license on the HP 3PAR StoreServ Storage system when a Recovery Set is created with retention. However, it is not mandatory to have HP 3PAR Virtual Lock. You must have the following minimum privileges: Browse level privilege For virtual volume operations. Administrator privilege For vcenter Server to register the plug-in. Prerequisites for selecting a host or cluster location to deploy an RMC instance You can deploy an RMC appliance on an ESXi host or ESXi cluster. This section lists the prerequisites for selecting a host or cluster to deploy an RMC appliance. Deployment dependencies 15

16 Prerequisites for host and cluster A host or cluster must meet the following requirements if a single RMC instance is deployed: Minimum storage capacity 100 GB Minimum vram 8 GB Number of vcpus 2 NOTE: Host must be managed by a vcenter Server. If you need to deploy multiple RMC instances, make sure that you have sufficient number of virtual CPUs and RAM. The maximum number of RMC instances supported per vcenter instance is eight. HP recommends that the datastore must reside on an array that will not be managed by this instance of HP StoreOnce Recovery Manager Central. Deploying RMC using vsphere Client You can download the RMC OVF package and deploy it using VMware vsphere Client. Perform the following tasks to deploy RMC using vsphere Client: 1. Download and deploy the RMC OVF package. For information on downloading and deploying RMC OVF Package, see the HP StoreOnce Recovery Manager Central User Guide. 2. Install HP OneView for VMware vcenter v7.7.1 and RMC-V plug-in v1.2.0 to register RMC-V vsphere Web Client Plug-in. For installation instructions, see the HP OneView for VMware vcenter Installation Guide. 3. Register the RMC instance. After you deploy RMC using vsphere Client, you must manually register the RMC instance. For information on registering RMC Appliances, see Registering RMC Appliances (page 20). Deploying RMC using HP OneView for VMware vcenter This section describes how to deploy an RMC instance on an ESXi host or cluster using HP OneView for VMware vcenter. IMPORTANT: HP recommends that during the installation of HP OneView for VMware vcenter, be sure that you specify the fully qualified domain name in vcenter Server Name. If you do not specify the fully qualified domain name, RMC-V might display Web Client session initialization error. 1. Install HP OneView for VMware vcenter v7.7.1 and RMC-V plug-in v For information on installing HP OneView for VMware vcenter, see the HP OneView for VMware vcenter Installation Guide. For information on installing the RMC-V plug-in, see Installing HP StoreOnce RMC-V for VMware (page 14). 2. Log in to vsphere Web Client. 3. Click Host and Clusters. 4. Right-click a host and click All HP Management Actions Deploy HP StoreOnce RMC. The Deploy HP StoreOnce Recovery Manager Central wizard appears. 16 Deploying RMC

17 TIP: To open the Deploy HP StoreOnce Recovery Manager Central wizard, you can also click Administration StoreOnce RMC Credentials and then click Deploy HP StoreOnce Recovery Manager Central ( icon). This wizard assists you to deploy the RMC Appliance on the selected ESXi host or cluster. NOTE: If the system on which you deploy HP OneView for VMware vcenter Server is connected to Internet and if the ftp port is enabled, then the Deploy HP StoreOnce Recovery Manager Central wizard automatically fetches the latest version of the RMC Appliance from the HP ftp site and displays the version in the HP StoreOnce RMC version field. 5. Select the appropriate version from HP StoreOnce RMC version. Deploying RMC using HP OneView for VMware vcenter 17

18 6. If the required version is not available in HP StoreOnce RMC version, perform the following steps: a. Click Upload HP StoreOnce RMC. The Upload HP StoreOnce Recovery Manager Central Installer window appears in a new tab of the browser. b. Complete the tasks listed on the Upload HP StoreOnce Recovery Manager Central Installer window to upload the HP StoreOnce Recovery Manager Central installer. NOTE: The upload procedure might take some time to complete. You need to wait until the upload is complete. After successful upload: A dialog box appears indicating that the installer is successfully uploaded. Close the tab of the browser containing the Upload HP StoreOnce Recovery Manager Central Installer window. The version number of the uploaded installer appears in HP StoreOnce RMC version of the Deploy HP StoreOnce Recovery Manager Central wizard. 7. Select Accept HP End User License Agreement and click Next. The Select type window appears. 8. Select any one of the following options: HP StoreOnce RMC only Selecting this option deploys the RMC Appliance without registering it against the vcenter Server. This does not include the option to import the RMV data. HP StoreOnce RMC integrated with VMware This option is selected by default. The vcenter server is enabled The RMC Appliance is automatically registered and you need not separately register the appliance. vcenter server Lists the vcenter servers configured in HP OneView for VMware vcenter. NOTE: This list also contains the vcenter Servers that are already registered with other RMC Appliances. 9. Click Next. 10. Select the location of a host or cluster to deploy the RMC Appliance from Select location and click Next. 11. Select a datastore from the table to deploy the RMC Appliance and click Next. NOTE: The table lists only those datastores: With 100 GB or more free space That are available on a selected location (cluster or host) 18 Deploying RMC

19 12. Specify the RMC Appliance credentials and the network information in the Specify networks settings window. a. Specify the following details in the Configure new HP StoreOnce RMC Virtual Machine section: Virtual Machine name Specify a valid name for the RMC-V virtual machine. NOTE: Virtual machine can have a maximum of 24 characters consisting of alphabets (A-Z), digits (0-9), and minus sign (-). Blank spaces are not permitted as part of a name. No distinction is made between upper and lower case. The first character must be an alpha character. The last character must not be a minus sign. Underscore (_) is not a valid character. If you do not specify a name with the correct naming convention then, by default the RMC appliance assigns controller as the appliance name. Username By default the user name is Admin and you cannot change this. Password You can use the default RMC appliance password (admin)or create a new password. Confirm password Enter the same password that you have entered in the password field. b. Select a network configuration from the Specify network configuration. Enable Snapshot only Select this option for the management network to be configured only to the HP 3PAR StoreServ Storage system. Enable Snapshot and HP StoreOnce Express Protect, single network Select this option to configure a single network for both HP 3PAR StoreServ Storage system and HP StoreOnce. Enable Snapshot and HP StoreOnce Express Protect, separate networks Select this option to configure two different dedicated networks. One network for HP 3PAR StoreServ Storage system and another for HP StoreOnce. c. Perform the following actions in the Configure Network section. Select an appropriate network. Assign IP address using one of the following options: Obtain IPv4 settings automatically (DHCP) Use static IPv4 settings Enter appropriate network configuration details in the following fields: IP address Subnet mask Gateway Preferred DNS Alternate DNS IMPORTANT: While deploying RMC instances, make sure that the network configuration details are appropriately entered. If you do not enter the appropriate details, the RMC appliance fails to communicate with the vcenter Server and you will not be able to perform any RMC-V tasks. Deploying RMC using HP OneView for VMware vcenter 19

20 Deployment of RMC instances on IPv6 (Internet Protocol version 6) is not supported. 13. Click Next. The Validation page appears. System validates and displays the details. Appropriate error messages are displayed against the failed items. You are required to rectify the errors to proceed. NOTE: If you see any validation error message, see the Troubleshooting (page 133) section. 14. Click Next. The Ready to complete page appears. Read the message carefully that is displayed on this page. 15. Click Finish. IMPORTANT: 1. After deploying RMC Appliance, the appliance will boot by itself and configure automatically. This might take few minutes to complete. 2. Once the RMC Appliance is up, automatic registration of the RMC appliance is triggered, then you must perform a manual vsphere Web Client refresh to see the RMC Appliance registered in the table of the StoreOnce RMC Credentials page. 3. Log off and log in to vcenter Web Client again. Registering RMC Appliances After deploying the RMC Appliance, the instance registration with vcenter Server appears automatically if you have selected the RMC integrated with VMware option (only if deployed using HP OneView for VMware vcenter) while deploying the HP StoreOnce Recovery Manager Central instance. However, if you do not see the RMC Appliance and vcenter Server registration details in the StoreOnce RMC Credentials page, perform the following steps for manual registration. A single vcenter Server can manage maximum of eight RMC instances. NOTE: If you have deployed RMC using vsphere Client, use the default RMC login credentials Admin/admin. If you have deployed RMC using HP OneView for VMware vcenter, use the login credentials that you entered during the time of deployment. If you deploy RMC using the RMC Credentials page, then you need not register the RMC appliance. The RMC appliance registers automatically. This section provides instructions for registering the RMC Appliance from HP OneView for VMware vcenter to enable RMC-V functionality. 20 Deploying RMC

21 1. To view the registered RMC Appliances, click Administration HP Management StoreOnce RMC Credentials. The StoreOnce RMC Credentials window appears. You can view, register, edit, and unregister Recovery Manager Central instances from this window. Registering RMC Appliances 21

22 2. To register an existing RMC Appliance, click Register HP StoreOnce RMC Instance (the icon). The Register HP StoreOnce Recovery Manager Central Instance window appears. Specify the following details: 3. Click Finish. vcenter Server System populates a list of the IP address or FQDN (fully qualified domain name) of all vcenter Servers that are configured in HP OneView for VMware vcenter. NOTE: If you select a vcenter Server that is already registered with another RMC Appliance, then an error message appears, indicating that you cannot select this vcenter Server. HP StoreOnce RMC hostname/ip Specify an appropriate hostname or IP address of the RMC. HP StoreOnce RMC username Specify the user name. HP StoreOnce RMC password Specify the password of the logon user. The Security Alert dialog box appears with the certificate details. 4. Verify the certificate details. a. Click Yes if you trust the Recover Manager Central host. b. Or, click No to stop connecting to the Recover Manager Central host. 5. Log off and log in to the vsphere Web Client after successful registration of the RMC Appliance. NOTE: If you do not log off and log in from the vsphere Web Client, the following error message appears: Please add at least one RMC appliance using Administration-Recovery Manager Central Instances option. Modifying RMC Appliance registration details This section describes how to modify the username and password that are used for the RMC Appliance registration. 22 Deploying RMC 1. Click Administration HP Management StoreOnce RMC Credentials. The StoreOnce RMC Credentials window appears.

23 2. Select the StoreOnce RMC Instance that you need to modify. 3. Click Modify HP StoreOnce RMC Instance (the icon). The Modify HP StoreOnce Recovery Manager Central Instance window appears. 4. Enter the details that you need to modify in the appropriate text box listed below: HP StoreOnce RMC username HP StoreOnce RMC password 5. Click Finish. The system displays the Security Alert message. 6. Click Yes to confirm that the certificate is valid. The system verifies the credentials by connecting to RMC. NOTE: Log off and log in to vcenter Web Client again for the changes to be effective. Unregistering RMC Appliance To unregister the RMC-V instances: 1. Click Administration HP Management StoreOnce RMC Credentials. The StoreOnce RMC Credentials window appears. 2. Select an RMC instance that you need to unregister. 3. Click Unregister HP StoreOnce RMC Instance (the icon). The Unregister HP StoreOnce Recovery Manager Central Instance window appears. 4. Click OK to unregister the selected RMC instance. The RMC instance is unregistered from the Credential Store and the record related to this instance does not appear in the flex table of the vsphere Web Client. You can use this vcenter Server to register another RMC instance. NOTE: After unregistering the RMC instance, you must log off from vsphere Web Client and log in again to see the changes. Re-registering RMC Appliance after changing the IP address This section describes how to change the IP address of an RMC appliance: Unregistering RMC Appliance 23

24 1. Log in to the Web Client. 2. Click Administration HP Management StoreOnce RMC Credentials. 3. Select the RMC Instance that you need to change the IP address. 4. Unregister the RMC appliance. For information on unregistering RMC appliances, see Unregistering RMC Appliance (page 23). 5. Log off from the vsphere Web Client. 6. Log in to the RMC appliance from the RMC appliance console and change the IP address of the RMC appliance. The default username/password to log in to the RMC appliance is netconf/netconf. Use appropriate menu options to change the IP address. For more information on changing the IP address, see the HP StoreOnce Recovery Manager Central User Guide. 7. Restart the RMC appliance from the RMC GUI. To restart the RMC appliance, log in to the RMC GUI, click HP StoreOnce Recovery Manager Central Settings Action and then click Restart Appliance. NOTE: HP recommends that you must restart the RMC appliance. Otherwise, the Snapshots associated with that particular RMC appliance might not be visible. 8. Log in to the Web Client. 9. Click Administration HP Management StoreOnce RMC Credentials. Register the RMC appliance with the new IP address. For information on registering RMC instances, see Registering RMC Appliances (page 20). Adding network interface cards By default, two network interface cards (NIC) are available after the RMC Appliance is deployed. However, if required, you can add additional NICs. To add a NIC: 1. Right-click the RMC Appliance. 2. Click Edit Settings. The Edit Settings window appears. 3. Select Ethernet Adapter and click Add. The Add Hardware wizard appears. 4. Follow the instructions on the wizard to complete the task. NOTE: Use the netconf command to configure an IP address for the NIC. 24 Deploying RMC

25 5 Upgrading RMC Appliances This chapter describes the prerequisites and the procedure to upgrade an RMC Appliance from versions or to version IMPORTANT: Before upgrading, ensure that you have saved the current RMC Appliance configuration file. If the upgrade fails, you can use this file to import the original RMC Appliance configuration and retry the upgrade. For information on exporting the RMC Appliance configuration, see the Exporting a configuration file section of the HP StoreOnce Recovery Manager Central User Guide. After you upgrade to RMC Appliance v1.2.0, you will not be able to downgrade to the previous version of RMV. NOTE: You need not perform the procedures listed in this chapter if you do not have RMC Appliance 1.0 already deployed. However, if you need to deploy RMC Appliance v1.2.0 directly, see Upgrading RMV to RMC-V (page 27). Prerequisites Before you upgrade, be sure that you upgrade HP OneView for VMware vcenter from version to or later. After upgrading to HP OneView for VMware vcenter v7.7.1 and installing RMC-V plug-in v1.2.0, if StoreOnce RMC Configuration or StoreOnce RMC Credentials, or both tabs are not displayed under Administration, then restart the following services: HP OneView for vcenter UI Manager VMware vsphere Web Client IMPORTANT: When you restart the VMware vsphere Web Client service, be sure that other applications that are accessing this service are not impacted. For installation instructions, see the HP OneView for VMware vcenter Installation Guide. NOTE: Internet Explorer does not support the upgrade process. Upgrading RMC Appliance To upgrade an RMC Appliance: 1. Download the master.rpm firmware image file to the required location. 2. Log in to RMC GUI. 3. Click HP StoreOnce Recovery Manager Central Settings. 4. Click Action Upgrade Appliance. The Upgrade Appliance window appears. 5. Click Choose File to select the master.rpm file. Prerequisites 25

26 6. Click Upgrade. After successful upgrade, The Appliance is upgraded successfully message appears. NOTE: Upgrading the RMC Appliance might take approximately 45 to 60 minutes. After successful upgrade, the RMC Appliance automatically reboots. Verifying the upgrade 1. Log in to RMC GUI. 2. Click HP StoreOnce Recovery Manager Central Settings. 3. Verify that, RMC Software Revision displays in the General section. 26 Upgrading RMC Appliances

27 6 Upgrading RMV to RMC-V You can upgrade the existing RMV (HP 3PAR Management Plug-in and Recovery Manager Software for VMware ) Recovery Set Snapshots, scheduled jobs, and policies to RMC v NOTE: Read the information provided in this chapter only if you need to import the Recovery Set Snapshots, scheduled jobs, and policies from RMV v2.5.0 or later to RMC v RMV versions supported for upgrade RMV v2.5.0 or later to RMC v Upgrade is not supported, if: The virtual volumes belong to different HP 3PAR domains. The virtual volumes are part of different virtual volume sets. IMPORTANT: Prerequisites You can successfully import snapshots for any functionality that is supported in RMV and not supported in RMC. However, any operation that you perform on the migrated snapshots might fail. Importing RMV data to RMC must be done on a single RMC configuration. If you need to set up multiple RMC instances, you must import the data from RMV to the first RMC instance immediately after it is registered with HP OneView for VMware vcenter Server. After the import is successfully completed, log off and log in again to the vsphere Web Client. You can then register additional RMC instances as required. After registering the required RMC instances, make sure that you log off and log in again to the vsphere Web Client. If you have configured multi-virtual domains in HP 3PAR StoreServ Storage system, then after importing data from RMV, the Express Protect feature might not work as expected. For workaround, see the Troubleshooting (page 133) chapter. If you need to perform a vcenter upgrade, then the web session initialization might fail after the upgrade. For workaround, see the vcenter Upgrade section under the Troubleshooting (page 133) chapter. Install HP OneView for VMware vcenterv7.7.1 or later and RMC-V plug-in v1.2.0 on the Primary site. If you have a Remote Copy configuration, see Working with Remote Recovery Sets Configurations (page 73). After upgrading to HP OneView for VMware vcenter v7.7.1 and RMC-V plug-in v1.2.0, if StoreOnce RMC Configuration or StoreOnce RMC Credentials or both tabs are not displayed under Administration, then you need to restart the following services: HP OneView for vcenter UI Manager VMware vsphere Web Client Prerequisites 27

28 IMPORTANT: When you restart the VMware vsphere Web Client service, be sure that other applications that are accessing this service are not impacted. Deploy an RMC Appliance from HP OneView for VMware vcenter. For information on deploying RMC Appliances, see Deploying RMC using HP OneView for VMware vcenter (page 16). At least one snapshot must be available in each VM for the scheduler import to succeed. Table 1 (page 28) lists the tasks that you need to do to upgrade from the existing RMV to RMC Appliance. Table 1 Workflow Upgrading from RMV to RMC Appliance Step No Action Install HP OneView for VMware vcenter v7.7.1 or later. Install RMC-V plug-in v Restart the vsphere Web Client service. Deploy and register an RMC Appliance. Additional notes For information on upgrading HP OneView for VMware vcenter, see the HP OneView for VMware vcenter Installation Guide. For information on installing the RMC-V plug-in, see Installing HP StoreOnce RMC-V for VMware (page 14). For information on deploying RMC instances, see Deploying RMC (page 15). For information on registering RMC instances, see Registering RMC Appliances (page 20). 4 If you need to configure Remote Copy Configuration, then you can deploy and register a different RMC Appliance or use the local RMC appliance as Remote RMC Appliance. For information on configuring Remote Copy RMC Appliances, see Working with Remote Recovery Sets Configurations (page 73). 5 Import data from the existing RMV setup. For information on importing data from an existing RMV setup, see Importing Recovery Sets from RMV to an RMC Appliance (page 28). If you need to deploy multiple RMC Appliances, you must deploy it only after the import is complete. For information on deploying RMC Appliances, see Deploying RMC using HP OneView for VMware vcenter (page 16). Table 2 (page 28) lists the different options to import the Recovery Set Snapshots, scheduled jobs, and policies. Table 2 Import tasks Import action Importing only Recovery Sets from RMV: Importing Recovery Sets and Remote Recovery Sets from RMV: Task Click Importing Recovery Sets from RMV to an RMC Appliance (page 28). Click Importing Remote Recovery Set Configurations to Remote RMC Appliance (page 29). Importing Recovery Sets from RMV to an RMC Appliance This section describes how to import the existing RMV Recovery Set Snapshots, scheduled jobs, and policies to an RMC Appliance. 28 Upgrading RMV to RMC-V

29 NOTE: Before you import data, be sure that: You upgrade to HP OneView for VMware vcenter v7.7.1 or later. For information on upgrading, see the HP OneView for VMware vcenter Installation Guide. You install RMC-V plug-in v For information on installing the RMC-V plug-in, see Installing HP StoreOnce RMC-V for VMware (page 14). To import Recovery Sets: 1. Log in to vsphere Web Client. 2. Click Administration HP Management StoreOnce RMC Configuration. Figure 3 StoreOnce RMC Configuration 3. Click Import Data to import the Recovery Set Snapshots, scheduled jobs, and policies from the RMV to the registered RMC Appliance. NOTE: The progress of importing the data is displayed in the task monitoring window of the vcenter Server. 4. Click Track Status to view the detailed status of the imported Recovery Set Snapshots, scheduled jobs, and policies. If you initiate migration after a successful migration the following message is displayed: The migration is completed sucessfully. Importing Remote Recovery Set Configurations to Remote RMC Appliance This section describes how to import the existing RMV Remote Recovery Sets, scheduled jobs, and policies to RMC-V Importing Remote Recovery Set Configurations to Remote RMC Appliance 29

30 1. Upgrade to HP OneView for VMware vcenter or later and install RMC-V plug-in v1.2.0 on the Primary site and the Secondary site (if the Secondary site is configured). For information on upgrading HP OneView for VMware vcenter, see the HP OneView for VMware vcenter Installation Guide. For information on installing the RMC-V plug-in, see Installing HP StoreOnce RMC-V for VMware (page 14). NOTE: After upgrading to HP OneView for VMware vcenter v7.7.1 or later and installing RMC-V plug-in v1.2.0, if StoreOnce RMC Configuration tab or StoreOnce RMC Credentials tab or both tabs are not displayed under Administration, then you need to restart the following services: HP OneView for vcenter UI Manager VMware vsphere Web Client IMPORTANT: When you restart the VMware vsphere Web Client service, be sure that other applications that are accessing this service are not impacted. 2. Deploy one or more Remote RMC Appliances for your Remote Copy topology. For more information on Remote Copy topologies, see RMC Remote Copy Configurations Topologies (page 76). NOTE: Add multiple RMC appliances only after the import is complete. 3. Register the Remote RMC Appliances for your Remote Copy topology. For more information on registering remote RMC Appliances, Registering Remote RMC Appliances (page 79). Importing RMV to RMC-V at Primary Site NOTE: Before you import Remote Copy data, be sure that you have the Remote RMC Appliance(s) appropriately registered for your Remote Copy topology. For more information, see RMC Remote Copy Configurations Topologies (page 76) and Registering Remote RMC Appliances (page 79). You must configure a remote RMC Appliance for each target HP 3PAR StoreServ Storage system as per the previous RMV remote configuration. You must configure the source Storage system to the local RMC Appliance to start the import. 30 Upgrading RMV to RMC-V

31 Scenario 1: Importing a single site environment 1. From Administration, select StoreOnce RMC Configuration from the left pane. All HP 3PAR StoreServ Storage systems registered in the Storage Administrator Portal are listed. Figure 4 HP StoreOnce RMC Configuration 2. Click Import Data to begin the import of local and Remote Recovery Snapshots, Schedules, and policies to the RMC Appliance. 3. Click Track Status after the migration starts to view the import status. For more information on the import status, see Figure 8 (page 34). Importing RMV database This procedure is applicable only for scenario 2 and scenario 3 that are explained in this section. Navigate to and download the database upload tool rmcvuploadfile.exe. Scenario 2: Importing a multi-site environment (source and target storage systems are managed in multiple environments) In the existing RMV setup, you might have configured the target HP 3PAR StoreServ Storage system to a remote RMV server, that can be other than the HP OneView for VMware vcenter server. In such a scenario, the Recovery Sets are stored on the remote RMV Server database. Therefore, you must use the rmcvuploadfile.exe tool to import the Recovery Sets from the Remote RMV Server to the RMC Appliance. If in RMV, you are using a similar HP OneView for VMware vcenter server for all target HP 3PAR StoreServ Storage systems, then you need not perform the steps mentioned in this scenario (scenario 2). NOTE: It is mandatory to run the rmcvuploadfile.exe only on the remote RMV server. To upload database files from the remote RMV server to the local RMC Appliance: 1. Connect to the RMV Windows Server using Remote Desktop sharing or console. Importing Remote Recovery Set Configurations to Remote RMC Appliance 31

32 2. From the MS DoS prompt, navigate to the folder where the rmcvuploadfile.exe file is copied and run the rmcvuploadfile.exe command. Figure 5 RMC for VMware database upload tool 3. Enter the following details when prompted: a. IP address of the source RMC Appliance b. User credentials After the upload completes, the Uploaded file sucessfully to RMC Appliance message appears. 4. To upgrade HP OneView for VMware vcenter on the Primary Site: a. From Administration, select StoreOnce RMC Configuration in the left pane. b. Click Import to start the import. c. After the import starts, click Track Status to view the import status. For more information on the migration status, see Figure 8 (page 34). Scenario 3: Importing a multi-site environment (source and all target HP 3PAR StoreServ Storage systems are managed by the source and target HP OneView for VMware vcenter servers respectively) The target HP OneView for VMware vcenter is upgraded to v7.7.1 and RMC-V plug-in v1.2.0 is installed HP recommends that you upgrade the target HP OneView for VMware vcenter to v7.7.1 and then install RMC-V plug-in v NOTE: It is mandatory to execute rmcvuploadfile.exe only on the remote RMV server or the target HP OneView for VMware vcenter Windows server if it was used as a remote RMV Server. Uploading database file from remote HP OneView for VMware vcenter server to rmc 1 appliance 1. Connect to the remote HP OneView for VMware vcenter Windows Server using Remote Desktop sharing or console. 2. Stop the RMV server service if the service is running. The rmcvuploadfile.exe file displays the service name that is currently running. 32 Upgrading RMV to RMC-V

33 3. Open the MS DOS prompt and run the rmcvuploadfile.exe command. Figure 6 RMC for VMware database upload tool 4. Enter the following details when prompted: a. IP address of the source RMC Appliance b. User credentials After the upload is successfully complete, the message Uploaded file sucessfully to RMC Appliance appears. Do the following to upgrade HP OneView for VMware vcenter on the Primary Site: 1. From Administration, select StoreOnce RMC Configuration in the left pane. 2. Click Import to start the migration. Importing Remote Recovery Set Configurations to Remote RMC Appliance 33

34 3. Click Track Status after the migration starts to view the import status. Figure 7 Track Status 4. Track Status opens a log file in a new browser tab. Press F5 to refresh the status. Figure 8 Track Status file 34 Upgrading RMV to RMC-V

35 5. You can also monitor VMware vcenter tasks using the Track Status log file. Figure 9 Track Status file Importing Remote Recovery Set Configurations to Remote RMC Appliance 35

36 Policy status after import Table 3 (page 36) lists the Recovery Sets policy status before and after the import is complete. Table 3 Policy status RMV Policy for VM or datastore Numeric policy is set to N and the Create Recovery set with Application consistency check box is not selected. Numeric policy is set to N and the Create Recovery set with Application consistency check box is selected. Numeric policy is set to N and the Create Recovery set with Application consistency check box is not selected. The Enable Expirable Recovery Sets check box selected (with any of the two options). Numeric policy is set to N and the Create Recovery set with Application consistency check box selected. The Enable Expirable Recovery Sets check box is selected (with any of the two options). Numeric policy is set to N and the Create Recovery set with Application consistency check box is not selected. The Retain recovery set check box is selected. Numeric policy is set to N and the Create Recovery set with Application consistency check box is selected. The Retain recovery set check box selected. Numeric policy is set to N and the Create Recovery set with Application consistency check box is not selected. The Enable Expirable Recovery Sets check box is selected (with any of the two options). The Retain recovery set check box is selected. Numeric policy is set to N and the Create Recovery set with Application consistency check box is selected. The Expirable Recovery Sets check box is selected (with any of the two options). The Retain recovery set check box is selected. VM or datastore policy after migrating to RMC-V Numeric policy is set to N and the Create Recovery set with Application consistency check box is not selected. Numeric policy is set to N and the Create Recovery set with Application consistency check box is selected. The Create Recovery set with Application consistency check box is not selected. The Enable Expirable Recovery Sets check box selected (with any of the two options). NOTE: Numeric policy is set to N is ignored after migration. Create Recovery set with Application consistency check box is selected. The Enable Expirable Recovery Sets check box selected (with any of the two options) NOTE: Numeric policy is set to N is ignored after migration. The Create Recovery set with Application consistency check box is not selected. The Retain recovery set check box is selected. NOTE: Numeric policy is set to N is ignored after migration. The Create Recovery set with Application consistency check box is selected. The Retain recovery set check box is selected. NOTE: Numeric policy is set to N is ignored after migration. The Create Recovery set with Application consistency check box is not selected. The Expirable recovery set check box is selected (with any of the two options). The Retain recovery set check box is selected. NOTE: Numeric policy is set to N is ignored after migration. The Create Recovery set with Application consistency check box is selected. The Expirable recovery set check box is selected (with any of the two options). The Retain recovery set check box is selected. NOTE: Numeric policy is set to N is ignored after migration. 36 Upgrading RMV to RMC-V

37 Import Status To view the migration status, log in to the vsphere Web Client, and click Administration StoreOnce RMC Configuration. Click Track Status to view the status of data migration. There are two entries in Track Status output and vcenter Task list. The first entry is for the snapshot import task and second entry for the schedule job import task. The status of snapshot and schedule job import task is displayed as follows: where, The migration of virtual machine or datastore snapshot is completed successfully. success:m, failed:n, invalid:p m The count of snapshots successfully migrated. n The count of snapshots that failed to migrate. p The count of invalid snapshots. Success If snapshots/schedule job from RMV 2.5/2.6 is imported successfully into RMC v Failed If snapshots/schedule job failed to import from RMV 2.5/2.6 into RMC v1.2.0 due to missing HP 3PAR StoreServ, network issue, or any other error. Retry import operation if snapshot is not expired/deleted from HP 3PAR StoreServ Storage system. Check the error message in the Track status output and take appropriate action. Invalid The RMV 2.5/2.6 snapshots will be in invalid state and will not be imported into RMC v1.2.0 if state of snapshot in RMV 2.5/2.6 is not valid. The possible state for invalid RMV 2.5/2.6 snapshots can be any of the following: CreationFailed CreationInProgress Policy status after import 37

38 NOTE: Scheduled tasks that are in No Run state are not imported after you upgrade from RMV 2.5 or later to RMC-V v If you had selected a schedule in RMV 2.x that is a combination of Monthly and specific day of a week (for example, 2nd Tuesday), then such scheduled jobs are not imported to RMC-V v You must create a new scheduled job in RMC-V with the supported combinations. If all snapshots or scheduled jobs are not successfully imported in the first attempt, you must import it once again. However, before you import again, read the detailed status using Track Status, fix the issue, and import the failed snapshots or scheduled jobs. After you click the Track Status button, a new tab appears in the browser that displays the migration status. You must do a manual refresh on the browser to view the current import status. After you click Import, the Track Status button might disappear. After initiating data import, click on any other tab and then navigate back to StoreOnce RMC Configuration page to view the Track Status button. If you click the Import button when import is already in progress, the system displays the following error message in the task monitoring window of the vcenter Server: Please retry after sometime. The previous migration is still in progress. If you do not have a catalogue file from the previous RMV version and click Import, the system might display the following error message: Failed to download legacy RMV metadata file. Please check if vcenter is accessible. NOTE: While importing Remote Copy configurations, if you see the error message "Reason: 'Recovery Set 'None' could not be found.', then you must manually save the policy for the same remote copy group and then retry Import. For information on saving Remote Configuration Policy, see Creating policies (page 83). 38 Upgrading RMV to RMC-V

39 7 Storage Administrator Portal The Storage Administrator Portal for VMware vcenter enables you to configure Storage Systems and Backup Systems that are managed by the Storage Module for vcenter. For Storage Systems that support provisioning, use the Storage Administrator Portal to assign access permissions to storage pools. You can use the vsphere Web Client to perform storage provisioning operations, such as adding a new datastore, deleting or expanding an existing datastore, creating new VMs, or cloning existing VMs on storage pools that are set to Full Access. For more information on Storage Administrator Portal, see the HP OneView for VMware vcenter Server User Guide. RMC-V requires that all the discovered HP 3PAR StoreServ Storage systems and HP StoreOnce Express Protect systems are added to the Storage Administrator Portal for the management operations. NOTE: HP recommends that you use Internet Explorer to launch the Storage Administrator Portal. Using Storage Administrator Portal for VMware vcenter This section describes how to add HP 3PAR StoreServ Storage systems and HP Backup systems. Adding HP 3PAR StoreServ Storage systems This section describes how to add HP 3PAR StoreServ Storage systems. NOTE: If you need to configure Remote Copy, then you must separately add the required Storage systems for local and remote sites. 1. Click Start All Programs HP OneView for VMware vcenter, and then click Storage Administrator Portal for vcenter. TIP: To open HP OneView for VMware vcenter Storage Administrator Portal login page, log in to the Web Client. From the Home page, click Administration HP Management Storage Administrator Portal. Figure 10 HP OneView for VMware vcenter Storage Administrator Portal 2. Enter the user name and password and click OK. The Storage Administrator Portal for VMware vcenter appears. Figure 11 Storage Administrator Portal for VMware vcenter Using Storage Administrator Portal for VMware vcenter 39

40 3. Click Add. The Add Storage System or Management Server appears. 4. Select HP 3PAR StoreServ from Type. Add HP 3PAR StoreServ appears. 5. Specify details for the following connection parameters and click Next: Management Server User Name Password 6. The Management Server and Backup System details are displayed. Confirm the details and click Finish. 7. If the HP 3PAR StoreServ certificate changes, then the Storage Administrator Portal displays a warning message. You must accept the certificate to connect to the HP 3PAR StoreServ Storage system. 8. Click Refresh Cache to view the HP 3PAR StoreServ Storage system details that are available for the VMware vcenter Web Client. If the certificate changes, then the Storage Administrator Portal displays a warning message. NOTE: HP 3PAR StoreServ is available in VMware vcenter Web Client only after all the details pertaining to that HP 3PAR StoreServ is displayed in Storage Administrator Portal. The System model, System Firmware, and Storage Pool with access level details are displayed only after the cache is completely refreshed. After you add a new HP 3PAR StoreServ Storage system, you must ensure that the cache refresh state is completed. NOTE: When you click Refresh Cache, if the application displays the error message An error occurred while attempting to start the cache refresh, then you must restart the HP OneView for vcenter storage module service. Depending on your configuration, the time to complete Refresh Cache might vary. CAUTION: If an HP 3PAR StoreServ status is disconnected in VMware vcenter Web Client, then navigate to Storage Administrator Portal and accept the SSL certificate if any new certificates are available for the HP 3PAR StoreServ. If a Certificate Change happens at the StoreServ end, then the StoreServ is disconnected. For more information on adding Storage System or Management Server, see HP OneView for VMware vcenter Server product documentation. 40 Storage Administrator Portal

41 Adding HP Backup systems This section describes how to add HP Backup system. 1. Click Start All Programs HP OneView for VMware vcenter, and then click Storage Administrator Portal for vcenter. Figure 12 HP OneView for VMware vcenter Storage Administrator Portal 2. Enter the user name and password and click OK. The Storage Administrator Portal for VMware vcenter appears. This page displays all configured storage systems and management servers. 3. Click Add. The Add Storage System or Management Server appears. 4. Select HP StoreOnce from Type. Add HP StoreOnce window appears. 5. Specify details for the following connection parameters and click Next: Management Server <host name> or <IP> User Name Password 6. The Management Server and Backup System details are displayed. Confirm the details and click Finish. Using Storage Administrator Portal for VMware vcenter 41

42 8 Working with vsphere Web Client The RMC-V provides management of Recovery Sets, Remote Recovery Configuration of HP 3PAR Recovery Sets, recovery of VMs and datastores, and Express Protect and restore of VMs and datastores. For more information on virtual volume mapping, see HP OneView for VMware vcenter Server Product Documentation. This section explains how to log in to vsphere Web Client and view HP 3PAR StoreServ Storage information used by RMC-V. NOTE: Microsoft Internet Explorer is the default browser for vsphere Web Client. When configured with secure access to the vcenter Server, the Security Information message, This page contains both secure and non-secure items, appears. To enable the display of secure and non-secure content: 1. Click Start Settings Control Panel Network and Internet Connections Internet Options. 2. Select Security, and click Custom level. The Security Settings Internet Zone screen appears. 3. Navigate to Miscellaneous and click Display mixed content, and then select Enable. 4. Click OK. Supported browsers For information on the supported browsers for using the vsphere Web Client, see the VMware documentation. Logging on to the vsphere Web Client and viewing HP 3PAR StoreServ information To start the VMware vsphere Web Client: 1. Click Start All Programs VMware VMware vsphere Web Client vsphere Web Client. The VMware vsphere Web Client login screen appears. Figure 13 Logging on to the VMware vsphere Web Client 42 Working with vsphere Web Client

43 2. Log on to the VMware vsphere Web Client. a. Enter user name and password. b. Click Login. The VMware vsphere Web Client home page appears. Figure 14 VMware vsphere Web Client home page NOTE: If you have selected a language other than English during installation of the Operating System, then the Recent Tasks might display: the tasks and events generated from the RMC Appliance in English. the tasks and events generated from the vcenter Server in the language that you selected during installation. Logging on to the vsphere Web Client and viewing HP 3PAR StoreServ information 43

44 3. Click Administration HP Management StoreOnce RMC Configuration. TIP: You can also click HP Management Administration icon from the Administration section on the vsphere Web Client home page to view the list of Storage Systems that are associated with the ESXi host. The list of storage systems associated with the ESXi host is displayed. Figure 15 Storage list The Storage arrays listed in StoreOnce RMC Configuration might be in either of the following status: Storage system is connected. Storage system is disconnected. NOTE: Make sure that the virtual volumes from the HP 3PAR StoreServ Storage systems are mapped to the ESXi host. Otherwise, the Storage systems might not be available in connected status. NOTE: The Import Data section at the bottom of the screen is used to import Recovery Set Snapshots, scheduled jobs, and policies from the existing RMV versions. To reconnect the HP 3PAR StoreServ Storage systems in disconnected state: a. To view the recently added Storage System entry, click Launch Storage Administrator Portal. The Storage Administrator Portal for VMware vcenter appears with the updated list Storage Systems. For more information on the Storage System details, see the HP OneView for VMware vcenter Server User Guide. Figure 16 Storage Administrator Portal for VMware vcenter 44 Working with vsphere Web Client

45 NOTE: The Storage Administrator Portal enables you to configure arrays and management servers managed by the Storage Module for vcenter. For arrays that support provisioning, use the Storage Administrator Portal to assign access permissions to storage pools. Logging on to the vsphere Web Client and viewing HP 3PAR StoreServ information 45

46 b. To add an HP 3PAR StoreServ storage system, click Add... Figure 17 Add Storage System or Management Server Select HP 3PAR StoreServ from Type, and click Next. The Add HP 3PAR StoreServ page appears. i. To add an HP 3PAR StoreServ, enter the following details: Management Server Host name or IP address of the management server. User Name The name of the user. NOTE: You cannot enter root as the user name. ii. Password The password of the login user. Click Next. The HP 3PAR StoreServ certificate appears. NOTE: If you do not validate and accept the certificate, connection to HP 3PAR StoreServ is denied. iii. Click Next to accept the certificate. iv. The Management Server and Storage System details of HP 3PAR StoreServ are displayed. v. Select the appropriate access levels for each storage pool. NOTE: pools. To enable the provisioning operations, provide full access to all the Storage vi. vii. Click Finish to add HP 3PAR StoreServ storage with access to the Storage pools. The HP 3PAR StoreServ Storage will be displayed as connected in the StoreOnce RMC Configuration page. NOTE: Perform the above-mentioned steps to add a new HP 3PAR StoreServ that is not on the list. If the StoreServ list is not correctly updated, this might be caused due to the cache building delay in the background. However, if the Cache Refresh is not in progress, then click Refresh Cache to refresh the Storage Administrator Portal cache. 4. The Summary tab lists the detailed information about the selected system: 46 Working with vsphere Web Client

47 Table 4 Storage System information summary General StoreServ name StoreServ model Serial number StoreServ ID StoreServ WWN Number of nodes Nodes online Logged on as RMV server name RMV server port 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 name RMV installed server name Web service port number of Remote Recovery Manager server NOTE: If you have made any changes in the storage system (such as firmware changes), then log in to the RMC GUI, go to Storage System and refresh it from the Action menu. Logging on to the vsphere Web Client and viewing HP 3PAR StoreServ information 47

48 9 Working with Recovery Sets Snapshots Getting started What a Recovery Set Snapshot is Recovery Set Snapshot is a snapshot collection of one or more virtual volumes that reside on the HP 3PAR StoreServ used to form a VMware datastore or VM. These snapshots are also called as Virtual Copies in HP 3PAR StoreServ. A Recovery Set contains application specific metadata and is registered as a custom object in Web Client that allows relationship building between the different VMware objects. RMC-V supports Recovery Set creation at both VM and datastore levels. Prior to creating Recovery Sets, ensure that the following conditions are met: Creating a Recovery Set at the VM level requires sufficient free space on the datastore where the VMDK file resides. To create a Recovery Set on an HP 3PAR virtual volume, the Volume must have Snapshot space allocated in the storage array during its creation. Datastore creation from NFS drives is not supported for Recovery Set operations. RMC-V supports only one virtual volume per datastore. VMware Tool is required in a VM to guarantee a consistent and usable backup when application consistency is required. All existing VMFS snapshots pertaining to the VM or datastore must be removed before creating Recovery Set. Once created, Recovery Set allows you to mount individual Recovery Set to a specific ESXi host. You can further attach the mounted Volume to a selected VM as additional disk for file level restore. Recovery Sets tab The Recovery Sets tab is available under Related Objects for VMs and datastores. When you select a Recovery Set, all the Recovery Set objects associated with the selected VM or datastore is displayed. The Recovery Sets that belong to the vcenter Server are also available under Home vcenter Inventory Lists HP Infrastructure. NOTE: The Recovery Sets node that displays the Recovery Sets is removed from Home HP Infrastructure. This change is effective from RMC-V v Actions menu Actions menu support the following actions: Delete Removes the selected Recovery Set object. Restore Restores the content of the base Volume with the selected Recovery Set. This option is only available to the datastore level Recovery Set. When you run this operation, access to the base Volume is temporarily removed until the restore operation completes. The entire virtual volume is promoted to the selected point-in-time image. Update Recovery Manager Cache Refreshes the current server cache to reflect the changes in vcenter or storage array inventory objects. When you select a Recovery Set object from the list, the details pertaining to the object is displayed. 48 Working with Recovery Sets Snapshots

49 NOTE: If you make any changes in the HP 3PAR StoreServ Storage system such as, upgrading HP 3PAR OS, changing HP 3PAR licenses, and so on, then you must log in to the RMC GUI ( or <Host_name>), click HP StoreOnce Recovery Manager Central Storage System Action Menu and then click Refresh and Yes, Refresh for the changes to be effective. Create Express Protect Recovery Set Creates Express Protects of the Recovery Sets. Getting Started tab Displays information about Recovery Sets. Summary tab Displays the properties of the Recovery Set object Manage tab Displays the list of Virtual Copies and VMDKs that are contained in the set, and allows you to perform mount, unmount, attach, detach, and copy VMDK operations. Prerequisites Related Objects tab Displays the objects that are related to the Recovery Set. Both source and target HP 3PAR StoreServ Storage systems must be registered using the Storage Administrator Portal. Creating default Recovery Set policy This section describes how to define a default Recovery Set policy for a VM or datastore. NOTE: If you are using multiple RMC instances, then you must first create a default Recovery Set Policy and then proceed to create a snapshot or an Express Protect. To create the default policy for a Recovery Set: 1. Navigate to the vsphere Web Client home page. 2. Click Hosts and Clusters. 3. Select a VM and click Recovery Sets on the left navigation pane. The system displays all the available Recovery Sets in Recovery Sets under the Related Objects tab. 4. Select a VM to apply a set of policies. 5. Click Actions All HP StoreOnce Recovery Manager Actions Set Recovery Set Creation Policy, and then click Snapshot. The Default Snapshot Policy Settings screen appears. Prerequisites 49

50 Figure 18 Default Snapshot Policy Settings To modify the selected RMC instance, select the required RMC instance from the Select RMC Host Name list. After selecting a different RMC instance, it must have a new default policy created. The system does not consider the old snapshots that are created through the first RMC instance. However, snapshots of both the first and the second RMC instances are displayed. Snapshot restore can be performed using the Snapshots of any of the RMC instances. However, you must not perform the restore operations simultaneously. The following values are selected by default: Select RMC Host Name The first RMC instance that was registered on the vcenter Server is displayed by default. Numeric The default value of the number of recovery sets that you can create is five. NOTE: Numeric policy set for one RMC instance does not apply to other RMC instance to which the user moves the VM object. Each RMC instance has its own numeric policy. Creation of recovery sets is enabled with VSS-aware application consistency. 50 Working with Recovery Sets Snapshots

51 6. You can specify the following details in the Default Snapshot Policy Settings screen If Expiration /Retention is selected: Figure 19 Default Snapshot Policy Settings a. Select an appropriate RMC instance for the selected VM. NOTE: list. All RMC instances registered with the vcenter Server are listed in the drop-down b. Specify the maximum number of Recovery Sets. The maximum number of Recovery Sets that you can specify to create a policy is 500. The maximum number of snapshots supported for a VVOL numeric policy is 30. NOTE: Based on the order in which the Recovery Sets are created, the nonexpirable Recovery Sets are deleted when they reach a position in the queue that exceeds the set count. c. Select Expiration/Retention to remove the Recovery Sets according to a specified schedule. The removal of Recovery Sets are not affected by the maximum count. NOTE: The Expiration/Retention option is not available for VVOL VMs. Therefore, you can create only numeric policies for VVOL VMs. If you select Enable expirable Recovery Sets, then in Expire after you must specify the time duration in hours or days from the current time that the Recovery Sets need to expire. The maximum expiry period that you can specify for Recovery Set expiry is hours or 1825 days. Creating default Recovery Set policy 51

52 NOTE: Expirable Recovery Sets are not included in the maximum count. If you enable expirable Recovery Sets, then you must specify how the existing non-expirable copies are handled. Keep non-expirable Recovery Sets This is the default option. Phase out non-expirable Recovery Sets (Advanced) Select this option if you want to create expirable Recovery Sets and need to eventually phase out the older non-expirable Recovery Sets. Therefore, whenever a new expirable Recovery Set is created, the oldest non-expirable copy is deleted. d. Select Retain Recovery Set to retain the Recovery Sets. i. Specify 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. RMC-V checks for an existing HP 3PAR Virtual Lock license on the Storage System when a Recovery Set is created with retention specified. The maximum retention period for Recovery Sets is 43,800 hours or 1,825 days. The expiry value must be equal to or greater than the retention value, when using both the expiry and retention options. e. Select Create Recovery Set with VSS-aware application consistency to ensure application consistency. This option is used to create snapshots of Recovery Sets that adhere to data format standards used by the VMware tools. CAUTION: While installing or upgrading the VMware tools, you must reboot VMware on the system where it is running, otherwise the application consistent snapshots may not be valid even though they are reported as completed successfully. This might also occur when the VMware tools are not upgraded on the VM system, after an upgrade of the ESXi server. NOTE: If you add a new VM to a datastore, you must update the policy to ensure VM application consistency. If you add a new VM or a datastore, click Actions Update Recovery Manager Cache to refresh the Recovery Manager cache. 7. Click Save. 8. The Default Snapshot Policy Settings dialog box appears. Click Yes to save the default policy. 52 Working with Recovery Sets Snapshots

53 IMPORTANT: When you change the affinity from one RMC instance to the other, an advisory message is displayed indicating that all schedules from the earlier RMC instance for that VM or datastore to be deleted. Every time you select a different RMC instance from the Select RMC Host Name drop-down list, this dialog box appears. 9. Click OK. NOTE: You can perform a similar procedure to modify the Recovery Sets on datastores. Modifying Recovery Set policies The Recovery Set policies can be defined for a given VM or datastore. This section describes how to modify policies for Recovery Sets. To modify the policy for a Recovery Set: 1. Navigate to the vsphere Web Client home page. 2. Click Hosts and Clusters. 3. Select a VM, and then click Recovery Sets on the left navigation pane. System displays all the available Recovery Sets in Related Objects Recovery Sets. 4. Select a VM to apply a set of policies. 5. Click Actions All HP StoreOnce Recovery Manager Actions Set Recovery Set Creation Policy, and then click Snapshot. The HP StoreOnce Recovery Manager Recovery Set Management Policy screen appears. Modifying Recovery Set policies 53

54 Figure 20 Default Snapshot Policy Settings To change the selected RMC instance, navigate to the Default Snapshot Policy Settings and select the required RMC instance. After selecting a different RMC instance, it must have a new default policy created. System will not consider the old snapshots that are created through the first RMC instance. However, snapshots or Express Protects of both the first and the second RMC instance is displayed. The following features and values are selected by default: Select RMC Host Name The first RMC instance that was registered on the vcenter Server is displayed by default. Numeric The default value of the number of recovery sets that you can create is five. NOTE: Numeric policy set for one RMC instance does not apply to other RMC instance to which the user moves the VM object. Separate numeric policies must be defined for each RMC instance. Creation of recovery sets is enabled with VSS-aware application consistency. 54 Working with Recovery Sets Snapshots

55 6. If you have selected Expiration/Retention, then specify the following details: Figure 21 Recovery Set Management Policy a. Select an appropriate RMC instance for the selected VM. NOTE: list. All RMC instances registered with the vcenter Server are listed in the drop-down b. Specify the maximum number of Recovery Sets. The maximum number of Recovery Sets that you can specify to create a policy is 500. NOTE: Based on the order in which the Recovery Sets are created, the non-expirable Recovery Sets are deleted when they reach a position in the queue that exceeds the set count. c. Select Expiration/Retention to remove the Recovery Sets according to a specified schedule. The removal of Recovery Sets are not affected by the maximum count. If you select Enable expirable Recovery Sets, then in Expire after you must specify the time duration in hours or days from the current time that the Recovery Sets need to expire. The maximum expiry period that you can specify for Recovery Set expiry is hours or 1825 days. NOTE: Expirable Recovery Sets are not included in the maximum count. Modifying Recovery Set policies 55

56 If you enable expirable Recovery Sets, then you must specify how the existing non-expirable copies are handled. Keep non-expirable Recovery Sets Select this option to keep the existing non-expirable Recovery Sets. Phase out non-expirable Recovery Sets (Advanced) Select this option if you want to create expirable Recovery Sets and need to eventually phase out the older non-expirable Recovery Sets. Therefore, whenever a new expirable Recovery Set is created, the oldest non-expirable copy is deleted. NOTE: If all non-expirable Recovery Sets are in valid retention and have already reached the maximum count, then choosing the Enable expirable Recovery Sets with the Phase out non-expirable Recovery Sets option will fail. If this occurs, then select the Keep non-expirable Recovery Sets option. d. Select Retain Recovery Set to retain the Recovery Sets. i. Specify 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. RMC-V checks for an existing HP 3PAR Virtual Lock license on the Storage System when a Recovery Set is created with retention specified. The maximum retention period for Recovery Sets is 43,800 hours or 1,825 days. The expiry value must be equal to or greater than the retention value, when using both the expiry and retention options. e. Select Create Recovery Set with VSS-aware application consistency to ensure application consistency. This option is used to create snapshots of Recovery Sets that adhere to data format standards used by the VMware tools. CAUTION: While installing or upgrading the VMware tools, you must reboot VMware on the system where it is running, otherwise the application consistent snapshots may not be valid even though they are reported as completed successfully. This might also occur when the VMware tools are not upgraded on the VM system, after an upgrade of the ESXi server. NOTE: If you add a new VM to a datastore, you must update the policy to ensure VM application consistency. If you add a new VM or a datastore, click Actions Update Recovery Manager Cache to refresh the Recovery Manager cache. 7. Click Save. 8. The Default Snapshot Policy Settings dialog box appears only if you have selected an RMC Instance other than the default RMC Instance from Select RMC Host Name. Click Yes to save the default policy. 56 Working with Recovery Sets Snapshots

57 IMPORTANT: When you change the affinity from one RMC instance to another, a warning message is displayed indicating that all schedules from the earlier RMC instance (for that particular VM or datastore) must be deleted. 9. Click OK. NOTE: You need to perform a similar procedure to modify Recovery Sets on a datastore. Creating Recovery Sets Recovery Set is a set of virtual volumes that resides on the HP 3PAR StoreServ Storage system. RMC-V supports Recovery Set creation at both VM and datastore levels. Prior to creating Recovery Sets, ensure that the following conditions are met: Creating a Recovery Set at the VM level requires sufficient free space on the datastore where the VMDK file resides. Datastore creation from NFS drives is not supported for Recovery Set operations. RMC-V 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). RMC-V supports only one virtual volume per datastore. NOTE: Snapshot space must be available on the HP 3PAR virtual volume. To create a Recovery Set on an HP 3PAR base volume, the volume must have snapshot space allocated during its creation. To create a new Recovery Set on the VM: 1. Navigate to the home page, and click VMs and Templates. 2. Click the VM for which you need to create the Recovery Set. 3. Click Related Objects and then click Recovery Sets. All the Recovery Sets related to the VM are displayed. Creating Recovery Sets 57

58 4. Right-click the VM and then click All HP StoreOnce Recovery Manager Actions Create Recovery Set Snapshot. The Create Recovery Set page appears. Figure 22 Create Recovery Sets NOTE: The Expiration/Retention option is not available for VVOL VMs. a. RMC Host Instance The RMC instance that you selected in the policy is displayed. You cannot select a different RMC instance. b. Specify the Recovery Set name. NOTE: Recovery Set name is optional. However, if you do not specify a name for the Recovery Set, then the set name is identified by the time stamp. The Recovery Set name must not exceed 32 characters. c. You may select any of the following options, if applicable: Enable expirable Recovery Sets To set the snapshot expiration. Retain Recovery Sets To set the snapshot retention period. Create Recovery Sets with application consistency To create application consistent snapshots. 5. Click Create. You are prompted to confirm the creation of Recovery Set. 58 Working with Recovery Sets Snapshots

59 6. Click Yes to create a Recovery Set. The Recovery Set creation task is submitted and started. NOTE: Information regarding the Recovery Set creation process is displayed in the Recent Tasks pane. After creating the Recovery Set, an entry appears in the Recovery Sets tab under the Related Objects tab. NOTE: You can perform a similar procedure to create Recovery Sets for datastores. Viewing Recovery Set information This section describes how to view Recovery Set information. 1. Navigate to the vsphere Web Client home page. 2. Click Hosts and Clusters. 3. Select a VM and click Recovery Sets on the left navigation pane. The system displays all the available Recovery Sets in the Recovery Sets tab below Related Objects of a VM. 4. Double-click a Recovery Set to view the details. Figure 23 Recovery Set information Viewing Recovery Set information 59

60 5. The following information about the selected Recovery Set is displayed: Base datastore/rdm virtual volume Type Base Volume Base ID Virtual Copy Volume Virtual Copy ID Status The status can be Available or Mounted. NOTE: If the status of a Recovery Set is Mismatched, then the Recovery Set 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 allowed to remove the record. Manually remove the actual Recovery Set from the originating Storage System. Retention Expiry Exported Host LUN ID ESXi Host Virtual Copy datastore NOTE: You need to perform a similar procedure to view the Recovery Set information on a datastore. The Recovery Set timestamp displayed is converted to the local time zone of the RMC Appliance. The Expiry and Retention values on the same display are set to the time zone of the RMC Appliance. If the virtual volumes that are used are in a Peer Persistent configuration, then the local Recovery Set creation is disabled. HP recommends that you must not delete Snapshots from a Snapshot set using HP 3PAR Management Console. If you delete a snapshot, then the Snapshot is displayed in the Manage tab of the vsphere Web Client, however, you will not be able to perform any RMC-V tasks on such Snapshots. You can only delete this Snapshot. Viewing Virtual Disk details Click the entry to view the following details on the Virtual Disk associated with a Recovery Set. Virtual Disk Displays the Virtual Disk name. Original Virtual Machine Name Provides additional information on the VM name associated with the VMDK. For snapshots created earlier than version 2.3, system displays N/A. VSS-aware Application Consistent Provides information if this VMDK is application consistent. VM Attached Displays if the VM is attached. 60 Working with Recovery Sets Snapshots

61 Viewing Recovery Set event logs Recovery Sets operation event logs lists the events and the other event relevant details. To view event logs, click the Monitor tab, and then click the Events tab. You can filter and view the following information: Description Type Date Time Task Target User System displays the following additional details of a selected event: Event Type Description Possible Causes Related Events Figure 24 Viewing the Recovery Set event logs Mounting Recovery Sets This section describes how to mount Recovery Sets. 1. Navigate to the vsphere Web Client home page. 2. Click VMs and Templates. Mounting Recovery Sets 61

62 3. Select a VM, and then click Recovery Sets on the left navigation pane. System displays all the available Recovery Sets in the Recovery Sets tab below Related Objects. Double-click a Recovery Set to view the Manage tab. 4. Select the Recovery Set to mount from the Recovery Sets list, and click Mount/Unmount. 5. The Mount Virtual Copy screen appears with the following options: Mount on ESX host as Datastore Select from a list of 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 that are not managed by the vcenter Server, but which have access to the HP 3PAR StoreServ Storage System. 6. Click Mount. The Mount Local Recovery Set Confirm dialog box appears. 7. Click Yes, to mount the Recovery Set. NOTE: After the Recovery Set is successfully mounted, the status of the Recovery Set is displayed as Mounted. System also displays appropriate values in the following columns: Exported Host LUN ID ESXi Host Virtual Copy datastore You can perform a similar procedure to mount Recovery Sets on a datastore. For the mount operation to succeed: FC HBA WWNs or iscsi Initiator must be enabled and online in the ESXi server, and The host entry containing these WWNs or IQNs must be created in the storage system. 62 Working with Recovery Sets Snapshots

63 Unmounting Recovery Sets This section describes how to unmount Recovery Sets. CAUTION: RMC-V does not verify that the volume you unmount is active or inactive. Therefore, be sure that the volume you need to unmount is inactive. To unmount an already mounted Recovery Set: 1. Navigate to the vsphere Web Client home page. 2. Click VMs and Templates. 3. Select a VM, and then click Recovery Sets on the left navigation pane. System displays all the available Recovery Sets in the Related Objects Recovery Sets. 4. Select the Recovery Set you need to unmount from the list of Recovery Sets. Double-click a Recovery Set to view the Manage tab. 5. Click Mount/Unmount and then select the host. The Confirm dialog box appears. 6. Click OK. A message appears, indicating that the request is in process. The mounted copy is then unmounted. NOTE: You need to perform a similar procedure to unmount Recovery Sets from a datastore. Attaching Recovery Sets This section describes how to attach Recovery Sets. You can attach a Recovery Set to a VM only if the Recovery Set is already mounted. To attach a Recovery Set: 1. Navigate to the vsphere Web Client home page. 2. Click VMs and Templates. 3. Select a VM, and then click Recovery Sets on the left navigation pane. System displays all the available Recovery Sets in the Recovery Sets tab below Related Objects. Double-click a Recovery Set to view the Manage tab. 4. Select a mounted Recovery Set that you need to attach to a VM. 5. Click Copy/Attach/Detach. The Copy/Attach window appears. Unmounting Recovery Sets 63

64 Figure 25 Copy to Datastore 64 Working with Recovery Sets Snapshots

65 6. Select one of the following options: Copy to Datastore Select the datastore to which you need to copy the selected Recovery Set. Attach to Virtual Machine Select the VM to which you wish to attach the selected Recovery Set. a. To copy the VMDK file: i. Select Copy to datastore. The associated datastores are displayed. ii. Select an appropriate datastore to which you want to copy the Recovery Set. iii. Select Overwrite existing Virtual Disk to overwrite the VMDK file. iv. Click Copy. v. Click Yes when you are prompted for confirmation. The Recovery Set is successfully copied to the datastore. b. To attach the Recovery Set to a VM: Figure 26 Attach to Virtual Machine i. Select Attach to Virtual Machine. All datastores associated with the ESXi host are displayed. ii. Select an appropriate VM to which you want to attach the Recovery Set. iii. Click Attach to attach the Recovery Set. iv. Click Yes when you are prompted for confirmation. The Recovery Set is successfully attached to the VM. Detaching Recovery Sets You can detach a Recovery Set that is attached to a VM. To detach a Recovery Set: Detaching Recovery Sets 65

66 1. Navigate to the vsphere Web Client home page. 2. Click VMs and Templates. 3. Select a VM, and then click Recovery Sets on the left navigation pane. System displays all the available Recovery Sets in the Recovery Sets tab under Related Objects tab. 4. Select the Recovery Set you need to detach from the list of Recovery Sets. Double-click a Recovery Set to view the Manage tab. 5. Click Copy/Attach/Detach and then select the host. 6. Click Yes when you are prompted for confirmation. Restoring Virtual Machines 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, restore one of the Recovery Sets 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. RMC-V limits the promotion of a Recovery Set taken before a virtual volume conversion. The following error message is displayed if the action occurs: Performing any RMV Recovery Set operations such as creating or deleting must only occur after a Virtual Volume conversion is completed. NOTE: After a virtual volume conversion is complete, click Actions Update Recovery Manager Cache to see the changes. The RMC Appliance does not notify the RMC-V Plug-in for any backend data changes, until you do Update Recovery Manager Cache. To restore a datastore by restoring a Recovery Set: 1. Click Storage Related Objects. NOTE: Ensure that you are in the datastores view, because you can restore only datastores. 2. Select the Recovery Set that you want to restore, from the Recovery Sets. 3. Right-click the Recovery Set, and click Restore. The Restore datastore to Recovery Set dialog box appears. 4. Click Yes. The Recovery Set restore task is submitted and a message appears indicating that the request is in process. TIP: You can also restore a Recovery Set by performing the following action: Double-click the Recovery set and click Manage Actions Restore. Restoring VVOL Virtual Machines To restore a VVOL VM: 1. Navigate to the vsphere Web Client home page and click VMs and Templates. 2. Click the VVOL VM that you need to restore. 3. Click Related Objects and then click Recovery Sets. All Recovery Sets related to the VVOL VM are displayed. 4. Power off the VM. 5. Right-click the VM and then click All HP StoreOnce Recovery Manager Central Actions Update Recovery Manager Cache. 66 Working with Recovery Sets Snapshots

67 6. Right-click a Recovery Set and click Restore. The Restore Virtual Machine to Recovery Set window appears: Figure 27 Restore Virtual Machine to Recovery Set 7. Click Yes to restore. Deleting Recovery Sets This section describes how to delete Recovery Sets. 1. Navigate to the vsphere Web Client home page. 2. Click Hosts and Clusters. 3. Select a VM, and then click Recovery Sets on the left navigation pane. System displays all the available Recovery Sets in the Recovery Sets tab below Related Objects. 4. Select the Recovery Set you need to delete from the list of Recovery Sets. 5. Click Actions Delete. TIP: You can also delete a Recovery Set by performing the following action: Double-click the Recovery set and click Manage Actions Delete. The Confirm dialog box appears. 6. Click Yes, to confirm deletion of the selected Recovery Set. NOTE: The Recovery Set deletion task is submitted, and you are prompted to confirm the deletion. The Recovery Set is then removed from the Recovery Set list. If you select more than one Recovery Sets Snapshots for deletion, then the delete confirmation message might be displayed in the local language. You need to perform a similar procedure to delete Recovery Sets on a datastore. Viewing Recovery Sets You can view a list of Recovery Sets for a VM or datastore. You can view a list of Recovery Sets for a VM or datastore, created for the RMC instance that you selected in the policy, while creating that particular Recovery Set. 1. Navigate to the vsphere Web Client home page. 2. Click Hosts and Clusters. Deleting Recovery Sets 67

68 3. Select a VM and click Recovery Sets on the left navigation pane. System displays all the available Recovery Sets in Recovery Sets under the Related Objects tab. Figure 28 Recovery Sets Scheduling Recovery Sets This section describes how to perform the following scheduling tasks for Recovery Sets. Viewing a schedule list Add Adding a schedule Edit Editing a schedule Delete Deleting a schedule Refresh Refreshing a schedule list Close To close the Schedule List window. Viewing a schedule list 1. Navigate to the vsphere Web Client home page. 2. Click Hosts and Clusters. 3. Click Virtual Machine. 4. Select a Virtual Machine on the right pane to apply schedule. 5. Click Actions All HP StoreOnce Recovery Manager Central Actions Schedule Recovery Set Creation. The Schedule List for the VM that you have selected appears. 68 Working with Recovery Sets Snapshots

69 This window lists all the tasks that are currently scheduled for a Recovery Set. From the Scheduled List window, you can add a schedule, modify an existing schedule, or delete an existing schedule. 6. Click Close to close the Scheduled List window. NOTE: select. The Schedule List window lists the schedules only for a single VM or datastore that you You can automatically create Recovery Sets according to a specified schedule. Creating schedules To create a schedule for a Recovery Set: 1. Navigate to Schedule List. NOTE: For information on navigating to the Schedule List, see Viewing a schedule list. 2. Click Add, to automatically create Recovery Sets according to a specified schedule. The Welcome tab of the Create Schedule Task Wizard window appears. 3. Click Next. The Recovery Set Type window appears with the following options: Snapshot To schedule creation of snapshot for a virtual machine or datastore. Express Protect To schedule Express Protect of snapshot for a virtual machine or datastore. Scheduling Recovery Sets 69

70 4. Click Next. The Schedule window appears. a. Specify a task name for the schedule in Schedule task name. b. Select the task frequency from Perform Recovery Set creation task to create a Recovery Set. The following frequencies are listed: i. By minutes NOTE: HP recommends that you maintain a minimum of 30 minutes between two snapshot schedules. ii. Hourly iii. Daily iv. Weekly You can select one or more days of a week to schedule the task. v. Monthly You can select a particular date of any month to schedule the task. vi. One time only You can select a date from the calendar and specify the time to schedule the task for only one time. Additional options are displayed when you select a frequency from Perform Recovery Set creation task. The following table lists the frequency details: Frequency Daily Hourly Monthly One time only Weekly Frequency details Start time Recur Every Start time Recur Every Start time Day Start date Start time Start time Recur Every Select day(s) of a week below Descriptions You can specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the frequency of the scheduled task. You can specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the frequency of the scheduled task. You can specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the day of every month to start the scheduled task. Select the date on which you need to schedule the Express Protect. You can specify the schedule start time in hours and minutes. Also, select AM or PM. You can specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the frequency of the scheduled task. All seven days of a week are displayed. You can select one or more days to schedule the weekly Express Protect. 5. Click Next. The Recovery Set Type window appears with the following options: Snapshot Select this option to create a schedule for a virtual machine or datastore. By default this option is selected. Express Protect Select this option to create a schedule to take backup of Virtual Machines or datastores to HP StoreOnce. 6. Click Next. The Snapshot Configuration window appears. The following screen appears. 70 Working with Recovery Sets Snapshots

71 1. Select Create Recovery Set with VSS-aware application consistency to create application consistent Recovery Sets. 2. Select either of the following options: To apply the schedule to all the VMs, select Apply to all Virtual Machines. To apply the schedule task to specific VMs, select Apply to following Virtual Machine(s), and then select the required Virtual Machines. NOTE: Overwrite default policy setting is disabled for numeric policies. For Expiration/Retention policies this option is enabled. You can modify the values for Set Recovery Set to expire after and Retain Recovery Set of the default policy. 7. Click Next. The Schedule Task Summary window appears. Verify that the details listed in Schedule Task Summary are correct. 8. Click Finish to complete the task schedule. The Schedule Modification window appears. Editing schedules Click Yes to schedule the task. This section describes how to make changes to an existing schedule task. 1. Navigate to the Schedule List. NOTE: For information on navigating to the Schedule List, see Viewing a schedule list. 2. Select the schedule that you need to edit and click Edit. The Edit Schedule Task Wizard appears. 3. Click Next until you reach the Schedule and Snapshot Configuration pages of the Edit Schedule Task Wizard. Editing schedules 71

72 4. Make appropriate changes to the schedule. For information on setting the schedule parameters, see Scheduling Recovery Sets (page 68). 5. Click Next. The Schedule Task Summary window appears. Verify that the details listed in Schedule Task Summary are correct. 6. Click Finish to complete the task schedule. The Schedule Modification window appears. Click Yes to confirm the changes made to the schedule. Removing schedules To remove an existing schedule: 1. Navigate to the Schedule List. NOTE: For information on navigating to the Schedule List, see Viewing a schedule list. 2. Select the schedule that you need to delete and click Delete. 3. Click Yes to confirm deletion of the schedule. Updating Recovery Manager Cache If you make changes to HP 3PAR StoreServ storage or create a VM or a datastore, then you must update the Recovery Manager cache. Otherwise, RMC-V operations fail with an error message Perform a cache refresh. To update the Recovery Manager cache: 1. Navigate to the vsphere Web Client home page. 2. Click Hosts and Clusters. 3. Select a VM and click Recovery Sets on the left navigation pane. System displays all the available Recovery Sets in the Recovery Sets tab under Related Objects tab. 4. Select and right-click a Virtual Machine to apply a set of policies. 5. Click All HP StoreOnce Recovery Manager Update Recovery Manager Cache to update the Recovery Manager Cache. 72 Working with Recovery Sets Snapshots

73 10 Working with Remote Recovery Sets Configurations HP 3PAR Remote Copy Software provides RMC-V the capability to copy virtual volumes from protected site to recovery site. The Remote Recovery Configuration feature allows you to create and manage Synchronous, Periodic, or Synchronous Long Distance Remote Recovery Sets at HP 3PAR Remote Copy group level. HP 3PAR Remote Copy solution replicates data from one site (or Storage system) to another site (or Storage system), thus protecting data in case of disaster or failure of a Storage system. RMC helps you to either recover data or restore data at either site. RMC-V supports HP 3PAR Peer Persistence. When virtual volumes use Peer Persistence, it allows creation of remote Virtual Copies on Remote Recovery Configurations. Therefore, when an active path fails over to a different Storage system, the virtual copies become available on either of the Storage Systems for restoration. For more information on establishing a Peer Persistent setup, see the HP 3PAR Remote Copy User Guide. The Remote Recovery Configurations node that displays the Remote Recovery Sets is removed from Home HP Infrastructure. This change is effective from RMC-V v You can configure Remote Copy groups in one of the following replication modes: Synchronous Asynchronous Periodic Asynchronous Streaming NOTE: RMC Remote Copy Configuration supports only 1:1 configurations. The 1:N and N:1 configurations are not supported. VVOL is not supported for Remote Recovery Sets. RMC-V supports the following Remote Copy configurations: One-to-One Synchronous Long Distance IMPORTANT: Be sure that all VMs associated with the datastore are in the power off state. Be sure that the Remote Copy group is in the stopped state before you restore a datastore-level Recovery Set that is a part of the Remote Copy group. Getting started What Remote Recovery Configuration is Remote Recovery Configuration is a collection of replication groups that contain virtual volumes that are exposed to the ESXi hosts managed in a vcenter Server. These replication groups are called Remote Copy Groups in HP 3PAR StoreServ Storage. HP 3PAR Remote Copy feature provides enterprise and cloud data centers with autonomic replication and disaster recovery technology that allows protection and sharing of data between multiple arrays within the same or different geographical locations. If a Remote Copy Group is setup for the virtual volumes used by the ESXi hosts, RMC-V allows you to take advantage of the Remote Copy Group by taking snapshots on local, remote, or both storage systems using Remote Copy group as an entity for operation. Getting started 73

74 After the Recovery Set is created, it allows you to mount individual virtual copy to a specific ESXi host that resides on the local storage system. You can then attach the mounted volume to a selected Virtual Machine as additional disk for a file-level restore. Remote Recovery Configurations tab Remote Recovery Configuration is available under Related Objects for Virtual Machines and datastores. The following tabs are available under Related Objects of a Remote Recovery configuration group: Recovery Sets on Source StoreServ Recovery Sets on Target StoreServ Virtual Volumes Datastore Virtual Machine Action Menu Table 5 (page 74) lists the tasks that you can perform from the Action menu. Table 5 Action menu items Task Create Remote Recovery Set Set Remote Recovery Set Creation Policy Schedule Remote Recovery Set Creation Update Recovery Manager Cache Description Creates a Remote Recovery Set for a selected configuration. Sets the default policy. You can over-ride this using the Creation wizard. Manages creation of Remote Recovery Sets using a schedule. Refreshes the current server cache memory to reflect the changes in vcenter Server or storage system inventory objects. When you select a Remote Copy group from the list, the details pertaining to the selected object is available in the following tabs: Prerequisites Getting Started Displays information about Remote Copy group. Summary Displays properties of the Remote Copy group. Related Objects Displays objects that are related to the Remote Copy group. Before creating Recovery Sets through Remote Recovery Configuration, be sure that the following conditions are met: All virtual volumes in the Remote Copy group must be exported to ESXi host. At least one of the first eight characters of all virtual volume names in a Synchronous Remote Copy group must be unique. The Remote Copy group must be in Started state, and all virtual volumes must be in Synced state. For information on creating Remote Copy groups, see the HP 3PAR Remote Copy Software User Guide. All Virtual Machines involved in the operation must contain virtual volumes from same Remote Copy groups. 74 Working with Remote Recovery Sets Configurations

75 Workflow If you need application consistency, be sure that you have VMware Tool in the Virtual Machine to guarantee consistent and usable backup. All RMC Appliances can reach each other. For Peer Persistence groups, both source and target volumes must be exported to same ESXi host. Table 6 (page 75) lists the tasks that you need to do to configure and use the Remote Recovery Sets feature. Table 6 Workflow Remote Recovery Set Configuration Step no. Action Additional notes and references 1 Install a vcenter Server (for example, You can ignore this step if a vcenter Server is already installed. vcenter1). Ensure that you have an ESXi Host that is managed by this vcenter Server. For information on installing vcenter Server, see the VMware documentation. 1a 2 2a 3 4 4a 4b 5 Install secondary vcenter Server (for example, vcenter2). Install HP OneView for VMware vcenter v7.7.1 or later on vcenter1. Install HP OneView for VMware vcenter v7.7.1 or later on vcenter2. Add source and target HP 3PAR StoreServ Storage systems using the Storage Administrator Portal. Log in to the Web Client and perform the following tasks: Deploy an RMC Appliance. Register the Remote RMC Appliance. Create Remote Copy Groups on HP 3PAR StoreServ Storage system, if the groups are not already created. It is optional to have a secondary vcenter Server. In case of disasters, secondary vcenter Server can be used for disaster recovery solutions. For more information and illustrations, see RMC Remote Copy Configurations Topologies (page 76). For information on installing HP OneView for VMware vcenter, see the HP OneView for VMware vcenter Installation Guide. This step is optional and is applicable only if you need to configure disaster recovery solutions. For information on adding HP 3PAR StoreServ Storage systems, see Storage Administrator Portal (page 39). For information on logging in and performing various tasks using the Web Client, see Working with vsphere Web Client (page 42). For information on deploying RMC instances, see Deploying RMC (page 15). For information on Registering Remote RMC Appliances, see Registering Remote RMC Appliances (page 79). You can configure the Remote Copy Configuration in the following ways: Synchronous Asynchronous Periodic Synchronous Long Distance For more information to set up a Remote Copy Configuration, see the HP 3PAR Remote Copy Software User Guide. For information on the Remote Copy Configurations supported by RMC-V, see RMC Remote Copy Configurations Topologies (page 76). Workflow 75

76 Table 6 Workflow Remote Recovery Set Configuration (continued) Step no. Action Additional notes and references 6 Present the virtual volumes from the The virtual volumes appear in the Remote Copy Group only after Primary StoreServ to the ESXi Host. they are presented to the ESXi Server. For the RC Groups to appear: Update Recovery Manager Cache Do a vcenter refresh. For information on presenting the virtual volumes, see the HP 3PAR Management Console User Guide. If a secondary vcenter Server is configured, you must export volumes from the secondary HP 3PAR StoreServ to the secondary ESXi host Click Remote Recovery Configurations tab. Creating Policies Creating Remote Recovery Sets Managing schedules for Remote Recovery Sets Add new schedules Edit schedules Delete schedules Managing Remote Recovery Sets Mounting Remote Recovery Sets Unmounting Remote Recovery Sets Attaching Remote Recovery Sets Detaching Remote Recovery Sets Deleting Remote Recovery Sets To verify that all Remote Copy groups are displayed. Remote Recovery Set tasks For more information, see Creating policies (page 83). For more information, see Creating Remote Recovery Sets (page 85). For more information, see Managing Remote Recovery Sets schedules (page 88). For more information, see Managing Remote Recovery Sets (page 91). For more information, see Deleting Remote Recovery Sets (page 98). RMC Remote Copy Configurations Topologies This section describes the different Remote Copy Configurations topologies supported for RMC. Remote Copy Configuration Single-site RMC Appliance Figure 29 (page 77) illustrates configuring Remote Copy with a single-site RMC Appliance. 76 Working with Remote Recovery Sets Configurations

77 Figure 29 Remote Copy Configuration Single-site RMC Appliance For a Remote Copy configuration with a single RMC appliance and a single vcenter Server, the same RMC appliance must be registered for both primary, and remote arrays. For example, RMC1 must be registered for Primary StoreServ and Secondary StoreServ. NOTE: For information on deploying RMC Appliances, see Deploying RMC using HP OneView for VMware vcenter (page 16). To configure RMC Appliances for Remote Copy Configuration Single-site RMC Appliance, see Registering Remote RMC Appliances (page 79). Remote Copy Configuration Multi-site RMC Appliances Figure 30 (page 77) illustrates configuring Remote Copy with multi-site RMC Appliances. Figure 30 Remote Copy Configuration Multi-site RMC Appliances You can configure two different RMC instances with different vcenter Servers at the local and remote locations. For example, RMC1 is registered with vcenter Server1; and RMC2 is registered with vcenter Server2. RMC Remote Copy Configurations Topologies 77

78 NOTE: You can register RMC instances to a vcenter from the RMC Credentials tab. For information on deploying RMC Appliances, see Deploying RMC using HP OneView for VMware vcenter (page 16). To configure RMC Appliances for Remote Copy Configuration Single-site RMC Appliance, see Registering Remote RMC Appliances (page 79). Register RMC Appliances for the respective HP 3PAR StoreServ Storage systems from the RMC configuration tab in each vcenter Server. For example, RMC2 for Secondary StoreServ in vcenter server1. Figure 31 Remote Copy Configuration Multi-site RMC Appliances RMC1 for Primary StoreServ and RMC2 for Secondary StoreServ in vcenter Server1 (StoreOnce RMC Configurations). Remote Copy Configuration Synchronous Long Distance Figure 32 (page 78) illustrates configuring Remote Copy in Synchronous Long Distance (SLD). Figure 32 Remote Copy Configuration Synchronous Long Distance For SLD configurations, you can configure three RMC Appliances and three vcenter Servers. 78 Working with Remote Recovery Sets Configurations

79 SLD configuration with a Single RMC Appliance Single vcenter Server (vcenter1) that has RMC1 as the appliance. On the primary site (vcenter1) you must set the target array2 and array3 to RMC1. SLD configuration with two RMC Appliances vcenter1 and vcenter2 RMC1 and RMC2 On the primary site (vcenter1) you must set the target array2 and array3 to RMC2 On the secondary site (vcenter2) you must set the target array1 to RMC1 and array3 to RMC2. SLD configuration with three RMC Appliances vcenter2 and vcenter3 RMC2 and RMC3. On the primary site (vcenter1) you must set the target array2 to RMC2 and array3 to RMC3. On the Secondary Site (vcenter2) you must set the target array1 to RMC1 and array2 to RMC2. On the Tertiary Site (vcenter3) you must set the target array1 to RMC1 and array2 to RMC2. NOTE: For information on deploying RMC Appliances, see Deploying RMC using HP OneView for VMware vcenter (page 16). To configure RMC Appliances for Remote Copy Configuration Single-site RMC Appliance, see Registering Remote RMC Appliances (page 79). Registering Remote RMC Appliances For a Remote Copy configuration with a single RMC appliance and a single vcenter Server, the same RMC appliance must be registered for both, primary and remote storage systems. For example, RMC1 must be registered for Primary StoreServ and Secondary StoreServ. For more information, see Figure 29 (page 77). You can configure two different RMC instances with different vcenter Servers at the local and remote locations. For example, RMC1 is registered with vcenter Server1; and RMC2 is registered with vcenter Server2. For a Remote Copy configuration with multi-site RMC appliances, register RMC Appliances for the respective HP 3PAR StoreServ Storage systems from the RMC configuration tab in each vcenter Server. For example, RMC2 for Secondary StoreServ in vcenter server1; and RMC1 for Primary StoreServ in vcenter server2. For more information, see Figure 30 (page 77). For Synchronous Long Distance (SLD) configurations: You need to configure three RMC appliances and three vcenter Servers. An RMC appliance is registered for each Array, under each vcenter instance. Either single or two RMC Appliances and one vcenter Server configurations are also supported. For more information, see Figure 32 (page 78). To register a Remote RMC Appliance: 1. Click Start All Programs VMware VMware vsphere Web Client vsphere Web Client. The VMware vsphere Web Client login screen appears. Registering Remote RMC Appliances 79

80 2. Log on to the VMware vsphere Web Client. a. Enter the user name and password. b. Click Login. The VMware vsphere Web Client home page appears. 3. Click Administration StoreOnce RMC Configuration. The list of HP 3PAR StoreServ Storage systems associated with the ESXi host is displayed. Figure 33 HP 3PAR StoreServ Storage systems associated with the ESXi host 4. Select the target HP 3PAR StoreServ Storage system that you need to register in a Remote Recovery Configuration and click Edit. For more information on the supported Remote Copy topologies, see RMC Remote Copy Configurations Topologies (page 76). 5. Enter the following details: RMC Server Name RMC Server Username RMC Server Password 6. Click Save. The selected HP 3PAR StoreServ Storage system is registered in the Remote Recovery Configuration. After you click Save, the target HP 3PAR StoreServ is registered to the Remote RMC Appliance. 80 Working with Remote Recovery Sets Configurations

81 NOTE: You must configure the source Storage system to the local RMC Appliance to start the import. To register HP 3PAR StoreServ Storage Systems on the Remote Recovery Configuration, repeat the procedures in steps 4 through 6. For Peer Persistence, you must register the same RMC appliance for both source and target HP 3PAR StoreServ Storage systems. For more information on Peer Persistence, see Peer Persistence (page 99). For Remote Copy Configuration with multi-site RMC Appliances, repeat this procedure for the remote site also. For illustrations, see Figure 30 (page 77). For Remote Copy Configuration Synchronous Long Distance, repeat above steps for both Secondary Storage systems. For illustrations, see Figure 32 (page 78). Remote Copy Configuration Synchronous Long Distance setup can be configurations in one of the following ways: Single RMC Appliance for both Secondary Sites Separate RMC Appliances for each Secondary StoreServ device Viewing Remote Recovery configurations To view Remote Recovery Configurations: 1. Click Start All Programs VMware VMware vsphere Web Client vsphere Web Client. The VMware vsphere Web Client login screen appears. 2. Log in to the VMware vsphere Web Client. 3. Click vcenter Remote Recovery Configurations. The Remote Copy groups mapped to the ESXi Server are displayed. Figure 34 Remote Copy groups mapped to the ESXi Server NOTE: If you make any changes in Remote Recovery Configurations, you must perform Updating Recovery Manager Cache (page 72) and vcenter Refresh. Otherwise, the Remote Recovery Sets might not be listed. Viewing Remote Recovery Configuration information details To view the details of the source or target HP 3PAR StoreServ Storage systems: 1. Navigate to the Remote Recovery Configurations page. Viewing Remote Recovery configurations 81

82 2. Select a Remote Recovery Configuration and click the Summary in the detail pane to view the summary of the selected storage system. Figure 35 Remote Recovery Configuration details NOTE: If Peer Persistent is enabled, then the local Recovery Sets are disabled because Recovery Set snapshots are taken both locally and remotely using Recovery Set creation. 82 Working with Remote Recovery Sets Configurations

83 3. The Summary page displays the following details: Table 7 Remote Recovery Configuration information summary Field name Source name Source StoreServ Role StoreServ Target Name RMC host Peer persistence Mode Status Link type Value Name of the Remote Copy group. Name of the source HP 3PAR StoreServ Storage. Displays one of the following roles for the HP 3PAR StoreServ: Primary The role of source HP 3PAR StoreServ Storage is always primary. Secondary The role of target HP 3PAR StoreServ Storage is always secondary. The Remote Copy group name that gets created on the target 3PAR StoreServ Storage. The name of the target Remote Copy group. Host name or IP address of the RMC Appliance. Indicates if Peer persistence is enabled or disabled for the virtual volumes. Displays appropriate values to indicate one of the following modes: Sync For synchronous mode. Periodic For asynchronous periodic mode. Displays one of the following status: Started Stopped Syncing Displays one of the following connectivity modes: FC iscsi Creating policies You can create expirable or retention policies for each Remote Recovery Set based on the local Recovery Sets. When you create a policy for the source Remote Copy Group, a similar policy is automatically created by the RMC Appliance for the target Remote Copy Group. 1. Log in to the VMware vsphere Web Client. 2. Right-click Remote Recovery Configurations. All Remote Recovery Sets associated with the host and cluster are displayed. 3. Click Actions Set Remote Recovery Set Creation Policy. The HP StoreOnce Recovery Manager Central Recovery Set Management Policy window appears. TIP: You can also right-click a Remote Recovery Configuration listed in the left pane and click Set Remote Recovery Set Creation Policy to open the HP StoreOnce Recovery Manager Central Recovery Set Management Policy window. Creating policies 83

84 Figure 36 HP StoreOnce Recovery Manager Central Recovery Set Management Policy 4. The IP address of the RMC appliance that was added first is displayed. 5. To create a numeric policy, select Numeric and specify the Maximum number of Recovery Sets. CAUTION: Based on the order in which the Recovery Sets are created, the non-expirable Recovery Sets are deleted when they reach a position in the queue that exceeds the set count. 6. To create an expiration or retention policy, select Expiration/Retention. To create expiration policies, perform steps 7 through 10. To create retention policies, perform steps 11 through To create an expiration policy, select Enable expirable Recovery Sets. 8. Select days or hours from the drop-down menu. 9. Specify the expiration period in Expire after and select day(s) or hours. NOTE: The maximum period that you can specify for Recovery Set expiry is hours or 1825 days. 10. If you enable expirable Recovery Sets, then you can also specify how to handle the existing non-expirable copies by selecting one of the following options: Keep non-expirable Recovery Sets Select this option if you want to create both expirable and non-expirable Recovery Sets. All non-expirable copies (new and existing) are counted 84 Working with Remote Recovery Sets Configurations

85 against the maximum count, with the oldest being deleted, as it exceeds the maximum count. Phase out non-expirable Recovery Sets (Advanced) Select this option if you need to create expirable Recovery Sets and you need to eventually phase out the older non-expirable Recovery Sets. NOTE: When a newer expirable Recovery Set is created, the oldest non-expirable copy is deleted. However, you can still create non-expirable Recovery Sets, as long as the aggregate count is less than the policy maximum. 11. Select Retain Recovery Set to retain the Recovery Sets. 12. Specify the Retention period. 13. Select day(s) or hours. NOTE: Setting the retention policy requires the HP 3PAR Virtual Lock license on the HP 3PAR StoreServ Storage System. The Recovery Sets can be retained up to 43,800 hours or 1,825 days maximum. If you are using both the expiry and retention options, the expiry value must be equal to or greater than the retention value. 14. Select Create Recovery Set with VSS-aware application consistency to ensure application consistency. This option is used to create snapshots of Recovery Sets that adhere to data format standards used by the VMware Tools. CAUTION: While installing or upgrading the VMware Tools, you must reboot VMware on the system where it is running. Otherwise, the application consistent snapshots might become invalid even though they are reported as successfully completed. This might also happen when the VMware Tools are not upgraded on the VM system after upgrading the ESXi host. NOTE: If you add a new VM to a datastore, you must update the policy to ensure VM application consistency. If you add a new VM or a datastore, click Actions Update Recovery Manager Cache to refresh the Recovery Manager cache. 15. Click Save. An alert message appears indicating that the new policy is saved. 16. Click OK. Creating Remote Recovery Sets You can create Remote Recovery Sets for Remote Recovery Configurations associated with a specific ESXi Server. Other Virtual Machines from other ESXi Servers are not displayed. When you create Synchronous Remote Recovery Sets, RMC-V creates a copy on both local and remote arrays. For Periodic Remote Recovery Sets, only a Remote Recovery Set is created on the remote array. For Periodic Remote Recovery sets, both local and Remote Recovery Sets are created. However, HP 3PAR StoreServ Storage system keeps only the latest Recovery Set on the HP 3PAR StoreServ Storage system at the local site. Therefore, at any given point only one snapshot is available on the primary storage system unless retention policy is used. Creating Remote Recovery Sets 85

86 NOTE: You can create snapshots of volumes that only belong to a Remote Copy group. If you attach a virtual hard disk from a datastore that is hosted by a volume that does not belong to the Remote Copy group, then that volume will not be considered during Remote Recovery Set creation. HP 3PAR StoreServ has only the latest snapshot at the primary site. Therefore, after creating a Remote Recovery set for a periodic group, HP recommends that you update the Recovery Manager cache and refresh the vcenter. 1. Log in to the VMware vsphere Web Client. 2. Click vcenter Remote Recovery Configurations. All Remote Recovery Sets associated with the host or cluster are displayed. 3. Click Actions Create Remote Recovery Set. The Create Remote Recovery Set window appears. Figure 37 Creating Remote Recovery Sets NOTE: In the event of a failure, be sure that all storage systems are back in operation and the groups are in Started state for the Remote Recovery Set to be successfully created. However, you can also create a Recovery Set locally without Remote Copy. 86 Working with Remote Recovery Sets Configurations

87 4. Select Create Recovery Set with VSS-aware application consistency. Enable expirable Recovery Sets This option is automatically selected if you have selected expiration period in the policy. This option is disabled for numeric policies. Retain Recovery Set This option is selected if you have selected retention period in the policy. This option is disabled for numeric policies. Create Recovery Set with VSS-aware application consistency Creates VSS-aware application consistent Recovery Set. This option is disabled for Expiration/Retention policies. CAUTION: The dialog box displays the maximum number of Recovery Sets defined in the policy if the maximum number is already defined in the policy. If the number of existing Recovery Sets reaches the maximum number specified in the policy and if you create a new Recovery Set, then the oldest Recovery Set is deleted. 5. Click Create to create the Remote Recovery Set. 6. Click Yes to confirm. NOTE: Tasks. You can view the status of Remote Recovery Sets creation in Recent Tasks or More Viewing Remote Recovery Sets group details This section describes how to view the details of the snapshots that are available in a Remote Recovery Sets group. 1. Log in to the VMware vsphere Web Client. 2. Click Remote Recovery Configurations. All Remote Recovery Sets associated with the host or cluster are displayed. 3. Double-click a Remote Recovery Set. 4. Click Summary. The details of the selected Remote Recovery Sets are displayed. Figure 38 Remote Recovery Sets details Creating Remote Recovery Sets 87

88 Managing Remote Recovery Sets schedules RMC-V allows you to automatically create Remote Recovery Sets according to a predefined schedule. The RMC-V scheduler allows you to perform the following tasks: Add schedules Edit schedules Delete schedules To add, edit, or delete schedules: 1. Log in to the VMware vsphere Web Client. 2. Click vcenter Remote Recovery Configurations. All Remote Recovery Sets associated with the host or cluster are displayed. 3. Click Actions Schedule Remote Recovery Set Creation. The Schedule Create Remote Recovery Set window appears with a list of existing schedules. Figure 39 Schedule list 4. You can perform any of the following tasks from Schedule Create Remote Recovery Set: Adding a new schedule To add a new schedule, see Adding schedules (page 88). Editing a new schedule To edit an existing schedule, see Editing schedules (page 90). Deleting a new schedule To delete a schedule, see Deleting schedules (page 90). 5. After performing one or more tasks listed in the previous step, click Refresh, to refresh the list of schedules. 6. Click Close, to close the window. Adding schedules This section describes how to automatically create Remote Recovery Sets in a Remote Recovery Configuration. 1. Click Add, to add a new scheduled Remote Recovery Set task. The Welcome windows appears. 88 Working with Remote Recovery Sets Configurations

89 2. Click Next. The Schedule window appears. a. Specify a task name for the schedule in Schedule task name. b. Select the task frequency from Perform Recovery Set creation task to run the schedule. The following frequencies are available: Frequency By minutes Hourly Daily Weekly Monthly One time only Select this option to Specify the time in minutes to run the schedule. NOTE: HP recommends that you maintain a minimum of 30 minutes interval between two schedules. Specify the time in hours and minutes to run the schedule. Specify the time in days to run the schedule. Specify the time in weeks to run the schedule. You can select one or more days of a week to schedule the task. Specify the time in months to run the schedule. You can select a particular date of any month to schedule the task. Specify the time to run the schedule only one time. You can select a date from the calendar and specify the time to run the schedule only for one time. c. Specify details under Select time and frequency you want this task to start as listed in the following table. A different set of fields are displayed for each frequency that you select in Perform Recovery Set creation task. Frequency By Minutes Hourly Daily Weekly Monthly One time only Frequency details Start time Recur every Start time Recur every Start time Recur every Start time Recur every Select day(s) of week below Start time Day Start date Start time Select this option to Specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the frequency of the schedule in minutes. Specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the frequency of the schedule in hours. You can specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the frequency of the schedule in days. Specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the frequency of the schedule in weeks. All seven days of a week are displayed. You can select one or more days to for weekly schedule. Specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the day of the month to run the schedule. Use the calendar to select the date on which you need to run the schedule. Specify the schedule start time in hours and minutes. Also, select AM or PM. Managing Remote Recovery Sets schedules 89

90 3. Click Next. The Snapshot Configuration screen appears. Figure 40 Snapshot Configuration a. Select an appropriate Target StoreServ. b. Select Create Recovery Set with VSS-aware application consistency to create application consistent Recovery Sets. 4. Click Next. The Summary screen appears. 5. Verify the details listed in Summary and click Finish. 6. Click Yes to confirm creating the schedule. Editing schedules After successful creation, the task is listed in the Schedule Create Remote Recovery Set window. This section describes how to make changes to an existing schedule task. 1. Select the schedule that you need to edit and click Edit. The Edit Schedule Task Wizard appears. 2. For information on making changes to the schedule using Edit Schedule Task Wizard, see Adding schedules (page 88). NOTE: You can make appropriate changes to all the schedule parameters except the Schedule task name. 3. Click Refresh to refresh the list of schedules. 4. Click Close to close the window. Deleting schedules This section describes how to delete an existing schedule task. 1. Select the schedule task that you need to delete. 2. Click Delete. 3. Click Yes to confirm deletion of the schedule task. 90 Working with Remote Recovery Sets Configurations

91 4. Click Close to close the window. IMPORTANT: The scheduled jobs will fail after failover of the Remote Copy group and the Remote RMC/RMC-V fails to run the scheduled jobs. You need to schedule the jobs again at new source side. Viewing Source and Target StoreServ Recovery Sets This section describes how to view the source and target Recovery Sets for the HP 3PAR StoreServ Storage systems. 1. Log in to the Web Client. 2. Click vcenter Remote Recovery Configurations. 3. Double-click the Remote Copy group on which you have created Recovery Sets. 4. Click the Related Objects tab, and click Recovery Sets on Source StoreServ to view the Recovery Sets on the source HP 3PAR StoreServ Storage systems. The Recovery Sets on Source StoreServ tab appears. Figure 41 Recovery Sets on Source StoreServ 5. Click Recovery Sets on Source StoreServ to view the Recovery Sets on the source HP 3PAR StoreServ Storage systems. The Recovery Sets on Target StoreServ tab appears. Figure 42 Recovery Sets on Target StoreServ Managing Remote Recovery Sets This section describes how to manage the Remote Recovery Sets. You can perform the following tasks from the Manage tab: Mounting Remote Recovery Sets Unmounting Remote Recovery Sets Viewing Source and Target StoreServ Recovery Sets 91

92 Attaching Remote Recovery Sets Detaching Remote Recovery Sets To manage the Remote Recovery Sets: 1. Log in to the VMware vsphere Web Client. 2. Click vcenter Remote Recovery Configurations. All Remote Recovery Sets associated with the host or cluster are displayed. 3. Select a Remote Recovery Configuration from the left navigation pane. 4. Click Recovery Sets on Source StoreServ. All Recovery Sets on the Source StoreServ are displayed. 5. Double-click a Recovery Set and click the Manage tab. Figure 43 Remote Recovery Sets Manage tab 92 Working with Remote Recovery Sets Configurations

93 6. You can perform the following tasks from the Manage tab: Mounting a Remote Recovery Sets To mount Remote Recovery Sets, see Mounting Remote Recovery Sets (page 93). Unmounting a Remote Recovery Sets To unmount Remote Recovery Sets, see Unmounting Remote Recovery Sets (page 95). Attaching a Remote Recovery Sets To attach Remote Recovery Sets, see Attaching Remote Recovery Sets (page 95). Detaching a Remote Recovery Sets To detach Remote Recovery Sets, see Detaching Remote Recovery Sets (page 97). NOTE: For more information about the tasks that are enabled for Recovery Sets on Source StoreServ and Recovery Sets on Target StoreServ, see Managing Remote Recovery Sets in various configurations (page 97). Mounting Remote Recovery Sets This section describes how to mount Remote Recovery Sets to an ESXi host or a proxy host. Be sure that you are in the Manage tab to mount the Remote Recovery Sets. For information on navigating to the Manage tab, see steps 1 through 6 in Managing Remote Recovery Sets (page 91). NOTE: In a Remote Recovery Set configuration, you must mount the Recovery Set Snapshots to an ESXi Server other than the server where the base volume is already mounted. You can mount snapshots that are available only on the source HP 3PAR StoreServ Storage system. To mount Remote Recovery Sets: 1. Click Mount/Unmount to mount a Recovery Set that is not mounted to an ESXi host. Managing Remote Recovery Sets 93

94 2. Select one of the following options: Mount on ESXi host as Datastore Select from a list of ESXi host managed by the vcenter Server that shares access to the HP 3PAR StoreServ Storage System. Figure 44 Mounting Snapshots ESXi host Mount on proxy host Select from a list of hosts that are not managed by the vcenter Server, but which have access to the source HP 3PAR StoreServ Storage System. Figure 45 Mounting Snapshots Proxy host 3. Click Yes to confirm. The Recovery Set is mounted on the selected host. NOTE: After the Recovery Set is successfully mounted, the status changes from Available to Mounted. 94 Working with Remote Recovery Sets Configurations

95 Unmounting Remote Recovery Sets This section describes how to unmount Remote Recovery Sets. CAUTION: RMC-V does not verify that the volume you unmount is active or inactive. Therefore, be sure that the volume is inactive before you unmount it. Be sure that you are in the Manage tab to unmount the Remote Recovery Sets. For information on navigating to the Manage tab, see steps 1 through 6 in Managing Remote Recovery Sets (page 91). To unmount a Remote Recovery Set that is already mounted: 1. Select the Recovery Set you need to unmount and click Mount/Unmount. The Unmount Volume window appears. Figure 46 Unmounting Volumes 2. Verify the details mentioned on the Unmount Volume window and click Unmount. NOTE: After the Recovery Set is successfully unmounted, the status changes from Mounted to Available. The target site's Remote Recovery Set of the source HP 3PAR StoreServ Storage allows you to perform only mount task to the proxy host if the Target StoreServ does not have any Virtual Volume path exported to the ESXi host managed by the vcenter Server. Attaching Remote Recovery Sets This section describes how to copy a Remote Recovery Set to a datastore and how to attach a Recovery Set to a Virtual Machine. Be sure that you are in the Manage tab to attach the Remote Recovery Sets. For information on navigating to the Manage tab, see steps 1 through 6 in Managing Remote Recovery Sets (page 91). NOTE: You can attach a Remote Recovery Set only if it is already mounted. To attach a Remote Recovery Set: 1. Select a mounted Recovery Set that you need to attach to a VM. 2. Click Copy/Attach/Detach to mount a Recovery Set. The Copy/Attach window appears. The Copy to Datastore option is selected by default. Managing Remote Recovery Sets 95

96 Figure 47 Copying to a Datastore 3. Select one of the following options: Copy to Datastore Select the datastore to which you need to copy the selected Recovery Set. Attach to Virtual Machine Select the Virtual Machine to which you need to attach the selected Recovery Set. NOTE: If you select Attach to Virtual Machine, the Copy button changes to Attach. 4. To copy the Recovery Set to a datastore: a. Select Copy to Datastore. The associated datastores are displayed. b. Select the datastore to which you need to copy the Recovery Set. c. To overwrite an existing VMDK file, select Overwrite existing Virtual Disk. d. Click Copy. e. Click Yes to confirm. The Recovery Set is successfully copied to the datastore. NOTE: Copying Recovery Sets to a datastore is also known as copy VMDK. When you copy a VMDK file from the Express Protect object datastore, the copied VMDK is always thick provisioned. 96 Working with Remote Recovery Sets Configurations

97 5. To attach the Remote Recovery Set to a VM: Figure 48 Attaching to a Virtual Machine a. Select Attach to Virtual Machine. All the associated virtual machines are displayed. b. Select the virtual machine to which you want to attach the Recovery Set. c. Click Attach to attach the Recovery Set. d. Click Yes to confirm. The Recovery Set is successfully attached to the VM. Detaching Remote Recovery Sets Be sure that you are in the Manage tab to detach a Remote Recovery Sets. For information on navigating to the Manage tab, see steps 1 through 6 in Managing Remote Recovery Sets (page 91). NOTE: You can detach a Remote Recovery Set only if it is already attached. To detach a Remote Recovery Set: 1. Select the Recovery Set you need to detach from the list of Recovery Sets. 2. Click Copy/Attach/Detach. The Detach window appears. 3. Confirm the details mentioned in the Detach window and click Detach. Managing Remote Recovery Sets in various configurations Single vcenter Server Managing both sites Tasks possible from Recovery Sets on Recovery Sets on Source StoreServ and Recovery Sets on Target StoreServ tabs Mount, Unmount, Attach, and Detach; if mounted to the same ESXi host. Managing Remote Recovery Sets 97

98 Tasks possible from Recovery Sets on Recovery Sets on Source StoreServ and Recovery Sets on Target StoreServ tabs Mount and Unmount; if mounted to a proxy host. NOTE: After failover, the Recovery Sets listed in Recovery Sets on Source StoreServ and Recovery Sets on Target StoreServ tabs are interchanged. One vcenter Server at each site (one at Primary Site and another at Secondary Site) Tasks possible from the Primary vcenter Server: Tasks possible from Recovery Sets on Recovery Sets on Source StoreServ tab Mount, Unmount, Attach, and Detach; if mounted to the same ESXi host. Tasks possible from Recovery Sets on Recovery Sets on Target StoreServ tab None. We have to use the remote site for the supported tasks. Tasks possible from the Secondary vcenter Server: Tasks possible from Recovery Set on Recovery Sets on Source StoreServ tab Mount and Unmount tasks on ESXi and proxy hosts. Tasks possible from Recovery Set on Recovery Sets on Target StoreServ tab None. We have to use the remote site for the supported tasks. One vcenter Server managing Primary Site and Remote Site (with one RMC Appliance) Tasks possible from the Primary vcenter: Tasks possible from Recovery Sets on Recovery Sets on Source StoreServ tab Mount, Unmount, Attach, and Detach; if mounted to same ESXi host. Tasks possible from Recovery Sets on Recovery Sets on Target StoreServ tab None of the tasks are allowed. We have to use the remote site for the supported operations. Managing Remote Recovery Sets in Peer Persistence Tasks possible from Recovery Sets on Recovery Sets on Source StoreServ and Recovery Sets on Target StoreServ tabs Mount, Unmount, Attach, and Detach; if mounted to same ESXi host. Tasks possible from Recovery Sets on Recovery Sets on Source StoreServ and Recovery Sets on Target StoreServ tabs Mount and Unmount; if mounted on a proxy host. NOTE: After failover, the Recovery Sets listed on the Recovery Sets on Source StoreServ and Recovery Sets on Target StoreServ tabs are interchanged. For more information on Peer Persistence, see Peer Persistence (page 99). Deleting Remote Recovery Sets This section describes how to delete a Remote Recovery Set: 1. Navigate to the vsphere Web Client home page. 2. Click vcenter Remote Recovery Configurations. 3. Select a Remote Recovery Configuration from the left navigation pane. 4. Click Recovery Sets on Source StoreServ or Recovery Sets on Target StoreServ from the left navigation pane. All the Recovery Sets pertaining to the selection is displayed. 5. Select the Remote Recovery Set that you wish to delete from the left navigation pane. 6. Right-click, and then click Delete. 7. Click Yes to confirm deletion of the Remote Recovery Set. The Remote Recovery Set is deleted from the list. 98 Working with Remote Recovery Sets Configurations

99 Updating Recovery Manager Cache You must update the Recovery Manager Cache and do a vcenter refresh for the changes to appear after you perform the following tasks: Any changes are made to the storage systems A new Remote Copy Group is presented A failover happens To update Recovery Manager Cache: 1. Log in to the vsphere Web Client. 2. Click vcenter Remote Recovery Configurations. 3. Select a Remote Recovery Configuration from the left navigation pane. 4. Right-click, and then click Update Recovery Manager Cache. 5. Click Yes to confirm the update of the Recovery Manager cache. Peer Persistence HP 3PAR Peer Persistence is available for VMware configurations with HP 3PAR OS MU2 and later, and for Microsoft Windows configurations with HP 3PAR OS and later. Peer persistence provides the ability to redirect host I/O, either manually or automatically, from the source to the target storage system in a manner that is transparent to the host while causing minimal disruption to service. For information on configuring Peer Persistence, see HP 3PAR Remote Copy Software User Guide. Figure 49 Remote Copy Configuration Peer Persistence In Peer Persistence configuration, the source and target Remote Copy Groups must be managed by a single RMC instance and vcenter Server. For information on registering a remote RMC appliance, see Registering Remote RMC Appliances (page 79). The source and target Remote Recovery Sets are displayed in the RMC-V Plug-in GUI (Web Client). Since the virtual volumes under the source and target Remote Copy Groups are exported to an ESXi host from the same vcenter Server, the tasks: Attach, detach, mount, and unmount tasks can be performed on the source Remote Recovery Sets. Mount and unmount tasks can be performed on the target Remote Recovery Sets. Updating Recovery Manager Cache 99

100 NOTE: While configuring Peer Persistence, be sure that: The source and target volumes are already presented to the ESXi host. For more information on managing the Remote Recovery Sets (Mount, Unmount, Attach, and Detach), see Managing Remote Recovery Sets in Peer Persistence (page 98). You can then perform all other tasks related to Remote Recovery Sets. Express Protect for Remote Recovery Sets You cannot take a backup of Remote Copy groups snapshots. However, you can create a local Recovery Set of the virtual machine or datastore, and then take a backup. For more information on taking Recovery Set backup, see Creating Express Protects (page 108). Multiple RMC Appliance support for Remote Copy configurations Remote copy configuration can coexist with multi-rmc configurations. However, only one RMC Appliance manages remote copy configurations, policies, and operations. The first registered RMC appliance is implicitly used for managing the Remote Copy Snapshots. If the first RMC appliance is removed from the configuration, Remote Copy Snapshots and the configuration information will not be available anymore. On the removal of the first RMC appliance from the multi-rmc configuration, the next available RMC appliance is used for Remote Copy operations. However, you are required to create the Remote Copy policies and schedules again. Figure 50 Remote Copy configurations with Multiple RMC appliances ESXi Server RMC-V Plugin Storage Administrator Portal RMC 1 RMC 2 RMC 3 RMC Local Site Remote Site 100 Working with Remote Recovery Sets Configurations

101 11 Working with Recovery Sets Express Protect HP Express Protect enables you to back up snapshots that are created on HP Storage Systems and store to HP StoreOnce device. For more information on Express Protect, see the documentation provided with your HP StoreOnce product. Prerequisites Make sure that: Backup System is added to your RMC Appliance using Storage Administrator Portal. HP 3PAR StoreServ Storage system running HP 3PAR OS MU1 to make use of Express Protect. Catalyst license on HP StoreOnce. Adding HP Backup Systems To add a new Express Protect system, see Storage Administrator Portal (page 39). NOTE: You can verify the details of a newly added Express Protect and Storage systems in the RMC Appliance GUI Interface. For information on logging in to the RMC Appliance GUI Interface and viewing the HP StoreOnce Recovery Manager Central Dashboard screen, see the HP StoreOnce Recovery Manager Central User Guide. You can verify the newly added Storage and Backup systems from Recovery Manager Central GUI under Administration. Types of Backups RMC-V supports the following types of backup: Full backup Incremental backup RMC-V supports the following backup options: Single Stream Multi-stream NOTE: If you do not select the Multi-stream option, the Express Protect is performed as single stream. Both multi-streaming and single stream support Express Protect with verification or without verification. RMC-V supports multi-streaming of 2, 4, 8, or 16 streams for virtual volumes. When you perform a multi-stream Express Protectwith verification, Express Protect verification is also performed concurrently as multi-stream. Multi-streaming is a configuration whereby data from multiple sources is backed up concurrently to one endpoint device. Prerequisites 101

102 HP StoreOnce multi-node configuration RMC-V supports both single node and multi-node configurations. If Express Protect is in progress and the associated node fails, then Express Protect fails. However, when a new Express Protect job triggers next time either through a schedule or manually, the Express Protect takes the path of the surviving node and completes the Express Protect task successfully. For information on configuring HP StoreOnce in single node or multi-node configurations, see the HP StoreOnce documentation. NOTE: Federated catalyst is a single Store that is created using both the Service set IDs. Federated catalysts are not supported in RMC-V. Adding Express Protect systems For information on adding Express Protect, see Adding HP Backup systems (page 41). TIP: You can also add, edit, or delete an Express Protect system using RMC GUI. For more information, see HP StoreOnce Recovery Manager Central User Guide. You can also add, edit, or delete an Express Protect system using Storage Administrator Portal (page 39). Creating Express Protect policies You can define Express Protect policy parameters such as multi-streaming, backup system, store name, CoFC, Coeth, and transport protocol types FC or iscsi. NOTE: RMC-V does not support editing and deleting the existing Express Protect policies. To set up an Express Protect policy with the CoFC option enabled, the FC connectivity between the RMC Appliance and HP StoreOnce must be appropriately configured. Creating default Express Protect policies This section describes how to create default Express Protect policies. To create default Express Protect policies for your HP StoreOnce backup system. 1. Navigate to the vsphere Web Client home page. 2. Click Hosts and Clusters. 3. Select a VM and click Recovery Sets on the left navigation pane. System displays all the available Recovery Sets in the Recovery Sets tab under Related Objects tab. 4. Select a Virtual Machine to apply a set of policies. 102 Working with Recovery Sets Express Protect

103 5. Click Actions All HP StoreOnce Recovery Manager Actions Set Recovery Set Creation Policy, and then click Express Protect. The Default Express Protect Policy Settings screen appears. Table 8 Creating default Express Protect policies Group name Field name RMC Host Name Express Protect Policy Create Policy Backup system Store Multi-Streaming Verify Express Protect Description The IP address of the deployed RMC appliance. If you have deployed more than one RMC appliances, then all appliances are listed. Select an Express Protect policy from the list of policies available in the drop-down list. The listed Express Protect policies are bound to the RMC instance that you have selected. Click Create Policy to create a new Express Protect policy. NOTE: For information on creating policies, see Creating new Express Protect policies (page 104). Defaulted from Create New Express Protect Policy Defaulted from Create New Express Protect Policy Defaulted from Create New Express Protect Policy Defaulted from Create New Express Protect Policy Creating Express Protect policies 103

104 Table 8 Creating default Express Protect policies (continued) Group name Numeric Field name Coeth IP CoFC IP Storage array access protocol Maximum Number of Express Protects Remove Oldest Express Protect Description Details of this field is displayed only if you have selected a Coeth IP in Create New Express Protect Policy. Details of this field is displayed only if you have selected a CoFC IP in the Create New Express Protect Policy. Displays either iscsi or FC protocol that you selected in the Create New Express Protect Policy. Specify the maximum number of Express Protects that you need to retain. Express Protect count zero indicates that no upper limit is set on the maximum number of Express Protects. If you save the default policy, the maximum number of Express Protects count is set to five. Select this option to remove the oldest Express Protect after the maximum defined limit of Express Protect is reached. If you do not select this option, then the Express Protect that you take after the maximum number of permissible Express Protects is reached will fail. The Remove Oldest Express Protect option is not selected by default. Select this option to continue backups after the maximum number of Express Protect is reached. IMPORTANT: HP recommends that you specify the value of Maximum Number of Express Protects in the policy to be greater than one. Otherwise, incremental Express Protect will fail; because, the first Express Protect is always a full Express Protect. If you set the value to zero and create few Express Protects and later, if you change the number of Express Protect policies to a number that is less than the number of Express Protects already created, then the system displays an error message stating that the number cannot be less than the number of already existing Express Protect. NOTE: Express Protects of all the registered RMC instances are displayed and is not dependent on the RMC instance that is currently active. To view the CoFC ID, click the Fibre Channel tab of HP StoreOnce Management Console. Depending on the parameter selected in the Create New Express Protect Policy, only that value is displayed. Creating new Express Protect policies To create a new Express Protect policy for a datastore or a VM: 104 Working with Recovery Sets Express Protect

105 1. Click Create Policy from Create Express Protect Recovery Set or Default Express Protect Policy Settings screen. The Create New Express Protect Policy screen appears. 2. Specify a name for the Express Protect policy in Express Protect Policy Name. 3. Express Protect System lists the IP address or the name of the added Express Protect system. 4. Service Set Id The ID of the Service Set on which the store resides (StoreOnce 6500 and B6200). If HP StoreOnce is configured in multi-node, then service set IDs for both nodes are displayed. Select an appropriate service set Id for the policy. 5. Store Select an existing store from the menu. Click Create/Modify Store to either create a new store or to grant access to an existing catalyst client. TIP: You can also manually create a new store using HP StoreOnce Management Console. Creating Express Protect policies 105

106 a. The Modify StoreOnce Catalyst Store window appears. NOTE: If a Store already exists, then Modify Existing Store option is selected by default. However, if there are no stores, then Create Store option is selected by default. For a multi-node StoreOnce, RMC-V supports only one catalyst store per service set ID. However, RMC-V does not support teamed catalyst store. b. Select one of the following options: Create Store To create a new Express protect store. Modify Existing Store To grant access to a user for the Express protect store. c. If you select Modify Existing Store, you can grant access to a user: i. Specify a valid catalyst user name in User name. This user must exist in the HP StoreOnce Backup system. If you enter a wrong user name, system displays an error message prompting you to enter a valid user name. NOTE: If you specify All Clients as the catalyst client user name, then access is granted to all the existing clients in the selected store. ii. Click Grant Access. A confirmation message appears after the access is successfully granted. 106 Working with Recovery Sets Express Protect

107 d. If you select Create Store, you can create a new Express Protect store: i. Backup System lists the IP addresses or backup system name of the configured HP StoreOnce Backup systems. Select an appropriate IP address. ii. Specify a name of the store in Store Name. iii. Specify a brief description of the store in Store Description. iv. Service Set Id lists all the service set Ids associated with the HP StoreOnce Backup system that you selected. For single-node HP StoreOnce Backup systems, the service set Id is 1 and for multi-node HP StoreOnce Backup systems, the service set Id is more than one set Id. Select an appropriate service set Id based on where the store resides. v. To grant access to the Catalyst Client, navigate to the Express Protect policy window in the vsphere Web Client, click Modify store, provide the catalyst user name, and then grant access to the catalyst client. Alternatively, you can also grant access from the StoreOnce Management Console. NOTE: If the Client Access Permission is not checked in the Settings tab of the Confirm page, user credentials will not be validated for any Express Protect activity. vi. vii. Click Create. Click Yes when you are prompted for confirmation. Creating Express Protect policies 107

108 A confirmation message is displayed after the datastore is created. NOTE: When Express Protect is triggered, the snapshot is mapped in RMC appliance as a raw block device in the appliance OS. 6. The following fields display the status when the policy was created and you cannot modify these status from this screen: Backup System Default Policy Store Multi-Streaming When you select this option, the number of streams also appears. The default value is 4. For information on selecting values for multi-streaming, see the SPOCK. Verify Express Protect Catalyst over Fiber Channel (CoFC) CoFC Id Catalyst over Ethernet (Coeth) If HP StoreOnce is configured in multi-node, then you must provide the node IP of the corresponding service set ID that you have selected. To see the node IP of the service set ID, navigate to the tab of HP StoreOnce Management Console. Creating Express Protects You can create Express Protect of a datastore or a VM using a VC-level Express Protect (Create Express Protect Recovery Set screen) or one-click Express Protect. Creating one-click Express Protect You can use one-click Express Protect to create a snapshot and take the Express Protect. 1. Navigate to the home page and click VMs and Templates. 2. Click the Virtual Machine for which you need to create the Recovery Set. 3. Click Related Objects, and then click Recovery Sets. All the Recovery Sets related to the Virtual Machine are displayed. 108 Working with Recovery Sets Express Protect

109 4. Right-click the Virtual Machine, and then click All HP StoreOnce Recovery Manager Actions Create Recovery Set and then click Express Protect. The Create Express Protect Recovery Set page appears. NOTE: The Expiration/Retention option is not available for VVOL VMs. Creating one-click Express Protect 109

110 5. Enter the following details: Name Specify a name for the Express Protect. Description Specify a brief description for the Express Protect. Incremental Express Protect Select this box for incremental Express Protect. All other fields in this screen are display fields and you cannot modify them. NOTE: If you do not provide a name for the snapshot or Express Protect, the timestamp of the RMC instance is considered as the default snapshot or Express Protect name. When you take a one-click Express Protect, system internally creates a snapshot for the Express Protect. If there is a numeric policy set for the snapshot, then it will trigger deletion of the oldest snapshot when you take an Express Protect if Remove Oldest Snapshot is selected. HP recommends that you set the number of snapshots such that you are able to take both snapshots and Express Protect created by RMC-V. Numeric policy count with remove oldest snapshot must be set such that the Express Protect operation of the oldest snapshot can be completed before it reaches numeric policy limit set. If Express Protect of the oldest snapshot is not complete and numeric count reaches the limit, then the subsequent scheduled Express Protects start failing until the Express Protect operation of the oldest snapshot completes. This might happen for Express Protects such as full Express Protects or incremental Express Protects with large amount of changes, that take a long time to complete. For information on setting the numeric policy count, see Modifying Recovery Set policies (page 53). Creating VC-level Express Protect 1. Navigate to the vsphere Web Client home page. 2. Click Hosts and Clusters. 3. Select a VM and click Recovery Sets on the left navigation pane. System displays all the available Recovery Sets in the Recovery Sets tab under Related Objects tab. 4. Select a Virtual Machine to take Express Protect. 5. Click Actions (Actions for selected objects in this list), and then click Create Express Protect Recovery Set. The Create Express Protect Recovery Set window appears. 110 Working with Recovery Sets Express Protect

111 Figure 51 Create Express Protect Recovery Set 6. Specify the following information in the Express protect section: RMC Host Name The IP address of the selected RMC instance is displayed by default. This is a display field and you cannot change it from this screen. Name A name for the Express Protect. Description A brief description of the Express Protect. 7. To apply an existing policy for the Express Protect, select a backup policy from the policies listed in Express Protect Policy. The following details are listed for the selected policy: Backup System Default Policy The Default Policy check box is selected by default if a default Express Protect policy is saved for the VM or datastore. If Default policy is selected, then you cannot select any other Express Protect policy listed in Policy. To enable selecting a policy other than the default policy, you need to clear the Default policy check box. If a default policy does not exist, then the following message appears indicating that you have not saved any default Express Protect policy for the VM/DS: Creating VC-level Express Protect 111

112 No default backup policy exists. Backup Store Multi-Streaming Verify Express Protect CoFC Id (Catalyst over Fiber Channel) or Coeth IP (Catalyst over ethernet) that you have selected. Storage array access protocol Maximum number of Express Protects Remove Oldest Express Protect Backup System, Multi-Streaming, Verify Express Protect, CoFC Id, Coeth IP, Storage array access protocol, Express Protect Store, Maximum number of Express Protects, and Remove Oldest Express Protect are display fields. They display the respective values used during creation of the selected Express Protect policy. 8. Select one of the following protocols to access the Storage array: FC iscsi 9. To create and apply a new policy, click Create Policy. NOTE: For information on creating policies, see Creating new Express Protect policies (page 104). 10. Click Create and then click Yes to confirm creation of the Express Protect. IMPORTANT: If full backup recovery set is not available, incremental Express Protect fails. Scheduling Express Protects This section describes the following scheduling tasks for an Express Protect: Viewing a schedule list Add Adding a schedule. Edit Editing a schedule. Delete Deleting a schedule. Refresh Refreshing a schedule. Close To close the Schedule List window. IMPORTANT: If you make changes to virtual volumes that are managed by RMC-V from outside RMC-V, you must do a refresh before you perform any RMC-V tasks. For more information see the Troubleshooting (page 133) section. Viewing a schedule list 1. Navigate to the vsphere Web Client home page. 2. Click Hosts and Clusters. 3. Click a datastore or VM, and then click Recovery Sets on the left navigation pane. System displays all the available Recovery Sets in the Recovery Sets tab, under the Related Objects tab. 4. Select a Virtual Machine or datastore to apply a schedule. 112 Working with Recovery Sets Express Protect

113 5. Click Actions All HP StoreOnce Recovery Manager Actions Schedule Recovery Set Creation. The Schedule List window appears. This window lists the RMC Instance, time zone of the RMC Instance and all tasks that are currently scheduled for Express Protect. From the Scheduled List window, you can add an Express Protect, modify an existing schedule for an Express Protect, or delete an existing Express Protect schedule. 6. Click Close to close the Scheduled List. You can automatically create Express Protects according to a specified schedule. Creating schedules To create a schedule for an Express Protect: 1. Navigate to the Schedule List. NOTE: For information on navigating to the Schedule List, see Viewing a schedule list. 2. Click Add, to create data protect Express Protect schedule task. The Welcome tab of the Create Schedule Task Wizard window appears. 3. Click Next. The Recovery Set Type window appears with the following options: Snapshot To schedule creation of snapshot for a virtual machine or datastore. Express Protect To schedule Express Protect of snapshot for a virtual machine or datastore. 4. Select Express Protect to create a schedule for an Express Protect. Scheduling Express Protects 113

114 5. Click Next. The Schedule window appears. a. Specify a task name for the schedule in Schedule task name. b. Select the task frequency from Perform Recovery Set creation task to create an Express Protect schedule. The following frequencies are listed: i. Hourly ii. Daily iii. Weekly You can select one or more days of a week to schedule the task. iv. Monthly You can select a particular date to schedule the task. v. One time only You can select a date and time to schedule the task for only one time. Additional options are displayed when you select a frequency from Perform Recovery Set creation task. Table 9 (page 114) lists the frequency details of a schedule: Table 9 Scheduling frequency Frequency Daily Hourly Monthly One time only Weekly Frequency details Start time Recur Every Start time Recur Every Start time Day Start date Start time Start time Recur Every Select day(s) of a week below Description You can specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the frequency of the scheduled task. You can specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the frequency of the scheduled task. You can specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the day of the month to start the scheduled task. Select the date on which you need to schedule the Express Protect. You can specify the schedule start time in hours and minutes. Also, select AM or PM. You can specify the schedule start time in hours and minutes. Also, select AM or PM. Specify the frequency of the scheduled task. All the seven days of a week are displayed. You can select one or more days to schedule a weekly Express Protect. 114 Working with Recovery Sets Express Protect

115 6. Click Next. The Snapshot Configuration window appears. Scheduling Express Protects 115

116 NOTE: The Expiration/Retention option is not available for VVOL VMs. 1. In Snapshot Configuration do the following: Select Create Recovery Set with VSS-aware application consistency to create application consistent Recovery Sets. Select one of the following options: To apply the schedule to all the VMs, select Apply to all Virtual Machines on the datastore that you selected to schedule. To apply the schedule task to specific VMs, select Apply to following Virtual Machine(s), and then select the required Virtual Machines. NOTE: Overwrite default policy setting is disabled for numeric policies. For Expiration/Retention policies this option is enabled. You can modify the values for Set Recovery Set to expire after and Retain Recovery Set of the default policy. The Expiration/Retention option is not available for VVOL VMs. Therefore, Expiration/Retention details are not displayed for VVOL VMs. 7. Click Next. The Express Protect Configuration window appears. 116 Working with Recovery Sets Express Protect

117 Specify the following details: Name A name for the Express Protect. Description A brief description of the Express Protect. 8. To apply an existing policy for the backup, select a backup policy from the policies listed in Express Protect Policy. The following details are listed for the selected backup policy: Backup System Default Policy Express Protect Store Multi-Streaming Verify Backup Express Protect Backup Maximum number of Express Protects Remove Oldest Express Protect 9. Click Next. The Schedule Task Summary window appears. Verify that the details listed in Schedule Task Summary are correct. 10. Click Finish to complete the task schedule. The Schedule Modification window appears. Click Yes to confirm and schedule the task. NOTE: If a VM or datastore is removed, then the associated scheduled tasks continue to run. However, these tasks cannot be managed from the vsphere Web Client. Therefore, the task must be manually removed from RMC-V Scheduler GUI. Modifying Express Protect schedules To update an existing Express Protect schedule: 1. Navigate to Schedule List. NOTE: For information on navigating to the Schedule List, see Viewing a schedule list. 2. Select the schedule that you need to edit and click Edit. The Edit Schedule Task Wizard appears. 3. Click Next until you reach the Schedule and Snapshot Configuration pages of the Edit Schedule Task Wizard. 4. Make appropriate changes to the schedule. For information on setting the schedule parameters, see Scheduling Recovery Sets (page 68). 5. Click Next. The Schedule Task Summary window appears. Verify that the details listed in Schedule Task Summary are correct. 6. Click Finish to complete the task schedule. The Schedule Modification window appears. Click Yes to confirm the changes made to the schedule. Viewing Express Protect details You can view the details of the Backup system on the Summary tab. 1. Navigate to the vsphere Web Client home page. 2. Click Hosts and Clusters. Modifying Express Protect schedules 117

118 3. Click the VM, and click Recovery Sets on the left navigation pane. The system displays all the available Recovery Sets in the Recovery Sets tab below Related Objects of a VM. 4. Double-click datastore time stamp to view the details. The Manage tab appears with the message, No manage operations exist for backup. 5. Click Manage. The No manage operations exist for backup details appear in the Summary tab. You can view the following details in the Summary screen: Field name vcenter Name Type Express Protect Name Express Protect GUID State Application Consistent Verified Catalyst Item Name Timestamp Express Protect Policy Name Store Name StoreOnce Name Catalyst User Snapshot Name SnapshotSet ID Incremental RMC Time Zone Description IP address or name of the vcenter. Name of the VM or datastore. Type of Express Protect, either VM or datastore. Name of the Express Protect. GUID of the Express Protect job. The state of the Express Protect, Partial or Available. If the snapshot from which the Express Protect is created is application consistent; True or False. Status of the Express Protect; True or False. The status True indicates that the Express Protect is completed and successfully compared with the source. Name of the catalyst item in HP StoreOnce. Time the Express Protect was created. Time is denoted in UTC time. Name of the Express Protect policy. Name of the Store in HP StoreOnce. Name of the HP StoreOnce Backup System. Name of the catalyst user in HP StoreOnce. Name of the snapshot. A unique ID of the snapshot. Is the Express Protect incremental. True for incremental Express Protect and False for non-incremental Express Protect. Time zone of the RMC appliance. 118 Working with Recovery Sets Express Protect

119 Element Recovery Technology Element Recovery Technology (ERT) provides you the ability to access Recovery Sets objects as read-only entities from HP StoreOnce protected Express Protect objects, without repopulating the primary disk array volumes. Transport protocols For ERT, the transport protocol: between ESXi host and RMC Appliance must be over iscsi between RMC Appliance and HP StoreOnce can either be FC or IP depending on CoFC Id (Catalyst over Fiber Channel) or Coeth IP (Catalyst over Ethernet). You can mount Express Protect objects only on ESXi hosts. ERT tasks can be performed only for Express Protect of the Recovery Sets created after installing or upgrading to RMC-V v For Express Protect objects that were created in previous versions, you can perform only mount, unmount, and additional vcenter operations on the mounted Express Protect objects. However copy, attach, and detach tasks cannot be performed. NOTE: ERT feature does not provide support for VMware VVOLs. ERT tasks You can perform the following ERT tasks on Express Protect objects from the vsphere Web Client GUI: Mounting Express Protect objects (page 120) Unmounting Express Protect objects (page 122) Copying VMDK files to Datastores (page 122) Attaching Express Protect objects (page 123) Detaching VMDK files from Virtual Machines (page 124) Detaching Express Protect objects Configuring ERT You must add in RMC host as a dynamic discovery target to the ESXi host adapter to discover the Express Protect object iscsi targets. Pre-requisites Be sure that the ESXi host has an iscsi Software Adapter configured as shown in Configuring ERT (page 119). Element Recovery Technology 119

120 Figure 52 Configuring ERT 1. Log in to the vsphere Web Client and select a host from the Inventory panel. 2. Click Manage Storage. 3. Click Storage Adapters and select the iscsi adapter that you need to configure from the list. 4. Click the Dynamic Discovery tab. 5. Under Adapter Details, click Targets, and then click Dynamic Discovery. 6. Click Add. 7. Enter the IP address of the RMC Appliance and click OK. NOTE: After adding the iscsi adapter details you are prompted to rescan HBA to make the changes effective. For more information on setting up a dynamic discovery, see VMware documentation. Mounting Express Protect objects This section describes how to mount an Express Protect object as a datastore to an ESXi host. 1. Navigate to the vsphere Web Client home page. 2. Click vcenter Datastore. All the datastores managed by the vcenter Server are displayed. 120 Working with Recovery Sets Express Protect

121 3. Select a datastore, click Related Objects Recovery Sets and then double-click the Express Protect that you need to mount. Figure 53 Mounting Express Protect 4. Click Mount/Unmount. Figure 54 Mounting Express Protect 5. The Mount on ESX host as Datastore lists the ESXi hosts managed by the vcenter Server. Select an appropriate ESXi host. 6. Click Mount. The Mount Express Protect Confirm dialog box appears. 7. Click Yes to confirm. After the Express Protect is successfully mounted, the status of the Express Protect changes to Mounted. After the Express Protect is successfully mounted, the following details are displayed: Mounted ESXi Host Mounted Datastore Name for Express Protect Object NOTE: You can perform a similar procedure to mount Express Protect on Virtual Machines also. Element Recovery Technology 121

122 Unmounting Express Protect objects This section describes how to unmount Recovery Sets. CAUTION: RMC-V does not perform any checks to ensure that the volume you unmount is active or inactive. Therefore, before you unmount a volume, ensure it is inactive. 1. Navigate to the Manage tab and select the Express Protect that you need to unmount. 2. Click Mount/Unmount. The Unmount Express Protect dialog box appears. 3. Click Unmount to unmount the selected datastore from the ESXi host. Copying VMDK files to datastores Copy a VMDK file from mounted Express Protect objects to a target datastore on an ESXi host. NOTE: When you copy a VMDK file from the Express Protect object datastore, the copied VMDK is always thick provisioned. 1. Navigate to the Manage tab. 2. From Virtual Disks, select the VMDK file that you need to attach and click Copy/Attach/Detach. The Copy/Attach window appears. 122 Working with Recovery Sets Express Protect

123 Figure 55 Copy to Datastore 3. To copy the VMDK file to a datastore: 1. Select Copy to Datastore. The datastores associated with the ESXi host are displayed. 2. Select an appropriate datastore to which you want to copy the Express Protect. The following fields are populated when you select a datastore: Target Datastore Virtual Disk to copy Virtual Disk target directory 3. Select Overwrite existing Virtual Disk to overwrite the VMDK file. 4. Click Copy to copy the VMDK file to the selected Datastore. 5. Click Yes to confirm. Attaching VMDK files to Virtual Machines This section describes how to attach a VMDK file from the mounted Express Protect objects to a VM on an ESXi host. Element Recovery Technology 123

124 NOTE: You can attach a VMDK file only if the Express Protect object is already mounted to an ESXi host. To attach a VMDK file: 1. Navigate to the Manage tab. 2. From Virtual Disks, select the VMDK file that you need to attach and click Copy/Attach/Detach. The Copy/Attach window appears. 3. To attach the VMDK file to a Virtual Machine click Attach to Virtual Machine. All datastores associated with the ESXi host are displayed. 4. Select an appropriate VM to which you want to attach the VMDK file. 5. Click Yes to confirm. Detaching VMDK files from Virtual Machines You can detach a VMDK file associated with an Express Protect that is attached to a Virtual Machine. 1. Navigate to the Manage tab. 2. From Virtual Disks, select the VMDK file that you need to attach and click Copy/Attach/Detach. The Detach window appears. 3. Click Detach and click Yes when prompted to confirm detaching the Express Protect. 124 Working with Recovery Sets Express Protect

125 Additional vcenter operations vcenter Server supports the following additional operations for mounted Express Protect objects: You can perform additional datastore related operations on the Express Protect objects using the vcenter GUI after the Express Protect object is mounted and presented as a datastore to an ESXi host. In the Manage tab, the Snapshot Datastore column of the Express Protects displays the name of the Express Protect object datastore after it is mounted. The newly presented datastore becomes available in the Datastores section of the vcenter GUI. On selecting the Express Protect datastore that are listed under Manage Files, you can browse and edit contents of the datastore. HP recommends that you use Express Protect datastores only for restore purposes. You must not add or modify the contents on the datastores. You can instantiate VMs directly from the Express Protect datastore using the Register VM option that is available for a datastore. For information on registering a virtual machine with the vsphere Web Client, see VMware Documentation. Make sure that all virtual disks of the VM belong to the mounted Express Protect datastore. It is strictly recommended not to register a VM containing virtual disks across different datastores. HP recommends that you use the newly registered VM from the Express Protect datastore for temporary restore purposes and not to perform any data writes. After restoring a VM from an Express Protect object, if you use both the original and the restored VM at the same time, then IP address conflict might occur. Make sure that the IP addresses of the VMs are appropriately assigned to avoid any potential IP address conflict. You can v-motion the VM to a different datastore (also belonging to a different ESXi host) enabling active usage for production level environment, including write operations, of the newly restored VM. Managing concurrent Express Protects RMC Appliance allows you to submit any number of Express Protect jobs concurrently. You can reconfigure the vcpu and vram of the RMC Appliance so that the concurrent Express Protect jobs complete faster. Incremental Express Protects require double the number of streams, because it needs to read data from the HP StoreOnce system. For optimal Express Protect performance: Plan and schedule your Express Protect jobs to ensure that, at any point in time the number of data streams, is as shown in the Table 10 (page 125). For each RMC Appliance configuration the number of data streams can be determined from the number of volumes that are backed up and the number of streams that are selected per volume. Also consider Maximum Concurrent Data and Inbound Copy Jobs of the HP StoreOnce Backup system. This value is displayed in the StoreOnce catalyst below the Status and Settings tabs. Table 10 Concurrent data streams vcpu/vram 2/8 GB (default) 4/16 GB 8/32 GB 16/64 GB Maximum data streams permitted Managing concurrent Express Protects 125

126 Types of restores RMC-V supports the following types of restores: Restore datastore snapshots from HP 3PAR StoreServ Storage This is supported only on datastore level snapshots. If you have a VM level snapshot, restore operation is not allowed. Restore backup from HP StoreOnce This is supported for both datastores and VM level Express Protect to HP StoreOnce tasks. Restoring from Express Protects This section explains how to restore the backed-up datastores and virtual machines. NOTE: All VMs in the datastore must be shut down before you perform a restore. Recommendations for Restore to Snapshot HP recommends that you have the following conditions applied to the parent volume before you perform restore to snapshot: Do not to use a CPG that has a set Growth Limit for Copy CPG. Clear the Allow stale snapshots check box on the virtual volumes that are exported to a host. Prerequisites for restoring to any Volume If you need to do restore to any volume, be sure that the following prerequisites are met: The storage system must be registered with an RMC instance. The Volume must exist on the storage system. The Volume must be read-write enabled. 1. Select the Express Protect that you need to restore. IMPORTANT: You can restore a Express Protect that is in available status. NOTE: Express Protects of Virtual Machines are listed under Recovery Sets tab and Express protects of datastores are listed under Datastores tab. Restore can be performed using the Express Protects of any of the RMC instances. However, you must not perform the restore operations simultaneously. 2. Click Restore. TIP: You can also perform a restore by clicking Actions Restore. 3. Select either of the following options: Restore to Snapshot If you select this option, system creates a snapshot first and then a restore is done. This snapshot is also listed below Recovery Sets. However, the field in the Summary screen of this snapshot, indicates that this snapshot is created as part of a restore. Restore to Parent Volume If you select this option, the backed-up data is restored to the parent virtual volume. 126 Working with Recovery Sets Express Protect

127 NOTE: Before you do a restore to parent volume, ensure that all the VMs in the datastore are powered off. First incremental backup after an Express Protect restore to parent might be longer than the normal incremental backup duration. Restore to any Volume If you select this option, the backed-up data is restored to any other virtual volume (existing in HP 3PAR StoreServ Storage system) except the parent volume. The following screen appears if you have selected restore for a Virtual Machine of type VMFS. This task will restore the VMFS Virtual Machine to another HP 3PAR StoreServ storage system registered with the RMC appliance. NOTE: The Array Volume must be created prior to performing the restore. The following screen appears if you have selected restore for a Virtual Machine of type VVOL. This task will restore and recreate the VVOL Virtual Machine to another storage container known to the vcenter Server. NOTE: The Array Volume must be created prior to performing the restore. Restoring from Express Protects 127

128 Specify the following details: 1. Virtual Machine Name Select an appropriate Virtual Machine from the list of the parent Virtual Machine name. By default, the parent Virtual Machine name is displayed along with the current time stamp. 2. Host Select an appropriate ESXi host from the list of compatible ESXi hosts that are available in the vcenter Server. 3. Resource Pool The parent resource pool of the selected ESXi host is displayed. 4. DataStore The VVOL datastores associated with the ESXi host are displayed. 5. Power on Virtual Machine After Restore Select this option to power on the recreated Virtual Machine. NOTE: Restoring a Virtual Machine of type VVOL to the parent volume does not restore the configuration information. However, if you need to restore the configuration information, then you must use the Restore to Another Volume (Recreate VM) option. 4. Click OK. The status of the Express Protect changes to restoring. After the restore is complete the status changes to available. NOTE: For restore to any volume, the OK button is enabled only if the Array Volume names are added. If you perform restore in a multi-node configuration and if the associated node fails, then the restore fails. To restore data, you must manually trigger the restore task and it will take the path of the secondary node and complete the restore task successfully. Additional steps to complete restore to any Volume If you have selected the Restore to Any Volume option during restore, then to complete the restore you must perform the following steps in addition to the procedure mentioned in the beginning of this section. 128 Working with Recovery Sets Express Protect

129 1. After the restore operation is successfully completed, export the volume from the storage system to the ESXi Server. 2. Scan the storage system once again. 3. If it s the same ESXi Server where the source virtual volume was presented then please check Create new signature and keep data intact option. 4. Refresh the datacenter from the vsphere Web Client. Mounting snapshots and performing Copy/Attach VMDK for snapshots created during restore to snapshot 1. Navigate to the Summary tab of the snapshot object and identify the snapshot name. 2. Log in to the HP 3PAR StoreServ Management Console and export the above identified snapshot to an ESXi host that you want to mount. 3. Log in to the vsphere Web Client select a host, a cluster, or a datacenter. 4. Click Actions All vcenter Actions Rescan Storage. The Datacenter Rescan Storage window appears. 5. Select Scan for New Storage Devices and Scan for New VMFS Volumes and click OK. The datastore is listed in the Related Objects tab of the Datacenter page. 6. Right-click on datastore that is newly created. Select Browse Files (the datastore, if on same ESXi host. will have the original name appended to it; otherwise, the same name will exist for the datastore.) 7. Select the required file. Right-click Download from Datastore. Navigate to another datastore and use the Upload a file to the Datastore option to copy the file. 8. Or, if you need to attach a VMDK to any other VM: a. Right-click the VM and select Edit Settings. b. Select the Existing Hard Disk option from the New Device drop-down list and click Add. The Select File window appears. c. Select the datastore, select a virtual machine folder, and select the disk to add. d. Review the selected options and click OK. Restoring from Express Protects 129

130 12 Licensing Overview Licensing is used to enable optional product functionality, such as capacity upgrades and replication. Most features are only enabled when they are licensed. Certain features are enabled only if they are licensed. For more information on licensing, see the HP StoreOnce Recovery Manager Central User Guide. HP 3PAR StoreServ licensing RMC and RMC-V licenses must be installed on HP 3PAR StoreServ Storage systems. NOTE: RMC does not allow users to install or delete RMC Base or RMC-V licenses. These licenses are directly installed on the HP 3PAR StoreServ Storage system. For information on installing these licenses, see the HP 3PAR StoreServ Storage documentation. HP StoreOnce licensing StoreOnce Catalyst license must be installed on HP StoreOnce Backup systems. NOTE: RMC does not allow users to install or delete a StoreOnce Catalyst license. This license is directly installed on the HP StoreOnce Backup system. For information on installing this license, see the HP StoreOnce documentation. License models supported by RMC-V The following types of licenses are available for RMC-V: RMC and RMC-V licenses HP StoreOnce Catalyst licenses Other licenses: Virtual Copy License Virtual Lock License Recovery Manager License of VMware vsphere License Remote Copy License Licenses required for RMC appliance and RMC-V to communicate with HP 3PAR StoreServ. Licenses required for RMC-V to communicate with HP StoreOnce. There are no checks made for these licenses in the code and an error message appears if they are not available. Virtual Copy license is required to create a snapshot in a virtual copy of a base volume. Virtual Lock license is required to enforces the retention period of any volume or copy of a volume. Locking a volume prevents the volume from being deleted intentionally or unintentionally before the retention period elapses. The Remote Copy license must be installed in the HP 3PAR StoreServ Storage system to perform any operations related to Remote Recovery Set Configurations. Licensing scenarios Table 11 (page 131) describes how the appliance handles licensing for different user actions: 130 Licensing

131 Table 11 Licensing scenarios User action License policy or type Result Notes Create Snapshot RMC-V license Create snapshot with Virtual Copy license expiration and retention Virtual Lock license time You can create a snapshot if a valid license exist. The license required is either Permanent or valid Temporary license. Create Backup StoreOnce Catalyst license You can back up your required files, if a valid license exists. The license required is either Permanent or valid Instant-On license. Mount, unmount, delete, and restore of snapshots. License not required All these operations function without licenses provided a valid license exist when a snapshot is created. Restore and delete all backups License is required All these operations function with licenses provided a valid license exists when a backup is created. Licensing scenarios 131

132 13 Using HP 3PAR Peer Motion Manager Software with RMC-V HP 3PAR Peer Motion Manager is a feature of the HP 3PAR Operating System Software and manages migration of data in between existing storage systems or third party storage arrays. RMC-V supports HP 3PAR Peer Motion Manager data migration activities without any impact on host operations while monitoring the primary storage system. NOTE: After the data migration between two HP 3PAR StoreServ Storage systems is complete, you must log out of Web Client, log in again, and the update the Recovery Manager cache. All scheduled tasks will fail until you perform Recovery Manager cache update after the data migration. Before migrating if the virtual volume is already in use by an ESXi host, the following conditions are applicable: The Virtual Copies created by a potential migrating virtual volume cannot migrate with its virtual volume during an active Peer Motion migration operation. The virtual copies become invalid from RMC-V perspective even if they continue to appear in RMC-V. You must log out of Web Client, log in again, and then update the Recovery Manager cache. You can access the virtual copies using HP 3PAR Inform Management Console or CLI. If you do not need these virtual copies you must manually remove them. RMC-V supports migration between two HP 3PAR StoreServ Storage systems only. Migration from HP EVA P6000 Storage to HP 3PAR StoreServ Storage is not supported. The existing snapshots are not migrated; only the base volume is migrated. After migration, the existing snapshot information for that VM will not be available. All virtual volumes that are part of a VM or datastore must be migrated during HP 3PAR StoreServ Storage to HP 3PAR StoreServ Storage Peer Motion. If all virtual volumes are not migrated, unexpected behavior might occur. For more information about performing Peer Motion data migration, see the HP 3PAR Peer Motion User Guide. To download the HP 3PAR Peer Motion User Guide click 3par/, navigate to your product page, click Support, and then click Manuals. NOTE: To view backups taken before Peer Motion, select one of the Restore Express Protect options in the Restore Now window in RMC GUI. To Restore backups taken before Peer Motion, select the Restore Express Protect option in the Restore Now window in RMC GUI. After Peer Motion, you must perform a full backup before you restart the incremental backup schedules on Virtual Machines or datastores. For more information on RMC GUI, see the HP StoreOnce Recovery Manager Central User Guide. 132 Using HP 3PAR Peer Motion Manager Software with RMC-V

133 14 Troubleshooting General instructions For any general troubleshooting issues, make sure that you perform the following tasks: Storage Administrator Portal Cache Refresh. Update Recovery Manager Cache. To update Recovery Manager Cache right-click any object and click All HP StoreOnce Recovery Manager Actions Update Recovery Manager Cache. Log out and log in again to the vcenter Server. Restart the following services: HP OneView for VMware vcenter VMware vcenter Web Client HP OneView for vcenter UI Manager IMPORTANT: When you restart the VMware vsphere Web Client service, be sure that other applications that are accessing this service are not impacted. While registering an existing RMC Appliance using the Register HP StoreOnce Recovery Manager Central Instance window, the following error appears: The address provided does not meet URI standards, please check that it is valid. Workaround: Log out and log in again to the vcenter Web Client and retry registering the RMC Appliance. When user navigates to the StoreOnce RMC Configuration page, the following error message is displayed: Web client session is not initialized. 133

134 This error might also be displayed if the RMC Appliance fails to add Storage or Backup systems. Workaround: During deployment of RMC, ensure that the DNS configuration is done correctly to resolve the hostname or FQDN (fully qualified domain name) of the vcenter server hostname, Storage system, and Backup system. This error might also be reported, if the RMC Appliance fails to add the Storage and Backup systems. After users upgrade HP 3PAR OS from to 3.2.2, the Incompatible version <version_number> found on storage system StorageSystem_number>, requires '322000' or above error message is displayed. Workaround: If you make any changes in the HP 3PAR StoreServ Storage system such as, upgrading HP 3PAR OS, changing HP 3PAR licenses, and so on, then before you perform any task, you must do a storage system refresh. To refresh the storage system details: 1. Log in to the RMC GUI ( or <Host_name>). 2. Click HP StoreOnce Recovery Manager Central Storage System Action Menu and then click Refresh. 3. Click Yes, Refresh for the changes to be effective. While loading the StoreOnce RMC Configuration page the progress bar appears does not display any progress. 134 Troubleshooting

135 Workaround: Log out and log in from the vcenter Server. However, if the same progress bar appears again, then restart the VMware vsphere Web Client service. IMPORTANT: When you restart the VMware vsphere Web Client service, be sure that other applications that are accessing this service are not impacted. When a Recovery Set Snapshot/Express protect backup restore is attempted while the target VM is powered on, the user is prompted to power off the VM and try again. The next attempt to restore with the VM powered off will execute, but the task will report a failure and the error message Failed to restore array Snapshot will be displayed. Workaround: Before you restore a Recovery Set Snapshot/Express protect backup: 1. Power off the VM. 2. Right-click the VM and then click All HP StoreOnce Recovery Manager Central Actions Update Recovery Manager Cache. Deployment While deploying RMC appliance using HP OneView for VMware vcenter, a network validation error appears in the Validation page if you have selected the Use static IPv4 settings option to select a virtual network in the Specify network settings page. 135

136 The static IP addresses fetched by the ESXi virtual network adaptor might be different from the static IP address that you intend to assign to the RMC appliance. This discrepancy in fetching the IP address from the ESXi virtual network adaptor might cause the One or more hosts is not accessible error in the Validation page during the deployment of the RMC Appliance. Workaround: To resolve this, perform the following steps: 1. Navigate back to the Specify network settings page. 2. Select the Obtain IPv4 settings automatically option in the Specify network settings page for the virtual network that displays the incorrect IP address range. 3. Click Next to continue. The validation is successful. 136 Troubleshooting

137 4. Click Next and complete the deployment. 5. After the appliance is successfully deployed, log in to the vcenter Sever and launch the RMC appliance console. 6. To view or to manually change the IP address, enter user name/ password as netconf/netconf. For more information about using the RMC appliance console, see the HP StoreOnce Recovery Manager Central User Guide. 137

138 Unable to connect to FTP server to download RMC executable for deploying RMC appliance through HP OneView for VMware vcenter. Workaround: Verify that the proxy server of your browser is appropriately set to access HP FTP site. When user deploys RMC using HP OneView for VMware vcenter, the events does not appear in the vcenter More Tasks pane. Workaround: Click Refresh icon in the Web Client GUI. The deployment events appear in the vcenter More Tasks pane. 138 Troubleshooting

139 Unable to view HP StoreOnce after adding it in Storage Administrator Portal or RMC GUI in StoreOnce RMC Configuration under Administration tab. StoreOnce RMC Configuration displays only HP 3PAR StoreServ added through Storage Administrator Portal. Workaround: StoreOnce RMC Configuration displays only HP 3PAR StoreServ Storage systems that you have added through Storage Administrator Portal. However, HP StoreOnce added through Storage Administrator Portal or RMC GUI are not displayed in the StoreOnce RMC Configuration. To view HP StoreOnce from the Default Express Protect Policy Settings click Create Policy. The Create New Backup Policy page appears. Select the appropriate HP StoreOnce from the Backup System menu. 139

140 To view the HP StoreOnce, log in to RMC GUI Dashboard, click HP StoreOnce Recovery Manager Central Backup Systems. To view the HP 3PAR StoreServ Storage systems, log in to RMC GUI Dashboard, click HP StoreOnce Recovery Manager Central Storage Systems. If VMDirectPath is not on enabled on the ESXi Server and if the user tries to create an Express Protect policy choosing the CoFC option, then the Express Protect policy creation fails displaying the error message Internal server error occurred. Workaround: To set up a Express Protect policy with CoFC option enabled, the FC connectivity between the RMC Appliance and HP StoreOnce must be appropriately configured. 140 Troubleshooting

141 If you do not have FC connectivity, then HP recommends that you choose the default option (other than CoFC) to create Express Protect policies. If HP OneView for VMware vcenter and vcenter are running on different servers, using a vcenter host name that is not a FQDN (Fully Qualified Domain Name) failed to perform any RMC tasks. Workaround: If you have HP OneView for VMware vcenter and vcenter running on two different servers, then HP recommends that you use FQDN while installing HP OneView for VMware vcenter. Also, make sure that the forward and reverse look-up validation is successful. Also, ensure that the host is pingable and returns the correct IPv4 IP address. After installing the RMC appliance or after upgrading RMV from v2.5.0 or later to RMC-V v1.2.0, and registering the HP 3PAR StoreServ Storage system, and HP StoreOnce, if you click HP recovery manager for Central system might display the error message This object not initialized. Workaround: While deploying the RMC appliance and upgrading RMV using HP OneView for VMware vcenter for the first time, the RMC Appliance might approximately take five minutes to configure by itself. This is a one-time activity. If you try to perform any other task during this time, system might display the initialization error. You need to wait for some time after the RMC appliance is successfully deployed. Log off and log in again to the vcenter Server and then perform any RMV task. System displays an error while communicating with HP services during RMC deployment or registration. Workaround: One of the reasons might be that the communication between HP OneView for VMware vcenter and vcenter Server. Even though user has configured HP OneView for VMware vcenter and vcenter Server in IPv4, it pings with IPv6. To resolve this, disable the IPv6, remove from the DNS entry, and try to ping IP/FQDN from both the HP OneView for VMware vcenter and vcenter Server. Both must ping using IPv4. While installing HP OneView for VMware vcenter v7.7.1 or upgrading from RMV v2.5.0 or later to RMC-V plug-in v1.2.0, the RMC-V plug-in does not appear or partially appears in the VMware vcenter Web Client. Workaround: To resolve this error: 1. Log off from VMware vsphere Web Client. 2. Restart the HP OneView for vcenter UI Manager service. 3. Restart the VMware vsphere Web Client service. 4. Log in to VMware vsphere Web Client. 5. Verify that 1. StoreOnce RMC Configuration & 2. StoreOnce RMC Credential options are available in Administration menu. 141

142 vcenter Upgrade The web session initialization fails after upgrading VMware vcenter from version 5.x to 6.0. After upgrading VMware vcenter to 6.0, do the following procedure before you use vcenter 6.0 with HP OneView for VMware vcenter: 1. Stop the Web Client service. 2. Go to C:\ProgramData\VMware\vSphere Web Client\vc-packages and delete data from the vc-packages folder. 3. Go to C:\ProgramData\VMware\vSphere Web Client\catalog\ VirtualCenter\5.5.0\en and delete all folders in the catalog that are related to HP OneView for VMware vcenter and RMC. 4. Go to C:\Users\<user>\AppData\Roaming\VMware\vpx\catalog\ VirtualCenter\5.5.0\en and delete all folders related to HP OneView for VMware vcenter and RMC. 5. Repeat steps 1 through 4 for: AppData\Local and AppData\LocalLow. All users in C:\Users. 6. Clear the web browser cache. 7. Start the Web Client service. This will deploy vcenter 6.0 versions of HP OneView for VMware vcenter and RMC-V plug-ins. 8. If vcenter 6.0 versions of HP OneView for VMware vcenter and RMC-V plug-ins are not deployed then: 1. Verify that the vcenter Service is stable and running. 2. Restart the Web Client service again. 9. Open the virgo log file and verify that the vcenter 6.0 version of the HP OneView for VMware vcenter and RMC plug-ins are deployed. The virgo log file for vcenter 6.0 is available at C:\ProgramData\VMware\ vcenterserver\logs\vsphere-client\logs. And vc-packages in vcenter 6.0 is available at C:\ProgramData\VMware\ vcenterserver\cfg\vsphere-client\vc-packages NOTE: This procedure is applicable for the installation of the vcenter Server in Windows environment. However, if you are using VCVA/VCSA, then click HP Administration vcenter Credentials and register the new vcenter Server. After registering the new vcenter Server, unregister the old vcenter Server. Express Protect If you take a backup on HP StoreOnce with failed fibre ports, then the backup might fail displaying the error message 'NoneType' object is not iterable. Workaround: If the fibre ports have failed, you need to rectify the port failure. 142 Troubleshooting

143 However, if you need the backup to proceed prior to the fix, then remove the failing ports from the fibre zone. The error message Failed to attach the VV is displayed when user performs an Express Protect to HP StoreOnce on iscsi or a VM direct path FC appliance. Workaround: Make sure that the HP 3PAR StoreServ host connectivity is appropriate. If user deletes one or more virtual volumes from HP 3PAR StoreServ storage and does not do a refresh, then any request to take incremental Express Protect or full back up on snapshots that were taken earlier, fails. This happens because, one or more snapshots were deleted from HP 3PAR StoreServ storage along with their respective base volume. The Task tracker displays a message stating that RMC failed to attach one or more snapshots. Workaround: HP recommends that you perform a Refresh from the vsphere Web Client. Element Recovery Technology Express Protect object Mount/Unmount tasks fail and the An Unknown Error occurred error message is displayed. Workaround: This might happen because HP StoreOnce is offline. To resolve this, ensure that HP StoreOnce Server is online. Express Protect object Mount/Unmount tasks fail and the Unable to detect Express Protect Object LUNS error message is displayed. Workaround: You must add in RMC host as a dynamic discovery target to the ESXi host adapter to discover the Express Protect object iscsi targets. 1. Click on the ESXi host. 2. Click Manage Storage Storage Adapters. 3. Select the iscsi adapter and then click Dynamic Discovery Add to add RMC IP as the iscsi server. Mount task fails displaying the error Unable to detect all Express Protect Object volumes. Please make sure RMC IP is added as a dynamic discovery target on the ESXi host iscsi Initiator.. You might also see that some of the target devices in iscsi Software Adapter Adapter Details displays Inactive or Error under the Operational State column. NOTE: If the vcenter Server (RMC-V plug-in) locale is Japanese language, then the My Tasks might display Fault task error. Workaround: 1. Make sure that the you configure the RMC appliance as a dynamic discovery target with the ESXi host iscsi software adapter. 2. Select the iscsi software adapter on which the ERT is configured and perform a Rescan HBA operation. 3. Retry the mount task. After mounting the Express Protect object, the status of the mounted object in the Status column of the Manage tab displays Not Accessible. Workaround: HP StoreOnce might be powered-off while the Express Protect object is still mounted. 1. HP StoreOnce is online. 2. Unmount the Express Protect object. 3. Mount the Express Protect object again. 143

144 The Mount/Unmount task fails displaying Express Protect Object attachstatus is invalid to continue current operation error message. 144 Troubleshooting Workaround: There might be a delay in updating the Express Protect object state depending on the backup environment you are using. Retry the Mount/Unmount task after some time. The unmount task fails with datastore deletion error The object has been already been deleted or has not been completely created. Workaround: Datastore becomes inactive if HP StoreOnce is powered-off. Web Client might still list the datastore as active, until the datastore status is refreshed. This might result in datastore deletion error during unmounts operation. To resolve this, retry the unmout task. The unmount task fails with datastore deletion error indicating that a file is in use from the datastore. Workaround: A VMDK from the Express Protect datastore might be attached to an existing VM. Remove the hard disk from the VM (under VM settings) and retry the unmount task. Mount/Unmount task fails with error Express Protect Object is in use. RMC Appliance might have rebooted leaving the data sessions to the catalyst objects on the StoreOnce open. This will result failure in any further operations on the Express Protect Object (as previous data session is still open and the catalyst objects are locked). Reboot StoreOnce server to close all data sessions or wait for 2 to 4 hours for the data session to timeout on the particular Express Protect Object. The Manage tab and does not display the Virtual Disks table and Copy/Attach/Detach button for VMDK. Workaround: ERT tasks can be performed only for Express Protect of the Recovery Sets created after installing or upgrading to RMC-V v For Express Protect objects that were created in previous versions, you can perform only mount, unmount, and additional vcenter operations on the mounted Express Protect objects. However copy, attach, and detach tasks cannot be performed. Other functionalities While creating a application consistent snapshots, VMware might fail the operation and display 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. For information on resolving this issue, see VMware KB article , , or other related articles. User is unable to delete a VVOL Recovery Set. The error message Failed to delete array snapshot is displayed. Workaround: Click All HP StoreOnce Recovery Manager Central Actions Update Recovery Manager Cache to do a refresh and retry the task. If you have one or more virtual volumes greater than 8 TB in a Recovery Set, and if you perform incremental backup, the following error message is displayed: Operation cannot be performed because 'Snapshot snapshot_name is greater than size limit of 8TB for incremental backup. Workaround: HP recommends that you upgrade the HP 3PAR StoreServ OS version to MU3 or later or take a full backup of the Recovery Sets that have virtual volumes greater than 8 TB.

145 When the user tries to perform any RMC-V related task, the following error message is displayed: Error connecting via ssh: Error reading SSH protocol banner. Workaround: Any delay in receiving response from the HP 3PAR StoreServ management command might cause this error. You need to check and verify the network responses between the RMC Appliance and HP 3PAR StoreServ Storage system. How can users generate a support ticket for troubleshooting issues? Does user need any other logs other than support ticket from customer? Workaround: To generate a support ticket: 1. Enter the IP address of appliance (https ://<appliance IP> 2. Enter user name and password and log in to RMC GUI. 3. If you are logging into the RMC appliance for the first time, you are prompted to change the RMC appliance password. 4. Click HP StoreOnce Recovery Manager Central and select Support ticket from the Action menu. 5. Click Yes, to generate the ticket. Wait till the ticket is generated. If you do not see the Ticket ID, click Refresh. 6. Click the Up arrow key to save the ticket in your system. You must also generate the logs pertaining to HP OneView for VMware vcenter and Web Client. To generate the logs perform the following: 145

146 1. Launch the Support Tool. To launch the Support Tool for Windows 2008: Click Start All Programs HP OneView for VMware vcenter, and then click Support Tool. To launch the Support Tool for Windows 2012 or 2012 R2: Click Start Apps. The HP OneView for VMware vcenter Support Tool appears. 2. Click Zip Logs to save the data logs related to HP OneView for VMware vcenter and vsphere Web Client to a user specified folder. What are the log files required for troubleshooting RMC-V issues? For troubleshooting RMC-V issues, the following log files are required: rmv-api.log rmv-app.log For troubleshooting RMC logs, see HP StoreOnce Recovery Manager Central User Guide. Log file name rmv-api.log rmv-app.log Description This file is used to look into the call submission log. You can verify the job type (synchronous / asynchronous) and job submission status. This also helps you to understand the json request URI that has been submitted to RMC appliance. Support engineer can extract the support ticket and view the log file to understand the call flow. It will show you the response and subsequent success or failure of any RMC job request call from vcenter. 146 Troubleshooting The required log files can be downloaded from the RMC GUI. For more information on downloading the log files, see the HP StoreOnce Recovery Manager Central User Guide. User is not allowed to take simultaneous backup of a VM or datastore if the virtual volume is created in multiple HP 3PAR virtual domains. Workaround: If user has a single RMC appliance running, then while creating a backup, RMC creates a host either with or without a domain name. The domain name is picked up based

147 on the existence of a virtual volume in any HP 3PAR Virtual domain. If the user has ESXi in multiple 3PAR virtual domain, then the user must select more than one RMC appliance for backup to HP StoreOnce operation. Scheduled jobs are not running in the system, if they are triggered in a time zone different from the RMC appliance time zone. Workaround: Before deploying the RMC appliance using HP OneView for VMware vcenter or using vsphere Client, make sure that the ESXi host time zone is appropriately set and synced. The RMC appliance, when installed through HP OneView for VMware vcenter or using vsphere Client, takes the time zone set in your ESXi host. You can verify the current time zone: RMC-V Schedule job GUI. Log in to the RMC GUI and click Settings option. RMC-V is unable to take snapshots or backups after adding a new datastore or a new VM in the vcenter Server. Workaround: If you created a new datastore with VMs and perform a Virtual machine or datastore level snapshot, then RMV GUI prompts user to perform a cache refresh operation. When you perform Update Recovery Manager Cache, a system-level cache refresh is done for the registered HP 3PAR StoreServ Storage systems and vcenter Server. The expected time to complete the cache refresh depends on the vcenter Server and HP 3PAR StoreServ Storage environments. If user reboots the RMC appliance while a backup job is in progress, the jobs that are in running state does not move to the failed state. Workaround: HP recommends that the RMC appliance must not be rebooted abruptly. Be sure that the scheduled jobs that are running are completed before you reboot the RMC Appliance. However, the state of the backup will be in error state and is displayed under the Recovery Sets tab. User will not be able to restore from such a backup. After deleting HP StoreOnce or HP 3PAR StoreServ Storage from Storage Administrator Portal, the deleted HP StoreOnce or HP 3PAR StoreServ Storage continues to appear in the RMC GUI Dashboard. Workaround: If user has created any snapshot or backup to HP StoreOnce, or created any RMC-V policies, then a recovery set is created for the datastore or Virtual Machine. This will not allow HP StoreOnce or HP 3PAR StoreServ Storage to be removed from the RMC GUI Dashboard. However, if the user has not made any changes related to recovery set, snapshot, backup time stamp, or policy for the associated HP StoreOnce or HP 3PAR StoreServ Storage, then user can remove the HP StoreOnce or HP 3PAR StoreServ Storage from RMC GUI Dashboard. 147

148 To remove an HP StoreOnce or HP 3PAR StoreServ Storage system, you must remove the associated objects from RMC GUI. HP StoreOnce and HP 3PAR StoreServ Storage system can then be permanently removed from the RMC GUI. If user enters an incorrect store client password, system allows the user to create backup to HP StoreOnce. Workaround: If the Client Access Permission check box is not selected, then HP StoreOnce does not validate the catalyst access credentials to perform the backup and restore tasks. After user adds storage system and storage pools to the RMC appliance, the create snapshot task displays the Driver uninitialized error message. Workaround: While creating or updating the storage system, make sure that the credentials can be used for accessing HP 3PAR StoreServ Storage system via SSH and WSAPI. Otherwise, any operation on that particular storage system will fail and display the error message Driver uninitialized. Unable to restore the RMC appliance deployment wizard from the work in progress window. System displays Could not restore: Deploy HP Recovery Manager the error message. Workaround: If the session times out, then the wizard cannot be restored from the work in progress window. System displays Object not found error while performing any task in vsphere Web Client. Workaround: Perform a cache refresh in HP OneView for VMware vcenter after you add any new object in vcenter. If Object not found error message is displayed for an existing or newly added object (for example, VM, datastore, or virtual volume), click Host Manage HP Management and click the refresh icon. NOTE: After clicking the Refresh icon once, allow the refresh to complete. Clicking the Refresh icon multiple times increases the time required to complete the refresh task. 148 Troubleshooting

149 If new volumes are added to a Recovery Set and then user takes a new snapshot, incremental backup of the new snapshot fails. This happens because the parent snapshot reference of the newly added volume(s) is not available. Workaround: HP recommends that you must initiate a full backup after you add or delete one or more volume(s) from the Recovery Set. While creating snapshots, RMC-V displays the following error message: Could not fetch license for storage system. Workaround: Make sure that the array connectivity to your RMC appliance is available. When you perform restore on a multi-node HP StoreOnce, the restore fails and displays an error message. Workaround: If you perform restore in a multi-node configuration and if the associated node fails, then the restore fails. To restore data, you must manually trigger the restore task and it will take the path of the secondary node and complete the restore task successfully. Initially, RMC Appliance is registered with a vcenter (for example, VC1). The user registers this RMC Appliance with another vcenter (for example, VC2). After logging in to the vsphere Web Client for VC1, user is unable to perform any operation from the vsphere Web Client. Workaround: RMC Appliance is not registered with VC1 since this RMC Appliance is now registered with VC2. 1. Log in to the Web Client of VC2 and unregister the RMC instance through HP One View for VMware vcenter. 2. Log in to the Web Client of VC1 and register the RMC instance through HP One View for VMware vcenter. You can now perform tasks from the vsphere Web Client of VC1. During restore, if the RMC Appliance is restarted, then the restore target (snapshot/base volume) is not automatically unexported from the RMC Appliance. Workaround: The impacted snapshot/base volume must be manually unexported. User has active schedules running on a particular RMC Appliance (for example, say RMC1). When the user tries to modify the policy to another RMC Appliance (for example, RMC2) without removing the existing schedules, the vsphere Web Client displays the following error message: An internal error has occurred Error #

150 Workaround: To resolve this error: 1. Click No. 2. Log out from the vsphere Web Client and log in again. 3. Move the policy back to RMC1 for the particular datastore or VM. 4. Delete the RMC1 schedules. 5. Set the policy of the datastore or VM to RMC2. If users have multiple RMC instances configured in their setup, and if even one RMC instance becomes inaccessible, then while accessing the Default Snapshot Policy Settings page, the vsphere Web Client displays an error message. Workaround: Identify the RMC instance that is not accessible and rectify the issue. If you are unable to rectify the issue, unregister the RMC instance. For information on unregistering the RMC instance, see Unregistering RMC Appliance (page 23). If the system is idle for some time and if you modify the default snapshot policy of a VM, datastore, or Remote Recovery Set Configuration, the following error message appears: Session is not initialized. Please try to login again. Workaround: Log off and log in again to the vsphere Web Client and wait until the web initialization is complete. The mount action fails for the snapshots and displays the HP 3PAR mount operation failed : " Invalid input received: 'rwsnapshot' cannot be specified if snapshot is not read only." error message. This might happen when you perform a mount action on a snapshot that was created during restore to snapshot operation. Workaround: To perform mount and Copy/Attach VMDK actions, perform the procedure listed in the Mounting snapshots and performing Copy/Attach VMDK for snapshots created during restore to snapshot section. Remote Recovery Sets Configurations After deploying the local RMC Appliance user might get the following error message: 150 Troubleshooting

151 Register atleast one RMC using StoreOnce RMC Credential option in Administration. Workaround: Log off and log in again to the Web Client. The existing and newly created Remote Copy groups are not getting listed Remote Recovery Configurations. Workaround: Be sure that: The ESXi Server is in connected state. Ensure that the virtual volume is presented and discovered by the ESXi Server managed by the vcenter. Web Client initialization might take some time to complete. After the Web Client is initialized, do a vcenter refresh. Listing the Remote Copy groups is taking a long time in the Remote Recovery Configuration page. Workaround: This might happen because of any of the following reasons: One or more HP 3PAR StoreServ Storage systems are either down or not reachable The maximum permissible number of connection with the Storage systems has exceeded The WSAPI service is down Also, ensure that all Storage systems are reachable and connections are available and the WSAPI service is running. The newly created Recovery Sets are not appearing in the Recovery Sets on Source StoreServ and Recovery Sets on Target StoreServ tabs. Workaround: Do a vcenter Refresh. After failover, the existing scheduled jobs fails and in the Tasks pane, snapshot creation failed message is displayed. Workaround: Delete the existing schedule and create a new schedule for the new primary system. When user double-clicks a Recovery Set, the Manage window might not appear for the Recovery Set. Sometimes, the same window is loaded again and the following error message is displayed: You have no privileges to view this object or it does not exist. Workaround: Refresh the Web Client and retry the action. If a Synchronous Remote Copy group has multiple volumes and if the first eight characters are same in the names of any two virtual volumes, then snapshot creation fails and displays the following error message: 151

HP OneView for VMware vcenter User Guide

HP OneView for VMware vcenter User Guide HP OneView for VMware vcenter User Guide Abstract This document contains detailed instructions for configuring and using HP OneView for VMware vcenter (formerly HP Insight Control for VMware vcenter Server).

More information

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

HP 3PAR Management Plug-in and Recovery Manager Software for VMware vsphere Client User Guide HP 3PAR Management Plug-in and Recovery Manager 2.6.1 Software for VMware vsphere Client User Guide Abstract This guide is intended for VMware and database administrators responsible for backing up databases

More information

HP OneView for VMware vcenter User Guide

HP OneView for VMware vcenter User Guide HP OneView for VMware vcenter User Guide Abstract This document contains detailed instructions for configuring and using HP OneView for VMware vcenter (formerly HP Insight Control for VMware vcenter Server).

More information

Data Protection Guide

Data Protection Guide SnapCenter Software 4.0 Data Protection Guide For VMs and Datastores using the SnapCenter Plug-in for VMware vsphere March 2018 215-12931_C0 doccomments@netapp.com Table of Contents 3 Contents Deciding

More information

HPE Recovery Manager Central User Guide

HPE Recovery Manager Central User Guide HPE Recovery Manager Central 4.0.0 User Guide Abstract This guide is intended for administrators who are responsible for primary storage data protection activities using HPE Recovery Manager Central 4.0.0.

More information

HPE OneView for VMware vcenter Release Notes (8.2 and 8.2.1)

HPE OneView for VMware vcenter Release Notes (8.2 and 8.2.1) HPE OneView for VMware vcenter Release Notes (8.2 and 8.2.1) Abstract This document describes changes in HPE OneView for VMware vcenter to help administrators understand the benefits of obtaining the 8.2

More information

HPE OneView for VMware vcenter User Guide

HPE OneView for VMware vcenter User Guide HPE OneView for VMware vcenter User Guide Abstract This document contains detailed instructions for configuring and using HPE OneView for VMware vcenter. It is intended for system administrators who are

More information

Data Protection Guide

Data Protection Guide SnapCenter Software 4.1 Data Protection Guide For VMs and Datastores using the SnapCenter Plug-in for VMware vsphere September 2018 215-13399_B0 doccomments@netapp.com Table of Contents 3 Contents Deciding

More information

HP Insight Control for VMware vcenter Server Release Notes 7.2.1

HP Insight Control for VMware vcenter Server Release Notes 7.2.1 HP Insight Control for VMware vcenter Server Release Notes 7.2.1 HP Part Number: 678314-006a Published: June 2013 Edition: 2 Copyright 2013 Hewlett-Packard Development Company, L.P. Acknowledgements Microsoft

More information

HP 3PAR Recovery Manager 2.0 Software for Microsoft Hyper-V

HP 3PAR Recovery Manager 2.0 Software for Microsoft Hyper-V HP 3PAR Recovery Manager 2.0 Software for Microsoft Hyper-V User Guide Abstract This document provides information about using HP 3PAR Recovery Manager for Microsoft Hyper-V for experienced Microsoft Windows

More information

HP LeftHand SAN Solutions

HP LeftHand SAN Solutions HP LeftHand SAN Solutions Support Document Installation Manuals VSA 8.0 Quick Start - Demo Version Legal Notices Warranty The only warranties for HP products and services are set forth in the express warranty

More information

Dell Storage Compellent Integration Tools for VMware

Dell Storage Compellent Integration Tools for VMware Dell Storage Compellent Integration Tools for VMware Administrator s Guide Version 3.1 Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your

More information

Installing VMware vsphere 5.1 Components

Installing VMware vsphere 5.1 Components Installing VMware vsphere 5.1 Components Module 14 You Are Here Course Introduction Introduction to Virtualization Creating Virtual Machines VMware vcenter Server Configuring and Managing Virtual Networks

More information

Dell Storage Compellent Integration Tools for VMware

Dell Storage Compellent Integration Tools for VMware Dell Storage Compellent Integration Tools for VMware Version 4.0 Administrator s Guide Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your

More information

HPE OneView for Microsoft System Center Release Notes (v 8.2 and 8.2.1)

HPE OneView for Microsoft System Center Release Notes (v 8.2 and 8.2.1) Center Release Notes (v 8.2 and 8.2.1) Part Number: 832154-004a Published: April 2017 Edition: 2 Contents Center Release Notes (v 8.2 and 8.2.1)... 4 Description...4 Update recommendation... 4 Supersedes...

More information

SonicWall Secure Mobile Access SMA 500v Virtual Appliance 8.6. Getting Started Guide

SonicWall Secure Mobile Access SMA 500v Virtual Appliance 8.6. Getting Started Guide SonicWall Secure Mobile Access SMA 500v Virtual Appliance 8.6 Getting Started Guide Copyright 2017 SonicWall Inc. All rights reserved. SonicWall is a trademark or registered trademark of SonicWall Inc.

More information

vsphere Replication for Disaster Recovery to Cloud

vsphere Replication for Disaster Recovery to Cloud vsphere Replication for Disaster Recovery to Cloud vsphere Replication 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide

HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide AT459-96002 Part number: AT459-96002 First edition: April 2009 Legal and notice information Copyright 2009 Hewlett-Packard

More information

Dell Storage Integration Tools for VMware

Dell Storage Integration Tools for VMware Dell Storage Integration Tools for VMware Version 4.1 Administrator s Guide Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION:

More information

NexentaStor VVOL

NexentaStor VVOL NexentaStor 5.1.1 VVOL Admin Guide Date: January, 2018 Software Version: NexentaStor 5.1.1 VVOL Part Number: 3000-VVOL-5.1.1-000065-A Table of Contents Preface... 3 Intended Audience 3 References 3 Document

More information

vsphere Replication for Disaster Recovery to Cloud vsphere Replication 6.5

vsphere Replication for Disaster Recovery to Cloud vsphere Replication 6.5 vsphere Replication for Disaster Recovery to Cloud vsphere Replication 6.5 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments

More information

SnapCenter Software 4.0 Concepts Guide

SnapCenter Software 4.0 Concepts Guide SnapCenter Software 4.0 Concepts Guide May 2018 215-12925_D0 doccomments@netapp.com Table of Contents 3 Contents Deciding whether to use the Concepts Guide... 7 SnapCenter overview... 8 SnapCenter architecture...

More information

HPE StoreVirtual Storage Application Aware Snapshot Manager Deployment Guide

HPE StoreVirtual Storage Application Aware Snapshot Manager Deployment Guide HPE StoreVirtual Storage Application Aware Snapshot Manager Deployment Guide Abstract This guide contains instructions for installing and deploying the StoreVirtual Application Aware Snapshot Manager to

More information

Installing and Configuring vcloud Connector

Installing and Configuring vcloud Connector Installing and Configuring vcloud Connector vcloud Connector 2.6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

More information

REVISED 1 AUGUST REVIEWER'S GUIDE FOR VMWARE APP VOLUMES VMware App Volumes and later

REVISED 1 AUGUST REVIEWER'S GUIDE FOR VMWARE APP VOLUMES VMware App Volumes and later REVISED 1 AUGUST 2018 REVIEWER'S GUIDE FOR VMWARE APP VOLUMES VMware App Volumes 2.13.1 and later Table of Contents Introduction Audience What You Will Learn Navigating This Document for App Volumes Use

More information

Configuring and Managing Virtual Storage

Configuring and Managing Virtual Storage Configuring and Managing Virtual Storage Module 6 You Are Here Course Introduction Introduction to Virtualization Creating Virtual Machines VMware vcenter Server Configuring and Managing Virtual Networks

More information

on VMware Deployment Guide November 2018 Deployment Guide for Unitrends Free on VMware Release 10.3 Version Provide feedback

on VMware Deployment Guide November 2018 Deployment Guide for Unitrends Free on VMware Release 10.3 Version Provide feedback Deployment Guide November 2018 Release 10.3 Version 1.11152018 2 Copyright Copyright 2018 Unitrends Incorporated. All rights reserved. Content in this publication is copyright material and may not be copied

More information

DSI Optimized Backup & Deduplication for VTL Installation & User Guide

DSI Optimized Backup & Deduplication for VTL Installation & User Guide DSI Optimized Backup & Deduplication for VTL Installation & User Guide Restore Virtualized Appliance Version 4 Dynamic Solutions International, LLC 373 Inverness Parkway Suite 110 Englewood, CO 80112 Phone:

More information

vcenter Server Installation and Setup Modified on 11 MAY 2018 VMware vsphere 6.7 vcenter Server 6.7

vcenter Server Installation and Setup Modified on 11 MAY 2018 VMware vsphere 6.7 vcenter Server 6.7 vcenter Server Installation and Setup Modified on 11 MAY 2018 VMware vsphere 6.7 vcenter Server 6.7 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/

More information

HPE StoreVirtual 3200 Application Aware Snapshot Manager User Guide

HPE StoreVirtual 3200 Application Aware Snapshot Manager User Guide HPE StoreVirtual 3200 Application Aware Snapshot Manager User Guide Abstract The StoreVirtual Application Aware Snapshot Manager simplifies the tasks of managing credentials and creating snapshots for

More information

Deployment Guide for Unitrends Backup on VMware

Deployment Guide for Unitrends Backup on VMware Deployment Guide for Unitrends Deployment Guide July 2018 Deployment Guide for Unitrends Backup on VMware Release 10.2 Version 1.07102018 2 Deployment Guide for Unitrends Copyright Copyright 2018 Unitrends

More information

REVISED 1 AUGUST QUICK-START TUTORIAL FOR VMWARE APP VOLUMES VMware App Volumes and later

REVISED 1 AUGUST QUICK-START TUTORIAL FOR VMWARE APP VOLUMES VMware App Volumes and later REVISED 1 AUGUST 2018 QUICK-START TUTORIAL FOR VMWARE APP VOLUMES VMware App Volumes 2.13.1 and later Table of Contents Introduction Audience What You Will Learn Navigating This Document for App Volumes

More information

OnCommand Unified Manager Installation and Setup Guide for Use with Core Package 5.2 and Host Package 1.3

OnCommand Unified Manager Installation and Setup Guide for Use with Core Package 5.2 and Host Package 1.3 IBM System Storage N series OnCommand Unified Manager Installation and Setup Guide for Use with Core Package 5.2 and Host Package 1.3 GA32-1020-03 Table of Contents 3 Contents Preface... 10 Supported

More information

HPE OneView SCVMM Integration Kit (v 3.0) User Guide

HPE OneView SCVMM Integration Kit (v 3.0) User Guide HPE OneView SCVMM Integration Kit (v 3.0) User Guide Abstract This guide is intended for system administrators who use the HPE OneView SCVMM Integration Kit (v 3.0) and other Hewlett Packard Enterprise

More information

HP StoreVirtual Storage Multi-Site Configuration Guide

HP StoreVirtual Storage Multi-Site Configuration Guide HP StoreVirtual Storage Multi-Site Configuration Guide Abstract This guide contains detailed instructions for designing and implementing the Multi-Site SAN features of the LeftHand OS. The Multi-Site SAN

More information

Storage Manager 2018 R1. Installation Guide

Storage Manager 2018 R1. Installation Guide Storage Manager 2018 R1 Installation Guide Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either

More information

vsphere Replication for Disaster Recovery to Cloud vsphere Replication 8.1

vsphere Replication for Disaster Recovery to Cloud vsphere Replication 8.1 vsphere Replication for Disaster Recovery to Cloud vsphere Replication 8.1 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments

More information

Installing and Configuring vcenter Support Assistant

Installing and Configuring vcenter Support Assistant Installing and Configuring vcenter Support Assistant vcenter Support Assistant 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

PHD Virtual Backup Exporter. version 6.5 Users Guide. Document Release Date: August 26,

PHD Virtual Backup Exporter. version 6.5 Users Guide. Document Release Date: August 26, PHD Virtual Backup Exporter version 6.5 Users Guide Document Release Date: August 26, 2013 www.phdvirtual.com i PHD Virtual Backup Exporter - Users Guide Legal Notices PHD Virtual Backup Exporter Users

More information

IBM Spectrum Protect Plus Version Installation and User's Guide IBM

IBM Spectrum Protect Plus Version Installation and User's Guide IBM IBM Spectrum Protect Plus Version 10.1.1 Installation and User's Guide IBM Note: Before you use this information and the product it supports, read the information in Notices on page 119. Third edition

More information

USER GUIDE. HYCU Data Protection for Nutanix

USER GUIDE. HYCU Data Protection for Nutanix USER GUIDE HYCU Data Protection for Nutanix Version: 3.1.3 Product release date: August 2018 Document release date: August 2018 Legal notices Copyright notice 2017 2018 HYCU. All rights reserved. This

More information

Data Protection Guide

Data Protection Guide SnapCenter Software 4.0 Data Protection Guide For Custom Plug-ins March 2018 215-12932_C0 doccomments@netapp.com Table of Contents 3 Contents Deciding on whether to read the SnapCenter Data Protection

More information

Dell EMC Avamar. vsphere Web Client Administration Guide. Version REV 01

Dell EMC Avamar. vsphere Web Client Administration Guide. Version REV 01 Dell EMC Avamar Version 18.2 vsphere Web Client Administration Guide 302-005-122 REV 01 Copyright 2001-2018 Dell Inc. or its subsidiaries. All rights reserved. Published December 2018 Dell believes the

More information

vrealize Suite Lifecycle Manager 1.0 Installation and Management vrealize Suite 2017

vrealize Suite Lifecycle Manager 1.0 Installation and Management vrealize Suite 2017 vrealize Suite Lifecycle Manager 1.0 Installation and Management vrealize Suite 2017 vrealize Suite Lifecycle Manager 1.0 Installation and Management You can find the most up-to-date technical documentation

More information

Basic Configuration Installation Guide

Basic Configuration Installation Guide EMC RecoverPoint for VMs 5.0 Basic Configuration Installation Guide P/N 302-003-534 REV 01 December 7, 2016 This document contains information on these topics: Revision History... 2 Overview... 3 Reference

More information

OpenManage Integration for VMware vcenter Quick Install Guide for vsphere Client Version 3.0

OpenManage Integration for VMware vcenter Quick Install Guide for vsphere Client Version 3.0 OpenManage Integration for VMware vcenter Quick Install Guide for vsphere Client Version 3.0 Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of

More information

Data Protection Guide

Data Protection Guide SnapCenter Software 4.0 Data Protection Guide For Microsoft Exchange Server March 2018 215-12936_C0 doccomments@netapp.com Table of Contents 3 Contents Deciding whether to read the SnapCenter Data Protection

More information

vcenter Server Installation and Setup Update 1 Modified on 30 OCT 2018 VMware vsphere 6.7 vcenter Server 6.7

vcenter Server Installation and Setup Update 1 Modified on 30 OCT 2018 VMware vsphere 6.7 vcenter Server 6.7 vcenter Server Installation and Setup Update 1 Modified on 30 OCT 2018 VMware vsphere 6.7 vcenter Server 6.7 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/

More information

vsphere Replication for Disaster Recovery to Cloud

vsphere Replication for Disaster Recovery to Cloud vsphere Replication for Disaster Recovery to Cloud vsphere Replication 5.6 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

VMware vsphere Data Protection Evaluation Guide REVISED APRIL 2015

VMware vsphere Data Protection Evaluation Guide REVISED APRIL 2015 VMware vsphere Data Protection REVISED APRIL 2015 Table of Contents Introduction.... 3 Features and Benefits of vsphere Data Protection... 3 Requirements.... 4 Evaluation Workflow... 5 Overview.... 5 Evaluation

More information

HPE VMware ESXi and vsphere 5.x, 6.x and Updates Getting Started Guide

HPE VMware ESXi and vsphere 5.x, 6.x and Updates Getting Started Guide HPE VMware ESXi and vsphere 5.x, 6.x and Updates Getting Started Guide Abstract This guide is intended to provide setup information for HPE VMware ESXi and vsphere. Part Number: 818330-003 Published: April

More information

USER GUIDE. Backup and Recovery for Nutanix

USER GUIDE. Backup and Recovery for Nutanix USER GUIDE Backup and Recovery for Nutanix Version: 2.0.1 Product release date: February 2018 Document release date: February 2018 Legal notices Copyright notice 2017 2018 Comtrade Software. All rights

More information

Virtual Storage Console, VASA Provider, and Storage Replication Adapter for VMware vsphere

Virtual Storage Console, VASA Provider, and Storage Replication Adapter for VMware vsphere Virtual Storage Console, VASA Provider, and Storage Replication Adapter for VMware vsphere Workflow Guide for 7.2 release July 2018 215-13170_B0 doccomments@netapp.com Table of Contents 3 Contents Deciding

More information

Setting Up the DR Series System on Veeam

Setting Up the DR Series System on Veeam Setting Up the DR Series System on Veeam Quest Engineering June 2017 A Quest Technical White Paper Revisions Date January 2014 May 2014 July 2014 April 2015 June 2015 November 2015 April 2016 Description

More information

Configuring the SMA 500v Virtual Appliance

Configuring the SMA 500v Virtual Appliance Using the SMA 500v Virtual Appliance Configuring the SMA 500v Virtual Appliance Registering Your Appliance Using the 30-day Trial Version Upgrading Your Appliance Configuring the SMA 500v Virtual Appliance

More information

Installing and Configuring vcloud Connector

Installing and Configuring vcloud Connector Installing and Configuring vcloud Connector vcloud Connector 2.5.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

More information

VMware vfabric Data Director Installation Guide

VMware vfabric Data Director Installation Guide VMware vfabric Data Director Installation Guide vfabric Data Director 2.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by

More information

Veeam Cloud Connect. Version 8.0. Administrator Guide

Veeam Cloud Connect. Version 8.0. Administrator Guide Veeam Cloud Connect Version 8.0 Administrator Guide June, 2015 2015 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication may be reproduced,

More information

OpenManage Integration for VMware vcenter Quick Install Guide for vsphere Client, Version 2.3.1

OpenManage Integration for VMware vcenter Quick Install Guide for vsphere Client, Version 2.3.1 OpenManage Integration for VMware vcenter Quick Install Guide for vsphere Client, Version 2.3.1 Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use

More information

How to Deploy vcenter on the HX Data Platform

How to Deploy vcenter on the HX Data Platform First Published: 2016-07-11 Last Modified: 2019-01-08 vcenter on HyperFlex Cisco HX Data Platform deployment, including installation and cluster configuration and management, requires a vcenter server

More information

HP VMware ESXi and vsphere 5.x and Updates Getting Started Guide

HP VMware ESXi and vsphere 5.x and Updates Getting Started Guide HP VMware ESXi and vsphere 5.x and Updates Getting Started Guide Abstract This guide is intended to provide setup information for HP VMware ESXi and vsphere. HP Part Number: 616896-409 Published: September

More information

Hands-on Lab Manual. Introduction. Dell Storage Hands-on Lab Instructions. Estimated Completion Time: 30 minutes. Audience. What we will be doing

Hands-on Lab Manual. Introduction. Dell Storage Hands-on Lab Instructions. Estimated Completion Time: 30 minutes. Audience. What we will be doing Dell Storage Hands-on Lab Instructions Dell SC Series CITV Integration with VMware VASA Estimated Completion Time: 30 minutes Introduction Audience The audience for this document is technical professionals

More information

Veritas NetBackup Plug-in for VMware vsphere Web Client Guide. Release 8.1.1

Veritas NetBackup Plug-in for VMware vsphere Web Client Guide. Release 8.1.1 Veritas NetBackup Plug-in for VMware vsphere Web Client Guide Release 8.1.1 Veritas NetBackup Plug-in for VMware vsphere Web Client Guide Last updated: 2018-02-16 Document version:netbackup 8.1.1 Legal

More information

ilo Amplifier Pack User Guide

ilo Amplifier Pack User Guide ilo Amplifier Pack User Guide Abstract This guide provides information about installing, configuring, and operating ilo Amplifier Pack. Part Number: P04465-001 Published: December 2017 Edition: 4 Copyright

More information

ProLiant Cluster HA/F500 for Enterprise Virtual Array Introduction Software and Hardware Pre-Checks Gathering Information...

ProLiant Cluster HA/F500 for Enterprise Virtual Array Introduction Software and Hardware Pre-Checks Gathering Information... Installation Checklist HP ProLiant Cluster F500 for Enterprise Virtual Array 4000/6000/8000 using Microsoft Windows Server 2003, Enterprise Edition Stretch Cluster May 2005 Table of Contents ProLiant Cluster

More information

USER GUIDE. HYCU Data Protection for Nutanix

USER GUIDE. HYCU Data Protection for Nutanix USER GUIDE HYCU Data Protection for Nutanix Version: 3.0.0 Product release date: April 2018 Document release date: April 2018 Legal notices Copyright notice 2017 2018 HYCU. All rights reserved. This document

More information

SRA Virtual Appliance Getting Started Guide

SRA Virtual Appliance Getting Started Guide SRA Virtual Appliance Getting Started Guide 1 Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your system. CAUTION: A CAUTION indicates potential

More information

HPE OneView SCVMM Integration Kit (v 3.2) User Guide

HPE OneView SCVMM Integration Kit (v 3.2) User Guide HPE OneView SCVMM Integration Kit (v 3.2) User Guide Abstract This guide is intended for system administrators who use the HPE OneView SCVMM Integration Kit (v 3.2) and other Hewlett Packard Enterprise

More information

EMC VSI for VMware vsphere Web Client

EMC VSI for VMware vsphere Web Client EMC VSI for VMware vsphere Web Client Version 6.9.2 Product Guide 302-000-051 REV 13 Copyright 2013-2016 EMC Corporation. All rights reserved. Published in the USA. Published June 2016 EMC believes the

More information

Dell Storage Manager 2016 R3 Installation Guide

Dell Storage Manager 2016 R3 Installation Guide Dell Storage Manager 2016 R3 Installation Guide Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either

More information

VMware Skyline Collector Installation and Configuration Guide. VMware Skyline 1.4

VMware Skyline Collector Installation and Configuration Guide. VMware Skyline 1.4 VMware Skyline Collector Installation and Configuration Guide VMware Skyline 1.4 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have

More information

Oracle VM. Getting Started Guide for Release 3.2

Oracle VM. Getting Started Guide for Release 3.2 Oracle VM Getting Started Guide for Release 3.2 E35331-04 March 2014 Oracle VM: Getting Started Guide for Release 3.2 Copyright 2011, 2014, Oracle and/or its affiliates. All rights reserved. Oracle and

More information

Virtual Storage Console, VASA Provider, and Storage Replication Adapter for VMware vsphere

Virtual Storage Console, VASA Provider, and Storage Replication Adapter for VMware vsphere Virtual Storage Console, VASA Provider, and Storage Replication Adapter for VMware vsphere Administration Guide for 7.2 release June 2018 215-13169_A0 doccomments@netapp.com Table of Contents 3 Contents

More information

Virtual Storage Console 6.1 for VMware vsphere

Virtual Storage Console 6.1 for VMware vsphere Virtual Storage Console 6.1 for VMware vsphere Installation and Administration Guide NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 U.S. Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support

More information

vrealize Infrastructure Navigator Installation and Configuration Guide

vrealize Infrastructure Navigator Installation and Configuration Guide vrealize Infrastructure Navigator Installation and Configuration Guide vrealize Infrastructure Navigator 5.8.5 This document supports the version of each product listed and supports all subsequent versions

More information

Archiware Pure User Manual

Archiware Pure User Manual Archiware Pure User Manual Content 1 Preface... 3 1.1 About This Manual... 3 1.2 Who Should Read This Document?...3 1.3 Software Description... 3 1.4 Software Licensing... 3 1.5 Registration... 3 1.6 Technical

More information

Data Protection Guide

Data Protection Guide SnapCenter Software 4.0 Data Protection Guide For Oracle Databases May 2018 215-12930_D0 doccomments@netapp.com Table of Contents 3 Contents Deciding whether to read the SnapCenter Data Protection Guide

More information

Quest VROOM Quick Setup Guide for Quest Rapid Recovery for Windows and Quest Foglight vapp Installers

Quest VROOM Quick Setup Guide for Quest Rapid Recovery for Windows and Quest Foglight vapp Installers Quest VROOM Quick Setup Guide for Quest Rapid Recovery for Windows and Quest Foglight vapp Installers INTRODUCTION Setup of Quest VROOM requires installation of Rapid Recovery and Foglight for Virtualization

More information

HP StorageWorks. EVA Virtualization Adapter administrator guide

HP StorageWorks. EVA Virtualization Adapter administrator guide HP StorageWorks EVA Virtualization Adapter administrator guide Part number: 5697-0177 Third edition: September 2009 Legal and notice information Copyright 2008-2009 Hewlett-Packard Development Company,

More information

HP StoreVirtual Storage Multi-Site Configuration Guide

HP StoreVirtual Storage Multi-Site Configuration Guide HP StoreVirtual Storage Multi-Site Configuration Guide Abstract This guide contains detailed instructions for designing and implementing the Multi-Site SAN features of the LeftHand OS. The Multi-Site SAN

More information

vrealize Suite Lifecycle Manager 1.1 Installation, Upgrade, and Management vrealize Suite 2017

vrealize Suite Lifecycle Manager 1.1 Installation, Upgrade, and Management vrealize Suite 2017 vrealize Suite Lifecycle Manager 1.1 Installation, Upgrade, and Management vrealize Suite 2017 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/

More information

OpenManage Integration for VMware vcenter Quick Installation Guide for vsphere Web Client Version 3.1

OpenManage Integration for VMware vcenter Quick Installation Guide for vsphere Web Client Version 3.1 OpenManage Integration for VMware vcenter Quick Installation Guide for vsphere Web Client Version 3.1 Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better

More information

Virtual Recovery Assistant user s guide

Virtual Recovery Assistant user s guide Virtual Recovery Assistant user s guide Part number: T2558-96323 Second edition: March 2009 Copyright 2009 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind

More information

HP integrated Citrix XenServer Online Help

HP integrated Citrix XenServer Online Help HP integrated Citrix XenServer Online Help Part Number 486855-002 September 2008 (Second Edition) Copyright 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to

More information

VMware vfabric Data Director Installation Guide

VMware vfabric Data Director Installation Guide VMware vfabric Data Director Installation Guide vfabric Data Director 1.0.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Dell EMC vsan Ready Nodes for VDI

Dell EMC vsan Ready Nodes for VDI Dell EMC vsan Ready Nodes for VDI Integration of VMware Horizon on Dell EMC vsan Ready Nodes April 2018 H17030.1 Deployment Guide Abstract This deployment guide provides instructions for deploying VMware

More information

Hewlett Packard Enterprise. HPE OmniStack for vsphere Upgrade Guide

Hewlett Packard Enterprise. HPE OmniStack for vsphere Upgrade Guide Hewlett Packard Enterprise HPE OmniStack for vsphere Upgrade Guide Part number: P00126-001 Published: September 2017 2017 Hewlett Packard Enterprise Development LP Notices The information contained herein

More information

Setting Up the Dell DR Series System on Veeam

Setting Up the Dell DR Series System on Veeam Setting Up the Dell DR Series System on Veeam Dell Engineering April 2016 A Dell Technical White Paper Revisions Date January 2014 May 2014 July 2014 April 2015 June 2015 November 2015 April 2016 Description

More information

Installation and Cluster Deployment Guide for VMware

Installation and Cluster Deployment Guide for VMware ONTAP Select 9 Installation and Cluster Deployment Guide for VMware Using ONTAP Select Deploy 2.8 June 2018 215-13347_B0 doccomments@netapp.com Updated for ONTAP Select 9.4 Table of Contents 3 Contents

More information

Version 2.3 User Guide

Version 2.3 User Guide V Mware vcloud Usage Meter Version 2.3 User Guide 2012 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. This product is covered

More information

iscsi Configuration for ESXi using VSC Express Guide

iscsi Configuration for ESXi using VSC Express Guide ONTAP 9 iscsi Configuration for ESXi using VSC Express Guide May 2018 215-11181_E0 doccomments@netapp.com Updated for ONTAP 9.4 Table of Contents 3 Contents Deciding whether to use this guide... 4 iscsi

More information

Basic Configuration Installation Guide

Basic Configuration Installation Guide RecoverPoint for VMs 5.1 Basic Configuration Installation Guide P/N 302-003-975 REV 1 July 4, 2017 This document contains information on these topics: Revision History... 2 Overview... 3 Reference architecture...

More information

Archiware Pure Quick Start Guide

Archiware Pure Quick Start Guide Archiware Pure Quick Start Guide Content 1 System Requirements... 3 1.1 Hardware Requirements... 3 1.2 Supported Hypervisors... 3 1.3 Deployment Requirements... 3 2 Deploying the Virtual Appliance... 4

More information

Veritas High Availability 7.3 Solution Guide for VMware - Linux

Veritas High Availability 7.3 Solution Guide for VMware - Linux Veritas High Availability 7.3 Solution Guide for VMware - Linux June 2017 Last updated: 2017-06-01 Legal Notice Copyright 2017 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo

More information

Introduction to Virtualization

Introduction to Virtualization Introduction to Virtualization Module 2 You Are Here Course Introduction Introduction to Virtualization Creating Virtual Machines VMware vcenter Server Configuring and Managing Virtual Networks Configuring

More information

Dell EMC Ready Architectures for VDI

Dell EMC Ready Architectures for VDI Dell EMC Ready Architectures for VDI Designs for VMware Horizon 7 on Dell EMC XC Family September 2018 H17387 Deployment Guide Abstract This deployment guide provides instructions for deploying VMware

More information

HP Insight Remote Support Advanced HP StorageWorks P4000 Storage System

HP Insight Remote Support Advanced HP StorageWorks P4000 Storage System HP Insight Remote Support Advanced HP StorageWorks P4000 Storage System Migration Guide HP Part Number: 5900-1089 Published: August 2010, Edition 1 Copyright 2010 Hewlett-Packard Development Company, L.P.

More information

VMware vcloud Air User's Guide

VMware vcloud Air User's Guide vcloud Air This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document,

More information

Dell Storage vsphere Web Client Plugin. Version 4.0 Administrator s Guide

Dell Storage vsphere Web Client Plugin. Version 4.0 Administrator s Guide Dell Storage vsphere Web Client Plugin Version 4.0 Administrator s Guide Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION:

More information

Administering vrealize Log Insight. 05-SEP-2017 vrealize Log Insight 4.3

Administering vrealize Log Insight. 05-SEP-2017 vrealize Log Insight 4.3 Administering vrealize Log Insight 05-SEP-2017 4.3 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about this documentation,

More information