Dell PowerProtect 19.2 Data Manager Installation Guide PDF

vRealize Data Protection Extension for PowerProtect Version 19.2

Installation and Administration Guide REV 02

November 2019

Copyright 2019- Dell Inc. All rights reserved.

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

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS-IS. DELL 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 DELL SOFTWARE DESCRIBED

IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property

of their respective owners. Published in the USA.

Dell EMC Hopkinton, Massachusetts 01748-9103 1-508-435-1000 In North America 1-866-464-7381 www.DellEMC.com

2 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

7

9

PREFACE 11

Introduction 15 vRealize Data Protection Extension for PowerProtect Data Manager............... 16 Key concepts and components.......................................................................... 16

Users.................................................................................................... 16 Blueprints............................................................................................. 16 Catalog services................................................................................... 17 Advanced services................................................................................ 17 Property groups....................................................................................17 Data protection policies........................................................................ 17

Data protection policy definitions and descriptions............................................17 vRealize Automation and vRealize Orchestrator integration.............................. 18 vRealize Automation endpoints..........................................................................18 vRealize Automation tasks.................................................................................18 vCloud Automation vs. vRealize Automation......................................................19 Recommended timeout values.......................................................................... 20 PowerProtect limitations.................................................................................. 20

Installation and Upgrade 21 Compatibility.....................................................................................................22

Required components.......................................................................... 22 Supported product versions for the vRealize Data Protection Extension for PowerProtect Data Manager..........................................................22

Pre-installation..................................................................................................22 Verify the configuration of the vRealize Automation installation.......... 22 Install the VMware vCenter Orchestrator Plug-in for vCloud Automation Center..................................................................................................23 Configuring XaaS to recognize vRealize Orchestrator......................... 23 Install and configure a 3-node cluster...................................................23 Check for the default tenant................................................................ 24 Add a vRealize Automation host...........................................................25 Adding an IaaS host............................................................................. 28 Verify vCenter endpoints..................................................................... 32

Installing the vRealize Data Protection Extension............................................. 32 Install the vmoapp using vRealize Orchestrator................................... 32 Install the vmoapp from the command line........................................... 33

Installing data protection admin services into a specific tenant.........................34 Licensing........................................................................................................... 41

Linux-based vRealize Orchestrator server............................................ 41 Verifying the licensing validation check................................................ 41

Upgrading the vRealize Data Protection Extension........................................... 42 Install the vRealize Data Protection Extension vmoapp........................43

Figures

Tables

Chapter 1

Chapter 2

CONTENTS

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 3

Update the default setup in each vRealize Automation tenant............. 43 Update custom workflows and actions.................................................46 Verifying the new version.....................................................................46

Uninstalling the vRealize Data Protection Extension.........................................46 Uninstall EMC data protection from a single tenant............................. 46 Uninstall the plug-in from vRealize Orchestrator..................................47

Administration 49 Data protection configuration for the tenant.................................................... 50

Clustered vRealize Orchestrator environment..................................... 50 Multi-tenancy support with PowerProtect Data Manager.................... 51

Data protection administration.......................................................................... 51 Service blueprints.................................................................................51 Configuring a PowerProtect data protection system........................... 52 Set up data protection on a blueprint...................................................52 Restoring application backups..............................................................54 Restore a virtual machine to a new location using advanced options....54 Restore a deleted virtual machine........................................................ 56

Business Group User Operations 59 Provision a protected virtual machine............................................................... 60 Data protection actions..................................................................................... 61

Adding data protection to a virtual machine..........................................61 Running data protection on a virtual machine....................................... 61 Viewing the protection status of a virtual machine...............................62 Removing data protection from a virtual machine................................ 62

Restore actions.................................................................................................62 Restore a virtual machine to its original location.................................. 62 Restore a virtual machine to a new location......................................... 63

Expiring or destroying a virtual machine............................................................64

Logging and Supportability 67 Monitoring status..............................................................................................68 Event and error message codes........................................................................ 69 PowerProtect Jobs window for activity monitoring and log files.......................69 Single-click log capturing and packaging.......................................................... 69

vRealize Automation log bundling.........................................................70 vRealize Orchestrator log bundling...................................................... 70

Log locations.....................................................................................................70

Troubleshooting 73 General Troubleshooting................................................................................... 74 Items to investigate when data protection is not added.................................... 74 Troubleshooting the EMC vRealize Data Protection Extension......................... 74

A Day 2 operation such as Restore Data times out when submitting the operation from the vRA web portal...................................................... 74 Recently changed policies not displaying when running Setup a Data Protection Property Group or Add Data Protection workflows............ 75 Null error when provisioning from blueprint with deleted policy........... 75 No available policy found from virtual machine properties when there is no EDP system.....................................................................................76 vRealize Automation event subscriptions............................................. 76

Check the vRealize Data Protection Extension configuration............................76

Chapter 3

Chapter 4

Chapter 5

Chapter 6

Contents

4 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Configuration checks performed by the EMC data protection configuration workflow.........................................................................77 Error and warning messages................................................................ 78

Contents

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 5

Contents

6 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Synchronized cluster configuration in vRO....................................................................... 24 Inventory tab in vRealize Orchestrator..............................................................................24 Existing tenants in vRealize Orchestrator......................................................................... 25 Workflows tab in vRealize Orchestrator............................................................................25 Start Workflow in vRealize Orchestrator.......................................................................... 26 Start Workflow: Add a vRA host....................................................................................... 27 Host Authentication in Start Workflow wizard.................................................................. 28 Start workflow in vRealize Orchestrator........................................................................... 29 Add an IaaS host in Start workflow wizard........................................................................29 Host Authentication in Start workflow wizard...................................................................30 Host Authentication in Start workflow wizard................................................................... 31 Valid provisioning groups under vRealize Automation Infrastructure ................................ 32 Start Workflow in vRealize Orchestrator.......................................................................... 35 Start Workflow wizard...................................................................................................... 35 Select vCACCAFE Host dialog.......................................................................................... 36 Catalog Service in Start Workflow wizard......................................................................... 37 Administrator Entitlement in Start Workflow wizard......................................................... 38 user Entitlement in Start Workflow wizard........................................................................39 Data Protection in Start Workflow wizard.........................................................................40 Workflow interaction form................................................................................................ 44 Start Workflow : Update default setup for tenant.............................................................45 Select policy for the blueprint...........................................................................................60 Successful request in vRA................................................................................................ 68 Failed request in vRA........................................................................................................ 68

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

FIGURES

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 7

Figures

8 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Revision history..................................................................................................................11 Typographical conventions................................................................................................ 12 vRealize Automation tasks.................................................................................................18 Service catalog blueprints................................................................................................. 51 Event and error codes.......................................................................................................69 Default log locations..........................................................................................................70 Error and warning messages............................................................................................. 78

1 2 3 4 5 6 7

TABLES

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 9

Tables

10 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

PREFACE

As part of an effort to improve product lines, periodic revisions of software and hardware are released. Therefore, all versions of the software or hardware currently in use might not support some functions that are described in this document. The product release notes provide the most up-to-date information on product features.

If a product does not function correctly or does not function as described in this document, contact a technical support professional.

