hpe recovery manager central for vmware user guideh20628. · ... vmware® vcenter server™, and...

HPE Recovery Manager Central3.0.0 for VMware User Guide

AbstractThe guide is intended for VMware vSphere Web Client administrators and database administrators who are responsiblefor backing up databases. This guide provides information on how to install, configure, and use HPE Recovery ManagerCentral for VMware vSphere Web Client with HPE 3PAR StoreServ and HPE Hyper Converged 250 storage systemsand HPE Express Protect.

Part Number: 837749-004a Published: April 2017 Edition: 2

© Copyright 2015, 2017 Hewlett Packard Enterprise Development LP.

The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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.

Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

Microsoft® and Windows® are trademarks of the Microsoft group of companies.

VMware®, VMware® vCenter Server™, and VMware 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.

Revision history

Edition NotesPublication dateEditionDocument part number

Initial publication for version 3.0.0August 20161837749-004

Updated the section on page 164April 20172837749-004a

Contents1 Overview..............................................................................................................8

Features................................................................................................................................................9Recovery Set management.............................................................................................................9Recovery Set data consistency.....................................................................................................10Recovery Set policy.......................................................................................................................10Datastore Recovery Sets...............................................................................................................11Virtual Machine Recovery Sets.....................................................................................................12VM Recovery Sets with additional disks........................................................................................12Recovery Set browser...................................................................................................................13VMFS snapshots...........................................................................................................................14Scheduling options........................................................................................................................14

2 Licensing...........................................................................................................15Overview.............................................................................................................................................15License models supported by RMC-V................................................................................................15Licensing scenarios............................................................................................................................15

3 Installing HPE RMC-V.......................................................................................16Installation workflow............................................................................................................................16Prerequisites.......................................................................................................................................17Connectivity requirements..................................................................................................................18RMC installation options.....................................................................................................................19Using the installation wizard...............................................................................................................20RMC Installation Wizard screens........................................................................................................21

Introduction....................................................................................................................................21License Agreement........................................................................................................................21Deploy HPE Recovery Manager Central.......................................................................................21Install/Upgrade..............................................................................................................................23

Upgrading to RMC-V................................................................................................................23Single RMC-V...........................................................................................................................23RMC-V upgrade.......................................................................................................................24Multi RMC.................................................................................................................................24RMC only..................................................................................................................................24

ESXi Server and Datastore selection............................................................................................25RMC Configuration........................................................................................................................26Network Configuration...................................................................................................................28Network Interface Settings............................................................................................................29Storage System Configuration (optional)......................................................................................31Backup System Configuration (optional).......................................................................................32Summary.......................................................................................................................................33Diagnostics (optional)....................................................................................................................34Install/Upgrade complete summary...............................................................................................35

4 Working with vSphere Web Client.....................................................................37Logging in to the vSphere Web Client................................................................................................37HPE RMC Configuration tabs.............................................................................................................38

RMC Appliances............................................................................................................................39Storage Systems...........................................................................................................................43Backup Systems............................................................................................................................44vCenter Server..............................................................................................................................45

5 Working with Recovery Sets Snapshots............................................................47Prerequisites for working with Recovery Set Snapshots....................................................................48Creating default Recovery Set policy..................................................................................................48

Contents 3

Creating Recovery Sets......................................................................................................................54Viewing Recovery Set information......................................................................................................56

Viewing Virtual Disk details...........................................................................................................58Viewing Recovery Set event logs..................................................................................................58

Mounting Recovery Sets.....................................................................................................................59Unmounting Recovery Sets................................................................................................................60Attaching virtual machine disks..........................................................................................................60Detaching virtual machine disks.........................................................................................................63Restoring Virtual Machines.................................................................................................................63

Restoring VVOL Virtual Machines.................................................................................................63Deleting Recovery Sets......................................................................................................................64Viewing Recovery Sets.......................................................................................................................64Scheduling Recovery Sets..................................................................................................................65Editing schedules................................................................................................................................69Removing schedules..........................................................................................................................69Creating Email Notification Policies....................................................................................................69Updating Recovery Manager Cache...................................................................................................71

Auto cache refresh........................................................................................................................716 Working with Remote Recovery Sets Configurations........................................73

Working with Remote Copy Groups...................................................................................................73Prerequisites to configure Remote Copy Group.................................................................................74Workflow.............................................................................................................................................74RMC Remote Copy Configurations Topologies..................................................................................76Viewing Remote Recovery configurations..........................................................................................80

Viewing Remote Recovery Configuration information details.......................................................80Creating policies.................................................................................................................................82Creating Remote Recovery Sets........................................................................................................84

Viewing Remote Recovery Sets group details..............................................................................86Managing Remote Recovery Sets schedules.....................................................................................87

Adding schedules..........................................................................................................................87Editing schedules..........................................................................................................................89Deleting schedules........................................................................................................................89

Viewing Source and Target StoreServ Recovery Sets.......................................................................90Managing Remote Recovery Sets......................................................................................................90

Mounting Remote Recovery Sets..................................................................................................92Unmounting Remote Recovery Sets.............................................................................................94Attaching Remote Recovery Sets.................................................................................................94Detaching Remote Recovery Sets................................................................................................96Managing Remote Recovery Sets in various configurations.........................................................96Managing Remote Recovery Sets in Peer Persistence................................................................97

Deleting Remote Recovery Sets.........................................................................................................97Updating Recovery Manager Cache...................................................................................................98Peer Persistence................................................................................................................................98Express Protect for Remote Recovery Sets.......................................................................................99Multiple RMC Appliance support for Remote Copy configurations.....................................................99

7 Working with Recovery Sets Express Protect.................................................100Prerequisites.....................................................................................................................................100Types of Backups.............................................................................................................................100

Multistreaming.............................................................................................................................100HPE StoreOnce multinode configuration.....................................................................................100

Cancelling backup............................................................................................................................101Creating Express Protect policies.....................................................................................................101

Creating default Express Protect policies....................................................................................102Creating Express Protect policies...............................................................................................104

4 Contents

Creating Express Protects................................................................................................................109Creating one-click Express Protect...................................................................................................109Creating Recovery Set level Express Protect...................................................................................110Scheduling Express Protects............................................................................................................112Modifying Express Protect schedules...............................................................................................117Viewing Express Protect details.......................................................................................................117Element Recovery Technology.........................................................................................................119

Configuring ERT..........................................................................................................................119Mounting Express Protect objects...............................................................................................120Unmounting Express Protect objects..........................................................................................122Copying VMDK files to datastores...............................................................................................122Attaching VMDK files to Virtual Machines...................................................................................123Detaching VMDK files from Virtual Machines..............................................................................124Virtual Machine Instant Recovery................................................................................................125

Instant recovery of VMs from the Express Protect Object datastore.....................................125Listing VMs on Express Protect Object datastore..................................................................125Recovering a VM from the mounted Express Protect objects on ESXi host..........................126Removing from inventory.......................................................................................................127

Additional vCenter operations.....................................................................................................128Managing concurrent Express Protects............................................................................................128Types of restores..............................................................................................................................129Restoring from Express Protects......................................................................................................129

8 Working with Catalyst Copy Recovery Sets....................................................133Prerequisites.....................................................................................................................................133Creating Catalyst Copy policies........................................................................................................133

Prerequisites................................................................................................................................133Configuring default Catalyst Copy policies..................................................................................133

Creating Catalyst Copy Recovery Sets............................................................................................135Creating one-click Catalyst Copy Recovery Sets........................................................................135Creating Catalyst Copy Recovery Sets.......................................................................................138

Managing Catalyst Copy Recovery Set schedules...........................................................................139Creating Catalyst Copy schedules..............................................................................................139Modifying Catalyst Copy schedules............................................................................................143Deleting Catalyst Copy schedules...............................................................................................143

Restoring from Catalyst Copy...........................................................................................................1439 Using HPE 3PAR Peer Motion Manager Software with RMC-V......................14810 Troubleshooting.............................................................................................149

Common issues................................................................................................................................149Registering an RMC Appliance.........................................................................................................149

RMC Configuration error.............................................................................................................149HPE 3PAR OS upgrade error......................................................................................................149Recovery Set Snapshot or Express Protect backup restore.......................................................150

RMC-V Installation............................................................................................................................150Installation fails............................................................................................................................150User does not have required privileges.......................................................................................150Old RMC-V plugins......................................................................................................................151Unable to connect to the given IP/Host Name............................................................................152Unable to add storage or backup systems..................................................................................153OVF deployment failed................................................................................................................154Not able to reach the RMC VM....................................................................................................154Not able to reach the RMC IP......................................................................................................155Password update failed...............................................................................................................155RMC-V plugin not visible.............................................................................................................156

Contents 5

RMC-V Upgrade...............................................................................................................................156Found an existing RMC-V plugin.................................................................................................156Unable to proceed with upgrade.................................................................................................157Upgrade failure............................................................................................................................158Multi RMC deployment partial failures.........................................................................................158Installer logs................................................................................................................................158

RMC-V Snapshots............................................................................................................................158Smartclone with multiple disks or volumes..................................................................................158Unable to back up Snapshots.....................................................................................................159Snapshot creation failed..............................................................................................................159Snapshots and backups not displayed........................................................................................159Incorrect Snapshot count.............................................................................................................160

RMC-V Schedules............................................................................................................................160Failed email notifications.............................................................................................................160Incorrect VMs on the Summary page..........................................................................................160Failed to create array snapshot...................................................................................................160

Element Recovery Technology.........................................................................................................161Instant VM recovery fails.............................................................................................................161vCenter selection dialog box.......................................................................................................161VM recovery error........................................................................................................................161Mount/Unmount error..................................................................................................................161Unable to detect Express Protect Object LUNs..........................................................................162Unable to detect Express Protect Object volumes......................................................................162Inaccessible Express Protect Objects.........................................................................................162Invalid Express Protect Object....................................................................................................163Object deleted or not created......................................................................................................163File in use from the datastore......................................................................................................163Express Protect Object in use.....................................................................................................163Virtual Disks not displayed..........................................................................................................164

Remote Recovery Sets Configurations.............................................................................................164Error: Not a 3PAR Volume...........................................................................................................164Remote Copy groups not listed...................................................................................................164Listing Remote Copy groups takes a long time...........................................................................165Recovery Sets not appearing......................................................................................................165Snapshot creation fails................................................................................................................165Manage tab not appearing..........................................................................................................165Snapshot error.............................................................................................................................165Recovery Set not displayed.........................................................................................................166Remote appliance not found.......................................................................................................166Schedule fails..............................................................................................................................166Datastores not displayed.............................................................................................................166

Others...............................................................................................................................................166Attaching VMDKs........................................................................................................................166Adding a storage system.............................................................................................................167Objects state................................................................................................................................167VMware operations fail................................................................................................................167Unable to delete VVOL Recovery Set.........................................................................................167ssh connection error....................................................................................................................168Backup issue...............................................................................................................................168Scheduled jobs not running.........................................................................................................168Unable to take snapshots or backups.........................................................................................169Rebooting RMC appliance while a backup job is in progress.....................................................169Failed to attach the VV................................................................................................................169Incorrect store client password....................................................................................................169Driver uninitiated error.................................................................................................................170

6 Contents

Object not found error..................................................................................................................170Incremental Express protect or full backup fails..........................................................................170License error................................................................................................................................170Restore fails.................................................................................................................................171Unable to operate from the vSphere Web Client.........................................................................171Restore target issue....................................................................................................................171Default Snapshot policy settings error.........................................................................................171Error: Session not initialized........................................................................................................172Snapshot mount fails...................................................................................................................172

11 Support and other resources.........................................................................173Accessing Hewlett Packard Enterprise Support...............................................................................173Accessing updates............................................................................................................................173Websites...........................................................................................................................................173Customer self repair.........................................................................................................................174Remote support................................................................................................................................174Documentation feedback..................................................................................................................174

A FAQs...............................................................................................................175How to generate a support ticket for troubleshooting issues............................................................175What are the log files required for troubleshooting RMC-V issues...................................................176What are the required user privileges...............................................................................................176

Glossary.............................................................................................................178Index...................................................................................................................179

Contents 7

1 OverviewThe HPE Recovery Manager Central for VMware (RMC-V) allows VMware Server administratorsto protect vSphere Web Client Server instances and databases with application-consistentrecovery points. The application-consistent snapshots are created, scheduled, and managed onHPE 3PAR StoreServ or HPE Hyper Converged 250. The RMC Express Protect feature providesa second-tier of data protection with backup from HPE 3PAR StoreServ or HPE Hyper Converged250 to HPE StoreOnce. Backups to HPE StoreOnce are self-contained volumes, de-duplicatedto save space, and can be used to recover back to the original or a different HPE 3PAR StoreServarray, even if the original base volume is lost.

Host Server Hardware

VMware ESXi

VM

APP

VM

APP

VM

RMC

NIC

NICFibreChannel

vCenterAdministrator

vCenter server

IP NetworkCatalyst API -

data movement

CoFC protocolBlock level

SCSI commands

SnapshotBackup/recovery StoreOnce Backup System

Catalyst Store

vCenterPlug-in

(RMC-V)

RMC GUI

Snapshots

StoreServ Disk Array

Virtualvolumes

ManagementInterface

iSCSI(optional)

FibreChannel

FC-HBA

FC SAN

NOTE: HPE StoreVirtual is referred to as HPE Hyper Converged 250 System, since HPEHyper Converged 250 System is a flavor of HPE StoreVirtual System. The GUI refers to thestorage system type, the product documentation refers to the hardware supported.

RMC-V is deployed as a vCenter Web Client plugin. First log on to the vCenter Server beforeaccessing the RMC-V features. Restart the VMware vCenter Web Client services before loggingin for the first time.Plug-in integration for RMC-V is available only with the vSphere Web Client.For information on the supported hardware and software platforms, see the Single Point ofConnectivity Knowledge (SPOCK) website: http://www.hpe.com/storage/spock.SPOCK is the primary portal used to obtain detailed information about supported HP Storageproduct configurations. An HP Passport account is required to enter the SPOCK website.

8 Overview

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

IMPORTANT: If you have selected a language other than English during installation of theOS, the Recent Tasks pane displays:• 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 selectedduring installation.

RMC-V supports installation on Windows server with English, Chinese, and Japanese locale.However, operations are supported only in English.

NOTE: RMC-V does not support VMware vCenter Servers configured in Linked mode andEnhanced Linked mode.

Features• “Recovery Set management” (page 9)

• “Recovery Set data consistency” (page 10)

• “Recovery Set policy” (page 10)

• “Datastore Recovery Sets” (page 11)

• “Virtual Machine Recovery Sets” (page 12)

• “VM Recovery Sets with additional disks” (page 12)

• “Recovery Set browser” (page 13)

• “VMFS snapshots” (page 14)

• “Scheduling options” (page 14)

Recovery Set managementRMC-V allows you to take volume level Snapshots of VMs and datastores.A Recovery Set is a collection of Snapshots of the HPE 3PAR StoreServ storage system, storedon the HPE StoreOnce backup system.A datastore is created on HPE 3PAR StoreServ and HPE Hyper Converged 250 System Storagevolume. A VM can have multiple disks from one or more datastores. During VM Recovery Setcreation, RMC-V identifies all underlying HPE 3PAR StoreServ and HPE Hyper Converged 250System Storage volumes and takes Recovery Sets simultaneously for all volumes to ensureconsistency. For more information, see “Creating Recovery Sets” (page 54).

Figure 1 VM Recovery Sets

Features 9

Recovery Set data consistencyYou can create the following types of consistent recovery sets from RMC-V:

• Crash Consistent—A simple virtual volume Recovery Set without disabling the memoryblocks inside the guest OS results in a crash consistent Recovery Set of the VM. Data thatis not flushed is lost, however all data written to the file system is available. Sanity checkingof file system (fsck) is needed after recovery.

• Application Consistent—Application consistent Recovery Set of VMs for data compatibilitywith supported applications.

To stop IO on a VM, ensure the following:

• The latest Windows updates are installed.

• If additional disks are to be configured, then the SCSI bus must be configured as per VMwareKB article 2015181.

NOTE: An application consistent Recovery Set is attempted only if VMware Tools is installedon the Windows guest OS. VMware must first successfully create a VMFS (Virtual Machine FileSystem) snapshot. For information on the best practices and limitations of VMware snapshots,see the VMware knowledge base http://kb.vmware.com/.

Recovery Set policyRMC-V allows you to create Recovery Set policies for VMs and datastores. Only one defaultpolicy is permitted for every VM and datastore. VM and datastore policies exist independently.At least one policy must be defined or available for the creation of Recovery Sets. RMC-V allowsyou to deploy multiple RMC instances on the vCenter Server.

NOTE: RMC-V supports maximum eight RMC instances on a vCenter Server. However,multi-RMC is not supported for HPE StoreServ 3PAR Remote Copy solution.

The Retain Recovery Set option requires the HPE 3PAR Virtual Lock license. RMC-V checksfor an existing HPE 3PAR Virtual Lock license on the storage system when a Recovery Set iscreated with the specified retention.In RMC-V, the Recovery Set policy contains the following attributes:

• “Select RMC Host Name”

• “Numeric”

• “Expiration/Retention”

• “Create Recovery Sets with VSS-aware application consistency”Numeric and Expiration/Retention policies are mutually exclusive. For a numeric policy, if theoldest snapshot is mounted, it cannot be deleted and the snapshot creation fails.

Select RMC Host NameBy default this field displays the first RMC instance registered on the vCenter Server. All RMCinstances registered with the vCenter Server are listed in the drop-down list.

• If multiple RMC Appliances are configured, save a snapshot policy and perform otheroperations.

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

10 Overview

http://kb.vmware.com/kb/2015181

http://kb.vmware.com/

• For a VM or datastore, only one RMC instance acts as an active RMC instance. CreateRecovery Set (both, Back up and Snapshot) is allowed only on the active RMC instance.

• VM ownership can be moved from one RMC to another. However, the numeric policy countis reset to the count reflected in the selected RMC. If you change the VM ownership betweenRMCs in the same multi-RMC configuration, Recovery Sets from all RMCs are consolidatedand displayed.

NumericYou can choose the number of Recovery Sets to be retained, in the range:

• 1–500 for HPE 3PAR StoreServ

• 1–30 for VVOL

• 1–32 for HPE Hyper Converged 250When the number of Recovery Sets is at the maximum limit, the oldest Recovery Set is deletedwhen a new Recovery Set is created.

Expiration/Retention

• Enable expirable Recovery Sets—Allows you to specify that the created Recovery Sets areremoved according to a specified schedule and the number of Recovery Sets created is notaffected.

• Retain Recovery Set—The supported number of hours and days that a Recovery Set isretained.

You can select expiration time or retention time or both. However, if you select both expirationtime and retention time, then expiration time must be greater than or equal to retention time.Otherwise, the retention time defaults to the expiration time.Expiration/Retention option is not supported for VVOLs and HPE Hyper Converged 250.

Create Recovery Sets with VSS-aware application consistencyThis option is used to create Recovery Sets that adhere to data format standards used by MicrosoftVSS for guest operating systems. This option is available for VMs and datastores. Also, thisoption can be enabled while using pre- or post freeze scripts with other operating systems (LINUX)and vmware-tools for guest consistency.

Datastore Recovery SetsA datastore is created on a fibre channel or iSCSI virtual volume. During Recovery Set creation,RMC-V identifies the HPE 3PAR volume used and creates a Recovery Set of the volume. RMC-Vstores the details of all virtual disks and VMs available in the datastore.This feature has the following restrictions:

• The maximum number of datastore snapshots that you can create is 500 for HPE 3PARStoreServ, 32 for HPE Hyper Converged 250, and 30 for VVOLs. If you create more thanthe maximum number of snapshots, the oldest snapshot gets deleted. However, if the oldestsnapshot is mounted, the create operation fails until the oldest snapshot is unmounted.

• The datastore must be on one HPE 3PAR StoreServ or HPE Hyper Converged 250 volume.

• RDM virtual volumes in the datastore are not contained in the Recovery Set. It is possiblefor an HPE 3PAR virtual volume to be used as an RDM volume in a guest OS. The RDMvolume is in a datastore created on another HPE 3PAR virtual volume.

NOTE: A Recovery Set of a datastore does not include any RDM 3PAR virtual volumes.

Features 11

• Snapshots of only the volume hosting the datastore are considered in the Recovery Set. IfVMs in the datastore are associated with other datastores (additonal virtual hard disks fromother datatores), the associated datastores are ignored.

• All datastore Recovery sets can be application or crash consistent. File system and/orapplication integrity checks must be performed in the guest OS for the crash consistentRecovery Sets after restoration.

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

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

• The datastore must not be on an ESXi SAN boot disk. Recovery Set operations are notsupported on datastores residing in ESXi SAN boot disks.

Virtual Machine Recovery SetsVM configuration files are created in a datastore. Virtual disks (VMDKs) used by VMs are createdon one or more datastores. A VM can use HPE 3PAR volumes directly as RDM virtual disks.RMC-V identifies all HPE 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 alsorecorded in the repository during Recovery Set creation.A VM Recovery Set has the following restrictions:

• The maximum number of VM snapshots that you can create is 500. If you create more than500 snapshots, the oldest snapshot gets deleted. However, if the oldest snapshot is mounted,the create operation fails until the oldest snapshot is unmounted.

• Virtual disks used by a VM must be from the HPE 3PAR datastore and the latter must satisfythe conditions mentioned in “Datastore Recovery Sets” (page 11).

• If the VM uses more than one HPE 3PAR or HPE Hyper Converged volume, all of thevolumes must be from the same HPE 3PAR or HPE Hyper Converged storage array.

• VMs that use a mix of HPE 3PAR or HPE Hyper Converged virtual volumes, and third-partyvirtual volumes are not supported.

• All VM Recovery sets can be application or crash consistent. File system and/or applicationintegrity checks must be performed on the guest OS after restoration for the crash consistentRecovery Sets.

• VMs using NFS datastores are not permitted.

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

For more information, see Figure 1 (page 9).

VM Recovery Sets with additional disksUsing RMC-V you can create Snapshots (Recovery Set) and Express Protect for the VMs thatare configured with additional disks, such as Virtual Disks and Raw Device Mapping (RDM).Application consistent Snapshot is supported for virtual mode RDM. However, applicationconsistent Snapshot is not supported for physical mode RDM. Hence, while creating scheduledjob for a VM that has physical mode RDM, application consistent option must not be selected.RMC-V identifies all storage volumes hosting the virtual disks (including RDM volumes) associatedwith the VM, and creates a Snapshot of all volumes as a group simultaneously. This is applicableonly for VM level Snapshot/Express Protect.However, when a datatsore level snapshot/Express Protect is selected, RMC-V creates Snapshotof only the volumes hosting the datastore. The volumes hosting additional virtual disks (inclusiveof RDM) associated with one or more VMs in the datastore, are not considered.

12 Overview

For obtaining application consistent snapshot of the associated RDM, the RDM must be a virtualmode RDM.Recovery Set is not supported for RDM associated or attached to VVOL VMs.For the Remote Copy Group Snapshots to include the additional virtual disk in the Snapshotprocess, the datastore volume hosting this additional virtual disk must be part of the same RemoteCopy Group.

Recovery Set browserIn RMC-V, every Recovery Set, VM, or datastore has its own metadata, which is used in instanceswhere a restoration is necessary.To view the Recovery Set browser:1. On the vCenter, click VMs and Templates.2. Select a VM and click the Related Objects tab.3. Click Recovery Sets.4. Double-click the Snapshot.5. Click the Summary tab.

Figure 2 Recovery Set browser

A Recovery Set of a VM or datastore has the following properties:

• Recovery Set creation time.

• HPE 3PAR StoreServ or HPE Hyper Converged 250 storage system details where RecoverySet volumes exist.

• Recovery Set name (optional).

• Number of Recovery Set volumes in the Recovery Set.

• List of pairs (source volume, Recovery Set volume), where each pair can have a list of virtualdisks and/or VM names.

All Recovery Sets are organized in the browser based on their creation times. The browserdisplays relevant metadata so that you can make restore decisions faster and without mountingRecovery Set volumes.The data shown in the Recovery Set browser comes from the metadata repository and might notreflect the current state of the HPE 3PAR StoreServ or HPE Hyper Converged 250 storagesystem. It is possible that volumes shown in the browser might not exist in the HPE 3PARStoreServ or HPE Hyper Converged 250 storage system. For example, if a volume is deleted.

