Contents

Dell Symmetrix VMAX 20K V4.1.2 Storage Administration Guide PDF

1 of 150
1 of 150

Summary of Content for Dell Symmetrix VMAX 20K V4.1.2 Storage Administration Guide PDF

Enterprise Hybrid Cloud 4.1.2

Administration Guide

May 2018

H15833.2

Abstract

This guide describes the administration functionality of Enterprise Hybrid Cloud 4.1.2. Enterprise Hybrid Cloud enables IT organizations to deliver infrastructure, storage, backup, continuous availability, and disaster recovery as cloud services.

Dell EMC Solutions

Copyright

2 Enterprise Hybrid Cloud 4.1.2 Administration Guide

The information in this publication is provided as is. Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.

Use, copying, and distribution of any software described in this publication requires an applicable software license.

Copyright 2018 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Intel, the Intel logo, the Intel Inside logo and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Other trademarks may be the property of their respective owners. Published in the USA 09/18 Administration Guide H15833.2.

Dell Inc. believes the information in this document is accurate as of its publication date. The information is subject to change without notice.

Contents

3 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Contents

Chapter 1 Executive Summary 5

Document purpose ................................................................................................ 6

Audience ............................................................................................................... 6

Essential reading .................................................................................................. 6

Business challenge ............................................................................................... 6

Solution purpose ................................................................................................... 7

Technology solution .............................................................................................. 7

We value your feedback ........................................................................................ 8

Chapter 2 Getting Started 9

Terminology ........................................................................................................ 10

Important prerequisites ....................................................................................... 11

Administration scenarios ..................................................................................... 11

Special character restrictions .............................................................................. 11

Chapter 3 Environment Configuration 12

Managing features and environmental defaults ................................................... 13

Managing environment connections .................................................................... 15

Managing sites .................................................................................................... 17

Managing vCenters ............................................................................................. 19

Managing vCenter relationships .......................................................................... 22

Managing hardware islands ................................................................................ 29

Managing RecoverPoint for Virtual Machines vRPA clusters ............................... 33

Managing vSphere clusters ................................................................................. 35

Remove a VMware ESXi host from a cluster ....................................................... 42

Managing datastores ........................................................................................... 48

Chapter 4 Storage Services 50

Overview ............................................................................................................. 51

Storage provisioning services ............................................................................. 51

Creating resource reservations ........................................................................... 52

Storage as a Service ........................................................................................... 54

Assigning storage to business group reservations .............................................. 62

Chapter 5 Virtual Machine Lifecycle 64

Virtual machine lifecycle ...................................................................................... 65

Continuous availability ........................................................................................ 70

Contents

4 Enterprise Hybrid Cloud 4.1.2 Administration Guide

VMware vCenter Site Recovery Manager disaster recovery ................................ 71

RecoverPoint for Virtual Machines ...................................................................... 75

Virtual machine encryption .................................................................................. 82

Onboarding a VxRail Appliance endpoint ............................................................ 94

Chapter 6 Data Protection 96

Overview ............................................................................................................. 97

Managing Avamar ............................................................................................... 97

Managing Avamar Site Relationships ................................................................ 100

Managing Avamar Replication Relationships .................................................... 103

Managing Avamar proxies ................................................................................. 107

Managing Backup service levels ....................................................................... 115

Virtual machine backup lifecycle ....................................................................... 121

Ensuring continuity of backup in CA failure scenarios ....................................... 126

Data protection reporting ................................................................................... 132

Chapter 7 Administration Scenarios 136

Overview ........................................................................................................... 137

Scenario 1: Single site with backup ................................................................... 137

Scenario 2: Dual-site CA with replicated backup ............................................... 140

Scenario 3: Dual-site Site Recovery Manager DR with replicated backup.........143

Chapter 8 Conclusion 147

Summary .......................................................................................................... 148

Chapter 9 References 149

Dell EMC Documentation .................................................................................. 150

Chapter 1: Executive Summary

5 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Chapter 1 Executive Summary

This chapter presents the following topics:

Document purpose ............................................................................................. 6

Audience .............................................................................................................. 6

Essential reading ................................................................................................ 6

Business challenge ............................................................................................. 6

Solution purpose................................................................................................. 7

Technology solution ........................................................................................... 7

We value your feedback ..................................................................................... 8

Chapter 1: Executive Summary

6 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Document purpose

This administration guide describes the functionality and use cases of Dell EMC

Enterprise Hybrid Cloud. It explains how IT organizations can use Enterprise Hybrid Cloud

to deliver infrastructure, storage, backup, continuous availability (CA), and disaster

recovery (DR), among other functions, as services.

Audience

This administration guide is intended for architects, cloud administrators, and technical

administrators of IT environments who want to implement or use Enterprise Hybrid Cloud.

Readers should be familiar with the VMware vRealize Suite, storage technologies, and

general IT functions and requirements, and how they fit into a hybrid cloud architecture.

Essential reading

The following guides provide further information about various aspects of Enterprise

Hybrid Cloud:

Enterprise Hybrid Cloud 4.1.2: Concepts and Architecture

Enterprise Hybrid Cloud 4.1.2: Reference Architecture

Enterprise Hybrid Cloud 4.1.1: Infrastructure and Operations Management

Business challenge

While many organizations have successfully introduced virtualization as a core technology

within their datacenters, the benefits of virtualization have largely been restricted to the IT

infrastructure owners. End users and business units within customer organizations have

not experienced virtualization benefits, such as increased agility, mobility, and control.

Transforming from the traditional IT model to a cloud-operating model involves

overcoming the challenges of legacy infrastructure and processes, such as:

Inefficiency and inflexibility

Slow, reactive responses to customer requests

Inadequate visibility into the cost of the requested infrastructure

Limited choice of availability and protection services

To meet these challenges, public cloud providers have built technology and business

models that cater to the requirements of end-user agility and control. Many organizations

are under pressure to provide these same service levels within the secure and compliant

confines of the on-premises datacenter. As a result, IT departments must create

alternative cloud solutions that are cost-effective and that do not compromise enterprise

requirements such as data protection, DR, and guaranteed service levels.

Chapter 1: Executive Summary

7 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Solution purpose

Enterprise Hybrid Cloud is a completely virtualized datacenter, fully automated by

software. It starts with a foundation that delivers infrastructure as a service (IaaS). When

Enterprise Hybrid Cloud is live, you can customize it with add-on modules, including

database as a service, platform as a service, and cloud brokering. In addition, you can

optionally implement high availability (HA) and data recovery, as well as backup and

recovery services.

Enterprise Hybrid Cloud enables:

Complete management of the infrastructure service lifecycle

On-demand management of network bandwidth, servers, storage, and security

Provisioning, monitoring, protection, and management of the infrastructure services by line-of-business users (without IT administrator involvement)

Provisioning of application blueprints with associated infrastructure resources by line-of-business application owners (without IT administrator involvement)

Provisioning of backup, CA, and DR services as part of the cloud service provisioning process

Maximum asset utilization

Technology solution

Enterprise Hybrid Cloud integrates automated workflows and application blueprints with

converged and hyperconverged infrastructures with Dell EMC, VMware, professional

services, and single-contact support into an easy-to-consume hybrid cloud converged

platform.

Enterprise Hybrid Cloud integrates the best of Dell EMC and VMware products and

services with converged and hyperconverged infrastructures. This integration empowers

IT organizations to accelerate implementation and adoption of a hybrid cloud

infrastructure, while still enabling customer choice for the compute and networking

infrastructure within the datacenter. Enterprise Hybrid Cloud caters to customers who

want to preserve their investment and make better use of their existing infrastructure, and

to those who want to build out new infrastructures that are dedicated to a hybrid cloud.

Enterprise Hybrid Cloud takes advantage of the strong integration between Dell EMC

technologies and the VMware vRealize Suite. Enterprise Hybrid Cloud, developed by Dell

EMC, includes Dell EMC scalable storage arrays, integrated Dell EMC and VMware

monitoring, and data protection suites to provide the foundation for enabling cloud

services within the customer environment.

Enterprise Hybrid Cloud offers several key benefits to customers:

Rapid implementationEnterprise Hybrid Cloud provides the foundation for infrastructure as a service (IaaS) and can be designed and implemented in a validated, tested, and repeatable way that is based on Dell EMC converged infrastructure. This increases the time-to-value for the customer while simultaneously reducing risk. You can deliver IT as a service (ITaaS) with add- on modules for backup, DR, CA, virtual machine encryption, applications,

Chapter 1: Executive Summary

8 Enterprise Hybrid Cloud 4.1.2 Administration Guide

application lifecycle automation for continuous delivery, ecosystem extensions, and more.

Defined upgrade pathCustomers implementing Enterprise Hybrid Cloud receive upgrade guidance based on the testing and validation completed by our engineering teams. This upgrade guidance enables customers, partners, and Dell EMC services teams to perform upgrades faster and with much less risk.

Validated and tested integrationExtensive integration testing by Dell EMC has made Enterprise Hybrid Cloud simpler to use and manage, and more efficient to operate.

We value your feedback

Dell EMC and the authors of this document welcome your feedback on the solution and

the solution documentation. Contact Dell EMC Solutions team with your comments.

Authors: Brian OConnell, Penelope Howe-Mailly

Chapter 2: Getting Started

9 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Chapter 2 Getting Started

This chapter presents the following topics:

Terminology ...................................................................................................... 10

Important prerequisites .................................................................................... 11

Administration scenarios ................................................................................. 11

Special character restrictions .......................................................................... 11

Chapter 2: Getting Started

10 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Terminology

Table 1 defines some of the terms used in this guide when describing Enterprise Hybrid

Cloud.

Table 1. Terminology

Terminology Description

Object model Enterprise Hybrid Cloud uses an object model that provides the framework for storing and referencing metadata related to infrastructure and compute resources. It also acts as the rules engine for provisioning storage, backup service levels, and inter-site or intra-site protection services.

Hardware island An Enterprise Hybrid Cloud hardware island of compute, storage, and networking resources. The hardware island concept is the key determining factor in configuring VMware vSphere clusters that offer inter-site or intra-site resilience.

Avamar Site Relationship (ASR) A relationship between sites for backup purposes. An ASR is required even if there is only one physical site.

Avamar Replication Relationship (ARR) A relationship between as many as three Dell EMC Avamar grids. The ARR determines the specific Avamar grids that are responsible for backup operations on an individual Enterprise Hybrid Cloud workload. An ARR is required even if there is only one physical site.

Storage as a service (STaaS) Storage provisioning services provided by Dell EMC ViPR Controller.

Backup as a service (BaaS) Virtual machine backup services provided by Avamar.

Chapter 2: Getting Started

11 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Important prerequisites

When configuring your Enterprise Hybrid Cloud, you must meet certain requirements for

the operations that you want to run.

The flowchart in Figure 1 shows the steps that you must complete before you can create

an Avamar backup service level, for example. Each of these steps represents a VMware

vRealize Automation catalog item. Where environmental prerequisites exist, they are

described in each section and represented in each flow diagram by the initial step.

Figure 1. Example flowchart: Create backup service level

Administration scenarios

This guide outlines all Day 2 operations that are possible with Enterprise Hybrid Cloud.

Chapter 7 contains common end-to-end administration scenarios that you can use as a

reference when configuring Enterprise Hybrid Cloud.

Special character restrictions

Because of delimiter requirements in the backend database, do not use the pipe character

| or the underscore character _ in a property name or property value (for example, Site

Names) in the object model.

Prerequisites Add a site Add a vCenter Add a

hardware island

Add local cluster

Add Avamar grid

Create ASRCreate ARR

Associate cluster with

ASR

Create Backup Service Level

Chapter 3: Environment Configuration

12 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Chapter 3 Environment Configuration

This chapter presents the following topics:

Managing features and environmental defaults .............................................. 13

Managing environment connections ............................................................... 15

Managing sites .................................................................................................. 17

Managing vCenters ........................................................................................... 19

Managing vCenter relationships ...................................................................... 22

Managing hardware islands ............................................................................. 29

Managing RecoverPoint for Virtual Machines vRPA clusters ........................ 33

Managing vSphere clusters .............................................................................. 35

Remove a VMware ESXi host from a cluster ................................................... 42

Managing datastores ........................................................................................ 48

Chapter 3: Environment Configuration

13 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Managing features and environmental defaults

The Enterprise Hybrid Cloud object model contains options that you can use to control

system behavior across all sites and infrastructure. Some options are internal controls that

are visible but cannot be changed directly by an Enterprise Hybrid Cloud administrator.

You can use EHC Global Options Maintenance to edit the values of the Enterprise Hybrid

Cloud global options, to enable features, and to set environmental defaults.