Note: This document was accurate at publication time. To find the latest version of this document, go to Online Support (https://support.EMC.com).

Purpose

This document describes how to install, configure, and use the vRealize Data Protection Extension.

Audience

This document is intended for system administrators who will be installing, configuring, and using the vRealize Data Protection Extension. A high degree of knowledge regarding PowerProtect Data Manager and VMware vRealize Automation administration is required.

Revision history

The following table prevents the revision history of this document.

Table 1 Revision history

Revision Date Description

02 November 15, 2019 Fixed several broken links.

01 September 24, 2019 First release of this document for the vRealize Data Protection Extension for PowerProtect version 19.2.

Related documentation

The following publications available at https://support.emc.com provide additional information:

l vRealize Data Protection Extension Release Notes

l PowerProtect Data Manager 19.2 Administration and User Guide

The following VMware publications available at https://www.vmware.com/support/pubs/ provide additional information:

l vRealize Automation documentation:

n Foundations and Concepts

n Installation and Configuration

n System Administration

n IaaS Configuration

n Tenant Administration

l vRealize Orchestrator documentation:

n Using the vRealize Orchestrator plugin for vRealize Automation

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 11

Special notice conventions used in this document

These conventions are used for special notices.

DANGER Indicates a hazardous situation which, if not avoided, results in death or serious injury.

WARNING Indicates a hazardous situation which, if not avoided, could result in death or serious injury.

CAUTION Indicates a hazardous situation which, if not avoided, could result in minor or moderate injury.

NOTICE Addresses practices that are not related to personal injury.

Note: Presents information that is important, but not hazard-related.

Typographical conventions

These type style conventions are used in this document.

Table 2 Typographical conventions

Bold Used for names of interface elements, such as names of windows, dialog boxes, buttons, fields, tab names, key names, and menu paths (what the user specifically selects or clicks)

Italic Used for full titles of publications that are referenced in text

Monospace Used for:

l System code

l System output, such as an error message or script

l Pathnames, filenames, prompts, and syntax

l Commands and options

Monospace italic Used for variables

Monospace bold Used for user input

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means or

{ } Braces enclose content that the user must specify, such as x or y or z

... Ellipses indicate nonessential information that is omitted from the example

Where to get help

The PowerProtect Data Manager support page provides access to licensing information, product documentation, advisories, and downloads, as well as how-to and troubleshooting information. This information may resolve a product issue before contacting Customer Support.

To access the PowerProtect Data Manager support page:

1. Go to https://www.dell.com/support/home/us/en/19.

2. Type a product name in the Enter a Service Tag, Serial Number, Service Request, Model, or Keyword search box.

3. Select the product from the list that appears. When you select a product, the Product Support page loads automatically.

PREFACE

12 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

4. (Optional) Add the product to the My Products list by clicking Add to My Saved Products in the upper right corner of the Product Support page.

Knowledgebase

The Knowledgebase contains applicable solutions that you can search for either by solution number (for example, KB000xxxxxx) or by keyword.

To search the Knowledgebase:

1. Go to https://www.dell.com/support/home/us/en/19.

2. Under the Support tab, click Knowledge Base.

3. Type either the solution number or keywords in the search box. Optionally, you can limit the search to specific products by typing a product name in the search box and then selecting the product from the list that appears.

Online communities

Go to Community Network at http://community.EMC.com for peer contacts, conversations, and content on product support and solutions. Interactively engage online with customers, partners, and certified professionals for all products.

Live chat

To engage Customer Support by using live interactive chat, click Join Live Chat on the Service Center panel of the PowerProtect Data Manager support page.

Service Requests

For in-depth help from Customer Support, submit a service request by clicking Create Service Requests on the Service Center panel of the PowerProtect Data Manager support page.

Note: To open a service request, you must have a valid support agreement. Contact a sales representative for details about obtaining a valid support agreement or with questions about an account.

To review an open service request, click the Service Center link on the Service Center panel, and then click View and manage service requests.

Enhancing support

It is recommended to enable ConnectEMC and Email Home on all PowerProtect Data Manager systems:

l ConnectEMC automatically generates service requests for high priority events.

l Email Home sends configuration, capacity, and general system information to Customer Support.

Comments and suggestions

Comments and suggestions help to continue to improve the accuracy, organization, and overall quality of the user publications. Send comments and suggestions about this document to DPAD.Doc.Feedback@emc.com.

Please include the following information:

l Product name and version

l Document name, part number, and revision (for example, 01)

l Page numbers

l Other details to help address documentation issues

PREFACE

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 13

PREFACE

14 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

CHAPTER 1

Introduction

This chapter includes the following topics:

l vRealize Data Protection Extension for PowerProtect Data Manager....................................16 l Key concepts and components.............................................................................................. 16 l Data protection policy definitions and descriptions................................................................ 17 l vRealize Automation and vRealize Orchestrator integration.................................................. 18 l vRealize Automation endpoints.............................................................................................. 18 l vRealize Automation tasks..................................................................................................... 18 l vCloud Automation vs. vRealize Automation.......................................................................... 19 l Recommended timeout values...............................................................................................20 l PowerProtect limitations.......................................................................................................20

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 15

vRealize Data Protection Extension for PowerProtect Data Manager

VMware vRealize Automation allows authorized administrators, developers, and business users to request new IT services and manage specific cloud and IT resources based on their roles and privileges. The vRealize Data Protection Extension for PowerProtect Data Manager adds data protection to the services available during self-provisioning.

Data protection to a PowerProtect Data Manager system consists of image level data protection (backup and recovery), which protects virtual machines at the disk level.

Note: Information about supported Avamar and NetWorker functionality in vRealize Automation is provided in the vRealize Data Protection Extension 19.1 Installation and Administration Guide at https://support.emc.com/products/38096_vRealize-Data-Protection- Extension-for-Avamar/Documentation/.

With the vRealize Data Protection Extension, the management of data protection is integrated into the standard vRealize Automation workflow. Service Level Agreements (SLAs) seamlessly enable data protection in the cloud. The applications are protected automatically when you enable Dell EMC data protection.

Key concepts and components The following sections define the key components of the vRealize Data Protection Extension.

Users The EMC vRealize Data Protection Extension has two primary intended users. The first user is the data protection administrator. This user most likely has the tenant administrator role in vRealize Automation and should be added to the Administrator Entitlement that is created when running the Install default setup for tenant workflow. This user is responsible for the administration of the EMC vRealize Data Protection Extension. The responsibilities of the user include tenant administration, setting up blueprints with data protection, adding or removing data protection systems, deleting build profiles, and performing any advanced restore requests. For further information regarding these administrative responsibilities, see Administration on page 49.

The second user is the end user. This user most likely has the Business Group User role in vRealize Automation and should be added to the User Entitlement that is created when running the Install default setup for tenant workflow. This end user will provision virtual machines with data protection by using the blueprints that the data protection administrator creates. End users can also perform additional data protection actions on their provisioned virtual machines.

Blueprints vRealize Automation enforces business rules around the self-provisioning of virtual machines using blueprints. A blueprint is the complete specification used to determine one or more virtual machines attributes, the manner in which they are provisioned, and their policy and management settings.

Individual machines or all the machines in the blueprint can be protected using the EMC vRealize Data Protection Extension.

Introduction

16 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Catalog services Self-provisioners select services from a catalog of services to which they are entitled.

Catalog services are backed by one of two types of blueprints:

l Blueprints define the rules about provisioning a virtual machine. l Service blueprints define rules about self-provisioning custom services created with the

Advanced Services mechanism, which is backed by the vRealize Orchestrator component.

Advanced services Advanced Services, also known as XaaS (Anything as a Service), is vRealize Automation's extensible service construct.

The EMC vRealize Data Protection Extension delivers its data protection services as Advanced Services.

l If a service level agreement is assigned to the blueprint, the virtual machine will be added to a data protection policy at provisioning time.

l Blueprints can be configured with or without data protection policies assigned to them.

Property groups A property group is a set of properties to be applied to a machine when it is provisioned.

These properties may determine the specification of the machine, the manner in which it is provisioned, operations to be performed after it is provisioned, or management information about the machine maintained within vRealize Automation. The EMC vRealize Data Protection Extension uses these property groups to add the data protection policy to blueprints.

Data protection policies Data protection policies allow data protection administrators to control backup schedules and retention periods.

Policies map to the underlying data protection provider from which the policy originated, and adhere to the service level agreement (SLA) that the data protection provider supports. For example, PowerProtect Data Manager uses protection policies.

Data protection policy definitions and descriptions Backup policies are created and stored within the data protection system. The vRealize Data Protection Extension does not hold copies of policy definitions but keeps references to the original policy. This allows the backup administrator to modify the policy definition as needed without affecting the vRealize Data Protection Extension's loosely coupled reference.

Note: The policy name references the policy objects. It is recommended that you do not change the policy name after creating it. If you do change the policy name in the data protection system, then associated property groups that reference the policy must either be updated manually or the Setup data protection property group service must be requested again to update the property group with the new policy.

Since policies are referenced by name, It is recommended to use a unique name for each policy across all the data protection providers. For example, if two PowerProtect Data Manager systems contain a policy that is named Gold, two Gold policies appear in some of the workflows in vRA, making it difficult to determine which Gold policy applies to which specific PowerProtect Data Manager system.

Introduction

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 17

Note: The vRealize Data Protection Extension uses the term "policy" to refer to PowerProtect Data Manager protection policies.

For blueprints with multiple components, you can either apply a configured Property Group to the root blueprint properties, which each component will then inherit, or apply to individual components as desired.

vRealize Automation and vRealize Orchestrator integration vRealize Orchestrator is the workflow engine integrated with vRealize Automation. The vRealize Orchestrator server that is distributed with vRealize Automation is pre-configured, and therefore, when the Virtualization Administrator deploys the vRealize Automation Appliance, the vRealize Orchestrator server is up and running.

The vRealize Orchestrator product already offers hundreds of reusable workflows that vRealize Automation workflows can leverage. vRealize Automation workflows can run vRealize Orchestrator workflows, immediately extending the vSphere-oriented use cases for vRealize Automation. With the EMC vRealize Data Protection Extension installed, data protection features are accessible from the vRealize Automation and the vRealize Orchestrator user interfaces.

The vRealize Data Protection Extension includes both vRealize Automation services and public vRealize Orchestrator workflows and actions. General vRealize Orchestrator conventions for versioning and logging of workflows are followed.

Note: vRealize Orchestrator workflows and vRealize Automation services are not used during scheduled protection operations.

vRealize Automation endpoints In vRealize Automation, an endpoint represents an external resource that is assigned to vRealize Automation to manage and allocate on behalf of tenants. In essence, this endpoint is the infrastructure fabric that vRealize Automation manages and makes available via reservations to one or more tenants.

Typically, IaaS administrators are responsible for creating endpoints while setting up the vRealize Automation infrastructure.

The EMC vRealize Data Protection Extension supports vCenter Server endpoints. For information on configuring the vCenter Server as the endpoint, refer to vRealize Automation documentation, which is available on the VMware website.

vRealize Automation tasks The tasks in the following table encompass a typical end-to-end workflow using all required systemsvRealize Automation, vRealize Orchestrator, and your data protection system. The components must be configured and running with the vRealize Data Protection Extension for PowerProtect Data Manager.

Table 3 vRealize Automation tasks

Task Typical User For more information

Install the vRealize Data Protection Extension

System administrator

Installing the Plug-in for vRealize Automation

Introduction

18 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Table 3 vRealize Automation tasks (continued)

Task Typical User For more information

Install the data protection service blueprints and resource actions into a tenant

Tenant administrator or XaaS architect

Installing data protection admin services into a specific tenant on page 34 or the following link

Configure and entitle access to data protection functionality

Tenant administrator

Installing data protection admin services into a specific tenant on page 34

Create a virtual vSphere blueprint

Tenant administrator

Refer to vRealize Automation documentation for instructions on creating blueprints

To enforce data protection rules during provisioning, add data protection to a blueprint

Tenant administrator

Setting up data protection on a blueprint

Use advanced options to restore a virtual machine to a new location

Tenant administrator

Restore a virtual machine to a new location using advanced options on page 54

Restore a deleted virtual machine

Tenant administrator

Restore a deleted virtual machine on page 56

Provision virtual machines from a protected blueprint

Business group user

Provision a protected virtual machine on page 60

Use actions to manage protection on provisioned virtual machines:

l Add data protection to a virtual machine

l Run data protection on a virtual machine

l View protection status and backup inventory

l Remove data protection from a virtual machine

l Restore a virtual machine to its original location

l Restore a virtual machine to a new location

Business group user

Data protection actions Restore actions

View error logs Any user Event and error message codes

vCloud Automation vs. vRealize Automation vRealize Automation is the new brand name to replace VMware vCloud Automation Center (vCAC). Throughout this document, the product is referred to as vRealize Automation. However, sometimes, the vCAC name still exists within the product. The same is true for vRealize Orchestrator, previously referred to as vCenter Orchestrator.

Introduction

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 19

Recommended timeout values It is recommended to set the following timeout values before using the vRealize Automation Data Protection Extension.

Log in to each vRealize Automation server node in the cluster and change each of the following default timeout values in the file /usr/lib/vcac/server/webapps/o11n-gateway- service/WEB-INF/classes/META-INF/spring/root/o11ngateway-service- context.xml to the following values:

l For a system with up to 300 virtual machines, set the connectionTimeout to 120000 ms.

l For a system with 300 to 1000 virtual machines, set the connectionTimeout to 240000 milliseconds.

Run the vRO > Update a data protection system workflow, and for systems that have 300 to 1000 virtual machines, consider changing the default timeout values to the following:

l edp.timeout=240s;ecdm.response.timeout=120s Note: The connectionTimeout values must be greater than or equal to the value for edp.timeout, and the edp.timeout value must be greater than the PowerProtect timeout parameter (ecdm.response.timeout) value.

PowerProtect limitations The following features are not currently supported by the vRealize Data Protection Extension for PowerProtect:

l File-level restore.

l Agent-based application support for blueprints (SQL, Exchange, Oracle, SharePoint).

l PowerProtect does not support multi-tenancy for VMware data protection. Multi-tenancy can be supported with vRA by assigning/dedicating one PowerProtect instance per tenant.

Introduction

20 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

CHAPTER 2

Installation and Upgrade

This chapter includes the following topics:

l Compatibility......................................................................................................................... 22 l Pre-installation...................................................................................................................... 22 l Installing the vRealize Data Protection Extension..................................................................32 l Installing data protection admin services into a specific tenant............................................. 34 l Licensing................................................................................................................................41 l Upgrading the vRealize Data Protection Extension............................................................... 42 l Uninstalling the vRealize Data Protection Extension............................................................. 46

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 21

Compatibility This section describes the components that are required for using the vRealize Data Protection Extension, and the versions of the products that the vRealize Data Protection Extension supports.

Required components Operation of the vRealize Data Protection Extension requires the following products:

l VMware vRealize Automation, including the latest IaaS server

l VMware vRealize Orchestrator

l VMware vSphere

l VMware ESXi Host

l PowerProtect Data Manager Server

Supported product versions for the vRealize Data Protection Extension for PowerProtect Data Manager

The following table lists the software versions that vRealize Data Protection Extension for PowerProtect Data Manager supports.

vRealize Automation and vRealize Orchestrator

PowerProtect

7.4, 7.5, 7.6 19.1, 19.2

Pre-installation Before you install the EMC vRealize Data Protection Extension, perform the following tasks.

Verify the configuration of the vRealize Automation installation Before installing the vRealize Data Protection Extension, verify the following in the base vRealize Automation installation configuration:

l The vRealize Automation Appliance has been deployed and configured

l IaaS components have been installed

l Tenants have been configured

l Agents, endpoints, and groups have been configured

l Blueprints have been created and published

l XaaS services have been set up

l A vRealize Automation (vCAC CAFE) endpoint exists for the default tenant (vsphere.local). Note that you can also create this endpoint by running the Add a vRA host workflow.

l A vRealize Automation Infrastructure Administration endpoint exists for the IaaS component. There is only one endpoint. Note that you can also create this endpoint by running the Add the IAAS host of a vRA host workflow.

Installation and Upgrade

22 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Install the VMware vCenter Orchestrator Plug-in for vCloud Automation Center The VMware vCenter Orchestrator Plug-in for vCloud Automation Center allows interaction between vRealize Orchestrator and vRealize Automation. The plug-in is a .vmoapp file name extension, which is a VMware vCenter Orchestrator application file that you must install in the vRealize Orchestrator Client.

Note: This step is not required when using the vRealize Automation Appliance with the internal vRealize Orchestrator server.

The VMware vCenter Orchestrator Plug-in for vRealize Automation contains the following two plug-ins:

l vCloud Automation Center plug-in for vCenter Orchestrator

l vCloud Automation Center Infrastructure Administration plug-in for vCenter Orchestrator

Refer to the VMware vCenter Orchestrator Plug-in for vCloud Automation Center Release Notes, and download the vCloud Automation Center Plug-in that is specific to the version of vRealize Automation.

Configuring XaaS to recognize vRealize Orchestrator vRealize Automation's XaaS (Advanced Services) depend on an underlying vRealize Orchestrator. If you are using an external vRealize Orchestrator, configure that instance as an endpoint.

About this task

Note: If you are using the vRealize Orchestrator instance that is bundled with the vRealize Automation Appliance, and you have turned on the vRealize Orchestrator service during the general vRealize Automation installation, verify that vRealize Automation automatically points at the internal vRealize Orchestrator instance.

The following procedure configures the external vRealize Orchestrator instance that backs the XaaS/ASD mechanisms.

Procedure

1. Open a browser window, and access vRealize Automation.

2. Log in using the system administrator or tenant administrator credentials.

3. For the system administrator, select Administration > Advanced Services > Server Configuration. For the tenant administrator, select Administration > vRO Configuration > Server Configuration.

4. Point the server to the vRealize Orchestrator. By default, vRealize Automation points to the internal vRealize Orchestrator.

Install and configure a 3-node cluster Perform the following steps to install and configure a 3-node cluster.

Procedure

1. Complete the steps to configure the vRO cluster by using the instructions at the following link:

https://docs.vmware.com/en/vRealize-Orchestrator/7.4/ com.vmware.vrealize.orchestrator-install-config.doc/GUID-0D106F6E-A9C3-4259- AB25-6ADB5640177E.html

2. Complete the steps to configure the load balancer by using the instructions at the following links.

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 23

l For vRO 7.4, go to https://docs.vmware.com/en/vRealize-Automation/7.4/vrealize- automation-load-balancing.pdf

l For vRO 7.5, go to https://docs.vmware.com/en/vRealize-Automation/7.5/vrealize- automation-load-balancing.pdf

3. Log in to the two additional vRO nodes and confirm that vRO and vRO Orchestrator are running.

For example, when you type the commands service vco-server status and service vco-configurator status and the services are not running, type service vco-server start and service vco-configurator start.

4. On the vRealize Orchestrator Control Center main window, click Refresh.

When the configuration is successful, each node displays a status of "Synchronized" in green, as shown in the following.

Figure 1 Synchronized cluster configuration in vRO

Check for the default tenant This section describes how to determine whether you have configured a default tenant and the other required tenants for the EMC vRealize Data Protection Extension system. If not, add a vRealize Automation host for each tenant.

Procedure

1. In vRealize Orchestrator Client, select the Inventory tab.

Figure 2 Inventory tab in vRealize Orchestrator

Installation and Upgrade

24 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

2. Expand vRealize Automation, as shown in the following figure.

Existing tenants are listed.

Figure 3 Existing tenants in vRealize Orchestrator

If one or more of the tenants are missing, add a vRealize Automation host for each of those tenants as described in the following section.

Add a vRealize Automation host About this task

This section describes how to run the Add a vRA host workflow, which adds and configures a vRealize Automation host. If you have already done this task, you can skip this section.

Procedure

1. In the vRealize Orchestrator Client, select the Workflows tab.

Figure 4 Workflows tab in vRealize Orchestrator

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 25

2. Browse to /Library/vRealize Automation/Configuration.

3. Right-click Add a vRA host, and select Start Workflow.

Figure 5 Start Workflow in vRealize Orchestrator

The workflow wizard opens on the Add a vRA host screen.

Installation and Upgrade

26 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Figure 6 Start Workflow: Add a vRA host

4. In the Add a vRA host screen, supply the following information:

l Host Name: Type the tenant, "default tenant" or the actual tenant name.

l Host URL: Type the vCloud Automation Center/vRealize Automation Appliance URL.

l Automatically install SSL certificates: Select Yes.

5. Click Next.

The Host Authentication screen displays.

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 27

Figure 7 Host Authentication in Start Workflow wizard

6. In the Host Authentication screen, type the tenant name and the tenant administrator credentials.

7. Click Submit.

8. Repeat this procedure for each tenant that you are configuring.

Adding an IaaS host This section describes how to add an IaaS (Infrastructure-as-a-Service) host.

Procedure

1. In the vRealize Orchestrator Client, select the Workflows tab.

2. Browse to /Library/vRealize Automation/Infrastructure Administration/ Configuration.

3. Right-click Add an IaaS host, and select Start workflow.

Installation and Upgrade

28 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Figure 8 Start workflow in vRealize Orchestrator

The workflow wizard opens to the Add an IaaS host screen.

Figure 9 Add an IaaS host in Start workflow wizard

4. In the Add an IaaS host Host Properties screen:

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 29

l Type the IaaS hostname in both the Name and the Host fields.

l Select Yes for Automatically install SSL certificates.

5. In the Add an IaaS host Connection Settings screen, select Yes for default connection settings.

6. Click Next.

The Host Authentication - User credentials screen displays.

Figure 10 Host Authentication in Start workflow wizard

7. In the Host Authentication - User credentials screen, type the vRealize Automation service account name (without the domain) and password, and click Next.

The Host Authentication - Domain and Workstation screen displays.

Installation and Upgrade

30 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Figure 11 Host Authentication in Start workflow wizard

8. In the Host Authentication - Domain and Workstation screen, type the domain name in the Domain for NTLM authentication field, and click Submit.

9. To verify that the new IaaS host has been created, select the Inventory tab.

10. Expand vRealize Automation Infrastructure > host > Provisioning Groups.

If valid provisioning groups are listed as shown in the following figure, the connection was successful.

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 31

Figure 12 Valid provisioning groups under vRealize Automation Infrastructure

Verify vCenter endpoints vRealize Orchestrator is bundled with a vCenter plug-in. If you configured an external vRealize Orchestrator in the previous section, you must re-add the vCenter endpoint. A vCenter endpoint must exist, since this endpoint enables the provisioning of virtual machines in vRealize Automation.

You can create the endpoint by running the vRealize Orchestrator Add a vCenter Server instance workflow (located in /Library/vCenter/Configuration) or from the Administration > vRO Configuration > Endpoints tab in vRealize Automation.

Installing the vRealize Data Protection Extension The vRealize Data Protection Extension is packaged as a vRealize Orchestrator vmoapp. The vmoapp contains a vRealize Orchestrator plug-in and a package of workflows and actions.

The vRealize Data Protection Extension is designed so that it can be consumed as Advanced Services and Resource Actions within vRealize Automation. Organizations that are accustomed to using workflows from the vRealize Orchestrator level can leverage the workflows in that context as well.

You can install the vmoapp either from the vRealize Orchestrator Control Center, or from the command line, as described in the following two sections.

Install the vmoapp using vRealize Orchestrator About this task

If you are using multiple vRealize Orchestrator (vRO) nodes in a cluster, install the vmoapp by connecting to a load balancer vRO hostname/IP.

Procedure

1. Open the browser to the vRealize Orchestrator Control Center.

If using the local vRO server, this system is the vRealize Automation server. Otherwise, the system is the external vRO server. Note that using a Cluster vRO requires you to use the

Installation and Upgrade

32 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

load balancer IP/FQDN to connect to the vRealize Orchestrator Control Center and install the plug-in.

2. Click Manage Plug-ins on the main window.

3. Click Browse..., select the .vmoapp file that you want to install, and click Install.

4. Read and accept the license agreement, and then click Install.

The installation should complete quickly.

5. In the main window, select Startup Options, and restart the vRO server.

To specifically restart the vRO server, use the SSH command to run the following on the vRA nodes:

service vco-server restart service vco-configurator restart

After running the commands, wait for a few minutes to ensure all of the nodes become synchronized. Note that in vRO versions 7.4 and later these services are restarted automatically after a few minutes.

6. Check the vRealize Automation configuration by running the Check EMC data protection configuration workflow. Instructions are provided in Check the vRealize Data Protection Extension configuration on page 76.

Install the vmoapp from the command line If you prefer, you can install the vmoapp from the command line rather than using vRealize Orchestrator Configuration web application. For a vRO cluster, it is recommended to perform the installation from the vRO load balancer Control Center.

Procedure

1. Use an http client, such as curl, to upload the .vmoapp file to the vRealize Orchestrator server. For example:

$ curl --insecure --user 'user:password' --form file=@/path/to/.vmoapp -- form format=vmoapp https://vro.server:8281/vco/api/plugins

Note: The port on vRealize Orchestrator bundled with vRealize Automation is now port 443. However, you should continue to use port 8281 if using a standalone vRealize Orchestrator appliance.

2. Restart the vco-server service on the vRealize Orchestrator server. The following example illustrates how to do this using the ssh command:

$ ssh user@vro.server service vco-server restart

3. Check the vRealize Automation configuration by running the Check EMC data protection configuration workflow. Instructions are provided in Check the vRealize Data Protection Extension configuration on page 76.

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 33

Installing data protection admin services into a specific tenant This section describes how to use the vRealize Orchestrator Install default setup for tenant workflow to automate some of the Advanced Services configuration steps.

Before you begin

l For the tenant you are setting up, there must be a user configured with credentials having Infrastructure Architect, Tenant Administrator and XaaS Architect roles. When adding the vRealize Automation host, a user with these roles is required.

Note: For a secondary tenant, you must have both the vsphere.local default tenant and the secondary tenant added as vRealize Automation (vCAC CAFE) hosts.

l A business group must exist, to which the data protection admin services are entitled.

l Data protection systems such as NetWorker, Avamar or Avamar Virtual Edition (AVE) must be installed, and the versions must be supported as described in the compatibility and interoperability matrix documents for the respective systems.

l If using Avamar or NetWorker, vRealize Automation vCenter endpoints must be registered with the data protection systems using the fully qualified domain name (FQDN).

l If using Avamar or NetWorker for image-level backups, proxies compliant with the server version must be deployed within the vCenter endpoints and registered with their respective data protection systems.

WARNING The data protection admin services should not be exposed to any user who does not qualify as an administrator of the data protection services.

Procedure

1. Log in to the vRealize Orchestrator client.

2. Select the Workflows tab.

3. Browse to /Library/EMC/Data Protection/vRA/Installation.

4. Right-click the Install default setup for tenant workflow and select Start Workflow as shown in the following figure.

Installation and Upgrade

34 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Figure 13 Start Workflow in vRealize Orchestrator

The workflow wizard opens on the vCloud Automation Center screen.

Figure 14 Start Workflow wizard

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 35

5. If you have already created the tenant-specific vCloud Automation Center host (as described in Adding a vCloud Automation Center host, perform the following three steps. If you have not created the host, continue to step 6.

a. Click the Not set link in the top-most field.

The vCACCAFE Host dialog box opens.

Figure 15 Select vCACCAFE Host dialog

b. In the left pane, expand the vCloud Automation Center list.

c. Select the tenant-specific vCAC host, and then click Select.

You are returned to the workflow wizard. Continue to step 7.

6. If you have not created a tenant-specific vCloud Automation Center host (as described in Adding a vCloud Automation Center host, supply the following information in the vCloud Automation Center screen to create the host.

Note: When you enter this information manually, the workflow creates the vCenter Automation Center host for you. However, you cannot use the Chooser dialog boxes to select existing vRealize Automation Catalogs and Entitlements in the following screens. You must specify them manually.

l The new vCloud Automation Center host name: Type a hostname for the vRealize Automation host. You can choose any name, but best practice is to provide the name of the tenant.

l The new vCloud Automation Center host url: Type the base URL for the vRealize Automation host (for example, https:// ...).

l The new vCloud Automation Center host tenant: Type the tenant URL name (for example, vsphere.local).

l The new vCloud Automation Center host user: Type the username for a user who has both the tenant administrator and the service architect roles for the tenant.

l The new vCloud Automation Center host password: Type the password for the user specified in the previous field.

Installation and Upgrade

36 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

7. Click Next.

The Catalog Service screen displays. Data protection admin services are published in the catalog service.

Figure 16 Catalog Service in Start Workflow wizard

8. On the Catalog Service screen, click Not set to select an existing catalog service, or type a name to create one.

9. Click Next.

The Administrator Entitlement screen displays. On this screen, you can entitle the data protection admin services to data protection admin users.

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 37

Figure 17 Administrator Entitlement in Start Workflow wizard

10. On the Administrator Entitlement screen, do the following:

l The administrator entitlement name: To select an existing administrator entitlement name, or type a new entitlement name, Click Not set.

Note: If you type the entitlement name, the system automatically creates the entitlement. However, a newly created entitlement does not have any users. Users must be added manually to the entitlement in vRealize Automation after the installation completes.

l The administrator entitlement description: Optionally, type a description for the entitlement.

l The administrator entitlement business group name: To select an existing business group name, or type the name of an existing business group, click Not set.

11. Click Next.

The User Entitlement screen displays.

Installation and Upgrade

38 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Figure 18 user Entitlement in Start Workflow wizard

12. On the User Entitlement screen, do the following:

l The user entitlement name: To select an existing entitlement name, or type a user entitlement name, click Not set.

Note: If you type the entitlement name, the system automatically creates the entitlement. However, a newly created entitlement does not have any users. Users must be added manually to the entitlement in vRealize Automation after the installation completes.

l The user entitlement description: Optionally, type a description for the entitlement.

l The user entitlement business group name: To select an existing business group name, or type the name of an existing business group, click Not set.

13. Click Next.

The Data Protection screen displays.

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 39

Figure 19 Data Protection in Start Workflow wizard

14. On the Data Protection screen, do the following:

l The data protection type to configure: Select the data protection system (Avamar or NetWorker) used to protect the tenant.

l The data protection system hostname: Type the data protection system's FQDN.

l The data protection system port: Leave the data protection system port field blank unless the data protection system has been configured to listen on a non-standard port.

l The data protection system username: Type the username required to log in to the data protection system.

l The data protection system password: Type the password required to log in to the data protection system.

l The data protection system custom connection properties: Leave this field blank.

15. To run the workflow, click Submit.

16. Verify that the workflow ran successfully as follows:

a. After the workflow has finished running, watch for State - completed in the workflow output.

b. View the data protection endpoint by selecting the Inventory tab, and clicking EMC Data Protection. If the endpoint does not immediately display, right-click EMC Data Protection and select Reload.

c. If the vRealize Automation tenant-specific host was created by the workflow, verify that it exists for the tenant.

d. Log in to vRealize Automation as a tenant administrator (any user who was entitled to the data protection admin services published above).

e. On the Catalog tab, select the service that you created or selected.

Installation and Upgrade

40 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

f. Verify that you see the data protection service blueprints.

You use the services to add data protection to the business rules incorporated in a blueprint.

17. Optionally, check the vRealize Data Protection Extension configuration as described in the section Check the vRealize Data Protection Extension configuration on page 76.

Licensing Currently, you can order the EMC vRealize Data Protection Extension at no cost through the EMC DirectXpress (DXP) or ChannelXpress (CXP) ordering process. A License Authorization Code (LAC) letter is emailed or physically delivered to customers and partners during order processing and fulfillment. The LAC letter contains instructions for downloading software binaries as well as activating the license, entitlement, and generating the licensing key and/or file via the licensing website. The vRealize Data Protection Extension requires this licensing file, which you must place on the vRealize Orchestrator server.

The following sections describe where to put the licensing file on the Orchestrator server, and how to verify the validation check that is performed by the licensing.

Linux-based vRealize Orchestrator server Procedure

1. Log in as root to the Linux system where the vRealize Orchestrator server is installed.

2. Browse to the following directory:

/var/lib/vco/app-server/conf/plugins/ 3. In this directory, create a folder named edplicense.

4. Secure FTP the license file from the download location to the edplicense directory.

5. To change the owner of the edplicense directory and of the license file to the vCO user, type the following commands:

chown vco:vco /var/lib/vco/app-server/conf/plugins/edplicense chown vco:vco /var/lib/vco/app-server/conf/plugins/edplicense/ edplicenseFileName

6. Open the browser to the vRealize Orchestrator Configuration web application for the vRealize Automation system, and in the left-hand pane, select Startup Options, and restart the vRealize Orchestrator server.

Results

The license file will now reside in /var/lib/vco/app-server/conf/plugins/edplicense. The EMC vRealize Data Protection Extension will look in this directory to find the file and to validate its contents after any EMC plug-in operation is performed.

Verifying the licensing validation check This section describes where to look in the log files to verify that the validation check performed by the plug-in licensing was successful.

The log files and their locations are listed as follows:

l Linux /var/lib/vco/app-server/logs, which is sym-link'ed to /var/log/ vmware/vco/app-server/

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 41

l Windows C:\Program Files\VMware\Infrastructure\Orchestrator\app- server\logs

l Files:

n catalina.out log file may or may not have an entry, depending on platform

n edp_4_vcac.log file has an entry

n server.log file has an entry

The following example shows a successful validation:

2016-12-05 23:33:46.236+0000 [ForkJoinPool.commonPool-worker-1] [doStartup] INFO {} [EdpAdapter] Starting EMC vRealize Data Protection Extension v4.0.0.76 2016-12-05 23:34:23.322+0000 [http-nio-127.0.0.1-8280-exec-9] [createPluginFactory] INFO {} [EdpAdapter] Initializing EMC vRealize Data Protection Extension v4.0.0.76 2016-12-05 23:34:23.591+0000 [http-nio-127.0.0.1-8280-exec-9] [readFeatures] INFO {} [EdpAdapter] License Feature: vra_edp_plugin Valid: true 2016-12-05 23:34:23.600+0000 [http-nio-127.0.0.1-8280-exec-9] [readFeatures] INFO {} [EdpAdapter] License Feature: VRA_EDP_PLUGIN Valid: true

The following example shows a validation that failed with an invalid file in place:

2016-12-05 23:40:10.570+0000 [ForkJoinPool.commonPool-worker-1] [doStartup] INFO {} [EdpAdapter] Starting EMC vRealize Data Protection Extension v4.0.0.76 2016-12-05 23:40:48.869+0000 [http-nio-127.0.0.1-8280-exec-8] [createPluginFactory] INFO {} [EdpAdapter] Initializing EMC vRealize Data Protection Extension v4.0.0.76 2016-12-05 23:40:49.128+0000 [http-nio-127.0.0.1-8280-exec-8] [readFeatures] WARN {} [EdpAdapter] ClientTestFeature2: Warning! Soft error detected=License path "/var/lib/vco/app-server/../app-server/conf/plugins/ edplicense" error: no valid license files found. (-1,0) 2016-12-05 23:40:49.129+0000 [http-nio-127.0.0.1-8280-exec-8] [readFeatures] WARN {} [EdpAdapter] ClientTestFeature2: No license files were found. 2016-12-05 23:40:49.129+0000 [http-nio-127.0.0.1-8280-exec-8] [readFeatures] INFO {} [EdpAdapter] License Feature: vra_edp_plugin Valid: false 2016-12-05 23:40:49.137+0000 [http-nio-127.0.0.1-8280-exec-8] [readFeatures] WARN {} [EdpAdapter] ClientTestFeature2: Warning! Soft error detected=License path "/var/lib/vco/app-server/../app-server/conf/plugins/ edplicense" error: no valid license files found. (-1,0) 2016-12-05 23:40:49.138+0000 [http-nio-127.0.0.1-8280-exec-8] [readFeatures] WARN {} [EdpAdapter] ClientTestFeature2: No license files were found. 2016-12-05 23:40:49.139+0000 [http-nio-127.0.0.1-8280-exec-8] [readFeatures] INFO {} [EdpAdapter] License Feature: VRA_EDP_PLUGIN Valid: false

Upgrading the vRealize Data Protection Extension This section describes how to upgrade an existing vRealize Data Protection Extension installation to the latest version. It assumes that you have already downloaded the edp4vcac-19.2.0.n.vmoapp file, where n is the build number.

Note: Before upgrading, it is recommended to back up or take snapshots of the vRealize infrastructure, including:

l The vRealize Automation server.

l The vRealize Automation database.

l The vRealize Orchestrator server(s) (if using external servers).

Installation and Upgrade

42 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

While upgrading the vRealize Data Protection Extension, you can continue to perform data protection system operations, including scheduled backups. You cannot, however, perform the following:

l During the upgrade, you are not able to:

n Run data protection

n Restore data

n View protection status

n Add/remove data protection

n Perform property group operations

n Add/remove data protection systems

n Set up a data protection property group

l During restart of the vRealize Orchestrator server(s), you are not able to:

n Assign data protection during virtual machine provisioning

n Retire the protection client during virtual machine destroy

After the upgrade completes, the existing Dell EMC data protection systems will be available, and all policies, clients, and backups will still be available.

Note: If upgrading from vRealize Data Protection Extension version 3.0 or earlier, note the following changes to naming and workflows:

l Build Profiles are now identified as Property Groups

l Machine Blueprints are now identified as Blueprints and will become new Blueprints. Multi- machine Blueprints become Blueprints with multiple machine components.

l New Property Groups will be mapped to new blueprint components.

Install the vRealize Data Protection Extension vmoapp

Install the vRealize Data Protection Extension vmoapp and verify the installation as described in Installing the Plug-in for vRealize Automation.

Note: If using multiple vRealize Orchestrator nodes in a cluster, use the vCO Orchestrator Control Center to monitor the cluster synchronization progress.

Update the default setup in each vRealize Automation tenant This procedure deletes and re-creates the catalog items and resource actions (and their forms) that were added to the vRealize Automation service catalog in the previous release.

If you previously applied form customizations to the catalog items or resource actions, or changed the icon, those changes are lost and must be reapplied in vRealize Automation. The update process maintains the previous entitlements and approval policies, if any. After performing this update, verify the entitlement(s) on each catalog item and resource action.

You can run the update workflow to update all tenants, or to update individual tenants.

Note: If you are using multiple vRealize Orchestrator nodes in a cluster, this update only must be run on one of them against the vRealize Automation server.

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 43

Running the update workflow for all tenants This section describes how to run the workflow that updates all the vRealize Automation tenants of the data protection systems that support the virtual machine's vCenter host.

Procedure

1. In the vRealize Orchestrator client, select the Workflows tab.

2. Browse to the following workflow:

Library/EMC/Data Protection/vRA/Installation/ 3. Select the Update default setup for protected tenants workflow, and click the green

arrow ( ) in the upper-left corner of the right-hand pane to start the workflow.

Figure 20 Workflow interaction form

If the Workflow interaction form does not open automatically, select the icon at the top of the workflow editor.

Note: You are prompted with a workflow interaction form for each vRealize Automation tenant in the system that has been configured with the vRealize Data Protection Extension and supports the virtual machine's vCenter host. If you want to skip updating a particular tenant, select No for the Update setup for tenant? option, and then click Submit (do not click Cancel).

4. In the Workflow interaction form, click Not set for each of the parameters (catalog service, entitlement for tenant administrators, and entitlement for tenant users), and select the appropriate options in the Chooser dialog box.

5. When you have set the parameters, click Submit.

Installation and Upgrade

44 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Running the update workflow for individual tenants This section describes how to run the workflow that lets you select a vRealize Automation tenant to update.

Procedure

1. In the vRealize Automation client, select the Workflows tab.

2. Browse to the following workflow:

Library/EMC/Data Protection/vRA/Installation/ 3. Select the Update default setup for tenant workflow, and click the green arrow ( ) in the

upper-left corner of the right-hand pane to start the workflow.

The Start Workflow : Update default setup for tenant form opens.

Figure 21 Start Workflow : Update default setup for tenant

4. For The vRealize Automation center host, tied to a tenant parameter, Click Not set, and select the vRealize Automation tenant that you want to update in the Chooser dialog box.

5. Click Not set for each of the remaining three parameters (catalog service, entitlement for tenant administrators, and entitlement for tenant users), and select the appropriate options in the Chooser dialog box.

6. An additional upgrade option will remove the old ExternalWfStub.* properties from upgraded blueprints, now referred to as property groups. Prior to selecting Yes to remove these properties, EMC recommends that you back up your blueprints by using the instructions at the following link.

7. When you have set the parameters, click Submit.

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 45

Update custom workflows and actions In vRealize Orchestrator, if you have written custom workflows or actions that use the EMC vRealize Data Protection Extension's workflows, actions, or scripting objects, you must verify the code against the new version in the vRealize Orchestrator client.

Verifying the new version After upgrading the EMC vRealize Data Protection Extension and restarting the vRealize Orchestrator server, use one of the following methods to verify that the system has the correct new version:

About this task

l Select Help > Installed Plug-ins in the vRealize Orchestrator Control Center.

l Select Manage Plug-ins in the left-hand pane of vRealize Orchestrator Control Centre. Note: If you deployed the .vmoapp file using an http client, restart the vRealize Orchestrator Configuration server to see the updated version here.

l View the contents of the Workflows and Actions tabs for the com.emc.edp4vcac package in the vRealize Orchestrator client. All the workflows and actions should have a new version number.

Uninstalling the vRealize Data Protection Extension

The following sections describe how to uninstall the vRealize Data Protection Extension. The tasks include removing data protection from each tenant, and uninstalling the extension from vRealize Orchestrator.

Uninstall EMC data protection from a single tenant The following two sections describe how to remove default setup items, and how to reconfigure vRealize Automation blueprints for a single tenant. These procedures must be performed on each vRealize Automation tenant.

Remove default setup items This procedure describes how to remove the catalog items and resource actions.

You can also remove the EMC data protection system configured for the vRealize Automation tenant.

1. Open the vRealize Orchestrator client.

2. In the Workflows tab, browse to /Library/EMC/Data Protection/vRA/ Installation/Uninstall, and run the Remove default setup for tenant workflow.

3. Select the vRealize Automation host connection for the tenant.

4. Select if you want to remove the EMC data protection system(s) configured for the tenant. If you do not remove the configured systems for the tenant, you can still perform protection operations through vRealize Orchestrator.

Alternate Procedure

If preferred, you can uninstall the plug-in from a tenant using the following steps.

1. In vRealize Automation, delete the catalog items and resource actions manually.

Installation and Upgrade

46 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

2. In the vRealize Orchestrator client's Workflows tab, browse to /Library/EMC/Data Protection/vRO/Configuration, and run the Remove a data protection system workflow to remove the systems configured for the tenant.

Reconfigure vRealize Automation blueprints

About this task

After removing the default setup items, reconfigure the blueprints.

Procedure

1. Open vRealize Automation.

2. Browse to Design > Blueprints, and update any Blueprints available to the tenant that you had previously configured for data protection during provisioning and retiring.

3. Remove from the blueprint any property groups that were created and/or configured for data protection.

4. Browse to Administration > Property Dictionary, and remove any property groups that were created and/or configured for data protection (generally, by using the Setup data protection property group), and remove their associated property definitions.

Uninstall the plug-in from vRealize Orchestrator This section describes how to uninstall the vRealize Data Protection Extension from vRealize Orchestrator.

Before you begin

The vRealize Data Protection Extension must have been uninstalled from each tenant in vRealize Automation.

Procedure

1. Open the vRealize Orchestrator client.

2. In the Inventory tab under the EMC Data Protection branch, verify that all the data protection systems were removed. If they were not, right-click each one, select Run Workflow... > Remove a data protection system, and run that workflow.

Note: Ensure that you take a backup or snapshot of the vRealize Orchestrator virtual machine in case you need to revert the changes.

3. For vRO versions 7.4 and later, use the instructions provided in the following VMware documentation:

l https://kb.vmware.com/s/article/2151653

l https://docs.vmware.com/en/vRealize-Orchestrator/7.4/ com.vmware.vrealize.orchestrator-install-config.doc/GUID-F5C8EF0E- C169-43E1-8A6F-D9A191FE129D.html

Note: Replace "7.4" in the link above with your specific vRO version if not using vRO version 7.4.

Note the following information when performing the steps in the Knowledge Base article:

l The dar file is edp4vcac.dar l The package to remove in the vRealize Orchestrator client is com.emc.edp4vcac l If using a vRO cluster, repeat the steps in https://docs.vmware.com/en/vRealize-

Orchestrator/7.4/com.vmware.vrealize.orchestrator-install-config.doc/GUID-

Installation and Upgrade

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 47

F5C8EF0E-C169-43E1-8A6F-D9A191FE129D.html on all vRO nodes separately before starting vCO services.

4. Verify that all the com.emc.edp action modules are deleted; if not, delete them in the vRealize Orchestrator client.

5. Verify that the /Library/EMC/Data Protection workflow folder is empty and/or delete it in the vRealize Orchestrator client.

Installation and Upgrade

48 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

CHAPTER 3

Administration

This chapter includes the following topics:

l Data protection configuration for the tenant.........................................................................50 l Data protection administration...............................................................................................51

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 49

Data protection configuration for the tenant The EMC vRealize Data Protection Extension provides the ability to perform data protection operations within vRealize Automation.

These operations are configured at a per-tenant level and consist of two main components:

l A set of data protection XaaS Blueprints which are made available to data protection administrators.

l A set of XaaS Resource Actions which are made available so that owners of virtual machines can manage their own data protection needs on a per-virtual machine basis.

Clustered vRealize Orchestrator environment The EMC vRealize Data Protection Extension supports a clustered vRealize Orchestrator (vRO) environment. However, the Data Protection system information is stored locally on each vRO appliance. Therefore, in a clustered vRealize Orchestrator environment, you must run the Install default setup for tenant workflow per tenant on one of the vRO appliances.

Additionally, if you want to replicate the configuration information among the other nodes in the cluster, you must synchronize this vRO appliance with the other nodes. For example, if the vRO appliance that you run the Install default setup for tenant workflow on is node A, to synchronize the other nodes in the cluster with node A:

1. Log in to the vRO Control Center of each of the other nodes.

2. Invoke Join Node to Cluster.

3. Specify the Remote Orchestrator Server as Node A (IP address or hostname).

4. Provide the Remote Orchestrator Server's vRO Control Center credentials.

This replicates the configuration information of node A into the current node. Even if the cluster was formed previously, you must repeat this step and specify the number of active nodes for any configuration changes to occur.

Note that in an environment with clustered vRO appliances, you may need to perform the steps above for the following workflows as well:

l Remove a data protection systemIf you want to remove a tenant data protection system, run the Remove a data protection system workflow from the vRealize Orchestrator client of each vRO in the cluster, or from the vRealize service catalog, per tenant on one of the vRO appliances. This removes the EDP system from one of the nodes in the cluster. You must then perform the steps above to replicate this removal on the other nodes.

l Add a tenant data protection systemIf you want to add a tenant data protection system, run the Install default setup for tenant or Add a tenant data protection system workflow per tenant on one of the vRO appliances. You must then perform the steps above to replicate this addition on the other nodes.

l Update a tenant data protection systemThis is a vCO workflow that is not currently available in vRA, and is located under Library/EMC/Data Protection/vRO/ Configuration. After running this workflow, you must then perform the steps above to replicate the update on the other nodes.

Note: In a clustered vRealize Orchestrator environment with load balancing of vRA traffic across two vRO systems, the EdpSystem ID on both vRO systems must match. If the IDs do not match, and you run the vRA request for findAll on one vRO and then send a findById using that list to the other vRO, the unique ID created for clients, policies, and so on, do not match and result in some empty select boxes in vRA. To ensure that both systems have the same

Administration

50 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

EdpSystem ID, log in to the vRO Control Center and invoke Join Node to Cluster. This joins the vRealize Orchestrator server to another vRealize Orchestrator server to form or expand a cluster. The current server automatically replicates the configuration of the remote server. You can then restart the vRO services on the updated systems by using Startup Options in the vRO Control Center.

Multi-tenancy support with PowerProtect Data Manager PowerProtect Data Manager does not natively support multi-tenancy for VMware data protection.

In order to support multi-tenancy in vRA with these data protection systems, it is recommended that for each tenant in vRA there should be a dedicated PowerProtect Data Manager instance. The data protection policies in the tenant's PowerProtect Data Manager instance will then only apply to that tenant.

In cases where the backup administrator is allowed to view all virtual machines across multiple tenants, it may be possible to share a PowerProtect Data Manager instance for multiple vRA tenants.

Data protection administration After the one-time configuration of the data protection system connection information, the tenant administrator must assign available data protection policies to virtual machine blueprints.

Service blueprints The following table lists the vRealize Data Protection Extension XaaS blueprint names and descriptions. These XaaS blueprints are added to the service catalog for the data protection administrator user with the Administrator Entitlement, which you create by running the Install default setup for tenant workflow in vRealize Orchestrator.

Table 4 Service catalog blueprints

Service blueprint name Description

Add a tenant data protection system

Configures and adds a Dell EMC Data Protection system to the vCenter Orchestrator inventory. Dell EMC's PowerProtect Data Manager system offers data backup, recovery, and archiving.

Remove a tenant data protection system

Removes a vRealize Data Protection system from the vRealize Orchestration inventory. Typically, this service blueprint is only required if the user wants to change the data protection system.

Set up a data protection property group

Allows you to add or modify data protection on a new or existing property group. Both image-level and application- consistent protection policies are available. If you select an application-consistent protection policy, an optional configuration field allows you to specify a time in minutes that the custom workflow should wait to discover a configured hostname of the virtual machine.

Restore deleted machine from backup

Restores a deleted virtual machine that had data protection and backups on a PowerProtect Data Manager server. The machine is restored as a new virtual machine.

Administration

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 51

Configuring a PowerProtect data protection system This topic describes how to configure a PowerProtect system by using vRealize Automation. After you have configured the system, you can verify that it has been added by logging in to the vRealize Orchestrator Client.

Before you begin

You must be logged in to vRealize Automation as a user with the administrator entitlement, as defined in the Install default setup for tenant workflow.

Procedure

1. In vRealize Automation, select the Catalog tab.

2. In the left pane, click the data protection service.

3. In the Services pane, click Request for Add a tenant data protection system.

The Add a tenant data protection system page displays, open on the System Information tab.

4. In the System Information tab:

a. Select PowerProtect Data Manager from the drop-down list.

b. Type the FQDN of the system that you are adding.

c. Optionally, select a port, and type custom properties.

d. To display the Credentials tab, click Next.

5. In the Credentials tab:

a. Type the username and password that is required to access the data protection system.

b. Click Submit.

6. To close the request configuration message, click OK.

7. Select the Requests tab, and view the progress of the PowerProtect system addition until it completes successfully.

8. To verify that the data protection system has been successfully added, log in to the vRealize Orchestrator Client.

The client opens on the My Orchestrator tab.

9. Select the Inventory tab.

10. In the Inventory tab, click the arrow beside EMC Data Protection to expand its list.

The PowerProtect server displays.

Set up data protection on a blueprint To add data protection to a blueprint in vRealize Automation, perform the following steps. Once the data protection has been added to the blueprint, the business group user can apply data protection to a virtual machine at the time of provisioning.

About this task

During this procedure, you create a property group that contains either a list of user-selectable policies, or a single, non-selectable policy. A selectable-policy property group allows the business group user to choose a policy when requesting a blueprint. A non-selectable-policy property group contains a single policy that is applied automatically when the business group user requests a blueprint.

Administration

52 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Procedure

1. In vRealize Automation, browse to Catalog > Setup data protection property group, and click Request.

The Setup a data protection property group page displays.

2. Create a property group or select an existing one.

l To create a property group:

a. Select [New Property Group] from the drop-down list.

b. Specify a name, a unique ID, and an optional description. Note: The property group created will only be visible by the current tenant.

c. To display the Data Protection tab, click Next.

l To use an existing property group, select the property group from the drop-down list, and click Next to display the Data Protection tab.

Note: You can use existing property groups that do not have data protection. Any required data protection properties will be added to the property group. If the property group already has data protection properties, you can select one or more policies to add to the existing policy for the property group.

3. In the Data Protection tab, you can decide whether the business group user can select one or more protection policies when the blueprint is requested. Also, you can select the policy or policies that the property group uses.

The property group can contain either a list of selectable policies or a single, non-selectable policy that is applied automatically to the virtual machine at provisioning time.

l To create or update a property group with selectable policies:

a. In the Allow user to select data protection policy when blueprint is run? drop- down, select Yes.

b. If the VM is a database server (for example, if the VM is an Oracle database), EMC recommends protecting the virtual machine with both the Application consistent data protection policy and an Image level data protection policy.

c. Select the checkbox next to one or more policies in the list. Note: Ensure that the selected policy's detailed information contains the name of the vCenter that will manage the virtual machines to be provisioned in the future.

d. If you select an Application Consistent Data Protection policy, specify a time in minutes that the custom workflow should wait to discover a configured hostname of the virtual machine. The default is 10 minutes.

l To create or update a property group with a non-selectable policy that is applied automatically to the virtual machine at provisioning time:

a. In the Allow user to select data protection policy when blueprint is run? drop- down, select No.

b. If the VM is a database server (for example, if the VM is an Oracle database), EMC recommends protecting the virtual machine with both the Application consistent data protection policy and an Image level data protection policy.

c. Select one policy in the list.

d. If you select an Application Consistent Data Protection policy, specify a time in minutes that the custom workflow should wait to discover a configured hostname of the virtual machine. The default is 10 minutes.

4. Click Submit.

Administration

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 53

Edit the blueprint by navigating to the Design > Blueprints tab, and adding the property group to either the blueprint directly or to one or more components of the blueprint. The vRealize Automation documentation available at the following link provides more information.

Restoring application backups You can perform restores of application backups by using the PowerProtect Data Manager user interface.

The PowerProtect Data Manager Administration and User Guide, available at http://dell.com/ support, provides instructions.

Restore a virtual machine to a new location using advanced options Tenant administrators can use advanced options to restore a virtual machine backed up with PowerProtect Data Manager to a new location. These options are additional to the options available to a business group user when restoring a virtual machine to a new location.

Before you begin

l You must be logged in to vRealize Automation as a user with the administrator entitlement, as defined in the Install default setup for tenant workflow.

l The virtual machine that you plan to restore must have one or more existing image level backups to PowerProtect Data Manager. Restores of virtual machines that are backed up using an application-consistent policy are not available.

Procedure

1. In vRealize Automation, select the Items tab.

2. In the left pane, click Machines.

The Machines list displays in the right pane.

3. In the Owned by list, select the group that owns the virtual machine that you plan to restore.

Only the machines that are owned by that group are displayed in the Machines list.

4. Click the row of the machine that you want to restore.

The row is highlighted. Note: If you are unsure if a machine has been backed up, select View protection status from the Actions menu. Existing image-level backups are listed in the scrolling status field.

5. From the Actions menu, select Advanced restore to new.

The Advanced restore to new page opens on the Restore Options tab.

6. In the Restore Options tab, select a backup from the drop-down list or search for backups by date range. You can also limit the number of backups that are listed.

a. If you want to filter the backups by date range, select Yes, and select the Start Date and time and the End Date and time.

b. Select the maximum number of backups that you want to view.

c. To display the backups that match the filter criteria, click the Backup drop-down list.

d. Select the backup that you want to restore.

Note: When you select a backup, the new name for the virtual machine is populated automatically. If you change the name, Dell EMC recommends that you follow the

Administration

54 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

naming standard as outlined in the VMware knowledgebase article at https:// kb.vmware.com/s/article/2009820 and the Microsoft knowledgebase article at http:// support.microsoft.com/kb/909264.

7. To display the Advanced Options tab, click Next.

The advanced options on this tab are described in the following list.

l Reservation to put the virtual machine in: Where to create the virtual machine. The reservation the original virtual machine was in is selected by default. Only the reservations available for the original virtual machines owner are visible based on the business groups they belong to.

l Datastore to store the virtual machine disks: Select the datastore within the reservation to put the virtual machine in. The list of available datastores is based on the datastores that have been configured for the selected reservation. The datastore that is used for the original virtual machines first disk is selected by default if the datastore has been added to the selected reservation. If the restored virtual machine has multiple disks, then all these disks are created in the selected datastore.

l Resource Pool to put the virtual machine in: The pool from the original virtual machine is selected by default. You can select a different pool if preferred.

l VM folder to put the virtual machine in: The folder from the original virtual machine is selected by default. You can select a different folder if preferred.

Note: Using vRealize Automation to restore client virtual machines that are inside a vAPP fails when you select that virtual machine folder name as the destination. Before restoring any vApp client virtual machines, ensure that you manually remove the virtual machine from the vApp.

l *Blueprint for new virtual machine: The blueprint you use to import the new virtual machine into vRealize Automation. Displays the published blueprints entitled to the original virtual machine owner.

l *Component in the blueprint: The component in the blueprint to use when importing the new virtual machine.

l Set Inherit custom properties from source vm? to Yes if you want to import the source virtual machine custom properties and key values to the restored virtual machine. Set Inherit custom properties from source vm? to No if you want to apply the blueprint custom properties and key values to the restored virtual machine. If you select No, Blueprint for new virtual machine will be enabled and you can then choose the required blueprint and component in the blueprint to associate to the virtual machine.

l Set Configure IP? to Yes if you want vRealize Automation to automatically assign a new IP address to the restored virtual machine. Selecting Yes will disable the Remove Nic and Reconnect NIC options. Set Configure IP? to No to enable the Remove Nic and Reconnect NIC options.

Note: If you set Configure IP? to Yes, ensure that you also configure the defaultVCACHostSysAdminPassword under Library/EMC/RestoreConfig, and that you increase the timeout for inventoryImportTimeoutInMinutes in case vRA initially fails to import the virtual machine to the vRA inventory.

l Set Remove Nic to Yes if you want to remove the NIC from the restored virtual machine. Set Remove Nic to No if you do not want to remove the NIC from the restored virtual machine. If set to No, then the Reconnect NIC option will be enabled.

8. Select the advanced options that you want to use to restore the virtual machine, and then click Next.

9. If a warning message appears indicating that vRealize Automation does not have the ability to do an automated import, accept the warning and click Submit.

Administration

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 55

10. To close the request confirmation message, click OK.

11. To view the progress of the restore, select the Requests or Deployments tab.

12. When the workflow completes, perform the following to verify the workflow:

a. Select the Infrastructue tab.

b. Select Managed Machines in the left pane. In this list, the name of the restored virtual machine appears. You can also verify options that you selected for restoring the virtual machine, such as the blueprint or the reservation.

The machine will display the Items tab after the vRealize Automation import process completes.

Restore a deleted virtual machine Deleted virtual machines that had data protection and backups on a PowerProtect Data Manager server retain these backups until the retention period expires. Backups are retained even when the virtual machine is deleted from the VMware infrastructure. As a tenant administrator, you can restore one of these backups as a new virtual machine.

Before you begin

l You must be logged in to vRealize Automation as a user with the administrator entitlement, as defined in the Install default setup for tenant workflow.

l The virtual machine that you plan to restore must have one or more existing image level backups. Restores of virtual machines that are backed up using an application-consistent policy are not available.

About this task

Note: This feature does not provide a filter by tenant. Therefore, when restoring a deleted virtual machine, as a tenant administrator you can see every deleted machine on the PowerProtect Data Manager server. If security concerns exist regarding a multi-tenant system, it is recommended that each tenant have its own unique PowerProtect Data Manager server for storing backups. Alternatively, you can add entitlement for this catalog item to only appropriate users.

Procedure

1. In vRealize Automation, select the Catalog tab.

2. In the left pane, click the data protection service.

3. In the right pane, click Request for the Restore deleted machine from backup catalog item.

The Restore deleted machine from backup page opens on the Select VM tab.

4. On the Select VM tab, select which virtual machine to restore. The Filter By Name? option is set to Yes by default. If you select No, the Name Filter option is no longer visible.

a. If you want to filter the results by virtual machine name, leave the FIlter By Name? option set to Yes, and type the filter criteria in the Name Filter field.

You can filter by partial or full virtual machine name, and/or by the date the machine was deleted.

b. To display the list of machines that match the filter criteria, click the Deleted Machine drop-down list.

Note: This list includes all machines that match the filter criteria, including machines that do not have backups.

Administration

56 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

c. Select the machine that you want to restore, and click Next to display the Select backup tab.

5. In the Select backup tab, select a backup from the drop-down list or search for backups by date range. You can also limit the number of backups that are listed.

a. If you want to filter the backups by date range, select Yes, and select the Start Date and time and the End Date and time.

b. Select the maximum number of backups that you want to view.

c. To display the backups that match the filter criteria, click the Backup drop-down list.

d. Select the backup that you want to restore.

Note: When you select a backup, the new name for the virtual machine is populated automatically. If you change the name, Dell EMC recommends that you follow the naming standard as outlined in the VMware knowledgebase article at https:// kb.vmware.com/s/article/2009820 and the Microsoft knowledgebase article at http:// support.microsoft.com/kb/909264.

6. In the Import Information tab, specify the new owner's vRealize Automation username, and select the business group, reservation, and blueprint that the new VM has when it is restored.

The username is contained in the Owner field by default.

a. In the Owner field, type the username of the owner. For example, Annie@machine.local.

The Business Group list is populated with the business groups that are common to you (as the tenant administrator) and to the owner that you specified. If the username of the new owner is invalid, or if there are no common business groups between you and the owner, the list is empty.

b. Select the Business Group for the new owner.

c. Select the Reservation that you want to use to determine what resources are available on the new virtual machine. Only the reservations that are available for the selected business group are contained in the Reservation list.

d. Set Configure IP? to Yes if you want vRealize Automation to automatically assign a new IP address to the restored virtual machine. Selecting Yes will disable the Remove Nic and Reconnect NIC options. Set Configure IP? to No to enable the Remove Nic and Reconnect NIC options.

Note: If you set Configure IP? to Yes, ensure that you also configure the defaultVCACHostSysAdminPassword under Library/EMC/RestoreConfig, and that you increase the timeout for inventoryImportTimeoutInMinutes in case vRA initially fails to import the virtual machine to the vRA inventory.

e. Set Remove Nic to Yes if you want to remove the NIC from the restored virtual machine. Set Remove Nic to No if you do not want to remove the NIC from the restored virtual machine. If set to No, then the Reconnect NIC option will be enabled.

f. Blueprint for new virtual machine is the blueprint you use to import the new virtual machine into vRealize Automation, and displays the published blueprints entitled to the original virtual machine owner.

g. Component in the blueprint is the component in the blueprint to use when importing the new virtual machine.

Administration

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 57

h. Click Next, or select the Restore Location tab.

7. In the Restore Information tab, you specify details about the physical hardware for the new virtual machine based on the reservation.

a. In the New Virtual Machine Name field, type a name for the new machine, or accept the default name, which is the original name plus a current timestamp.

During the restore, the system prevents the new virtual machine name from overwriting an existing virtual machine.

b. Select a Host.

The hosts that are contained in the list are the ESX hosts that are available in the selected reservation.

c. Select a Datastore.

The datastores that are contained in the list have been enabled in the selected reservation and that are visible to the selected ESX host.

d. Select a Resource Pool.

The resource pools that are contained in the list have been filtered based on the selected datastore.

e. Select a Virtual Machine Folder.

The folders that are contained in the list have been filtered based on the selected datastore.

f. If a warning appears that vRealize Automation does not have the ability to do an automated import, accept the warning and click Submit.

The size of the deleted virtual machine that you are restoring directly affects the length of time that is required to complete the restore. The larger the machine, the more time it takes.

8. When the workflow completes, perform the following to verify the workflow:

a. Select the Infrastructue tab.

b. Select Managed Machines in the left pane. In this list, the name of the restored virtual machine appears. You can also verify options that you selected for restoring the virtual machine, such as the blueprint or the reservation.

The machine will display the Items tab after the vRealize Automation import process completes.

Administration

58 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

CHAPTER 4

Business Group User Operations

This chapter includes the following topics:

l Provision a protected virtual machine................................................................................... 60 l Data protection actions..........................................................................................................61 l Restore actions..................................................................................................................... 62 l Expiring or destroying a virtual machine................................................................................ 64

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 59

Provision a protected virtual machine You can provision a protected virtual machine by requesting a blueprint that has a data protection policy assigned to it. Depending on how the tenant administrator configured the blueprint, a policy that is used to protect the machine may or may not be selectable. If the policy is not selectable during provisioning, a policy that is pre-selected by the administrator is applied to the virtual machine by default.

Procedure

1. In vRealize Automation, select the Catalog tab.

2. In the list of service catalogs, locate a blueprint that contains data protection, and click the blueprint's Request button.

The New Request page for the blueprint displays.

If the blueprint contains selectable policies, you can select one from the EMC data protection policy drop-down list as shown in the following figure.

Figure 22 Select policy for the blueprint

If a policy is not selectable on this page, that means that a policy has already been configured for the blueprint and is applied by default to the virtual machine that you are provisioning.

3. Optionally, change any of the remaining values on the New Request page as needed.

4. Click Submit.

5. To close the request confirmation message, click OK.

6. If you want to monitor the status of the provisioning request, select the Requests or Deployments tab.

To refresh the page, click the Refresh button at the bottom of the page.

Results

After the virtual machine has been provisioned successfully, it will be listed in the Machines list on the Items tab. The remaining sections in this chapter describe the data protection and restore actions that you can perform on the virtual machine.

Business Group User Operations

60 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Data protection actions This section describes the EMC vRealize Data Protection Extension actions that the business group user can perform. These tasks include:

l Adding data protection to a virtual machine

l Running data protection on a virtual machine

l Viewing the protection status of a virtual machine

l Removing data protection from a virtual machine

Adding data protection to a virtual machine The steps in the following procedure describe how to add data protection to an existing, unprotected virtual machine by adding one, or more protection policies.

Before you begin

At least one protection policy must support the vCenter that manages the virtual machine to be provisioned. Procedure

1. In the vRealize Automation user interface, select the Items tab.

2. In the Machines list, click the row of the virtual machine to which you want to add data protection.

The row is highlighted.

3. Click Actions, and select Add data protection from the menu.

The Add data protection page displays.

4. Select a policy from the list of policies, and click Submit.

5. To close the request confirmation message, click OK.

6. If you want to monitor the status of the request, select the Requests or Deployments tab.

To refresh the information, click the Refresh button at the bottom of the page.

Running data protection on a virtual machine The steps in the following procedure describe how to perform an immediate backup of a virtual machine that has been provisioned.

Before you begin

The virtual machine must have a policy assigned to it. At least one protection policy must support the vCenter that manages the virtual machine to be provisioned. Procedure

1. In vRealize Automation, select the Items tab.

2. In the Machines list, click the row of the virtual machine that you want to back up.

The row is highlighted.

3. Click Actions, and select Run data protection from the menu.

The Run data protection page displays.

4. Select a policy from the list, and click Submit.

5. To close the request configuration message, click OK.

Business Group User Operations

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 61

6. If you want to monitor the status of the request, select the Requests or Deployments tab.

To refresh the status, click the Refresh button.

Viewing the protection status of a virtual machine The steps in the following procedure describe how to view the protection status of a virtual machine.

Procedure

1. In vRealize Automation, select the Items tab.

2. In the Machines list, click the row of the virtual machine for which you want to view protection status.

The row is highlighted.

3. Click Actions, and select View protection status in the menu.

The View protection status page displays with the machine's protection status.

Removing data protection from a virtual machine The steps in the following procedure describe how to remove data protection from a virtual machine that has already been provisioned.

Procedure

1. In vRealize Automation, select the Items tab.

2. In the Machines list, click the row of the virtual machine from which you want to remove data protection.

The row is highlighted.

3. Click Actions, and select Remove data protection from the menu.

The Remove data protection page displays.

4. Click the checkbox beside one or more of the policies that you want to remove from the virtual machine.

5. Click Submit.

6. To close the request confirmation message, click OK.

Restore actions This section describes the restore operations that the business group user can perform. These actions include restoring a virtual machine to its original location or to a new location, and restoring individual files.

Restore a virtual machine to its original location The steps in the following procedure describe how to restore a backup of a virtual machine to its original location.

Before you begin

The virtual machine that you plan to restore must have an existing image-level backup to PowerProtect Data Manager. Virtual machines that are backed up using an application-consistent policy are not available, as described in the section Restore a virtual machine to a new location on page 63.

Business Group User Operations

62 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Procedure

1. In vRealize Automation, select the Items tab.

2. Click the row of the machine whose backup you want to restore.

The row is highlighted.

3. From the Actions menu, select Restore data.

The Restore data page displays.

4. In the Restore data page, you can search for backups by date range, and you can limit the number of backups that are listed.

a. If you want to filter the backups by date range, select Yes, and select the Start Date and time and the End Date and time.

b. Select the maximum number of backups that you want to view.

c. To display the backups that match the filter criteria, click the Backup drop-down list.

d. Select the backup that you want to restore.

5. Select Yes for Synchronize virtual machine power status? if you want to synchronize the power status of the virtual machine by running data collection on the back-end.

6. Select Yes for Restore configuration? if you want to restore the virtual machine configuration data along with the backup restore.

7. Select Yes for Delete existing configuration? if you want to remove the existing virtual machine configuration data.

Note: Restore configuration? and Delete existing configuration? are applicable only to NetWorker.

8. Select Yes or No as required for the power off and power on options.

9. Click Submit.

10. To close the request confirmation message, click OK.

11. Select the Requests or Deployments tab, and monitor the restore progress until it completes successfully.

Restore a virtual machine to a new location The steps in the following procedure describe how to restore a backup of a virtual machine to a location that is different from the location of the original machine. When you restore a backup to a new location, a new virtual machine is created on the vCenter and then imported back into vRealize Automation. When the restore completes, you can view the new virtual machine in the Items tab in vRealize Automation.

Before you begin

The virtual machine that you plan to restore must have one or more existing image level backups to PowerProtect Data Manager. Virtual machines that are backed up using an application-consistent policy are not available.

Procedure

1. In vRealize Automation, select the Items tab.

2. Click the row of the machine whose backup you want to restore.

The row is highlighted.

3. From the Actions menu, select Restore to new.

The Restore to New page displays.

Business Group User Operations

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 63

4. In the Restore to New page, you can search for backups by date range, and you can limit the number of backups that are listed.

a. If you want to filter the backups by date range, select Yes, and select the Start Date and time and the End Date and time.

b. Select the maximum number of backups that you want to view.

c. To display the backups that match the filter criteria, click the Backup drop-down list.

d. Select the backup that you want to restore.

Note: When you select a backup, the new name for the virtual machine is populated automatically. If you change the name, it is recommended that you follow the naming standard as outlined in the VMware knowledgebase article at https:// kb.vmware.com/s/article/2009820 and the Microsoft knowledgebase article at http://support.microsoft.com/kb/909264.

5. In the Restoring Custom Properties page:

l Set Inherit custom properties from source vm? to Yes if you want to import the source virtual machine custom properties and key values to the restored virtual machine.

l Set Inherit custom properties from source vm? to No if you want to apply the blueprint custom properties and key values to the restored virtual machine. If you select No, Blueprint for new virtual machine will be enabled and you can then choose the required blueprint and component in the blueprint to associate to the virtual machine.

l Set Configure IP? to Yes if you want vRealize Automation to automatically assign a new IP address to the restored virtual machine. Selecting Yes will disable the Remove Nic and Reconnect NIC options. Set Configure IP? to No to enable the Remove Nic and Reconnect NIC options.

Note: If you set Configure IP? to Yes, ensure that you also configure the defaultVCACHostSysAdminPassword under Library/EMC/RestoreConfig, and that you increase the timeout for inventoryImportTimeoutInMinutes in case vRA initially fails to import the virtual machine to the vRA inventory.

l Set Reconnect NIC to Yes if you want the virtual machine to connect to the NICs after the restore, or No if you want the virtual machine to stay disconnected from NICs after the restore.

If a warning message appears indicating that vRealize Automation does not have the ability to do an automated import, accept the warning and click Submit.

6. To close the request confirmation message, click OK.

7. To view the progress of the restore, select the Requests or Deployments tab.

8. When the restore and import complete successfully, the new virtual machine appears in the Items tab.

Expiring or destroying a virtual machine The steps in this procedure describe how to expire or destroy a virtual machine. To perform these standard vRA machine actions, you must have the appropriate entitlements. Otherwise, these actions do not display in the Items tab.

Before you begin

The destroy operation occurs in a strict sequence so that orderly removal of virtual machines from data protection systems occurs before the virtual machine is actually destroyed. For example, a virtual machine may be protected by one or multiple data protection (Avamar, NetWorker, PowerProtect Data Manager) endpoints and/or multiple policies within the same data protection

Business Group User Operations

64 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

endpoint. Removal of a virtual machine from vSphere without first removing it from related data protection policies can cause errors in the data protection endpoint. Therefore, in order to keep systems consistent regarding virtual machine status, the following sequence occurs:

1. Removal of the virtual machine from all data protection endpoint policies it is associated with.

2. After the completion of step one, the virtual machine is destroyed in vSphere.

3. After the completion of step two, vRealize Automation removes the virtual machine from its inventory and it is no longer listed in the vRealize Automation Items > Machines tab for that tenant user.

Procedure

1. In vRealize Automation, select the Items tab.

2. In the Machines list, click the row of the virtual machine that you want to expire or destroy.

The row is highlighted.

3. Click Actions, and select either Expire or Destroy from the menu.

A confirmation message displays.

4. Select the Deployments tab to view a tree structure of the machine(s) in each executed blueprint. You can select a deployment and click the Destroy action to delete all the machines in the deployment, or you can select individual machine(s) of the deployment and click the Destroy action.

5. Click Submit.

6. To close the request confirmation dialog box, click OK.

Results

Note: Data protection is not removed when the virtual machine is expired. It is removed when the virtual machine is destroyed. The virtual machine can expire and be archived before it is destroyed, but the vRealize Data Protection Extension retires the client and removes the policy only when the machine is destroyed.

Note: The Destroy operation is a vRealize Automation action that a tenant administrator must entitle to the user.

Business Group User Operations

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 65

Business Group User Operations

66 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

CHAPTER 5

Logging and Supportability

This chapter includes the following topics:

l Monitoring status.................................................................................................................. 68 l Event and error message codes.............................................................................................69 l PowerProtect Jobs window for activity monitoring and log files........................................... 69 l Single-click log capturing and packaging...............................................................................69 l Log locations......................................................................................................................... 70

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 67

Monitoring status You can monitor the status of the requests and view request details from the Requests or Deployments tab in vRealize Automation Center.

The following figure shows status details for a successful request. Figure 23 Successful request in vRA

The following figure shows status details for a request failure. Figure 24 Failed request in vRA

Check the status details shown in the text area that is highlighted in the figure above to determine the meaning of the error and use the information for troubleshooting.

Logging and Supportability

68 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Event and error message codes The following table lists the events and error codes that exist for the EMC vRealize Data Protection Extension.

Note: in the following error codes, {provider} indicates the data protection system.

Table 5 Event and error codes

Error code Description

EDP.EDP4VCAC. {provider}.BU-000005

EDP: General error from the EMC vRealize Data Protection Extension. Please check data protection for details.

EDP.EDP4VCAC. {provider}.BU-000010

EDP: Backup cancelled and failed to backup client.

EDP.EDP4VCAC. {provider}.BU-000030

EDP: Backup failed with backup operation error.

EDP.EDP4VCAC. {provider}.BU-000040

EDP: One or more disks protected by backup policy may have been migrated to new datastores. Please edit the backup job and verify the correct disks are still protected.

EDP.EDP4VCAC. {provider}.BU-000050

EDP: Backup failed because policy was disabled.

EDP.EDP4VCAC. {provider}.RST-000200

EDP: Restore cancelled, check data protection provider for underlying reason.

EDP.EDP4VCAC. {provider}.RST-000210

EDP: Restore failed, check data protection provider for underlying reason.

EDP.EDP4VCAC. {provider}.RST-000220

EDP: Restore failed because client is running.

EDP.EDP4VCAC.{provider}. RST-000230

EDP: Restore failed because disk restore step failed. Please verify disks in backup and try again.

PowerProtect Jobs window for activity monitoring and log files

In addition to monitoring the status through the vRealize Automation Requests details, you can log in to the PowerProtect UI to view status details from the Jobs window. You can also view audit log information from the Jobs window.

Logs for PowerProtect are located in /var/log/brs.

Single-click log capturing and packaging Log bundling occurs in two areas of the product: vRealize Automation and the data protection system. The vRealize Data Protection Extension logs are included in the bundling facility of vRealize Automation.

Logging and Supportability

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 69

vRealize Automation log bundling vRealize Automation has a log bundle facility separate from the data protection system's log bundling.

About this task

You can export vRealize Orchestrator log and configuration settings using the Export logs and application settings vRealize Orchestrator workflow, which is located in /Library/ Troubleshooting. Please reference vRealize Automation documentation for log bundling specifics.

The following procedure describes how to collect the log bundle manually when using a vRealize Automation appliance.

Procedure

1. Log in to the vRealize Automation appliance management site.

2. Click the vRA Settings tab on the menu bar.

3. Click the Cluster tab.

4. Click Create Support Bundle.

5. When log collection completes, click the bundle link to download the file.

vRealize Orchestrator log bundling You can collect the vRealize Orchestrator log files from vRealize Orchestrator Configuration.

Procedure

1. Log in to vRealize Orchestrator Control Center at:

http://<orchestrator_server_ip_address>:8283/vco-controlcenter 2. In the Export Logs section, click EXPORT LOGS.

The system generates a .zip file bundle that you can download and save locally.

Log locations The following table contains log descriptions and locations for the vRealize Data Protection Extension and the data protection system.

The most up-to-date log information is provided at the following links:

l Default log locations

l Log locations for VMware vRealize Automation 7.x

Table 6 Default log locations

vRealize Automation component log description

Default log location

IaaS installation configuration logs C:\Program Files (x86)\VMware\vCAC\Server \ConfigTool\Log

IaaS Manager Server logs C:\Program Files (x86)\VMware\vCAC\Server \Logs

Logging and Supportability

70 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Table 6 Default log locations (continued)

vRealize Automation component log description

Default log location

IaaS Model Manager Web (Repository) logs

C:\Program Files (x86)\VMware\vCAC\Server \Model Manager Web\Logs

IaaS Distributed Execution Manager (DEM) Orchestrator and Worker logs

C:\Program Files (x86)\VMware\vCAC \Distributed Execution Manager\ atdhl- ms1-70.sqa.local DEO\Logs

IaaS Proxy Agent logs C:\Program Files (x86)\VMware\vCAC\Agents \Agent_Name\Logs

vRealize Automation Identity Appliance logs

/var/log/vmware/sso/

vRealize Automation Appliance logs /var/log/vmware/vcac/

vRealize Automation Appliance Apache error log

/var/log/apache2/error_log

vRealize Automation Appliance Upgrade logs

/opt/vmware/var/log/vami/

vRealize Orchestrator Appliance In the vRealize Orchestrator Appliance (and the vRealize Orchestrator in the vRealize Automation Appliance), both the vRealize Orchestrator server and configuration server use tomcat logging, so the logs are in:

l /var/lib/vco/app-server/logs, which is sym-linked to /var/log/vmware/vco/app- server/. The edp_4_vcac.log in this directory

contains the log messages from the vRealize Data Protection Extension.

l /var/lib/vco/configuration/logs, which is sym-linked to {{/var/log/ vmware/vco/configuration/}}. Mostly you will look in catalina.out.

l vRealize Automation is similar: /var/lib/vcac/logs, which is sym-link'ed to /var/log/vmware/vcac.

PowerProtect log description PowerProtect log location

PowerProtect logs /var/log/brs

PowerProtect documentation https://support.emc.com/products/ 40720_Enterprise-Copy-Data-Management/ Documentation/

Logging and Supportability

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 71

Logging and Supportability

72 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

CHAPTER 6

Troubleshooting

This chapter includes the following topics:

l General Troubleshooting........................................................................................................74 l Items to investigate when data protection is not added.........................................................74 l Troubleshooting the EMC vRealize Data Protection Extension..............................................74 l Check the vRealize Data Protection Extension configuration................................................ 76

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 73

General Troubleshooting Infrastructure administrators can obtain detailed failure status in the following locations in vRealize Automation:

l Infrastructure > Recent Events

l Infrastructure > Monitoring > Logs

Note: Non-Infrastructure administrators can use the View protection status action to see if the assignment occurred, but cannot see the logs.

Items to investigate when data protection is not added Investigate the following items if a virtual machine is successfully provisioned but data protection is not added.

l Is the data protection system up and running?

l Does the policy exist in PowerProtect Data Manager?

l Is the environment configured correctly? In the vRealize Orchestrator client, select the Workflows tab, browse to /Library/EMC/Data Protection/vRA, and run the Check EMC data protection configuration workflow. To see if there are any errors or warnings, check the logs.

Troubleshooting the EMC vRealize Data Protection Extension The following are known issues that you may encounter when working with vRealize Automation components.

A Day 2 operation such as Restore Data times out when submitting the operation from the vRA web portal

When you run the Restore Data workflow for a PowerProtect Data Manager-protected virtual machine from vRealize Automation, the operation might fail with an error similar to the following on the vRA web portal.

The connection to the vCenter Orchestrator server timed out.

If this error occurs, log in to each vRealize Automation server node in the cluster and change the following default timeout values in the file /usr/lib/vcac/server/webapps/o11n- gateway-service/WEB-INF/classes/META-INF/spring/root/o11n-gateway- service-context.xml to a higher value:

l

l

l

l

Troubleshooting

74 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Note: Set your timeout values according to the scale of the total number of backup clients present in Avamar, NetWorker, or PowerProtect Data Manager.

For up to 300 virtual machines, it is recommended to set the connectionTimeout to 120000 milliseconds. For 300 to 1000 virtual machines, it is recommended to set the connectionTimeout to 240000 milliseconds.

Note: After modifying these variables, you must restart the vcac-server service on each vRA appliance in the cluster. For example, from the command line, type service vcac-server restart.

The following ecdm response/cache timeout parameters are specific to PowerProtect Data Manager. These parameters are registered by running the vRO Update a tenant data protection system workflow and typing the values in the text box on the System Information tab:

l edp.timeoutThe amount of time the DPE waits for the EDP systems to respond.

l ecdm.response.timeoutThe number of seconds or milliseconds that DPE waits for PowerProtect to respond.

l ecdm.cache.timeoutThe number of seconds (s) before the DPE PowerProtect cache expires.

For example, the default values are edp.timeout=120s;ecdm.response.timeout=120s Note: vRA/vRO timeout values must be greater than the value for edp.timeout, and the edp.timeout value must be greater than the Avamar, NetWorker, or PowerProtect Data Manager timeout value.

Recently changed policies not displaying when running Setup a Data Protection Property Group or Add Data Protection workflows

A recently added, modified or deleted policy might not immediately display in the vRA policy lists when running the Setup a Data Protection Property Group or Add Data Protection workflows.

You can either wait for a few minutes or perform the following steps if you require these policies to display immediately.

Log into the vRealize Orchestrator client and refresh using the following steps:

1. Select the Inventory tab.

2. Select and expand the EMC Data Protection top node.

3. Right-click the protection system node and select Reload, or click Refresh in the top right corner to refresh all vRealize Orchestrator objects, including all of the data protection systems.

Alternatively, you can log into the vRealize Orchestrator client and flush the cache using the following steps:

1. Select the Workflows tab.

2. Navigate to EMC > Data Protection > vRO > Utilities.

3. Run Flush cached data or Flush cached data on system.

4. Ensure that the policies have been created under the correct domain.

Null error when provisioning from blueprint with deleted policy When it is discovered that a virtual machine is not protected by the data protection system as expected, there may have been a change to the underlying data protection system itself.

The vRealize Automation user provisions a virtual machine, which uses a build profile configured with the data protection policy.

The result of the provisioning request: Success.

Troubleshooting

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 75

The cause of the error: A change to the underlying data protection system has removed the policy attached to the blueprint. Protection cannot be added to the virtual machine and fails.

The protection failure is NOT a hard failure for the provisioning request. At the version level of the system, there is no way to show a warning through the UI of the vRealize Automation system.

Therefore, a message is logged in the catalina.out log file of the vRealize Orchestrator system. The vRealize Data Protection Extension logs the following message:

[McsdkProtectionProvider] EDP: Backup Policy could not be found and may have been deleted.

No available policy found from virtual machine properties when there is no EDP system

When it is discovered that a virtual machine is not protected by the data protection system as expected, the underlying data protection system may not be available.

The vRealize Automation user provisions a virtual machine, which uses a build profile configured with the data protection policy.

The result of the provisioning request: Success.

The cause of the error: The underlying data protection system has either been removed or is not functional. Protection cannot be added to the virtual machine and fails.

The protection failure is NOT a hard failure for the provisioning request. At the version level of the system, there is no way to show a warning through the UI of the vRealize Automation system.

Therefore, a message is logged in the catalina.out log file of the vRealize Orchestrator system. The vRealize Data Protection Extension logs the following message:

EDP Provider is null.

No available policy found from VM properties of , skipping protection policy assignment.

vRealize Automation event subscriptions The vRealize Data Protection Extension uses a new method introduced in vRealize Automation 7 called event subscriptions.

In vRealize Automation, Administration > Events > Event Logs lists all events in the vRealize Automation system, including machine workflows.

For Provisioning, events with descriptions of "Workflow 'Machine provisioned subscription' has started" and "Workflow 'Machine provisioned subscription' has completed" appear.

For Destroy, events with descriptions of "Workflow 'Machine unprovisioned subscription' has started" and "Workflow 'Machine unprovisioned subscription' has completed" appear.

Check the vRealize Data Protection Extension configuration The vRealize Data Protection Extension provides a utility workflow that can diagnose some of the potential configuration issues between itself and vRealize Automation, vRealize Orchestrator, vCenter, and PowerProtect Data Manager.

Procedure

1. Log in to the vRealize Orchestrator client.

2. Select the Workflows tab, and browse to the following location:

Library/EMC/Data Protection/vRA

Troubleshooting

76 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

3. Select the Check EMC data protection configuration workflow, and click the green arrow ( ) in the upper-left corner of the right-hand pane to start the workflow.

4. While the workflow is running, select the Logs tab to monitor its progress.

Results

If errors are discovered, the workflow run fails and errors are logged. If warnings are discovered, the workflow run passes and warning messages are logged. All errors and warnings display in the Logs tab and are written to the /var/log/vco/app-server/server.log file on the server running the vRealize Orchestrator instance (typically the vRealize Automation server machine).

Configuration checks performed by the EMC data protection configuration workflow

The Check EMC data protection configuration workflow runs the following configuration checks:

l Ensures that the required plug-ins and packages are installed. If the required plug-ins are not installed, the workflow fails immediately with a validation error. To see more information regarding the error:

1. Select Tools > User Preferences.

2. Select Workflows.

3. Clear the selection for Validate a workflow before running it checkbox.

4. Click Save & Close.

5. Re-run the Check EMC data protection configuration workflow, which is located in / Library/EMC/Data Protection/vRA.

l Ensures that the vRA Infrastructure Administration and vCloud Automation Center connections are in the vRealize Orchestrator inventory. You can typically address these issues by running the following workflows in the specified order:

n The Add an IaaS host workflow, which is located in Library/vCloud Automation Center/Infrastructure Administration/Configuration/.

n The Add a vRA host workflow, which is located in Library/vCloud Automation Center/Configuration.

l Ensures that the vCenter Server connection(s) are in the vRealize Orchestrator inventory, and that they match up with the vSphere endpoint(s) configured in the vRealize Automation Infrastructure configuration. To add missing vCenter Server connections to vRealize Orchestrator, run Add a vCenter Server instance workflow, which is located in Library/ vCenter/Configuration.

l Ensures the machine lifecycle event subscriptions are configured in each tenant.

l Ensures that at least one vRealize Automation host per tenant has sufficient permissions. The user connected to the vRealize Automation host requires the Infrastructure Architect, Tenant Administrator, and XaaS Architect roles.

l Ensures that any configured EMC data protection systems are valid and connected, and have protection policies.

l If there are clients in the EMC data protection systems, ensures that the VirtualCenter.FQDN field in the vSphere Client under Administration > vCenter Server Settings > Advanced Properties matches the vCenter server configured in the EDP Protection System.

You can run the Check EMC data protection configuration workflow multiple times as you correct issues with the configuration.

Troubleshooting

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 77

Error and warning messages The following table lists error and warning messages that can occur when you run the Check EMC data protection configuration workflow, which is located in /Library/EMC/Data Protection/vRA. It also provides a number of possible solutions that you can use to resolve the error and warning conditions.

Table 7 Error and warning messages

Messages Type Possible solution(s)

Missing vCAC Infrastructure plugin.

Error l In vRealize Orchestrator client, select Help > Installed Plug-ins... and verify the vCAC plug-in is installed.

l Install the VMware vCenter Orchestrator Plug-In for vCloud Automation Center from VMware.com.

Missing vCAC Cafe plugin. Error l In vRealize Orchestrator client, select Help > Installed Plug-ins... and verify the vCACCAFE plug-in is installed.

l Install the VMware vCenter Orchestrator Plug-In for vCloud Automation Center from vmware.com.

Missing EDP plugin. Error l In vRealize Orchestrator client, select Help > Installed Plug-ins... and verify the EDP plug-in is installed.

l Install the EMC vRealize Data Protection Extension from emc.com.

Missing default IaaS host in vCO inventory.

Error To add the host to vRealize Orchestrator, run the Library/vCloud Automation Center/ Infrastructure Administration/ Configuration/Add an IaaS host workflow.

Found IaaS hosts in vCO inventory, with not connected to . Only the ' ' host is used, which might not be the expected one.

Warning To remove the other hosts from vRealize Orchestrator, run the Library/vCloud Automation Center/Infrastructure Administration/Configuration/Remove an IaaS host workflow.

Failed to get provisioning groups from IaaS host , other operations might not work.

Error l Verify that the IaaS server is running and accessible. Restart, if needed.

l Verify that the IaaS server connection is in the Inventory tab of the vRealize Orchestrator client, under vCAC Infrastructure Administration.

l Check the log files on the IaaS server.

Unexpected exception checking vcac hosts:

Error l Verify that the IaaS server is running and accessible. Restart, if needed.

l Check the log files on the vRealize Orchestrator server for more information related to the error.

Troubleshooting

78 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Table 7 Error and warning messages (continued)

Messages Type Possible solution(s)

l Check the log files on the IaaS server.

Missing default vCAC cafe host in vCO inventory.

Error To add a vsphere.local tenant host to vRealize Orchestrator, run the Library/vCloud Automation Center/Configuration/Add a vCAC host workflow.

Found 'vsphere.local' tenant vCAC cafe hosts in vCO inventory, with not connected to .

Error To remove the other hosts from vRealize Orchestrator, run the Library/vCloud Automation Center/Configuration/Remove a vCAC host workflow.

Found 'vsphere.local' tenant vCAC cafe hosts in vCO inventory, but they point to same vcac url which should work fine. This can occur when vCAC 6.1+ creates the 'Default' vCAC cafe host connections.

Warning To remove the other hosts from vRealize Orchestrator, optionally run the Library/vCloud Automation Center/Configuration/Remove a vCAC host workflow.

No vCenter connections found in vCO inventory.

Error To add the vCenter server connection(s) to vRealize Orchestrator, run the Library/vCenter/ Configuration/Add a vCenter Server instance workflow.

Malformed endpoint URL ' ' : must be of type: https:// hostname/sdk or https:// IP_Address/sdk.

Warning Verify and fix the vSphere endpoint URL in the vRealize Automation Infrastructure tab.

Failed to find vCenter connection in vCO matching ' ' vSphere endpoint in IasS host ' '.

Warning l To add the vCenter server connection to vRealize Orchestrator, run the Library/vCenter/ Configuration/Add a vCenter Server instance workflow.

l To update the vCenter server connection in vRealize Orchestrator to match what is configured in the vRealize Automation Infrastructure tab, run the Library/vCenter/ Configuration/Update a vCenter Server instance workflow.

vCenter endpoint in IaaS host ' ' has invalid uri ' '.

Warning Verify and fix the vSphere endpoint URL in the vRealize Automation Infrastructure tab.

Failed to find vSphere endpoints in IaaS host ' '.

Warning Create the vSphere endpoint(s) in the vRealize Automation Infrastructure tab.

Troubleshooting

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 79

Table 7 Error and warning messages (continued)

Messages Type Possible solution(s)

Unexpected exception checking IaaS vSphere connection endpoints:

Error l Verify the IaaS server is running and accessible. Restart, if needed.

l Check the log files on the vRealize Orchestrator server for more information related to the error.

l Check the log files on the IaaS server.

Failed to find the vCenter hostname and IP information:

Warning l Verify the vCenter connection information in the vRealize Orchestrator client Inventory tab, under vCenter Server.

l To correct the vCenter Server information for the connection in vRealize Orchestrator, run the Library/vCenter/Configuration/Update a vCenter Server instance workflow.

No EdpSystems have been configured for data protection.

Warning l Use the Add a tenant data protection system catalog item in vRealize Automation, if you already ran the install workflow for the tenant.

l To configure a vRealize Automation tenant, including the data protection system, run the Library/EMC/Data Protection/vRA/ Installation/Install default setup for tenant workflow.

l To configure a data protection system instance for a vRealize Automation tenant, without doing the other tenant setup steps, run the Library/EMC/Data Protection/vRA/ Installation/Utilities/Create or update a tenant data protection system workflow.

l To manually setup a data protection system, run the Library/EMC/Data Protection/vRO/ Configuration/Add a data protection system workflow.

Failed to find a matching vCenter for the vCenter configured in the EdpServer: . EdpServer FQDN= . vCenter FQDN(s)= . Please check the VirtualCenter.FQDN setting in the vCenter Advanced Properties

Warning l To add the vCenter server connection to vRealize Orchestrator, run the Library/vCenter/ Configuration/Add a vCenter Server instance workflow.

l To update the vCenter server connection in vRealize Orchestrator to match what is configured in the PowerProtect Data Manager server, run the Library/vCenter/ Configuration/Update a vCenter Server instance workflow.

l Verify or update the VirtualCenter.FQDN setting in the Advanced Properties of the vCenter server settings in the vSphere web client to

Troubleshooting

80 vRealize Data Protection Extension for PowerProtect Installation and Administration Guide

Table 7 Error and warning messages (continued)

Messages Type Possible solution(s)

match what is configured in the PowerProtect Data Manager server.

Unexpected exception checking EdpSystems:

Error Check the logs files on the vRealize Orchestrator server for more information related to the error.

Unable to find vRealize Automation machine provisioning event subscription for ' ' tenant EMC data protection system(s), or Unable to find vRealize Automation machine unprovisioning event subscription for ' ' tenant EMC data protection system(s).

Warning Run the installation for the tenant, if not done already, and then update the default setup for the tenant.

Unexpected exception checking vRealize Automation event subscriptions:

Error Check the log files on the vRealize Orchestrator server for more information.

None of the vRealize Automation hosts for tenant ' ' appear to have the Infrastructure Architect, Tenant Administrator, and XaaS Architect roles. The EMC data protection default tenant setup workflows requires a vRealize Automation host with a user configured with those roles.

Error Verify that the Roles of the user(s) of the vRealize Automation hosts.

Task 'customize' error: Windows customization resources were not found on the server.

Error This error is related to configuring the IP address for the virtual machine during restore workflows. Refer to the knowledgebase article at https:// kb.vmware.com/s/article/1005593 for the workaround.

Task 'customize' error: A specified parameter was not correct: spec.identity.userData.com puterName

Error This error is related to configuring the IP address for the virtual machine during restore workflows. Refer to the knowledgebase article at https:// kb.vmware.com/s/article/2009820 for the workaround.

Please provide vRA system admin password in VRO

Error This error is related to configuring the IP address for the virtual machine during restore workflows. Provide the vRA system admin password in the configuration

Troubleshooting

vRealize Data Protection Extension for PowerProtect Installation and Administration Guide 81

Table 7 Error and warning messages (continued)

Messages Type Possible solution(s)

(located at Library/EMC/RestoreConfig/ defaultVCACHostSysAdminPassword) to

configure the IP.

Operation not supported on this object

Error This error can occur during the Advanced restore to new workflow when a vApp client virtual machine fails, particularly when specifying the VM folder. Before restoring any vApp client virtual machine, ensure that you manually remove the virtual machine from vApp.

Restoring the backup to a new virtual machine was successful; however, an error was encountered when attempting to verify that the import of the new virtual machine into vRealize Automation was successful.

Error This error can occur during the Import restored machine workflow. If the new virtual machine does not show up in the Items tab after a few minutes, a fabric administrator will be required to import the virtual machine manually.

Troubleshooting

82 vRealize Data Protection Extension