Features 13

VMFS snapshotsTo maintain an application consistent Recovery Set, a VMFS snapshot is created before creatingan HPE 3PAR Recovery Set and the VMFS copy is deleted after the HPE 3PAR Recovery Setis created.Coexistence of VMware vCenter snapshots (VMFS) with RMC-V local and Remote Copysnapshots is supported.

Scheduling optionsYou can do the following:

• Snapshots and Express Protects creation according to a schedule using the scheduler.

• Options to schedule Recovery Set and Express Protect creation and also to specify whenthe task must be performed.

• Schedule a Recovery Set and Express Protect creation task to occur on a one off basis.

14 Overview

2 LicensingLicensing is used to enable optional product functionality, such as capacity upgrades andreplication. Most features are only enabled when they are licensed.

OverviewCertain features are enabled only if they are licensed. For more information on licensing, seethe HPE Recovery Manager Central User Guide.

HPE 3PAR StoreServ and HPE Hyper Converged 250 Systems licensingRMC and RMC-V licenses must be installed on the HPE 3PAR StoreServ Storage Systems andthe HPE Hyper Converged 250 Systems.

NOTE: RMC does not allow users to install or delete RMC Base or RMC-V licenses. Theselicenses are directly installed on the HPE 3PAR StoreServ Storage and HPE Hyper ConvergedStorage 250 Systems. For information on installing these licenses, see the HPE 3PAR StoreServStorage and HPE Hyper Converged Storage documentation.

HPE StoreOnce licensingStoreOnce Catalyst license must be installed on HPE StoreOnce Backup systems.

NOTE: RMC does not allow users to install or delete a StoreOnce Catalyst license. This licenseis directly installed on the HPE StoreOnce Backup system.

License models supported by RMC-VThe Recovery Manager for VMware vSphere License is required for RMC-V.For information on the required HPE 3PAR StoreServ, HPE Hyper Converged 250, and HPEStoreOnce licenses, see http://www.hpe.com/storage/spock.

Licensing scenariosTable 1 (page 15) describes how the appliance handles licensing for different user actions:

Table 1 Licensing scenarios

NotesResultLicense policy or typeUser action

The license required iseither Permanent or validTemporary license.

If a valid license exists,create a snapshot.

•• RMC-V licenseCreate snapshot

• •Create snapshot withexpiration and retentiontime

Virtual Copy license

• Virtual Lock license

The license required iseither Permanent or validInstant-On license.

If a valid license exists,you can back up yourrequired files.

StoreOnce Catalyst licenseCreate Backup

All these operationsfunctions without

License not requiredMount, unmount, delete,and restore of snapshots.

licenses provided a validlicense exists when asnapshot is created.

All these operationsfunctions with licenses

RMC-V license is required.Restore and delete allbackups.

provided a valid licenseexists when a backup iscreated.

Overview 15


3 Installing HPE RMC-VThe simple, intuitive RMC installation wizard guides you through a set of screens with customfields for installing RMC-V. The following sections explain the installation process and theprerequisites required.

Installation workflowFigure 3 (page 16) represents the RMC installation workflow and options. The installation wizardprovides the following options:• HPE RMC Only: Deploys RMC without VMware vCenter plug-in. HPE RMC standalone VM

can be used for other Recovery Manager products (RMC-S, RMC-O).• HPERMC integratedwith VMware: Manages recovery instances for single VMware vCenter

Server.The highlighted section in Figure 3 (page 16) explains installing HPE RMC integrated withVMware.

Figure 3 RMC Installation Wizard workflow

HPE RMC installer

HPE RMC only

Installstandalone RMC

Upgradestandalone RMC

Install RMC-V plug-inand register existing

RMC appliance

HPE RMC integratedwith VMware

Multi RMCdeployment

RMC-V upgrade/RMC upgrade

RMC-Vplug-inexists?

Standalone RMC exists?

Upgraderequired?

Yes Yes

NoYes

No

Install RMC-V plug-inand RMC appliance/VM

16 Installing HPE RMC-V

Prerequisites• Ensure that your system meets the system requirements for installing RMC.

• Extract the HPE RMC Installer 3.0.0 ZIP folder to a Windows host. Windows vCenterserver can also be used. The supported Windows hosts are:

◦ Windows 7

◦ Windows 8

◦ Windows 10

◦ Windows 2008 R2

◦ Windows 2012 R2

Following are the contents of the ZIP file:

Table 2 Installer files

DescriptionInstaller files

Execution fileApplication

Required for upgradingRPM file

Required for deploying VMVMDK file

MF file

OVF file

Configuration file of the installerJSON file

Ensure that all the files are extracted to the same folder.

• For FC deployments, your environment must meet the following requirements:

All the FC HBAs required for FC-based backups must be of the same vendor.◦◦ Appropriate zoning configuration to access storage and backup systems.

• For iSCSI deployments, your environment must meet the following requirements:

HPE 3PAR StoreServ must be configured for iSCSI.◦◦ Assigned IP address for iSCSI port must be reachable from the RMC appliance.

• If FQDN is used, the domain server must be accessible by the installer host and the RMCVM to be deployed.

• Ensure appropriate CPU, RAM, and licenses are available on the ESXi and vCenter servers.

• Ensure appropriate CPU and RAM is configured on the ESXi server.

• Ensure that you have enough free space (minimum 120 GB) on the datastore, to install RMCon a thick provisioned vdisk.

• Ensure you have the required privileges for deployment and RMC-V plugin integration. Formore information, see “For deployment” and “For RMC-V plugin integration”.

• Ensure that all old RMC-V plugins and HPE OneView for vCenter plugins are removed. Formore information, see “Found an existing RMC-V plugin” (page 156).

• Check the CKsum of the HPE RMC Installer 3.0.0 file.

Prerequisites 17

https://h20272.www2.hpe.com/spock/

Connectivity requirementsFigure 4 (page 18) details the connections between the RMC VM, HPE 3PAR StoreServ or HPEHyper Converged 250 System, and HPE StoreOnce Backup System.

Figure 4 Connectivity diagram

HPE 3PAR StoreServor

HPE HyperConverged 250 System

FC or iSCSI for Data Traffic

FC or Ethernet for Data Traffic

Management Network

HPE StoreOnce

RMC VM

vCenter server Installer Host

RMC-V

NIC NIC

For successful RMC deployment, ensure that connectivity is established between the followingcomponents:1. Installer host and vCenter server2. vCenter server and the (to be deployed) Installer RMC VM3. Installer RMC VM (to be deployed) and the Installer host4. Storage system and RMC VM (management link)5. Backup system and RMC VM (management link)

Connectivity between storage systems and RMC appliance• The connectivity between HPE 3PAR StoreServ and RMC appliance is either on:

FC◦◦ iSCSI

• The connectivity between HPE Hyper Converged 250 System and RMC appliance is oniSCSI.


Connectivity between backup systems and RMC appliance• The connectivity between HPE StoreOnce to RMC appliance is over:

◦ Co-FC (Catalyst Over Fibre Channel)

◦ Co-Ethernet (Catalyst Over Ethernet)

RMC installation options

HPE RMC integrated with VMwareHPE RMC

• RMC install and register RMC-V plugin• Standalone RMC install

• •Standalone RMC upgrade Register plugin only

• Multi RMC deployment

• RMC-V upgrade

RMC installation options 19

Using the installation wizard1. In the extracted HPE RMC Installer 3.0.0 folder, double click the HPE RMC Installer

3.0.0.exe file.The introduction screen appears:

Figure 5 Introduction screen

Introduction

License AgreementDeploy HPE RecoveryManager Central

Install / Upgrade

RMC Configuration

Network Configuration

Network Interface Settings

Array ConfigurationBackupSystemConfiguration

Summary

Diagnostics

Install / Upgrade CompleteSummary

InstallAnywhere

Cancel Help

ESXi Server and DatastoreSelection

Next

HPE StoreOncePrimary Storage Array

RMC VM

HPE Recovery Manager Central

Welcome to the RMC Installation Wizard!

HPE Recovery Manager Central (RMC) - Your gateway to fast, simple, efficient, and reliabledata protection for your business critical applicxations!

This wizard will help you install or upgrade RMC with either of the following options:

HPE RMC Virtual Machine Instance

Allows you to use RMC for MS SQL (RMC-S), RMC for Oracle (RMC-O) aswell as protect any other application with crash-consistent snapshots and backups

Additionally includes the installation of RMC plug-in to VMware vCenter forprotecting VMware Virtual Machines and Datastores

HPE RMC Virtual Machine Instance + RMC for VMware (RMC-V)

PreviousPrevious

IntroductionHPE Recovery Manager Central Installer 3.0.0.57

2. On the Introduction screen, click Next.3. On the License Agreement screen, review the license agreement and if you agree, select

I accept the terms of the License Agreement, and then click Next.4. Select the deployment type and enter the vCenter details on the “Deploy HPE Recovery

Manager Central” (page 21) screen and click Next.5. To proceed with either additional RMC VM deployment or, RMC standalone installation or

upgrade, enter the required credentials and click Next on the “Install/Upgrade” (page 23)screen.

6. Select the ESXi host and datastore from the “ESXi Server and Datastore selection” (page25) screen and click Next.

7. Enter the RMC configuration details on the “RMC Configuration” (page 26) screen and clickNext.

8. Select the appropriate network configuration from the “Network Configuration” (page 28)screen and click Next.

9. Enter the required details on the “Network Interface Settings” (page 29) screen and clickNext.


10. To add a storage system and a backup system, enter the required details on the “StorageSystem Configuration (optional)” (page 31) and “Backup System Configuration (optional)”(page 32) screens. (This step is optional during installation and can be completed laterthrough the RMC GUI after installation.)

11. Click Start and after installation click Next on the Summary screen.12. Click Start Diagnostics on the “Diagnostics (optional)” (page 34) screen for details on the

overall health of the deployed RMC VM.13. Click Next on the “Install/Upgrade complete summary” (page 35) screen, after viewing the

displayed details.

More information“RMC Installation Wizard screens” (page 21)

RMC Installation Wizard screens1. “Introduction” (page 21)2. “License Agreement” (page 21)3. “Deploy HPE Recovery Manager Central” (page 21)4. “Install/Upgrade” (page 23)5. “ESXi Server and Datastore selection” (page 25)6. “RMC Configuration” (page 26)7. “Network Configuration” (page 28)8. “Network Interface Settings” (page 29)9. “Storage System Configuration (optional)” (page 31)10. “Backup System Configuration (optional)” (page 32)11. “Summary” (page 33)12. “Install/Upgrade complete summary” (page 35)13. “Diagnostics (optional)” (page 34)

IntroductionThe Introduction screen displays the tasks you can perform using the RMC-V wizard. You canperform one of the following tasks:

• Install or upgrade HPE RMC standalone Virtual Machine instance.

• Install or upgrade HPE RMC for VMware (including the RMC vCenter plugin).

License AgreementThe License Agreement screen displays the end-user license agreement—terms of the licenseagreement.Details mentioned as part of the agreement: authorization, consumer rights, copyright, warrantyinformation, and so on.

Deploy HPE Recovery Manager CentralChoose the deployment option and provide the system details. The two options of deploymentavailable are:HPE RMC integrated with VMware (Install/Upgrade)Select to manage recovery instances for single VMware vCenter server.When you select this option, the RMC VM is installed and the RMC-V plugin is registered withVMware vCenter. You can either install or upgrade both RMC VM and the RMC-V plugin. Also,

RMC Installation Wizard screens 21

you can install RMC-V plugin and associate with the existing RMC VM. For more information,see Figure 3 (page 16).

NOTE: The RMC VM installed using this option, can be configured for RMC-S and RMC-Odata protection.

HPE RMC Only (Install/Upgrade)Select to install or upgrade HPE RMC without VMware vCenter plugin. HPE RMC standaloneVM can be used for other Recovery Manager products (RMC-S, RMC-O).

HPE Recovery Manager Central Installer 3.0.0.57

Deploy HPE Recovery Manager Central

Introduction


Install / Upgrade

RMC Configuration




Summary

Diagnostics



InstallAnywhere

Cancel Help NextPrevious

Fields marked with * are mandatory

Hostname/IP address*

Password*

Username*

vCenter Details

Installation Type

HPE RMC integrated with VMware (Install / Upgrade)

HPE RMC Only (Install / Upgrade)

Installs/upgrades HPE RMC with VMware vCenter plug-in.

Installs/upgrades HPE RMC as a standalone VM without registering as a plug-in withVMware vCenter. HPE RMC standalone VM can be used for other Recovery Managerproducts (RMC-S, RMC-O).

Select the intended use of HPE RMC after the deployment:

The vCenter details to provide are:

• Host Name/IP address—If you enter the Fully Qualified Domain Name (FQDN), ensure thatyou enter the appropriate DNS IP in the Network Configuration screen.If host name of the FQDN is entered, ensure that you provide an appropriate search domainand DNS IP in the Network Configuration screen.Host name without DNS entry must not be entered.

• Username—Enter valid vCenter user name.

• Password—Enter valid vCenter password.You can change the default password from the RMC GUI. For more information, see theHPE Recovery Manager Central User Guide.


Ensure you have the required privileges for deployment and RMC-V plugin integration. For moreinformation, see “For deployment” and “For RMC-V plugin integration”.

NOTE: The vCenter details entered remain in the RMC-V repository for specific operations.You can view and change the details, after deployment, by going to HPE RMCConfiguration→vCenter→vCenter vSphere Web Client.

Install/Upgrade

Upgrading to RMC-VTable 3 Upgrade scenarios

Upgrade to RMC-V 3.0.0 possible?Current version

YesRMC-V 1.2.0, 1.2.1, 2.0.0, 2.0.2

NoRMC-V 1.1.0

NoRMV 2.5.0 or later

Single RMC-V


Introduction


Install / Upgrade

RMC Configuration




Summary

Diagnostics



InstallAnywhere

Cancel Help NextPrevious

HPE RMC-V Install

This is a fresh installation as there is no Existing RMC-V Plug-in detected in the vCenter

Install RMC-V Plug-in & RMC Appliance

Install RMC-V Plug-in & Register ExistingRMC Appliance

This option installs RMC-V Plug-in and RMCAppliance. The RMC appliance installed will beautomatically registered with the installedRMC-V Plug-in.

RMC-V Install


On the Deploy HPE Recovery Manager Central screen, if the deployment option selected isHPE RMC integrated with VMware (Install/Upgrade), and if there is no previously existingRMC-V plugin, the HPE RMC-V Install screen displays the following options:

• Install RMC-V Plug-in and RMC Appliance—Select to install a new instance of RMC VM.

• Install RMC-V Plug-in and Register Existing RMC Appliance—Select to register anRMC-V plugin with the current instance of standalone RMC.The credentials to enter are RMC Host/IP, Username, and Password.

Select any one of the two available options, as per the requirement.

IMPORTANT: For the upgrade process to succeed, the installer host must have a minimumavailable space of 1.2 GB in RAM. If available space is less than 1.2 GB, the upgrade processmay fail with error: File upload failed.

RMC-V upgradeIf the deployment option selected is HPE RMC integrated with VMware (Install/Upgrade), andif an RMC-V plugin is already registered, the Install/Upgrade screen displays the following detailsof the registered RMC-V plugin:

• RMC Host Name/IP address.

• RMC version.

• Upgrade required.

• Current RMC-V vCenter plugin version.If the RMC VM or RMC-V plugin is not of the latest version, the installation wizard displays apopup message stating an upgrade is required. After clicking Next on the popup message, theRMC installation wizard upgrades all components (RMC-V plugin and RMC Appliance) thatrequire an upgrade. If there are multiple RMCs (multRMC configuration) configured with the samevCenter, then the installation wizard upgrades all RMCs that require an upgrade.

Multi RMCIf the RMC components are of the latest versions, the screen displays the RMC details and byclicking Next you can install additional RMC VMs attached to the same RMC-V plugin, allowinga multi-RMC configuration.RMC-V supports a maximum of eight RMC instances on a vCenter Server. However, multi-RMCis not supported for HPE StoreServ 3PAR Remote Copy solution.To ensure that the upgrade is successful, the installer host must have a minimum available spaceof number of RMCs * 1.2 GB in RAM. If this condition is not met, the upgrade process mayfail with error: File upload failed.

RMC onlyIf the deployment option selected is HPE RMC Only (Install/Upgrade), the Install/Upgradescreen displays the following options:

• Install—Select to install a new instance of RMC VM.

• Upgrade—Select to upgrade the current instance of RMC.The credentials to enter are RMC Host/IP, Username, and Password.

Select any one of the two available options, as per the requirement.


ESXi Server and Datastore selection

Introduction


Install / Upgrade

RMC Configuration




Summary

Diagnostics


InstallAnywhere

Cancel Help



NextPrevious

ESXi Server and Datastore Selection

Installation Location

Select Datastore

Datastore Name

DEV-DC

*Thick provisioned virtual disk format will be used.

Type VendorAvailable Space (GB)

It is mandatory to select an ESXi host and a datastore before clicking Next.Only datastores with minimum required free space (120GB) are enabled, rest remain disabled inthe table below.

Search boxAll the ESXi hosts are displayed on the screen. If the list of ESXi hosts is long, you can use theSearch box to find an ESXi host quickly.Select ESXi hostIf the selected ESXi host is not connected, an error message is displayed and you cannot selecta datastore.Select DatastoreContains information of datastore name, type, available space in GBs, and vendor details.VVOL datastores are not supported for RMC deployment.Datastores with a minimum space of 120 GB are enabled, the other datastores are disabled.Although 120 GB is required, RMC VM does not occupy all 120 GB. RMC VM occupiesapproximately 60 GB of space and the free space is left to ensure proper functioning of RMCVM.


RMC Configuration

CAUTION: Before selecting configuration options, check the selected ESXi Host Memory andCPU configurations. The selected option fails if the ESXi Host Memory and CPU configurationdoes not support the option. The VM is deployed on root resource pool, therefore appropriateamount of CPU and memory must be available for use at the root resource pool for the deploymentto succeed.

Introduction


Install / Upgrade

RMC Configuration




Summary

Diagnostics


InstallAnywhere

Cancel Help



NextPrevious

RMC Configuration

RMC Virtual Machine Configuration

CPU and Memory Configuration

2 vCPU, 8 GB vRAM

4 vCPU, 16 GB vRAM

8 vCPU, 32 GB vRAM

16 vCPU, 64 GB vRAM

Note: For Custom configuration use VM edit settings option in vCenter vSphere client.

The selected option “2 vCPU, 8 GB vAM” directs theinstaller to deploy RMC VM with 2 vCPU and 8 vRAM.

Specify RMC Hostname/VM name and Timezone here.

Hostname/VM name

Timezone

UserName*

Password*

Confirm Password*


Asia/Calcutta (GMT +5:30)

rmc-Jul-15-2016-14-58-49

Specify RMC GUI Password here.

Admin

CPU and Memory ConfigurationsSelect one of the following options to proceed:

• 2 vCPU and 8 GB vRAM





NOTE:• The number of CPUs and RAM size in the deployed RMC VM depends on the option you

select in this screen. The CPU and RAM configurations determine the number of concurrentExpress Protect backups. For more information, see the Single Point of ConnectivityKnowledge (SPOCK) website: http://www.hpe.com/storage/spock and the HPERecoveryManager Central User Guide.

• To increase the number of concurrent backups to HPE StoreOnce, select a higher CPU andmemory configuration.

• To achieve maximum performance, Hewlett Packard Enterprise recommends you to usephysical vCPUs for deploying RMC VM.This is because if logical cores (hyper-threading) are enabled in the ESXi host, RMC installerconsiders only the physical cores while validating the selection. The RMC installer permitsthe selection only if the physical cores of the total available vCPUs is equal or more thanthe selection made.

RMC VM ConfigurationHost name/VM nameEnter the host name of the RMC VM.TimezoneDrop-down with timezones of different regions.

RMC credentialsThe RMC credentials to enter are:

• UserName—By default, UserName is the Admin name. The default UserName cannot bechanged during RMC deployment.

• Password—Based on input given, the password strength is displayed. It can either be weak,fair, strong, or very strong.Enter the password again for confirmation.




Configuration options

PortsManagement and DataConnectionsConfiguration

Assign a single port group.Single virtual networkinterface connected to

Single virtual NIC • Single vNIC used formanagement only

storage system and storagedevice.

operations (no expressprotect backup).

• Single vNIC used forboth management anddata. However, thephysical NIC must be ofhigher configuration tohandle the load.

• Combination of singlevNIC and FC can beused, where vNIC isused as managementpath and FC used asdata path.

Assign two different portgroups.

Shared management anddata path.

Two virtual networkinterface connected to twodifferent subnets.

Two virtual NIC

Assign three different portgroups.

Dedicated managementinterface and two data pathinterfaces.

Three virtual networkinterface connected to threedifferent subnets.

Three virtual NIC


Introduction


Install / Upgrade

RMC Configuration




Summary

Diagnostics


InstallAnywhere

Cancel Help


Next

HPE StoreOnce

NIC 1

Primary Storage Array Primary Storage Array

RMC VMRMC VM

Snapshot Only Snapshot and Express Protect

Man

agem

ent

Previous



Single virtual NIC Configuration

Two virtual NIC Configuration

Three virtual NIC Configuration

Single network interface connected to a subnet. Works as both management and data interface.

NOTE: By default three NICs will be added to the RMC VM though single NIC configuration option isselected, however these additional NICs will be in disabled state and will not impact the configuration.


NIC 1

NOTE: If you select the Single virtual NIC option, you can see three NICs in the VM EditSettings page. Although the additional NICs appear on the screen, these NICs are not configured.Therefore, safe to ignore.


WARNING! HPE recommends using a DHCP server configured to provide unlimited leaseperiod. This recommendation is because though the deployment may succeed, periodic renewalof IP address by the DHCP server can prevent communication between the RMC-V WebClientplugin and RMC VM.



Introduction


Install / Upgrade

RMC Configuration




Summary

Diagnostics


InstallAnywhere

Cancel Help


NextPrevious


Network Interface SettingsNetwork Interface 1 (Management & Data)

FQDN

Network Port

Switch vSwitch0

Default Gateway

Preferred DNS

Alternate DNS

Search Domains

Subnet Mask*

IP Address*

Boot protocolVM Network (vSwitch0)

DHCP Static


FQDN (optional)Fully Qualified Domain Name (FQDN)—Check this box to enter either the FQDN or the IP address.The FQDN must be registered in the DNS before RMC VM deployment. If there is no DNS entryand FQDN is specified, the installation wizard fails to resolve and an error is displayed. RMC VMregistration with RMC-V plugin occurs with the specified FQDN, and subsequently RMC-V plugininteracts with the RMC VM using the FQDN. You can specify either the FQDN or the IP address.Network PortDrop-down with list of port groups of vSwitches with active physical NICs.SwitchDefined when selecting the network configuration.Boot protocolDHCP—Dynamic Host Configuration Protocol.Static—If you select static, then enter the IP address and subnet mask.Other details to enter are (optional):

• Default Gateway—If multiple subnets are involved, ensure that the default gateway isprovided.For the installer host and vCenter server to access the RMC appliance, subnet of themanagement network interface, installer host, and vCenter server must be the same. Ifsubnet is not the same, ensure that the default gateway is provided. Access to the RMC VMis required to change the default password, and register array or HPE StoreOnce credentials.If you deploy RMC without providing the default gateway, the installer cannot access the


RMC VM. In this scenario, you can go to the new RMC GUI deployed and complete theconfigurations mentioned. If an RMC-V plugin is deployed, go to the RMC-V GUI, remove,and add the RMC credentials on the RMC Appliance page.

• Preferred DNS—Make sure that preferred DNS is specified when vCenter, Array, andStoreOnce hostnames are specified as FQDN.

• Alternate DNS

• Search Domains—Enter a domain name.After installation, if you want to add either a storage system or a backup system in the samedomain, then enter the search domain name. You do not have to enter the complete FQDN.

Storage System Configuration (optional)Entering details on this screen during installation is optional. The details can be entered later onthe RMC GUI, after installation

Introduction


Install / Upgrade

RMC Configuration




Summary