To enable the Enterprise Hybrid Cloud CA protection service:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Global Options Maintenance catalog item (for

example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select EHC Global Options Maintenance.

3. Choose ca_enabled from the list box and select Yes.

To modify the default Avamar replication port, which is 27000:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Global Options Maintenance catalog item (for

example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select EHC Global Options Maintenance.

3. Select avamar_replication_port.

4. Set the value to a different port.

If Dell EMC Data Domain has been added to the environment, enable Data Domain to

ensure backup settings are optimized:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Global Options Maintenance catalog item (for

example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select EHC Global Options Maintenance.

3. Select the data_domain_available option and set the value to Yes.

If you change your ViPR project name, update the object model with the new name:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Global Options Maintenance catalog item (for

example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select EHC Global Options Maintenance.

3. Select the default_vipr_project option and click Next.

4. Select the new ViPR project name from the list box.

5. Click Next, and then click Submit.

Overview

Enable CA

Modify Avamar

replication port

Enable Data

Domain

Modify the

default ViPR

project

Chapter 3: Environment Configuration

14 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Note: The project must exist in ViPR.

If data protection tasks time out because of latency or high wait times, increase the default

timeout:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Global Options Maintenance catalog item (for

example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select EHC Global Options Maintenance.

3. Select dp_task_completion_max_wait_time and type the updated value in seconds.

To set the polling interval for data protection tasks:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Global Options Maintenance catalog item (for

example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select EHC Global Options Maintenance.

3. Select dp_task_polling_time and type the updated value.

If multiple physical arrays provide physical storage pools of the same service level to Dell

EMC VPLEX through different ViPR virtual pools, use the virtual pool collapser (VPC)

function to ensure that all LUNs provisioned across those physical pools are collapsed

into the same storage reservation policy (SRP).

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Global Options Maintenance catalog item (for

example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select EHC Global Options Maintenance.

3. Select ehc_vpc_disabled and select Yes or No.

Modify data

protection task

wait times

Modify the data

protection

polling time

Modify the

virtual pool

collapser

function

Chapter 3: Environment Configuration

15 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Enable the policy to present hardware island names in the SRP names in vRealize

Automation. This functionality is useful if you have multiple hardware islands per site and

want to have control of the destination of a virtual machine.

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Global Options Maintenance catalog item (for

example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select EHC Global Options Maintenance.

3. Select hwi_srp_policy_enabled and select Yes or No.

To choose the log level for VMware vRealize Orchestrator logging or change the log level

if debugging issues (the default is Info.):

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Global Options Maintenance catalog item (for

example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select EHC Global Options Maintenance.

3. Select log_level and select the required level.

Create a list of Host LUN Units (HLUs) to exclude from use by ViPR. This functionality is

useful when certain HLUs are used for SAN boot.

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Global Options Maintenance catalog item (for

example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select EHC Global Options Maintenance.

3. Select san_boot_hlu.

4. Type the HLU value that you want to reserve and click the green plus sign.

5. Click Submit.

Managing environment connections

Use the Connection Maintenance catalog item to update Enterprise Hybrid Cloud

connections, in the Enterprise Hybrid Cloud object model, that were created when the

environment was first initialized. This functionality is useful for managing the password

lifecycle.

Note: Passwords are updated in the object model only. Update them in other locations manually

(for example, Active Directory, service accounts, and so on).

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Connection Maintenance catalog item (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Connection Maintenance.

Enable the

hardware island

name in the

storage

reservation

name

Modify the

environment

logging level

Reserve HLUs

for SAN boot

Modify Active

Directory details

Chapter 3: Environment Configuration

16 Enterprise Hybrid Cloud 4.1.2 Administration Guide

3. Select ActiveDirectoryConnection and modify the details.

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Connection Maintenance catalog item (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Connection Maintenance.

3. Select DPAConnection and modify the details.

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Connection Maintenance catalog item (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Connection Maintenance.

3. Select IAASConnection and modify the details.

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Connection Maintenance catalog item (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Connection Maintenance.

3. Select NSXConnection and modify the details.

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Connection Maintenance catalog item (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Connection Maintenance.

3. Select SMTPConnection and modify the details.

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Connection Maintenance catalog item (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Connection Maintenance.

3. Select SOAPConnection and modify the details.

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Connection Maintenance catalog item (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Connection Maintenance.

3. Select SQLConnection and modify the details.

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Connection Maintenance catalog item (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Connection Maintenance.

3. Select ViPRConnection and modify the details.

Modify Data

Protection

Advisor details

Modify vRealize

Automation IaaS

web VIP details

Modify VMware

vCenter NSX

details

Modify SMTP

server details

Modify Simple

Access Object

Protocol (SOAP)

server details

Modify SQL

Server

details

Modify ViPR

details

Chapter 3: Environment Configuration

17 Enterprise Hybrid Cloud 4.1.2 Administration Guide

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Connection Maintenance catalog item (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Connection Maintenance.

3. Select vRAConnection and modify the details.

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Connection Maintenance catalog item (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Connection Maintenance.

3. Select vROConnection and modify the details.

Managing sites

In the Enterprise Hybrid Cloud object model, sites are the first item to be created and all

other items ultimately depend on one or more sites. A site is a label that is given to a

physical site. The site maintenance catalog item enables the administrator to change site

objects.

Note: For information about the maximum number of sites, refer to the Enterprise Hybrid Cloud

4.1.2 Concepts and Architecture Guide.

To perform site maintenance:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Maintenance catalog items (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Site Maintenance, as shown in Figure 2.

Figure 2. Site Maintenance catalog item

Modify vRealize

Automation

details

Modify vRealize

Orchestrator

details

Chapter 3: Environment Configuration

18 Enterprise Hybrid Cloud 4.1.2 Administration Guide

3. Under Request Information, type a description, optionally type a reason, and click Next, as shown in Figure 3.

Figure 3. Site Maintenance: Request Information

4. Select an action from the list, as shown in Figure 4.

Figure 4. Site Maintenance: Action Choice

Prerequisites

While there are no physical prerequisites for adding a site to the object model, we assume

that the corresponding physical site exists.

Figure 5 shows the required steps to add a site.

Figure 5. Example flowchart: Add a site

Prerequisites Add a site

Add a site

Chapter 3: Environment Configuration

19 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Catalog Item description

Table 2 describes the Add Site catalog item requirements.

Table 2. Add Site Options

Parameter Description

Site Name A free-text field that is verified to ensure no duplication occurs of an existing site name.

Catalog Item description

Table 3 describes the Update Site catalog item requirements.

Table 3. Update Site options

Parameter Description

Site Select an existing site from the list.

New Site Name Editing a site name is only permitted if the site is not referenced elsewhere in the Enterprise Hybrid Cloud object model. Otherwise, a list of references that need to be updated or deleted before editing is presented to the administrator.

Catalog Item description

Table 4 describes the Delete Site catalog item requirements.

Table 4. Delete Site options

Parameter Description

Site Select an existing site from the list.

Confirm Select Confirm or Deny, as required. Deleting a site name is

only permitted if that name is not referenced elsewhere in the Enterprise Hybrid Cloud object model. Otherwise, a list of references that must be updated or deleted first is presented to the administrator.

Managing vCenters

Enterprise Hybrid Cloud supports up to four VMware vCenter endpoints, which are

managed by Enterprise Hybrid Cloud. Each managed vCenter can be configured as a

vRealize Automation vCenter endpoint to provide Enterprise Hybrid Cloud services. An

additional six IaaS-only vCenter endpoints may be added for a maximum of 10 vCenters.

The vCenter maintenance catalog item enables the administrator to change vCenter

objects.

To perform vCenter endpoint maintenance:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Maintenance catalog items (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select vCenter Endpoint Maintenance, as shown in Figure 6.

Update a site

Delete a site

Chapter 3: Environment Configuration

20 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 6. vCenter Endpoint Maintenance catalog item

3. Under Request Information, type a description, optionally a reason, and click Next, as shown in Figure 7.

Figure 7. vCenter Endpoint Maintenance: Request Information

4. Select the operation you want to perform from the list, as shown in Figure 8.

Figure 8. vCenter Endpoint Maintenance: Action Choice

Chapter 3: Environment Configuration

21 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Prerequisites

The vCenter must exist.

The vCenter must be added to the vRealize Orchestrator vCenter plug-in.

Figure 9 shows the required steps to add a vCenter.

Figure 9. Example flowchart: Add a vCenter

Catalog Item description

Table 5 describes the Add vCenter catalog item requirements.

Table 5. Add vCenter options

Option Description

Name for vCenter endpoint Add a user-friendly name for the vCenter.

Select VC FQDN to add Select a Fully Qualified Domain Name (FQDN) with values from the vRealize Orchestrator vCenter plug- in. vCenters that are already added to the object model are not shown.

New vCenter Associated Sites Select up to two sites from a list of on-boarded sites.

Select Datacenter to Add Select a single datacenter from the list of datacenters that are discovered in the chosen vCenter.

Prerequisites Add a site Add a

vCenter

Add a vCenter

Chapter 3: Environment Configuration

22 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Catalog Item description

Table 6 describes the Updated vCenter catalog item requirements.

Table 6. Update vCenter Options

Parameter Description

vCenter Select a vCenter from the list box of previously added vCenters.

New vCenter nameEdit this parameter only if it is not referenced by any cluster or hardware island. If it is part of a DR pair relationship, you must also update its partners dr_partner_name.

FQDNSelect an alternate vCenter FQDN from the list of vCenters presented by the vRealize Orchestrator plug-in. vCenters that are already added are not shown. Edit this parameter only if the vCenter is not referenced by any hardware islands or clusters.

Datacenter Edit this parameter only if the vCenter is not referenced by any hardware islands or clusters associated with the same vCenter.

SitesEdit this parameter only if it is not referenced by any hardware islands or clusters that are associated with the same vCenter.

Note: A vCenter object may only be deleted if not referenced by any other objects (clusters,

hardware islands, or other vCenters).

Catalog Item description

Table 7 describes the Delete vCenter parameters.

Table 7. Delete vCenter options

Parameter Description

vCenter Select a vCenter from the list of previously- added vCenters.

Confirm Select Confirm or Deny, as required.

Managing vCenter relationships

The vCenter Relationship Maintenance catalog item allows you to change the

relationships between vCenters in the Enterprise Hybrid Cloud object model. vCenters

that participate in DR relationships require a relationship in the object model to enable and

control the availability of DR services.

To perform vCenter relationship maintenance:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Maintenance catalog items (for example, ehc_config_admin@domain.local).

Update a vCenter

Delete a vCenter

Chapter 3: Environment Configuration

23 Enterprise Hybrid Cloud 4.1.2 Administration Guide

2. Go to Catalog > EHC Configuration and select vCenter Relationship Maintenance, as shown in Figure 10.

Figure 10. vCenter Relationship Maintenance catalog item

3. Under Request Information, type a description, optionally type a reason, and click Next.

4. Under Action Choice, select the operation that you want to perform, as shown in Figure 11.

Figure 11. vCenter Relationship Maintenance: Action Choice

Chapter 3: Environment Configuration

24 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Prerequisites

Both vCenters must exist.

Both vCenters must be added to the vRealize Orchestrator vCenter plug-in.

Cross VMware vCenter NSX must be configured.

RecoverPoint for Virtual Machines must be configured.

Figure 12 shows the required steps to add a vCenter relationship.

Figure 12. Example flowchart: Add a vCenter Relationship

Catalog item description

To add a RecoverPoint for Virtual Machines vCenter relationship, supply information

about each vCenter and its associated components.

Table 8 describes the available vCenter parameters.

Table 8. Add RecoverPoint for Virtual Machines vCenter relationship: vCenter Information

Parameter Description

Protected vCenter Select the protected vCenter from the list. Only vCenters already added in the object model are shown.

Protected vCenter Username Type a vCenter username (for example,

app_vro_vcenter@domain.local).

Protected vCenter Password Enter a vCenter password.

Recovery vCenter Select the recovery vCenter. Only vCenters already added in the object model are shown.

Recovery vCenter Username Enter a vCenter username (for example,

app_vro_vcenter@domain.local).

Recovery vCenter Password Enter a vCenter password.

Note: The recovery vCenter must be on a different site from the protected vCenter.

Prerequisites Add first site Add first vCenter

Add partner site

Add partner vCenter

Add vCenter Relationship

Add a Dell EMC

RecoverPoint for

Virtual Machines

vCenter

relationship

Chapter 3: Environment Configuration

25 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Table 9 describes the parameters that are available for NSX Manager host configurations.

Table 9. Add RecoverPoint for Virtual Machines vCenter relationship: NSX Manager host configurations

Parameter Description

NSX Available Select if NSX is being used.

Protected site NSX endpoint Name Enter a friendly name for the protected site NSX endpoint.

Type Protected site NSX manager URL Enter the protected site NSX manager URL.

Protected site NSX manager username. Enter a username for the protected site NSX manager (for example,

app_vro_nsx@domain.local).

Protected site NSX manager password. Enter an NSX manager password.

Recovery site NSX endpoint Name Enter a friendly name for the recovery site NSX manager.

Type Recovery site NSX manager URL Enter the URL of the recovery site NSX manager.

Recovery site NSX manager username. Enter the recovery site NSX manager username

(for example, app_vro_nsx@domain.local).

Recovery site NSX manager password. Enter the password for the recovery site NSX manager.

Prerequisites

Both vCenters must exist.

Both vCenters must be added to the vRealize Orchestrator vCenter plug-in.

When vCenters are added to the object model, they must be associated with different sites.

NSX must be configured (if being used).

VMware vCenter Site Recovery Manager must be configured.

Figure 13 shows the required steps to add a vCenter relationship.

Figure 13. Example flowchart: Add a vCenter relationship

Prerequisites Add first site Add first vCenter

Add partner site

Add partner vCenter

Add vCenter Relationship

Add a VMware

vCenter Site

Recovery

Manager DR

vCenter

relationship

Chapter 3: Environment Configuration

26 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Catalog item description

To add a vCenter Site Recovery Manager DR vCenter relationship, provide information

about each vCenter and associated components.

Table 10 describes the parameters that are available for vCenter Information.

Table 10. Add vCenter Site Recovery Manager DR vCenter relationship: vCenter Information

Parameter Description

Protected vCenter Select the protected vCenter. Only vCenters already added are shown.

Protected vCenter Username Type a vCenter username (for example,

app_vro_vcenter@domain.local).

Protected vCenter Password Type a vCenter password.

Recovery vCenter Select the recovery vCenter. Only vCenters already added in the object model are shown.

Recovery vCenter Username Type a vCenter username (for example,

app_vro_vcenter@domain.local).

Recovery vCenter Password Type a vCenter password.

Table 11 describes the parameters that are available for NSX Manager host

configurations.

Table 11. Add vCenter Site Recovery Manager vCenter relationship: NSX Manager host configurations

Parameter Description

NSX Available Select if NSX is being used.

Protected site NSX endpoint Name Type a friendly name for the protected site NSX endpoint.

Type Protected site NSX manager URL Type the protected-site NSX manager URL.

Protected site NSX manager username Type a username for the protected-site NSX manager (for example,

app_vro_nsx@domain.local).

Protected site NSX manager password Type the password for the account (for

example, app_vro_nsx@domain.local).

Recovery site NSX endpoint Name Type a friendly name for the recovery-site NSX manager.

Type Recovery site NSX manager URL Type the recovery-site NSX manager URL.

Recovery site NSX manager username Type the recovery-site NSX manager username

(for example, app_vro_nsx@domain.local).

Recovery site NSX manager password Type the password for the account (for

example, app_vro_nsx@domain.local)

Chapter 3: Environment Configuration

27 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Table 12 describes the parameters that are available for vCenter Site Recovery Manager

plug-in information.

Table 12. Add vCenter Site Recovery Manager DR vCenter relationship: vCenter Site Recovery Manager plug-in information

Parameter Description

Select Protected SRM Site Select the protected vCenter Site Recovery Manager site.

Username Type a username for the protected-site vCenter Site Recovery Manager server (for example,

app_vro_srm@domain.local).

Password Type the password for the account defined above (for

example, app_vro_srm@domain.local)

Select Recovery SRM Site Select the recovery vCenter Site Recovery Manager site.

Username Type a username for the recovery-site vCenter Site Recovery Manager server (for example,

app_vro_srm@domain.local).

Password Type the password for the account defined above (for

example, app_vro_srm@domain.local)

Table 13 describes the parameters that are available for vCenter Site Recovery Manager

SQL Server site Information.

Table 13. Add vCenter Site Recovery Manager DR vCenter relationship: vCenter Site Recovery Manager SQL Server site information

Parameter Description

Protected SRM SQL host Name Type a friendly name for the protected-site vCenter Site Recovery Manager SQL Server.

SRM Protected Site SQL Database Host

Type the protected-site vCenter Site Recovery Manager SQL Server FQDN (for

example, sql01.domain.local).

Protected Site SQL Database Port

Type the protected-site vCenter Site Recovery

Manager SQL Server port (for example, 1433).

Select Authentication Type (Local SQL or Domain)

Select windows domain authentication.

Protected Site SQL Username Type the username for the protected-site vCenter Site Recovery Manager SQL Server for example,

app_vro_sql).

Protected Site SQL Password Type a name for the protected-site vCenter Site Recovery Manager SQL Server password.

Protected Site SQL User Domain Type the protected-site vCenter Site Recovery Manager SQL Server domain (for

example, domain.local).

Protected Site SQL Database Name

Type the protected-site vCenter Site Recovery Manager SQL Server database name (for

example, srm01).

Chapter 3: Environment Configuration

28 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Parameter Description

Recovery SRM SQL host Name Type a friendly name for the recovery-site vCenter Site Recovery Manager SQL Server.

SRM Recovery Site SQL Database Host

Type the protected-site vCenter Site Recovery Manager SQL Server FQDN (for

example, sql02.domain.local).

Recovery Site SQL Database Port

Type the recovery-site vCenter Site Recovery

Manager SQL Server port (for example, 1433).

Select Authentication Type (Local SQL or Domain)

Select windows domain authentication.

Recovery Site SQL Username Type the username for the recovery-site vCenter Site Recovery Manager SQL Server (for example,

app_vro_sql).

Recovery Site SQL Password Type the password for the recovery site vCenter Site Recovery Manager SQL Server.

Recovery Site SQL User Domain Enter recovery site vCenter Site Recovery Manager

SQL Server domain (for example, domain.local).

Protected Site SQL Database Name

Type the protected site vCenter Site Recovery Manager SQL Server database name (for

example, srm02).

Table 14 describes the parameters that are available for vCenter Site Recovery Manager

plug-in Information.

Table 14. Add vCenter Site Recovery Manager DR vCenter relationship: vCenter Site Recovery Manager SOAP information

Parameter Description

Protected SRM SOAP host Name Type a friendly name for the protected site vCenter Site Recovery Manager SOAP host

Protected SRM SOAP Host FQDN

Type the FQDN for the protected site vCenter Site

Recovery Manager server (for example,

srm01.domain.local). This parameter is used for

creating a SOAP host in vRealize Orchestrator for

execution of SOAP calls.

Username Username for the protected site vCenter Site Recovery Manager SOAP host (for

example, app_vro_srm@domain.local).

Password Password for the protected site vCenter Site Recovery Manager SOAP host

Recovery SRM SOAP host Name Type a friendly name for the recovery site vCenter Site Recovery Manager SOAP host

Recovery SRM SOAP Host FQDN

Type the FQDN for the recovery site vCenter Site Recovery Manager server. This parameter is used for creating a SOAP host in vRealize Orchestrator for execution of SOAP calls.

Chapter 3: Environment Configuration

29 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Parameter Description

Username Username for the recovery site vCenter Site Recovery Manager SOAP host (for example,

app_vro_srm@domain.local).

Password Password for the recovery site vCenter Site Recovery Manager SOAP host

A vCenter relationship can only be deleted if it has no associated clusters of type DR2S.

Catalog item description

Table 15 describes the Delete vCenter parameters that are available.

Table 15. Delete vCenter options

Parameter Description

Protected vCenter Name Select a vCenter from the list.

Recovery vCenter Name Select a vCenter from the list.

A RecoverPoint for Virtual Machines vCenter relationship can be extended with vCenter

Site Recovery Manager DR protection to allow both protection services to co-exist. This

catalog item action allows you to type vCenter Site Recovery Manager DR information,

as described in Add a VMware vCenter Site Recovery Manager DR vCenter

relationship, to extend the protection services.

Managing hardware islands

A hardware island is a concept within Enterprise Hybrid Cloud that describes an island of

compute, storage, and networking resources. The hardware island concept is the key

determining factor for configuring vSphere clusters that offer inter- or intra-site resilience.

The hardware island maintenance catalog item lets you manipulate hardware island

objects.

To perform hardware island maintenance:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Maintenance catalog items (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Hardware Island Maintenance, as shown in Figure 14.

Delete a vCenter

relationship

Add vCenter Site

Recovery

Manager DR to an

environment with

RecoverPoint for

Virtual Machines

Chapter 3: Environment Configuration

30 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 14. Hardware Island Maintenance catalog item

3. Under Request Information, type a description, optionally type a reason, and click Next.

4. Under Action Choice, select the action you want to perform, as shown in Figure 15.

Figure 15. Hardware Island Maintenance: Action Choice

Prerequisites

The vCenters must exist.

The vCenters must be added to the vRealize Orchestrator vCenter plug-in.

ViPR must be configured with virtual arrays (applicable to hardware islands with clusters that require ViPR based storage provisioning services).

Figure 16 shows the required steps to a hardware island.

Add a hardware

island

Chapter 3: Environment Configuration

31 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 16. Example flowchart: Add a hardware island

Catalog item description

Table 16 describes the add hardware island parameters that are available for Dell EMC

VxRail Appliances.

Table 16. Add hardware island options for VxRail Appliances

Parameter Description

Name A free-text field that is verified to ensure no duplication occurs of an existing hardware island name. Type a name.

vCenter A list that presents vCenter endpoints configured within the vCenters object. Choose one.

Site A list of sites associated with the chosen vCenter object. Choose one.

Table 17 describes the add hardware island parameters that are available for Dell EMC

VxRack System FLEX and Dell EMC VxBlock Systems.

Table 17. Add hardware island options for VxRack FLEX and VxBlock Systems

Parameter Description

Name A free-text field that is verified to ensure no duplication occurs of an existing hardware island name. Type a name.

vCenter A list that presents vCenter endpoints configured within the vCenters object. Choose one.

Site A list of sites associated with the chosen vCenter object. Choose one.

ViPR Instance Pre-populated with the ViPR information of the ViPR instance used in Enterprise Hybrid Cloud.

ViPR Virtual Arrays

A list of ViPR virtual arrays, filtered to exclude virtual arrays already associated with a Hardware Island. Choose vArray(s) to be associated with the new hardware island.

Prerequisites Add a site Add a vCenter

Add a hardware

island

Chapter 3: Environment Configuration

32 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Catalog item description

Table 18 describes the update hardware island parameters that are available for VxRail

Appliances.

Table 18. Update VxRail-based hardware island options for VxRail Appliances

Parameter Description

Hardware Island A list of hardware islands. Choose one.

New Name This parameter can be edited only if the hardware island is not referenced by a cluster or datastore.

vCenter This parameter can be edited only if there are no clusters mapped to the hardware island.

Site(s) This parameter can be edited only if the hardware island is not used by any cluster or datastore.

Table 19 describes the update hardware island parameters that are available for VxRack

System FLEX and VxBlock Systems.

Table 19. Update hardware island options for VxRack FLEX and VxBlock Systems

Parameter Description

Hardware Island This is a list of hardware islands. Choose one.

New Name This parameter can be edited only if the hardware island is not referenced by a cluster or datastore.

vCenter This parameter can be edited only if there are no clusters mapped to the hardware island.

Site(s) This parameter can be edited only if the hardware island is not used by any cluster or datastore.

ViPR Instance This parameter can be edited only if there are no datastores associated with the hardware island.

ViPR Virtual Arrays This parameter can be appended with additional vArrays. A vArray can be removed only if there are no datastores associated with it.

Note: If CA clusters exist, their affinity groups might need to be updated if

hwi_srp_policy_enabled is set to true. See Enable the hardware island name in the storage

reservation name for more information.

Catalog item description

Table 20 describes the delete hardware island parameters that are available.

Table 20. Delete hardware island options

Parameter Description

Hardware Island Select one from the list of hardware islands. A hardware island can only be deleted if there are no associated clusters or datastores.

Confirm Select Confirm or Deny, as required.

Update a

hardware island

Delete Hardware

Island

Chapter 3: Environment Configuration

33 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Managing RecoverPoint for Virtual Machines vRPA clusters

To enable RecoverPoint for Virtual Machines protection services in the Enterprise Hybrid

Cloud, the system administrator must onboard the virtual Dell EMC RecoverPoint

appliances (vRPAs) to the Enterprise Hybrid Cloud object model.

To onboard vRPAs:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Maintenance catalog items (for example, ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select RP4VM vRPA Cluster Maintenance, as shown in Figure 17.

Figure 17. Cluster Maintenance catalog item

3. Under Request Information, type a description, optionally type a reason, and click Next,as shown in Figure 18.

Figure 18. Cluster Maintenance: Request Information

Chapter 3: Environment Configuration

34 Enterprise Hybrid Cloud 4.1.2 Administration Guide

4. Under Action Choice, select the action you want to perform, as shown in Figure 19.

Figure 19. Cluster Maintenance: Action Choice

Prerequisites

Two vCenters must exist.

Both vCenters must be added to the vRealize Orchestrator vCenter plug-in.

A vRPA cluster must be deployed and configured at each physical site.

Each vRPA cluster must be associated with a vCenter cluster.

The vRPA clusters must not be present in the object model.

Figure 20 shows the required steps to onboard a vRPA cluster pair.

Figure 20. Example flowchart: Onboard a vRPA cluster pair

Catalog item description

1. To onboard a vRPA cluster pair, select Add Cluster Pair and click Next.

Table 21 describes the local cluster on-boarding parameters.

Table 21. vRPA cluster on-boarding parameters

Parameter Description

Primary Cluster Management IP Type the IP address of the primary vRPA cluster.

Primary Cluster Admin Username Type the primary vRPA cluster admin username (for

example, ehc_rp4vm_admin).

Primary Cluster Password Type the password for the vRPA cluster admin user

defined above (for example, ehc_rp4vm_admin).

Prerequisites Add first site Add first vCenter

Add partner site

Add partner vCenter

Add vCenter Relationship

Add a vRPA

cluster pair

Chapter 3: Environment Configuration

35 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Parameter Description

Secondary Cluster Management IP Type the IP address of the secondary vRPA cluster.

Secondary Cluster Admin Username

Type the secondary vRPA cluster admin username

(for example, ehc_rp4vm_admin).

Secondary Cluster Password Type the password for the vRPA cluster admin user

defined above (for example, ehc_rp4vm_admin).

2. Click Next to review, and then click Submit.

Managing vSphere clusters

A cluster object is created in the Enterprise Hybrid Could object model as soon as a

vSphere cluster is onboarded through the vRealize Automation catalog. When onboarding

clusters, each cluster must be given a type, which then dictates the type of storage that

can be provisioned to the cluster. The cluster maintenance catalog item allows the

administrator to manipulate cluster objects.

Table 22 shows the cluster types available in the model.

Table 22. Cluster types

Datastore type Storage description

LC1S Local Copy on One Site

VS1S VSAN Storage on One Site (not used by STaaS)

CA1S CA VPLEX Metro Storage on One Site

CA2S CA VPLEX Metro Storage across Two Sites

DR2S DR RecoverPoint Storage across Two Sites

To perform cluster maintenance:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Maintenance catalog items (for example, ehc_config_admin@domain.local).

3. Go to Catalog > EHC Configuration and select Cluster Maintenance, as shown in Figure 21.

Chapter 3: Environment Configuration

36 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 21. Cluster Maintenance catalog item

4. Under Request Information, type a description, optionally type a reason, and click Next,as shown in Figure 22.

Figure 22. Cluster Maintenance: Request Information

5. Under Action Choice, select the action you want to perform, as shown in Figure 23.

Chapter 3: Environment Configuration

37 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 23. Cluster Maintenance: Action Choice

Prerequisites

The vCenter must exist

The vCenter must be added to the vRealize Orchestrator vCenter plug-in.

The cluster must exist.

The cluster must not be present in the object model.

Figure 24 shows the required steps to onboard a local cluster.

Figure 24. Example flowchart: Onboard a local cluster

Catalog item description

1. To onboard a local cluster, select Onboard Local Cluster and click Next.

Table 23 describes the local cluster onboarding parameters.

Table 23. Local cluster on-boarding parameters

Parameter Description

Select a hardware island Select the relevant island.

Select unprepared cluster Select a cluster.

Prerequisites Add a site Add a vCenter

Add a hardware

island

Onboard a local cluster

Onboard a local

cluster

Chapter 3: Environment Configuration

38 Enterprise Hybrid Cloud 4.1.2 Administration Guide

2. Click Next to review, and then click Submit.

Prerequisites

The vCenter must exist.

The vCenter must be added to the vRealize Orchestrator vCenter plug-in.

The cluster must exist.

The cluster must not be present in the object model.

Figure 25 shows the required steps to onboard a local cluster.

Figure 25. Example flowchart: Onboard a local cluster

Catalog item description

1. To onboard a vSAN cluster, select Onboard vSAN Cluster and click Next.

Table 24 describes the local cluster on-boarding parameters.

Table 24. vSAN cluster on-boarding parameters

Parameter Description

Select a Hardware Island Select a hardware island from the list box.

Select unprepared cluster Select a cluster from the list box.

2. Click Next to review and then click Submit.

Prerequisites

The vCenter must exist.

The vCenter must be added to the vRealize Orchestrator vCenter plug-in.

During onboarding, the vCenter can be associated with one or two sites in the object model, depending on the CA configuration (single-site or dual-site).

Two hardware islands must exist.

The cluster must exist.

The cluster must not be present in the object model.

Figure 26 shows the required steps to onboard a CA cluster.

Prerequisites Add a site Add a vCenter

Add a hardware

island

Onboard a vSAN cluster

Onboard a vSAN

cluster

Onboard a CA

cluster

Chapter 3: Environment Configuration

39 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 26. Example flowchart: Onboard a CA cluster

Catalog item description

1. To onboard a CA cluster, select Onboard CA Cluster and click Next.

Table 25 describes the CA cluster on-boarding parameters.

Table 25. CA cluster on-boarding parameters

Parameter Description

Hardware Island 1 Select a hardware island.

Cluster Select a cluster.

Inter-site vs. Intra-site Choose whether the CA configuration is inter-site (dual site) or intra-site (single site).

Hardware Island 2 Select a hardware island.

Hosts for Hardware Island 1 Select hosts to be assigned to distributed resource scheduler (DRS) groups for hardware island 1.

Hosts for Hardware Island 2 Select hosts to be assigned to DRS groups for hardware island 2.

2. Click Next to review, and then click Submit.

Prerequisites

Two vCenters must exist.

Both vCenters must be added to the vRealize Orchestrator vCenter plug-in.

When vCenters are added to the object model, they must be associated with different sites.

Two hardware islands must exist.

The cluster must exist in each vCenter.

Cluster names must be unique.

The clusters must not be present in the object model.

Figure 27 shows the required steps to onboard a RecoverPoint for Virtual Machines

cluster.

Prerequisites Add a site(s) Add a vCenter

Add hardware island 1

Add hardware island 2

Onboard a CA cluster

Onboard a

RecoverPoint for

Virtual Machines

cluster

Chapter 3: Environment Configuration

40 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 27. Example flowchart: Onboard RecoverPoint for Virtual Machines cluster

Catalog item description

To onboard a RecoverPoint for Virtual Machines cluster:

1. Select Onboard Local Cluster and click Next.

Note: Enterprise Hybrid Cloud RecoverPoint for Virtual Machines protection service is

enabled on virtual machines that reside on local clusters at each physical site

Table 26 describes the RecoverPoint for Virtual Machines cluster on-boarding

parameters.

Table 26. DR cluster on-boarding parameters

Parameter Description

Hardware Island Select the primary hardware island.

Cluster Select the primary local cluster.

Partner Hardware Island Select the partner hardware island.

Partner cluster Select the partner cluster.

2. Click Next to review, and then click Submit.

Prerequisites

Two vCenters must exist.

Both vCenters must be added to the vRealize Orchestrator vCenter plug-in.

When vCenters are added to the object model, they must be associated with different sites.

Two hardware islands must exist.

The cluster must exist in each vCenter.

Cluster names must be unique.

The cluster must not be present in the object model.

Prerequisites Add site 1 Add site 2 Add vCenter 1

Add vCenter 2 Add vCenter Relationship

Add hardware island 1

Add hardware island 2

Add RP4VM vRPA Clusters

Onboard RP4VM cluster

Onboard a

VMware vCenter

Site Recovery

Manager DR

cluster

Chapter 3: Environment Configuration

41 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 28 shows the required steps to onboard a vCenter Site Recovery Manager DR

cluster.

Figure 28. Example flowchart: Onboard a VMware vCenter Site Recovery Manager DR cluster

Catalog item description

To onboard a vCenter Site Recovery Manager DR cluster:

1. Select Onboard DR Cluster, and then click Next.

Table 27 describes the DR cluster on boarding parameters.

Table 27. DR cluster on-boarding parameters

Parameter Description

Protected Hardware Island Select the protected hardware island.

Protected cluster Select the protected cluster.

Recovery Hardware Island Select the recovery hardware island.

Recovery cluster Select the recovery cluster.

2. Click Next to review, and then click Submit.

Table 28 describes the edit cluster parameters that are available for edit.

Table 28. Edit cluster parameters

Parameter Description

Select cluster Select the cluster to edit.

Select new site Edit this parameter only if there are no virtual machines or datastores associated with the cluster. Changing a site implies a change of hardware island in the same vCenter, but a different site. Site affinity groups might need manual remediation.

Prerequisites Add site 1 Add site 2 Add vCenter 1

Add vCenter 2 Add vCenter Relationship

Add hardware island 1

Add hardware island 2

Onboard a DR cluster

Edit a cluster

Chapter 3: Environment Configuration

42 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Parameter Description

Select new hardware island Edit this parameter only if there are no virtual machines or datastores associated with the cluster. Changing hardware island implies a change to a hardware island in the same vCenter and the same site. Site affinity groups may need manual remediation.

Delete clusters from the Enterprise Hybrid Cloud object model only if there are no

dependent datastores associated with that cluster.

Warning: This action is irrevocable and must not be performed unless all virtual machines and

datastores have been removed from the cluster.

Table 29 describes the available parameters.

Table 29. Delete cluster parameters

Parameter Description

Select Cluster Name Select a vSphere cluster.

Confirm Select Confirm or Deny, as required.

Remove a VMware ESXi host from a cluster

Before removing a VMware ESXi host from an Enterprise Hybrid Cloud tenant cluster, be

aware of the impact in ViPR. Also, remove the host from the ViPR export group to ensure

that the correct datastores are mounted.

Ensure that the version of SMI-S complies with the version stated in the Enterprise Hybrid

Cloud ESSM.

The following steps show the procedure for removing a host from a vSphere ESXi cluster

in vCenter and using the ViPR command line interface (CLI) to remove the same host

from the cluster Export Group.

Ensure that Auto-Exports is disabled for all clusters in VIPR; otherwise the following host

removal and add process will fail:

1. Log in to the ViPR user interface (UI) as a user with administrative permissions

(for example, ehc_vipr_admin).

2. Navigate to Physical > Clusters, click the cluster name, and then deselect Auto- Exports, as shown in Figure 29.

Delete a cluster

SMI-S Version

Remove a host

from a ViPR

Export Group

Chapter 3: Environment Configuration

43 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 29. Disabling Auto-Exports

Remove ESXi host from a vCenter cluster

1. Log in to vCenter as a user with vCenter administrator permissions (for example,

ehc_vc_admin).

2. Right click the ESXi host that you plan to remove from the cluster and select Enter Maintenance Mode, as shown in Figure 30.

Figure 30. Enter maintenance mode

3. Move the host out of the source cluster and into the target cluster, as shown in Figure 31.

Figure 31. Move ESXi host

4. Right-clicktheViPR-provisioned datastores associated with the host that you moved (drm-esxi084.infra.lab.local in this example). To remove the datastores, select Unmount, as shown in Figure 32, and then Detach, as shown in Figure 33.

Chapter 3: Environment Configuration

44 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 32. Unmount ViPR-provisioned datastores

Figure 33. Detach datastores

Rediscover vCenter server from the ViPR interface

1. Log in to the ViPR UI as a user with administrative permissions (for example,

ehc_vipr_admin).

2. Navigate to Physical > vCenters. Select the relevant vCenter and click Rediscover, as shown in Figure 34.

Figure 34. Rediscover vCenter

Chapter 3: Environment Configuration

45 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Edit the ViPR profile to enable CLI functionality

1. Connect to ViPR using Secure Shell (SSH) and log in as root.

2. Navigate to /opt/storageos/cli/ and run the following command to edit the profile:

vi viprcli.profile

3. Set VIPR_HOSTNAME to the ViPR FQDN and ensure VIPR_PORT is set to 4443, as shown in Figure 35.

Figure 35. Edit ViPR.Profile

4. Save the changes and exit vi.

Authenticate with ViPR to use CLI mode

1. Change directory to /opt/storageos/cli/bin/ and run the ./viprcli

authenticate u root d /tmp authentication command, as shown in

Figure 36.

Figure 36. Authenticate command

2. Run the ./viprcli exportgroup remove_host -n

OldExportGroupName -hl ESXi-Hostname -pr Project host removal

command, as shown in Figure 37:

Figure 37. Remove host command

Chapter 3: Environment Configuration

46 Enterprise Hybrid Cloud 4.1.2 Administration Guide

3. Navigate to Resources > Tasks to monitor the tasks progress from the ViPR UI, as shown in Figure 38.

Figure 38. Task status

Update vRealize Automation compute resources

1. Log in into the vRealize Automation Enterprise Hybrid Cloud tenant as a user with

fabric admin privileges (for example, ehc_fabric_admin).

2. Navigate to Infrastructure > Compute Resources > Compute Resources.

3. Move the mouse over the relevant Compute Resource (EHCWorkload01 in this example) and select Data Collection, as shown in Figure 39.

4. Click Request now under Inventory.

Figure 39. Data Collection

Chapter 3: Environment Configuration

47 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Perform a rediscovery of vCenter server from the ViPR interface.

1. Log in to the ViPR UI as a user with administrative permissions (for example,

ehc_vipr_admin).

2. Navigate to Physical > vCenters, select the relevant vCenter, and click Rediscover, as shown in Figure 40.

Figure 40. Rediscover vCenter

3. Connect to ViPR using SSH and log in as root.

4. Navigate to /opt/storageos/cli/bin and run the ./viprcli exportgroup add_host -n NewExportGroupName -hl ESXi-Hostname -pr Project

command, as shown in Figure 41:

Figure 41. Add Host

Note: This step adds the ESXi host to the new target Export Group in ViPR, with associated

zoning, masking, and LUN provisioning tasks being executed.

5. Navigate to Resources > Tasks to monitor the tasks progress from the ViPR UI, as shown in Figure 42.

Figure 42. Task Status

Add ESXi Host to

a ViPR Export

Group

Chapter 3: Environment Configuration

48 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Update vRealize Automation compute resources

1. Log in into the vRealize Automation Enterprise Hybrid Cloud tenant as a user with

fabric admin privileges (for example, ehc_fabric_admin).

2. Navigate to Infrastructure > Compute Resources > Compute Resources.

3. Move the mouse over the relevant Compute Resource (EHCWorkload01 in this example) and select Data Collection, as shown in Figure 43.

Figure 43. Data Collection

4. Click Request now under Inventory.

Managing datastores

Datastore objects are created in the Enterprise Hybrid Cloud object model when STaaS

workflows perform a storage provisioning operation against an on-boarded Enterprise

Hybrid Cloud cluster. The cluster type guides you to provision only suitable storage to that

cluster.

Run the Provision Cloud Storage catalog item to add new datastores. See Storage

provisioning services for more information.

Editing datastores is not supported.

Use the Datastore Maintenance catalog item to delete a datastore object from the

Enterprise Hybrid Cloud object model. Table 30 describes the parameters that are

available.

Prerequisites

The datastore must be empty.

Add a datastore

Edit a datastore

Delete a

datastore

Chapter 3: Environment Configuration

49 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Catalog item description

To delete a datastore from the Enterprise Hybrid Cloud object model:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator

with entitlements to the EHC Maintenance catalog items (for example,

ehc_config_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Datastore Maintenance, as

shown in Figure 44.

Figure 44. Datastore Maintenance catalog item

3. Under Request Information, type a description, optionally type a reason, and

then click Next.

4. Under Delete Datastore, select the datastore you want to delete and select

Confirm.

Available parameters

Note: Deletion of the physical datastore is a manual task.

Table 30. Delete datastore parameter

Parameter Description

Select Datastore Select the datastore to be deleted from the object model.

Confirm Select Confirm or Deny to complete the operation.

Chapter 4: Storage Services

50 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Chapter 4 Storage Services

This chapter presents the following topics:

Overview ............................................................................................................ 51

Storage provisioning services ......................................................................... 51

Creating resource reservations ....................................................................... 52

Storage as a Service ......................................................................................... 54

Assigning storage to business group reservations ....................................... 62

Chapter 4: Storage Services

51 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Overview

This chapter describes the storage services and the virtual machine lifecycle and

networking services available with Enterprise Hybrid Cloud. These services and the

associated use cases fall into the following categories:

Storage provisioning services

Virtual machine services

Advanced networking services

Public cloud services

This chapter focuses on the configuration and provisioning of storage and virtual machine

blueprints, as well as the provisioning of virtual machines with data protection services.

Storage provisioning services

Storage is provisioned, allocated, and consumed by different cloud users in Enterprise

Hybrid Cloud:

Storage administrators provision storage resources for consumption by other cloud users, using the storage services that are provided in the vRealize Automation service catalog.

The storage administrator selects Provision Cloud Storage under Storage

Services in the vRealize Automation service catalog. This catalog item works

dynamically with ViPR software-defined storage to discover the available storage,

based on the administrators selections through the deployment wizard, and

provides the ability to provision the following storage:

Block (Dell EMC VNXTM, Dell EMC VMAX, Dell EMC XtremIO, Dell EMC ScaleIO)

File (VNX)

Highly available (with VPLEX)

Replicated (with Dell EMC RecoverPoint)

vRealize Automation fabric group administrators assign the provisioned storage resources to business groups.

Business group managers define virtual machine storage when they create virtual machine blueprints with storage reservation policies.

End users can, depending on their entitlements, choose the storage service level when they provision their virtual machines.

Note: Storage provisioning services are not available on a VxRail Appliance because it is based

on fully pre-provisioned vSAN storage.

For the purposes of this guide, a storage administrator executes the storage services in

the vRealize Automation service catalog. In production environments, use vRealize

Automation entitlements to assign these services to other cloud administrators or users as

required.

Overview

Cloud roles and

personas

Chapter 4: Storage Services

52 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Creating resource reservations

Resource reservations are created to allocate provisioning resources in the fabric group to

a specific business group. Resource reservations allow sharing of compute resources.

To create a resource reservation, as shown in Figure 45:

1. Log in as a user with vRealize Automation infrastructure administrator privileges (for example, ehc_fabric_admin).

2. Select Infrastructure > Reservations > Reservations.

3. Select New > vSphere.

4. Enter a descriptive Name.

5. Select the appropriate vRA Tenant.

6. Select the appropriate Business Group.

7. Set the Priority.

Figure 45. Reservation information

8. Click Resources.

9. Select the relevant compute resource.

10. Allocate the required amount of memory and storage, as shown in Figure 46.

Create a

resource

reservation

Chapter 4: Storage Services

53 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 46. New Reservation: Resources

11. Click Network, select the relevant network path and, if applicable, network profile, as shown in Figure 47. If NSX is part of the solution, you can also select advanced settings such as Transport Zones and Security groups.

Figure 47. New Reservation: Network

12. Click OK.

When the request succeeds, the new reservation is created and associated with the

business group. View the properties in vRealize Automation under Infrastructure >

Resources.

Chapter 4: Storage Services

54 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Storage as a Service

Enterprise Hybrid Cloud can reserve LUN IDs for use by SAN boot hosts. By default no

LUN IDs are reserved, but this is configurable and allows for multiple exclusions by setting

the global option. See Reserve HLUs for SAN boot for more information.

Note: When enabled, all LUN IDs specified are excluded from use by ViPR when you are

provisioning to system-wide tenant resource pods.

Prerequisites

The vCenter must exist.

The vCenter must be added to the vRealize Orchestrator vCenter plug-in.

The cluster must exist.

The cluster must be present in the object mode.

Figure 48 shows the required steps to provision local storage.

Figure 48. Example flowchart: Provision local storage

Catalog item description

An Enterprise Hybrid Cloud storage administrator can provision ViPR software-defined

storage from the vRealize Automation self-service portal by selecting the Provision Cloud

Storage item from the service catalog, as shown in Figure 49.

Prerequisites Add a site Add a vCenter

Add a hardware

island

Onboard a Local cluster

Provision local storage

Set boot LUN

HLU (SAN boot

only)

Provision local

storage

Chapter 4: Storage Services

55 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 49. Provision Cloud Storage catalog item

The request to provision cloud storage requires the following inputs:

Request information

User authentication

vCenter cluster

Hardware island

Storage type: VMFS or NFS

Storage tier

Datastore size

The storage administrator selects most of these inputs from lists of items that are

determined by the cluster resources available through vCenter and the virtual pools

available in ViPR.

User authentication

Under Authentication, the requestor of this service provides their vRealize Automation

password, which is required to authenticate the request into ViPR during the storage

provisioning process. The user may optionally include a reason for the request, which

might be required if the request is subject to an approval. To provision storage using this

workflow requires the ViPR System Monitor role in ViPR.

Chapter 4: Storage Services

56 Enterprise Hybrid Cloud 4.1.2 Administration Guide

vCenter cluster

The vCenter Cluster tab displays the Choose vCenter cluster option, as shown

in Figure 50.

Figure 50. Provision Cloud Storage request: Selecting the vCenter cluster

VMware vCenter Server might be managing multiple tenant pod clusters; therefore, the

storage administrator must select the correct vCenter cluster to instruct the provisioning

operation where to assign the storage device.

Hardware island

Under Hardware Island, the storage administrator selects the relevant hardware island.

Storage type

Under Storage Type, the storage administrator selects which type of datastore is

required, based on the storage types detected in the underlying ViPR pools, as shown in

Figure 51.

Figure 51. Provision Cloud Storage request: Selecting the datastore type

A VMFS datastore type requires block storage, while NFS requires file storage. Other data

services, such as DR and CA, are displayed only if they are detected in the underlying

infrastructure.

Storage tier

Under Storage Tier, the storage administrator selects the storage tier from which the new

storage device should be provisioned. The list of available tiers reflects the virtual pools

available from the ViPR virtual array. Virtual pools can consist of XtremIO, ScaleIO, VNX,

VMAX, or VPLEX storage types.

Chapter 4: Storage Services

57 Enterprise Hybrid Cloud 4.1.2 Administration Guide

The available capacity of the virtual pool is also displayed, as shown in Figure 52.

Figure 52. Provision Cloud Storage request: Selecting the ViPR storage pool

Datastore size

Under Datastore Size, the storage administrator enters the required storage size, in GB,

as shown in Figure 53.

Figure 53. Provision Cloud Storage request: Specifying the storage size

Additional automated tasks

The storage provisioning task includes values that are dynamically assigned by the

workflows, such as the LUN and datastore name. Therefore, fields are not provided to

capture those values. The orchestration logic manages these values to ensure

consistency.

The workflow automates the vRealize Automation rediscovery of resources under the

vCenter endpoint, in addition to assigning a storage reservation policy to the new

datastore. If a matching storage reservation policy does not exist, it is created as part of

the process.

An email notifies the fabric group administrator that the storage is ready and available in

vRealize Automation. The vRealize Automation fabric group administrator must manually

reserve the new storage for use by a business group, as shown in Figure 54. See

Assigning storage to business group reservations for more information.

Figure 54. Storage reservation for vRealize Automation business group

Chapter 4: Storage Services

58 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Prerequisites

The vCenter must exist.

The vCenter must be added to the vRealize Orchestrator vCenter plug-in.

VPLEX must be configured.

The cluster must exist.

The cluster must be present in the object model.

The ViPR virtual array must exist.

Figure 55 shows the required steps to provision CA protected storage.

Figure 55. Example flowchart: Provision CA storage

Catalog item description

The storage provisioning process for CA environments differs slightly from the process for

a single site. The selection of the hardware island, as shown in Figure 56, determines

which hardware island will be the winning site in the event of a site failure. It also

determines the site affinity of the virtual machines deployed onto the storage.

Figure 56. Provision Cloud Storage request: Selecting a provisioning site

After selecting the hardware island, you are presented with the Choose vCenter cluster

option, as shown in Figure 57. Select the correct CA-enabled vCenter cluster to instruct

the provisioning operation where to assign the storage device.

Prerequisites Add a site Add a vCenter

Add a hardware

island

Onboard a CA cluster

Provision CA storage

Provision CA

protected

storage

Chapter 4: Storage Services

59 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 57. Provision Cloud Storage request: Selecting the vCenter cluster for CA-enabled storage

In this example, the vCenter cluster was configured with descriptive tags during

implementation, making it easy to identify the CA-enabled vCenter cluster. The selected

cluster is a single-site CA cluster in New York.

Storage type

When you choose a CA-enabled vCenter cluster, Storage Type is filtered to CA-enabled

storage. In this case, only VMFS CA-Enabled is applicable, as shown in Figure 58.

Figure 58. Provision Cloud Storage request: Selecting the datastore type for CA-enabled storage

In this example, a single ViPR virtual pool, based on Dell EMC VPLEX Metro, from

which to provision storage is available. That pool, along with its available capacity, is

displayed under Storage Tier, as shown in Figure 59.

Figure 59. Provision Cloud Storage request: Selecting the ViPR storage pool for CA- enabled storage

You can then type the required datastore size and, when provisioning is complete,

continue to configure the appropriate business group reservations. See Assigning storage

to business group reservations for more information.

Prerequisites

Two vCenters must exist.

Both vCenters must be added to the vRealize Orchestrator vCenter plug-in.

When vCenters are added to the object model, they must be associated with different sites.

Provision Dell

EMC

RecoverPoint

DR-protected

storage

Chapter 4: Storage Services

60 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Two hardware islands must exist (one per site).

The clusters must exist in vCenter.

The clusters must be present in the object model.

The ViPR virtual array must exist for each site.

The VMware vCenter Site Recovery Manager recovery group is created and contains both clusters.

Figure 60 shows the required steps to provision DR-protected storage.

Figure 60. Example flowchart: Provision DR-protected storage

Catalog item description

The storage provisioning process for DR environments is slightly different from the

process for a single site.

After selecting a provisioning site, the storage administrator is presented with the Choose

vCenter Cluster option, as shown in Figure 61, which displays only clusters on the

selected provisioning site. The storage administrator must select a DR-enabled cluster as

the target to provision the DR-protected storage.

Figure 61. Selecting the DR-protected tenant pod (vCenter cluster)

The Storage Type option lists the types of datastores that are available for provisioning,

based on the type of storage in the underlying infrastructure. If the selected tenant pod is

Prerequisites Add 2 sites Add 2 vCenters

Add 2 hardware

islands

Onboard a DR cluster pair

Provision DR storage

Chapter 4: Storage Services

61 Enterprise Hybrid Cloud 4.1.2 Administration Guide

configured for DR services, then only DR-enabled VMFS storage is presented as an

available option, as shown in Figure 62.

Figure 62. Provision Cloud Storage request: Selecting the required storage type

The storage administrator then selects the storage tier offering from which the new

datastore is to be provisioned. To expose the underlying recovery point objective (RPO) to

the storage administrator, make sure the ViPR pool includes the RPO in its name, as

shown in Figure 63.

Each tier of DR-enabled storage has a predetermined RPO. The storage administrator

selects a tier that supports the RPO required for the storage that is being provisioned.

Figure 63. Provision Cloud Storage request: Selecting the storage tier and RPO

The storage administrator can then type the required datastore size. The newly

provisioned storage is then automatically associated with the corresponding SRP, as

shown in Figure 64.

Figure 64. ViPR storage tiers and corresponding vRealize Automation reservation policies

Chapter 4: Storage Services

62 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Automatic addition of the new datastore to a protection group

When the new datastore is provisioned, the workflow creates a corresponding protection

group and adds the newly created datastore to that protection group. The workflow then

adds the protection group to the recovery plan that corresponds to the compute cluster

where the storage is provisioned, as shown in Figure 65. These steps ensure that any

virtual machines provisioned on the storage are replicated to the recovery site and are

protected.

Figure 65. Adding newly provisioned storage to a protection group

Rescan arrays to detect configuration changes

By default, vCenter Site Recovery Manager checks arrays for changes to device

configurations by rescanning arrays every 24 hours. However, you can force an array

rescan at any time.

You can reconfigure the frequency with which vCenter Site Recovery Manager

performs regular array scans by changing the storage.storagePingInterval option in Advanced Settings. See Site Recovery Manager Administration for more information.

Note: Before adding a newly provisioned datastore to a vRealize Automation reservation, ensure

that the datastore has been discovered by vCenter Site Recovery Manager.

If provisioning multiple DS, we recommend that you wait until the last datastore has completed

deploying before performing the SRA rediscovery.

Assigning storage to business group reservations

After the newly provisioned storage is protected, the vRealize Automation fabric

administrator can configure reservations on the storage for the appropriate business

group.

Business group managers can set the storage policy for a virtual machine and, if

appropriate, allow end users to view and change the policy.

Business group managers set the storage type for the virtual machine disks when they

create a virtual machine blueprint by applying the appropriate storage reservation policy to

each of the virtual disks, as shown in Figure 66.

Set the virtual

machine storage

policy

Chapter 4: Storage Services

63 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 66. Setting the storage reservation policy for virtual machine disks

When the storage reservation policy is set, the blueprint always deploys the virtual

machine and its virtual disks to the specified storage type.

To enable more user control at deployment time, the business group manager can select

the Allow users to see and change storage reservation policies option, which permits

business group users to reconfigure the storage reservation policies at deployment time.

Chapter 5: Virtual Machine Lifecycle

64 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Chapter 5 Virtual Machine Lifecycle

This chapter presents the following topics:

Virtual machine lifecycle .................................................................................. 65

Continuous availability ..................................................................................... 70

VMware vCenter Site Recovery Manager disaster recovery .......................... 71

RecoverPoint for Virtual Machines .................................................................. 75

Virtual machine encryption .............................................................................. 82

Onboarding a VxRail Appliance endpoint ....................................................... 94

Chapter 5: Virtual Machine Lifecycle

65 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Virtual machine lifecycle

This section provides an overview of some of the more common tasks in the lifecycle of

virtual machines in Enterprise Hybrid Cloud.

A blueprint must be created for a virtual machine before the machine can be provisioned

from the vRealize Automation service catalog. A blueprint contains the complete

specification for a virtual machine, defining the machines attributes, policy, and

management settingsincluding any approvals required, expiration date, and owner

operationsand the manner in which the machine is provisioned.

When users provision a machine using the self-service portal, the machine is provisioned

according to the specifications of the associated blueprint.

Blueprints can be single-machine or multi-machine and can include multitier enterprise

applications that require multiple components (application, database, and web). A multi-

machine blueprint contains multiple individual machine blueprints.

When a virtual machine is provisioned, it is deployed from a vSphere virtual machine

template and customized within a vRealize Automation virtual machine blueprint.

Tenant administrators can create a global blueprint, which can be made available to all

business groups, or a local blueprint, which is available only to a single business group.

Business group managers can create blueprints for only the business groups for which

they are responsible.

Prerequisites

The vCenter must exist.

The vCenter must be added to the vRealize Orchestrator vCenter plug-in.

The virtual machine template must exist in vCenter.

Figure 67 shows the required steps to provision a virtual machine.

Figure 67. Example flowchart: Provision storage virtual machine

Prerequisites Add a site Add a vCenter Add a hardware

island

Onboard a local cluster

Provision local storage

Add local storage to

reservation

Create local blueprint

Virtual machine

blueprints

Provision a

virtual machine

Chapter 5: Virtual Machine Lifecycle

66 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Creating a local blueprint

To create a virtual machine blueprint in the vRealize Automation console:

1. Log in as a user with vRealize Automation tenant administrator or business group manager privileges.

2. Select Design > Blueprints.

3. Select New.

4. In the New Blueprint window, provide the required information under the following tabs:

General

NSX Settings

Properties

Each tab contains input fields that combine to define the final blueprint.

5. Click OK.

Design Canvas

The design canvas enables you to define and customize the new blueprint properties:

1. Under Categories, click Machine Types.

2. Select vSphere Machine and then drag it to the design canvas to customize it, as shown in Figure 68.

Chapter 5: Virtual Machine Lifecycle

67 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 68. Creating a virtual machine blueprint

Build Information

Under Build Information, the blueprint type is Server and the action is Clone, which

means that virtual machines deployed from this blueprint leverage an existing template in

vSphere. You can select the required template from the Clone from list, as shown in

Figure 69.

Chapter 5: Virtual Machine Lifecycle

68 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 69. Selecting a vSphere template for cloning

The virtual machine inherits the minimum required resources that are defined within the

virtual machine template. You can set the blueprint to allow these values to be increased

to the maximum value at a later time. Figure 70 shows how to set the maximum values for

the machine resources and specify the storage service level (Storage Reservation

Policy) to be used.

Figure 70. Specifying build information for a new blueprint

In this example, the minimum machine resources are inherited from the vSphere template

and the maximum values have been manually increased from the minimum values. At

deployment time, this virtual machine can be configured with resources up to the

maximum values.

Properties

The Properties tab can contain build profiles that consist of a set of properties that you

can apply to a machine when it is provisioned.

You can publish the virtual machine blueprint and, using vRealize Automation service

entitlements, make it available to end users as a catalog item in their self-service portal,

as shown in Figure 71.

Chapter 5: Virtual Machine Lifecycle

69 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 71. Deploying a new virtual machine blueprint from the self-service portal

To provision the virtual machine, you can request the virtual machine from the service

catalog, as shown in Figure 72.

Figure 72. Specifying request information for a virtual machine

The request process can require user input to confirm the number of virtual machines to

be provisioned and any increases in CPU, memory, and storage. The blueprint controls

these settings, which can be configured as required.

Figure 73 shows how to select the storage service level for the virtual machine by

selecting the corresponding vRealize Automation storage reservation policy.

Figure 73. Selecting the storage reservation policy for a virtual machine

Click Submit after the virtual machine is configured to initiate the provisioning process,

which can be viewed under the Requests tab.

You can configure the provisioning process to include approval operations, either with

vRealize Automation or with integrated third-party approval or ticketing systems.

Chapter 5: Virtual Machine Lifecycle

70 Enterprise Hybrid Cloud 4.1.2 Administration Guide

After the provisioning process is complete, you can access the virtual machine from the

Items menu in the vRealize Automation console.

Continuous availability

Prerequisites

The vCenter must exist.

The vCenter must be added to the vRealize Orchestrator vCenter plug-in.

VPLEX must be configured.

The cluster must exist.

The cluster must be present in the object model.

The ViPR virtual array must exist.

The virtual machine template must exist.

Figure 74 shows the required steps to provision a CA-protected virtual machine.

Figure 74. Example flowchart: Provision CA-protected virtual machine

Single site CA

In a CA configuration, the preferred hardware island is selected during storage

provisioning. See Provision CA protected storage for more information.

Note: In the case of single-site CA, both hardware islands reside on the same geographical site.

Users can also set the preferred hardware island during virtual machine deployment, if the

option to do so has been enabled by the administrator, by choosing a storage reservation

policy in vRealize Automation during virtual machine deployment.

Prerequisites Add sites Add a vCenter Add hardware

islands

Onboard a CA cluster

Provision CA storage

Provision CA protected

virtual machine

Provision a CA

protected virtual

machine

Chapter 5: Virtual Machine Lifecycle

71 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Setting a preferred hardware island during virtual machine deployment

Note: The following example is applicable when a user is permitted to select the storage

reservation policy for the virtual machine at deployment time. The virtual machine storage

reservation policy can also be set and locked in the virtual machine blueprint, in which case the

virtual machine always has its preferred hardware island set to the hardware island specified in

the policy.

Figure 75 shows how a user sets site affinity by selecting a storage reservation policy

when deploying a virtual machine.

Figure 75. Setting site affinity while deploying a virtual machine

As part of the deployment process, the virtual machine is added to the vSphere host

affinity group for the selected site.

VMware vCenter Site Recovery Manager disaster recovery

To support vCenter Site Recovery Man-based DR protection, the SRM configuration must

include resource mappings for resource pools, folders and network objects between the

vCenter Server instance on the protected site and the vCenter Server instance on the

recovery site.

These mappings enable you to define automated recovery plans to fail over application

workloads between the sites according to defined recovery time objectives (RTOs) and

recovery point objectives (RPOs). Configure the settings on both the protected and

recovery sites to support application workload recovery between the two sites.

Note: When failover occurs with the SRM-based DR protection service, all Layer 3 networks

associated with the protected cluster fail over entirely. Active machines in a specified Layer 3

network must reside only in the site with the "permit" route redistribution policy.

A placeholder datastore must be accessible to the compute clusters that support the DR

services. The placeholder datastore must be configured in vCenter Site Recovery

Manager and must be associated with the compute clusters.

A protection group is the unit of failover in vCenter Site Recovery Manager.

Enterprise Hybrid Cloud supports failover at a Workload Pod level.

Site mappings

Placeholder

datastore

Protection

groups

Chapter 5: Virtual Machine Lifecycle

72 Enterprise Hybrid Cloud 4.1.2 Administration Guide

In the context of the SRM-based DR protection, two workload Pods are assigned to a DR

cluster pair. One pod is at the primary site and is the protected cluster. The second pod is

at the alternate site and is the recovery cluster. All protection groups associated with a DR

cluster pair and all the virtual machines running on a particular pod must fail over together.

With SRM-based DR protection, there is a 1:1 mapping between a DR cluster pair and a

recovery plan. Each recovery plan contains one or more protection groups.

Each protection group contains a single replicated vSphere datastore, and all the virtual

machines that are running on that datastore. When you deploy new virtual machines to a

Workload Pod using vRealize Automation, Enterprise Hybrid Cloud lifecycle

customizations automatically add them to the corresponding protection group so that they

fail over successfully.

Recovery plans enable administrators to automate the steps required for recovery

between the primary and recovery sites. A recovery plan may include one or more

protection groups.

You can test recovery plans to ensure that protected virtual machines recover correctly to

the recovery site.

Tenant pod recovery plans

The automated network reconvergence capabilities of vCenter Site Recovery Manager -

based DR protection for Enterprise Hybrid Cloud eliminate the need to change the IP

addresses of workload virtual machines when they fail over from one site to the other.

Instead, the tenant networks move with the virtual machines and support virtual machine

communication outside the network when on the recovery site.

When using VMware NSX, Enterprise Hybrid Cloud can automate network reconvergence

of the tenant pods and, through a custom vCenter Site Recovery Manager step in the

vCenter Site Recovery Manager recovery plan, ensure security policy compliance on the

recovery site during a failover. However, running a test vCenter Site Recovery Manager

recovery plan with NSX does not affect the production virtual machines. Because the

network convergence automation step has the required built-in intelligence, it does not

reconverge the networks in that scenario.

If non-NSX alternatives are used, then network reconvergence is not automated. The

reconvergence must be performed manually during a pause in the vCenter Site Recovery

Manager recovery plan or by an automated vCenter Site Recovery Manager task created

as part of a professional services engagement.

Note: Create a recovery plan manually for each DR-enabled workload cluster before you execute

any STaaS operations. There must be two recovery plans for a cluster pair to enable failover and

failback.

Automation pod recovery plans

Network reconvergence of the network that supports the Enterprise Hybrid Cloud

Automation Pod is a manual task regardless of the presence of VMware NSX.

Recovery plans

Chapter 5: Virtual Machine Lifecycle

73 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Note: This behavior is the solution default. A professional services engagement provides

automated network reconvergence for the Automation Pod.

The vRealize Automation self-service portal supports the provisioning of virtual machines

on storage that has vCenter Site Recovery Manager DR protection.

Prerequisites

Two vCenters must exist.

Both vCenters must be added to the vRealize Orchestrator vCenter plug-in.

When vCenters are added to the object model, they must be associated with different sites.

Two hardware islands must exist (one per site).

The clusters must exist in vCenter.

The clusters must be present in the object model.

The ViPR virtual array must exist for each site.

vCenter Site Recovery Manager must be fully configured.

Figure 76 shows the required steps to provision a DR-protected virtual machine.

Figure 76. Example flowchart: Provision DR-protected virtual machine

Users can protect their virtual machines at deployment time by selecting a storage

reservation policy that includes vCenter Site Recovery Manager DR protection, as shown

in Figure 77, which can be set and locked in the blueprint. A storage reservation policy

can also be configured to allow users to modify it for DR protection as required.

Prerequisites Add 2 sites Add 2 vCenters Add 2 hardware

islands

Onboard a DR cluster pair

Provision DR storage

Provision DR protected

virtual machine

Provision an

SRM DR-

protected virtual

machine

Chapter 5: Virtual Machine Lifecycle

74 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 77. Assigning a storage reservation policy

Selecting a storage reservation policy that has DR protection ensures that the virtual

machine is deployed on storage that is being replicated to the recovery site with the

required RPO. To restrict provisioning of machines to a subset of available reservations

such as a DR-protected cluster, you can also apply a reservation policy to the blueprint.

Protecting virtual machines with vCenter Site Recovery Manager

As shown in Figure 78, the new virtual machine is deployed on the protected vSphere

cluster and datastore that provide DR protection. The virtual machine is automatically

added to the vCenter Site Recovery Manager protection group associated with the

datastore and included in any recovery plans that include the protection group.

Figure 78. Virtual machine summary displaying the protected site

Placeholder virtual machine on the recovery site

As part of the protection process, a placeholder virtual machine that corresponds to the

deployed source virtual machine is provisioned on the recovery site, as shown in Figure

79. The placeholder virtual machine maintains the configuration properties of the source

virtual machinefor example, compute resources, folder, network, and security group.

Figure 79. Placeholder virtual machine summary on the recovery site

Chapter 5: Virtual Machine Lifecycle

75 Enterprise Hybrid Cloud 4.1.2 Administration Guide

When a recovery plan is executed, meaning that the source virtual machine is recovered

on the DR site, the source virtual machine properties are retained on the recovered virtual

machine.

Enabling virtual machine restart priority for recovery

The creator of the virtual machine blueprint can set the order, or priority, in which SRM

restarts virtual machines on the recovery site.

To enable this option, select the SRM Power On Priority Option build profile on the

Properties tab of the virtual machine blueprint.

RecoverPoint for Virtual Machines

In a dual-site/dual vCenter environment, RecoverPoint for Virtual Machines provides DR

for the virtual machines hosted on a vSphere environment. This section describes how to

set up a replication policy, subscribe to the replication policy, and make changes to

replication policy of virtual machines.

Create a replication policy

The RecoverPoint for Virtual Machines administrator creates various replication policies

based on the RPO. Users can subscribe to policies based on their RPO need.

1. Log in to the EHC Portal with the entitled user for Create an RP4VM Policy advanced service blueprint (for example, ehc_config_admin@domain.local).

2. Under Create an RP4VM Policy, click Request as shown in Figure 80.

Figure 80. Create an RP4VM Policy catalog item

3. Provide a description for the request and click Next, as shown in Figure 81.

Provision an

RecoverPoint for

Virtual Machines

protected virtual

machine

Chapter 5: Virtual Machine Lifecycle

76 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 81. Create an RP4VM request information

4. Select the replication type. For asynchronous replication, provide a policy name, journal size, and RPO information, as shown in Figure 82.

Figure 82. Create an RP4VM policy replication information

5. For synchronous replication, provide a policy name and journal size, as shown in Figure 83.

Figure 83. Create an RP4VM policy name

6. Click Submit.

Replication policy subscription

This section describes how to subscribe to a RecoverPoint for Virtual Machines replication

policy during the virtual machine provisioning as well as Day 2 operation for any existing

machines.

Chapter 5: Virtual Machine Lifecycle

77 Enterprise Hybrid Cloud 4.1.2 Administration Guide

The vRealize Automation blueprint administrator must apply the RecoverPoint for Virtual

Machines build profile to a blueprint to enable RecoverPoint for Virtual Machines

protection of virtual machines at provisioning time. Figure 84 shows the build profile.

Figure 84. RecoverPoint for Virtual Machines build profile

When users request a virtual machine from a RecoverPoint for Virtual Machines enabled

blueprint, they are prompted for the following additional information, as shown in Figure

85:

Power-on priority of the virtual machine

Whether to create a new consistency group (CG) for the virtual machine or reuse an existing CG

Replication policy, which lists the policies created by the administrator

Chapter 5: Virtual Machine Lifecycle

78 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 85. RecoverPoint for Virtual Machines enabled blueprint request

Note: When a virtual machine fails over, the source blueprint cannot be modified and virtual

machine resources cannot be changed outside the original parameters of the blueprint.

Protect an existing virtual machine with RecoverPoint for Virtual Machines

To protect an existing virtual machine with RecoverPoint for Virtual Machines, navigate to

the Items tab in vRealize Automation. Select the virtual machine you want to protect and

then select RP4VM Protect VM from the Actions list box, as shown in Figure 86.

Figure 86. Apply RecoverPoint for Virtual Machines protection to an existing VM

You are presented with the option to create a new CG or to use an existing CG. When you

create a new CG, the group name is auto populated with the virtual machine name and

provides a list from which to select the replication policy for the CG, as shown in Figure

87.

Chapter 5: Virtual Machine Lifecycle

79 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 87. Create a consistency group

If you choose to use an existing CG, the form refreshes and provides an option to select

an existing CG, as shown in Figure 88.

Figure 88. Select an existing consistency group

If there are multiple virtual machines in the CG, the boot sequence defines the order of

power-on. For example, 1 is first to power on and 5 is the last to power on. The default is

3. Refer to the RecoverPoint for Virtual Machines Product Guide for more information.

Change a consistency group

A CG allows a set of virtual machines to recover in a consistent state and is the unit of

failover with RecoverPoint for Virtual Machines.

To move a virtual machine from one CG to another:

1. Log in to the vRealize Automation portal with a username that has an entitlement to the RP4VM Change CG resource action.

2. Under Items, select the virtual machine for which you would like to change the CG. Then click the Actions menu and select RP4VM Change CG, as shown in Figure 89.

Chapter 5: Virtual Machine Lifecycle

80 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 89. RP4VM Change CG

3. Select an existing CG or select the option to create a new one, as shown in Figure 90. Type the details and click Submit.

Figure 90. Consistency group selection

Change Power-On Priority

Power-on priority of a CG specifies the power-on order of virtual machines in the CG.

Power-on priority is by ascending order. Virtual machines with priority 1 power on first.

To modify power-on priority of a virtual machine:

1. Select the virtual machine from the Items tab. Select the RP4VM Change Boot Sequence Option from the Actions menu, as shown in Figure 91.

Figure 91. RP4Vm Change Boot Sequence Action

Chapter 5: Virtual Machine Lifecycle

81 Enterprise Hybrid Cloud 4.1.2 Administration Guide

2. Select a new boot sequence from the list box, as shown in Figure 92.

Figure 92. Select new boot sequence

Delete a replication policy

When a replication policy is no longer required, it can be removed. Removing the

replication policy does not affect existing consistency groups that use the policy. You

remove the replication policy from the vRealize Orchestrator inventory and also from the

property dictionary.

To delete a replication policy:

1. Log in to the vRealize Automation portal as a user that has an entitlement to the Delete an RP4VM Policy catalog item.

2. Click Request and select the policy to delete, as shown in Figure 93.

Figure 93. Delete Replication Policy

3. Click Submit.

Remove RecoverPoint for Virtual Machines protection

When a virtual machine no longer requires replication, it can be unprotected to remove it

from a CG. If it is the last virtual machine on the CG, the group also is removed.

1. Log in to the vRealize Automation portal as a user that has an entitlement to the RP4VM Unprotect VM resource action.

Chapter 5: Virtual Machine Lifecycle

82 Enterprise Hybrid Cloud 4.1.2 Administration Guide

2. Under Items, select the virtual machine that you want to unprotect. From the Actions menu, select RP4VM Unprotect VM, as shown in Figure 94.

Figure 94. RP4VM Unprotect VM

Note: This operation is irreversible and all the journal data will be lost.

Virtual machine encryption

The Enterprise Hybrid Cloud Encryption module and Dell EMC CloudLink SecureVM

provide encryption for virtual machines. CloudLink SecureVM uses an agent that is

installed in the virtual machine to control the native operating systems encryption

technologies. The encryption keys are stored within CloudLink Center. If the key release

policies are met, the keys are returned to the virtual machine when requested. If the

policies are not met, the key request is placed in a pending state and the request must be

manually accepted or rejected.

Before a virtual machine can be encrypted, add a CloudLink Center cluster to Enterprise

Hybrid Cloud. CloudLink Center might have been deployed when the initial Enterprise

Hybrid Cloud deployment was built or deployed at a later time. If CloudLink Center was

deployed at a later time, add it as follows:

1. Log in to vRealize Orchestrator client as the vRealize Orchestrator administrator.

2. Select the Workflows tab on the left navigation pane.

3. Select Library > CloudLink SecureVM > Cluster Configuration > Add cluster.

4. Click the Start Workflow icon.

5. Type a unique name in the Cluster unique name field.

6. Type the hostname or the IP address of one server in the CloudLink Center cluster in the Cluster known server address field. Only a single value is needed. Additional servers in the cluster are discovered automatically.

7. Type the username and password of a client user in CloudLink Center in the CloudLink Center user name and CloudLink Center password fields. Client users in CloudLink Center are special users that represent a client application and are only allowed to use the CloudLink Center REST APIs.

Overview

Add a CloudLink

Center cluster

Chapter 5: Virtual Machine Lifecycle

83 Enterprise Hybrid Cloud 4.1.2 Administration Guide

When a CloudLink Center cluster is added, all existing SecureVM machine groups

appear as encryption groups in Enterprise Hybrid Cloud. These groups can be

restricted by configuring the encryption groups.

When you encrypt a virtual machine, it is automatically registered in the SecureVM

machine group associated with the encryption group. You can restrict the encryption

groups to which a business group has access. For example, a specified business group

might want all encrypted virtual machines to be associated with a specific SecureVM

machine group.

To configure encryption groups:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Encryption catalog items (for example,

ehc_encryption_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Configure Encryption Groups.

3. Under Request Information, type a description, optionally type a reason, and click Next.

4. On the Configure Encryption Groups tab, select the business group in which to configure the encryption groups.

5. Select each encryption group that members of the business group can select when encrypting a virtual machine. The No Encryption group option lets the user provisioning a virtual machine to decide not to encrypt a virtual machine, even if the blueprint is enabled for encryption.

6. Click Next to review the request.

7. On the Review and Submit tab, ensure the selections are correct and click Submit.

The Bulk Encryption Status catalog item generates and sends an email report of all

virtual machines owned by a business group. The report lists if the SecureVM agent is

installed and the encryption status for each volume in the virtual machine. You do not

have to start the virtual machine. The report contains the encryption status of the volumes

when the virtual machine was last running.

To generate the bulk encryption status report:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Encryption catalog items (for example,

ehc_encryption_admin@domain.local).

2. Go to Catalog > EHC Configuration and select Bulk Encryption Status.

3. Under Request Information, type a description, optionally type a reason, and click Next.

4. On the Bulk Encryption Status tab, select the business group for which to generate the report.

The Encryption Report field shows the entire report.

Note: If this report does not provide enough information, click Cancel to dismiss the

request without sending the email report.

Configure

encryption

groups

Bulk encryption

status

Chapter 5: Virtual Machine Lifecycle

84 Enterprise Hybrid Cloud 4.1.2 Administration Guide

5. Type a valid SMTP email address in the Target Email field and click Next to review the request.

6. On the Review and Submit tab, ensure the Target Email is correct and click Submit.

Add user entitlements to Enterprise Hybrid Cloud encryption resource actions

You can perform encryption on existing virtual machines when the correct entitlements are

granted.

To update an entitlement:

1. Log in to the vRealize Automation tenant portal as the tenant administrator (for

example, ehc_tenant_admin@domain.local).

2. From Administration, click Catalog Management and then select Entitlements.

3. Select the entitlement and click Edit.

4. From Items & Approvals, click Add for Entitled Actions.

5. Select the resource action you want, and then click OK.

6. Click Update to save changes.

Show the encryption status of a virtual machine

To show the encryption status of a virtual machine:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Encryption resource actions (for example,

ehc_encryption_admin@domain.local).

2. Select Items.

3. Select the virtual machine.

4. Select Encryption Status from Actions.

5. Under Request Information, type a description, optionally type a reason, and click Next.

The SecureVM Summary field shows the current encryption status of the virtual

machine.

Note: If this is enough information, click Cancel to dismiss the request without sending

the report by email.

6. Type a valid SMTP email address in the Target Email field and click Next.

7. On the Review and Submit tab, review the Action and Target Email fields, and then click Submit to send the encryption status report by email.

Encrypt or decrypt a virtual machines volumes

To encrypt or decrypt a virtual machines volumes:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Encryption resource actions (for example,

ehc_encryption_admin@domain.local).

2. Select Items.

Existing virtual

machine

operations

Chapter 5: Virtual Machine Lifecycle

85 Enterprise Hybrid Cloud 4.1.2 Administration Guide

3. Select the virtual machine.

4. Select Encrypt or Decrypt from Actions.

5. Under Request Information, type a description, optionally type a reason, and click Next.

6. Under Action Choice, select either the Encrypt or Decrypt action and click Next.

7. On the Encrypt tab or Decrypt tab (depending on the action selected on the previous tab), check the Volumes To Encrypt field if encrypting an unencrypted volume or check the Volumes To Decrypt field if decrypting a volume.

8. Click Next to review the request.

9. On the Review and Submit tab, review the information and click Submit to implement the encryption.

Install or Uninstall SecureVM agent

To install or uninstall SecureVM agent to or from an existing virtual machine:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Encryption resource actions (for example, ehc_encryption_admin@domain.local).

2. Select Items.

3. Select the virtual machine.

4. Select Encrypt or Decrypt from Actions.

5. Under Request Information, type a description, optionally type a reason and click Next.

6. Under Action Choice, select either Install SecureVM agent or Uninstall SecureVM and click Next.

Note: If the SecureVM agent is not installed on the virtual machine, you can only select

the Install SecureVM agent action. If the SecureVM agent is installed on the virtual

machine, you can select one of three available actions: Encrypt, Decrypt, or Uninstall

SecureVM.

7. On the Credentials tab, type the username and password of the virtual machine administrator account and click Next. The username and password are required to deploy the SecureVM agent into the virtual machine or to uninstall it.

8. If you are installing the SecureVM agent, on the Install SecureVM options tab select the encryption group and click Next.

9. On the Review and Submit tab, review the Action field, and then click Submit.

Accept or reject pending key releases

When the key release policies are not met, a key request is placed in a pending state.

To accept or reject a pending key release:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Encryption resource actions (for example,

ehc_encryption_admin@domain.local).

Chapter 5: Virtual Machine Lifecycle

86 Enterprise Hybrid Cloud 4.1.2 Administration Guide

2. Select Items.

3. Select the virtual machine.

4. Select Accept or Reject Pending Key Release from Actions.

5. Under Request Information, type a description, optionally type a reason, and click Next.

6. Under Action Choice, choose Accept or Reject for the Action field, and then click Next.

Note: The virtual machine must be in a pending state.

7. On the Review and Submit tab, select Submit.

Block or unblock a virtual machine

You can block a virtual machine when you do not want to release encryption keys for the

virtual machines volumes.

To block or unblock a virtual machine:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Encryption resource actions (for example,

ehc_encryption_admin@domain.local).

2. Select Items.

3. Select the virtual machine.

4. Select Block or Unblock VM from Actions.

5. Under Request Information, type a description, optionally type a reason, and click Next.

6. Under Action Choice tab, choose Block or Unblock for the Action field, and then click Next.

7. On the Review and Submit tab, select Submit.

Release the encryption license

When a virtual machine is encrypted, it uses a CloudLink SecureVM license. The license

is automatically released when the virtual machine is decrypted. However, the license can

be manually released if the virtual machine is powered off. When the virtual machine is

powered on, it uses a CloudLink SecureVM license automatically.

To release the encryption license:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Encryption resource actions (for example,

ehc_encryption_admin@domain.local).

2. Select Items.

3. Select the virtual machine.

4. Select Release Encryption License from Actions.

5. Under Request Information, type a description, optionally type a reason, and click Next.

6. On the Release Encryption License tab, review an Action field, and then click Submit.

Chapter 5: Virtual Machine Lifecycle

87 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Update a blueprint

A blueprint can specify that a virtual machine have encrypted volumes after provisioning.

To encrypt a virtual machine, the Enterprise Hybrid Cloud encryption module is required

and a CloudLink Center cluster must be added to the environment. See Add a CloudLink

Center cluster for more information.

To update a virtual machine blueprint in the vRealize Automation console:

1. Log in as a user with vRealize Automation tenant administrator or business group manager privileges.

2. Select Design > Blueprints.

3. Select the blueprint to edit.

4. Select the blueprint properties.

5. Select the Properties tab.

6. Select the Property Groups tab.

7. Click Add and then select CloudLink SecureVM Encryption in the Add Property Groups list.

Customize encryption properties in the blueprint

The CloudLink SecureVM Encryption property group contains four properties that control

the encryption process. Some of these properties can be customized directly in the

blueprint to lock down what you see during provisioning.

To force the use of a specific encryption group, set the blueprint properties as shown in

Table 31.

Table 31. CloudLink SecureVM Encryption property group properties

Property Description

com.emc.ehc.encryption.businessgroup Clear Show in Request and type the name of the business group for the Value.

com.emc.ehc.encryption.group Clear Show in Request and type the name of the encryption group for the Value.

To deploy the SecureVM agent in the virtual machine without prompting the user for a

username and password, set the blueprint properties as shown in Table 32.

Table 32. CloudLink SecureVM Encryption build profile credential properties

Property Description

com.emc.ehc.encryption.username Clear Show in Request and type the username of the

administrator account in the virtual machine for the Value.

com.emc.ehc.encryption.password Clear Show in Request and type the password of the

administrator account in the virtual machine for the Value. Encrypted must be cleared, otherwise the

provisioning workflows have no access to the required clear password.

Provision an

encrypted virtual

machine

Chapter 5: Virtual Machine Lifecycle

88 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Select encryption options during provisioning

When requesting a virtual machine from an encryption-enabled blueprint, the user is

prompted to supply the information described in Table 33.

Table 33. Encryption options during provisioning

Field Description

Business group List box with available business groups.

Encryption group List box with available encryption groups based on the selected business group. Selecting the value No Encryption deploys the virtual machine without

encrypting it.

VM administrator username The username of the virtual machine administrator account. The username is required to deploy the SecureVM agent into the virtual machine.

VM administrator password The password of the virtual machine administrator account. This is required to deploy the SecureVM agent into the virtual machine.

For environments that require existing virtual machines to be imported into the Enterprise

Hybrid Cloud, the vRealize Automation bulk import feature enables the import of one or

more virtual machines.

This functionality is available only to vRealize Automation users who have Fabric

Administrator and Business Group Manager privileges. The Bulk Import feature imports

virtual machines complete with defining data such as reservation, storage path, blueprint,

owner, and any custom properties.

The Enterprise Hybrid Cloud offers the ability to layer Enterprise Hybrid Cloud services

onto pre-existing virtual machines by using the bulk import process. Before beginning the

bulk import process, the following must be true:

Target virtual machines are located in an Enterprise Hybrid Cloud vCenter endpoint.

Note: This is not an additional IaaS-only vCenter endpoint if they are also present.

Target virtual machines are on the correct vRealize Automation-managed compute resource cluster and that cluster is already onboarded as an Enterprise Hybrid Cloud cluster:

In cases where DR services are required for the target virtual machines, the machines are on a DR-enabled cluster.

In cases where data protection services are required for the target virtual machines, the machines are on a cluster that is associated with an Avamar pair.

Target virtual machines are on the correct vRealize Automation-managed datastore.

In cases where DR services are required for the target virtual machines, they are on a datastore protected by Dell EMC RecoverPoint.

In cases where data protection services are required for the target virtual machines, they are on a datastore that is registered with an Avamar grid.

Import existing

virtual machines

into the

Enterprise

Hybrid Cloud

Chapter 5: Virtual Machine Lifecycle

89 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Applying data protection backup services to imported virtual machines

To apply data protection backup services to newly imported virtual machines, first create a

new blueprint with the BackupAndRestoreForBulkImport build profile.

This build profile is available after import of either of these Enterprise Hybrid Cloud

modules:

Data protection

Disaster recovery

To import existing virtual machines, first generate a CSV file containing the virtual

machines to be imported, and then edit the CSV file to specify the virtual machine

reservation details.

Virtual machine import procedure

To import the virtual machine:

1. In the vRealize Automation portal, select Infrastructure > Infrastructure Organizer > Bulk Imports.

2. Under Generate CSV File, make the following selections, as shown in Figure 95:

a. For virtual machines currently outside of vRealize Automation management, set Machines to Unmanaged.

b. Select the relevant vRealize Automation Business group, Owner, and the Blueprint created earlier.

The associated virtual machine blueprint can be created specifically for the

import or it can be an existing blueprint.

Note: Ensure that virtual machine blueprint parameters are appropriate to incoming

virtual machines and do not cause conflict. The parameters specified in the

blueprint are assigned to virtual machines that are attached to the blueprint. Pay

particular attention to lease and archive periods.

c. At Resource, select either EndPoint (for example, vCenter) or Compute Resource (for example, vSphere cluster) to locate the virtual machines to be imported.

d. At Name, depending on the resource type you have chosen, select an endpoint or vSphere cluster.

Chapter 5: Virtual Machine Lifecycle

90 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 95. Generating the CSV file containing virtual machines to be imported

3. Click OK.

4. Edit the CSV file to specify the virtual machine reservation details, as shown in Figure 96.

Figure 96. Editing the CSV file to match virtual machines and storage reservation policies

All of the values for each machine must be present in the target vRealize

Automation deployment for the import to succeed. To change the values for

reservation, storage location, blueprint, and owner for each machine that you

want to import, edit the CSV file.

Note: The storage location (which is listed in the Host To Storage column of the CSV

file) is the name of the storage device/path, not the storage reservation policy or the

name of the storage reservation for the business group. To apply DR services to newly

imported virtual machines, the storage device entered must be a DR protected datastore.

If any virtual machines are discovered and present in the CSV file that do not

need to be imported, manually set their value for ImportYes or No to No in the

first column of the CSV file.

To apply Data Protection services to newly imported virtual machines, type

epc.backup.servicelevels in the Property Name column and the backup Service

Level name in the Property Value column.

To import existing virtual machines, select the CSV file containing the virtual machines to

be imported and then begin the import, as follows:

1. In the vRealize Automation portal, navigate to Infrastructure > Infrastructure Organizer > Bulk Imports.

Chapter 5: Virtual Machine Lifecycle

91 Enterprise Hybrid Cloud 4.1.2 Administration Guide

2. Select New Bulk Import, and provide the following details:

a. Type a Name for the import and select the CSV file, as shown in Figure 97.

Figure 97. Executing the Bulk Import operation

b. At Start time, select Now or specify a date and time.

c. At Batch size, select Batch to define the total number of machines being registered at a specified time.

d. Select Ignore managed machines to omit managed machines during the import process.

e. Select Skip user validation to omit validating users during the import process.

f. Complete other options as appropriate to the import.

3. Click OK.

When the import operation is complete, the requestor receives an email notification for

each virtual machine that is successfully imported, as shown in Figure 98.

Chapter 5: Virtual Machine Lifecycle

92 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 98. Email notification of successful import of virtual machine

As shown in Figure 99, the newly imported virtual machines are immediately available in

the vRealize Automation portal to the virtual machine owner specified in the import CSV

file.

Figure 99. Imported virtual machines available in vRealize Automation portal

Cloud users can reconfigure the resources already assigned to their virtual machines as

defined by the virtual machine blueprint. When business group managers create a virtual

machine blueprint, they can restrict the scope of possible reconfiguration by a business

group user.

As a machine owner, the cloud user can make any of the following changes to a

provisioned machine:

Increase or decrease memory or number of CPUs.

Modify storage by adding, removing, or increasing the size of volumes.

Modify networks by adding, removing, or updating network adapters.

Reconfiguring an

existing virtual

machine

Chapter 5: Virtual Machine Lifecycle

93 Enterprise Hybrid Cloud 4.1.2 Administration Guide

As shown in the example in Figure 100, changes to each of these parameters are subject

to the upper limits defined in the blueprint used to provision the machine.

Figure 100. Reconfiguring virtual machine resources

The execution of the reconfiguration task can be immediate, scheduled, or queued for the

virtual machine user, as shown in Figure 101.

Figure 101. Scheduling reconfiguration of virtual machine resources

Note: A deployed virtual machines upper limit cannot be increased beyond the original maximum

set on the source blueprint, even after the limit is increased on the blueprint. Any subsequent

virtual machines deployed from the increased blueprint inherit the new limits.

When the lease on a virtual machine expires, or the machine is manually expired, the

machine is either archived or destroyed, depending on whether its blueprint specifies an

archive period.

Decommissioning

a virtual machine

Chapter 5: Virtual Machine Lifecycle

94 Enterprise Hybrid Cloud 4.1.2 Administration Guide

When the end of the archive period is reached, or if no archive period exists, the virtual

machine is decommissioned. The business group user can also manually destroy the

virtual machine, as shown in Figure 102.

Figure 102. Destroying a virtual machine

When a virtual machine is destroyed, all charges relating to it are removed from vRealize

Business. Its resources are recycled and made available to provision new machines in

vRealize Automation.

Note: DR-protected virtual machines that have expired but have not yet been decommissioned

are recovered by vCenter Site Recovery Manager during a recovery operation. After a recovery,

these virtual machines cannot be managed until they have been failed back to their original

vSphere cluster. The recommendation, where possible, is to destroy or reactivate the protected

virtual machine prior to a recovery.

Onboarding a VxRail Appliance endpoint

To onboard a VxRail Appliance as an endpoint:

1. Log in to the Enterprise Hybrid Cloud tenant portal with an account that has infrastructure administrator privileges.

2. Click the Infrastructure tab and then click Endpoints.

3. Click the New Endpoint link on the right, navigate to Virtual, and then click vSphere (vCenter). See Figure 103.

4. Type the name for the endpoint, which must match the endpoint name that was entered during the IaaS agent installation.

Note: The vCenter endpoint must be configured with the same vSphere agent endpoint

name that was used during the initial installation of the IaaS Proxy Agent roles,

otherwise, discovery fails.

5. In the Address field, type the URL of the vCenter SDK: https://vxrail01- vc01.domain.local/sdk.

6. To select the credentials, click the ellipsis and select the vCenter Server credentials, and then click OK.

Chapter 5: Virtual Machine Lifecycle

95 Enterprise Hybrid Cloud 4.1.2 Administration Guide

7. If NSX is present, enable Specify manager for network and security platform and in the resulting address field, type the URL of the NSX manager: https://nsx- mgr.domain.local.

8. To select the credentials, click the ellipsis and select the NSX manager credentials. Click OK, and then click OK again.

Figure 103. Create VxRail vCenter endpoint for vRealize Automation

13. Click OK.

Chapter 6: Data Protection

96 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Chapter 6 Data Protection

This chapter presents the following topics:

Overview ............................................................................................................ 97

Managing Avamar ............................................................................................. 97

Managing Avamar Site Relationships ............................................................ 100

Managing Avamar Replication Relationships ............................................... 103

Managing Avamar proxies .............................................................................. 107

Managing Backup service levels ................................................................... 115

Virtual machine backup lifecycle ................................................................... 121

Ensuring continuity of backup in CA failure scenarios ................................ 126

Data protection reporting ............................................................................... 132

Chapter 6: Data Protection

97 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Overview

This chapter provides information about the data protection services available with

Enterprise Hybrid Cloud. It focuses on the services available to cloud users responsible

for the administration and management of data protection services, as follows:

Data protection backup

Data protection CA

Data protection DR

Cloud infrastructure or backup administrators, as well as cloud end users, consume the

backup and recovery services available with Enterprise Hybrid Cloud.

vRealize Automation cloud administrators use their service catalog to create backup

service levels. At virtual machine deployment time, cloud users can choose, in the

vRealize Automation self-service portal, to protect their machines with a predefined

backup service level, and initiate on-demand, point-in-time backups and restores of their

virtual machines.

The following section describes the catalog services and provides an overview of some of

the infrastructural and operational tasks involved in the protection of virtual machines in

Enterprise Hybrid Cloud. Before you can take advantage of Enterprise Hybrid Cloud Data

Protection Backup, set up your environment using the Avamar maintenance catalog items

in the vRealize Automation Service Catalog.

Managing Avamar

When the data protection packages have been installed and initialized, Avamar grids are

introduced into the Enterprise Hybrid Cloud object model. The Avamar Grid Maintenance

catalog item allows the administrator to manipulate Avamar grid objects.

To perform Avamar grid maintenance:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Data Protection Services catalog items (for example, ehc_backup_admin@domain.local).

2. Go to Catalog > Data Protection Services and select Avamar Grid Maintenance, as shown in Figure 104.

Chapter 6: Data Protection

98 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 104. Avamar Grid Maintenance catalog item

3. Under Request Information, type a description, optionally type a reason, and click Next, as shown in Figure 105.

Figure 105. Avamar Grid Maintenance Request Information tab

4. Select the action you want to perform from the Select Operation Type list box, as shown in Figure 106.

Figure 106. Avamar Grid Maintenance: Choose Action

Chapter 6: Data Protection

99 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Prerequisites

The Avamar grid must be deployed and configured for authentication.

A minimum of one Avamar proxy must be deployed and registered to Avamar.

A nonreplicated datastore must exist for proxy placement.

Figure 76 shows the required steps to add an Avamar grid.

Figure 107. Example flowchart: Add Avamar Grid

Catalog item description

Table 34 describes Add Avamar Grid parameters.

Table 34. Add Avamar Grid parameters

Parameter Description

Avamar Grid Name User-friendly name for the Avamar Grid.

Avamar Grid FQDN FQDN of the Avamar Grid.

Avamar Grid Admin User Username of the admin user of the Avamar Grid (for

example, admin).

Avamar Grid Admin Password Password of the admin user of the Avamar Grid.

Registered Proxies List of proxies registered with the Avamar Grid.

Choose Site List of available sites to associate with the Avamar Grid.

Avamar SOAP Username Username of the SOAP user of the Avamar Grid (for

example, app_avamar_soap@domain.local).

Avamar SOAP Password Password of the SOAP user of the Avamar Grid.

Prerequisites Add a site Add a vCenter Add a

hardware island

Onboard a local cluster

Provision local storage

Deploy Avamar proxies

Add Avamar Grid

Add Avamar Grid

Chapter 6: Data Protection

100 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Table 35 describes the Edit Avamar Grid parameters.

Table 35. Edit Avamar Grid parameters

Parameter Description

Modify Avamar Grid details Allows the administrator to edit all values entered during the Add Avamar Grid catalog item.

Associate manually deployed Avamar proxies with Avamar Grid

Allows the administrator to select an Avamar Grid and then associate manually deployed proxies with that grid.

Set Avamar Grid to Admin FullAllows the administrator to set an Avamar grid to Admin Full when a grid is full or when maintenance operations are required. All backup operations to that grid are suspended.

An Avamar grid object can be deleted only if it is not referenced by any other objects

(clusters, hardware islands, or other vCenters).

Table 36 describes the Delete Avamar Grid parameters.

Table 36. Delete Avamar Grid parameters

Parameter Description

Avamar Grid Select an Avamar Grid from the list.

Confirm Select Confirm or Deny, as required.

Managing Avamar Site Relationships

An Avamar Site Relationship (ASR) is a relationship between sites for backup purposes.

The Avamar Site Relationship (ASR) Maintenance catalog item allows the administrator to

manipulate ASR objects.

To perform ASR maintenance:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Data Protection Services catalog items (for example,

ehc_backup_admin@domain.local).

2. Go to Catalog > Data Protection Services and select Avamar Site Relationship (ASR) Maintenance, as shown in Figure 108.

Edit Avamar Grid

Delete Avamar

Grid

Chapter 6: Data Protection

101 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 108. ASR Maintenance catalog item

3. Under Request Information, type a description, optionally type a reason, and click Next, as shown in Figure 109.

Figure 109. ASR Maintenance Request Information tab

4. Select an action to perform, as shown in Figure 110.

Figure 110. ASR Maintenance: Choose Action

Chapter 6: Data Protection

102 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Prerequisites

The Avamar grid must be deployed and configured for authentication.

A minimum of one Avamar proxy must be deployed and registered to Avamar.

A nonreplicated datastore must exist for proxy placement.

Figure 111 shows the required steps to add an ASR.

Figure 111. Example flowchart: Add an ASR

Catalog item description

Table 37 describes the ASR backup types.

Table 37. Add ASR parameters

Backup type Description

1C1VC One backup copy. One vCenter. Applicable to local virtual machines only.

MC2VC Mixed copy. Two vCenters. Applicable to environments with RecoverPoint for Virtual Machines enabled. Because RecoverPoint for Virtual Machines protection can be enabled for any local VM, the ASR for all local clusters must be assigned as MC2VC. This assignment is required because a local cluster can contain both local-only virtual machines and virtual machines protected by RecoverPoint for Virtual Machines.

2C1VC Two backup copies. One vCenter. Applicable to CA-protected virtual machines and only available when global option ca_enabled = true.

See Enable the hardware island name in the storage reservation name for more information.

2C2VC Two backup copies. Two vCenters. Applicable to SRM DR protected virtual machines and only available when global option dr_enabled = true. See Managing features and environmental defaults for more

information.

The administrator must also specify the site or sites to be associated with the ASR.

Prerequisites Add a site Add a vCenter Add a hardware

island

Onboard a Local cluster

Provision local storage

Deploy Avamar proxies

Add Avamar Grid

Add an ASR

Add an ASR

Chapter 6: Data Protection

103 Enterprise Hybrid Cloud 4.1.2 Administration Guide

You can edit an ASR object only if it is not associated with an Avamar Replication

Relationship (ARR). Table 38 describes the Edit ASR parameters.

Table 38. Edit ASR parameters

Parameter Description

Select ASR Select an ASR to edit.

Select First SiteSelect the first site you want to associate.

Select Second SiteSelect the second site you want to associate.

You can delete an ASR object only if it is not referenced by any other objects (ARRs or

vCenter Clusters). Table 39 describes the Delete ASR parameter.

Table 39. Delete ASR parameter

Parameter Description

Select ASRSelect an ASR to delete.

Managing Avamar Replication Relationships

An ARR is a relationship between as many as three Avamar grids. The ARR determines

the specific Avamar grids that are responsible for backup operations on an individual

Enterprise Hybrid Cloud workload. The Avamar Replication Relationship (ARR)

Maintenance catalog item allows the administrator to manipulate ARR objects.

To perform ARR maintenance:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Data Protection Services catalog items (for example,

ehc_backup_admin@domain.local).

2. Go to Catalog > Data Protection Services and select Avamar Replication Relationship (ARR) Maintenance, as shown in Figure 112.

Edit an ASR

Delete an ASR

Chapter 6: Data Protection

104 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 112. ARR Maintenance catalog item

3. Under Request Information, type a description, optionally type a reason, and click Next,as shown in Figure 113.

Figure 113. ARR Maintenance Request Information tab

4. Select the action you want to perform, as shown in Figure 114.

Figure 114. ARR Maintenance: Choose Action

Chapter 6: Data Protection

105 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Prerequisites

The Avamar grid must be deployed and configured for authentication.

A minimum of one Avamar proxy must be deployed and registered to Avamar.

A nonreplicated datastore must exist for proxy placement.

Figure 115 shows the required steps to add an ARR.

Figure 115. Example flowchart: Add an ARR

Catalog item description

Table 40 describes the Add ARR parameters.

Table 40. Add ARR parameters

Parameter Description

ASR Select the relevant ASR.

First Avamar Grid Select the first Avamar Grid for the ARR.

Second Avamar Grid Select the second Avamar Grid for the ARR.

Table 41 describes the Edit ARR parameters.

Table 41. Edit ARR parameters

Parameter Description

Select ARR Select an ARR to edit.

Admin FullAllows the administrator to set an Avamar grid to Admin Full when a grid is full or when maintenance operations are required. All backup operations to that grid are suspended.

Prerequisites Add a site Add a vCenter Add a hardware

island

Onboard a local cluster

Provision local storage

Deploy Avamar Proxies

Add Avamar Grid

Add an ASR Add an ARR

Add an ARR

Edit an ARR

Chapter 6: Data Protection

106 Enterprise Hybrid Cloud 4.1.2 Administration Guide

An ARR object may only be deleted if not referenced by any other objects (ARRs or

vCenter Clusters). Table 42 describes the parameter that is available.

Table 42. Delete ARR parameter

Parameter Description

Select ARRSelect an ARR to delete from the list.

This catalog item associates a cluster with an ASR. This association dictates the backup

type that is available to virtual machines deployed on the cluster.

Prerequisites

The Avamar grid must be deployed and configured for authentication.

A minimum of one Avamar proxy must be deployed and registered to Avamar.

A nonreplicated datastore must exist for proxy placement.

Figure 116 shows the required steps to associate a cluster to ASR.

Figure 116. Example flowchart: Associate a cluster to an ASR

Catalog item description

Table 43 describes the parameters that are available.

Table 43. Associate Cluster to ASR parameters

Parameter Description

Select Cluster Name Select a vSphere cluster.

Select ASR Name Select the ASR to associate with the chosen vSphere cluster.

Prerequisites Add a site Add vCenters Add hardware

islands

Onboard a cluster

Provision storage

Deploy Avamar proxies

Add Avamar Grids

Add an ASRs Add an ARRs Associate a

cluster to ASR

Delete an ARR

Associate a

cluster to an

ASR

Chapter 6: Data Protection

107 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Managing Avamar proxies

Deploy Avamar proxy virtual machines to each Enterprise Hybrid Cloud-enabled cluster to

mount VMDKs directly from the datastores on that cluster. Each cluster type has its own

proxy requirements.

To determine the required number of Avamar proxy virtual machines for an LC1S cluster,

use the following logic:

1. Identify the 1C1VC ASR to which the cluster is mapped.

2. Determine the number of ARRs associated with the clusters ASR.

3. For each ARR that is discovered, deploy a minimum of one proxy virtual machine, registered to the Avamar grid that is a member of the 1C1VC ARR.

If there is scope within the overall number of proxies that can be deployed to the

environment, we recommend two proxies for high availability, as shown in Figure

117. This number can be approximately 60 to 80 proxies per vCenter.

Figure 117. LC1S without RecoverPoint for Virtual Machines proxy example

VS1S or LC1S

clusters without

RecoverPoint for

Virtual Machines

protection

Chapter 6: Data Protection

108 Enterprise Hybrid Cloud 4.1.2 Administration Guide

To determine the required number of Avamar proxy virtual machines for an LC1S cluster,

use the following logic:

1. Identify the MC2VC ASR to which the cluster is mapped.

2. Determine the number of ARRs associated with the clusters ASR.

3. For each ARR discovered, deploy a minimum of two proxy virtual machines:

One proxy must be on the LC1S cluster on the first site and registered to the Avamar grid member of the MC2VC ARR that is on the same site.

The second proxy must be on the LC1S clusters partner cluster on the second site and registered to the Avamar grid member of the MC2VC ARR that is on the same site as the partner cluster.

If there is scope within the overall number of proxies that can be deployed to the

environment, we recommend four proxies for high availability, as shown in Figure

118. This number can be approximately 60 to 80 proxies per vCenter.

Figure 118. LC1S with RecoverPoint for Virtual Machines proxy example

Note: In this configuration, if a single Avamar instance fails without a vCenter infrastructure failure

on the same site, the second member of the ARR does not automatically back up virtual

machines. For additional resilience on each site, use an Avamar Redundant Array of Independent

Nodes (RAIN) grid. Alternatively, move workloads to the site that is fully operational to continue

using backup services.

LC1S clusters

with

RecoverPoint for

Virtual Machines

protection

Chapter 6: Data Protection

109 Enterprise Hybrid Cloud 4.1.2 Administration Guide

To determine the required number of Avamar proxy virtual machines for a CA1S cluster,

use the following logic:

1. Identify the 1C1VC ASR to which the cluster is mapped.

2. Determine the number of ARRs associated with the clusters ASR.

3. For each ARR discovered, deploy a minimum of one proxy virtual machine, registered to the Avamar grid that is a member of the 1C1VC ARR.

If there is scope within the overall number of proxies that can be deployed to the

environment, two proxies are recommended for high availability, as shown in

Figure 119. This number can be approximately 60 to 80 proxies per vCenter.

Note: The hardware island on which these proxies normally reside on the CA1S cluster is of no

importance to the backup solution. We assume that latency from either side of the half of the

CA1S cluster to the Avamar infrastructure is the same because both hardware islands are on the

same site.

Figure 119. CA1S proxy example

CA1S clusters

Chapter 6: Data Protection

110 Enterprise Hybrid Cloud 4.1.2 Administration Guide

To determine the required number of Avamar proxy virtual machines for a CA2S cluster,

use the following logic:

1. Identify the 2C1VC ASR to which the cluster is mapped.

2. Determine the number of ARRs associated with the clusters ASR.

3. For each ARR discovered, deploy a minimum of two proxy virtual machines. One proxy should be registered to each Avamar grid that is a member of the 2C1VC ARR.

If there is scope within the overall number of proxies that can be deployed to the

environment, we recommend four proxies for high availability, as shown in Figure

120. This number can be approximately 60 to 80 proxies per vCenter.

Proxies must be bound to hosts in the cluster that are physically on the same site

as the Avamar grid to which they are registered by:

Adding the proxy virtual machines to DRS virtual machine affinity groups created on a per site basis.

Adding a DRS virtual machine to host rule that sets those virtual machines to must run on the DRS host group created by the CA2S onboarding process.

No unnecessary cross-WAN backups occur because Avamar can use vStorage

APIs for data protection to add VMDKs (from the local leg of the VPLEX volume)

to proxy virtual machines bound to physical hosts on the same site as the

Avamar grid.

Figure 120. CA2S proxy example

CA2S clusters

Chapter 6: Data Protection

111 Enterprise Hybrid Cloud 4.1.2 Administration Guide

To determine the required number of Avamar proxy virtual machines for a DR2S cluster,

use the following logic:

1. Identify the 2C2VC ASR to which the cluster is mapped.

2. Determine the number of ARRs associated with the clusters ASR.

3. For each ARR discovered, deploy a minimum of two proxy virtual machines:

One proxy must be on the DR2S cluster on the first site and registered to the Avamar grid member of the 2C2VC ARR that is on the same site.

The second proxy must be on the DR2S clusters partner cluster on the second site and registered to the Avamar grid member of the 2C2VC ARR that is on the same site as the partner cluster.

If there is scope within the overall number of proxies that can be deployed to the

environment, we recommend our proxies for high availability, as shown in Figure

121. This number can be approximately 60 to 80 proxies per vCenter.

Figure 121. DR2S with RecoverPoint for Virtual Machines proxy example

Note: In this configuration, if a single Avamar instance fails without a vCenter infrastructure failure

on the same site, the second member of the ARR does not automatically back up virtual

machines. For additional resilience on each site, use an Avamar RAIN grid. Alternatively, move

workloads to the site that is fully operational to continue using backup services.

DR2S clusters

Chapter 6: Data Protection

112 Enterprise Hybrid Cloud 4.1.2 Administration Guide

A user who is assigned the data protection backup service entitlement can deploy

additional Avamar proxies.

Prerequisites

The Avamar grid must be deployed and configured for authentication.

A minimum of one Avamar proxy must be deployed and registered to Avamar.

Avamar proxies must be added to DNS.

A nonreplicated datastore must exist for proxy placement.

Figure 122 shows the required steps to deploy Avamar proxies.

Figure 122. Example flowchart: Deploy Avamar proxies

Catalog item description

To deploy Avamar proxies:

1. In the vRealize Automation service catalog, click Request on Deploy Avamar Proxy.

2. Under Request Information, type a description of the request and click Next, as shown in Figure 123.

Figure 123. Deploy Avamar Proxy request

Prerequisites Add sites Add vCenters Add hardware

islands

Onboard a cluster

Provision storage

Deploy Avamar proxies

Deploying

Avamar proxies

Chapter 6: Data Protection

113 Enterprise Hybrid Cloud 4.1.2 Administration Guide

3. Select the required action:

Select Add Proxy to add an Avamar proxy.

Select Delete Proxy to delete an Avamar proxy.

4. Under vCenter Information, type the information described in Table 44:

Table 44. Deploy Avamar proxy vCenter information parameters

Parameter Description

Cluster NameThe vSphere cluster on which to deploy the proxy

Datastore Name The vSphere datastore on which to deploy the proxy

Network Name The vSphere network on which the proxy must be connected

5. Under Proxy Information, type the information described in Table 45:

Table 45. Deploy Avamar proxy information parameters

Parameter Description

NameThe name of the proxy virtual machine in vCenter.

Avamar Proxy Path The Avamar path to the proxy using FQDN (for

example, /clients/ny-av1-p0.domain.local)

IP Address The IP address of the proxy

Subnet Mask The subnet mask of the proxy

Gateway The gateway of the proxy

DNS The DNS server of the proxy

Username The username of the proxy (the default is root)

Password The password for the user

6. Under Avamar Information, type the information described in Table 46:

Table 46. Deploy Avamar proxy Avamar information parameters

Parameter Description

Avamar Grid NameSelect an Avamar grid with which to associate the proxy.

Avamar Domain The Avamar domain with which to associate the proxy.

OVA Location The proxy OVA location on the Avamar appliance. Update the default value as required.

Chapter 6: Data Protection

114 Enterprise Hybrid Cloud 4.1.2 Administration Guide

7. Under Deployment Server Information, type the information described in Table 47:

Table 47. Deploy Avamar proxy deployment server information parameters

Parameter Description

Deployment ServerThe FQDN of the deployment server.

Username The username for the Deployment Server.

Password The password for the user.

Disable Verification Optionally, skips SSL verification. The recommended setting is No.

8. Click Next and click Submit.

When all details are submitted, a new Avamar proxy is deployed to the specified location

and is automatically registered with Avamar.

This catalog item associates a cluster with manually deployed Avamar proxies.

Prerequisites

The Avamar grid must be deployed and configured for authentication.

A minimum of one Avamar proxy must be deployed and registered to Avamar.

A nonreplicated datastore must exist for proxy placement.

Figure 124 shows the required steps to associate Avamar proxies with a cluster.

Figure 124. Example flowchart: Associate Avamar proxies with a cluster

Prerequisites Add a site Add vCenters Add a

hardware islands

Onboard a cluster

Provision storage

Deploy Avamar Proxies

Add Avamar Grids

Add ASRs Add ARRs Associate a

cluster to ASR

Associate Avamar proxies with a cluster

Associate

Avamar proxies

with a cluster

Chapter 6: Data Protection

115 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Catalog item description

Table 48 describes the parameters that are available.

Table 48. Associate Avamar proxies with vCenter parameters

Parameter Description

Select Cluster Name Select a vSphere cluster.

Registered Proxy List Select Avamar proxies to associate with the chosen vSphere cluster.

Managing Backup service levels

Backup service levels are created using the vRealize Automation Create Backup Service

Level catalog item. An IaaS user can select a backup service level when deploying a

workload or apply BaaS policies to a workload as a Day 2 operation. The Backup Service

Level Maintenance catalog item lets the administrator manipulate backup service levels.

To perform backup service level maintenance:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Data Protection Services catalog items (for

example, ehc_backup_admin@domain.local).

2. Go to Catalog > Data Protection Services and select Backup Service Level Maintenance, as shown in Figure 125.

Figure 125. Backup Service Level Maintenance catalog item

Chapter 6: Data Protection

116 Enterprise Hybrid Cloud 4.1.2 Administration Guide

3. Under Request Information type a description, optionally type a reason, and click Next,as shown in Figure 126.

Figure 126. Backup Service Level Maintenance Request Information tab

4. Select the action you want to perform, as shown in Figure 127.

Figure 127. Backup Service Level Maintenance: Choose Action

Prerequisites

vCenter Endpoint Cloud-VC01 is added to the vRealize Orchestrator vCenter plug-in.

The ViPR virtual array has been created.

Local cluster NY-HWI-1-C1 has been created in Cloud-VC01.

The Avamar grid is online.

Avamar proxies deployed.

Add a backup

service level

Chapter 6: Data Protection

117 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 128 shows the required steps to add a backup service level.

Figure 128. Example flowchart: Backup service level creation

Catalog item description

To add a backup service level:

1. Select Add Backup Service Level from the Backup Service Level catalog item actions list and click Next.

2. Under Backup Schedule, enter a name for the backup service level and select a backup schedule.

The options are Daily, Weekly, and Monthly, as shown in Figure 129.

Figure 129. Add Backup Service Level request: Selecting a backup schedule

When selecting a daily schedule, specify one or more time intervals (for example,

03:00 and 03:30).

When selecting a monthly schedule, specify the week in which the backup will

take place. The backup time follows the default backup window.

3. On the Retention Policy tab, specify or create a retention policy appropriate for this backup service level.

You can specify or create one of several types of retention policies:

Retain the backups forever.

Retain the backups for a certain number of days/weeks/months/years.

Retain the backups until a certain date.

Prerequisites Add a site Add vCenters Add a

hardware islands

Onboard a cluster

Provision ctorage

Deploy Avamar proxies

Add Avamar Grids

Add ASRsAdd ARRs

Associate a cluster to ASR

Associate Avamar roxies with a cluster

Create a backup service

level

Chapter 6: Data Protection

118 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Define a custom retention period.

To keep the backups for a certain number of days, weeks, months, or years,

select the for option, type a number, and select days, weeks, months, or years

from the menu, as shown in Figure 130.

To define a backup retention period of forever, select forever. To keep the

backup until a certain date, select Until, which enables you to choose any future

date.

You can apply a custom retention schedule based on each of the backup types by

making selections from all of the possible parameters available.

Figure 130. Create Backup Service Level request: Specifying retention policy details

4. On the Final Backup tab, select either Yes or No to define whether a final backup, with long-term retention, is taken when a virtual machine is destroyed.

5. Under Replication Schedule, select a schedule from the list.

6. Click Next and Submit.

After you create the required Avamar objects, the vRealize Orchestrator workflows create

or update the service-level property in the Enterprise Hybrid Cloud Object Model and the

vRealize Automation custom dictionary with the new backup-service-level name. The

requester is notified by email when the workflow completes.

A backup service level may only be deleted if the associated vCenter folder does not

contain any virtual machines.

The following parameters are available:

Select Backup Service LevelSelect the backup service level to be deleted.

ConfirmSelect Yes or No.

Before the backup service level is deleted, the operation checks for any virtual machines

that are actively using that backup service level. If any exist, then the operation stops and

instructs the user to remove the virtual machine from that backup service level before

attempting to delete the backup service level again.

Delete Backup

Service Level

Chapter 6: Data Protection

119 Enterprise Hybrid Cloud 4.1.2 Administration Guide

To remove the virtual machine from the backup service level, the user in vRealize

Automation can retire the virtual machine or a vCenter administrator can manually move

the virtual machine from the backup service level folder to the VRM folder in vCenter.

Note: If a virtual machine backup service level has long-term final backup retention defined, a

long-term backup is created before the machine is destroyed.

When adding additional vCenters to the Enterprise Hybrid Cloud, you can add existing

backup service levels to the new vCenter. The Remediate Backup Service Level for new

vCenter Endpoint catalog item performs all of the actions necessary to remediate the data

protection components when adding a new vCenter

To remediate backup service levels for a new vCenter endpoint:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Data Protection Services catalog items (for example,

ehc_backup_admin@domain.local).

2. Go to Catalog > Data Protection Services and select Remediate Backup Service Level for new vCenter Endpoint, as shown in Figure 131.

Figure 131. Remediate Backup Service Level for new vCenter Endpoint catalog item

3. Under Request Information, type a description, optionally type a reason, and click Next,as shown in Figure 132.

Remediate

backup service

levels for a new

vCenter endpoint

Chapter 6: Data Protection

120 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 132. Remediate Backup Service Level for new vCenter Endpoint Request Information tab

4. Select the vCenter you want to remediate from the Select vCenter to remediate list box and click Submit.

Use the Remediate Single Failed Avamar service when an Avamar grid has been

replaced or brought back online.

Unless all the backup and replication policies on the failed unit are disabled when the unit

comes back online, both the primary and secondary Avamar instances attempt to execute

parallel scheduled backups of the virtual machines.

As shown in Figure 133, the Remediate Single Failed Avamar service requires the

selection of the Avamar grid for remediation.

Figure 133. Remediate Single Failed Avamar request: Selecting the Avamar grid

The service interrogates the Avamar grid and remediates any missing information.

Remediate a

single failed

Avamar grid

Chapter 6: Data Protection

121 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Virtual machine backup lifecycle

To enable backup and restore functionality for a vRealize Automation blueprint, enable the

BackupAndRestoreFunctions build profile on the blueprint, as shown in Figure 134.

Figure 134. Enabling a build profile for backup and restore functions in the blueprint

Prerequisites

The Avamar grid is online.

Avamar proxies deployed.

The blueprint with BackupAndRestoreFunctions is created and available to the business group.

Figure 135 shows the required steps to deploy a virtual machine with backup protection.

Figure 135. Example flowchart: Deploy a virtual machine with backup protection

Prerequisites Add a site Add vCenters Add hardware

islands

Onboard a clusterProvision storage Deploy Avamar

proxies Add Avamar Grids

Add ASRs Add ARRs Associate a

cluster to ASR

Associate Avamar proxies with a

cluster

Create a backup service level

Create a blueprint Enable backup

build profile

Deploy a virtual machine with

backup protection

Enable backup

and restore for a

blueprint

Deploy a virtual

machine with

backup and

restore services

Chapter 6: Data Protection

122 Enterprise Hybrid Cloud 4.1.2 Administration Guide

The cloud user follows these steps to deploy a virtual machine with automatic data

protection:

1. In the vRealize Automation self-service portal, log in to your account, click Catalog, and select a blueprint from the list of available blueprints, as shown in Figure 136.

Figure 136. Creating a new request in the service catalog

2. Within the virtual machine blueprint, select the required backup service level, as shown in Figure 137.

Figure 137. Selecting a backup service level for the virtual machine

You can also select the number of virtual machines to deploy, and increase or

decrease virtual machine resources, depending on your entitlements.

3. Review and edit the storage options for the virtual machine, click Next to view the Cost Summary, and then click Submit.

Chapter 6: Data Protection

123 Enterprise Hybrid Cloud 4.1.2 Administration Guide

The virtual machine is provisioned into the relevant folder defined in vCenter for that

service level, and it inherits the backup schedules defined for that service level.

Cloud users receive the name of the virtual machine in an email notification from the

administrator after the provisioning process successfully completes. The email notification

advises the user to wait a period of time before attempting to access the newly deployed

virtual machine. The customization operations, which are required to automatically protect

the virtual machine, are run during that time.

This use case describes how a cloud user can request an on-demand backup of a virtual

machine from the vRealize Automation self-service portal. The user does not have to wait

for the completion of the backup task. An email notification of the backup status is

automatically generated when the task is complete, whether the task succeeded or failed.

After logging in to the vRealize Automation self-service portal, a cloud user can select On

Demand Backup from the Actions menu for a virtual machine, as shown in Figure 138.

Figure 138. Selecting an on demand backup for a virtual machine

The on-demand backup request initiates the relevant vRealize Orchestrator workflow,

which performs the backup using the dataset and retention policy defined by the backup

service level.

When the task is complete, the user receives an automated email notification with the

status of the task. The email status workflow runs asynchronously and, therefore, the user

does not have to wait for the completion status of the backup.

This use case describes the on-demand restore of a virtual machine from the vRealize

Automation self-service portal, where the user can choose to restore from a list of the

available backups.

The cloud user follows these steps to restore a virtual machine with an available backup:

1. Power off the virtual machine.

2. Log in to the vRealize Automation self-service portal and browse to Items.

On-demand

backup

On-demand

restore

Chapter 6: Data Protection

124 Enterprise Hybrid Cloud 4.1.2 Administration Guide

3. Select the virtual machine to be restored and click On Demand Restore under Actions, which opens the On Demand Restore request wizard.

4. Under Request Information, type a description of the request in the Description field, as shown in Figure 139.

Figure 139. On Demand Restore request: Specifying request information

5. Under Choose Backup Point, select required, as shown in Figure 140.

Figure 140. On Demand Restore request: Selecting a backup point-in-time to restore

After requesting the on-demand restore, the cloud user receives an email notification that

indicates the success or failure status of the job, including the reason for a failure if

applicable, and how long it took to restore the backup.

If, for example, a virtual machine is powered on, then the restore operation fails and an

email is sent to the user that identifies the power state as the reason for the failure.

Restore points of a virtual machine fall into one of two categories:

Backups performed locally to the primary Avamar system

Replicated backups from the secondary Avamar system where the backups were previously performed on the secondary instance and later replicated to the primary

During an on-demand restore operation, Enterprise Hybrid Cloud workflows dynamically

interrogate the primary Avamar instance for relevant backups of both types and present a

consolidated list of available backups from which to choose, as shown in Figure 141.

Selecting a

restore point

during an on-

demand restore

(multisite, single

vCenter)

Chapter 6: Data Protection

125 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 141. On Demand Restore request: Selecting a backup point

Restore points that are taken to the other Avamar instance and replicated to the system

currently designated as primary have REPLICATED appended to the end of the backup

details.

Based on the choice the user makes, the Enterprise Hybrid Cloud workflows execute the

relevant restore tasks to return the virtual machine to the correct point in time. Regardless

of where the backup is taken (that is, to which Avamar instance) the data is always

restored from the Avamar system currently configured as the primary.

This use case describes how a cloud user can request the decommissioning of a virtual

machine that has data protection backup. From the vRealize Automation self-service

portal, the user can request that a virtual machine be destroyed (or retired), as shown in

Figure 142.

Figure 142. Destroying a virtual machine

The request initiates a number of tasks. Based on the service level of the virtual machine,

a final backup is taken and the virtual machine is retired in the Avamar system, meaning

that the virtual machine is permanently deleted from the service-level folder. A retired

virtual machine can be restored from Avamar at any time prior to the backup expiration

date. Retired virtual machine backups expire according to the retention policy of the

service level, but the last backup expires according to the long-term retention policy if

defined on the relevant backup service level. Retired virtual machines do not participate in

any further backup schedules after they have been retired.

Decommissioning

a virtual machine

with data

protection

backup

Chapter 6: Data Protection

126 Enterprise Hybrid Cloud 4.1.2 Administration Guide

RetireVM is the vRealize Orchestrator workflow that orchestrates the various tasks

required to decommission a virtual machine. The steps in the RetireVM workflow are as

follows:

1. Create Retire VM folderA temporary virtual machine folder is created with a unique string. The name of the folder also contains the long retention name and the virtual machine name. This is achieved using a VMware vCenter API call.

2. Move VM to Retire folderThe virtual machine is moved to the Retire folder from its service-level folder.

3. Perform on-demand backupBecause this virtual machine is retired permanently and no further backups of the machine are possible, a final backup is taken with a long-term retention policy if defined on the relevant service level.

4. Retire ClientAfter the backup is complete, the client is retired in the Avamar system. This de-lists the virtual machine from the regular Avamar backups, and no further backups are performed on this virtual machine. The virtual machine is also removed from the active view of the Avamar client folder.

5. Move VM back to Service Level folderThe virtual machine is moved to its original service level and the vRealize Automation destroy process deletes it permanently from vCenter.

6. Delete the temporary SL folderAs a cleanup process, the temporary virtual machine folder is deleted from vCenter.

Ensuring continuity of backup in CA failure scenarios

If a grid goes offline, the Failover Avamar policies for Offline Avamar Grid service enable

the administrator to fail over all backup policies to the secondary grid, and all backup

operations to continue.

To fail over Avamar policies:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Data Protection Services catalog items (for example,

ehc_backup_admin@domain.local).

2. Go to Catalog > Data Protection Services and select Failover Avamar policies for offline Avamar grid, as shown in Figure 143.

Failover Avamar

policies for an

offline Avamar

grid

Chapter 6: Data Protection

127 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 143. Failover Avamar Policies catalog item

3. Under Request Information, type a description, optionally type a reason, and click Next,as shown in Figure 144.

Figure 144. Failover Avamar Policies Request Information tab

4. Select the failed Avamar grid and click Submit, as shown in Figure 145.

Figure 145. Failover Avamar Policies: Select the failed Avamar Grid

If the original primary Avamar grid is offline because of unit or site failure, the Failover

Avamar Policies for offline Avamar Grid service enables the policies on the surviving

Avamar instance.

Chapter 6: Data Protection

128 Enterprise Hybrid Cloud 4.1.2 Administration Guide

The Failback Avamar policies after restoring an Avamar grid service enables the

administrator to fail back all backup policies to the original Avamar grid when the original

Avamar grid is brought back online.

To fail back Avamar policies:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Data Protection Services catalog items (for example,

ehc_backup_admin@domain.local).

2. Go to Catalog > Data Protection Services and select Failback Avamar policies after Restoring Avamar grid, as shown in Figure 146.

Figure 146. Failback Avamar Policies catalog item

3. Under Request Information, type a description, optionally type a reason, and click Next as shown in Figure 147.

Figure 147. Failback Avamar Policies Request Information tab

Failback Avamar

policies after

restoring an

Avamar grid

Chapter 6: Data Protection

129 Enterprise Hybrid Cloud 4.1.2 Administration Guide

4. Select the Avamar grid that has been restored and click Submit,as shown in Figure 148.

Figure 148. Failback Avamar Policies: Select restored Avamar grid

The Failover Avamar Grids after Site Failure service enables the administrator to fail over

all backup policies to the secondary site if a site goes offline. This allows all backup

operations to continue.

To fail over Avamar policies:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Data Protection Services catalog items (for example,

ehc_backup_admin@domain.local).

2. Go to Catalog > Data Protection Services and select Failover Avamar Grids after Site Failure, as shown in Figure 149.

Figure 149. Failover Avamar Grids after Site Failure catalog item

Failover Avamar

grids after a site

failure

Chapter 6: Data Protection

130 Enterprise Hybrid Cloud 4.1.2 Administration Guide

3. Under Request Information, type a description, optionally type a reason, and click Next,as shown in Figure 150.

Figure 150. Failover Avamar Grids after Site Failure Request Information tab

4. Select the failed site and click Submit, as shown in Figure 151.

Figure 151. Failover Avamar Grids after Site Failure: Site selection

The Failback Avamar Policies after Site Restoration service allows the administrator to fail

back all backup policies to the original site when the original site is restored. All backup

policies revert to their original Avamar grid.

To fail over Avamar policies:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Data Protection Services catalog items (for example, ehc_backup_admin@domain.local).

2. Go to Catalog > Data Protection Services and select Failback Avamar Policies after Site Restoration, as shown in Figure 152.

Failback Avamar

policies after site

restoration

Chapter 6: Data Protection

131 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 152. Failback Avamar Policies after Site Restoration catalog item

3. Under Request Information, type a description, optionally type a reason, and click Next as shown in Figure 153.

Figure 153. Failback Avamar policies after Site Restoration Request Information tab

4. Select the failed site and click Submit, as shown in Figure 154.

Figure 154. Failback Avamar Policies after Site Restoration: Site selection

Chapter 6: Data Protection

132 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Data protection reporting

Dell EMC Data Protection Advisor (DPA) is required for data protection reporting

workflows. If DPA was not initialized during the initial Enterprise Hybrid Cloud data

protection setup, use the Initialize DPA catalog item to add DPA to the environment.

To initialize DPA:

1. Log in to the Enterprise Hybrid Cloud tenant portal as the system administrator with entitlements to the EHC Data Protection Services catalog items (for example, ehc_backup_admin@domain.local).

2. Go to Catalog > Data Protection Services and select Initialize DPA, as shown in Figure 155.

Figure 155. Initialize DPA catalog item

3. Under Request Information, type a description, optionally type a reason, and click Next, as shown in Figure 156.

Figure 156. Initialize DPA Request Information tab

Initialize Date

Protection

Advisor

Chapter 6: Data Protection

133 Enterprise Hybrid Cloud 4.1.2 Administration Guide

4. Under Initialize DPA, type the DPA server FQDN and credentials of a user with DPA User role, as shown in Figure 157.

Figure 157. Initialize DPA server details

From the vRealize Automation self-service portal, a cloud user can run an on-demand

status report of available virtual machine backups.

1. After logging in to the vRealize Automation self-service portal, request the available backups by navigating to the virtual machine under Items, and then clicking Get Backup Status under Actions.

2. Provide the required information in the New Request dialog box, as shown in Figure 158.

Figure 158. Requesting a list of all available backups of a virtual machine

The vRealize Orchestrator workflow that supports this operation runs an Avamar MCCLI

command requesting that all the available backups for a virtual machine be emailed to the

cloud user.

Requesting a list

of available

backups for a

virtual machine

Chapter 6: Data Protection

134 Enterprise Hybrid Cloud 4.1.2 Administration Guide

When the workflow is complete, an email notification lists all the backups that are

available for the virtual machine, as displayed in Figure 159.

Figure 159. List of available virtual machine backups emailed to requestor

Cloud users can request cost and usage information about any of their virtual machines

from the vRealize Automation self-service portal by selecting Get Backup Summary from

the virtual machines Actions menu.

You receive an email notification containing the relevant backup usage information, as

shown in Figure 160.

Figure 160. Email report to cloud user with virtual machine backup summary

Cloud users can request a report containing comprehensive backup details specific to any

of their virtual machines. A user can run this operation from the self-service portal by

selecting the virtual machine and selecting Get Backup Detailed Report from the

Actions menu.

This backup report contains the following information categories:

Job Summary

Failed Jobs

Backup Jobs with Last Resolution

Requesting

backup usage

reports for a

virtual machine

Requesting

backup details

reports for a

virtual machine

Chapter 6: Data Protection

135 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Estimated Protected Backup Capacity Details

Backup Client De-Dupe Ratios

Chargeback Summary

Client Configuration

You receive an email message containing a report with backup information specific to the

virtual machine, as shown in Figure 161.

Figure 161. Backup status report emailed to cloud user on request

Note: DPA is required for the backup report.

Chapter 7: Administration Scenarios

136 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Chapter 7 Administration Scenarios

This chapter presents the following topics:

Overview .......................................................................................................... 137

Scenario 1: Single site with backup............................................................... 137

Scenario 2: Dual-site CA with replicated backup .......................................... 140

Scenario 3: Dual-site vCenter Site Recovery Manager DR with replicated backup ...................................................................................................... 143

Chapter 7: Administration Scenarios

137 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Overview

This chapter presents some common scenarios that an Enterprise Hybrid Cloud

administrator might need to perform. The scenarios are presented as high-level steps and

explain the sequence of events required to initialize and update sample Enterprise Hybrid

Cloud configurations.

Setup and integration of the cloud components in the Enterprise Hybrid Cloud Object

Model are performed on Day 2 and after. vRealize Automation cloud administrators use

their service catalog, when it has been populated, to initialize and update their

environment.

Scenario 1: Single site with backup

The Enterprise Hybrid Cloud administrator wants to set up a single site with backup

services, where the following are present:

Single site

Single vCenter

Single hardware island

Local-only cluster

Single Avamar grid with proxies

The following requirements must be met for this scenario:

vCenter Endpoint Cloud-VC01 is added to the vRealize Orchestrator vCenter plug-in.

ViPR virtual array NY-HWI-1-vArray1 has been created.

Local cluster NY-HWI-1-C1 has been created in Cloud-VC01.

Avamar grid NY-AV1 is online.

Avamar proxies are deployed.

Overview

Prerequisites

Chapter 7: Administration Scenarios

138 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 162 shows the required steps to set up a single site with backup.

Figure 162. Example flowchart: Single site with backup setup

The following scenario outlines the steps required to set up an environment with the

elements shown in Figure 163.

Figure 163. Single site with backup

Prerequisites Add a site Add a vCenter Add a

hardware island

Add local cluster

Add Avamar grid

Create ASRCreate ARR

Associate a cluster with

ASR

Create the backup service

level

Environment

details

Chapter 7: Administration Scenarios

139 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Follow these steps to complete scenario 1:

1. Add the site:

a. Run the Site Maintenance catalog item.

b. Select Add SiteNewYork.

2. Add a vCenter endpoint:

a. Run the vCenter Endpoint Maintenance catalog item.

b. Select Add vCenter:

i. Enter the vCenter nameCloud-VC01.

ii. Select the vCenter FQDN (populated from the vRealize Orchestrator vCenter plug-in).

iii. Select Associated siteNewYork (populated by the Site Maintenance workflow).

iv. Select vCenter Datacenter (populated from the vRealize Orchestrator vCenter plug-in).

3. Add a hardware island:

a. Run the Hardware Island Maintenance catalog item.

b. Select Add Hardware Island:

i. Enter the hardware island nameNewYork-HWI-1.

ii. Select the associated vCenterCloud-VC01 (populated from the vRealize Orchestrator vCenter plug-in).

iii. Select the associated siteNewYork (populated by the Site Maintenance workflow).

iv. Select the ViPR instance (populated from the Enterprise Hybrid Cloud Object Model).

v. Select the associated ViPR virtual array(s) NY-HWI-1-vArray1 (populated from the vRealize Orchestrator ViPR plug-in).

4. Onboard the local cluster:

a. Run the Cluster Maintenance catalog item.

b. Select Onboard Local Cluster.

c. Select Hardware IslandNewYork-HWI-1.

d. Select unprepared local clusterNY-HWI-1-C1.

5. Add the New York Avamar grid:

a. Run the Avamar Grid Maintenance catalog item.

b. Select Add Avamar Grid.

c. Enter the Avamar grid nameNY-AV1.

d. Enter the grid FQDN.

e. Enter the admin credentials.

f. Select proxies.

g. Select the associated siteNewYork (populated by the Site Maintenance workflow).

Setup steps

Chapter 7: Administration Scenarios

140 Enterprise Hybrid Cloud 4.1.2 Administration Guide

h. Enter Avamar Simple Object Access Protocol (SOAP) credentials.

6. Add the ASR:

a. Run the Avamar Site Relationship (ASR) Maintenance catalog item.

b. Select Add an ASR.

c. Select 1C1VC (One backup copy. Virtual machines on one site only).

d. Select ASR siteNewYork.

7. Add the ARR:

a. Run the Avamar Replication Relationship (ARR) Maintenance catalog item.

b. Select Add an ARR.

c. Select the 1C1VC ASR created in step 6.

8. Select the Avamar grid that was added in step 5.

9. Associate the local cluster with ASR:

a. Run the Cluster Maintenance catalog item.

b. Select Associate Cluster to ASR.

c. Select local clusterNY-HWI-1-C1.

d. Select the relevant ASR (only ASRs matching the cluster type are shown).

10. Deploy Avamar proxies to the cluster using the Deploy Avamar proxy catalog item (or associate existing proxies to the cluster using the Cluster Maintenance catalog item).

11. Provision local datastore using the Provision Cloud Storage catalog item.

Scenario 2: Dual-site CA with replicated backup

The Enterprise Hybrid Cloud administrator wants to set up a dual-site CA environment

with data protection backup services, as shown in Figure 164. The following scenario

outlines the steps required to set up an environment with the following (additional to

Scenario 1):

Two sites

One vCenter

Two hardware islands

Local-only cluster on one site

CA cluster across sites

A single Avamar grid at each site

Overview

Chapter 7: Administration Scenarios

141 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Figure 164. Dual-site CA with backup

The following prerequisites are required for scenario 2:

Scenario 1 has been completed.

vCenter Endpoint Cloud-VC01 is added to the vRealize Orchestrator vCenter plug-in.

ViPR virtual arrays NY-HWI-1-vArray1 and BOS-HWI-1-vArray1 have been created.

CA cluster NY-BOS-CA-C1 has been created in Cloud-VC01.

Avamar grids NY-AV1 and BOS-AV1 are online.

Figure 165 shows the required steps to set up a dual-site CA environment with replicated

backup.

Figure 165. Example flowchart: Dual site CA with backup setup

Prerequisites Add a site Add a vCenter Add a

hardware island

Add local cluster

Add Avamar grid

Create ASRCreate ARR

Associate a cluster with

ASR

Create the backup service

level

Prerequisites

Chapter 7: Administration Scenarios

142 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Follow the steps below to complete scenario 2:

1. Add the second site:

a. Run the Site Maintenance catalog item.

b. Select Add SiteBoston.

2. Update vCenter endpoint:

a. Run the vCenter Endpoint Maintenance catalog item.

b. Select Update vCenter:

i. Select vCenter to update Cloud-VC01.

ii. Select vCenter FQDN (populated from the vRealize Orchestrator vCenter plug-in).

iii. Select vCenter Datacenter (populated from the vRO vCenter plug-in).

iv. Select site to addBoston (populated by the Site Maintenance workflow).

3. Add a hardware island:

a. Run the Hardware Island Maintenance catalog item.

b. Select Add Hardware Island.

i. Enter the hardware island nameBoston-HWI-1.

ii. Select the associated vCenterCloud-VC01 (populated from the vRealize Orchestrator vCenter plug-in).

iii. Select the associated siteBoston (populated by the Site Maintenance workflow).

iv. Select the ViPR instance (populated from the Enterprise Hybrid Cloud Object Model).

v. Select the associated ViPR virtual array(s)BOS-HWI-1-vArray1 (populated from the vRealize Orchestrator ViPR plug-in).

4. Onboard the CA cluster:

a. Run the Cluster Maintenance catalog item.

b. Select Onboard CA Cluster.

c. Select Hardware Island 1 NewYork-HWI-1.

d. Select unprepared CA clusterNY-BOS-CA-C1.

e. Select Inter-site (Intra-site would be selected for single site CA).

f. Select Hardware Island 2Boston-HWI-1.

g. Select the hosts from hardware island 1Hosts from NewYork-HWI-1.

h. Select the hosts from hardware island 2Hosts from Boston-HWI-1.

5. Add the Boston Avamar grid:

a. Run the Avamar Grid Maintenance catalog item.

b. Select Add Avamar Grid.

c. Enter the Avamar grid nameBOS-AV1.

d. Enter the grid FQDN.

Setup steps

Chapter 7: Administration Scenarios

143 Enterprise Hybrid Cloud 4.1.2 Administration Guide

e. Enter admin credentials.

f. Select proxies.

g. Select the associated siteBoston (populated by the Site Maintenance workflow).

h. Enter Avamar SOAP credentials.

6. Add the ASR:

a. Run the Avamar Site Relationship (ASR) Maintenance catalog item.

b. Select Add an ASR.

c. Select 2C1VC (Two backup copies. Virtual machines move between two sites).

d. Select first ASR siteNewYork.

e. Select second ASR siteBoston.

7. Add the ARR.

a. Run the Avamar Replication Relationship (ARR) Maintenance catalog item.

b. Select Add an ARR.

c. Select the 2C1VC ASR created in step 6.

d. Select site 1 Avamar gridNY-AV1.

e. Select site 2 Avamar gridBOS-AV1.

8. Associate the CA cluster with ASR:

a. Run the Cluster Maintenance catalog item.

b. Select Associate Cluster to ASR.

c. Select CA clusterNY-BOS-CA-C1.

d. Select the 2C1VC ASR created in step 6 (Only ASRs matching the cluster type are shown).

9. Deploy Avamar proxies to the cluster using the Deploy Avamar proxy catalog item (or associate existing proxies to the cluster using the cluster maintenance catalog item).

10. Provision CA protected datastore using the Provision Cloud Storage catalog item.

When complete, you can create a backup service level with Avamar replication and

deploy CA protected virtual machines with data protection.

Scenario 3: Dual-site vCenter Site Recovery Manager DR with replicated backup

The Enterprise Hybrid Cloud administrator wants to set up a dual-site vCenter Site

Recovery Manager DR environment with data protection backup services, as shown in

Figure 166. The following scenario outlines the steps required to set up an environment

with the following (additional to scenario 1):

Two sites

Two vCenters

Overview

Chapter 7: Administration Scenarios

144 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Two hardware islands

Local-only cluster on one site

DR-protected cluster at each site

A single Avamar grid at each site

Figure 166. Dual-site vCenter Site Recovery Manager DR with backup

The following are required for scenario 3:

Scenario 1 has been completed.

vCenter Endpoint Cloud-VC02 is added to the vRealize Orchestrator vCenter plug-in.

ViPR virtual arrays NY-HWI-1-vArray1 and BOS-HWI-1-vArray1 have been created.

DR clusters NY-SEA-DR-C1 and SEA-NY-DR-C1 have been created in Cloud- VC01 and Cloud-VC02 respectively.

Avamar grids NY-AV1 and SEA-AV1 are online.

Note: Scenario 3 is independent of scenario 2 because CA and vCenter Site Recovery

Manager DR in the same environment is not a supported Enterprise Hybrid Cloud topology.

Follow these steps to complete scenario 3:

1. Add the second site:

a. Run the Site Maintenance catalog item.

b. Select Add SiteSeattle.

2. Add the vCenter endpoint:

a. Run the vCenter Endpoint Maintenance catalog item.

b. Select Add vCenter:

i. Enter the vCenter nameCloud-VC02.

Prerequisites

Setup steps

Chapter 7: Administration Scenarios

145 Enterprise Hybrid Cloud 4.1.2 Administration Guide

ii. Select vCenter FQDN (populated from the vRealize Orchestrator vCenter plug-in).

iii. Select vCenter Datacenter (populated from the vRealize Orchestrator vCenter plug-in).

iv. Select site to associateSeattle (populated by the Site Maintenance workflow).

3. Add the vCenter relationship:

a. Run the vCenter Relationship Maintenance catalog item.

b. Select Add SRMDR vCenter Relationship:

i. Enter the vCenter protected and recovery vCenters.

ii. Enter NSX manager details (if present).

iii. Enter vCenter Site Recovery Manager details.

iv. Enter vCenter Site Recovery Manager SQL Server details.

v. Enter vCenter Site Recovery Manager SOAP details.

4. Add a hardware island:

a. Run the Hardware Island Maintenance catalog item.

b. Select Add Hardware Island:

i. Enter the hardware island nameSeattle-HWI-1.

ii. Select the associated vCenterCloud-VC02 (populated from the vRealize Orchestrator vCenter plug-in).

iii. Select the associated site Seattle (populated by the Site Maintenance workflow).

iv. Select a ViPR instance (populated from the Enterprise Hybrid Cloud Object Model).

v. Select associated ViPR virtual array(s)SEA-HWI-1-vArray1 (populated from the vRealize Orchestrator ViPR plug-in).

5. Onboard DR clusters:

a. Run the Cluster Maintenance catalog item.

b. Select Onboard DR Cluster.

c. Select protected cluster hardware islandNewYork-HWI-1.

d. Select unprepared DR clusterNY-SEA-DR-C1.

e. Select recovery cluster hardware island Seattle-HWI-1.

f. Select unprepared DR cluster SEA-NY-DR-C1.

6. Add the Seattle Avamar grid:

a. Run the Avamar Grid Maintenance catalog item.

b. Select Add Avamar Grid.

c. Enter the Avamar grid nameSEA-AV1.

d. Enter the grid FQDN.

e. Enter the admin credentials.

f. Select proxies.

Chapter 7: Administration Scenarios

146 Enterprise Hybrid Cloud 4.1.2 Administration Guide

g. Select associated siteSeattle (populated by the Site Maintenance workflow).

h. Enter Avamar SOAP credentials

7. Add the ASR:

a. Run the Avamar Site Relationship (ASR) Maintenance catalog item.

b. Select Add an ASR.

c. Select 2C2VC (Two backup copies. Virtual machines move between two sites/vCenters).

d. Select first ASR site NewYork.

e. Select second ASR siteSeattle.

8. Add the ARR:

a. Run the Avamar Replication Relationship (ARR) Maintenance catalog item.

b. Select Add an ARR.

c. Select the 2C2VC ASR created in step 6.

d. Select site 1 Avamar gridNY-AV1.

e. Select site 2 Avamar gridSEA-AV1.

9. Associate the DR cluster with ASR:

a. Run the Cluster Maintenance catalog item.

b. Select Associate Cluster to ASR.

c. Select CA clusterNY-BOS-CA-C1.

d. Select the 2C1VC ASR created in step 6 (Only ASRs matching the cluster type are shown).

10. Deploy Avamar proxies to the clusters using the Deploy Avamar proxy catalog item (or associate existing proxies to the cluster using the cluster maintenance catalog item).

11. Provision a DR protected datastore using the Provision Cloud Storage catalog item.

After the operation is complete, you can create a backup service level with Avamar

replication and deploy vCenter Site Recovery Manager DR protected virtual machines

with data protection.

Chapter 8: Conclusion

147 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Chapter 8 Conclusion

This chapter presents the following topics:

Summary ......................................................................................................... 148

Chapter 8: Conclusion

148 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Summary

Enterprise Hybrid Cloud is the bridge between the applications of today (Platform 2) and

the social, mobile, analytics, and cloud applications of the future (Platform 3). It empowers

IT to be a broker of cloud services, providing the control and visibility that IT organizations

need and the on-demand self-service that developers and application users expect.

The data protection and recovery plans chapters in this guide discussed some of the data

protection services available with Enterprise Hybrid Cloud. The use cases presented data

protection scenarios addressing requirements for backup, CA, and DR. These services

are available to various cloud users, from those responsible for the administration and

management of data protection services to end users who consume the data protection

services for their virtual machines and applications. These data protection solutions are

optional for Enterprise Hybrid Cloud and require additional resources on top of the

foundation solution.

Enterprise Hybrid Cloud users can easily provision standardized services directly from an

application marketplace portal, with upfront pricing. Delivery of these resources from

private and public clouds, whatever the workload calls for, is built on policies set by IT,

which ensures application workloads are placed in the right cloud, with the right cost,

security, and performance.

Chapter 9: References

149 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Chapter 9 References

This chapter presents the following topic:

Dell EMC Documentation ................................................................................ 150

Chapter 9: References

150 Enterprise Hybrid Cloud 4.1.2 Administration Guide

Dell EMC Documentation

The following documents, available on Online Support or DellEMC.com, provide

additional, relevant information. If you do not have access to a document, contact your

Dell EMC representative.

Enterprise Hybrid Cloud 4.1.2: Concepts and Architecture Guide

Enterprise Hybrid Cloud 4.1.2: Reference Architecture Guide

Enterprise Hybrid Cloud 4.1.1: Infrastructure and Operations Management Guide

For additional information, see the followin

Manualsnet FAQs

If you want to find out how the Symmetrix VMAX Dell works, you can view and download the Dell Symmetrix VMAX 20K V4.1.2 Storage Administration Guide on the Manualsnet website.

Yes, we have the Administration Guide for Dell Symmetrix VMAX as well as other Dell manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The Administration Guide should include all the details that are needed to use a Dell Symmetrix VMAX. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Dell Symmetrix VMAX 20K V4.1.2 Storage Administration Guide is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Dell Symmetrix VMAX 20K V4.1.2 Storage Administration Guide consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Dell Symmetrix VMAX 20K V4.1.2 Storage Administration Guide free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Dell Symmetrix VMAX 20K V4.1.2 Storage Administration Guide, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell Symmetrix VMAX 20K V4.1.2 Storage Administration Guide as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.