Diagnostics


InstallAnywhere

Cancel Help


NextPrevious

Storage System Configuration (Optional)

Storage System Configuration (Optional)

Storage Type HPE 3PAR StoreServ

RMC requires you to select one or more Storage systems to function. Add storage systems andcredentials to the list below. You can skip this step now and configure storage systems later from RMC-V GUI after the installation.

Type FQDN / IP address*

This is optinal, click “Next” to skip.

Username* Rename

FQDN / IP address*

Username*

Password*



Storage type Drop-down with list of supported storage types. The supported storagetypes are HPE StoreServ and HPE Hyper Converged 250 System.

FQDN/IP address IP address of the host—FQDN/IP address of HPE StoreServ StorageSystem or HPE Hyper Converged 250 System. The IP of the HPE HyperConverged 250 System is any node on the management group.


IMPORTANT:• If FQDN is specified, make sure that DNS entry is provided in the

network configuration page. If the array is in a different subnet,make sure that default gateway is specified in the networkconfiguration page.

• The FQDN/IP address used to register HPE Hyper Converged 250systems must be a storage VSA node IP in the management group,and not the virtual IP or cluster VIP.

Username StoreServ/Hyper Converged 250 user name.Password StoreServ/Hyper Converged 250 password.Remove After adding an array, a Remove button is displayed on the screen. The

Remove button can be used to remove added storage arrays.Edit Select an existing array, make the required changes and then click Save.

NOTE: You can add one or more storage systems on this screen.

Backup System Configuration (optional)Entering details on this screen during installation is optional. The details can be entered later onthe RMC GUI, after installation

Introduction


Install / Upgrade

RMC Configuration




Summary

Diagnostics


InstallAnywhere

Cancel Help


NextPrevious

Backup System Configuration (Optional)

Backup System Configuration (Optional)

Type HPE StoreOnce

RMC requires you to select one or more Backup systems to function. Add HPE StoreOnce systemsand credentials to the list below. You can skip this step now and configure backup systems later from RMC-V GUI after the installation.

Type FQDN / IP address*

This is optinal, click “Next” to skip.

Username* Rename

FQDN / IP address*

Username*

Password*



Storage type The supported backup storage type is HPE StoreOnce.


FQDN/IP address IP address of the HPE StoreOnce Backup System.If FQDN is specified, make sure that DNS entry is provided in the networkconfiguration page. If the array is in a different subnet, make sure thatdefault gateway is specified in the network configuration page.

Username Backup system user name.Password Backup system password.Remove After adding a backup system, a Remove button is displayed on the

screen. The Remove button can be used to remove added backupsystems.

Edit Select an existing backup system, make the required changes and thenclick Save.

NOTE: If your HPE StoreOnce Backup System is located remotely and connected through aWAN, check for optimization of compression and checksum, over a low-bandwidth link.

SummaryThe Summary screen displays the configuration information entered by you in the previousscreens. This screen also displays invalid credentials (if any) entered for HPE 3PAR StoreServstorage systems, HPE Hyper Converged 250 storage systems, or HPE StoreOnce backupsystems.After successful deployment, the installation details are displayed on this screen. During theinstallation, the progress of deployment can be monitored on the Installation Details window.For troubleshooting installation and upgrade issues, see “RMC-V Installation” (page 150) and“RMC-V Upgrade” (page 156).


Introduction

License AgreementvCenter Name ::ESXi Name ::Datastore Name :: datastore1 (1)Host Name :: rmc-Jul-15-2016-14-58-49Disk Provisioning :: ThickDefault Gateway ::Preferred DNS Server ::eth0 Network Port :: VM Network(vSwitch0)eth0 bootprotocol :: staticeth0 IP Address ::eth0 Subset Mask ::CPU & Memory :: 2vCPU, 8GB vRAMRMC TimeZone :: Asia/Calcutta (GMT+5:30)

Installation Process Details

Start

100%

Deploy OVF template . . . CompletedPower ON Virtual Machine . . . CompletedChecking IP Reachablity Waiting for RMC Services to be available . . .CompletedUpdating RMC Password . . .Completed

. . .Completed

Deploy HPE RecoveryManager Central

Install / Upgrade

RMC Configuration




Summary

Diagnostics


InstallAnywhere

Cancel Help


NextPrevious


Summary

Diagnostics (optional)The Diagnostics screen displays in brief the health of the deployed RMC VM.The diagnostics of the RMC VM can also be performed after deployment from the RMC GUI.


Introduction


Install / Upgrade

RMC Configuration




Summary

Diagnostics


InstallAnywhere

Cancel Help


NextPrevious


Diagnostics

Diagnostics

Start Diagnostics

100%

The diagnostics will report on possible configuration issues in the setup. After running thediagnostics checks, the result will be shown below as well as saved for later reference, to view lateryou can go to RMC GUI. Running the diagnostics is optional.

ChecksRMC service checks

Services running

RAM sizeNumber of CPU coresProvisioned disk size

Storage systems registration

Backup systems (StoreOnce) registration

Backup systems registration

Remote copy registration

Element recovery technology (ERT) service(hp_istgt)

RMC hardware specific checks

RMC storage system specific checks

RMC backup system (StoreOnce)

RMC catalyst copy specific checks

RMC remote copy specific checks

RMC element recovery technology specific checks

RMC-V specific checks

Diagnostic checks is 100% complete.

Deatils

Saved the diagnostic details in C:/DiagnosticDetails.csv

Result

Passed

PassedPassedPassed

Passed

Not Registered

Not Registered

Not Registered

Not Registered

When you click on Start Diagnostics, checks are performed for RMC (checks specific to services,hardware, storage systems, backup systems, catalyst copy, element recovery technology, andremote appliances) and RMC-V (checks specific to vCenter configuration, RMC-V license instorage system, and RMV-related services). You can diagnose issues related to RMC or RMC-Vcomponents, and resolve the issues. However, if only RMC VM was installed without the vCenterplugin, the RMC-V checks are not performed and a warning is displayed. There are three possibleresults: Passed, Failed, and Warning.If the checks are either fail or warning, the following information is provided:1. Details—Cause of the failure.2. Resolution—Recommended action that will help you resolve the issue.Warnings do not affect RMC critical functions and can be ignored. For example, if the serviceset health of the backup systems is low, service set information like store, CoFC, and serviceset IP is displayed. This information is provided only to indicate that the health state is low.

Install/Upgrade complete summaryThe complete summary of the install or upgrade process is displayed on the Install/Upgradecomplete summary screen.


4 Working with vSphere Web ClientThis chapter explains how to log in to vSphere Web Client and view HPE 3PAR StoreServ orHPE Hyper Converged 250 storage information.

• 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 nonsecure 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.

Logging in to the vSphere Web Client1. If you are using Windows 2008—selectStart→All Programs→VMware→VMware vSphere

Web Client→vSphere Web Client.If you are using Windows 2012—select Start→Search→vSphere Web Client.If you are using a different system—Enter https://IP orhostname:9443/vsphere-client/ in the browser, where IP and hostname is for thevCenter.The VMware vSphere Web Client login screen appears.

Logging in to the vSphere Web Client 37

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 6 VMware vSphere Web Client home page

NOTE: If you have selected a language other than English during installation of theOperating System, the Recent Tasks displays:• the tasks and events generated from the RMC Appliance in English.

• the tasks and events generated from the vCenter Server in the language that youselected during installation.

3. Click Administration→HPE RMC Management→HPE RMC Configuration.The list of storage systems, backup systems, RMCs, and vCenter server associated withthe ESXi host are displayed.

NOTE: To remove an HPE StoreOnce, HPE 3PAR StoreServ, or HPE Hyper Converged 250storage system, you must remove the associated objects with remote RMC from the RMC/RMC-VGUI. The storage systems can then be permanently removed from the RMC/RMC-V GUI.When you create snapshots, backups, or RMC policies, references are made to the storagesystems. Hence, removing the storage systems from the RMC/RMC-V GUI dashboard is notallowed.

HPE RMC Configuration tabs• “RMC Appliances” (page 39)

• “Storage Systems” (page 43)

• “Backup Systems” (page 44)

• “vCenter Server” (page 45)

38 Working with vSphere Web Client

NOTE: When the HPE RMC appliance is down, the following error message is displayed:

RMC Appliances

CAUTION: After upgrading to RMC 3.0.0, to register RMC-V appliances, do not use theStoreOnce RMC Credentials page shown in the figure:

To register RMC-V appliances, you must use the HPE RMC Configuration tab under the HPERMC Configuration tab, as shown in the figure:

On the RMC Appliances tab, you can perform the following operations:• Register HPE RMC instances locally or remotely

If RMC-V plugin is installed using the installation wizard, RMC appliances are registered bydefault. Registering RMC appliances on this screen is required if you must perform thefollowing actions:

◦ Add an earlier deployed RMC standalone appliance to the RMC-V plugin.

◦ Change RMC Appliance IP and FQDN.

HPE RMC Configuration tabs 39

Local registration

To register HPE RMC instances locally, perform the following steps:1. Click the icon.2. Enter the IP/Host Name, User Name, and Password in the popup window that appears.

Click Save.The Refresh option is to update the latest appliance information on the page, while the WebClient is open for a long time and if RMC appliance properties have changed. For example,if RMC upgrade was done while the Web Client was open.The Sync option can be used if multiple RMC appliances are registered, when there is aconfiguration mismatch between the first RMC appliance (master) and other RMC appliances.


However, the sync option is not required when an additional RMC appliance is registered(local RMC ), because the RMC-V plugin synchrnoizes the configuration information withthe new RMC appliance.The Sync All option can be used if multiple RMC appliances are registered, to sync theconfiguration details between multiple RMC appliances. The configuration of the primaryRMC is added to all secondary RMCs, but the configuration details of secondary RMCs isnot added to the primary RMC.

Remote registration

To register HPE RMC instances remotely, click on the Show Remote RMC Configurationcheck box and perform the following steps:1. Click the icon.2. Enter the IP/Host Name, User Name, and Password in the popup window that appears.3. Select the array to be associated and click Save.


You cannot unregister Remote RMC appliances. However, the arrays associated with theremote RMC appliance can be disassociated. Arrays are disassociated when you associatethe arrays to other remote RMC appliances. You can see the remote RMC appliance on theUI, even if all arrays are disassociated from the appliance. This behavior does not impactthe working of the RMC appliance.

• View details of the RMC applianceTo view the details of an existing RMC appliance, click the RMC Host Name/IP field hyperlink. Details displayed are shown in the figure:

• Edit the registered HPE RMC instance

NOTE: If the registered HPE Hyper Converged node is down, see the HPE RMC UserGuide to edit the storage IP to a surviving node.

1. Select the IP/Host Name of the HPE RMC instance that you want to edit.2. Click the icon.3. Enter the new password in the popup window and click Save.

• Delete the registered HPE RMC instance1. Click the icon.2. Click Yes on the prompt that appears to proceed with the deletion.

• Unregister RMC-V plugin• Click the Unregister RMC-V plugin button.


Storage Systems

Figure 7 Storage Systems

On the Storage Systems tab, you can perform the following operations:

• Register either HPE StoreServ or HPE Hyper Converged 250 storage system

1. Click the icon.2. Select the storage type from the Storage Type drop-down.3. Enter the IP/Host Name, User Name, and Password in the popup window that appears.

Click Save.

• Edit the registered HPE storage system1. Select the IP/Host Name of the HPE storage system that you want to edit.2. Click the icon.3. Enter the new user name and password in the popup window and click Save.

• Delete the registered HPE storage system1. Click the icon.2. Click Yes on the prompt that appears to proceed with the deletion.

• Refresh the screen displaying the list of storage sytems• Click the icon.


Backup Systems

Figure 8 Backup Systems

On the Backup Systems tab, you can perform the following operations:

• Register HPE StoreOnce backup system

1. Click the icon.2. Enter the IP/Host Name, User Name, and Password in the popup window that appears.3. If the HPE RMC instance and HPE StoreOnce backup connectivity is remote or over

WAN link, select the Remote StoreOnce (WAN Enabled) check box.


4. Click Save.

• Edit the registered HPE StoreOnce backup system1. Select the IP/Host Name of the HPE StoreOnce backup system that you want to edit.2. Click the icon.3. Enter the new username and password in the popup window and click Save.4. If the HPE RMC instance and HPE StoreOnce backup connectivity is remote or over a

WAN link, select the Remote StoreOnce (WAN Enabled) check box.

• Delete the registered HPE StoreOnce backup system1. Click the icon.2. Click Yes on the prompt that appears to proceed with the deletion.

• Refresh the screen displaying the list of backup sytems• Click the icon.

vCenter Server

Figure 9 vCenter Server

IMPORTANT: The vCenter server is registered during RMC-V installation. You can use theAdd, Remove, and Modify options only when there is a change in the vCenter host (FQDN), IP,username, or password. Removing an existing vCenter Server results in all RMC-V operationsfailing, therefore ensure the vCenter is always available with accurate credentials. You cannothave more than one vCenter Server registered.

On the vCenter Server tab, you can perform the following operations:

• Register a vCenter Server1. Click the icon.2. Enter the IP/Host Name, User Name, and Password in the popup window that appears.3. Click Save.

• Edit the registered vCenter Server1. Select the IP/Host Name of the vCenter server that you want to edit.2. Click the icon.3. Enter the new password in the popup window and click Save.


• Delete the registered vCenter Server1. Click the icon.2. Click Yes on the prompt that appears to proceed with the deletion.

• Refresh the screen displaying the list of vCenter Servers• Click the icon, to see the latest information on the screen.


5 Working with Recovery Sets SnapshotsRecovery Set Snapshot is a snapshot collection of one or more virtual volumes that reside onthe HPE 3PAR StoreServ or HPE Hyper Converged 250 storage system, that is used to form aVMware datastore or VM. These snapshots are also called Virtual Copies in the HPE 3PARStoreServ and HPE Hyper Converged 250 systems. A Recovery Set contains application-specificmetadata and is registered as a custom object in Web Client that allows relationship buildingbetween the different VMware objects.RMC-V supports Recovery Set creation at both VM and datastore levels. Before creating RecoverySets, 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 HPE 3PAR virtual volume or HPE Hyper Converged 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 Tools is required in a VM to guarantee consistent and usable backup. VMwareTools must be installed on the guest VM when application consistency is required.

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

NOTE: If you make changes (adding or removing volumes) in the VM configuration of associateddatastores, the Snapshot backups created are full backups. However, subsequent backupsswitch back to incremental backups.

Recovery Sets tabThe Recovery Sets tab is available under Related Objects for VMs and datastores. When youselect a Recovery Set, all Recovery Set objects associated with the selected VM or datastoreare displayed.The Recovery Sets that belong to the vCenter Server are also available under Home→vCenterInventory Lists→HPE Infrastructure.

Actions menuActions menu supports the following actions:

• Cancel—Aborts the selected backup system or catalyst copy system.

• Delete—Removes the selected Recovery Set object.

• Restore—Restores the content of the base Volume with the selected Recovery Set. Thisoption 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 thechanges in vCenter or storage array inventory objects. When you select a Recovery Setobject from the list, the details pertaining to the object are displayed.For changes in the HPE 3PAR StoreServ or HPE Hyper Converged 250 storage system totake effect, perform the following steps:1. Log in to the RMC GUI (https://<IP_address> or <Host_name>).2. Click HPE Recovery Manager Central→Storage System→Action Menu.

47

3. Click Refresh and Yes, Refresh.

• Create Express Protect/Catalyst Copy Recovery Set—Creates Express Protect andCatalyst Copy of the Recovery Sets existing Express Protect/backup systems.

Getting Started tabDisplays information about Recovery Sets.

Monitor tabDisplays issues, performance, tasks, and events of Recovery Sets.

Summary tabDisplays the properties of the Recovery Set object.

Manage tabDisplays the list of Virtual Copies and VMDKs that are contained in the set, and allows you toperform mount, unmount, attach, detach, and copy VMDK operations.

Related Objects tabDisplays the objects that are related to the Recovery Set.

Prerequisites for working with Recovery Set Snapshots• Both source and target storage systems (HPE 3PAR StoreServ or HPE Hyper Converged

250) must be registered. However, while working on local Recovery Sets, registering targetstorage systems is not required.

• The datastore and VMs must be in accessible state. RMC-V operations cannot be performedon a VM when the VM or its datastore is in inaccessible state.

Creating default Recovery Set policyIf you are using multiple RMC instances, you must first create a default Recovery Set Policy andthen 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.4. Click the Related Objects tab and click Recovery Sets on the left navigation pane.5. To apply a set of policies, select a VM.6. ClickActions→All HPERecoveryManager Central Actions→Set Recovery Set Creation

Policy, and then click Snapshot.The Default Snapshot Policy Settings screen appears.

48 Working with Recovery Sets Snapshots

Figure 10 Default Snapshot Policy SettingsDatastore level

VM level

Creating default Recovery Set policy 49

• To modify the selected RMC instance, select the required RMC instance from the SelectRMC Host Name list.

• After selecting a different RMC instance, it must have a new default policy created. Thesystem does not consider the old snapshots that are created through the first RMCinstance.

• However, snapshots of both the first and the second RMC instances are displayed.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.

Numeric policy set for one RMC instance does not apply to other RMC instance to whichyou move the VM object. Each RMC instance has its own numeric policy.

• While creating recovery sets, select the VSS-aware application consistency checkbox.


NOTE: If Expiration/Retention is selected for Recovery Set (snapshot) and the expirationtime given is less than the next Express Protect backup, the previous snapshot is deleteddue to expiry. In this case, RMC cannot perform incremental backups.

7. You can specify the following details in the Default Snapshot Policy Settings screen IfExpiration /Retention is selected:

Figure 11 Default Snapshot Policy Settings

a. Select an appropriate RMC instance for the selected VM.

NOTE: All RMC instances registered with the vCenter Server are listed in thedrop-down list.

b. Specify the maximum number of Recovery Sets.The maximum number of Recovery Sets that you can specify to create a numeric policyis 500. The maximum number of snapshots supported is 30 for a VVOL numeric policyand 32 for a Hyper Converged 250.


NOTE: Based on the order in which the Recovery Sets are created, the nonexpirableRecovery Sets are deleted when they reach a position in the queue that exceeds theset count.

c. To remove the Recovery Sets according to a specified schedule, selectExpiration/Retention. Maximum count does not affect the removal of Recovery Sets.

NOTE: The Expiration/Retention option is not available for VVOL VMs and HyperCoverged VMs. Therefore, you can create only numeric policies for VVOL VMs.

If you select Enable expirable Recovery Sets, then in Expire after you must specifythe time duration in hours or days from the current time that the Recovery Sets expires.The maximum expiry period that you can specify for Recovery Set expiry is 43800 hoursor 1825 days.

NOTE: Expirable Recovery Sets are not included in the maximum count.

If you enable expirable Recovery Sets, you must specify how the existing nonexpirablecopies are handled.

• Keep non-expirable Recovery Sets—This option is default.

• Phase out non-expirable Recovery Sets (Advanced)—Select this option if youwant to create expirable Recovery Sets to phase out the older nonexpirableRecovery Sets. Therefore, whenever a new expirable Recovery Set is created, theoldest nonexpirable copy is deleted.

d. Select Retain Recovery Set.i. Specify the Retention period.ii. Select Hours or Days.

NOTE:• Setting the retention policy requires the HPE 3PAR Virtual Lock license on the

HPE 3PAR StoreServ storage system. RMC-V checks for an existing HPE3PAR Virtual Lock license on the Storage System when a Recovery Set iscreated with retention specified.

• The maximum retention period for Recovery Sets is 43,800 hours or 1,825days.

• The expiry value must be equal to or greater than the retention value, whenusing both the expiry and retention options.


e. To ensure application consistency, select Create Recovery Set with VSS-awareapplication consistency. This option is used to create snapshots of Recovery Setsthat adhere to data format standards used by the VMware tools. You can also selectthis option if you are using pre- or post freeze scripts with other operating systems thathave vmware-tools installed on the guest VM (LINUX).

CAUTION: After installing or upgrading VMware Tools, you must reboot thecorresponding VM. If you do not reboot, the application consistent snapshots are takenas crash consistent and are reported as successful. The same behavior can be seen ifthe VMware Tools is not upgraded on the VM, after an upgrade of the ESXi server.

NOTE:• If you add a VM to a datastore, update the datastore policy (enable the VM for

Application Consistency) to ensure VM application consistency.• If you add a VM or a datastore, clickActions→Update Recovery Manager Cache

to refresh the Recovery Manager cache.

8. To enable email notifications, select the Enable Email Notification check box. For moreinformation, see “Creating Email Notification Policies” (page 69).

9. Click Save.10. The Default Snapshot Policy Settings dialog box appears. This dialog box appears only

in a multi-RMC scenario.To save the default policy, click Yes.

IMPORTANT: When you change the affinity from one RMC instance to the other, anadvisory message is displayed indicating that all schedules from the earlier RMC instancefor that VM or datastore to be deleted.Every time you select a different RMC instance from the Select RMCHost Name drop-downlist, this dialog box appears.

11. Click OK.

NOTE: You can perform the same procedure to create Recovery Set policies on datastores.


Creating Recovery SetsRecovery Set is a set of virtual volumes that reside on the HPE 3PAR StoreServ or HPE HyperConverged 250 storage system. RMC-V supports Recovery Set creation at both VM and datastorelevels. Before creating Recovery Sets, ensure that the following conditions are met:

• Creating a Recovery Set at the VM level requires sufficient free space on the datastorewhere 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 participatingin disk sharing, such as Microsoft MSCS, is not a supported VMFS limitation.

• RMC-V supports only one virtual volume per datastore.

NOTE: Snapshot space must be available on the HPE 3PAR virtual volume. To create aRecovery Set on an HPE 3PAR base volume, the volume must have snapshot space allocatedduring its creation. The same applies for HPE Hyper Converged 250 volumes.

To create a Recovery Set on the VM:1. Navigate to the home page and click VMs and Templates.2. Click the VM for which the Recovery Set is to be created.


3. Right-click the VM and then click All HPE Recovery Manager Central Actions→CreateRecovery Set→Snapshot. The Create Recovery Set page appears.

Figure 12 Create Recovery SetsDatastore level

VM level

Creating Recovery Sets 55

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 time stamp identifies the set name.• The Recovery Set name preferably must not exceed 32 characters.

c. You can 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 VSS-aware application consistency—To createVSS-aware application consistent snapshots.

• Force create if known VMware error occurs while IO quiescence—To forcecreate Recovery Sets if known IO errors exist.

4. Click Create.

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.• To create Recovery Sets at a datastore level, perform the same steps.

Viewing Recovery Set informationThis 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.4. Click the Related Objects tab and click Recovery Sets in the left navigation pane.5. Go to Manage tab.


6. To view the details, double-click a Recovery Set and click the Manage tab.

Figure 13 Recovery Set information

The following information about the selected Recovery Set is displayed:

• Base datastore/RDM LUN.

• Type.

• Base volume.

• Snapshot volume.

• Status—Available or Mounted.

NOTE: If the status of a Recovery Set is mismatched, the Recovery Set is createdon a different Storage System instead of its current connected system. The HPE 3PARPeer Motion operation might have caused the mismatch. The delete operation is allowedto remove the record. Manually remove the actual Recovery Set from the originatingStorage System.

• Expiration

• Retention

• Exported Host

• ESXi Host

• Snapshot datastore

NOTE:To view the Recovery Set information on a datastore, perform a similar procedure.• 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 timezone of the RMC Appliance.

• If the virtual volumes that are used are in a Peer Persistent configuration, the localRecovery Set creation is disabled.

Viewing Recovery Set information 57

• Do not delete snapshots from a snapshot set using HP 3PAR Management Console.If you delete a snapshot, the snapshot is displayed in the Manage tab of the vSphereWeb Client. However, you cannot perform any RMC-V tasks on such snapshots. Youcan only delete this snapshot.

Viewing Virtual Disk detailsClick 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 associatedwith the VMDK. For snapshots created earlier than version 2.3, system displays N/A.

• VSS-aware Application Consistent—Provides information if this VMDK is applicationconsistent.

• VM Attached—Displays if the VM is attached.

Viewing Recovery Set event logsRecovery Sets operation event logs lists the events and other event relevant details. To viewevent logs, Go to Hosts and Clusters→Monitor→Events. You can filter and view the followinginformation:• Description

• Type

• Date Time

• Task

• Target

• UserThe system displays the Event Type ID of the selected event.


Figure 14 Viewing the Recovery Set event logs

Mounting Recovery Sets1. Navigate to the vSphere Web Client home page.2. Click VMs and Templates.3. Select a VM.4. Click the Related Objects tab and click Recovery Sets in the left navigation pane. The

system displays all Recovery Sets in the Recovery Sets tab. Double-click a Recovery Setto view the Manage tab.

Mounting Recovery Sets 59

5. Select the Recovery Set to mount from the Recovery Sets list, and click Mount/Unmount.6. 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 thevCenter Server that share access to the HPE 3PAR StoreServ or HPE Hyper Converged250 storage system.

• Mount on Proxy Host—Select from a list of hosts the vCenter Server does not manage,but which have access to the HPE 3PAR StoreServ or HPE Hyper Converged 250storage system.

7. Click Mount.The Mount Local Recovery Set — Confirm dialog box appears.

8. To mount the Recovery Set, click Yes.After the Recovery Set is successfully mounted, the status of the Recovery Set is displayedas Mounted. The system also displays appropriate values in the following columns:• Exported Host

• LUN ID

• Snapshot datastore

NOTE: To mount Recovery Sets on a datastore, you can perform a similar procedure.For the mount operation to succeed:• FC HBA WWNs or iSCSI Initiator must be enabled and online in the ESXi server.

• The host entry containing these WWNs or IQNs must be created on the storage system.

• Mount, unmount, attach, and detach tasks are not supported on VVOLs.

Unmounting Recovery Sets

CAUTION: RMC-V does not verify that the volume you unmount is active or inactive. Therefore,ensure the volume 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.4. Click the Related Objects tab and click Recovery Sets in the left navigation pane.

The system displays all Recovery Sets in Related Objects→Recovery Sets.5. Select the Recovery Set to unmount from the list of Recovery Sets.6. Double-click a Recovery Set to view the Manage tab.7. Click Unmount.

Attaching virtual machine disksYou can attach a Recovery Set to a VM only if the Recovery Set is already mounted. To attacha Recovery Set:1. Navigate to the vSphere Web Client home page.2. Click VMs and Templates.3. Select a VM from the left pane and click Recovery Sets on the right pane. The system

displays Recovery Sets in the Recovery Sets tab under Related Objects. Double-click aRecovery Set to view the Manage tab.


4. Select a mounted Recovery Set to attach to a VM.5. Select a virtual disk and click Copy/Attach/Detach.

The Copy/Attach window appears.

Figure 15 Copy to Datastore

Attaching virtual machine disks 61

6. Select one of the following options:• Copy to Datastore—Select the datastore to copy the associated VMDK of the Recovery

Set.• Attach to Virtual Machine—Select the VM to attach the selected Recovery Set.a. To copy the VMDK file:

i. Select Copy to datastore.The associated datastore of mounted ESXi is displayed.

ii. Select an appropriate target datastore with required space available, to which youwant to copy the Recovery Set.

iii. To overwrite the VMDK file, select Overwrite existing Virtual Disk.iv. Click Copy.v. Click Yes when you are prompted for confirmation.

The VMDK of the virtual machine is successfully copied to the datastore.

NOTE: After performing copy VMDK operation once on the mounted snapshotcontaining VMFS snapshots associated with it, if you attempt to perform copy or attachVMDK once again in the same mounted state then it fails with the error Filexxxxx.vmdk was not found. For performing copy or attach VMDK operation thesecond time, the snapshot has to be unmounted and remounted.

b. To attach the Recovery Set to a VM:

Figure 16 Attach to Virtual Machine

i. Select Attach to Virtual Machine.All VMs associated with the mounted ESXi host are displayed.

ii. Select an appropriate VM to which you want to attach the VMDK.iii. To attach the VMDK, click Attach.iv. Click Yes when you are prompted for confirmation.

The Recovery Set is successfully attached to the VM.

NOTE: The same steps apply to attaching VMDKs at datastore level.


Detaching virtual machine disksYou can detach a Recovery Set that is attached to a VM.1. Navigate to the vSphere Web Client home page.2. Click VMs and Templates.3. Select a VM on the left pane and click Recovery Sets on the right pane. The system displays

the Recovery Sets in the Recovery Sets tab under Related Objects tab.4. Select the Recovery Set to detach from the list of Recovery Sets. Double-click a Recovery

Set to view the Manage tab.5. Select the attached virtual disk and then click Copy/Attach/Detach.6. Click Detach when you are prompted for confirmation.

NOTE: The same steps apply to detaching VMDKs at datastore level.

Restoring Virtual MachinesNormal restore scenarios involve restoring VMDKs. In a VMFS datastore, there can be manyvirtual disks. Typically, you can identify the virtual disk to be restored and copy it over the oldvirtual disk. However, in some cases, the virtual machine file system gets corrupted after allvirtual disks are replaced. In such scenarios, restore one of the Recovery Sets to a base volume.The 3PAR Operating System Software supports a nondisruptive virtual volume conversion froma fully to thinly provisioned or thinly to fully provisioned virtual volume. RMC-V limits the restorationof a Recovery Set taken before a virtual volume conversion. If the action occurs, the followingerror message is displayed:

Performing any RMC-V Recovery Set operations such as creating or deletingmust only occur after a Virtual Volume conversion is completed.

NOTE: After a virtual volume conversion is complete, click Actions→Update RecoveryManager Cache to see the changes. The RMC Appliance does not notify the RMC-V plugin forany backend data changes, until you 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 datastore view because you can restore only datastoreRecovery Sets.

2. Select the Recovery Set 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 therequest 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 Machines1. Navigate to the vSphere Web Client home page and click VMs and Templates.2. Click the VVOL VM to restore.

Detaching virtual machine disks 63

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 HPE Recovery Manager Central Actions→Update

Recovery Manager Cache.6. Right-click a Recovery Set and click Restore.

The Restore Virtual Machine to Recovery Set window appears:

Figure 17 Restore Virtual Machine to Recovery Set

7. Click Yes to restore.

Deleting Recovery Sets1. Navigate to the vSphere Web Client home page.2. Click Hosts and Clusters.3. Select a VM and click Recovery Sets in the left navigation pane. The system displays all

the available Recovery Sets in the Recovery Sets tab under the Related Objects tab.4. Select the Recovery Set 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.

6. To confirm deletion of the selected Recovery Set, click Yes.

NOTE:• If a Recovery Set is also a smartclone point, you must first delete all Recovery Sets except

for the Recovery Set the smartclone is dependent on.• If the Mount operation is in progress, then Snapshot cannot be deleted.

• If the Snapshot is Mounted/Attached the delete operation fails.

• If you select more than one Recovery Set Snapshots for deletion, the delete confirmationmessage is displayed.

• To delete Recovery Sets on a datastore, perform the same procedure: “Deleting RecoverySets” (page 64).

Viewing Recovery Sets1. Navigate to the vSphere Web Client home page.2. Click Hosts and Clusters.3. Select a VM.


4. Click the Related Objects tab and click the Recovery Sets tab in the right navigation pane.

Figure 18 Recovery Sets

Scheduling Recovery Sets• Viewing a schedule list

• Add—Adding a schedule

• Edit—Editing a schedule

• Delete—Deleting a schedule

• Refresh—Refreshing a schedule list

• Close—Closing the Schedule List window

Viewing a schedule list1. Navigate to the vSphere Web Client home page.2. Click Hosts and Clusters.3. Click Virtual Machine.4. To create a schedule, select a Virtual Machine in the right pane.5. Click Actions→All HPE Recovery Manager Central Actions→Schedule Recovery Set

Creation.The Schedule List for the VM that you have selected appears.

This window lists all tasks that are currently scheduled for a Recovery Set. From theScheduled List window, you can add a schedule, modify an existing schedule, or delete aschedule.

6. To close the Scheduled List window, click Close.

Scheduling Recovery Sets 65

NOTE: The Schedule List window lists the schedules only for the selected VM or datastore.

You can automatically create Recovery Sets according to a specified schedule.

Creating schedules for Recovery Set1. Navigate to Schedule List.

NOTE: For information on navigating to the Schedule List, see “Viewing a schedule list”.

2. Click Add to create Recovery Sets according to a specified schedule.The Welcome screen of the Create Schedule Task Wizard window appears.

3. Click Next. The Recovery Set Type window appears with the following options:• Snapshot—Schedule creation of a snapshot for a virtual machine or datastore.

• Express Protect—Schedule Express Protect of a snapshot for a virtual machine ordatastore.


4. Click Next. The Schedule window appears.a. Specify a task name for the schedule in Schedule task name.b. To create a Recovery Set, select the task frequency from Perform Recovery Set

creation task. The following frequencies are listed:i. By minutes

The minutes option is available only for scheduling Snapshots. Minutes option isnot available for scheduling Express Protects.

NOTE: HPE recommends that you maintain a minimum of 30 minutes betweentwo snapshot schedules.

ii. Hourlyiii. Dailyiv. 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 RecoverySet creation task. The following table lists the frequency details:

DescriptionsFrequency detailsFrequency

You can specify the schedule start time in minutes.Start timeBy minutes

Specify the frequency of the scheduled task.Recur Every

You can specify the schedule start time in hours andminutes. Also, select AM or PM.

Start timeDaily



Start timeHourly



Start timeMonthly

To start the scheduled task, specify the day of everymonth.

Day

Select the date on which you want to schedule theSnapshot/Express Protect.

Start dateOne time only


Start time


Start timeWeekly

All seven days of a week are displayed. You canselect one or more days to schedule the weeklySnapshot/Express Protect.

Select days of a week.

Scheduling Recovery Sets 67

5. Click Next. The Recovery Set Type window appears with the following options:• Snapshot—Select to create a schedule for a virtual machine or datastore. By default,

this option is selected.• Express Protect—Select to create a schedule to take snapshot of a virtual machine

or datastore from HPE 3PAR StoreServ or HPE Hyper Converged 250 storage systemto backup the snapshot to the HPE StoreOnce backup system.

6. Click Next. The Snapshot Configuration window appears.

1. To create application consistent Recovery Sets, select Create Recovery Set withVSS-aware application consistency.

2. (This screen appears only for datastore level schedules)


Select one of the following options:• To apply the schedule to all 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

Machines, and then select the required Virtual Machines.

NOTE: Overwrite default policy setting is disabled for numeric policies. ForExpiration/Retention policies, this option is enabled. You can modify the values for SetRecovery 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. To complete the task schedule, click Finish.The Schedule Modification window appears.

9. To schedule the task, click Yes.

NOTE: If objects (VMs, Datastores, or RCgroups) are deleted or modified after schedulecreation, you must update the corresponding schedule to reflect the change. To troubleshoot,see “Failed to create array snapshot” (page 160).

Editing schedules1. Navigate to the Schedule List.


2. Select the schedule 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” (page65).


6. To complete the task schedule, click Finish.The Schedule Modification window appears.

7. To confirm changes made to the schedule, click Yes.

Removing schedules1. Navigate to the Schedule List.


2. Select schedule and click Delete.3. Click Yes to confirm deletion of the schedule.

Creating Email Notification PoliciesEmail notifications can be enabled when creating Snapshot, Express Protect, or Catalyst Copypolicies. You can receive notifications either to your mailbox or to another mail ID of your choice,when create, delete, or restore operation is performed. Also, you can choose to receivenotifications either only for error, or generic information, or both.

Editing schedules 69

To navigate to the Create Email Notification Policy page:1. Right-click a VM and select Set Recovery Set Creation Policy.2. Click either on a Snapshot or an Express Protect.

The Default Snapshot Policy Setting or Default Express Protect/Catalyst Copy PolicySetting window appears.

3. Select the Create Email Notification check box.

1. To add a notification, specify the following details:

DescriptionField name

RMC-V type email notification policy. This field is a uniquevalue.

Email Policy Name

Server that is used to send/receive mails.Mail Server

Port that is configured for the mail server.Mail Port

Email address of the user.Sender Email Address

Password for email notification. Applicable only if youselect SSL.

Password

Enable to authenticate password. Emails are SSL/TLSencrypted.

SSL

By default, the Timeout duration is set to 60 seconds .You can increase the timeout duration on a need basis.

Timeout

Specify the recipient email address, multiple emailaddresses are separated by a comma.

Receiver Email Address

2. To test the configuration, click Test Email Configuration.


3. Select Info or Error or both for the following:• Snapshot

• Express Protect / Catalyst Copy4. Click Create.

Updating Recovery Manager CacheIf you change HPE 3PAR StoreServ or HPE Hyper Converged 250 storage system, update theRecovery Manager cache. Otherwise, RMC-V operations fail with an error message Performa cache refresh.To update the Recovery Manager cache:1. Navigate to the vSphere Web Client home page.2. Click Hosts and Clusters.3. Right-click on a VM.4. To update the Recovery Manager Cache, click All HPE Recovery Manager

Actions→Update Recovery Manager Cache.

Auto cache refreshThe Recovery Manager cache update is now automated. The frequency of auto updates is dailyand cannot be changed. Start Time, Description, and Schedule Name can be changed. For moreinformation on changing the scheduled auto refresh settings, see the scheduler section in theRMC user guide. An example of the RMC-V Auto Cache Refresh on the RMC GUI is shown inthe figure:

To edit the RMC-V Auto Cache Refresh schedule in the RMC GUI:1. Go to the Schedules page.2. Select RMC-V Auto Cache Refresh.

Updating Recovery Manager Cache 71

NOTE:• After upgrading to RMC-V 3.0.0, to enable Auto Cache refresh, remove, and re-add the

vCenter server.• The Type box is disabled for RMC-V Auto Cache Refresh.


6 Working with Remote Recovery Sets ConfigurationsHPE 3PAR Remote Copy Software provides RMC-V the capability to copy virtual volumes fromprotected site to recovery site. The Remote Recovery Configuration feature allows you to createand manage Synchronous, Periodic, or Synchronous Long-Distance Remote Recovery Sets atHPE 3PAR Remote Copy group level.RMC-V supports the following Remote Copy configurations:

• One-to-One

• Synchronous Long DistanceHPE 3PAR Remote Copy solution replicates data from one site (or storage system) to anothersite (or storage system), thus protecting data if there is disaster or failure of a storage system.RMC helps you to either recover data or restore data at either site.RMC-V supports HPE 3PAR Peer Persistence. When virtual volumes use Peer Persistence, itallows creation of remote Virtual Copies on Remote Recovery Configurations. Therefore, whenan active path fails over to a different Storage system, the virtual copies become available oneither of the Storage Systems for restoration. For more information on establishing a PeerPersistent setup, see the HPE 3PAR Remote Copy User Guide.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.

• The Remote Recovery Configurations node that displays the Remote Recovery Sets isremoved from Home→HPE Infrastructure.

Working with Remote Copy GroupsRemote Recovery Configuration is a collection of replication groups that contain virtual volumesthat are exposed to the ESXi hosts managed in a vCenter Server. These replication groups arecalled Remote Copy Groups in the HPE 3PAR StoreServ storgae systems. HPE 3PAR RemoteCopy feature provides enterprise and cloud data centers with autonomic replication and disasterrecovery technology that allows protection and sharing of data between multiple arrays withinthe same or different geographical locations.If a Remote Copy Group is set up for the virtual volumes used by the ESXi hosts, RMC-V allowsyou to take advantage of the Remote Copy Group by taking snapshots on local, remote, or bothstorage systems using Remote Copy group as an entity for operation.After a Recovery Set is created, you can mount individual virtual copy to a specific ESXi hostthat resides on the local storage system. You can then attach the mounted volume to a selectedVirtual Machine as additional disk for a file-level restore.

Remote Recovery Configurations tabRemote Recovery Configuration tab is available under Related Objects for Virtual Machinesand datastores.

Working with Remote Copy Groups 73

The following tabs are displayed when you double-click the Remote Copy Group:

• Recovery Sets on Source StoreServ• Recovery Sets on Target StoreServ• Virtual Volumes• Datastore• Virtual Machine

Action MenuTable 4 (page 74) lists the tasks that you can perform from the Action menu.

Table 4 Action menu items

DescriptionTask

Creates a Remote Recovery Set for a selected Remote Copy Group.Create Remote Recovery Set

Sets the default policy. You can override this using the Creation wizard.Set Remote Recovery SetCreation Policy

Manages creation of Remote Recovery Sets using a schedule.Schedule Remote Recovery SetCreation

Refreshes the current server cache memory to reflect the changes in vCenterServer or storage system inventory objects.

Update RecoveryManager Cache

When you double-click a Remote Copy Group from the list, details pertaining to the selectedobject are available on the following tabs:

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

Prerequisites to configure Remote Copy Group• All virtual volumes in the Remote Copy group must be exported to ESXi host.

• At least one of the first twenty characters of all virtual volume names in a SynchronousRemote Copy group must be unique.

• The Remote Copy group must be in Started state and all virtual volumes must be in Syncedstate.For information on creating Remote Copy groups, see the HPE 3PARRemote Copy SoftwareUser Guide.

• All Virtual Machines involved in the operation must contain virtual volumes from same RemoteCopy groups.

• If you need application consistent Snapshots, install VMware Tools in the Virtual Machineto 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 sameESXi host.

WorkflowTable 5 (page 75) lists the tasks that you must perform to configure and use the Remote RecoverySets feature.

74 Working with Remote Recovery Sets Configurations

Table 5 Workflow — Remote Recovery Set Configuration

Additional notes and referencesActionStepno.

If a vCenter Server is already installed, you can ignore this step.Install a vCenter Server (for example,vCenter1).

1Ensure that you have an ESXi Host that the vCenter Server manages.

It is optional to have a secondary vCenter Server. During disasters,secondary vCenter Server can be used for disaster recovery solutions.

Install secondary vCenter Server (forexample, vCenter2).

1a

For more information and illustrations, see “RMC Remote CopyConfigurations Topologies” (page 76).

For information on logging in and performing various tasks using theWeb Client, see “Working with vSphere Web Client” (page 37).

Log in to the Web Client and performthe following tasks:

2

For information on installing RMC instances, see “Installing HPERMC-V” (page 16).

• Deploy an RMC Appliance.

• Register the Remote RMCAppliance.You can also register a local RMCas remote.

For information on Registering Remote RMC Appliances, see “RMCAppliances” (page 39).

You can configure the Remote Copy Configuration in the followingways:

Create Remote Copy Groups on HPE3PAR StoreServ Storage system, ifthe groups are not already created.

3

• Synchronous

• Asynchronous Periodic

• Synchronous Long Distance

For information on setting up a Remote Copy Configuration, see the3PAR Remote Copy Software User Guide.For information on the Remote Copy Configurations supported byRMC-V, see “RMC Remote Copy Configurations Topologies” (page76).

Present the virtual volumes from thePrimary StoreServ to the ESXi Host.

4 • The virtual volumes appear in the Remote Copy Group only afterpresenting to the ESXi server and creating a datastore of thesource LUN.

• For the RC Groups to appear:

◦ Update Recovery Manager Cache

◦ Refresh the vCenter

• For information on presenting the virtual volumes, see the HP3PAR Management Console User Guide.

• If a secondary vCenter Server is configured, you must exportvolumes from the secondary HPE 3PAR StoreServ to thesecondary ESXi host.

To verify that all Remote Copy groups are displayed.Click Remote RecoveryConfigurations tab.

5

Remote Recovery Set tasks6

For more information, see “Creating policies” (page 82).Creating Policies6.1

For more information, see “Creating Remote Recovery Sets” (page84).

Creating Remote Recovery Sets6.2

Workflow 75

Table 5 Workflow — Remote Recovery Set Configuration (continued)

Additional notes and referencesActionStepno.

For more information, see “Managing Remote Recovery Setsschedules” (page 87).

Managing schedules for RemoteRecovery Sets

6.3

• Add new schedules

• Edit schedules

• Delete schedules

For more information, see “Managing Remote Recovery Sets” (page90).

Managing Remote Recovery Sets6.4

• Mounting Remote Recovery Sets

• Unmounting Remote RecoverySets

• Attaching Remote Recovery Sets

• Detaching Remote Recovery Sets

For more information, see “Deleting Remote Recovery Sets” (page97).

Deleting Remote Recovery Sets6.5

RMC Remote Copy Configurations TopologiesRemote Copy Configuration—Single-site RMC ApplianceFigure 19 (page 76) illustrates configuring Remote Copy with a single-site RMC Appliance.

Figure 19 Remote Copy Configuration—Single-site RMC Appliance

RMC1

vCenter Server

TCP/IP Network

Synchronous/Asynchronous Periodic

RMC-V Plugin(RMC-V GUI

PrimarySystem

SecondarySystem

For a Remote Copy configuration with a single RMC appliance and a single vCenter Server, thesame RMC appliance must be registered for both primary and remote arrays. For example, RMC1must be registered for Primary StoreServ and Secondary StoreServ.For information on installing RMC Appliances, see “Installing HPE RMC-V” (page 16).To configure RMC Appliances for Remote Copy Configuration—Single-site RMC Appliance, see“RMC Appliances” (page 39).


Remote Copy Configuration—Multisite RMC AppliancesFigure 20 (page 77) illustrates configuring Remote Copy with multisite RMC Appliances.

Figure 20 Remote Copy Configuration—Multisite RMC Appliances

RMC1

vCenter Server 1


TCP/IP Network


PrimarySystem

RMC2

vCenter Server 2


SecondarySystem

You can configure two different RMC instances with different vCenter Servers at the local andremote locations. For example, RMC1 is registered with vCenter Server1; and RMC2 isregistered with vCenter Server2.

NOTE:• You can register RMC instances to a vCenter from the RMC Credentials tab.

• For information on deploying RMC Appliances, see “Installing HPE RMC-V” (page 16).

• To configure RMC Appliances for Remote Copy configurations—Single-site RMC Appliance,see “RMC Appliances” (page 39).

In Figure 20 (page 77), RMC2 is remote with associated arrays of primary and secondary systems.In Figure 21 (page 78), RMC1 is remote with associated arrays of primary and secondary systems.From the HPE RMC Configuration tab, you can register RMC Appliances for the respectiveHPE 3PAR StoreServ storage systems in each vCenter server.For example, you can register RMC2 for Secondary StoreServ in vCenter server1.

RMC Remote Copy Configurations Topologies 77

Figure 21 Remote Copy Configuration—Multisite RMC Appliances

RMC1

vCenter Server 1


TCP/IP Network


PrimarySystem

RMC2

SecondarySystem

RMC1 for Primary StoreServ and RMC2 for Secondary StoreServ in vCenter Server1(RMC Configurations).

Remote Copy Configuration—Synchronous Long DistanceRemote Copy Configuration—Synchronous Long-Distance setup can be configured in one ofthe following ways:• Single RMC Appliance for both Secondary Sites

• Separate RMC Appliances for each Secondary StoreServ deviceFigure 22 (page 79) illustrates configuring Remote Copy in Synchronous Long Distance (SLD).


Figure 22 Remote Copy Configuration—Synchronous Long Distance

RMC1

vCenter Server 1

Synchronous Mode


PrimarySystem

RMC2

vCenter Server 2


RMC3

vCenter Server 3

AsynchronousPeriodic Mode


SecondarySystem

Standby Link

Secondary System

For SLD configurations, you can configure three RMC Appliances and three vCenter Servers.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,where array2 and array3 are secondary systems.

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 array3to 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 toRMC3.

• On the Secondary Site (vCenter2), you must set the target array1 to RMC1 and array2to RMC2.

• On the Tertiary Site (vCenter3), you must set the target array1 to RMC1 and array2 toRMC2.

For information on installing RMC Appliances, see “Installing HPE RMC-V” (page 16).

RMC Remote Copy Configurations Topologies 79

To configure RMC Appliances for Remote Copy Configuration—Single-site RMC Appliance, see“RMC Appliances” (page 39).

Viewing Remote Recovery configurations1. 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 23 Remote Copy groups mapped to the ESXi Server

NOTE: If changes are made in Remote Recovery Configurations, you must perform“Updating Recovery Manager Cache” (page 71) and vCenter refresh. Otherwise, the RemoteRecovery Sets might not be listed.

Viewing Remote Recovery Configuration information detailsTo view the details of the source or target HPE 3PAR StoreServ Storage systems:1. Navigate to the Remote Recovery Configurations page.


2. To view the summary of the selected storage system, select a Remote Recovery Configurationand click the Summary in the detail pane.

Figure 24 Remote Recovery Configuration details

NOTE: If Peer Persistent is enabled, the local Recovery Sets are disabled becauseRecovery Set snapshots are taken both locally and remotely using Recovery Set creation.

Viewing Remote Recovery configurations 81

3. The Summary page displays the following details:

Table 6 Remote Recovery Configuration information summary

ValueField name

Name of the Remote Copy group.Source name

Name of the source HPE 3PAR StoreServ Storage.Source StoreServ

Displays one of the following roles for the HPE 3PARStoreServ:

Role

• Primary—The role of source HPE 3PAR StoreServStorage is always primary.

• Secondary—The role of target HPE 3PAR StoreServStorage is always secondary.

Remote Copy group name that gets created on thetarget 3PAR StoreServ Storage.

StoreServ

Name of the target Remote Copy group.Target Name

Host name or IP address of the Remote RMCappliance.

RMC host

Indicates if Peer persistence is enabled or disabled forthe virtual volumes.

Peer persistence

Displays appropriate values to indicate one of thefollowing modes:

Mode

• Sync—For synchronous mode

• Periodic—For asynchronous periodic mode

Displays one of the following statuses:Status• Started

• Stopped

• Syncing

Displays one of the following connectivity modes:Link type• FC

• iSCSI

Creating policiesBased on the local Recovery Sets, you can create expiry or retention policies for each RemoteRecovery Set. When you create a policy for the source Remote Copy Group, a similar policycreated 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.

TheHPERecoveryManager Central Recovery Set Management Policywindow appears.

TIP: You can also right-click a Remote Recovery Configuration listed in the left pane andclick Set Remote Recovery Set Creation Policy to open the HPE Recovery ManagerCentral Recovery Set Management Policy window.


Figure 25 HP StoreOnce Recovery Manager Central Recovery Set Management Policy

4. For Synchronous Long-Distance Remote Recovery Sets, the Target StoreServ box is adropdown, since there can be two target StoreServs. However, for Sync and Periodic RemoteRecovery Sets, there can be only one target StoreServ.

5. The IP address of the RMC appliance that was added first is displayed.6. To create a numeric policy, selectNumeric and specify theMaximumnumber of Recovery

Sets.

CAUTION: Based on the order in which the Recovery Sets are created, the nonexpirableRecovery Sets are deleted when they reach a position in the queue that exceeds the setcount.

7. 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 13.8. To create an expiration policy, select Enable expirable Recovery Sets.9. Select days or hours from the drop-down menu.10. Specify the expiration period in Expire after and select days or hours.

NOTE: The maximum period that you can specify for Recovery Set expiry is 43800 hoursor 1825 days.

Creating policies 83

11. If you enable expirable Recovery Sets, you can also specify how to handle the existingnonexpirable copies by selecting one of the following options:• Keep nonexpirable Recovery Sets—Select this option if you want to retain the existing

non-expirable Recovery Sets along with the new expirable Recovery Sets.• Phase out nonexpirable Recovery Sets (Advanced)—Select to create expirable

Recovery Sets to phase out the older nonexpirable Recovery Sets.

NOTE: When a newer expirable Recovery Set is created, the oldest nonexpirablecopy is deleted. However, you can still create nonexpirable Recovery Sets as long asthe aggregate count is less than the policy maximum.

12. Select Retain Recovery Set to retain the Recovery Sets.13. Specify the Retention period.14. Select days or hours.

NOTE:• Setting the retention policy requires the HPE 3PAR Virtual Lock license on the HPE

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 equalto or greater than the retention value.

15. SelectCreate Recovery Set with VSS-aware application consistency to ensure applicationconsistency. This option is used to create snapshots of Recovery Sets that adhere to dataformat standards used by VMware Tools.

CAUTION: After installing or upgrading VMware Tools, you must reboot the correspondingVM. If you do not reboot, the application consistent snapshots are taken as crash consistentand are reported as successful. The same behavior can be seen if the VMware Tool is notupgraded on the VM, after an upgrade of the ESXi server.

NOTE:• If you add a VM to a datastore, update the policy to ensure VM application consistency.

• If you add a VM or a datastore, click Actions→Update Recovery Manager Cache torefresh the Recovery Manager cache.

16. Click Save.An alert message appears indicating that the new policy is saved.

17. Click OK.

Creating Remote Recovery SetsYou can create Remote Recovery Sets for Remote Recovery Configurations associated with aspecific 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 localand remote arrays. For Periodic Remote Recovery Sets, only a Remote Recovery Set is createdon the remote array.For Periodic Remote Recovery sets, both local and Remote Recovery Sets are created. However,HPE 3PAR StoreServ Storage system keeps only the latest Recovery Set on the HPE 3PARStoreServ Storage system at the local site. Therefore, at any given point only one snapshot isavailable on the primary storage system unless retention policy is used.


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 hosted by a volume that does not belong to the RemoteCopy group, then that volume will not be considered during Remote Recovery Set creation.

• HPE 3PAR StoreServ has only the latest snapshot at the primary site. Therefore, aftercreating a Remote Recovery set for a periodic group, HPE recommends that you updatethe 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 26 Creating Remote Recovery Sets

NOTE: If a failure, be sure that all storage systems are back in operation and the groupsare in Started state for the Remote Recovery Set to be successfully created. However,you can also create a Recovery Set locally without Remote Copy.

Creating Remote Recovery Sets 85

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.

CAUTION: If the maximum number is already defined in the policy, the dialog box displaysthe maximum number of Recovery Sets defined in the policy. If the number of existingRecovery Sets reaches the maximum number specified in the policy and if you create aRecovery Set, then the oldest Recovery Set is deleted.

5. Click Create to create the Remote Recovery Set.6. Click Yes to confirm.

NOTE: You can view the status of Remote Recovery Sets creation in Recent Tasks orMore Tasks.

Viewing Remote Recovery Sets group details1. 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 27 Remote Recovery Sets details


Managing Remote Recovery Sets schedulesRMC-V allows you to create Remote Recovery Sets according to a predefined schedule. TheRMC-V scheduler allows you to perform the following tasks:

• Add schedules

• Edit schedules

• Delete schedulesTo 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 existingschedules.

Figure 28 Schedule list

4. You can perform any of the following tasks from Schedule Create Remote Recovery Set:• Adding a schedule—To add a schedule, see “Adding schedules” (page 87).

• Editing a new schedule—To edit an existing schedule, see “Editing schedules” (page89).

• Deleting a new schedule—To delete a schedule, see “Deleting schedules” (page 89).5. After performing one or more tasks listed in the previous step, click Refresh to refresh the

list of schedules.6. To close the window, click Close.

Adding schedulesTo create Remote Recovery Sets in a Remote Recovery Configuration:1. To add a new scheduled Remote Recovery Set task, click Add.

The Welcome windows appears.

Managing Remote Recovery Sets schedules 87

2. Click Next. The Schedule window appears.a. Specify a task name for the schedule in Schedule task name.b. Select the task frequency fromPerformRecovery Set creation task to run the schedule.

The following frequencies are available:

Select this option toFrequency

Specify the time in minutes for the schedule.

NOTE: HPE recommends that you maintain a minimum of 30 minutesinterval between two schedules.

By minutes

Specify the time in hours and minutes for the schedule.Hourly

Specify the time in days for the schedule.Daily

Specify the time in weeks for the schedule. You can select one or moredays of a week to schedule the task.

Weekly

Specify the time in months for the schedule. You can select a particulardate of any month to schedule the task.

Monthly

Specify the time to run the schedule only one time. You can select a datefrom the calendar and specify the time to run the schedule only for onetime.

One time only

c. Specify details under Select time and frequency you want this task to start as listedin the following table.A different set of fields are displayed for each frequency that you select in PerformRecovery Set creation task.

Select this option toFrequency detailsFrequency

Specify the schedule start time in hours and minutes.Also, select AM or PM.

Start timeBy Minutes

Specify the frequency of the schedule in minutes.Recur every


Start timeHourly

Specify the frequency of the schedule in hours.Recur every


Start timeDaily

Specify the frequency of the schedule in days.Recur every


Start timeWeekly

All seven days of a week are displayed. You can selectone or more days.

Select days of week below


Start timeMonthly

Specify the day of the month for the schedule.Day

Select the date on which you must run the schedule.Start dateOne time only


Start time


3. Click Next.The Snapshot Configuration screen appears.

Figure 29 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. To confirm creating the schedule, click Yes.

After successful creation, the task is listed in the Schedule Create Remote Recovery Setwindow.

Editing schedules1. Select the schedule and click Edit. The Edit Schedule Task Wizard appears.2. For information on changing schedules using Edit Schedule Task Wizard, see “Adding

schedules” (page 87).

NOTE: You can make appropriate changes to all schedule parameters except theScheduletask name.

3. To refresh the list of schedules, click Refresh.4. To close the window, click Close.

Deleting schedulesThis section describes how to delete an existing schedule task.1. Select the schedule task to delete.2. Click Delete.3. Click Yes to confirm deletion of the schedule task.

Managing Remote Recovery Sets schedules 89

4. Click Close.

IMPORTANT: The scheduled jobs will fail after failover of the Remote Copy group and theRemote RMC/RMC-V fails to run the scheduled jobs. Schedule the jobs again at new sourceside.

Viewing Source and Target StoreServ Recovery SetsThis section describes how to view the source and target Recovery Sets for the HPE 3PARStoreServ 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 then click Recovery Sets on Source StoreServ to view

the Recovery Sets on the source HPE 3PAR StoreServ Storage systems.The Recovery Sets on Source StoreServ tab appears.

Figure 30 Recovery Sets on Source StoreServ

5. Click Recovery Sets on Source StoreServ to view the Recovery Sets on the source HPE3PAR StoreServ Storage systems.The Recovery Sets on Target StoreServ tab appears.

Figure 31 Recovery Sets on Target StoreServ

Managing Remote Recovery SetsThis section describes how to manage the Remote Recovery Sets. You can perform the followingtasks from the Manage tab:• Mounting Remote Recovery Sets

• Unmounting Remote Recovery Sets


• Attaching Remote Recovery Sets

• Detaching Remote Recovery SetsTo 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 32 Remote Recovery Sets Manage tab

Managing Remote Recovery Sets 91

6. You can perform the following tasks from the Manage tab:• Mounting Remote Recovery Sets—To mount Remote Recovery Sets, see “Mounting

Remote Recovery Sets” (page 92).• Unmounting Remote Recovery Sets—To unmount Remote Recovery Sets, see

“Unmounting Remote Recovery Sets” (page 94).• Attaching Remote Recovery Sets—To attach Remote Recovery Sets, see “Attaching

Remote Recovery Sets” (page 94).• Detaching Remote Recovery Sets—To detach Remote Recovery Sets, see “Detaching

Remote Recovery Sets” (page 96).

NOTE: For more information about the tasks that are enabled for Recovery Sets onSource StoreServ and Recovery Sets on Target StoreServ, see “Managing RemoteRecovery Sets in various configurations” (page 96).

Mounting Remote Recovery SetsThis 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 onnavigating to theManage tab, see steps 1 through 6 in “Managing Remote Recovery Sets” (page90).

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


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 HPE 3PAR StoreServ Storage System.

Figure 33 Mounting Snapshots—ESXi host

• Mount on proxy host—Select from a list of hosts that the vCenter Server does notmanage, but which have access to the source HPE 3PAR StoreServ Storage System.

Figure 34 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 fromAvailable to Mounted.


Unmounting 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 informationon navigating to the Manage tab, see steps 1 through 6 in “Managing Remote Recovery Sets”(page 90).To unmount a Remote Recovery Set that is already mounted:1. Select the Recovery Set you must unmount and click Mount/Unmount.

The Unmount Volume window appears.

Figure 35 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 Remote Recovery Set of the source HPE 3PAR StoreServ Storage allowsyou to perform only mount task to the proxy host if the Target StoreServ does not have anyVirtual Volume path exported to the ESXi host managed by the vCenter Server.

Attaching Remote Recovery SetsThis section describes how to copy a Remote Recovery Set to a datastore and how to attach aRecovery Set to a Virtual Machine.Be sure that you are in the Manage tab to attach the Remote Recovery Sets. For information onnavigating to theManage tab, see steps 1 through 6 in “Managing Remote Recovery Sets” (page90).

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 must attach to a VM.2. To mount a Recovery Set, click Copy/Attach/Detach.

The Copy/Attach window appears. The Copy to Datastore option is selected by default.


Figure 36 Copying to a Datastore

3. Select one of the following options:• Copy to Datastore—Select the datastore to which you must copy the selected Recovery

Set.• Attach to Virtual Machine—Select the Virtual Machine to which you must 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 must 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 copiedVMDK is always thick provisioned.


5. To attach the Remote Recovery Set to a VM:

Figure 37 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 SetsBe sure that you are in the Manage tab to detach Remote Recovery Sets. For information onnavigating to theManage tab, see steps 1 through 6 in “Managing Remote Recovery Sets” (page90).

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 must 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 sitesTasks possible from Recovery Sets on Recovery Sets on Source StoreServ and RecoverySets on Target StoreServ tabs—Mount, Unmount, Attach, and Detach; if mounted to the sameESXi host.


Tasks possible from Recovery Sets on Recovery Sets on Source StoreServ and RecoverySets 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 andRecovery 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.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—Mountand 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 ofthe tasks are allowed. We have to use the remote site for the supported operations.

Managing Remote Recovery Sets in Peer PersistenceTasks possible from Recovery Sets on Recovery Sets on Source StoreServ and RecoverySets on Target StoreServ tabs—Mount, Unmount, Attach, and Detach; if mounted to sameESXi host.Tasks possible from Recovery Sets on Recovery Sets on Source StoreServ and RecoverySets 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 StoreServand Recovery Sets on Target StoreServ tabs are interchanged.

For more information on Peer Persistence, see “Peer Persistence” (page 98).

Deleting Remote Recovery Sets1. 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. To confirm deletion of the Remote Recovery Set, click Yes. The Remote Recovery Set is

deleted from the list.

Deleting Remote Recovery Sets 97

Updating Recovery Manager CacheUpdate the Recovery Manager Cache and do a vCenter refresh if you have performed anyone of the following actions:

• Changes to the storage systems.

• Presenting a new Remote Copy Group.

• Failover.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. To confirm the update of the Recovery Manager cache, click Yes.

Peer PersistencePeer persistence enables redirect host I/O, either manually or automatically, from the source tothe target storage system in a manner that is transparent to the host while causing minimaldisruption to service. HPE 3PAR Peer Persistence is available for VMware configurations with3PAR OS 3.1.2 MU2 and later, and for Microsoft Windows configurations with 3PAR OS 3.2.1and later.For information on configuring Peer Persistence, see HP 3PAR Remote Copy Software UserGuide.

Figure 38 Remote Copy Configuration—Peer Persistence

RMC1

vCenter Server

TCP/IP Network

Synchronous


PrimarySystem

SecondarySystem

In Peer Persistence configuration, a single RMC instance and a vCenter Server manages thesource and target Remote Copy Groups. For more information on registering a remote RMCappliance, see “RMC Appliances” (page 39)The source and target Remote Recovery Sets are displayed in the RMC-V GUI.


Since the virtual volumes under the source and target Remote Copy Groups are exported to anESXi 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.

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 97).

You can then perform all other tasks related to Remote Recovery Sets.

Express Protect for Remote Recovery SetsYou cannot take a backup of Remote Copy groups snapshots. However, you can create a localRecovery Set of the virtual machine or datastore, and then take a backup. For more informationon taking Recovery Set backup, see “Creating Express Protects” (page 109).

Multiple RMC Appliance support for Remote Copy configurationsRemote copy configuration can coexist with multi-RMC configurations. However, only one RMCAppliance manages remote copy configurations, policies, and operations. The first registeredRMC appliance is implicitly used for managing the Remote Copy Snapshots. If the first RMCappliance is removed from the configuration, Remote Copy Snapshots and the configurationinformation are not available anymore. On the removal of the first RMC appliance from themulti-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 39 Remote Copy configurations with Multiple RMC appliances

RMC1 RMC2 RMC3 RMC

ESXi Server

StorageAdministrator Portal

RMC-V Plugin

Local Site Remote Site

Express Protect for Remote Recovery Sets 99

7 Working with Recovery Sets Express ProtectHPE Express Protect enables you to back up snapshots that are created on HP Storage Systems.These snapshots are stored on an HPE StoreOnce device.For more information on Express Protect, see the documentation provided with your HPEStoreOnce product.

Prerequisites• Ensure that HPE 3PAR StoreServ storage systems running 3PAR OS 3.2.1 MU1 are using

Express Protect.• Catalyst license on HPE StoreOnce.

Adding HPE Backup Systems• 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 GUIInterface and viewing the HP StoreOnce Recovery Manager Central Dashboard screen,see the HPE Recovery Manager Central User Guide.

• You can verify the newly added Storage and Backup systems from Recovery ManagerCentral GUI under Administration.

Types of BackupsRMC-V supports the following types of backup:

• Auto backup

• Full backup—This option is recommended when Auto backup fails.

NOTE: For HPE 3PAR StoreServ systems, a Full back up is performed when the Auto backupoperation fails. For HPE Hyper Converged 250 systems, an optimized backup (only data blocksare copied) is performed when the Auto backup operation fails. If the optimized backup for HPEHyper Converged 250 systems fails, then a Full backup is performed.

RMC-V supports the following backup options:

• Single stream

• Multi-streamFor more information, see “Multistreaming” (page 100).

Both multi-streaming and single stream support Express Protect with verification or withoutverification.

MultistreamingMultistreaming is a configuration whereby data from multiple sources is backed up concurrentlyto one endpoint device.

• If you do not select the Multistream option, the Express Protect is performed as single stream.

• RMC-V supports multistreaming of 2, 4, 8, or 16 streams for virtual volumes.

• When you perform a multistream Express Protect with verification, Express Protect verificationis also performed concurrently as multistream.

HPE StoreOnce multinode configurationRMC-V supports both single node and multinode configurations.

100 Working with Recovery Sets Express Protect

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 ormanually, the Express Protect takes the path of the active node and completes the ExpressProtect task successfully.For information on configuring HPE StoreOnce in single node or multinode configurations, seethe HPE 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.

Cancelling backupDuring the backup process, you can choose to abort the operation.1. Right-click the Express Protect and click Cancel running task.

2. To confirm cancellation, click Yes on the prompt that is displayed.

3. A message is displayed to indicate successful cancellation.

Creating Express Protect policiesYou 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 betweenthe RMC Appliance and HPE StoreOnce must be appropriately configured.

You can also add, edit, or delete an Express Protect system using RMC GUI. For more information,see HPE Recovery Manager Central User Guide.

Cancelling backup 101

Creating default Express Protect policiesTo create default Express Protect policies for your HPE 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.


5. ClickActions→All HPERecoveryManager Central Actions→Set Recovery Set CreationPolicy, and then click Express Protect.The Default Express Protect/Catalyst Copy Policy Settings screen appears.

Table 7 Creating default Express Protect policies

DescriptionField nameGroup name

The IP address of the deployed RMC appliance. If you havedeployed more than one RMC appliances, then all appliancesare listed.

RMC Host Name

Select an Express Protect policy from the list of policiesavailable in the drop-down list. The listed Express Protectpolicies are bound to the RMC instance that you have selected.

Express Protect Policy

ClickCreate Express Protect Policy to create a new ExpressProtect policy.

Create Express ProtectPolicy

NOTE: For information on creating policies, see “CreatingExpress Protect policies” (page 104).

Defaulted from Create Express Protect PolicyBackup system

Defaulted from Create Express Protect PolicyStore

Set expiry time in hours.Expiry Time

Set retention time in hours.Retention Time

Creating Express Protect policies 103

Table 7 Creating default Express Protect policies (continued)

DescriptionField nameGroup name

Defaulted from Create Express Protect PolicyMulti-Streaming

Defaulted from Create Express Protect PolicyVerify Express Protect

Displays either iSCSI or FC protocol that you selected in theCreate Express Protect Policy.

Storage array accessprotocol

Specify the maximum number of Express Protects that youmust retain. Express Protect count zero indicates that no upperlimit is set on the maximum number of Express Protects.

Maximum Number ofExpress Protects

Numeric

The default value displayed is seven.

Select this option to remove the oldest Express Protect afterthe maximum defined limit of Express Protect is reached. If

Remove Oldest ExpressProtect

you do not select this option, then the Express Protect that youtake after the maximum number of permissible ExpressProtects is reached will fail.This option is selected by default.

Select to choose and enable email notifications as per yourrequirements. For more information, see “Creating EmailNotification Policies” (page 69).

Enable Email Notification

Select to configure default copy policy settings.Configure Default CopyPolicy Settings

IMPORTANT:• HPE recommends that you specify the value ofMaximumNumber 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 changethe number of Express Protect policies to a number that is less than the number ofExpress Protects already created, then the system displays an error message statingthat 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 active.• To view the CoFC ID:

1. Log in to the HPE StoreOnce backup system.2. On the left pane, click StoreOnce Catalyst.3. On the right pane, click fibre channel settings.4. The Identifier value is the CoFC ID.

• Depending on the parameter selected in theCreate New Express Protect Policy, onlythat value is displayed.

Creating Express Protect policiesTo create an Express Protect policy for a datastore or a VM:


1. Click Create Policy from Create Express Protect Recovery Set or Default ExpressProtect 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 HPE StoreOnce is configured in multinode, then service set IDs for both nodes aredisplayed. 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 store or to grant access to an existing catalystclient.

TIP: You can also manually create a store using the HPE StoreOnce ManagementConsole.

a. The Modify StoreOnce Catalyst Store window appears.

NOTE:• If a Store exists, thenModify Existing Store option is selected by default. However,

if there are no stores, then Create Store option is selected by default.• For a multinode 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 HPEStoreOnce Backup system. If you enter a wrong user name, system displays anerror message prompting you to enter a valid user name.

NOTE: If you specify All Clients as the catalyst client user name, then accessis granted to all the existing clients in the selected store.

ii. Click Grant Access.A confirmation message appears after the access is successfully granted.


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 configuredHPE 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 HPE StoreOnce

Backup system that you selected. For single-node HPE StoreOnce Backup systems,the service set Id is 1. For multinode HPE StoreOnce Backup systems, the serviceset Id is more than one set Id. Select an appropriate service set Id based on wherethe store resides.

v. To grant access to the Catalyst Client, navigate to the Express Protect policy windowin the vSphere Web Client, clickModify store, provide the catalyst user name, andthen grant access to the catalyst client. Alternatively, you can also grant accessfrom the StoreOnce Management Console.

NOTE: If the Client Access Permission is not checked in the Settings tab ofthe Confirm page, user credentials will not be validated for any Express Protectactivity.


vi. Click Create.vii. Click Yes when you are prompted for confirmation.

A confirmation message is displayed after the datastore is created.

NOTE: When Express Protect is triggered, the snapshot is mapped in RMCappliance as a raw block device in the appliance OS.

6. The following fields display the status when the policy was created and you cannot modifythese statuses from this screen:• Backup System• Default Policy• Store• Expiry Time—Set expiry time in hours.

• Retention Time—Set retention time in hours.

• 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 theSPOCK.

• Verify Express Protect• Catalyst over Fiber Channel (CoFC)• CoFC Id• Catalyst over Ethernet (Coeth)—If HPE StoreOnce is configured in multinode, 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 HPE StoreOnceManagement Console.


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

Creating Express ProtectsYou can create Express Protect of a datastore or a VM using a VC-level Express Protect (CreateExpress Protect Recovery Set screen) or one-click Express Protect.

Creating one-click Express ProtectYou 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.4. Right-click the Virtual Machine, and then click All HPE Recovery Manager Central

Actions→Create Recovery Set and then click Express Protect. The Create ExpressProtect Recovery Set page appears.


Creating Express Protects 109

5. Enter the following details:• Name—Specify a name for the Express Protect.

• Description—Specify a brief description for the Express Protect.

• Backup Type—Select either Auto or Full backup. For more information, see “Typesof Backups” (page 100).

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 triggersdeletion of the oldest snapshot when you take an Express Protect if Remove OldestSnapshot is selected.HPE recommends that you set the number of snapshots such that you are able to takeboth snapshots and Express Protect created by RMC-V.

• Numeric policy count removes oldest snapshot must be set such that the Express Protectoperation of the oldest snapshot can be completed before it reaches numeric policylimit set. If Express Protect of the oldest snapshot is not complete and numeric countreaches the limit, then the subsequent scheduled Express Protects start failing until theExpress Protect operation of the oldest snapshot completes. For Express Protects, suchas full Express Protects or auto Express Protects with large number of changes, thattake a long time to complete.

Creating Recovery Set level Express Protect1. 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/Catalyst Copy Recovery Set.The Create Express Protect/Catalyst Copy Recovery Set window appears.


Figure 40 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.

You cannot change this display field from the 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—TheDefault Policy check box is selected by default if a default ExpressProtect policy is saved for the VM or datastore. If Default policy is selected, then youcannot select any other Express Protect policy listed in Policy.To enable selecting a policy other than the default policy, you must clear the Defaultpolicy check box. If a default policy does not exist, then the following message appearsindicating that you have not saved any default Express Protect policy for the VM/DS:

Creating Recovery Set level Express Protect 111

No default backup policy exists.

• Backup Store.

• Expiry/Retention Time in Hours.

• Multi-Streaming.

• Verify Express Protect.

• CoFC Id (Catalyst over Fibre Channel) or Coeth IP (Catalyst over ethernet) that youhave 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 arrayaccess protocol, Express Protect Store, Maximum number of Express Protects, Retentionand Expiration time, and Remove Oldest Express Protect are display fields. They displaythe respective values used during creation of the selected Express Protect policy.

8. To create and apply a new policy, click Create Express Protect Policy.

NOTE: For information on creating policies, see “Creating Express Protect policies” (page104).

9. Click Create and then click Yes to confirm creation of the Express Protect.

IMPORTANT: If a valid previous backup is not available, incremental express protect fails. Allbackups generated are full backups.

Scheduling Express ProtectsThis 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 change virtual volumes that the RMC-V plugin manages, you must do arefresh before you perform any RMC-V tasks.

Viewing a schedule list1. 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 theRecovery Sets tab, under theRelatedObjects tab.

4. Select a Virtual Machine or datastore to apply a schedule.


5. Click Actions→All HPE Recovery Manager Central Actions→Schedule Recovery SetCreation.The Schedule List window appears.

This window lists the RMC Instance, time zone of the RMC Instance and all tasks that arecurrently scheduled for Express Protect. From the Scheduled List window, you can add anExpress Protect, modify an existing schedule for an Express Protect, or delete an existingExpress Protect schedule.

6. To close the Scheduled List, click Close.You can automatically create Express Protects according to a specified schedule.

Creating schedules for Express Protect1. Navigate to the 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—Schedule creation of a snapshot for a virtual machine or datastore.

• Express Protect—Schedule Express Protect of a snapshot for a virtual machine ordatastore.

4. Select Express Protect to create a schedule for an Express Protect.

Scheduling Express Protects 113

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. Hourlyii. Dailyiii. 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 RecoverySet creation task. Table 8 (page 114) lists the frequency details of a schedule:

Table 8 Scheduling frequency

DescriptionFrequency detailsFrequency

You can specify the schedule starttime in hours and minutes. Also,select AM or PM.

Start timeDaily

Specify the frequency of thescheduled task.

Recur Every


Start timeHourly


Recur Every


Start timeMonthly

Specify the day of the month tostart the scheduled task.

Day

Select the date on which you needto schedule the Express Protect.



Start time


Start timeWeekly

All the seven days of a week aredisplayed. You can select one ormore days.

Select days of a week




1. To create application consistent Recovery Sets, select Create Recovery Set withVSS-aware application consistency.

2. (This screen appears only for datastore level schedules)

Scheduling Express Protects 115

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

Machines, 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 SetRecovery Set to expire after and Retain Recovery Set of the default policy.

• The Expiration/Retention option is not available for VVOL VMs. Therefore, expirationor retention details are not displayed for VVOL VMs.

7. Click Next. The Express Protect Configuration window appears.

Specify the following details:

• Name—A name for the Express Protect.

• Description—A brief description of the Express Protect.

• Backup Type—Select either Auto or Full backup. For more information, see “Typesof Backups” (page 100).


8. To apply an existing policy for the backup, select a backup policy from the policies listed inExpress 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 Protect9. Click Next. The Schedule Task Summary window appears.

Verify that the details listed in Schedule Task Summary are correct.10. To complete the task schedule, click Finish. The Schedule Modification window appears.

To confirm and schedule the task, click Yes.

NOTE: If a VM or datastore is removed, then the associated scheduled tasks continue torun. 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 schedulesTo 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 Wizardappears.

3. Click Next until you reach the Schedule and Snapshot Configuration pages of the EditSchedule Task Wizard.

4. Make appropriate changes to the schedule.For information on setting the schedule parameters, see “Scheduling Recovery Sets” (page65).


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

Modifying Express Protect schedules 117

4. Double-click datastore time stamp to view the details.The Manage tab appears with the message, No manage operations exist forbackup.

5. Click Manage. The No manage operations exist for backup details appear in the Summarytab.

You can view the following details in the Summary screen:

DescriptionField name

IP address or name of the vCenter.vCenter

Name of the VM or datastore.Name

Type of Express Protect, either VM or datastore.Type

Name of the Express Protect.Express Protect Name

GUID of the Express Protect job.Express Protect GUID

The state of the Express Protect, Partial or Available.State

If the Express Protect Snapshot is application consistent; True or False.Application Consistent

Status of the Express Protect; True or False.The status True indicates that the Express Protect is completed andsuccessfully compared with the source.

Verified

Name of the catalyst item in HPE StoreOnce.Catalyst Item Name

Time the Express Protect was created. Time is denoted in UTC time.Timestamp

Name of the Express Protect policy.Express Protect Policy Name

Name of the Store in HPE StoreOnce.Store Name

Name of the HPE StoreOnce Backup System.StoreOnce Name

Name of the catalyst user in HPE StoreOnce.Catalyst User

Name of the snapshot.Snapshot Name

A unique ID of the snapshot.SnapshotSet ID

Is the Express Protect incremental. True for incremental Express Protectand False for nonincremental Express Protect.

Incremental

Time zone of the RMC appliance.RMC Time Zone


Element Recovery TechnologyElement Recovery Technology (ERT) provides you the ability to access Recovery Sets objectsas read-only entities from HPE StoreOnce protected Express Protect objects, without repopulatingthe primary disk array volumes.

Transport protocolsFor ERT, the transport protocol:

• between ESXi host and RMC Appliance, must be over iSCSI

• between RMC Appliance and HPE StoreOnce can either be FC or IP depending on CoFCId (Catalyst over Fiber Channel) or Coeth IP (Catalyst over Ethernet).

You can mount Express Protect objects on ESXi hosts, Windows, or LINUX.ERT tasks can be performed only for Express Protect of the Recovery Sets created after installingor upgrading to RMC-V v1.2.0 and later versions. For Express Protect objects that were createdon versions before 1.2.0, you can perform only mount, unmount, and additional vCenter operationson the mounted Express Protect objects. However, copy, attach, and detach tasks cannot beperformed.

NOTE: ERT feature does not support VMware VVOLs.

ERT tasksYou can perform the following ERT tasks on Express Protect objects from the vSphere WebClient 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)

• “Virtual Machine Instant Recovery” (page 125)

• “Detaching Express Protect objects” (page 128)

Configuring ERTYou must add RMC host as a dynamic discovery target to the ESXi host adapter to discover theExpress Protect object iSCSI targets.

PrerequisitesBe sure that the ESXi host has an iSCSI Software Adapter configured as shown in“Configuring ERT” (page 119).This check is a one-time configuration task for each ESXi host.

Element Recovery Technology 119

Figure 41 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 for the changeto take effect.

Mounting Express Protect objects1. Navigate to the vSphere Web Client home page.2. Click vCenter→Datastore.

All the datastores managed by the vCenter Server are displayed.


3. Select a datastore, click Related Objects→Recovery Sets, and then double-click theExpress Protect that you must mount.

Figure 42 Mounting Express Protect

4. Click Mount/Unmount.

Figure 43 Mounting Express Protect

5. TheMount 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 changesto 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 Machinesalso.


Unmounting Express Protect objects

CAUTION: RMC-V does not perform any checks to ensure that the volume you unmount isactive or inactive. Therefore, before you unmount a volume, ensure that 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 datastoresCopy 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.• If snapshot is created on a VM that has other VMFS snapshots associated with it, then the

snapshot datastore also has VMFS snapshots files. This results in the failure of copy VMDKon mounted Express Protect object with the error: VMDK is part of one or moreVMFS snapshots. This is not a supported configuration for Express Protect VMDK copyoperation.

1. Navigate to the Manage tab.2. From virtual disks (scroll down to see the virtual disks on the sceen), select the VMDK file

that you must attach and click Copy/Attach/Detach.The Copy/Attach window appears.


Figure 44 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 MachinesThis section describes how to attach a VMDK file from the mounted Express Protect objects to aVM on an ESXi host.


NOTE: You can attach a VMDK file only if the Express Protect object is already mounted to anESXi 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 VMs 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 MachinesYou can detach a VMDK file associated with an Express Protect that is attached to a VirtualMachine.1. Navigate to the Manage tab.2. From virtual disks, select the VMDK file that you must detach and clickCopy/Attach/Detach.

The Detach window appears.3. Click Detach and click Yes when prompted to confirm detaching the Express Protect.


Virtual Machine Instant RecoveryThis feature enables you to recover a VM from a mounted Express Protect Object datastore, andyou can list Virtual Machines (VM) on the mounted Express Protect Object datastore. Also, youcan recover VMs with the option to redirect the input/output (IO) to another target datastore. Afterthe VM is registered to the vCenter, you can log in to the VM and recover the files.

Instant recovery of VMs from the Express Protect Object datastore1. Without IO redirect

This option can be chosen during VM recovery if the VM is used for only instant file restores.However, the recovered VM continues to operate from the Express Protect Object datastore.Use the VM for data restore purposes only.

2. With IO redirectThis option can be chosen during VM recovery if the VM is used for active read and writeoperations. When the VM is powered on, the IO is redirected to the target datastore. Thisoption enables you to use the VM for file restores and new write operations without affectingthe mounted Express Protect Object.

IMPORTANT:• HPE recommends using the recovered VM only for instant or temporary file restores.

However, for permanent file restores, you must Storage V-Motion the recovered VM toanother datastore.

• HPE recommends not to perform Storage V-Motion to the same IO redirect datastore,for VMs recovered with IO redirect option enabled.

Listing VMs on Express Protect Object datastoreThe Manage tab on the VM Instant Recovery window lists the VMs in the datastore. The VMtable lists information of the VM register status, IO Redirect target datastore, and so on.For VM backup set objects, the VM table lists only the VM to that belongs to the backup-setobject.For datastore backup set objects, the VM table lists all VMs in the datastore. However, VMrecovery is successful only if all virtual disks in the VM are in the mounted Express Protectdatastore.


NOTE: The VM table is empty if the Express Protect Object is not mounted. After the ExpressProtect Object is mounted, the VM table displays the VMX file path for VMs. For VM level ExpressProtect, only the corresponding VM is listed in the table.

Recovering a VM from the mounted Express Protect objects on ESXi host

IMPORTANT: You can recover a virtual machine only if the Express Protect object is alreadymounted to an ESXi host.

1. Click on the manage tab of the Express Protect Object.2. Select the VM instant recovery option from the Virtual Machine table.3. Enter the VM details and click on Finish.

VM detailsVM folder To register the VM.

Choose the default folder if no folders are created.

Resource Pool The resource pool of the ESXi host.Redirect IO Select the check box for enabling I/O redirection to another datastore.•

• Select the datastore for I/O redirection.

Registered VM NameThe registered VM name is automatically generated with the syntax:Original VM name + mounted datastore name

For example, if Windows is the original VM name and if snap-1234-3pardatastore is themounted datastore name. Then the registered VM name is:Windows_snap-1234-3pardatastore.

Notes

• VM recovery is not supported on VMs with RDM disks configured. Though VM registrationmight be successful, the power-on operation fails for the VM.

• VM recovery is not supported on VMware vApp.


• For subsequent VM recovery on the same VM, with redirect IO option, you must remountthe Express Protect Object.

• If a virtual machine disk (VMDK) from the mounted Express Protect datastore is attachedto an existing VM, then it is mandatory to detach the VMDK and remount the Express ProtectObject before recovering the VM.

Removing from inventory

1. Select the Remove from Inventory option from the Manage tab.2. Click on Unregister VM.3. Instant recovery VM is successfully unregistered.


Additional vCenter operationsvCenter Server supports the following additional operations for mounted Express Protect objects:

• You can perform additional datastore-related operations on the Express Protect objectsusing the vCenter GUI after the Express Protect object is mounted and presented as adatastore to an ESXi host.In the Manage tab, the Snapshot Datastore column of the Express Protects displays thename of the Express Protect object datastore after it is mounted.The newly presented datastore becomes available in the Datastores section of the vCenterGUI.

• On selecting the Express Protect datastore that is listed under Manage→Files, you canbrowse and edit contents of the datastore.HPE recommends that you use Express Protect datastores only for restore purposes. Donot add or modify the contents on the datastores.

• You can instantiate VMs directly from the Express Protect datastore using the Register VMoption that is available for a datastore.For information on registering a virtual machine with the vSphere web client, see VMwareDocumentation.

◦ Make sure that all virtual disks of the VM belong to the mounted Express Protectdatastore. It is strictly recommended not to register a VM containing virtual disks acrossdifferent datastores.

◦ HPE recommends that you use the newly registered VM from the Express Protectdatastore 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 andthe restored VM at the same time, then IP address conflict might occur. Make sure thatthe IP addresses of the VMs are appropriately assigned to avoid any potential IP addressconflict.

• 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 thenewly restored VM.

Managing concurrent Express ProtectsRMC Appliance allows you to submit any number of Express Protect jobs concurrently. You canreconfigure the vCPU and vRAM of the RMC Appliance so that the concurrent Express Protectjobs complete faster. Incremental Express Protects require double the number of streams,because it needs to read data from the HPE StoreOnce system.For optimal Express Protect performance:

• Plan and schedule your Express Protect jobs to ensure that, at any point in time the numberof data streams, is as shown in the Table 9 (page 129). For each RMC Appliance configuration,the number of data streams can be determined from the number of volumes that are backedup and the number of streams that are selected per volume.

• Also considerMaximumConcurrent Data and InboundCopy Jobs of the HPE StoreOnceBackup system. This value is displayed in the StoreOnce catalyst below the Status andSettings tabs.


Table 9 Concurrent data streams

16/64 GB8/32 GB4/16 GB2/8 GB (default)vCPU/vRAM

2561286432Maximumdata streamspermitted

Types of restoresRMC-V supports the following types of restores:

• Restore datastore snapshots from HPE 3PAR StoreServ Storage—This restore type issupported only on datastore level snapshots. If you have a VM level snapshot, restoreoperation is not allowed.

• Restore backup from HP StoreOnce—This restore type is supported for both datastore leveland VM level Express Protect to HPE StoreOnce tasks. ERT restores the mounted objects.

Restoring from Express ProtectsThis 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 SnapshotHPE recommends that you have the following conditions applied to the parent volume beforeyou perform restore to snapshot:

• Do not 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 ahost.

Prerequisites for restoring to any VolumeIf you must 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.

• The Express Protect is in available status.1. Select the Express Protect that you want to restore.

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.• The volume to restore must be either the same size or greater size compared to the

original volume.

2. Click Restore.

TIP: You can also perform a restore by clicking Actions→Restore.

Types of restores 129

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 createdas part of a restore.

• Restore to Parent Volume—If you select this option, the backed-up data is restoredto the parent virtual volume.

NOTE:

◦ Before you do a restore to parent volume, ensure that all the VMs in the datastoreare powered off.

◦ First incremental backup after an Express Protect restore to parent might be longerthan the normal incremental backup duration.

• Restore to any Volume—If you select this option, the backed-up data is restored toany other virtual volume (existing in HPE 3PAR StoreServ Storage system) except theparent volume.The following screen appears if you have selected restore for a Virtual Machine of typeVMFS. This task will restore the VMFS Virtual Machine to another HPE 3PAR StoreServstorage system registered with the RMC appliance.

NOTE: The Array Volume must be created prior to performing the restore. The sizeof the target volume must be equal to or greater than the size of the source volume.

The following screen appears if you have selected restore for a Virtual Machine of typeVVOL. This task restores and recreates the VVOL Virtual Machine to another storagecontainer known to the vCenter Server.

NOTE: The Array Volume must be created prior to performing the restore. The sizeof the target volume must be equal to or greater than the size of the source volume.


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 isdisplayed along with the current time stamp.

2. Host—Select an appropriate ESXi host from the list of compatible ESXi hosts thatare 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 restorethe 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 Volumenames are added.

If you perform restore in a multinode configuration and if the associated node fails, then therestore fails. To restore data, you must manually trigger the restore task and it will take the pathof the secondary node and complete the restore task successfully.

Additional steps to complete restore to any VolumeIf you have selected the Restore to Any Volume option during restore, then to complete therestore you must perform the following steps after the procedure mentioned in the beginning ofthis section.

Restoring from Express Protects 131

1. After the restore operation is successfully completed, export the volume from the storagesystem to the ESXi Server.

2. Scan the storage system once again.3. If it is the same ESXi Server where the source virtual volume was presented, then 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 snapshotscreated during restore to snapshot1. Navigate to the Summary tab of the snapshot object and identify the snapshot name.2. Log in to the HPE 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. ClickActions→All vCenter Actions→RescanStorage. TheDatacenter—RescanStorage

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 willexist for the datastore).

7. Select the required file. Right-clickDownload fromDatastore. Navigate to another datastoreand 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.


8 Working with Catalyst Copy Recovery SetsCatalyst Copy enables you to make a copy of the Express Protects that are created on an HPEStoreOnce store to either the same or another HPE StoreOnce store.

• Catalyst Copy supports all ERT tasks supported for Express Protect.

• Catalyst Copy Recovery Sets supports VMware VVOLs.

Prerequisites• Source and target HPE StoreOnce stores must be available on the RMC appliance.

• HPE 3PAR StoreServ storage system running 3PAR OS 3.2.1 MU1 or later.

Creating Catalyst Copy policiesNOTE:• Catalyst Copy over Fiber Channel is not supported.

• You cannot edit or delete Catalyst Copy policies from the RMC-V GUI. However, you canedit or delete Catalyst Copy policies from the RMC VM GUI.

PrerequisitesAn Express Protect policy (backup policy) with iSCSI option must exist to create a Catalyst Copypolicy.

Configuring default Catalyst Copy policies1. Navigate to the vSphere Web Client home page.2. Click VMs and Templates and select a VM or datastore.

The system displays all the available Recovery Sets in theRecovery Sets tab underRelatedObjects.

3. ClickActions→All HPERecoveryManager Central Actions→Set Recovery Set CreationPolicy, and then click Express Protect.The Default Express Protect/Catalyst Copy Policy Settings screen appears.

NOTE: For more information on Default Express Protect Policy settings, see “Creatingdefault Express Protect policies” (page 102).

4. Select Configure Default Copy Policy Settings.The Default Copy Policy Settings window appears.

Prerequisites 133

Figure 45 Creating Default Catalyst Copy Policy Settings

5. Click Create Copy Policy.The Create New Copy Policy screen appears.

Figure 46 Creating new Copy Policy

6. Copy Policy Name—Enter a name for the Copy Policy.7. Copy Policy Description—Enter a brief description of the Copy Policy.

134 Working with Catalyst Copy Recovery Sets

8. Express Protect Policy—Select an Express Protect Policy with an iSCSI storage protocolfrom the list.The details of the selected policy are displayed under the Details of Selected ExpressProtect Policy section.

Creating Catalyst Copy Recovery SetsThis section describes how to create Catalyst Copy Recovery Sets using one-click and directmethods.

Creating one-click Catalyst Copy Recovery SetsYou can use one-click Catalyst Copy to create a Snapshot, an Express Protect, and a CatalystCopy.1. Navigate to the vSphere Web Client home page and click VMs and Templates.2. Select a VM or datastore.3. Click Related Objects→Recovery Sets.

Recovery Sets related to the VM or datastore are displayed.4. Right-click the VM or datastore, and then click All HPE Recovery Manager Central

Actions→Create Recovery Set→Express Protect.The Create Express Protect/Catalyst Copy Recovery Set window appears.

Datastore level

VM level

Creating Catalyst Copy Recovery Sets 135

5. Enter the following details:• Name—Specify a name for the Express Protect.

• Description—Enter a brief description for the Express Protect.

• Back Type—Select either Auto or Full backup.6. Select Create Catalyst Copy Recovery Set.

The Catalyst Copy section appears.


7. Enter the following information in the Catalyst Copy section:• Name—Specify a name for the Catalyst Copy.

• Description—Enter a brief description of the Catalyst Copy.8. To apply an existing policy for the Catalyst Copy, select a Copy Policy from the policies listed

under Copy Policy.The following details are listed for the selected policy:

• Express Protect Policy

• Backup System

• Store

• Coeth IP (Catalyst over Ethernet)

• Expiration/Retention

• If a default Copy Policy is saved for the VM or datastore, the Default Policy check boxis selected by default.

NOTE: If Default Policy is selected, then you cannot select any other policy listedunder Copy Policy.To enable selecting a policy other than the default policy, you must clear the Defaultpolicy check box.If a default policy does not exist, then the following message appears indicating thatyou have not saved any default Copy Policy for the VM or datastore:No default copy policy exists.

• Maximum number of Catalyst Copies.

• Remove Oldest Catalyst Copy.

Creating Catalyst Copy Recovery Sets 137

NOTE: Backup System, Coeth IP, Store, Maximum number of Catalyst Copies, andRemove Oldest Catalyst Copy are display fields. Backup System, Coeth IP, and Store displayare values associated with the Express Protect policy of the selected Copy Policy. The fieldsMaximum number of Catalyst Copies and Remove Oldest Catalyst Copy display therespective values that were used during the creation of the default Copy Policy.

9. To create and apply a new policy, click Create Copy Policy.For more information on creating a Copy Policy, see “Configuring default Catalyst Copypolicies” (page 133).

10. Click Create and then click Yes to confirm creation of the Catalyst Copy Recovery Set.

Creating Catalyst Copy Recovery Sets1. Navigate to the home page and click VMs and Templates.2. Click the Virtual Machine or Datastore for which you want 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.4. Right-click the backup object and click Create Express Protect/Catalyst Copy Recovery

Set.The Create Express Protect/Catalyst Copy Recovery Set window appears.

Figure 47 Create Express Protect/Catalyst Copy Recovery Set

5. Enter the following information:• Name—Specify a name for the Catalyst Copy Recovery Set.

• Description—Enter a brief description of the Catalyst Copy Recovery Set.

• Copy Policy—The default Copy Policy is displayed. To change the default policy, clearthe Default Policy check box and select an appropriate policy from the Copy Policydrop-down list.

• Create Copy Policy—Click to create and apply a new policy.For more information on creating a Catalyst Copy policy, see “Configuring defaultCatalyst Copy policies” (page 133).


6. Click Create and then click Yes to confirm creating the Catalyst Copy Recovery Set.

NOTE: Use the RMC GUI to cancel the Catalyst Copy Recovery Set task that you have initiatedfrom RMC-V. For more information on cancelling the Catalyst Copy Recovery Set tasks, see theHPE Recovery Manager Central User Guide.

Managing Catalyst Copy Recovery Set schedulesRMC-V allows you to automatically create Catalyst Copy Recovery Sets according to a predefinedschedule.Using the RMC-V scheduler, you can:

• View a schedule list

• Add—Add a schedule

• Edit—Edit a schedule

• Delete—Delete a schedule

• Refresh—Refresh the schedule list

IMPORTANT: If you change virtual volumes that the RMC-V plugin manages, then you mustdo a refresh before you perform any RMC-V tasks.

Viewing the schedule list1. Navigate to the vSphere Web Client home page.2. Click Hosts and Clusters.3. Click a VM or a datastore.

System displays all the available Recovery Sets in the Recovery Sets tab, under RelatedObjects.

4. Select a VM or datastore to apply a schedule.5. Click Actions→All HPE Recovery Manager Central 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 arecurrently scheduled for Catalyst Copy. From the Scheduled List window, you can add aschedule, modify an existing schedule, or delete an existing Catalyst Copy schedule.

6. Click Refresh to view the schedule changes in the schedule list.7. Click Close to close the Schedule List.

Creating Catalyst Copy schedulesYou can automatically create Catalyst Copies according to a predefined schedule.

Managing Catalyst Copy Recovery Set schedules 139

1. Navigate to the Schedule List.


2. Click Add, to create a Catalyst Copy 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 a snapshot for a VM or a datastore.

• Express Protect—To schedule an Express Protect or Catalyst Copy of a snapshot fora VM or datastore.

4. Select Express Protect to create a schedule for a Catalyst Copy.5. Click Next. The Schedule window appears.

a. Specify a task name for the schedule in Schedule task name.b. Select the task frequency fromPerformRecovery Set creation task to create a Catalyst

Copy schedule. The following frequencies are listed:Additional options are displayed when you select a frequency from Perform RecoverySet creation task. Table 8 (page 114) lists the frequency details of a schedule.

Table 10 Scheduling frequency

DescriptionFrequency detailsFrequency


Start timeHourly


Recur Every


Start timeDaily


Recur Every


Start timeWeekly

All the seven days of a week aredisplayed. You can select one ormore days to schedule a weeklyCatalyst Copy.

Select days of week


Start timeMonthly

Specify the day of the month tostart the scheduled task.

Day

Select the date on which you needto schedule the Catalyst Copy.



Start time



In Snapshot Configuration do the following:a. Select Create Recovery Set with VSS-aware application consistency to create

application consistent Recovery Sets.b. Select one of the following options:

• Apply to all Virtual Machines—To apply the schedule to all VMs.

• Apply to following Virtual Machines—To apply the schedule task to specificVMs, select this option and then select the required VMs.

• Force creation if known VMware error occurs while I/O quiescence—Selectthis option if you require RMC-V to continue creating array snapshots even if anyof the selected datastore VMs encounter I/O quiesce error while creating VMwareVMFS snapshots for application consistency.

NOTE:

◦ Overwrite default policy setting is disabled for numeric policies. However,for Expiration/Retention policies this option is enabled. You can modify thevalues for Set Recovery Set to expire after and Retain Recovery Set of thedefault 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.a. Enter the following information:

• Name—Specify a name for the Express Protect.

• Description—Enter a brief description of the Express Protect.

• Backup Type—Select eitherAuto or Full backup. For more information, see “Typesof Backups” (page 100).

b. To apply an existing Express Protect policy, select a policy from Express ProtectPolicy.If you have to create a policy, click Create Express Protect Policy.

For more information on selecting or creating an Express Protect policy, see “SchedulingExpress Protects” (page 112).

Managing Catalyst Copy Recovery Set schedules 141

8. Click Create Catalyst Copy Recovery Set.The Catalyst Copy Configuration window appears.

Figure 48 Catalyst Copy Configuration

a. Enter the following information:• Name—Specify a name for the Catalyst Copy.

• Description—Enter a brief description of the Catalyst Copy.b. To apply an existing Copy Policy, select a policy from Copy Policy.

If you have to create a new Copy Policy, click Create Copy Policy.For more information, see steps 6 through 8 in section “Configuring default CatalystCopy policies” (page 133).

c. Default Policy—Select to apply the default policy.

NOTE: Ensure that Copy policy and Express Protect policy do not refer to the same store.

9. Click Next.The Summary window appears. Verify that the details listed in this window 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 torun. However, these tasks cannot be managed from the vSphere Web Client. Therefore,the task must be manually removed from RMC GUI.


Modifying Catalyst Copy schedules1. Navigate to Schedule List.


2. Select the schedule and click Edit.The Edit Schedule Task Wizard appears.

3. Click Next until you reach the Schedule and Snapshot Configuration pages of the EditSchedule Task Wizard.

4. Make appropriate changes to the schedule.For information on setting the schedule parameters, see “Scheduling Recovery Sets” (page65).

5. Click Next. The Schedule Task Summary window appears.Verify the details listed in Schedule Task Summary.

6. Click Finish to complete the task schedule.The Schedule Modification window appears.

7. Click Yes to confirm the changes made to the schedule.

Deleting Catalyst Copy schedules1. Navigate to Schedule List.


2. Select the schedule that you have to remove and click Delete.3. Click Yes to confirm deleting the schedule.

The schedule is removed from the schedule list.

Restoring from Catalyst CopyThis section explains how to restore the backed-up VMs and datastores.

NOTE: All VMs in the datastore must be shut down before you restore.

Recommendations for restoring to SnapshotHPE recommends that the following conditions are met before you perform restore to a snapshotfor the parent volume:

• Do not 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 ahost.

Prerequisites for restoring to any Volume• 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.To restore the backed-up VMs and datastores:

Restoring from Catalyst Copy 143

1. Select the Catalyst Copy from which you need to restore.

IMPORTANT: You can restore Catalyst Copies that are in the available state only.

NOTE:• Catalyst Copies of Virtual Machines are listed under theRecovery Sets tab and Catalyst

Copies of datastores are listed under the Datastores tab.• Restore is performed using the Catalyst Copies 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 one 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 in Recovery Sets. However, thefield in the Summary screen of this snapshot, indicates that this snapshot is createdas part of a restore.

• Restore to Parent Volume—If you select this option, the backed-up data is restoredto the parent virtual volume.

NOTE:

◦ Before you do a restore to parent volume, ensure that all the VMs in the datastoreare powered off.

◦ The first incremental backup after a Catalyst Copy restore to parent might be longerthan the normal incremental backup duration.

• Restore to any Volume—If you select this option, the backed-up data is restored toany other virtual volume (existing in HPE 3PAR StoreServ storage system) except theparent volume.The following screen appears if you select restore for a Virtual Machine of type VMFS.This task restores the VMFS Virtual Machine to another HPE 3PAR StoreServ storagesystem registered with the RMC appliance.

NOTE: An Array Volume must be created before performing a restore. The size ofthe target volume must be equal to or greater than the size of the source volume.


The following screen appears if you have selected restore for a Virtual Machine of typeVVOL. This task will restore and recreate the VVOL Virtual Machine to the vCenterServer.

NOTE: An Array Volume must be created before performing the restore. The sizeof the target volume must be equal to or greater than the size of the source volume.

Specify the following details:


1. Virtual Machine Name—Select an appropriate VM from the list of the parent VMs.By default, the parent VM name is displayed along with the current time stamp.

2. Host—Select an appropriate ESXi host from the list of compatible ESXi hosts thatare 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 VM.

NOTE: Restoring a Virtual Machine of type VVOL to the parent volume does not restorethe 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 Catalyst Copy changes to restoring. After the restore is complete, thestatus changes to available.

NOTE: For restore to any volume, the OK button is enabled only if the Array Volumenames are added.

If you perform restore in a multinode configuration and if the associated node fails, then therestore fails. To restore data, you must manually trigger the restore task and it will take the pathof the secondary node and complete the restore task successfully.

Additional steps to complete restore to any VolumeIf you have selected the Restore to Any Volume option during restore, then to complete therestore task you must perform the following additional steps:1. After the restore operation is successfully completed, export the volume from the storage

system to the ESXi Server.2. Scan the storage system.3. Select the Create new signature and keep data intact option if the same ESXi Server

where the source virtual volume was presented.4. Refresh the datacenter from the vSphere Web Client.

Mounting snapshots and performing Copy/Attach VMDK for snapshotscreated during restore to snapshot1. Navigate to the Summary tab of the snapshot object and identify the snapshot name.2. Log in to the HPE 3PAR Management Console and export the above identified snapshot to

an ESXi host that you need to mount.3. Log in to the vSphere Web Client and 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 the newly created datastore. Select Browse Files (the datastore, if on same

ESXi host will have the original name appended to it, otherwise, the same name exists forthe datastore).

7. Select the required file. Right-clickDownload fromDatastore. Navigate to another datastoreand use the Upload a file to the Datastore option to copy the file.

8. 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, virtual machine folder, and the disk to add.d. Review the selected options and click OK.


9 Using HPE 3PAR Peer Motion Manager Software withRMC-V

HPE 3PAR Peer Motion Manager is a feature of the 3PAR Operating System Software andmanages migration of data in between existing storage systems or third-party storage arrays.RMC-V supports HPE 3PAR Peer Motion Manager data migration activities without any impacton host operations while monitoring the primary storage system.

IMPORTANT: After the data migration between two HPE 3PAR StoreServ Storage systemsis complete, log out of Web Client, log in again, and update the Recovery Manager cache. Allscheduled tasks 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 conditionsare 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 becomeinvalid from RMC-V perspective even if they continue to appear in RMC-V. Log out of WebClient, log in again, and then update the Recovery Manager cache. You can access thevirtual copies using HP 3PAR Management Console or CLI. If you do not need these virtualcopies, you must manually remove them.

• RMC-V supports migration between two HPE 3PAR StoreServ storage systems only.Migration from HP EVA P6000 storage to HPE 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 is not available.

• All virtual volumes that are part of a VM or datastore must be migrated during HPE 3PARStoreServ storage to HPE 3PAR StoreServ storage Peer Motion. If all virtual volumes arenot migrated, unexpected behavior might occur.

For more information about performing Peer Motion data migration, see the HPE 3PAR PeerMotion User Guide. To download the HPE 3PAR Peer Motion User Guide click http://www.hp.com/go/3par/, navigate to your product page, click Support, and then click Manuals.

• To view backups taken before Peer Motion, select one of the Restore ExpressProtect/Catalyst options in the Restore Now window in RMC GUI.

• To Restore backups taken before Peer Motion, select theRestore Express Protect/CatalystCopy option in the Restore Now window in RMC GUI.

• After Peer Motion, you must perform a full backup before you restart the incremental backupschedules on Virtual Machines or datastores.

For more information on RMC GUI, see the HPE Recovery Manager Central User Guide.

148 Using HPE 3PAR Peer Motion Manager Software with RMC-V

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

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

10 TroubleshootingCommon issues

To troubleshoot common issues, perform the following tasks:

• Update Recovery Manager Cache.To update Recovery Manager Cache, right-click any object and click All HPE RecoveryManager Central Actions→Update Recovery Manager Cache.

• Log out and log in again to the vCenter Server.

• Restart the following services:

◦ VMware vCenter Web Client

IMPORTANT: When you restart the HPE VMware vCenter service, be sure that otherapplications that are accessing this service are not impacted.

Registering an RMC ApplianceRMC Configuration error

SymptomThe following error message is displayed on the HPE RMC Configuration page:

Web client session is not initialized.

CauseThis error message appears if the RMC Appliance fails to access or add the Storage and Backupsystems.

ActionDuring deployment of RMC, ensure that the DNS configuration is done correctly to resolve thehostname or fully qualified domain name (FQDN) of the vCenter server hostname, storage system,and backup system.

HPE 3PAR OS upgrade error

SymptomAfter upgrading HPE 3PAR OS from 3.2.1 to 3.2.2, the Incompatible version <version_number>found on storage system StorageSystem_number>, requires '322000' or above error messageis displayed.

Common issues 149

CauseIf changes are made in the HPE 3PAR StoreServ storage system, such as, upgrading HPE 3PAROS, changing HPE 3PAR licenses, and so on.

ActionPerform a storage system refresh:1. Log in to the RMC GUI (https://<IP_address> or <Host_name>).2. Click HPE RMC Configuration→Storage System→Action Menu and then click Refresh.3. Click Yes, Refresh for the changes to be effective.

Recovery Set Snapshot or Express Protect backup restore

SymptomError message Failed to restore array Snapshot is displayed.

CauseRecovery Manager cache is not updated.

ActionBefore restoring a Recovery Set Snapshot or Express Protect backup, perform the followingsteps:1. Power off the VM.2. Right-click the VM and then click All HPE Recovery Manager Central Actions→Update

Recovery Manager Cache.

RMC-V InstallationInstallation fails

SymptomInstallation using the RMC installation wizard fails.

Cause 1The .exe files are in a different folder.

Action 1Ensure that the .exe files extracted from the zip folder are all in the same folder.

Cause 2The free space in the Windows server is less than 4 GB.

Action 2Ensure a minimum space of 4 GB on the Windows server for the installer to execute.

User does not have required privileges

SymptomError: User does not have these required privileges[VirtualMachine.Provisioning.DiskRandomRead,VirtualMachine.Provisioning.GetVmFiles] to proceed with deployment.

150 Troubleshooting

ActionEnsure you have the required privileges for deployment and RMC-V plugin integration. For moreinformation, see “For deployment” and “For RMC-V plugin integration”.

Old RMC-V plugins

SymptomError: Found an RMC-V plugin already registered with the vCenter server.

CauseExistence of old RMC-V plugins.

RMC-V Installation 151

ActionTo unregister the old RMC-V plugins, perform the below steps:1. Open vCenter mob(https://<vcenterIP>/mob).2. Go to Content→Extension Manager.3. Click the Unregister Extension link.4. Enter the RMC-V plugin name: com.hp.rmcv.ngc_6.0 or com.hp.rmcv.ngc.5. Click Unregister.6. Repeat steps 2 and 5 until all old plugins are removed.

Unable to connect to the given IP/Host Name

SymptomError: Unable to connect to the given IP/Host Name. Provide valid IP/Host Name and credentials.

ActionPerform the following checks:1. vCenter server is ON.2. vCenter Web Client service is running on the vCenter server.3. vCenter firewall is disabled.4. vCenter server username and password are correctly entered.

152 Troubleshooting

5. vCenter server, ESXi host, RMC VM, and local machine with the installer are connectedthrough the same network (DNS,Gateway,subnet).

6. If FQDN is used, ensure that the domain server is accessible.

Unable to add storage or backup systems

SymptomUnable to add HPE 3PAR StoreServ or HPE Hyper Converged storage systems, and HPEStoreOnce backup systems.

ActionPerform the following checks:1. Valid credentials are entered for HPE 3PAR StoreServ or HPE Hyper Converged storage

systems, and HPE StoreOnce backup systems.2. RMC VM, HPE 3PAR StoreServ or HPE Hyper Converged systems, and HPE StoreOnce

backup systems are connected through the same network and can communicate in thenetwork (DNS, Gateway, subnet).

3. If FQDN is used, ensure that the domain server is accessible.4. If Hostname is used, ensure that the search domain is entered, while configuring RMC during

installation.


OVF deployment failed

SymptomError: Exception in deployOVF.

ActionPerform the following checks:

• Network connectivity. VMDK upload can fail because of network issues.

• Ensure the required licenses are installed on the ESXi or vCenter host.

• Clean the stalled VM entry on the ESXi host and restart installation.

Not able to reach the RMC VM

SymptomError: Not able to reach the IP. Check the default gateway of the installer host.

154 Troubleshooting

ActionPerform the following checks:1. RMC VM, Installer host, and vCenter server are connected through the same network and

can communicate in the network (DNS, Gateway, subnet).2. If FQDN is used, ensure domain server is accessible.3. If Hostname is used, ensure search domain is entered, while configuring RMC during

installation.

Not able to reach the RMC IP

SymptomError: Not able to reach the IP. Check the default gateway of the installer host.

ActionPerform the following checks:1. Ensure that DHCP is configured in the network.2. Ensure that DHCP has available IPs for allocation.

Password update failed

SymptomRMC password update failed during installation.


ActionPerform the following checks:1. Ensure that firewall is disabled on the vCenter server and installer host.2. Ensure that RMC is accessible through the network.

RMC-V plugin not visible

SymptomRMC-V plugin is not visible after successful installation.

ActionPerform the following actions:1. Restart the VMware Web Client service on the vCenter server.2. Disable firewall on the vCenter server.3. Ensure RMC is accessible from the vCenter server. Network configuration

(DNS,Gaterway,Subnet).4. Modify the network configuration for RMC. For more information, see the HPE Recovery

Manager Central User Guide.

RMC-V UpgradeFound an existing RMC-V plugin

SymptomError: Found an existing RMC-V plugin in the vCenter server.

156 Troubleshooting

CauseExistence of old RMC-V and OV4VC plugins.

ActionAfter RMC-V upgrade, uninstall old RMC-V and OV4VC plugins. However, if you must use OV4VCafter the upgrade, the old plugins are available on the web client. The old plugins do not affectthe RMC-V operations with the new plugin.

Unable to proceed with upgrade

SymptomUnable to proceed with upgrade, if old RMC-V plugins exists in the vCenter server.

ActionTo unregister the old RMC-V plugins, perform the below steps:1. Open vCenter mob(https://<vcenterIP>/mob).2. Go to Content→Extension Manager.3. Click the Unregister Extension link.4. Enter the RMC-V plugin name: com.hp.rmcv.ngc_6.0 or com.hp.rmcv.ngc.5. Click Unregister.6. Repeat steps 2 and 5 until all old plugins are removed.

RMC-V Upgrade 157

Upgrade failure

SymptomUpgrade to RMC-V 3.0.0 was unsuccessful.

ActionPerform the following checks:1. Ensure that the network configuration is correct.2. Ensure that processes in RMC are not in running state. You can check the processes on

the Activity link of the RMC GUI.3. Ensure that the RMC VM is accessible from the installer host and vCenter server.4. If FQDN is used, ensure that domain server is accessible.5. If Hostname is used, ensure that search domain is configured in RMC. For more information,

see the HPE Recovery Manager Central User Guide.

Multi RMC deployment partial failures

SymptomMulti RMC deployment partial failures observed.

ActionPerform the following checks:1. RMC VM, Installer host, and vCenter server are connected through the same network and

can communicate in the network (DNS, Gateway, subnet).2. If FQDN is used, ensure that domain server is accessible.3. If Hostname is used, ensure that search domain is entered, while configuring RMC during

installation.4. Rerun the installer for failed RMCs and restart the VMware Web Client service on the vCenter

server.

Installer logs

SymptomLocation of the installer logs on the installer host.

ActionInstaller logs are available at: C:\Program Files\HPE\RMCV on the system, where the installerwas executed.

RMC-V SnapshotsSmartclone with multiple disks or volumes

SymptomHPE RMC Snapshot creation fails with error: Exception in CreateVMFSSnapshotoperation for VM 'test' Detected an invalid snapshot configuration.

CauseThis error appears if you create snapshots of multiple base volumes with a smartclone for eachsnapshot, and add a virtual machine to the inventory. And when the secondary drives of thatvirtual machine are removed and added to the new smartclone datastore volumes.

158 Troubleshooting

ActionFollow the recommended actions at:VMware KnowledgeBase. Reattempt the snapshot creationfrom RMC.

Unable to back up Snapshots

SymptomWhen you attempt a Snapshot backup, with the base volume deleted, an error is displayed:Datastore/VM object not found in the vCenter. Object may have beendeleted from the inventory or the object base volume may have beendeleted.

CauseThe datastore volume is unexported or deleted.

ActionPerform the Snapshot backup from the RMC GUI.

Snapshot creation failed

SymptomError: Snapshot hierarchy is too deep. Failed to create array snapshot onVVOL-VM.

ActionTo remove existing VMware native snapshots from the VVOL VM, perform the following steps:1. Right-click the VVOL-VM.2. Select Manage Snapshots.3. Delete the VMware native Snapshots.

Snapshots and backups not displayed

SymptomAfter a VM with existing snapshots and backups is removed from the vCenter inventory andre-added to the inventory, the previously existing snapshots and backups in the VM do not appearin the RMC-V GUI.

CauseWhen a VM is removed from the vCenter Inventory, the Managed Object Reference (MoRef) IDof the VM is removed. And when the VM is readded, a new MoRef ID is set. As a result, theexisting snapshots and backups are removed from the RMC catalog.

RMC-V Snapshots 159

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005336

ActionNone

Incorrect Snapshot count

SymptomAfter migration, if array snapshot count for any LUN reaches the maximum (2048), the Snapshotcount for VM is shown as greater than the max limit (500).

ActionDelete few array Snapshots in the LUN, and create Snapshots on the VM, to restore the countback to 500.

RMC-V SchedulesFailed email notifications

SymptomA schedule is created in the RMC-V GUI, for the email notifications of virtual machines ordatastores. The schedule continues to run after the virtual machine or datastore is deleted,sending failed email notifications.

ActionOn the RMC GUI, remove the schedule.

Incorrect VMs on the Summary page

SymptomOn a datastore scheduler if there are multiple VMs, the VMs selected on the scheduler may varyfrom the VMs that appear on the Summary page. This behavior can result in the creation of aschedule that does not reflect the VMs you selected.

ActionClose and reopen the datastore scheduler. If you are editing an existing schedule, recreate theschedule.

Failed to create array snapshot

SymptomIf objects (VMs, Datastores, or RCgroups) are deleted or modified after schedule creation, anerror message is displayed: Failed to create array snapshot. HPE RMC Snapshotcreation failed.

ActionAfter objects (VMs, Datastores, or RCgroups) are deleted or modified after schedule creation,you must update the corresponding schedule to reflect the change.

160 Troubleshooting

Element Recovery TechnologyInstant VM recovery fails

SymptomSubsequent Instant VM Recovery with Redirect I/O option operation fails with the error Invalidsnapshot configuration was detected.

CauseInvalid snapshot configuration.

ActionRemount the Express Protect object and register the VM again for file level recovery.

vCenter selection dialog box

SymptomWhen the VM is powered on, the vCenter might display a user selection dialog box to selecteither the I Copied it or I moved it option.

CauseRegistering the same VM from the snapshot datastore.

ActionSelect I moved it if you want to reuse the same VM or select I copied it if you want to use theoriginal VM with the new VM.

VM recovery error

SymptomVM recovery, when creating a snapshot, fails with error message: File <unspecifiedfilename> is larger than the maximum size supported by datastore<unspecified datastore>.

CauseVMDK on the VM is larger than 2032 GB.

ActionPerform VM recovery without the IO redirect option. For more information, see VMwareKnowledge Base.

Mount/Unmount error

SymptomExpress Protect object Mount/Unmount tasks fails with the error message: An Unknown Erroroccurred.

CauseHPE StoreOnce is offline.

ActionEnsure the HPE StoreOnce server is online.




Unable to detect Express Protect Object LUNs

SymptomExpress Protect object Mount/Unmount task fails with the error message: Unable to detectExpress Protect Object LUNs.

CauseAdd an RMC host as a dynamic discovery target to the ESXi host adapter to discover the ExpressProtect object iSCSI targets.

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

Unable to detect Express Protect Object volumes

SymptomMount task fails with the error message: Unable to detect all Express ProtectObject volumes. Please make sure RMC IP is added as a dynamic discoverytarget on the ESXi host iSCSI Initiator.. You might also see that some of thetarget devices in iSCSI Software Adapter→Adapter Details display Inactive or Errorunder the Operational State column.

NOTE: If the vCenter Server (RMC-V plug-in) locale is Japanese language, then theMy Tasksmight display Fault task error.

Action1. Make sure that 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.

Inaccessible Express Protect Objects

SymptomAfter mounting the Express Protect object, the status of the mounted object in the Status columnof the Manage tab displays Not Accessible.

CauseHPE StoreOnce might be powered-off while the Express Protect object is still mounted.

Action1. HPE StoreOnce is online.2. Unmount the Express Protect object.3. Mount the Express Protect object again.

162 Troubleshooting

Invalid Express Protect Object

SymptomThe Mount/Unmount task fails with the error message: Express Protect Object‘attachStatus’ is invalid to continue current operation.

CauseThere might be a delay in updating the Express Protect object state depending on the backupenvironment you are using.

ActionRetry the Mount/Unmount task after some time.

Object deleted or not created

SymptomThe unmount task fails with datastore deletion error The object has already beendeleted or not completely created.

CauseDatastore is inactive if HPE StoreOnce is powered-off. Web Client lists the datastore as active,until the datastore status is refreshed. This results in datastore deletion error during unmountoperations.

ActionRetry the unmount task.

File in use from the datastore

SymptomThe unmount task fails with datastore deletion error indicating that a file is in use from thedatastore.

CauseA VMDK from the Express Protect datastore is attached to an existing VM.

ActionRemove the hard disk from the VM (under VM settings) and retry the unmount task.

Express Protect Object in use

SymptomMount/Unmount task fails with error message: Express Protect Object is in use.

CauseRMC Appliance rebooted leaving the data sessions to the catalyst objects on the StoreOnceopen. Further operations on the Express Protect Object fail (as previous data session is still openand the catalyst objects are locked).

ActionReboot StoreOnce server to close all data sessions or wait for 2 to 4 hours for the data sessionto time out on the particular Express Protect Object.


Virtual Disks not displayed

SymptomThe Manage tab does not display the Virtual Disks table and Copy/Attach/Detach button forVMDK.

CauseERT tasks can be performed only for Express Protect of the Recovery Sets created after installingor upgrading to RMC-V v3.0.0.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.

ActionInstall or upgrade to RMC-V 3.0.0.

Remote Recovery Sets ConfigurationsError: Not a 3PAR Volume

SymptomSnapshot creation fails with the error: Not a 3PAR Volume, when 3PAR Inform OS Patch isupgraded from 3.2.1 MU2 or older builds to 3.2.1 MU3 P19 and later versions.

CauseThis issue occurs if the XCOPY value is disabled on the array when Inform OS Patch is upgraded.

ActionEnabling the sdt_xcopy_lite_enable kvar value resolves the issue. Perform the followingsteps:1. Log in to HPE 3PAR CLI.2. Connect to the HPE 3PAR StoreServ from which the HPE 3PAR volumes are exported.3. To enable the XCOPY value, run the command: onallnodes tcli -e 'kvar show

-n sdt_xcopy_lite_enable'.4. To verify if the value set is correct, run the command: tcli -e 'kvar show -n

sdt_xcopy_lite_enable'.5. To fetch the correct details on volumes from vCenter MOB, perform the following operations

on VMware vSphere Web Client:

Remote Copy groups not listed

SymptomExisting and new Remote Copy groups are not listed in Remote Recovery Configurations

ActionEnsure the following:

• The ESXi server is in connected state.

• The ESXi server can discover array volumes.

164 Troubleshooting

• Rescan all storage adapters

• Recovery manager cache update =

Listing Remote Copy groups takes a long time

SymptomListing the Remote Copy groups is taking a long time in the Remote Recovery Configurationpage.

Cause

• One or more HPE 3PAR StoreServ or HPE Hyper Converged 250 storage systems areeither down or not reachable.

• The maximum permissible number of connections with the storage systems has exceeded.

• The WSAPI service is down.

ActionEnsure that all storage systems are connected and the WSAPI service is running.

Recovery Sets not appearing

SymptomNew Recovery Sets are not appearing in theRecovery Sets on Source StoreServ andRecoverySets on Target StoreServ tabs.

ActionPerform a vCenter refresh.

Snapshot creation fails

SymptomAfter failover, the existing scheduled jobs fail with the error message: snapshot creationfailed.

ActionDelete the existing schedule and create a schedule for the new primary system.

Manage tab not appearing

SymptomWhen you double-click a Recovery Set, the Manage tab does not appear. The error is: Youhave no privileges to view this object or it does not exist.

ActionRefresh the Web Client and retry the action.

Snapshot error

SymptomError: Create remote co-ordinated snapshot error due to createsv error.

CauseIf a Synchronous Remote Copy group has multiple volumes and if the first twenty characters aresame in the names of any two virtual volumes, then snapshot creation fails and the error messageis displayed.

Remote Recovery Sets Configurations 165

ActionWhile assigning a name to a virtual volume that is part of a Remote Copy group, ensure that thefirst twenty characters are unique.

Recovery Set not displayed

SymptomExisting Recovery Sets are not displayed.

CauseThe remote RMC Appliance is changed.

ActionTo view the existing Recovery Sets, add the same Remote RMC appliance again.

Remote appliance not found

SymptomIf you create a snapshot after the remote appliance is changed, the task fails with error message:Remote Appliance not found.

ActionRecreate the policy and create the Recovery Sets.

Schedule fails

SymptomIf you try to schedule creation of Remote Recovery Sets for Remote Copy Group and Local(Virtual Machine on the same Remote Copy group) at the same time, either of the tasks fails.

ActionEnsure that tasks are scheduled at different times.

Datastores not displayed

SymptomThe Datastore tab does not display the existing datastores unless VMs are associated with it.

ActionEnsure that datastores have VMs associated.

OthersAttaching VMDKs

SymptomWhile attaching a VMDK on the snapshot to a parent VM containing VMFS snapshot, the taskfreezes while reconfiguring the VM.

Action1. Go to the Summary tab of the parent VM.2. Select the Answer Question link, a popup appears.

166 Troubleshooting

3. Click Yes to attach the VMDK on the Snapshot.

Adding a storage system

SymptomWhen adding a storage system, either during installation or on the web client GUI, an error isdisplayed: Error in adding a storage system. Invalid input received: Badrequest (HTTP 400)

CauseThe wsapi service is not running on the HPE 3PAR StoreServ array.

ActionRestart the wsapi service on the HPE 3PAR StoreServ array.

Objects state

SymptomObjects in error_creating or deleting state.

CauseIf backup is terminated abruptly, the backup set is not deleted. This behavior is because thecatalyst object is in locked state.

ActionPerform the delete after the timeout is complete.

VMware operations fail

SymptomWhile creating application consistent snapshots, VMware might fail the operation and displaythe message Cannot create a quiesced snapshot because the create snapshotoperation exceeded the time limit for holding off I/O in the frozenVirtual Machine.

ActionEnsure that in the windows services the status of the following are as follows:

• Virtual disk service status is started and startup type automatic

• VMware snapshot provider service status is stopped and startup type disabled

• Volume shadow copy service service status is started and startup type automatic

• VMware tools service status is started and startup type automatic.For information on resolving this issue, see VMware KB articles 2069952, 1018194, 1031298,or other related articles.

Unable to delete VVOL Recovery Set

SymptomError message displayed: Failed to delete array snapshot.

Others 167

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2069952

http://kb.vmware.com/kb/1018194

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031298

ActionClick All HPE Recovery Manager Central Actions→Update Recovery Manager Cache to doa refresh and retry the task.

ssh connection error

SymptomWhen performing RMC-V related tasks, the following error message is displayed:

Error connecting via ssh: Error reading SSH protocol banner.

CauseDelay in receiving response from the HPE 3PAR StoreServ management command.

ActionCheck and verify the network responses between the RMC appliance and HPE 3PAR StoreServstorage system.

Backup issue

SymptomUnable to take simultaneous backup of a VM or datastore.

CauseVirtual volume is created in multiple HPE 3PAR virtual domains.

ActionIf you have a single RMC appliance running, then while creating a backup, RMC creates a hosteither with or without a domain name. The domain name is picked up based on the existence ofa virtual volume in any HPE 3PAR virtual domain. If you have ESXi in multiple HPE 3PAR virtualdomains, then you must select more than one RMC appliance for the backup to HPE StoreOncesystem.

Scheduled jobs not running

SymptomScheduled jobs are not running in the system.

CauseThe scheduled jobs are triggered in a time zone different from the HPE RMC appliance timezone.

ActionEnsure that the ESXi host time zone is appropriately set and synced. The RMC appliance, wheninstalled through the wizard, applies the time zone set in your ESXi hostTo verify the current time zone:

• RMC-V Schedule job GUI.

• Log in to the RMC GUI and click Settings option.

168 Troubleshooting

Unable to take snapshots or backups

SymptomUnable to take snapshots or backups after adding a new datastore or a VM in the vCenter server.

ActionPerform Update Recovery Manager Cache, a system-level cache refresh is done for theregistered HPE 3PAR StoreServ and HPE Hyper Converged 250 storage systems, and vCenterserver. The expected time to complete the cache refresh depends on the vCenter server andHPE 3PAR StoreServ or HPE Hyper Converged 250 storage environments.

Rebooting RMC appliance while a backup job is in progress

SymptomIf you reboot the RMC appliance while a backup job is in progress, the jobs that are in runningstate do not move to the failed state.

CauseThe RMC appliance is rebooted abruptly.

ActionEnsure that the scheduled jobs that are running are completed before you reboot the RMCAppliance. However, the state of the backup will be in error state and is displayed under theRecovery Sets tab. Restore from such a backup is not possible.

Failed to attach the VV

SymptomThe error message Failed to attach the VV is displayed when you perform an ExpressProtect to HPE StoreOnce on iSCSI or a VM direct path FC appliance.

ActionEnsure that the HPE 3PAR StoreServ or HPE Hyper Converged 250 host connectivity isappropriate.

Incorrect store client password

SymptomAfter entering an incorrect store client password, system allows you to create backup to HPEStoreOnce.

Others 169

CauseTheClient Access Permission check box is not selected, then HPE StoreOnce does not validatethe catalyst access credentials to perform the backup and restore tasks.

ActionSelect the Client Access Permission check box.

Driver uninitiated error

SymptomAfter adding a storage system to the RMC appliance, the create snapshot task displays theDriver uninitialized error message.

ActionWhile creating or updating the storage system, make sure that the credentials can be used foraccessing HPE 3PAR StoreServ or HPE Hyper Converged 250 storage system via SSH andWSAPI.

Object not found error

SymptomSystem displays Object not found error while performing RMC- V tasks on vSphere WebClient.

ActionPerform a cache refresh in the vSphere Web Client after you add any new object in the vCenter.If Object not found error message is displayed for an existing or newly added object (forexample, VM, datastore, or virtual volume), click Host→Manage→HPE Management and clickthe refresh icon.

NOTE: After clicking theRefresh icon once, allow the refresh to complete. Clicking theRefreshicon multiple times increases the time required to complete the refresh task.

Incremental Express protect or full backup fails

SymptomIf you delete one or more snapshots directly from the HPE 3PAR StoreServ storage and do notdo a refresh, then any request to take incremental Express Protect or full backup on snapshotsthat were taken earlier, fails.

CauseThis issue occurs because, one or more snapshots were deleted from the HPE 3PAR StoreServor HPE Hyper Converged storage with the respective base volumes. The Task tracker displaysa message stating that RMC failed to attach one or more snapshots.

ActionPerform a Refresh from the vSphere Web Client.

License error

SymptomWhile creating snapshots, RMC-V displays the following error message:

Could not fetch license from storage system.

170 Troubleshooting

ActionEnsure that the array connectivity to your RMC appliance is available.

Restore fails

SymptomWhen you perform restore on a multinode HPE StoreOnce, the restore fails and displays an errormessage.

CauseIf you perform restore in a multi-node configuration and if the associated node fails, then therestore fails.

ActionTo restore data, you must manually trigger the restore task and it will take the path of thesecondary node and complete the restore task successfully.

Unable to operate from the vSphere Web Client

SymptomInitially, RMC Appliance is registered with a vCenter (for example, VC1). Another RMC Applianceis registered with another vCenter (for example, VC2). After logging in to the vSphere Web Clientfor VC1, unable to perform any operation from the vSphere Web Client.

CauseRMC Appliance is not registered with VC1 since this RMC Appliance is now registered with VC2.

Action1. Log in to the Web Client of VC2 and remove the RMC appliance from the RMC Appliance

page, by clicking the HPE RMC Configuration tab on the left pane.2. Log in to the Web Client of VC1 and register the RMC instance from the RMC Appliance

page, by clicking the HPE RMC Configuration tab on the left pane.

Restore target issue

SymptomDuring restore, if the RMC Appliance is restarted, then the restore target (snapshot or basevolume) is not unexported from the RMC Appliance.

Action1. Detach the impacted snapshot or base volume manually, from the RMC appliance.2. Attach the snapshot or base volume to the original host.3. Rescan the host storage adapters.4. Retry the restore operation.

Default Snapshot policy settings error

SymptomWhile accessing the Default Snapshot Policy Settings page, if one RMC instance fails in amulti-RMC configuration setup, an error is displayed.

Others 171

ActionIdentify the RMC instance that is not accessible and rectify the issue. If you are unable to rectifythe issue, unregister the RMC instance.

Error: Session not initialized

SymptomIf the default snapshot policy of a VM, datastore, or a Remote Recovery Set is changed whilethe system is idle, the following error message appears: Session is not initialized.Please try to login again.

ActionLog off and log in again to the vSphere Web Client and wait until the web initialization is complete.

Snapshot mount fails

SymptomMount action for the Snapshot fails with the error: HP 3PAR mount operation failed :" Invalid input received: 'rwSnapshot' cannot be specified if snapshotis not read only."

CauseIf you perform a mount action on a Snapshot that was created during the restore operation.

ActionTo perform mount and Copy/Attach VMDK actions, perform the procedure listed in the Mountingsnapshots and performing Copy/Attach VMDK for snapshots created during restore to snapshotsection.

172 Troubleshooting

11 Support and other resourcesAccessing Hewlett Packard Enterprise Support

• For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:www.hpe.com/assistance

• To access documentation and support services, go to the Hewlett Packard Enterprise SupportCenter website:www.hpe.com/support/hpesc

Information to collect• Technical support registration number (if applicable)

• Product name, model or version, and serial number

• Operating system name and version

• Firmware version

• Error messages

• Product-specific reports and logs

• Add-on products or components

• Third-party products or components

Accessing updates• Some software products provide a mechanism for accessing software updates through the

product interface. Review your product documentation to identify the recommended softwareupdate method.

• To download product updates, go to either of the following:

Hewlett Packard Enterprise Support Center Get connected with updates page:www.hpe.com/support/e-updates

◦

◦ Software Depot website:www.hpe.com/support/softwaredepot

• To view and update your entitlements, and to link your contracts and warranties with yourprofile, go to the Hewlett Packard Enterprise Support Center More Information on Accessto Support Materials page:www.hpe.com/support/AccessToSupportMaterials

IMPORTANT: Access to some updates might require product entitlement when accessedthrough the Hewlett Packard Enterprise Support Center. You must have an HP Passportset up with relevant entitlements.

Websites

LinkWebsite

www.hpe.com/assistanceContact Hewlett Packard Enterprise Worldwide

www.hpe.com/support/e-updatesSubscription Service/Support Alerts

Accessing Hewlett Packard Enterprise Support 173

http://www.hpe.com/assistance

http://www.hpe.com/support/hpesc

http://www.hpe.com/support/e-updates

http://www.hpe.com/support/softwaredepot

http://www.hpe.com/support/AccessToSupportMaterials

http://www.hpe.com/assistance

http://www.hpe.com/support/e-updates

LinkWebsite

www.hpe.com/storage/rmc/swdepot/Software Depot

www.hpe.com/support/selfrepairCustomer Self Repair

Documentation

www.hpe.com/info/enterprise/docsHewlett Packard Enterprise Information Library

www.hpe.com/storage/rmc/docsRMC Documentation on Hewlett Packard EnterpriseInformation Library

www.hpe.com/support/hpescHewlett Packard Enterprise Support Center

www.hpe.com/storage/spock/Single Point of Connectivity Knowledge (SPOCK)nl

Storage Compatibility Matrix

www.hpe.com/storage/whitepapersStorage White Papers

Customer self repairHewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product.If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it atyour convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorizedservice provider will determine whether a repair can be accomplished by CSR.For more information about CSR, contact your local service provider or go to the CSR website:www.hpe.com/support/selfrepair

Remote supportRemote support is available with supported devices as part of your warranty or contractual supportagreement. It provides intelligent event diagnosis, and automatic, secure submission of hardwareevent notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolutionbased on your product’s service level. Hewlett Packard Enterprise strongly recommends thatyou register your device for remote support.For more information and device support details, go to the following website:www.hpe.com/info/insightremotesupport/docs

Documentation feedbackHewlett Packard Enterprise is committed to providing documentation that meets your needs. Tohelp us improve the documentation, send any errors, suggestions, or comments to DocumentationFeedback ([email protected]). When submitting your feedback, include the documenttitle, part number, edition, and publication date located on the front cover of the document. Foronline help content, include the product name, product version, help edition, and publication datelocated on the legal notices page.

174 Support and other resources

http://www.hpe.com/storage/rmc/swdepot

http://www.hpe.com/support/selfrepair

http://www.hpe.com/info/enterprise/docs

www.hpe.com/storage/rmc/docs

http://www.hpe.com/support/hpesc


http://www.hpe.com/storage/whitepapers

http://www.hpe.com/support/selfrepair

http://www.hpe.com/info/insightremotesupport/docs

mailto:[email protected]

A FAQsHow to generate a support ticket for troubleshooting issues

1. Enter the IP address of appliance (https: //<appliance IP>).2. Enter username and password and log in to RMC GUI.3. If you are logging in to the RMC appliance for the first time, you are prompted to change the

RMC appliance password.4. Click HPE Recovery Manager Central and select Support ticket from the Action menu.5. Click Yes, to generate the ticket.

Wait until 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.

How to generate a support ticket for troubleshooting issues 175

What are the log files required for troubleshooting RMC-V issues

DescriptionLog file name

This file is used to look into the call submission log. Youcan verify the job type (synchronous / asynchronous) and

rmv-api.log

job submission status. This also helps you to understandthe job request URI that is submitted to RMC appliance.

Support engineer can extract the support ticket and viewthe log file to understand the call flow. It will show you the

rmv-app.log

response and subsequent success or failure of any RMCjob request call from vCenter.

The required log files can be downloaded from the RMC GUI. For more information on downloadingthe log files, see the HPE Recovery Manager Central User Guide.

What are the required user privilegesFor deployment• VirtualMachine.Inventory.Create• VirtualMachine.Config.AddExistingDisk• VirtualMachine.Config.AddNewDisk• VirtualMachine.Config.RawDevice• Resource.AssignVMToPool• Datastore.AllocateSpace• Network.Assign• VApp.Import• Resource.CreatePool• VApp.Create• Host.Config.DateTime

For RMC-V plugin integration• System.Anonymous• System.Read• System.View• VirtualMachine.Config.DiskLease• VirtualMachine.Provisioning.DiskRandomRead• VirtualMachine.Provisioning.GetVmFiles• VirtualMachine.State.CreateSnapshot• VirtualMachine.State.RemoveSnapshot• Datastore.Browse• Host.Config.Storage• VirtualMachine.Config.AddExistingDisk• VirtualMachine.Config.AddNewDisk• VirtualMachine.Config.RawDevice

176 FAQs

• VirtualMachine.Config.RemoveDisk• VirtualMachine.Config.EditDevice• VirtualMachine.Config.Resource• Datastore.FileManagement• Global.LogEvent• Task.Create• Task.Update• Sessions.TerminateSession• Sessions.ValidateSession• Extension.Register• Extension.Unregister• Extension.Update

What are the required user privileges 177

GlossaryAppliance Preconfigured virtual machine that includes a preinstalled guest operating system and other

softwareCIM Common Interface ModelCoeth Catalyst over EthernetCoFC Catalyst over Fibre ChannelFC Fibre ChanneliSCSI Internet Small Computer System InterfaceSLD Synchronous Long DistanceThick ProvisionEager Zeroed

Thick virtual disk that supports clustering features, such as Fault tolerance

ThickProvisionedLazyZeroed

Virtual disk in a default thick format

Thin Provision Saves storage space. For the thin disk, you provision as much datastore space as the diskwould require based on the value that you enter for the disk size. However, the thin disk startssmall and at first, uses only as much datastore space as the disk needs for its initial operations.

vApps Preconfigured virtual machine that packages applications with the operating systemVASA vSphere APIs for Storage AwarenessVirtual Machine A Virtual Machine (VM) is a software computer that, like a physical computer, runs an operating

system and applications. Multiple virtual machines can operate on the same host systemconcurrently.

VV Virtual VolumeVVOL VMware vSphere virtual volume

178 Glossary

Index

Aaccessing

updates, 173active and passive RMC instances, 11application consistent recovery set, 14attaching recovery sets, 60attaching remote recovery sets, 94

Bbackup

managing concurrent Express Protects, 128types of backup, 100viewing details, 117

browser based, 13

Ccache

updating recovery manager cache, 71Catalyst Copies

creating one-click Catalyst Copies, 135Catalyst Copy

creating Catalyst Copy policies, 133deleting schedules, 143

Catalyst Copy Recovery Setscheduling, 139

Catalyst Copy recovery sets, 133concurrent Express Protects, 128contacting Hewlett Packard Enterprise, 173Creating Catalyst Copies, 135creating Catalyst Copy policies, 133creating default Catalyst Copy policies, 133creating default Express Protect policies, 102creating default recovery set policy, 48creating Express Protect policies, 101Creating Express Protects, 109creating new Express Protect policies, 104creating one-click Catalyst Copies, 135creating one-click Express Protect, 109creating recovery sets, 54creating VC-level Express Protect, 110creation time, 13credential sharing, 8customer self repair, 174

Ddata consistency, 10datastore Recovery Sets

restrictions, 11datastore recovery Sets, 11Default Recovery Set policies

creating, 48deleting Catalyst Copy schedules, 143deleting recovery sets, 64deleting Remote Recovery Sets, 97deployment models, 18detaching Express Protect, 124

detaching recovery sets, 63detaching remote recovery sets, 96documentation

providing feedback on, 174

Eediting schedules, 69ensuring volume consistency, 9Expirable Recovery Sets, 52

enabling, 52Express Protect

creating Express Protect policies, 101creating one-click Express Protect, 109creating VC-level Express Protects, 110detach, 124for Remote Recovery Sets, 99modifying schedules, 117, 143mounting, 120scheduling, 112unmounting, 122

HHPE 3PAR peer motion manager, 148

Kknowledge base, 10

Llicense models, 15licensing scenarios, 15

Mmemory blocks, 10modifying schedules, 117, 143mounting Express Protect, 120mounting Recovery Sets, 59mounting recovery sets, 59mounting remote recovery sets, 92multinode configuration, 100multiple disks, 9

Ooverview, 8

Ppair, 13Peer Persistence, 98policy

creating Catalyst Copy policies, 133creating default Catalyst Copy policies, 133creating default Express Protect policies, 102creating Express Protect policies, 101creating new Express Protect policies, 104

Prerequisitesrecovery sets Express Protect, 100

prerequisitesCatalyst Copy recovery sets, 133

179

RRecovery Set

Datastore, 11properties, 13

recovery setorganization, 13virtual machine, 12VM consistent, 14

recovery set browser, 13Recovery Set policy

attributes, 10recovery set policy, 10Recovery Sets

mounting, 59recovery sets

deleting, 64detach, 63restoring, 63unmount, 60

related objects, 102, 133Remote Copy configurations

multiple RMC Appliance support, 99Remote Recovery Sets

deleting, 97remote recovery sets

detach, 96remote support, 174removing schedules, 69restore

restoring from backups, 129, 143types, 129

restoring datastores, 63restoring virtual machines, 63retaining Recovery Sets, 52retention policies, 11RMC OVF template

deployment, 16RMC Remote Copy Configurations Topologies, 76

Sscheduling Catalyst Copy Recovery Sets, 139scheduling Express Protects, 112scheduling options

Express Protect, 14scheduling recovery sets, 65starting HPE 3PAR Management Plug-In for VMware

vCenter, 37support

Hewlett Packard Enterprise, 173supported environments, 8system requirements, 8

TTopologies

Remote Copy Configuration—Multisite RMC Appliance,76

Remote Copy Configuration—Single-site RMCAppliance, 76

Remote Copy Configuration—Synchronous LongDistance, 76

RMC Remote Copy Configurations Topologies, 76

Uunmounting Express Protect, 122unmounting recovery sets, 60unmounting remote recovery sets, 94updates

accessing, 173updating Recovery Manager Cache, 98updating recovery manager cache, 71user authentication, 8

Vviewing backup details, 117viewing recovery set event logs, 58viewing recovery set information, 56viewing recovery sets, 64viewing virtual disk details, 58virtual machine recovery sets

restrictions, 12VMFS , 10, 12VMFS snapshots, 14VMs and Templates, 54vSphere Web Client

logging in, 38, 80, 82, 85–87, 91

Wwebsites, 173

customer self repair, 174working with Catalyst Copy recovery sets, 133working with recovery sets Express Protect, 100working with recovery sets snapshots, 47working with vSphere Web Client, 37

180 Index

hpe recovery manager central for vmware user guideh20628. · ... vmware® vcenter server™, and...

Documents