HYCU User Guide · 2019-06-27 · 4 Contents 1AboutHYCU 10 HYCUkeyfeaturesandbenefits 11 Dataprotectionenvironmentoverview 12 HYCUdataprotection 13 2DeployingtheHYCUvirtualappliance

HYCU Data Protectionfor Nutanix

Version: 4.0.0

Product release date: June 2019

Document release date: June 2019

USER GUIDE

2

Legal noticesCopyright notice© 2017 HYCU. All rights reserved.

This document contains proprietary information, which is protected by copyright. No partof this document may be photocopied, reproduced, distributed, transmitted, stored in aretrieval system, modified or translated to another language in any form by any means,without the prior written consent of HYCU.

TrademarksHYCU logos, names, trademarks and/or service marks and combinations thereof are theproperty of HYCU or its affiliates. Other product names are the property of their respectivetrademark or service mark holders and are hereby acknowledged.

Acropolis and Nutanix are trademarks of Nutanix, Inc. in the United States and/or otherjurisdictions.

Azure®, Internet Explorer®, Microsoft®, Microsoft Edge™, and Windows® are eitherregistered trademarks or trademarks of Microsoft Corporation in the United States and/orother countries.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

Red Hat Enterprise Linux is a registered trademark of Red Hat, Inc. or its subsidiaries in theUnited States and other countries.

DisclaimerThe details and descriptions contained in this document are believed to have been accurateand up to date at the time the document was written. The information contained in thisdocument is subject to change without notice.

HYCU provides this material "as is" and makes no warranty of any kind, expressed orimplied, including, but not limited to, the implied warranties of merchantability and fitnessfor a particular purpose. HYCU shall not be liable for errors and omissions containedherein. In no event shall HYCU be liable for any direct, indirect, consequential, punitive,special or incidental damages, including, without limitation, damages for loss and profits,loss of anticipated savings, business interruption, or loss of information arising out of theuse or inability to use this document, or any action taken based on the informationcontained herein, even if it has been advised of the possibility of such damages, whetherbased on warranty, contract, or any other legal theory.

The only warranties for HYCU products and services are set forth in the express warrantystatements accompanying such products and services. Nothing herein should beconstrued as constituting an additional warranty.

3

NoticeThis document is provided in connection with HYCU products. HYCU may have copyright,patents, patent applications, trademark, or other intellectual property rights covering thesubject matter of this document.

Except as expressly provided in any written license agreement from HYCU, the furnishing ofthis document does not give you any license to these patents, trademarks, copyrights, orother intellectual property on HYCU products. Use of underlying HYCU product(s) isgoverned by their respective Software License and Support Terms.

Important: Please read Software License and Support Terms before using theaccompanying software product(s).

HYCUwww.hycu.com

http://www.hycu.com/

4

Contents1 About HYCU 10

HYCU key features and benefits 11

Data protection environment overview 12

HYCU data protection 13

2 Deploying the HYCU virtual appliance 14

Sizing your backup infrastructure for HYCU 15

Firewall settings 16

Deploying HYCU to a Nutanix AHV cluster 17

Deployment tasks 17

Deploying HYCU to a Nutanix ESXi cluster or a vSphere environment 20

Logging on to HYCU 22

3 Establishing a data protection environment 24

Adding sources 25

Adding a Nutanix cluster 25

Adding a vCenter Server 27

Adding a Nutanix Files server 28

Adding a physical machine 32

Setting up targets 33

Setting up an AWS S3/Compatible target 33

Setting up an Azure target 35

Setting up an NFS target 36

Setting up an SMB target 38

Setting up an iSCSI target 40

Defining your backup strategy 42

Applying a predefined policy 42

Creating a custom policy 43

Setting a default policy 50

4 Protecting virtual machines 51

5

Backing up virtual machines 52

Restoring a virtual machine 54

Restore options 55


Cloning a virtual machine 58

Restoring virtual disks 60

Cloning virtual disks 61

Exporting virtual disks 63

Restoring individual files 67

5 Protecting applications 72

Enabling access to application data 72

Planning your application backups 75

Backing up applications 78

Restoring a whole application 79

Restore options 80


Cloning a virtual machine 83

Restoring SQL Server databases 84

Restoring Exchange Server databases, mailboxes, and public folders 87

Restoring Oracle database instances and tablespaces 89

6 Protecting file shares 92

Backing up file shares 92

Restoring file share data 93

Restoring files to the original file share 94

Restoring a whole file share to an external location 94

7 Protecting the HYCU backup controller 96

Backing up the HYCU backup controller 97

Restoring the HYCU backup controller 98

Preparing for a HYCU backup controller restore 99

Restoring the HYCU backup controller to the original location 100

Restoring the HYCU backup controller to a different cluster 101

6

Other HYCU backup controller restore possibilities 103

Recreating HYCU instances 103

8 Performing daily tasks 105

Using the HYCU dashboard 106

Checking the status of jobs 107

Viewing events 108

Sending email notifications 109

Using HYCU reports 110

Getting started with reporting 110

Viewing reports 112

Generating reports 113

Scheduling reports 114

Exporting and importing reports 114

Viewing entity details 115

Viewing the backup status of entities 116

Filtering data 117

Applying the main filter 117

Applying the detail filter 118

Filtering options in the Applications panel 119

Filtering options in the Virtual Machines panel 120

Filtering options in the Volume Groups panel 121

Filtering options in the Shares panel 121

Filtering options in the Policies panel 122

Filtering options in the Targets panel 122

Filtering options in the Jobs panel 122

Filtering options in the Events panel 122

Filtering options in the Self-Service panel 123

Exporting the contents of the panel 123

Managing targets 123

Viewing target information 124

Editing a target 125

7

Activating or deactivating a target 125

Increasing the size of an iSCSI target 126

Deleting a target 126

Managing policies 126

Viewing policy information 127

Editing a policy 127

Deleting a policy 128

Performing a manual backup 128

Expiring backups manually 129

Adjusting the HYCU virtual machine resources 130

9 Managing users 131

HYCU groups 131

User roles 132

Setting up a user environment 134

Creating a new user 134

Creating a new self-service group 135

Setting ownership of virtual machines 136

Setting ownership of file shares 136

Activating or deactivating users or self-service groups 137

Adding users to groups 138

Switching to another group 138

10 Administering 140

Configuring Active Directory authentication 141

Configuring target encryption 142

Managing HYCU instances 142

Creating a HYCU instance by using the HYCU web user interface 142

Viewing HYCU instance information 143

Deleting a HYCU instance 144

Setting the iSCSI Initiator secret 144

Licensing 144

Creating a license request 145

8

Requesting and retrieving licenses 146

Activating licenses 147

Setting up logging 147

Changing the HYCU listening port number 150

Changing network settings 150

Setting power options 151

Configuring an SMTP server 151

Configuring the SSL certificate 152

Creating a new self-signed certificate 153

Importing a CA certificate 153

Upgrading HYCU 153

Upgrading HYCU on a Nutanix AHV cluster 154

Upgrading HYCU on a Nutanix ESXi cluster 156

Upgrading HYCU in a vSphere environment 161

Removing HYCU 164

11 Tuning your data protection environment 167

Accessing the HYCU backup controller virtual machine by using SSH 168

Enabling HTTPS for WinRM connections 169

Configuring FIPS-compliant mode for HYCU 170

Enabling FIPS-compliant mode for HYCU 171

Disabling FIPS-compliant mode for HYCU 171

Setting up LDAPS authentication 171

Securing SMTP connections 172

Importing an SSL certificate for the STARTTLS security mode 172

Importing an SSL certificate for the SSL/TLS security mode 173

Setting up HYCU to use multiple networks 173

Setting up HYCU to use multiple networks on a Nutanix AHV or ESXi cluster 174

Setting up HYCU to use multiple networks in a vSphere environment 175

Increasing the size of the HYCU virtual disks 176

Increasing the size of the HYCU disks in a Nutanix AHV cluster 176

Increasing the size of the HYCU disks in a Nutanix ESXi cluster or vSphere 176

9

environment

Assigning privileges to a vSphere user 177

Using the HYCU REST API Explorer 179

Using the command-line interface 179

12 Managing HYCU backup controllers 181

Using the HYCU Manager console 181

Managing your HYCU backup controllers 183

Adding a HYCU backup controller 183

Viewing information about HYCU backup controllers 183

Viewing events 184

Performing administration tasks 184

Managing users 185

A Customizing HYCU configuration settings 188

Snapshot settings 189

Utilization threshold settings 189

Display settings 190

SQL Server application settings 190

Settings for aborting jobs 190

HTTPS for WinRM configuration settings 191

Nutanix Files settings 191

Data rehydration settings 191

HYCU backup controller restore settings 192

B Restoring to an environment with a different hypervisor 193

Restoring a virtual machine on a Nutanix ESXi cluster or in a vSphereenvironment to a Nutanix AHV cluster 194

Restoring a virtual machine in a vSphere environment to a Nutanix ESXi cluster 197

10

About HYCUHYCU Data Protection for Nutanix (HYCU) is a high performing backup and recoverysolution for Nutanix. It is the first data protection solution that is fully integrated withNutanix, making data protection easy to deploy and simple to use.

Figure 1–1: Introduction to HYCU

Chapter 1

1 About HYCU

11

HYCU key features and benefitsThe following features make HYCU a solution that can transform your business, achievingcomplete compliance and data protection:

l Protects against data loss

Delivers native and reliable data protection for mission-critical applications and data inhyperconverged environments, while ensuring data consistency and easyrecoverability.

l Simplifies deployment

Deployment of the HYCU virtual appliance is performed through the Nutanix Prism webconsole (for Nutanix AHV clusters) or the VMware vSphere Web Client (for Nutanix ESXiclusters and vSphere environments).

l Provides new-found visibility

Discovery solution provides new-found visibility into virtual and physical machines,pinpointing where each application is running.

l Protects data in a few minutes

Data protection of virtual machines, physical machines, applications, file shares, volumegroups, and virtual machine templates can be enabled in a few minutes after thedeployment.

l Delivers predefined policies and provides opportunities for customization

Predefined policies (Gold, Silver, and Bronze) that come with HYCU simplify the dataprotection implementation. However, if the needs of the data protection environmentrequire it, a wide range of opportunities to customize policies is provided.

l Schedules backups based on RPOs

Automatic backup scheduling provides data protection based on your recovery pointobjectives (RPOs).

l Discovers and protects applicationsIn-built application awareness provides application discovery and application-specificbackup and restore flow, ensuring that the entire application data is protected andrecovered to a consistent state.

l Lets you choose targets and sources

Using data storage targets and sources is the administrator's choice.

l Gives you an at-a-glance overview of your environment

The HYCU dashboard helps you identify potential problems and bottlenecks to improvethe performance of your data protection environment.

l Provides an efficient ROBO data protection solution for Nutanix

Backs up remote office/branch office (ROBO) data from data center replicas andenables a one-click restore within the data center or at any remote location.

1 About HYCU

12

l Offers a scalable backup for Nutanix Files

Cuts down the time it takes to back up file shares, saves a significant amount ofcomputing resources, and allows you to take more frequent backups, reducing theamount of data loss in case of a failure.

Data protection environment overviewThe data protection environment consists of the following components:

HYCU backup controllerA virtual machine residing in a source environment. The HYCUbackup controller processes the data collected from sourcesand presents it in the web user interface.

HYCU interfaceAn interface for protecting entities and administering the dataprotection environment, available as the HYCU web userinterface and the command-line interface (hyCLI).

TargetsStorage locations that HYCU uses for storing the protecteddata.

SourcesEnvironments for which HYCU provides data protection—Nutanix clusters, vSphere environments, Nutanix Filesservers, and physical machines.

Entities

Objects to which you can assign a policy and for which youtherefore provide data protection—virtual and physicalmachines, applications, and file shares. Data is alwaysprotected at a granular level, allowing you to restore either thewhole entities or their parts (disks and application items).

The following diagram shows the data protection environment and its most importantcomponents:

Figure 1–2: HYCU architecture

1 About HYCU

13

HYCU data protectionWith the HYCU backup and recovery solution, you can be confident that your business datais protected, which means that it is backed up in a consistent state, stored, can be restored,accessed, and is not corrupted.

HYCU enables you to protect virtual and physical machines, applications running on them,file shares on Nutanix Files servers, volume groups, and virtual machine templates. Afteryou establish your data protection environment (that is, add sources, set up targets, and,optionally, create policies), you can enable data protection. After the first backup issuccessfully completed, you can restore the data if it becomes damaged or corrupted.

Because HYCU is application-aware, when you set credentials for virtual and physicalmachines, it discovers if any applications are installed and running on them. In addition, italso detects details about the discovered applications such as their versions, the hostswhere individual components for the discovered application are installed, and the role ofeach host.

After you deploy HYCU and establish your data protection environment, depending onwhat kind of data you want to protect, see one of the following sections:

l “Protecting virtual machines” on page 51

l “Protecting applications” on page 72

l “Protecting file shares” on page 92

14

Deploying the HYCU virtualapplianceThe HYCU virtual appliance is a preconfigured software solution that you can easily deployto a Nutanix AHV cluster, a Nutanix ESXi cluster, or a vSphere environment for which youwant to provide data protection.

You can deploy HYCU in one of the following modes:

Deployment mode Select this mode if you want to...

HYCU Backup Controller

Protect virtual and physical machines, applications, file shares,volume groups, and virtual machine templates. A HYCUbackup controller is a virtual machine residing in a sourceenvironment that processes data collected from the sourcesand presents it in the web user interface.

HYCU InstanceProtect file shares. A HYCU instance is a virtual machine thatHYCU uses for performing Nutanix Files data copy operations,taking the load off the HYCU backup controller.

HYCU Manager

Manage HYCU backup controllers. HYCU Manager is a virtualmachine residing in a source environment that collects datafrom all the HYCU backup controllers in your data protectionenvironments and presents it in the web user interface.

HYCU deployment consists of the following high-level tasks:

Task Instructions

1. Size the backup infrastructurefor HYCU.

“Sizing your backup infrastructure for HYCU” on thenext page

2. Deploy the HYCU virtualappliance to a source.

“Deploying HYCU to a Nutanix AHV cluster” onpage 17 or “Deploying HYCU to a Nutanix ESXi clusteror a vSphere environment” on page 20

Chapter 2

2 Deploying the HYCU virtual appliance

15

After you successfully deploy the HYCU virtual appliance, you can access HYCU by using asupported web browser. For details on how to log on to HYCU, see “Logging on to HYCU”on page 22.

Sizing your backup infrastructure for HYCUBefore you start deploying the HYCU virtual appliance, size the backup infrastructureaccording to the following requirements:

l HYCU virtual machine:

o Network connection

Make sure that you reserve an IP address for your virtual machine.

o System requirements

For HYCU deployment and configuration, at least 4 CPU cores and 4 GiB of RAM isrequired.

Only if deploying HYCU in the HYCU Backup Controller mode. When setting up your dataprotection environment, keep in mind that some aspects other than its size affectthe system requirements. The source environment performance, target efficiency,the chosen backup strategy, and compression of backup data may increase ordecrease the need for specific resources. For example, if you decide for copyingand archiving data, the number of required targets increases. Also, if you specify alow RPO or backup threshold, the load on your backup infrastructure increasesand HYCU requires more storage and CPU cores. Consider the following sizingrecommendations:

Environment Storage sizeNumber ofCPU cores

Memory

Small (100–200 VMs) 20–40 GiB 6 8 GiB

Medium (200–500 VMs) 100–200 GiB 8 32 GiB

Large (more than 500 VMs) Contact HYCU Support.

l HYCU web user interface:

For a list of web browsers that you can use to access the HYCU web user interface, seethe HYCU Compatibility Matrix.

n Note HYCU is designed to work with a screen resolution of at least 1280 × 720pixels.

l Only if deploying HYCU in the HYCU Backup Controller mode. Targets:

Make sure that destinations you want to use for storing your protected data areavailable and accessible.

https://support.hycu.com/hc/en-us/categories/115000458185-Hycu


16

Firewall settingsIf a firewall is configured in your network infrastructure, make sure that the required portsare open and inbound and outbound connections allowed on the systems.

Purpose Location Host Port Direction Protocol

Accessing the HYCU virtualmachine by using SSH.

HYCU backupcontroller

Local 22 Inbound TCP

Restoring applications andfiles.

HYCU backupcontroller


Backing up data to an NFS 3target.

NFS 3 target Local2049111mountda

InboundTCP/UDPRPC

Backing up data to an NFS 4target.

NFS 4 target Local 2049 Inbound TCP/UDP

Backing up data to an SMBtarget.

SMB target Local 445 Inbound TCP

Backing up data to an iSCSItarget.

iSCSI target Local 3260 Inbound TCP

Accessing Nutanix REST APIv3.

Nutanixclusters

Local 9440b Inbound TCP

Accessing Nutanix Volumes.Nutanixclusters


Discovering Windows VMsand APPs.

Virtualmachines

Local5985–5986

Inbound TCP

Discovering Linux VMs andAPPs.

Virtualmachines

Local 22c Inbound TCP

Accessing the HYCU web userinterface, discover, back up,and restore APPs, as well asrestore individual files.

Virtualmachines

Remote 8443 Outbound TCP

aIn case of the firewall between the HYCU backup controller and an NFS server, you also need to openthe mountd port. For details on the port number, see NFS server documentation.bPort 9440 must be open on the Virtual IP and on each of the Nutanix Controller virtual machines(CVMs).c The SSH daemon must be running.

i Important If there are any additional firewalls in your environment, make sure


17

traffic is allowed from or to the specified ports.

Deploying HYCU to a Nutanix AHV clusterThe HYCU virtual appliance is distributed as a virtual disk image that you can easily deployto a Nutanix AHV cluster by using the Nutanix Prism web console.

PrerequisiteThe backup infrastructure is sized according to the requirements described in “Sizing yourbackup infrastructure for HYCU” on page 15.

Deployment tasksWhen deploying HYCU to a Nutanix AHV cluster, you must perform the following tasks:

Task Instructions

1. Upload the HYCU virtual applianceimage to a Nutanix AHV cluster.

“Uploading the HYCU virtual applianceimage to a Nutanix AHV cluster” below

2. Create a virtual machine for HYCUdeployment.

“Creating a virtual machine for HYCUdeployment on a Nutanix AHV cluster” onthe next page

3. Configure HYCU on the created virtualmachine.

“Configuring HYCU on the virtual machine”on page 19

The following flowchart shows an overview of the HYCU deployment tasks:

Figure 2–1: Overview of deployment tasks

Uploading the HYCU virtual appliance image to a Nutanix AHVcluster

Procedure1. Log on to the Nutanix Prism web console.

2. In the menu bar, click , and then select Image Configuration.

3. In the Image Configuration dialog box, click Upload Image.

4. In the Create Image dialog box, provide the following information:


18

a. Enter the HYCU image name in the format that should correspond to that of theHYCU image file you are uploading.

i Important The HYCU virtual appliance image must be uploaded to theNutanix AHV cluster in the following format:

hycu-<Version>-<Revision>

For example: hycu-4.0.0-3634

If you enter the HYCU image name in a different format, you will not be able touse this image for an upgrade.

b. Optional. Enter an annotation.

c. From the Image Type drop-down menu, selectDISK.

d. From the Storage Container drop-down menu, select a storage container for theimage to be uploaded.

e. In the Image Source section, specify the location of the image file.

5. Click Save.

6. Click Close after the image is successfully uploaded.

Creating a virtual machine for HYCU deployment on a NutanixAHV cluster

Procedure1. In the menu bar in the Nutanix Prism web console, click Home, and then select VM.

2. Click Create VM at the upper right of the screen.

3. In the Create VM dialog box, provide the following information:

a. In the General Configuration section, do the following:

i. Enter a virtual machine name and, optionally, its description.

n Note You can choose any name you wish as long as it contains onlyletters, numbers, and hyphens. Keep in mind that it must start with a letter.

ii. Set the time zone as required.

iii. Leave the Use this VM as an agent VM check box clear.

b. In the Compute Details section, enter the number of virtual CPUs and cores pervirtual CPU, and the amount of memory to allocate to this virtual machine.

c. In the Disks section, click Add New Disk, and then, in the Add Disk dialog box,specify a system disk:

i. From the Type drop-down menu, selectDISK.

ii. From the Operation drop-down menu, select Clone from Image Service.

iii. From the Bus Type drop-down menu, select SCSI.


19

iv. From the Image drop-down menu, select the image you uploaded.

v. In the Size (GiB) field, leave the default size of the system disk (10 GiB).

n Note You can later increase the size of the system disk if needed. Fordetails, see “Increasing the size of the HYCU disks in a Nutanix AHV cluster”on page 176.

vi. Click Add.

d. In the Disks section, click Add New Disk, and then, in the Add Disk dialog box,specify a data disk:

i. Leave the default values for the type of storage device, the device contents, andthe bus type.

ii. From the Storage Container drop-down menu, select a storage container forthe image to be uploaded.

iii. In the Size (GiB) field, enter 32.

n Note You can later increase the size of the data disk if needed. Fordetails, see “Increasing the size of the HYCU disks in a Nutanix AHV cluster”on page 176.

iv. Click Add.

4. In the Network Adapters (NIC) section, click Add New NIC, and then, in the Create NICdialog box, do the following:

a. From the VLAN Name drop-down menu, select a VLAN.

b. Click Add.

5. Click Save.

Configuring HYCU on the virtual machine

Procedure1. From the list of virtual machines in the Nutanix Prism web console, select the one you

created, and then click Power on.

2. When the virtual machine is turned on, click Launch Console.

3. In the HYCU Mode Selection dialog box that opens, select one of the followingdeployment modes:

l HYCU Backup Controller

l HYCU Instance

l HYCU Manager

4. Tab to OK and press Enter.

5. In the Network Configuration dialog box that opens, do the following:


20

a. Enter the values for the following:

l Optional. Host name for the virtual machine

n Note The default host name is generated automatically during theHYCU virtual appliance deployment. The host name should begin with aletter and may contain only letters, numbers, and hyphens (-).

l IPv4 address (for example, 10.1.100.1)

l Subnet mask (for example, 255.0.0.0)

l Default gateway (for example, 10.1.1.1)

l Optional. DNS server (for example, 10.1.1.5)

l Optional. Search domain (for example, domain.com)

n Note The domain name should begin with a letter and contain one ormore periods. It may also contain only letters, numbers, and hyphens (-).

b. Tab to OK and press Enter.

The progress of the HYCU configuration displays.

6. Only if deploying HYCU in the HYCU Instance mode. In the HYCU Backup Controller dialogbox that opens, enter the HYCU backup controller URL and the user name andpassword you use to access HYCU.

i Important If the HYCU backup controller host name cannot be resolved fromthe HYCU instance (for example, in environments that do not use DNS servers),make sure to use the IP address:

https://<IPAddress>:<Port>

The progress of the HYCU backup controller assignment displays.

7. After HYCU is configured, confirm the summary message by pressing Enter.

You can start using HYCU immediately with a prebuilt Instant-on license. This licenseexpires automatically after 45 days and cannot be reused. Therefore, make sure to obtain apermanent license within this 45-day period. For instructions, see “Licensing” on page 144.

Deploying HYCU to a Nutanix ESXi cluster ora vSphere environmentThe HYCU virtual appliance is distributed as an OVF package that you can easily deploy to aNutanix ESXi cluster or a vSphere environment by using the VMware vSphere Web Client.

Prerequisitesl The backup infrastructure is sized according to the requirements described in “Sizing

your backup infrastructure for HYCU” on page 15.


21

l VMware vSphere 6.x only. The Client Integration Plug-In is installed. For instructions, seeVMware documentation.

l Only if deploying HYCU in the HYCU Instance mode. The vSphere Web Client (Flex) islaunched.

Procedure1. Log on to the VMware vSphere Web Client.

2. Right-click your vCenter Server, and then selectDeploy OVF Template.... The DeployOVF Template dialog box opens.

3. In the Select template section, specify the location of the OVF package:

URL Specify a URL to the HYCU OVF package.

Local file

Browse your file system for the HYCU OVF package.

i Important When you are browsing your file system, makesure to select both the .ovf file and the .vmdk file related to theOVF package.

Click Next.

4. In the Select name and location section, enter a name for the HYCU virtual machine andspecify a location where you want to deploy it, and then click Next.

i Important Make sure the virtual machine name you enter matches the HYCUOVF package name. For example, hycu-4.0.0-3634.

5. In the Select a resource section, select where to run the deployed package, and thenclick Next.

6. In the Review details section, verify the package details, and then click Next.

7. In the Select Configuration section, select a deployment configuration:

l HYCU Backup Controller

l HYCU Instance

l HYCU Manager

Click Next.

8. In the Select storage section, select where to store the files for the deployed package,and then click Next.

9. In the Select networks sections, leave the default values, and then click Next.

10. In the Customize template section, enter the values for the following:


n Note The default host name is generated automatically during the HYCUvirtual appliance deployment. The host name should begin with a letter and


22

may contain only letters, numbers, and hyphens (-).







l Only if deploying HYCU in the HYCU Instance mode.

o HYCU backup controller URL

i Important If the HYCU backup controller host name cannot beresolved from the HYCU instance (for example, in environments that do notuse DNS servers), make sure to use the IP address:

https://<IPAddress>:<Port>

o HYCU backup controller user

o HYCU backup controller password

Click Next.

11. In the Ready to complete section, review data, and then click Finish.

n Note Creating the virtual machine may take a few moments. The Power Onoption is enabled only after the virtual machine is created.

12. From the list of virtual machines, right-click the newly created virtual machine, and thenselect Power > Power On to turn it on.

You can start using HYCU immediately with a prebuilt Instant-on license. This licenseexpires automatically after 45 days and cannot be reused. Therefore, make sure to obtain apermanent license within this 45-day period. For instructions, see “Licensing” on page 144.

Logging on to HYCUAfter you successfully deploy the HYCU virtual appliance, you can access HYCU by using asupported web browser. For a list of supported web browsers, see the HYCU CompatibilityMatrix.

Procedure1. In a supported browser, enter the following URL:

https://<ServerName>:8443

In this instance, <ServerName> is the fully qualified domain name of the HYCU server.

For example:


23

https://hycu.example.com:8443

2. On the logon page, enter your logon name and password. You can use the default username and password for initial access to HYCU:

User name: admin

Password: admin

For security purposes, it is highly recommended that you change the default password.

n Note Keep in mind that the level of access depends on your user permissions. Fordetails, see “Managing users” on page 131.

After you log on to the HYCU web user interface, you can configure your environment touse also the HYCU command-line interface (hycli). For more information, see “Using thecommand-line interface” on page 179.

24

Establishing a dataprotection environmentAfter you deploy the HYCU virtual appliance and log on to HYCU, you must establish a dataprotection environment in which data will be effectively protected. Establishing the dataprotection environment involves adding sources, setting up targets, and, if yourenvironment requires custom policies, creating them.

The following flowchart explains the tasks you need to perform to establish your dataprotection environment:

Figure 3–1: Establishing a data protection environment

Chapter 3

3 Establishing a data protection environment

25

The tasks that are required to establish a data protection environment can be performedonly by an infrastructure group administrator and are as follows:

l “Adding sources” below

l “Setting up targets” on page 33

You can enable data protection by using predefined policies that come with HYCU. If you donot want to use any of them, make sure that you create your own policies. For details, see“Creating a policy” on page 44.

After the data protection environment is established, data protection can be accomplishedin several ways to fulfill the needs of particular business.

n Note Before you start protecting your data protection environment, make that theHYCU backup controller is protected. This way, you can quickly recover and resumeyour data protection activities in case of a disaster. For more information, see“Protecting the HYCU backup controller” on page 96.

Adding sourcesAn environment for which HYCU provides data protection consists of one or more sourcesthat you add to HYCU depending on what kind of data you want to protect—virtualmachines or applications running on virtual machines on Nutanix clusters or in vSphereenvironments, file shares on Nutanix Files servers, or physical machines and applicationsrunning on physical machines. For instructions on how to add a specific source, see one ofthe following sections:

l “Adding a Nutanix cluster” below

l “Adding a vCenter Server” on page 27

l “Adding a Nutanix Files server” on page 28

l “Adding a physical machine” on page 32

i Important To achieve the optimal performance of your data protectionenvironment and ensure recoverability, make sure to add the source on which theHYCU backup controller is running to HYCU.

Adding a Nutanix clusterA Nutanix environment consists of one or more Nutanix clusters, each of which hosts aseries of virtual machines running applications. Adding one or more Nutanix clusters toHYCU is as a first step to protecting your virtual machine data.

Nutanix ESXi cluster prerequisiteYour Nutanix ESXi cluster is registered to the vCenter Server through the Prism webconsole. For details on how to do this, see Nutanix documentation.


26

ConsiderationFor backing up virtual machines from their replicas in remote office/branch office (ROBO)environments, you must add both the central site Nutanix cluster and the branch office sitecluster.

Accessing the Sources dialog box

To access the Sources dialog box, clickAdministration, and then select Sources.

Procedure1. In the Sources dialog box, click the Hypervisor tab, and then clickNew.

2. Enter the name of the Nutanix cluster in the following URL format:

https://<ServerName>:<Port>

3. Enter the user name and password of a user with cluster administrative rights.

i Important When adding a Nutanix cluster that has client authenticationenabled, make sure you specify the local user.

4. Only if client authentication is enabled on the Nutanix cluster that you are adding to HYCU.Use the Enable Certificate Authentication switch, and then browse and upload thetrusted CA certificate, the client certificate, and the client private key. Keep in mind thefollowing:

l The supported certificate file formats are PKCS#1 and PKCS#8.

l The private key must not be encrypted.

By enabling certificate authentication, you allow HYCU to connect to the Nutanix cluster.

5. Click Next, and then, depending on the type of hypervisor on the Nutanix cluster youare adding, do one of the following:

Hypervisor type Procedure

AHVIn the Summary dialog box that opens, verify that the validationwas successful, and then click Save.

ESXi

l If you do not plan to use HYCU for file share protection or ifyou plan to use HYCU for file share protection and you donot want a HYCU instance to be created automatically:

a. In the New vSphere Credentials dialog box, leave blankfields and click Next.

b. In the Summary dialog box, verify that the validationwas successful, and then click Save.

l If you plan to use HYCU for file share protection and youwant a HYCU instance to be created automatically:

a. In the New vSphere Credentials dialog box, enter the


27

Hypervisor type Procedure

URL of the vCenter Server to which your Nutanix ESXicluster is registered and the user name and passwordof a user with specific privileges for vCenter Servers.

b. In the Summary dialog box, verify that the validationwas successful, and then click Save.

t Tip If your Nutanix ESXi cluster has the required

vCenter Server permissions, you can see the icon

next to its type.

For details about HYCU instances, see “HYCU instances” onpage 30.

You can also edit any of the existing Nutanix clusters (clickEdit and make the requiredmodifications) or delete the ones that you do not need anymore (clickDelete).

i Important Nutanix ESXi clusters only. Make sure to configure your Windows virtualmachines to not go into sleep mode after a certain amount of time. Otherwise, thenetwork settings are not recognized, and consequently such virtual machines cannot beprotected by HYCU.

Adding a vCenter ServerA vSphere environment consists of ESXi hosts that are managed by vCenter Servers. Oneach of these ESXi hosts, a series of virtual machines running applications reside. Addingone or more vCenter Servers to HYCU is a first step to protecting your virtual machine data.

PrerequisiteA user with specific privileges for vCenter Servers is specified. For details on which privilegesmust be assigned to a vSphere user, see “Assigning privileges to a vSphere user” onpage 177.

LimitationAdding vCloud Director or a stand-alone ESXi host is not supported.



Procedure1. In the Sources dialog box, click the Hypervisor tab, and then clickNew.

2. Enter the name of the vCenter Server in the following URL format:

https://<vCenterServerFQDN>:<Port>


28

The default port for the vCenter Server is 443.

i Important Make sure you configure the HYCU DNS settings in a way thatallows HYCU to resolve this FQDN and, consequently, connect to the vCenter Serverand ESXi hosts on which the virtual machines that you want to include in the backupare running.

3. Enter the user name and password of a user with specific privileges for vCenter Servers.

4. Click Save.

You can also edit any of the existing vCenter Servers (clickEdit and make the requiredmodifications) or delete the ones that you do not need anymore (clickDelete).

Adding a Nutanix Files serverHYCU enables you to protect SMB and NFS file shares on Nutanix Files servers. You can addone or more Nutanix Files servers that host file shares you want to include in the backup.

For protecting file shares, a HYCU instance is introduced in the data protectionenvironment. The HYCU instance is a virtual machine that HYCU uses for performingNutanix Files data copy operations, taking the load off the HYCU backup controller. You canhave one or more HYCU instances in your data protection environment, depending on yourbusiness needs. For details on HYCU instances, see “HYCU instances” on page 30.

PrerequisiteHYCU can access a Nutanix Files server. For details, see “How to allow HYCU to access aNutanix Files server” on the next page.



Procedure1. In the Sources dialog box, click the Nutanix Files tab, and then clickNew.

2. Enter the name of the Nutanix Files server in the following format:

https://<NutanixFilesServerHostname>:<Port>

Entering the port is optional if the default value is used, 9440.

3. In the Nutanix Files Server Credentials section, enter the user name and password of auser with Nutanix Files server administrative rights.

The default user name and password are the following:

User name: admin

Password: Nutanix/4u

If you created a new user for accessing the REST API, you can use this user's credentialsinstead.


29

4. Use the Use SMB protocol for accessing shares switch if you plan to protect SMB fileshares, and then, in the SMB Backup Credentials section, enter the user name andpassword of a server or backup administrator with access to all SMB file shares withinthe Nutanix Files server.

n Note Keep in mind you cannot assign credentials to each share individually.

5. Use the Use NFSv4 protocol for accessing shares switch if you plan to protect NFSfile shares.

6. Click Save.

You can later do the following:

l Edit any of the existing Nutanix Files servers. To do so, select the Nutanix Files server,clickEdit , make the required modifications, and then click Save.

l Delete the Nutanix Files servers that you do not need anymore as follows:

a. Select the Nutanix Files server, and then clickDelete.

b. In the Remove Nutanix Files dialog box, use the Remove unused HYCU instancesswitch if you want to delete also the corresponding HYCU instances, and then clickYes.

How to allow HYCU to access a Nutanix Files serverTo allow HYCU to access a Nutanix Files server, you must prepare the Nutanix Filesenvironment to verify incoming REST API requests. You can create a new user(recommended) or use the default administrator to access the REST API.

n Note Some versions of Nutanix Prism allow you to manage REST API accesspermissions through the Manage roles dialog box. For details, see Nutanixdocumentation.

If this dialog box is not available, do the following:

l To create a new user to access the REST API, follow these steps:

1. Establish a connection to the Nutanix cluster:

ssh @<NutanixClusterHostname>

2. Run the ncli fs list command to list the UUID for the file server.

3. Create a new user:

ncli fs add-user uuid=<UUIDFromStep2> user=<Username>password=<Password>

You can later use the newly created user and password as Nutanix Files servercredentials when adding a Nutanix Files server to HYCU.

l If you are using the default administrator to access the REST API, follow these steps:


30

1. Establish a connection to the Nutanix Files server:

ssh <NutanixFilesServerHostname>

When requested, enter the following credentials:

User name: nutanix

Password: nutanix/4u

2. Run the following command to reset the password for all Nutanix Files servernodes to the default one (that is, Nutanix/4u):

allssh reset_admin_password.py

You can afterward set this password to a different one by running the followingcommands:

allssh "sudo truncate -s 0 /etc/security/opasswd"

allssh "sudo faillock --user admin --reset"

allssh "echo <NewPassword> | sudo passwd --stdin admin"

HYCU instancesBefore you can start protecting file shares, your HYCU backup controller should have atleast one connected HYCU instance that will perform file copy operations in the dataprotection environment.

You can have one or more HYCU instances in your data protection environment. Havingmore than one HYCU instance is especially useful in environments with large file shares inwhich the HYCU instances can share load among themselves when performing file copyoperations.

Depending on your environment, an initial HYCU instance is created automatically whenyou add a Nutanix Files server to HYCU or you must create it manually:

l Automatically:

A HYCU instance is created automatically in the following cases:

On a NutanixAHV cluster

You add a Nutanix Files server that resides on a Nutanix AHV clusterto HYCU and, at the same time, the following applies:

o Either the Nutanix AHV cluster where the Nutanix Files server isdeployed or the Nutanix AHV cluster where the HYCU backupcontroller is deployed is added to HYCU.

o The HYCU virtual appliance image is present on the sameNutanix AHV cluster in the following format:


31


For example, hycu-4.0.0-3634.

On a NutanixESXi cluster

You add a Nutanix Files server that resides on a Nutanix ESXi clusterto HYCU and, at the same time, the following applies:

o The Nutanix ESXi cluster where the HYCU backup controller isdeployed is added to HYCU and the credentials for the vCenterServer associated with this cluster are provided. For details, see“Adding a Nutanix cluster” on page 25.

o The HYCU OVF package is imported to the vCenter Servercontent library and its format is as follows:



n Note By default, HYCU will always try to create a HYCU instance automatically.However, this behavior can be modified by using the afs.instance.autocreation

configuration setting. For details on how to customize the HYCU configurationsettings, see “Customizing HYCU configuration settings” on page 188.

l Manually:

You must create a HYCU instance manually in the following cases:

o Conditions for creating a HYCU instance automatically as described above are notfulfilled.

o DHCP is not enabled on the network where the Nutanix Files server resides.

o You do not want your HYCU instance to use the default network configurationsettings or storage container.

Create a HYCU instance in one of the following ways:

o By deploying the HYCU virtual appliance and selecting the HYCU Instance mode. Fordetails, see “Deploying the HYCU virtual appliance” on page 14.

o By using the HYCU web user interface. For details, see “Creating a HYCU instance byusing the HYCU web user interface” on page 142.

n Note When you create a HYCU instance manually, you can do it before or afteradding a Nutanix Files server to HYCU.

Independent of how the HYCU instance is created, it connects automatically to thecorresponding HYCU backup controller.

Considerationsl Nutanix AHV clusters only. Each HYCU instance is by default created with 8 GiB of RAM, 1

CPU, and 8 CPU cores. However, this can be overridden by setting theafs.instance.memory.mb, afs.instance.cpu, and afs.instance.cores.per.cpu


32

configuration settings to the desired values. For details on how to customize the HYCUconfiguration settings, see “Customizing HYCU configuration settings” on page 188.

l Nutanix ESXi clusters only. Each HYCU instance is by default created with 4 GiB of RAM, 1CPU, and 4 CPU cores.

l When the HYCU instance is created automatically on the Nutanix cluster where theHYCU backup controller resides, it uses the same network settings and storagecontainer as the HYCU backup controller.

l The name format of the HYCU instance virtual machine that is created automatically isas follows:

<HYCUBackupControllerName>-<IndexNumber>

If the HYCU backup controller name cannot be retrieved, the host name will be usedinstead.

l If you change the host name or IP address of the HYCU backup controller, you mustalso change it for all connected HYCU instances. On each connected HYCU instance,update the catalog.master.url configuration setting in the/hycudata/opt/grizzly/config.properties file.

If you later decide to remove any HYCU instance from your data protection environment,you can do it as described in “Deleting a HYCU instance” on page 144.

Adding a physical machineAdding one or more physical machines to HYCU is as a first step to protecting your physicalmachine data.



Procedure1. In the Sources dialog box, click the Physical Machines tab, and then clickNew.

2. Enter the name of the physical machine.

3. Enter the host name or IP address of the physical machine.

4. Click Save.

You can also edit any of the existing physical machines (clickEdit and make the requiredmodifications) or delete the ones that you do not need anymore (clickDelete).

n Note If you delete a physical machine from HYCU and then add it again (with thesame name and IP address), keep in mind that this physical machine will be treated as anew one and therefore no old restore points will be available.


33

Setting up targetsTargets are locations where the protected data is stored. HYCU allows you to store yourdata to AWS S3 or S3-compatible storage, Azure storage, an NFS share, an SMB share, andan iSCSI storage device.

n Note A Nutanix Files share can be used as an NFS or SMB target. If you plan to usethe Nutanix Files share only as a target and not as a source, there is no need to add theNutanix Files server to HYCU.

The approach to set up targets is common for different target types. However, there arespecific prerequisites and steps that are required for each target type. Depending on whichtarget you want to set up, see one of the following sections:

l “Setting up an AWS S3/Compatible target” below

l “Setting up an Azure target” on page 35

l “Setting up an NFS target” on page 36

l “Setting up an SMB target” on page 38

l “Setting up an iSCSI target” on page 40

Setting up an AWS S3/Compatible targetPrerequisitesl The target is configured and accessible.

l The bucket is created. When creating an S3 bucket for HYCU, make sure versioning isdisabled. For details on how to do this, see AWS documentation.

Limitationsl HYCU does not support the AWS S3 targets that use the Glacier storage class.

l HYCU currently supports only AWS S3 Signature Version 4.

l Storing physical machine data to this type of target is not supported.

Considerationsl The following are the minimum required AWS S3 permissions that must be specified:

s3:GetObject, s3:DeleteObject, s3:PutObject, s3:ListBucket, s3:GetBucketAcl,s3:ListBucketMultipartUploads, and s3:GetBucketLocation.

l Only if setting up a Tencent Cloud target. Make sure the service endpoint URL does notcontain the bucket name. For example, if the Tencent Cloud access domain ishttps://testbucket-1234567890.cos.ap-chengdu.myqcloud.com, in the HYCUService endpoint field, enter the URL without the bucket name:

https://cos.ap-chengdu.myqcloud.com

RecommendationIt is recommended that the target is dedicated only to a single HYCU backup controller.


34

Accessing the Targets panel

To access the Targets panel, in the navigation pane, clickTargets.

Procedure1. In the Targets panel, clickAdd/Import. The Add Target dialog box appears.

2. In the General section, do the following:

a. Enter the name of a target and, optionally, its description.

b. In the Size field, enter the maximum storage space that should be reserved for thebackup files (in MiB, GiB, or TiB).

c. In the Concurrent backups field, specify the maximum number of concurrentbackups.

If the backup throughput allows, you can specify that more backup jobs runconcurrently to reduce the duration of backups and the amount of queued backupjobs.

d. Use the Use for archiving switch if you want this target to be reserved for dataarchives.

i Important The target that you use for archiving data cannot be used forbacking up data or storing copies of backup data.

e. Use the Enable Compression switch if you want HYCU to compress backup databefore storing it on this target. Compression can be used for backup data, copies ofbackup data, and data archives.

i Important Compression may cause degradation of HYCU performance ifused with targets that are reserved for data archives, especially with backupchains that include numerous incremental backup images. Additionally, backingup, copying backup data, and archiving to targets with enabled compressionand archiving of compressed data may increase system requirements for theHYCU backup controller.

3. In the Target section, do the following:

a. From the Type drop-down menu, selectAWS S3/Compatible or AWSGovernment.

b. Enter the service endpoint URL, the bucket name, the access key ID, and the secretaccess key. The access key and the secret access key are used to authenticateAmazon API service calls.

c. Use the Path style access switch if you want HYCU to use a path-style URL(https://s3.amazonaws.com/<BucketName>) to access the bucket. HYCU by defaultuses a virtual-hosted–style URL (https://<BucketName>.s3.amazonaws.com).

4. Click Save.


35

The target is added to the list of targets. For details on managing targets, see “Managingtargets” on page 123.

Setting up an Azure targetPrerequisiteThe target is configured and accessible.

LimitationStoring physical machine data to this type of target is not supported.


ConsiderationYour data on the Azure target can be stored in the hot, cool, and archive storage tiers. Toensure the data stored in the archive storage tier is also restored, HYCU is configured toperform data rehydration before performing a restore. For details, see “Data rehydrationsettings” on page 191.






b. In the Size field, enter the maximum storage space that should be reserved for thebackup files (in MiB, GiB, or TiB).





For details on how HYCU manages archiving data to the Azure cloud, see “Archivingdata to the Azure archive storage tier” on page 49.


36


i Important Compression may cause degradation of HYCU performance ifused with targets that are reserved for data archives, especially with backupchains that include numerous incremental backup images. Additionally, backingup, copying backup data, and archiving to targets with enabled compressionand archiving of compressed data may increase system requirements for theHYCU backup controller.


a. From the Type drop-down menu, selectAZURE, AZURE Government, or AZUREChina.

b. Enter the storage account name, the secret access key, and the container name.

n Note If the container does not exist, it is created automatically.

4. Click Save.


Setting up an NFS targetPrerequisitesl The target is configured and accessible for the HYCU backup controller and the HYCU

instances.

l There is enough free space on the target for storing the data.

l If deduplication is enabled on the target, the target is dedicated exclusively to HYCUbackups. By dedicating a target exclusively to HYCU backups, you ensure that accuratestorage utilization reports are provided.

l If the target resides on Windows, local permissions (security) are set to Full Control

for Everyone. If you want to limit access to this system only for HYCU, use the HYCUbackup controller IP address for this purpose.

LimitationStoring physical machine data to this type of target is not supported.





37




b. Optional. In the Size field, enter the maximum storage space that should bereserved for the backup files (in MiB, GiB, or TiB). If your target is not dedicatedexclusively to HYCU backups, you must leave this field empty.

When this field is left empty, HYCU retrieves the available amount of storage spacefrom the target itself.

n Note If the target has deduplication enabled, HYCU's estimation ofrequired storage space on the target may be higher than the actual amount ofspace required on the storage media. Therefore, it is recommended to leavethis field empty in such cases.






i Important Compression may cause degradation of HYCU performance ifused with targets that are reserved for data archives, especially with backupchains that include numerous incremental backup images. Additionally,archiving of compressed data to targets with enabled compression mayincrease system requirements for the HYCU backup controller.


a. From the Type drop-down menu, selectNFS.

b. Enter the NFS server name or IP address and the path to the NFS shared folderfrom the root of the server (for example, /backups/HYCU).

c. Use the Target encryption switch if you want the data stored on this target to beencrypted.

If you enable target encryption, keep in mind the following:


38

l The deduplication ratio may be affected by it (in cases where the target hasdeduplication enabled).

l You cannot use this target when protecting the HYCU backup controller.

4. Click Save.


Setting up an SMB targetPrerequisitesl The target is configured and accessible for the HYCU backup controller and the HYCU

instances.

l There is enough free space on the target for storing the data.

l If deduplication is enabled on the target, the target is dedicated exclusively to HYCUbackups. By dedicating a target exclusively to HYCU backups, you ensure that accuratestorage utilization reports are provided.

l The supported SMB version is used. For a list of supported SMB versions, see the HYCUCompatibility Matrix.

l Only if protecting physical machine data. The target is accessible from the physicalmachine.

LimitationOnly if protecting physical machine data. Target encryption and compression are notsupported.







b. Optional. In the Size field, enter the maximum storage space that should bereserved for the backup files (in MiB, GiB, or TiB). If your target is not dedicatedexclusively to HYCU backups, you must leave this field empty.


39

When this field is left empty, HYCU retrieves the available amount of storage spacefrom the target itself.

n Note If the target has deduplication enabled, HYCU's estimation ofrequired storage space on the target may be higher than the actual amount ofspace required on the storage media. Therefore, it is recommended to leavethis field empty in such cases.








a. From the Type drop-down menu, select SMB.

b. Optional. Enter the domain and user credentials.

c. Enter the SMB server name or IP address and the path to the SMB shared folderfrom the root of the server (for example, /backups/HYCU).

d. Use the Target encryption switch if you want the data stored on this target to beencrypted.

If you enable target encryption, keep in mind the following:

l The deduplication ratio may be affected by it (in cases where the target hasdeduplication enabled).

l You cannot use this target when protecting the HYCU backup controller.

4. Click Save.


40


Setting up an iSCSI targetPrerequisitesl The target is configured and accessible.

l The target has not been initialized yet.

l The iSCSI storage device is dedicated only to a single HYCU backup controller.

C Caution Disregarding this prerequisite may result in data loss or corruption.Therefore, make sure to avoid the following scenarios:o Several HYCU backup controllers are using the same target simultaneously.

o Any appliance other than HYCU and HYCU itself are using the same targetsimultaneously.

l The HYCU iSCSI Initiator secret is added on the iSCSI server if you want to enablemutual authentication between HYCU and the iSCSI server.

l For improved backup and restore performance, the iSCSI Data Service IP address is

specified on the Nutanix cluster by using the Prism console ( > Cluster Details).

This automatically enables the Nutanix load balancing feature during backup andrestore, which eliminates heavy I/O load on the Nutanix cluster and storage containers.For details, see Nutanix documentation.

Limitationsl The iSCSI target cannot be used for protecting file shares on the Nutanix Files server.

l Storing physical machine data to this type of target is not supported.






b. Optional. In the Size field, enter the maximum storage space that should bereserved for the backup files (in MiB, GiB, or TiB).

If you leave this field empty, HYCU retrieves the available amount of storage spacefrom the target itself.

c. In the Concurrent backups field, specify the maximum number of concurrent


41

backups.







a. From the Type drop-down menu, select iSCSI.

b. Enter the target portal IP address and the target name.

n Note If data from sources other than HYCU resides on the storage device,such target cannot be set for HYCU backups.

c. Use the Target encryption switch if you want the data stored on this target to beencrypted.

n Note If you enable target encryption, you cannot use this target whenprotecting the HYCU backup controller.

4. If the iSCSI server requires CHAP authentication, in the CHAP section, do the following:

a. Use the switch to turn the CHAP authentication option on, and then provide a username and the target secret (the security key) for the user's account to access theiSCSI server.

b. Use the Perform mutual authentication switch if you want the iSCSI target to beauthenticated by HYCU. In this case, the HYCU iSCSI Initiator secret must bespecified on the iSCSI server. For details about setting the iSCSI Initiator secret, see“Setting the iSCSI Initiator secret” on page 144.

5. Click Save.



42

Defining your backup strategyHYCU enables you to schedule automatic backups to achieve the optimum level of dataprotection based on your recovery point and time objectives, and backup retentionrequirements. Backups can be scheduled to start each time the specific number of minutes,hours, days, weeks, or months has passed.

When defining your backup strategy, take into account the specific needs of yourenvironment and consider the following:

l Recovery Point Objective (RPO)

RPO is the maximum period of time for which data loss is considered acceptable (inmonths, weeks, days, hours, or minutes). For example, setting the RPO to 24 hoursmeans that your business can tolerate losing only data from the last 24 hours.

l Recovery Time Objective (RTO)

RTO is the maximum amount of time (in months, weeks, days, hours, or minutes) thatcan be spent on restoring data after a disaster occurs.

Decide which of the following two approaches best suits the needs of your environment:

l Applying a predefined policy

You can use any of the predefined policies (Gold, Silver, or Bronze) to simplify the dataprotection implementation. For details, see “Applying a predefined policy” below.

l Creating a custom policy

If none of the predefined policies meets the needs of your environment, you can createa new policy and tailor it to your needs. For details, see “Creating a custom policy” onthe next page.

If you consider one of the predefined or custom policies satisfies all data protection goalsof your environment, you can set such a policy as default. For details, see “Setting a defaultpolicy” on page 50.

Applying a predefined policyWhen establishing a data protection environment, you can take advantage of thepredefined policies that provide a fast and convenient way of enabling data protection, andcover the most common data protection scenarios.

HYCU comes with the following predefined policies:

Type of predefinedpolicy

Description

Gold Data is backed up every 4 hours and restored within 4 hours.

Silver Data is backed up every 12 hours and restored within 12 hours.

Bronze Data is backed up every 24 hours and restored within 24 hours.


43

If you want to exclude entities from being backed up, you can use the Exclude policy.

Creating a custom policyIf the needs of your environment are not covered with any of the predefined policies, youcan create a new policy and tailor it to your needs. While tailoring a policy to your needsand setting the desired RPO, RTO, and targets, you can also enable one or more policyoptions for optimal policy implementation. These policy options are the following:

Policy option Description

Backup windowAllows you to start all backup jobs within specific time framesto improve effectiveness and avoid overload of yourenvironment.

Backup from replica

Available only for Nutanix clusters. Allows you to back up yourvirtual machines from their replicas in remote office/branchoffice (ROBO) environments.

i Important Make sure that the schedule interval youset for the Nutanix protection domains that include thevirtual machines you want to protect is less than or equalto the RPO set in the HYCU policy.

Keep in mind that the replication retention for the respectivesnapshot on the Nutanix cluster is automatically adjusted tothe RPO set in the HYCU policy. This allows HYCU to use theChanged Block Tracking (CBT) feature to get a list of changeddata since the last snapshot and perform an incrementalbackup.

For details on protecting virtual machines through theNutanix Prism web console, see Nutanix documentation.

Archiving Allows you to preserve your data for future reference.

Copy Allows you to create a copy of backup data.

Fast restorea

Available only for Nutanix clusters. Allows you to restore virtualmachine or application data to the original storage containerin a fast way by keeping local snapshots on the Nutanixcluster for the specified retention time.

With this option enabled, HYCU will keep more than onesnapshot on the Nutanix cluster, depending on yourretention settings. This will allow you to restore virtualmachine or application data in a fast way, reducing downtime.


44

a Nutanix ESXi clusters only. If besides HYCU you use a Nutanix protection domain to protect virtual

machines, a fast restore is performed only if the required snapshot is available in the protectiondomain.

Creating a policyYou can create a custom policy that will meet all the needs of your data protectionenvironment.

Prerequisitesl If you plan to enable the Backup window policy option, make sure you have created a

backup window. For details on how to do this, see “Creating a backup window” onpage 46.

l If you plan to enable the Archiving policy option, make sure you have created a dataarchive. For details on how to do this, see “Creating a data archive” on page 48.

l Only if using Back up from replica option. If you plan to back up virtual machines fromtheir replicas in ROBO environments, make sure these prerequisites are met::o A protection domain that includes the virtual machines you want to protect is

created and the specified schedule interval is less than or equal to the RPO set inthe HYCU policy. For details on protecting virtual machines through the NutanixPrism web console, see Nutanix documentation.

o Both the central site Nutanix cluster and the branch office site cluster are added toHYCU. For details, see “Adding a Nutanix cluster” on page 25.

Accessing the Policies panel

To access the Policies panel, in the navigation pane, clickPolicies.

Procedure1. In the Policies panel, clickNew. The New Policy dialog box appears.

2. Enter a name and, optionally, a description of your policy.

3. Add any of the following policy options to the list of the enabled options by clicking it:

l Backup (mandatory)

l Backup window

l Copy

l Archiving

l Fast restore (available only if the Backup from replica option is disabled)

l Backup from replica (available only if the Fast restore option is disabled)

i Important The Backup from replica and Fast restore options are notavailable for vSphere virtual machines and applications.

4. In the Backup section, do the following:


45

a. In the Backup every field, set the RPO (in months, weeks, days, hours, or minutes).

b. In the Recover within field, set the RTO (in months, weeks, days, hours, or minutes).

c. In the Retention field, set a retention period (in months, weeks, or days) for thedata.

d. From the Targets drop-down menu, select one or more targets that you want touse for storing protected data.

If you want your target to be selected automatically, make sure the Automaticallyselected option is selected. In this case, the HYCU advanced schedulerautomatically selects only targets that can guarantee compliance with the RPO andRTO policy settings. Targets that have their estimated backup time lower than theRPO and estimated recovery time lower than the RTO are added to the pool oftargets. Based on each entity size, as well as target backup and restore throughputand queue, the HYCU advanced scheduler calculates the backup and recovery endtime and selects the target where the backup will complete fastest.

n Note The target for incremental backups can be any target in the selectedpool of targets. To have a single target for all backups in a backup chain, makesure to select a single target per policy.

e. In the Backup threshold field, specify a backup threshold value of 0 through 100percent (the default value is 25%). When the amount of changes on a virtualmachine since the last full backup reaches the specified value, a new full backup isperformed instead of an incremental one.

5. Depending on which policy options you have enabled, do the following:

Enabledoption

Procedure

Backupwindow

To specify a backup window, in the Backup section, from theBackup window drop-down menu, select a backup window forbackup jobs. If no backup window is available and you want tocreate one, see “Creating a backup window” on the next page.

If you do not select a backup window, the Always option is shown,which means that your backups are allowed to run at any time.

Copy

To create a copy of backup data, in the Copy section, do thefollowing:

a. Set a retention period (in months, weeks, or days) for the copyof backup data.

b. From the Targets drop-down menu, select one or more targetsthat you want to use for storing the copy of backup data.

If you want your target to be selected automatically, make sure


46

Enabledoption

Procedure

the Automatically selected option is selected. The copy targetwill be different from the target for data safety reasons.

n Note When there are several targets available forstoring the copy of backup data and multiple copies ofbackup data are being created in parallel, HYCU distributesthese copies accordingly among targets based on theestimated size of queued and running backups on them.

ArchivingTo archive data, in the Archiving section, from the Data archive drop-down menu, select a data archive. If no data archive is available andyou want to create one, see “Creating a data archive” on page 48.

Fast restorea

Available only for Nutanix clusters. To keep more than one snapshoton the Nutanix cluster, which allows a fast restore, in the Fastrestore section, set a retention period (in months, weeks, days,hours, or minutes) for snapshots. For example, if you set the RPO totwo days and the snapshot retention period to four days, you willhave two snapshots available on the Nutanix cluster.

n Note The snapshot retention period cannot be shorterthan the RPO or longer than the backup retention period.

Backup fromreplicaa

Available only for Nutanix clusters. To back up virtual machines fromtheir replicas, in the Backup from replica section, from the Centralsite cluster drop-down menu, select the cluster on which thereplicas of your virtual machines reside.

a Nutanix ESXi clusters only. If besides HYCU you use a Nutanix protection domain to protect

virtual machines, a fast restore is performed only if the required snapshot is available in theprotection domain.

6. Click Save.

The custom policy is created and added to the list of policies. For details on managingpolicies, see “Managing policies” on page 126.

Creating a backup windowHYCU enables you to define time frames when your backup jobs are allowed to start. If youuse a backup window, the backup jobs are started only within the specified hours,therefore improving effectiveness and avoiding an overloaded environment. For example,you can schedule your backup jobs to run on non-production hours to reduce loadsduring peak hours.

You can use backup windows with both predefined policies and custom policies.


47

i Important When defining a backup window, make sure that the RPO specified inthe affected policy can be achieved within this backup window. If the RPO is shorterthan any time frame during which backup jobs are not allowed to start, this will result inyour entity not being compliant with backup requirements.



Procedure1. In the Policies panel, clickBackup Window.

2. In the Backup Window dialog box that appears, clickNew. The New dialog boxappears.

3. Enter a name for your backup window and, optionally, a description.

4. From the Time zone drop-down menu, specify the time zone for your backup window.You can click one of the displayed time zones (your local time zone or your HYCUbackup controller time zone ) or select one from the drop-down list.

5. Click Full/Incremental or Incremental Only to schedule backups depending on thebackup type.

n Note During the Full/Incremental time frame, backups of any backup type arestarted, whereas during the Incremental Only time frame, only incremental backupsare started.

6. Select the week days and hours during which you want backups of the selected backuptype to start running. To specify a time frames for backups of a different backup type,select another backup type, and then repeat this step.

t Tip You can click and drag to quickly select a time frame that includes the daysand hours you want to add.

The selected time frames are displayed in the Time Frames field. If you want to deleteany of the selected time frames, clickx next to it.

7. Click Save.

8. In the Backup Window dialog box, click Close.

You can later edit any of the existing backup windows (clickEdit and make the requiredmodifications) or delete the ones that you do not need anymore (clickDelete).

After you create a backup window, you can do the following:

l Specify a backup window when creating a new policy. For details, see “Creating a policy”on page 44.

l Assign a backup window to the existing policy. To do so, select the policy, clickEdit,and then make the required modifications.


48

ExampleYou have selected the Bronze policy and specified the time frames for backups of any typeto start on Saturday and Sunday and for incremental only backups to start 6 PM to 6 AMon week days.

In this case, the backup jobs will be started every 24 hours (full backups will be startedonly during the weekends) at any point of time within the specified backup windows.

Creating a data archiveHYCU enables you to create an archive of your data and keep it for a longer period of time.By archiving data, the data is stored for future reference on a weekly, monthly, or yearlybasis. Your data is isolated from current activity and safely stored in a secure local or cloudarchive location.

Prerequisitesl The archive target is reserved only for data archives (no backup data is stored on the

archive target).

l Only for archiving data to the Azure archive storage tier. Data archives are stored in theAzure cloud with the Blob Storage or General Purpose v2 (GPv2) accounts.

Azure archive storage tier limitationsl General Purpose v1 (GPv1) accounts do not support moving data archives to the

archive storage tier.

l Data archives created with any of the previous versions of HYCU are not moved to thearchive storage tier.



49


Procedure1. In the Policies panel, click Archiving.

2. In the Archiving dialog box that appears, clickNew .

3. In the New dialog box that appears, enter a name for your data archive and, optionally,a description.

4. Add any of the desired archiving options to the list of the enabled options by clicking it.The following options are available:

Weekly Allows you to create a weekly archive of data.

Monthly Allows you to create a monthly archive of data.

Yearly Allows you to create a yearly archive of data.

5. Specify the hour and the minute when the archive job should begin running.

i Important All scheduled backup jobs are started based on the HYCU backupcontroller time zone and are not affected by the backup windows specified for thesame policy.

6. Provide information about when to archive data, the retention period to be used, andthe archive target.

n Note Make sure that the retention period is longer than the RPO to prevent thearchive from expiring before a new backup is performed.

For details on how HYCU manages archiving data to the Azure cloud, see “Archivingdata to the Azure archive storage tier” below.

7. Click Save.

You can later edit any of the existing data archives (clickEdit and make the requiredmodifications) or delete the ones that you do not need anymore (clickDelete). Keep inmind that you cannot modify an archive target if an archiving job is in progress on thattarget.

After you create a data archive, you can do the following:

l Specify a data archive when creating a new policy. For details, see “Creating a policy” onpage 44.

l Assign a data archive to the existing policy. To do so, select the policy, clickEdit, andthen make the required modifications.

Archiving data to theAzure archive storage tierHYCU automatically moves each data archive that has a retention period set to at least 180days from the Azure cool or hot storage tier to the archive storage tier. By moving dataarchives to the archive storage tier, HYCU ensures your data is stored most cost-efficiently


50

because the archive storage tier is optimized for storing data that is not accessed frequentlyand is stored for at least 180 days.

i Important When restoring data archives, HYCU performs data rehydrationduring which the tier of the Blob object storage is changed from the archive storage tierto the hot storage tier. Keep in mind that this can take a few hours to complete. HYCUmoves data back to the archive storage tier afterward.

Setting a default policyYou can select one of the predefined or custom policies to be the default policy for yourdata protection environment. After you set a default policy, it is assigned to all existingentities that do not have an assigned policy yet, and to all newly discovered ones.



To set a default policy, follow these steps:

1. In the Policies panel, select the policy that you want to set as default, and then click Set Default.

2. In the Set Default Policy dialog box that appears, do one of the following:

l Click Yes if you want to assign the default policy to all entities that do not have anassigned policy (that is, existing and newly discovered ones).

l Click No if you want to assign the default policy only to newly discovered entities.

If you later decide not to use this policy as the default one, click Clear Default.

51

Protecting virtual machinesHYCU enables you to protect your virtual machine data with fast and reliable backup andrestore operations. After you back up a virtual machine, you can choose to restore theentire virtual machine, virtual disks, or individual files.

n Note The instructions for protecting virtual machine data apply also to physicalmachines except where specifically stated otherwise.

Depending on your source, you can also protect the following:

Source Item available for protection

Nutanix cluster

Volume group (logically related virtual disks that are attachedto a virtual machine).

t Tip After you back up virtual machines, you can viewall protected volume groups attached to virtual machinesand their details in the Protected Volume Groups panel.The details that you can view for volume groups are thesame as for any entity. Therefore, the same informationapplies to volume groups as described for entities in“Viewing entity details ” on page 115.

Accessing the ProtectedVolume Groups panelTo access the Protected Volume Groups panel, in thenavigation pane, click Volume Groups.

vSphere environmentVirtual machine template (virtual machine that is used as atemplate to create other virtual machines).

LimitationHYCU can be used for protecting physical machines only if it at least one Nutanix cluster isadded to HYCU.

For details on how to protect virtual machine data efficiently, see the following sections:

l “Backing up virtual machines ” on the next page

l “Restoring a virtual machine” on page 54

l “Restoring individual files” on page 67

Chapter 4

4 Protecting virtual machines

52

Backing up virtual machinesWith HYCU, you can back up your virtual machines in a fast and efficient way.

n Note The procedure for backing up virtual machine templates is the same as forvirtual machines. Therefore, you can follow the same instructions as for backing upvirtual machines.

Prerequisitesl vSphere environments only. VMware Tools of the latest version is installed on virtual

machines.

l Nutanix clusters only. When backing up virtual machines that have volume groupsattached and you want the volume groups to be backed up as well, your AOS version is5.8 or higher. Otherwise, only the virtual machines will be backed up.

l Physical machines only.

o The VSS service is enabled and running, and the VSS writer status is stable.

o WinRM must is enabled and configured by using the winrm quickconfig

command.

Limitationsl Only a backup of local fixed disks and volume groups that are attached to virtual

machines on the same Nutanix cluster directly or by using iSCSI is supported. Whenbacking up a virtual machine with remote volumes (for example, iSCSI, disk arrays,mapped network disks), such volumes are not included in the snapshot and areconsequently not backed up.

l Backing up vSphere virtual machines that have RDM or independent disks is notsupported.

l Nutanix ESXi clusters and if using the Backup from replica option only. Backing up virtualmachines that have disks on different containers is not supported.

l Nutanix AHV clusters only. With a Nutanix protection domain configured with NearSync,HYCU can create snapshots only if the AOS version is 5.9 or higher.

Considerationsl On Linux, restoring files is possible only from file systems that are permanently

mounted. Therefore, make sure the required file systems are specified in the/etc/fstab file before the backup is made.

l In the large or medium size data protection environments with the virtual machines ofa larger size (2-4 TB), keep in mind, that the first backup of such virtual machines takesmore time and resources. Consider protecting these virtual machines in a way that theyare not backed up simultaneously. You can assign a policy to a large virtual machine,wait until it gets protected, and then continue with protecting other virtual machines.


53

l vSphere environments only. If something unexpected occurs during the backup of avirtual machine template (for example, a network problem), the virtual machinetemplate that is converted to a virtual machine as part of the backup process willremain converted. In this case, make sure to convert the virtual machine back to thevirtual machine template. For details on how to do this, see VMware documentation.

l Nutanix ESXi clusters only. If the snapshot that HYCU used to perform a full backup ismissing on a Nutanix cluster (for example, because the HYCU protection domain wasdeleted from Prism), the next virtual machine backup will be a full backup.

l Only if a protection domain is configured with NearSync. Although snapshots in aprotection domain are created in a 1–15 minute interval, HYCU uses only the snapshotsthat are created on an hourly basis for backing up and restoring from snapshots. Thisapplies to the following environments:o Nutanix ESXi clusters

o Nutanix clusters when using the Backup from replica option

l In the case of a Nutanix ESXi cluster whose storage container is presented as an NFSdatastore to the VMware infrastructure, a full backup of a virtual disk on such a storagecontainer performed using a corresponding vSphere source will copy the entireallocated disk, not only the used blocks.

l Only if you plan to clone a physical machine to a virtual machine running on a Nutanix AHVcluster by using the Clone VM restore option. Make sure the Nutanix VirtIO package isinstalled on the physical machine before you back it up. For detailed information aboutinstalling Nutanix VirtIO, see Nutanix documentation.

Recommendations if planning to restore a virtualmachine to an environmentwith a different hypervisorIf you plan to restore a virtual machine on a Nutanix ESXi cluster or in a vSphereenvironment to a Nutanix AHV cluster, follow these recommendations before backing it upto ensure that your virtual machine will boot after the restore (otherwise, you will need toperform additional manual steps as described in “Restoring a virtual machine on a NutanixESXi cluster or in a vSphere environment to a Nutanix AHV cluster” on page 194):

l Windows virtual machine only. The Nutanix VirtIO package is installed on a virtualmachine. If you have NGT installed on your virtual machine on the Nutanix ESXi cluster,there is no need to install the Nutanix VirtIO package because it is already installed aspart of NGT installation.

l Linux virtual machine on a Nutanix ESXi cluster only. NGT is installed on your virtualmachine.

l Linux virtual machine in a vSphere environment only. The VirtIO drivers are added to theGuest OS kernel.

Accessing the Virtual Machines panel

To access the Virtual Machines panel, in the navigation pane, click Virtual Machines.


54

Procedure1. Only if you plan to protect physical machines or volume groups that are attached to a virtual

machine by using iSCSI. Assign credentials to physical machines that you want to protector to virtual machines whose volume groups you want to protect. For each machine, dothe following:

a. Select the physical machine or the virtual machine to which volume groups areattached.

b. ClickCredentials. The Credential Groups dialog box appears.

c. ClickNew.

d. Enter the credentials with administrative privileges that are required for accessingthe machine.

e. Click Save.

f. Click Assign.

2. Select the virtual machines that you want to back up.

t Tip You can update the list of virtual machines by clicking Synchronize. Tonarrow down the list of displayed virtual machines, you can use the filtering optionsdescribed in “Filtering data” on page 117.

3. ClickPolicies. The Policies dialog box opens.

4. From the list of available policies, select the desired policy.

5. Click Assign to assign the policy to the selected virtual machines.

n Note When you assign the policy to the selected virtual machines, the samepolicy is also assigned to the applications running on them if these applicationsalready have an assigned policy. In this case, the policy assigned to the virtualmachines takes precedence over the policy assigned to the applications and isautomatically assigned to the applications.

The backup is scheduled according to the values that you defined for your policy. Ifrequired, you can also perform a manual backup at any time. For details, see “Performing amanual backup” on page 128.

Restoring a virtual machineHYCU enables you to restore either an entire virtual machine or only virtual disks (virtualmachine disks and/or Nutanix volume groups attached to virtual machines) that becamecorrupted.

n Note vSphere environments only. The procedure for restoring virtual machinetemplates is the same as for virtual machines. Therefore, you can follow the sameinstructions as for restoring virtual machines.


55

Prerequisitesl vSphere environments only. You have the required restore privileges assigned. For details,

see “Assigning privileges to a vSphere user” on page 177.

l If you are restoring a virtual machine to the same source and you want the existing ISOimage to be attached to the restored virtual machine, make sure the ISO image that wasattached to the virtual machine at backup time still exists on the source at virtualmachine restore time and its name and location are the same.

l Physical machines only. At least one Nutanix cluster is added to HYCU to provide astorage container for storing the restore data. For details on how to add a Nutanixcluster to HYCU, see “Adding a Nutanix cluster” on page 25.

Limitationsl If you are restoring a virtual machine from one source to another, the ISO image that

was attached to the virtual machine at backup time will not be attached to the restoredvirtual machine.

l Restoring a virtual machine running on a Nutanix ESXi cluster by using the Restore VMoption is supported only if your AOS version is 5.9 or higher.

ConsiderationYou cannot perform a restore of a virtual machine whose retention period specified in thepolicy has been exceeded (such restore points are grayed out in the HYCU web userinterface). However, if required, this can be overridden by setting therestore.enabled.if.retention.is.up configuration setting in the HYCUconfig.properties file to true. For details on how to customize the HYCU configurationsettings, see “Customizing HYCU configuration settings” on page 188.

Restore optionsYou can select among the following restore options:

Restore option Description

Restore VM

Enables you to restore a virtual machine to its original or a newlocation. Select this option if you want to replace the original virtualmachine with the restored one. For instructions, see “Restoring avirtual machine” on the next page.

i Important You cannot restore a physical machine byusing this option.

Clone VM

Enables you to create a clone of a virtual machine by restoring it toits original or a new location. Select this option if you want to keepthe original virtual machine. For instructions, see “Cloning a virtualmachine” on page 58.


56


Restore vDisks

Enables you to restore virtual disks to their original or a newlocation. Select this option if you want to replace the original virtualdisks with the restored ones. For instructions, see “Restoringvirtual disks” on page 60.

i Important You cannot restore physical machine disksby using this option.

Clone vDisks

Enables you to create clones of virtual disks by restoring them totheir original or a new location. Select this option if you want tokeep the original virtual disks. For instructions, see “Cloning virtualdisks” on page 61.

i Important You cannot restore vSphere virtual machinedisks by using this option.

Export vDisks

Enables you to restore virtual disks to an NFS or SMB share. Selectthis option if you want to make the virtual disks available to userswith specific access permissions or use the virtual disks later tocreate a new virtual machine. For instructions, see “Exportingvirtual disks” on page 63.

n Note By using the Clone VM or Export vDisks option, you can also restore a virtualmachine to an environment with a different hypervisor. For prerequisites, limitations,considerations, and/or additional steps that you should perform to successfully restorea virtual machine to an environment with a different hypervisor, see “Restoring to anenvironment with a different hypervisor” on page 193.

Restoring a virtual machineYou can restore a virtual machine to its original or a new location. In this case, the originalvirtual machine will be overwritten.

LimitationRestoring physical machines by using the Restore VM option is not supported.

Considerationsl Volume groups only. If there are one or more volume groups attached to the virtual

machine that you are restoring, you can choose to restore the volume groups togetherwith the virtual machine if they were attached to it at backup time. In this case, theoriginal volume groups are deleted and the restored ones are automatically attached tothe restored virtual machine as well as all other virtual machines to which they wereattached at backup time.


57

l Only if restoring a virtual machine that has the Backup from replica policy option enabled tothe original location. Depending on whether the original virtual machine is running on aNutanix AHV or ESXi cluster, consider the following when restoring its data:o Nutanix AHV cluster: A restore is performed from the snapshot only if the snapshot

is available on the original location (the cluster on which the original virtual machineis running). Otherwise, a restore is performed from the target.

o Nutanix ESXi cluster: A restore is performed from the target.



Procedure1. In the Virtual Machines panel, click the virtual machine that you want to restore.

2. In the Details section that appears at the bottom of the screen, select the desiredrestore point.

n Note The Details section appears only if you click a virtual machine. Selectingthe check box before the name of the virtual machine will not open the Detailssection.

3. ClickRestore VM or vDisks.

4. Select Restore VM, and then click Next.

5. From the Storage container drop-down menu, select where you want to restore thevirtual machine.

n Note By default, the original storage container is selected. If you decide torestore the virtual machine to another storage container, it will not be restored fromthe snapshot, but from the target. Therefore, no fast restore will be performed.

6. Use the Power virtual machine on switch if you want to turn the restored virtualmachine on after the restore. The original virtual machine will be deleted automatically.

7. From the Restore instance drop-down menu, select which restore instance you want touse for a restore. Your restore point can contain one or more restore instances amongwhich you can select:

l Automatic: This type of restore ensures the fastest restore to the latest state.

l Backup

l Copy

l Archive

l Snapshot (Nutanix clusters only)

8. Only if volume groups are attached to the virtual machine. Use the Restore volume groupsswitch if you want to restore also the volume groups that are attached to the virtualmachine.

9. Click Restore.


58

n Note Nutanix ESXi clusters only. Because the minimum RAM required for restoring avirtual machine is 256 MiB, any virtual machine with less RAM is automatically set to 256MiB during the restore.

Cloning a virtual machineYou can create a clone of the original virtual machine by restoring it to its original or a newlocation. In this case, the original virtual machine will not be overwritten.

LimitationvSphere environments only. Attaching the ISO image to the restored virtual machine is notsupported.

Considerationsl Volume groups only. If there are volume groups attached to the virtual machine that you

are restoring by creating its clone, you can choose to restore the volume groupstogether with the virtual machine if they were attached to it at backup time. In this case,the original volume groups are kept alongside the restored ones. If the volume groupsare at the same time also attached to other virtual machines, the following applies(depending on how they are attached to the virtual machines):o Directly: Volume groups are automatically attached only to the cloned virtual

machine.

o By using iSCSI: Volume groups are automatically attached to all virtual machines towhich they were attached at backup time.

l Only if restoring a virtual machine that has the Backup from replica policy option enabled.Depending on whether the original virtual machine is running on a Nutanix AHV or ESXicluster, consider the following when restoring its data:o Nutanix AHV cluster: If restoring a virtual machine to the original location, a restore

is performed from the snapshot only if the snapshot is available on the originallocation (the cluster on which the original virtual machine is running). Otherwise, arestore is performed from the target. If restoring a virtual machine to the centralsite, a restore is performed from the target.




Procedure1. In the Virtual Machines panel, click the virtual machine that you want to restore.


n Note The Details section appears only if you click a virtual machine. Selecting


59

the check box before the name of the virtual machine will not open the Detailssection.


4. Select Clone VM, and then click Next.


n Note Virtual machines only. By default, the original storage container is selected.If you decide to restore the virtual machine to another storage container, it will notbe restored from the snapshot, but from the target. Therefore, no fast restore willbe performed.

6. In the New VM name field, specify a new name for the virtual machine.

7. Use the Power virtual machine on switch if you want to turn the restored virtualmachine on after the restore. If you turn the restored virtual machine on, the originalvirtual machine will be turned off automatically.

i Important This option is disabled for virtual machines that have volumegroups attached by using iSCSI. For details on what needs to be done beforeturning on the restored virtual machine, see “After cloning a virtual machine” below.



l Backup

l Copy

l Archive


9. Only if volume groups are attached to the virtual machine. Use the Clone volume groupsswitch if you want to restore also the volume groups that are attached to the virtualmachine.

10. Click Restore.

After cloning a virtual machineAfter cloning a virtual machine, consider the following:

l Nutanix clusters only. If you restored a virtual machine to another source, make sure toadd a network adapter to the virtual machine afterward. For details on how to do this,see Nutanix documentation.

l vSphere environments only. Some operating systems (for example, RHEL 7) might requirenetwork configuration. For details, see VMware documentation.


60

l Only for virtual machines to which volume groups are attached by using iSCSI. Because theoriginal virtual machine and the restored one have the same network and iSCSIconfiguration settings after the restore, make sure both the virtual machines are notturned on at the same time to avoid any potential issues. As one way of preventingissues, you can disconnect the restored virtual machine from the network beforeturning it on and make the required changes such as replacing the network adapterand updating the iSCSI settings on it.

l Only if you plan to clone a physical machine to a virtual machine running on a Nutanix ESXicluster. Make sure to modify the machine configuration after the restore by specifyingthe appropriate Guest OS (Windows) and to install the latest version of VMware Toolson the machine. For detailed information, see VMware documentation.

Restoring virtual disksYou can restore virtual disks to their original or a new location. In this case, the originalvirtual disks will be overwritten.

LimitationRestoring physical machine disks by using the Restore vDisks option is not supported.

ConsiderationThe original virtual disks are deleted and the restored ones are automatically attached to allvirtual machines to which they were attached at backup time.



Procedure1. In the Virtual Machines panel, click the virtual machine whose virtual disks you want to

restore.




4. Select Restore vDisks, and then click Next.

5. From the list of virtual disks that are available for a restore, select the ones that youwant to restore, and then click Next.

i Important Volume groups only. You cannot select individual disks, but only thewhole volume group.


61

6. From the Storage container drop-down menu, select where you want to restore thevirtual disks.

n Note By default, the original storage container is selected. If you decide torestore the virtual disks to another storage container, they will not be restored fromthe snapshot, but from the target. Therefore, no fast restore will be performed.



l Backup

l Copy

l Archive


8. Click Restore.

Cloning virtual disksYou can create clones of virtual disks by restoring them to their original or a new location.In this case, the original virtual disks will not be overwritten.

LimitationsRestoring vSphere virtual machine disks by using the Clone vDisks option is not supported.

Considerationsl Volume groups only. The original volume groups are kept alongside the restored ones

and the following applies regarding their attachment:

o If you are restoring the volume groups to the original virtual machine, they areattached to all the virtual machines to which they were attached at backup time.

o If you are restoring the volume groups to a virtual machine other than originalrunning on a Nutanix AHV cluster, they are attached only to the selected virtualmachine. If you are restoring the volume groups to a virtual machine other thanoriginal running on a Nutanix ESXi cluster, you must attach them manually after therestore.

The name format of the cloned volume groups is as follows:

<OriginalVGName>-<Timestamp>

l Virtual machine disks only.

o The original virtual machine disks are kept alongside the restored ones that areautomatically attached to the virtual machine as the first available interface index(per interface type). For example, if you have the scsi.0, scsi.1, and scsi.4 virtualdisks already attached to your virtual machine, the restored one will be scsi.2.


62

o If the bus type of the original virtual disks is IDE, it is automatically changed to SCSIduring the restore.




restore.




4. Select Clone vDisks, and then click Next.


i Important Volume groups only. You cannot select individual disks, but only thewhole volume group.

6. From the VM drop-down menu, select the virtual machine to which you want to attachthe restored virtual disks. The restored virtual disks can be attached to the originalvirtual machine (the default selection) or any other virtual machine. Consider thefollowing:

l If you are attaching the virtual disks to the original virtual machine, make sure it isturned on.

l You cannot attach the restored disks to a physical machine.

i Important If you are attaching the virtual disks to the original virtual machine,make sure it is turned on.

7. From the Storage container drop-down menu, select where you want to restore thevirtual disks.

n Note Virtual machines only. You can select only among the storage containersthat are created on the Nutanix cluster on which the selected virtual machineresides.



l Backup


63

l Copy

l Archive


9. Click Restore.

Exporting virtual disksYou can restore virtual disks to an NFS or SMB share.

PrerequisiteOnly if restoring virtual disks to an SMB share. The SMB server is configured to stop creatingsparse files (the strict allocate parameter is set to yes in the smb.conf file).

ConsiderationOnly if restoring a virtual machine that has the Backup from replica policy option enabled to theoriginal location. Depending on whether the original virtual machine is running on a NutanixAHV or ESXi cluster, consider the following when restoring its data:

l Nutanix AHV cluster: A restore is performed from the snapshot only if the snapshot isavailable on the original location (the cluster on which the original virtual machine isrunning). Otherwise, a restore is performed from the target.

l Nutanix ESXi cluster: A restore is performed from the target.




restore.




4. Select Export vDisks, and then click Next.

i Important During the restore of virtual disks, you cannot perform additionalrestores or expire backups for this virtual machine.


6. From the Type drop-down menu, select where you want to restore the virtual disks,


64

and then provide the required information:

l SMB

a. Optional. Enter the domain and user credentials.

b. Enter the SMB server name or IP address and the path to the SMB shared folderfrom the root of the server (for example, /backups/HYCU).

l NFS

Enter the NFS server name or IP address and the path to the NFS shared folderfrom the root of the server (for example, /backups/HYCU).



l Backup

l Copy

l Archive


8. Click Restore.

After exporting virtual disksAfter the restore of the virtual disks is complete, you can upload them to the Nutanix imageservice (for Nutanix AHV clusters) or to the VMware datastore (for Nutanix ESXi clusters andvSphere environments) and create a new virtual machine by using them. You do not needHYCU to create a virtual machine from the restored virtual disks.

n Note Keep in mind that due to features such as data resiliency and provisioning,the virtual disks may require more space than on the shared location. Therefore, makesure to reserve enough space in the storage container. For details on how to do this,see Nutanix or VMware documentation.

Data is restored to the following location:

/<SharedPath>/<VMName>/<Timestamp>/<Filename>

In this instance, <SharedPath> is the path to the shared folder, <VMName> is the virtualmachine name, <Timestamp> is the time of the restore, and <Filename> is the virtualmachine disk UUID.

To create a new virtual machine by using the restored virtual disks, use one of the followingprocedures:

l “Recreating a virtual machine by using restored virtual disks on the Nutanix AHV cluster”on the next page

l “Recreating a virtual machine by using restored virtual disks on the Nutanix ESXi clusterand in the vSphere environment” on the next page


65

Recreating a virtualmachine by using restored virtual disks on theNutanixAHV clusterDepending on whether the virtual machine you want to recreate is present in the list ofvirtual machines on the source, select one of the following procedures to attach therestored virtual disks to the virtual machine:

l Virtual machine is present on the source:

1. Log on to the Nutanix Prism web console.

2. Upload the disk image and files to the image service by using the Nutanix Prismweb console. When uploading the disk image files, make sure to specify the DISKimage type.

3. Shut the virtual machine down.

4. Remove the old disks from it.

5. Add new disks based on the disk image files you uploaded.

6. Click Power on to turn on the virtual machine.

l Virtual machine is not present on the source:


2. Upload the disk image files to the image service by using the Nutanix Prism webconsole. When uploading the disk image files, make sure to specify the DISK imagetype.

3. Create a new virtual machine based on the disk image files you uploaded.

4. Click Power on to turn on the new virtual machine.

5. Configure the network settings for the new network interface that was assigned tothe virtual machine. You can edit the network connection by using the nmtui tool.Make sure to enter the original IP address of the virtual machine.

n Note After editing the connection, delete the old network interface.

Recreating a virtualmachine by using restored virtual disks on theNutanixESXi cluster and in the vSphere environment

n Note Keep in mind that some specific steps are required depending whether thevirtual machine was backed up in the environment with the same or a differenthypervisor. For the vSphere environment, different hypervisors are Nutanix AHV andNutanix ESXi clusters. For Nutanix ESXi cluster, different hypervisors are Nutanix AHVand vSphere environments .

Depending on whether the virtual machine you want to recreate is present in the list ofvirtual machines on the source, select one of the following procedures to attach therestored virtual disks to the virtual machine:


66

l Virtual machine is not present on the source:

1. Create a new virtual machine.

2. Upload all the restored virtual disks and the .vmdk file to the target datastore onyour Nutanix ESXi cluster or in your vSphere environment.

n Note Make sure not to change the file names after upload.

3. Only if the virtual machine was backed up in the environment with the same hypervisor.On the target, take note of the .vmdk file, and then append the -flat.vmdk

extension to the raw data file with the same name.

4. Only if the virtual machine was backed up in the environment with a different hypervisor.Convert the raw disk image file, and then clone it:

a. Convert the raw disk image file to the vmdk format by running the followingcommand from the folder where the disk image file is located:

qemu-img convert -f raw -O vmdk <SourceDiskImage><TargetDiskImage>.vmdk

b. Clone the existing disk image file into a thin-provisioned disk image file byrunning the following command:

vmkfstools -i <SourceDiskImage>.vmdk -d thin<TargetDiskImage>.vmdk

5. Add the restored virtual disks to the virtual machine.

6. Power the virtual machine on.

l Virtual machine is present on the source:

1. Upload all the restored virtual disks and the .vmdk file to the target datastore onyour Nutanix ESXi cluster or in your vSphere environment.

n Note Make sure not to change the file names after upload.

2. Only if the virtual machine was backed up in the environment with the same hypervisor.On the target, take note of the .vmdk file, and then append the -flat.vmdk

extension to the raw data file with the same name.

3. Only if the virtual machine was backed up in the environment with a different hypervisor.Convert the raw disk image file, and then clone it:

a. Convert the raw disk image file to the vmdk format by running the followingcommand from the folder where the disk image file is located:

qemu-img convert -f raw -O vmdk <SourceDiskImage><TargetDiskImage>.vmdk

b. Clone the existing disk image file into a thin-provisioned disk image file by usingthe following command:


67

vmkfstools -i <SourceDiskImage>.vmdk -d thin<TargetDiskImage>.vmdk

4. Remove the old disks and save configuration.

5. Add the restored virtual disk files to the virtual machine.

6. Power the virtual machine on.

For details on how to perform specific actions in your vSphere environment, see VMwaredocumentation.

Restoring individual filesYou can restore individual files to their original or another location, or to an SMB share. Thisalternative to restoring an entire virtual machine allows you to restore only one or morefiles that have become corrupted or have been deleted for some reason and are nowmissing on the virtual machine.

Prerequisites

Windows virtual machines

l The NTFS, FAT, or FAT32 file system is used.

l For improved restore performance, the startuptype of the Microsoft iSCSI Initiator Service is notset to Disabled.

l Only if restoring files to the original virtual machine.The following prerequisites are fulfilled:

o Applicable to Windows 7 andWindows Server2008 R2 virtual machines. WindowsPowerShell 3.0 is installed.

o Applicable to Windows 7, 8, and 10, andWindows Server 2008 R2 virtual machines.WinRM is enabled and configured by usingthe winrm quickconfig command.

o A Windows operating system user accountexists that has WinRM permissions grantedand is a member of the virtual machine'slocal Administrators group.

Linux virtual machines

l The FAT32, xfs, ext4/ext3/ext2, reiserfs, or btrfsfile system is used.

l References in the /etc/fstab systemconfiguration file entries use universally uniqueidentifiers (for example, UUID=8ff089c0-8e71-4320-a8e9-dbab8f18a7e5) rather than device


68

names (for example, /dev/sda1) unless theentries refer to logical volumes (for example,/dev/mapper/ol-root).

Nutanix ESXi clusters

l Only if restoring files to the original virtual machine.The latest versions of VMware Tools and NGT areinstalled on the client virtual machine.

For detailed information about installing VMwareTools, see VMware documentation. For detailedinformation about installing NGT, see Nutanixdocumentation.

vSphere environments

l At least one NFS, SMB, or iSCSI target is availableon the HYCU backup controller.

l You have the required restore privilegesassigned. For details, see “Assigning privileges toa vSphere user” on page 177.

Physical machines

At least one Nutanix cluster is added to HYCU toprovide a storage container for storing the restoredata. For details on how to add a Nutanix cluster toHYCU, see “Adding a Nutanix cluster” on page 25.

Limitationsl Performing a file-level restore on dual-boot systems is not supported.

l On Linux, a file-level restore of symbolic links and soft links is performed only whenrestoring to the original location.

l Restoring files from the same snapshot simultaneously by two different users is notpossible.

l Only when restoring files to a local machine. You can download an archive which size isequal or less than 4 GB.

Considerationsl You cannot perform a restore of a virtual machine whose retention period specified in

the policy has been exceeded (such restore points are grayed out in the HYCU web userinterface). However, if required, this can be overridden by setting therestore.enabled.if.retention.is.up configuration setting in the HYCUconfig.properties file to true. For details on how to customize the HYCUconfiguration settings, see “Customizing HYCU configuration settings” on page 188.

l Only if restoring files to the original location. To be able to restore some types of files (forexample, system files), the account you specify to access a virtual machine must be amember of the virtual machine's local Administrators group on Windows or have rootpermissions on Linux.


69

l Only if using the Backup from replica option. When restoring to the central o remote site(original location), a restore is always performed from the snapshot on the central site.



Procedure1. Only if restoring files to the original virtual machine. Provide access to files by assigning

credentials to the virtual machine:

a. Select the virtual machine that contains files you want to restore.

b. ClickCredentials. The Credential Groups dialog box appears.

c. ClickNew.

d. Enter the credentials that are required for accessing the virtual machine.

e. Click Save.

f. Click Assign.

2. Click the virtual machine that contains the files that you want to restore to open theDetails section.



4. Depending on whether the snapshot for the selected restore point is online, do one ofthe following:

l If the snapshot is online, theRestore Files option is available and you can startthe procedure for restoring the files by clicking it.

l If the snapshot is not online, you first need to prepare the files for the restore:

a. ClickPrepare for Restore Files.

b. Use the Restore with original settings switch if you want to restore data withoriginal settings.

If you choose to use different settings for restoring data, select a storagecontainer.

i Important If you are restoring individual files residing on a physicalmachine, the Restore with original settings switch is disabled and you mustalways specify a storage container.

c. From the Restore instance drop-down menu, select which restore instance youwant to use for a restore. Your restore point can contain one or more restoreinstances among which you can select:


70

o Automatic: This type of restore ensures the fastest restore to the lateststate.

o Backup

o Copy

o Archive

o Snapshot (Nutanix clusters only)

d. Click Prepare.

TheRestore Files option becomes available and you can start the procedure forrestoring the files by clicking it.

5. In the Restore Files dialog box, from the list of available files, select the ones that youwant to restore, and then click Next.

t Tip If there are too many files to be displayed on one page, you can movebetween the pages by clicking and.

You can also search for a file or a folder by entering its name and then pressingEnter in the Search field.

6. Select where you want to restore the files:

Original virtualmachine

To restore the files to the original virtual machine, follow thesesteps:

a. Select Restore to virtual machine, and then click Next.

b. Select the location on the virtual machine where you wantto restore the files, and provide the required information:

l Original location

Select how the restore should save the files when thereis a file with the same name and location on the virtualmachine (overwrite the file, rename the original file, orrename the restored file).

l Alternate location

Specify the path to an alternate location on the samevirtual machine in the following format:

C:\<Path>

c. Use the Restore ACL switch if you want to restore theoriginal access control list.

i Important If the original virtual machine is notaccessible due to various reasons (for example,credentials are not assigned to it, discovery was notsuccessful, or it is turned off or deleted from the


71

source), you cannot select it for restoring the individualfiles.

d. Click Restore.

Share

To restore the files to an SMB or NFS share, follow these steps:

a. Select Restore to fileshare, and then click Next.

b. SelectNFS or SMB for the share type, and then specify thepath to a shared folder in the following format:

\\server\<Path>

c. For SMB only. Optionally, provide user credentials to accessthe SMB share.

d. Click Restore.

Local machine

To save an archive of the selected files locally, follow thesesteps:

a. SelectDownload, and then click Next.

b. Click Download.

n Note Make sure not to reload the current page orlog out from the domain before the download processis finished.

72

Protecting applicationsHYCU enables you to protect your application data with fast and reliable backup andrestore operations. After you enable HYCU to access an application running on a virtualmachine, complete the required preparatory steps, and back up the application, you canchoose to restore either the whole application or only specific application items.

n Note The instructions for protecting applications residing on virtual machinesapply also to applications residing on physical machines except where specifically statedotherwise.

Limitationsl On physical machines, HYCU can discover and protect only SQL Server applications.

l HYCU can be used for protecting SQL Server applications running on physical machinesonly if it at least one Nutanix cluster is added to HYCU.

For details on how to protect application data efficiently, see the following sections:

l “Enabling access to application data” below

l “Planning your application backups” on page 75

l “Backing up applications” on page 78

l “Restoring a whole application” on page 79

l “Restoring SQL Server databases” on page 84

l “Restoring Exchange Server databases, mailboxes, and public folders” on page 87

l “Restoring Oracle database instances and tablespaces” on page 89

Enabling access to application dataBefore you can start protecting application data, you must enable HYCU to accessapplications running on virtual machines. HYCU can discover the following types ofapplications:

l SQL Server

l Active Directory

n Note The following roles are supported for Active Directory: Active DirectoryDomain Services, Active Directory Lightweight Directory Services, Active Directory

Chapter 5

5 Protecting applications

73

Certificate Services, Active Directory Federation Services, and Active Directory RightsManagement Services.

l Exchange Server

l Oracle

l SAP HANA

The following SAP HANA configuration is supported:

o SAP HANA savepoints are enabled.

o Multiple volume groups only. All data volumes belong to the same volume group, andalso all log volumes belong to the same volume group.

i Important HYCU can discover only SQL Server applications running on physicalmachines.

For a list of supported application versions, see the HYCU Compatibility Matrix.

Prerequisites

Windows virtualmachines

l On Windows 7 and Windows Server 2008 R2: WindowsPowerShell 3.0 is installed and the Windows PowerShell ScriptExecution Policy (Set-ExecutionPolicy) is set to RemoteSigned.

l On Windows 7, 8, and 10, and Windows Server 2008 R2: WinRM isenabled and configured by using the winrm quickconfig

command.

l A Windows user account with WinRM permissions exists. Thisaccount should have access to the application and be a memberof the virtual machine's local Administrators group.

Nutanix ESXiclusters

VMware Tools and NGT are installed on the client virtual machine.

For detailed information about installing VMware Tools, see VMwaredocumentation. For detailed information about installing NGT, seeNutanix documentation.

Oracle-specific considerationsl When an operating system is used to authenticate Oracle database users, the Oracle

database can be accessed with the OS user credentials, which allows you to skip theprocedure of providing access to application data. To enable such authenticationmode, contact the Oracle database administrator.

l The OS user must have sudo privileges.

SQL Server failover cluster considerationAccess should be enabled on all virtual machines where the SQL Server failover clusterinstance resides.


74

Procedure1. Assign credentials to virtual machines on which applications you want to back up are

running:

a. In the navigation pane, click Virtual Machines.

b. In the Virtual Machines panel, select virtual machines on which applications youwant to back up are running.

c. ClickCredentials. The Credential Groups dialog box appears.

d. ClickNew.

e. Enter a name for the credential group and credentials that are required foraccessing the virtual machines.

f. Click Save.

g. Click Assign.

The process of application discovery starts automatically after you assigncredentials to virtual machines. When the application discovery job completes, thediscovered applications are listed in the Applications panel. Depending on theDiscovery status of the applications, do one of the following:

Green

HYCU can access the discovered applications that you want to protectwith the virtual machine credentials and you can start protecting suchapplications. For instructions, see “Backing up applications” on page 78.

n Note Access to Active Directory and SAP HANA is always grantedwith the virtual machine credentials.

Red

The virtual machine credentials do not have proper permissions toaccess any of the discovered applications that you want to protect. Forsuch applications, you must assign specific credentials with permissionsto access them. In this case, continue with this procedure.

2. Only if the Discovery status is red. Assign credentials to applications:

a. In the navigation pane, click Applications.

b. In the Applications panel, select which applications you want to back up.

c. ClickConfiguration. The Configuration dialog box appears.

d. In the Credentials section, use the switch to enable using operating systemcredentials with enough permissions to access the applications.

e. Enter credentials for a user account with required permissions and access to theapplications. Make sure the following requirements are met:

l For applications running on Windows virtual machines. The specified account mustbe a member of the virtual machine's local Administrators or Backup Operatorsgroup.


75

l SQL Server only. The specified account must have the sysadmin role on theSQL Server application instance. The SQL Server account that connects by usingSQL Server Authentication is not supported.

l Exchange Server only. The specified account must be a member of theOrganization Management role group and have the default permissionsenabled.

f. Click Save.


l Edit any of the existing virtual machine credentials. To do so, clickEdit, make therequired modifications, and then click Save.

i Important After you click Save, a new process of application discovery isstarted with the modified credentials for all virtual machines that have thesecredentials assigned. Therefore, you do not need to perform any additionalassignments.

l Delete the virtual machine credentials that you do not need anymore by clickingDelete.

l Unassign the virtual machine credentials from a credential group by clicking Unassign.

i Important You can unassign or delete credentials from a virtual machine only ifthe discovered applications running on it do not have assigned policies or availablerestore points. Therefore, before unassigning or deleting credentials, make sure tounassign policies or mark restore points as expired.

Planning your application backupsBefore performing an application backup, consider prerequisites, limitations, andapplication-specific options to determine if your environment is ready for application dataprotection.

Prerequisitesl vSphere environments only. VMware Tools of the latest version is installed on virtual

machines on which the applications you want to protect are running.

l Physical machines only.

o The VSS service is enabled and running, and the VSS writer status is stable.

o WinRM is enabled and configured by using the winrm quickconfig command.

l Application-specific prerequisites are met:

SQL Server

o Databases reside on the local disks in the Nutanix environment.

o If you plan to restore an SQL Server database to a point in time. Thedatabase is online and is set to the full or bulk-logged recovery


76

model during the backup.

o If you plan to restore databases that are part of an AlwaysOnAvailability Group. Either all nodes in the AlwaysOn AvailabilityGroup are protected by HYCU or only the node with thesynchronized databases of the AlwaysOn Availability Group(must be online when being protected). In the latter case, therisk of data loss is increased if the node goes offline or thedatabases get out of sync.

SQL Server failover cluster only. All virtual machines where aSQL Server failover cluster resides are discovered by HYCU.

Active Directory

o NGT is installed and enabled on the client virtual machine. Fordetails on how to do this, see Nutanix documentation.

o No volume groups are attached to the client virtual machine.

ExchangeServer

o NGT is installed and enabled on the client virtual machine. Fordetails on how to do this, see Nutanix documentation.

o No volume groups are attached to the client virtual machine.

o All databases are mounted.

o The Active Directory application is protected.

Because Exchange Server stores all configuration information inActive Directory, make sure that you also back up your ActiveDirectory application so that you can retrieve the informationabout the configuration if required. For example, if an entiredatabase is deleted by accident and you want to restore it, youfirst need to restore the Active Directory application, and thenyou can restore this database by performing the ExchangeServer restore. However, if only the contents of the database isdeleted, you need to restore only the Exchange Serverapplication.

Oracle

o The SSH service is enabled on the Oracle server and is listeningon port 22, which is open for incoming connections.

o Tablespaces are online.

SAP HANAo Distributed (multi-host) environments only. All virtual machines

where SAP HANA resides are discovered by HYCU.

Limitations

SQL Server

l The tempdbSQL Server system database is excluded from allbackups.

l Only a full backup of the master, model, and msdbSQL Server


77

system databases is supported. You can restore an SQL Serversystem database only as a whole instance.

l A point-in-time restore of the master, model, msdb, ortempdbSQL Server system database is not possible.

l Backing up a database that is set to single-user mode is notpossible if it is already in use.

Active Directoryl Nutanix clusters only. Protecting applications that are running on

virtual machines with IDE disks is not possible.

Exchange Server

l Nutanix clusters only. Protecting applications that are running onvirtual machines with IDE disks is not possible.

l vSphere environments only. Log files are not truncated after abackup.

Oraclel Backing up Oracle Real Application Clusters (RAC) databases is not

supported. Consequently, assigning policies to such databases isnot possible.

Application-specific optionsHYCU enables you to set several application-specific options before you start backing upyour applications. By doing so, you make sure the actions specified by these options areperformed automatically as part of the application backup.

Accessing the Configuration dialog boxTo access the Configuration dialog box, follow these steps:

1. In the navigation pane, click Applications.

2. From the list of discovered applications, select the one for which you want to specifythe application-specific option, and then clickConfiguration.

The following application-specific options are available:

SQL Server

Back up and truncate SQL transaction logs (enabled by default)

Use the switch if you want your SQL Server transaction logs to bebacked up and truncated in the SQL Server database automatically aspart of the HYCU application backup. In this case, you can use HYCU torecover the SQL Server database.

If disabled, HYCU does not back up and truncate the SQL Servertransaction logs. In this case, to recover the SQL Server database, youshould apply the transaction logs manually after restoring data.

Exchange ServerPriority for Exchange Server restore requests

Specifies the priority in which the restore requests for a mailbox


78

restore are processed on the Exchange Server: Lowest, Lower, Low,Normal (the default value), High, Higher, Highest, Emergency.

Oracle

Back up and truncate Oracle archive logs (enabled by default)

Use the switch if you want your Oracle archive logs to be backed upand truncated in the Oracle database automatically as part of the HYCUapplication backup. In this case , you can use HYCU to recover theOracle database.

If disabled, HYCU does not back up and truncate the Oracle archivelogs. In this case, to recover the Oracle database, you should apply thetransaction logs manually after restoring data.

Backing up applicationsAn application-aware backup allows a consistent backup of the SQL Server, Active Directory,Exchange Server, Oracle, and SAP HANA applications.

Prerequisitesl SQL Server failover cluster and SAP HANA multi-host environments only. Policies are assigned

to all virtual machines on which application instance is running.

l Nutanix ESXi clusters and if using the Backup from replica option only. If besides HYCU youuse a Nutanix protection domain to protect virtual machines, you can perform anapplication-consistent backup of the applications running on such virtual machines. Todo so, make sure that the virtual machines where the applications reside have NGTinstalled and enabled, and that your protection domain is configured to createapplication-consistent snapshots. For instructions on how to do this, see the Nutanixdocumentation.

l Linux virtual machines with the installed NGT only. The following scripts are available onthe system, are owned by root, and have permissions set to 0700:/usr/local/sbin/pre_freeze

/usr/local/sbin/post_thaw

Limitationl You cannot back up the Active Directory and Exchange Server applications running on

the volume groups or on the virtual machines with the attached volume groups.

l Nutanix ESXi clusters and if using the Backup from replica option only. Backing up virtualmachines that have disks on different containers is not supported.

l Nutanix AHV clusters only. With a Nutanix protection domain configured with NearSync,HYCU can create snapshots only if the AOS version is 5.9 or higher.


79

Considerationsl HYCU enables you to back up multiple applications running on a virtual machine in a

single virtual machine backup job. This is supported for virtual machines runningmultiple SQL Server applications, multiple Oracle applications, or the Active Directoryand Exchange Server applications. When protecting multiple applications, you mustassign a policy to each application that you want to be included in the virtual machinebackup.

l Nutanix ESXi clusters only. If a full backup snapshot is missing on a Nutanix cluster (forexample, because the HYCU protection domain is deleted from Prism), the next backupwill be a full backup.

l Only if a protection domain is configured with NearSync. Although snapshots in aprotection domain are created in a 1–15 minute interval, HYCU uses only the snapshotsthat are created on an hourly basis for backing up and restoring from snapshots. Thisapplies to the following environments:o Nutanix ESXi clusters

o Nutanix clusters when using the Backup from replica option

Accessing the Applications panel

To access the Applications panel, in the navigation pane, click Applications.

Procedure1. In the Applications panel, select applications that you want to back up.

t Tip To narrow down the list of all displayed applications, you can use thefiltering options described in “Filtering data” on page 117.

2. ClickPolicies. The Policies dialog box appears.


4. Click Assign to assign the policy to the selected applications.

n Note When you assign the policy to the selected applications, the same policyis also assigned to the virtual machines on which they are running. If these virtualmachines already have an assigned policy, the policy assigned to the applicationstakes precedence over the policy assigned to the virtual machines and isautomatically assigned to the virtual machines.

The backup is scheduled according to the values that you defined for your policy. Ifrequired, you can also perform a manual backup of any application at any time. For details,see “Performing a manual backup” on page 128.

Restoring a whole applicationWith HYCU, you can restore a whole application to its original or a new location by restoringthe virtual machine and attached volume groups on which the application is running.


80

n Note Active Directory only. HYCU does not perform an authoritative restore.

Prerequisitesl vSphere environments only. You have the required restore privileges assigned. For details,

see “Assigning privileges to a vSphere user” on page 177.


LimitationRestoring a virtual machine running on a Nutanix ESXi cluster by using the Restore VMoption is supported only if your AOS version is 5.9 or higher.

Considerationsl You cannot perform a restore of an application whose retention period specified in the

policy has been exceeded (such restore points are grayed out in the HYCU web userinterface). However, if required, this can be overridden by setting therestore.enabled.if.retention.is.up configuration setting in the HYCUconfig.properties file to true. For details on how to customize the HYCUconfiguration settings, see “Customizing HYCU configuration settings” on page 188.

l SQL Server only. If you disabled the Back up and truncate SQL transaction logs option,you should apply transaction logs manually after restoring data to recover theSQL Server database.

l Oracle only. If you disabled the Back up and truncate Oracle archive logs option, youshould apply archive logs manually after restoring data to recover the Oracle database.

l SQL Server failover cluster and SAP HANA multi-host environments only. Make sure to selectthe virtual machine with the latest backup of attached volume groups. To identify theappropriate virtual machine, you can use the Jobs panel. For details, see “Checking thestatus of jobs” on page 107.

Restore optionsYou can select between the following restore options:


Restore VM

Enables you to restore an application by restoring the virtual machineon which it is running to its original or a new location with the sameconfiguration settings. Select this option if you want to replace theoriginal virtual machine on which your application is running with therestored one. For instructions, see “Restoring a virtual machine” on thenext page.

i Important You cannot restore an SQL Server application


81


running on a physical machine by using this option.

Clone VM

Enables you to create a clone of the original machine by restoring it toits original or a new location with different configuration settings. Selectthis option if you want to keep the original virtual machine on whichyour application is running. For instructions, see “Cloning a virtualmachine” on page 83.

Restoring a virtual machineHYCU enables you to restore an application by restoring the virtual machine on which it isrunning to its original or a new location with the same configuration settings.

C Caution When you are restoring the application to the original location, therestored data overrides the data in the original location. To avoid data loss, make surethat you back up the potentially unprotected data—the data that appeared between thelast successful backup and the restore. To start a manual backup, see “Performing amanual backup” on page 128.

LimitationRestoring SQL Server applications running on physical machines by using the Restore VMoption is not supported.

Considerationsl Volume groups only. If there are one or more volume groups attached to the virtual

machine that you are restoring, you can choose to restore the volume groups togetherwith the virtual machine if they were attached to it at backup time. In this case, theoriginal volume groups are deleted and the restored ones are automatically attached tothe restored virtual machine as well as all other virtual machines to which they wereattached at backup time.

l Only if restoring a virtual machine that has the Backup from replica policy option enabled tothe original location. Depending on whether the original virtual machine is running on aNutanix AHV or ESXi cluster, consider the following when restoring its data:o Nutanix AHV cluster: A restore is performed from the snapshot only if the snapshot

is available on the original location (the cluster on which the original virtual machineis running). Otherwise, a restore is performed from the target.





82

Procedure1. In the Applications panel, click the application that you want to restore to open the

Details section.

n Note The Details section appears only if you click an application. Selecting thecheck box before the name of the application will not open the Details section.

2. In the Details section that appears at the bottom of the screen, select the desiredrestore point, and then clickRestore.

i Important If the backup status for the selected restore point shows that thebackup is crash consistent, you cannot use this restore point for restoring theapplication.

3. Select Restore whole server, and then click Next.



n Note By default, the original storage container is selected. If you decide torestore the virtual machine to another storage container, it will not be restored fromthe snapshot, but from the target. Therefore, no fast restore will be performed.

6. Use the Power virtual machine on switch if you want to turn the restored virtualmachine on after the restore. The original virtual machine will be deleted automatically.



l Backup

l Copy

l Archive


8. Only if volume groups are attached to the virtual machine. Use the Restore volume groupsswitch if you want to restore also the volume groups that are attached to the virtualmachine.

9. Click Restore.

n Note Nutanix ESXi clusters only. Because the minimum RAM required for restoring avirtual machine is 256 MiB, any virtual machine with less RAM is automatically set to 256MiB during the restore.

During the restore, the original application instance is offline and not accessible.


83

After restoring a virtual machineAfter restoring an Exchange Server or Active Directory application, reinstall NGT to ensurethe future successful backups of application data.

Cloning a virtual machineHYCU enables you to create a clone of the original virtual machine by restoring it to itsoriginal or a new location with different configuration settings.

Considerationsl Volume groups only. If there are volume groups attached to the virtual machine that you

are restoring by creating its clone, you can choose to restore the volume groupstogether with the virtual machine if they were attached to it at backup time. In this case,the original volume groups are kept alongside the restored ones. If the volume groupsare at the same time also attached to other virtual machines, the following applies(depending on how they are attached to the virtual machines):o Directly: Volume groups are automatically attached only to the cloned virtual

machine.

o By using iSCSI: Volume groups are automatically attached to all virtual machines towhich they were attached at backup time.

l Only if restoring a virtual machine that has the Backup from replica policy option enabled.Depending on whether the original virtual machine is running on a Nutanix AHV or ESXicluster, consider the following when restoring its data:o Nutanix AHV cluster: If restoring a virtual machine to the original location, a restore

is performed from the snapshot only if the snapshot is available on the originallocation (the cluster on which the original virtual machine is running). Otherwise, arestore is performed from the target. If restoring a virtual machine to the centralsite, a restore is performed from the target.




Procedure1. In the Applications panel, click the application that you want to restore to open the

Details section.


2. In the Details section that appears at the bottom of the screen, select the desiredrestore point, and then clickRestore.

i Important If the backup status for the selected restore point shows that the


84

backup is crash consistent, you cannot use this restore point for restoring theapplication.

3. Select Restore whole server, and then click Next.



n Note Virtual machines only. By default, the original storage container is selected.If you decide to restore the virtual machine to another storage container, it will notbe restored from the snapshot, but from the target. Therefore, no fast restore willbe performed.

6. In the New VM name field, specify a new name for the virtual machine.

7. Use the Power virtual machine on switch if you want to turn the restored virtualmachine on after the restore. If you turn the restored virtual machine on, the originalvirtual machine will be turned off automatically.

i Important This option is disabled for virtual machines that have volumegroups attached by using iSCSI. For details on what needs to be done beforeturning on the restored virtual machine, see “After cloning a virtual machine” onpage 59.



l Backup

l Copy

l Archive


9. Only if volume groups are attached to the virtual machine. Use the Clone volume groupsswitch if you want to restore also the volume groups that are attached to the virtualmachine.

10. Click Restore.

During the restore, the original application instance is offline and not accessible.

Restoring SQL Server databasesWith HYCU, you can restore SQL Server databases to the original or a different SQL Serverinstance.


85

Prerequisitesl Point-in-time restore only. The database recovery model is set to full or bulk-logged.

l Only if restoring the whole SQL Server failover cluster instance. The SQL Server service isstopped by using the Failover Cluster Manager. For details on how to do this, seeSQL Server documentation.

l For improved restore performance, the startup type of the Microsoft iSCSI InitiatorService is not set to Disabled.


Limitationsl The restore of discovered applications is available for the NTFS, FAT, and FAT32 file

systems.

l Restoring SQL Server databases to another SQL Server application instance issupported only if you are restoring to the same or higher version of the application.

l Databases that are part of an AlwaysOn Availability Group can be restored only to aprimary node (from a secondary or primary node) and cannot be restored to a point intime.

Considerationsl If you are restoring the databases to a different SQL Server instance, they will be

renamed and copied to the default SQL Server location of the selected target.

l If a virtual machine is deleted from the source, but it still has at least one valid restorepoint available, it is considered protected. In this case, the status of the virtual machineor any discovered applications running on it is PROTECTED_DELETED. When restoringapplication items of such an application, keep in mind that you cannot restore them tothe original application instance.

l You cannot perform a restore of an application whose retention period specified in thepolicy has been exceeded (such restore points are grayed out in the HYCU web userinterface). However, if required, this can be overridden by setting therestore.enabled.if.retention.is.up configuration setting in the HYCUconfig.properties file to true. For details on how to customize the HYCUconfiguration settings, see “Customizing HYCU configuration settings” on page 188.

l SQL Server failover clusters only. Consider the following:

o The restore needs to be redirected to the active SQL Server failover cluster instance.

o The Overwrite existing databases option can be enabled for a redirected restoreonly if the database location also exists on the target virtual machine.




86

Procedure1. In the Applications panel, click the application whose databases you want to restore to

open the Details section. The Details section appears only if you click an application.Selecting the check box before the name of the application will not open the Detailssection.


i Important If the backup status for the selected restore point shows that thebackup is crash consistent, you cannot use this restore point for restoring thedatabases.

3. ClickRestore. The Restore MS SQL Server dialog box opens.

n Note If the Back up and truncate SQL transaction logs option was disabledduring the backup, you are prompted that database recovery must be performedafter the restore.

4. Select Restore databases, and then click Next.

5. From the Target instance drop-down menu, select where you want to restore thedatabases.

6. From the Destination storage container drop-down menu, select where you want torestore the databases.

7. Select the Whole instance check box if you want to restore the whole applicationinstance or, from the list of databases that are available for a restore, select the onesthat you want to restore.

8. Optional. Specify a point in time to which you want to restore data. The databases willbe restored to the state they were in at the specified time.

n Note To perform a point-in-time restore, select a backup that was performedbefore the specified point in time so that the database instance can be brought tothe appropriate state by applying the transaction log files from the next backup.

9. Click Next.

10. Use the Overwrite existing databases switch if you want to overwrite existingdatabases when performing a restore. In this case, the backups will be restored to theiroriginal location and all data will be overwritten. Keep in mind that if you are restoringthe databases to another SQL Server instance, all the databases that have the samenames (and not necessarily the contents) will be overwritten.

Otherwise, to restore data to a different location on the same or another SQL Serverinstance, specify a database prefix that will be given to the databases, a new databasefile location, and a new database log location.

i Important If you are restoring the whole instance, you can only overwriteexisting databases. In this case, the Overwrite existing databases option is enabled


87

by default and you cannot disable it.

11. Click Restore.

12. Only if the Back up and truncate SQL transaction logs option was disabled during the backup.Recover the SQL Server databases by applying the transaction logs manually.

13. SQL Server 2012 and 2014 AlwaysOn Availability Groups. Join the restored databases to anAlwaysOn Availability Group by using SQL Server Management Studio. For details onhow to do this, see Microsoft documentation.

n Note After you join the restored databases to the AlwaysOn Availability Group,it is recommended to perform a new backup of your AlwaysOn Availability Group.

14. Only if restoring the whole SQL Server failover cluster instance. Start the SQL Server serviceand all other related services by using the Failover Cluster Manager. For details on howto do this, see SQL Server documentation.

Restoring Exchange Server databases,mailboxes, and public foldersWith HYCU, you can restore Exchange Server databases, mailboxes, and public folders.When restoring Exchange Server databases, you can choose between restoring to theoriginal mailbox server and, if the mailbox server is a member of a Database AvailabilityGroup (DAG), to another mailbox server inside the DAG. When restoring mailboxes andpublic folders, the recovery database is restored to the original mailbox server. From there,the actual restore is performed to any mailbox or public folder within the organization.

Prerequisitesl Only when restoring public folders. The public folder exists in the public folder mailbox. If

it does not exist, recreate it manually with the same name it had at backup time.

l For improved restore performance, the startup type of the Microsoft iSCSI InitiatorService is not set to Disabled.

Limitationsl The restore of discovered applications is available for the NTFS, FAT, and FAT32 file

systems.

l Restoring data to the hycu subfolder (the Restore to subfolder option) is currently notsupported for public folders.

ConsiderationYou cannot perform a restore of an application whose retention period specified in thepolicy has been exceeded (such restore points are grayed out in the HYCU web userinterface). However, if required, this can be overridden by setting therestore.enabled.if.retention.is.up configuration setting in the HYCU


88

config.properties file to true. For details on how to customize the HYCU configurationsettings, see “Customizing HYCU configuration settings” on page 188.



Procedure1. In the Applications panel, click the application whose application items you want to

restore to open the Details section.



i Important If the backup status for the selected restore point shows that thebackup is crash consistent, you cannot use this restore point for restoringapplication items.

3. ClickRestore. The Restore MS Exchange Server dialog box appears.

4. Select which application items you want to restore:

l Restore databases

a. From the Destination server drop-down menu, select the server for restoringthe data. When specifying a destination server, keep in mind that you can selectit only if your mailbox server is a member of a DAG and you want to restoredata to another mailbox server inside the DAG. Otherwise, you can restore onlyto the original mailbox server.

i Important Only if your mailbox server is a member of a DAG. Make sureto select the destination server on which the databases are currently active.

b. From the Destination storage container drop-down menu, select the storagecontainer for restoring the data.

c. Select the All databases check box if you want to restore all databases or, fromthe list of databases that are available for a restore, select the ones that youwant to restore.

d. Use the Enable restore to recovery database switch if you want to enablerestoring data to a recovery database. If enabled, provide a recovery databasepath. The default one is C:\ProgramData\Hycu.

l Restore mailboxes and/or public folders

a. From the Storage container drop-down menu, select where you want to restorethe mailboxes and/or public folders.

b. From the list of mailboxes and/or public folders that are available for a restore,select the ones that you want to restore, and then click Next.


89

t Tip If there are too many mailboxes and/or public folders to bedisplayed on one page, you can move between the pages by clicking and. You can also use to set the number of mailboxes and/or publicfolders to be displayed per page.

You can search for a mailbox and/or public folder by entering its name andthen pressing Enter in the Search field.

c. Select where you want to restore data:

o Original mailbox

o Alternate mailbox, and then enter an alternate mailbox name.

d. Select the mode for restoring data:

o Restore in place

Enables you to restore data to the original location.

o Restore to subfolder (not supported for public folders)

Enables you to restore data to the hycu subfolder that is createdautomatically.

e. Only if restoring data to the original location. Use the Conflict resolution switch ifyou want to resolve any potential data conflict by keeping the most recentversion of the items in conflict. Otherwise, HYCU will overwrite the existing itemswith the ones from the backup.

f. Enter a temporary recovery database path. The default one isC:\ProgramData\Hycu.

5. Click Restore.

Restoring Oracle database instances andtablespacesWith HYCU, you can restore the whole Oracle database instance or the selected tablespacesto the original location.

Prerequisitesl On the original virtual machine, references in the /etc/fstab system configuration file

entries use universally unique identifiers (for example, UUID=8ff089c0-8e71-4320-a8e9-dbab8f18a7e5) rather than device names (for example, /dev/sda1) unless theyrefer to logical volumes (for example, /dev/mapper/ol-root).

Limitationsl Tablespaces can be restored only from the latest restore point in the backup chain and

cannot be restored to a point in time.


90

Considerationsl When performing a database instance or tablespace restore, you can perform a

complete or point-in-time restore:

o Complete restore

HYCU performs a complete restore of the whole database instance or tablespacesfrom the latest backup in the backup chain.

When performing the complete restore, the control file and archive log files are notrestored, and only existing archive log files are applied. If the control file or theexisting archive log files are lost, a complete restore is not possible and a point-in-time restore must be performed.

o Point-in-time restore

To perform a point-in-time restore, you must select a backup that was performedbefore the specified point in time so that the database instance can be brought tothe point in time by applying the archive log files from the next backup.

When performing the point-in-time restore, the control file, database files, andrequired archive log files are restored.

i Important After a successful point-in-time restore, the archive log filesare reset. Therefore, it is highly recommended to perform a backupimmediately after performing the point-in-time restore because the databasewill not be protected in terms of a complete restore until a new backup isperformed.

l You cannot perform a restore of an application whose retention period specified in thepolicy has been exceeded (such restore points are grayed out in the HYCU web userinterface). However, if required, this can be overridden by setting therestore.enabled.if.retention.is.up configuration setting in the HYCUconfig.properties file to true. For details on how to customize the HYCUconfiguration settings, see “Customizing HYCU configuration settings” on page 188.



Procedure1. In the Applications panel, click the application whose database you want to restore to

open the Details section. The Details section appears only if you click an application.Selecting the check box before the name of the application will not open the Detailssection.


i Important If the backup status for the selected restore point shows that thebackup is crash consistent, you cannot use this restore point for restoring the


91

database instance.

3. ClickRestore. The Restore Oracle Server dialog box opens.

n Note If the Back up and truncate Oracle archive logs option was disabledduring the backup, you are prompted that database recovery must be performedafter the restore.

4. Select Restore database, and then click Next.

5. Select the Whole instance check box if you want to restore the whole databaseinstance or, from the list of tablespaces that are available for a restore, select the onesthat you want to restore.

6. Whole database instance restore only. Optionally, specify a point in time to which you wantto restore data. The database instance will be restored to the state it was in at thespecified time.

7. Click Restore.

8. Only if the Back up and truncate Oracle archive logs option was disabled during the backup.Recover the Oracle databases by applying the archive logs manually.

92

Protecting file sharesHYCU enables you to protect your file share data with fast and reliable backup and restoreoperations. After you back up a file share, you can choose to restore either specific files tothe original file share or the whole file share to an external location.

For details on how to protect file share data efficiently, see the following sections:

l “Backing up file shares” below

l “Restoring file share data” on the next page

Backing up file sharesA file-share backup allows a rapid backup of file shares by using parallel backup streams.

Limitationsl The iSCSI target cannot be used for protecting file shares on the Nutanix Files server.

l Backing up from a replica is not supported for Nutanix Files. Therefore, if a policy thatyou plan to assign to file shares has the Backup from replica option enabled, thisoption will be ignored.

l Backing up file shares to cloud targets is supported if the file system item namescontain only characters in the Unicode Basic Multilingual Plane (BMP).

Considerationsl You can change the number of incremental file share backups after which a full reindex

is performed so that it suits the requirements of your environment. By doing so, youspeed up the process of searching for the relevant files when you are restoring them.For details on how to do this, see “Nutanix Files settings” on page 191.

l Nutanix Files 3.2.0 or higher only. When backing up a file share, HYCU also backs up anyfile shares that are inside the selected file share. Keep in mind that backing up nestedfile shares individually is not supported.

l Only if a particular file share folder was excluded from the backup and then included again.The next backup will be a full backup.

Accessing the Shares panel

To access the Shares panel, in the navigation pane, clickShares.

Chapter 6

6 Protecting file shares

93

Procedure1. Select the file shares that you want to back up.

t Tip You can update the list of file shares by clicking Synchronize. To narrowdown the list of displayed file shares, you can use the filtering options described in“Filtering data” on page 117.

2. Only if you want to exclude particular file share folders from the backup. ClickConfiguration, and then, in the Configuration dialog box that opens, do thefollowing:

a. In the Exclude folder path field, enter the full path (from the root of the file share) tothe file share folder that you want to exclude from the backup (for example,/backup), and then clickAdd. Repeat this step to add additional file sharefolders.

n Note The paths to all the file share folders that you excluded from thebackup are added to the Exclude folder paths list. If you want to remove any ofthem from the exclude list, clickRemove.

b. Click Save.

3. ClickPolicies. The Policies dialog box appears.


5. Click Assign to assign the policy to the selected file shares.

After you assign the policy, the backup is scheduled according to the values that youdefined for your policy. If required, you can also perform a manual backup at any time. Fordetails, see “Performing a manual backup” on page 128.

t Tip If you have more than one HYCU instance in your data protection environment,you can see which HYCU instance performed a backup by clicking the desired backupjob in the Jobs panel and checking the HYCU instance IP address in the Details section.

Restoring file share dataWhen restoring file share data, you can restore files to their original or a new location onthe original file share. You can also restore a whole file share to an external location.Depending on what you want to do, follow the instructions in one of the following sections:

l “Restoring files to the original file share” on the next page

l “Restoring a whole file share to an external location” on the next page

ConsiderationYou cannot perform a restore of a file share whose retention period specified in the policyhas been exceeded (such restore points are grayed out in the HYCU web user interface).However, if required, this can be overridden by setting therestore.enabled.if.retention.is.up configuration setting in the HYCU


94

config.properties file to true. For details on how to customize the HYCU configurationsettings, see “Customizing HYCU configuration settings” on page 188.



Restoring files to the original file shareTo restore files to the original file share, follow these steps:

1. In the Shares panel, click the file share that contains the files that you want to restore toopen the Details section. The Details section appears only if you click a file share.Selecting the check box before the name of the file share will not open the Detailssection.


3. ClickBrowse & Restore Files. The Restore Files dialog box opens.

4. In the Folders section, select the uppermost check box (the one in front of the icon)if you want to restore the whole file share. Otherwise, from the list of available foldersand files, select the ones that you want to restore. This information is entered also inthe File path field. Click Next.

t Tip If there are too many files to be displayed on one page, you can movebetween the pages by clicking and. You can also use to set the number offiles to be displayed per page.

5. Select where you want to restore the files and whether you want to restore the originalaccess control list. To do so, follow these steps:

a. Select the location on the file share where you want to restore the files:

l Original location, and then select how the restore should save the files whenthere is a file with the same name and location on the file share (overwrite thefile, rename the original file, or rename the restored file).

l Alternate location (on the same share), and then specify the path to analternate location on the same share in the following format:

/<Path>

b. Use the Restore ACL switch if you want to restore the original access control list forthe files.

6. Click Restore.

Restoring a whole file share to an external locationTo restore a whole file share to an external NFS or SMB shared location, follow these steps:


95

1. In the Shares panel, click the file share that you want to restore to open the Detailssection. The Details section appears only if you click a file share. Selecting the check boxbefore the name of the file share will not open the Details section.


3. ClickExport Share. The Restore Share dialog box opens.

4. From the Type drop-down menu, select where you want to restore the file share, andthen provide the required information:

l NFS

Enter the NFS server name or IP address and the path to the NFS shared folderfrom the root of the server (for example, /backups/HYCU).

l SMB

a. Optional. Enter the domain and user credentials.

b. Enter the SMB server name or IP address and the path to the SMB shared folderfrom the root of the server (for example, /backups/HYCU).

5. Click Restore.

i Important When restoring a whole file share to an external location, ADS andsecurity information will not be included.

96

Protecting the HYCU backupcontrollerHYCU provides functionality for recovery of the HYCU backup controller after a disaster. Forexample, if the virtual machine is deleted by accident or the hosting cluster node stopsoperating, you can successfully restore the HYCU backup controller from its backup images.Adequate protection of your HYCU backup controller is of crucial importance for highreliability and resilience of your backup environment, and therefore safety of protecteddata.

When your environment includes HYCU instances, disaster may also strike those virtualmachines. You can easily recover HYCU instances by redeploying them from theHYCU virtual appliance image and reestablishing their connections with the HYCU backupcontroller.

i Important To further increase safety, you should combine protection of HYCUbackup controller with protection of the source cluster where the HYCU backupcontroller is hosted. You can use, for example, Nutanix protection domains or VMwarevSphere Data Protection. For more information, see Nutanix or VMwaredocumentation.

To enable adequate protection for your HYCU backup environment and recover itscomponents after a disaster, complete the following procedures:

1. Back up the HYCU backup controller. For instructions, see “Backing up the HYCUbackup controller” on the next page.

n Note If you had the HYCU backup controller protected already in previousversions of HYCU, you might want to revise settings in the assigned policy due toexpanded possibilities for the HYCU backup controller protection.

2. Only if the HYCU backup controller was struck by a disaster. Do the following:

a. Restore the HYCU backup controller. For instructions, see “Restoring the HYCUbackup controller” on page 98.

b. Only if HYCU is protecting Nutanix Files servers. Reestablish connections of allHYCU instances with the HYCU backup controller. For instructions, see “RecreatingHYCU instances” on page 103.

3. Only if HYCU is protecting Nutanix Files servers and some HYCU instances were struck by a

Chapter 7

7 Protecting the HYCU backup controller

97

disaster. Recreate the affected HYCU instances. For instructions, see “Recreating HYCUinstances” on page 103.

Backing up the HYCU backup controllerAfter you deploy the HYCU virtual appliance, protect your HYCU backup controller byassigning a policy to it.

Prerequisitesl NFS, SMB, and iSCSI targets only. The target that will store backup images of HYCU backup

controller is not encrypted.

l Policy that you intend to assign to the HYCU backup controller has only one targetselected. The Copy or Archiving options are disabled in the policy.

For more information on policies, see “Defining your backup strategy” on page 42.

l Note of the selected target's configuration is taken. You will need this information whenrestoring the HYCU backup controller. The required properties depend on the targettype.

C Caution You cannot restore the HYCU backup controller if you are unable toprovide correct configuration data when importing the target for disaster recovery.

Target type Mandatory properties for importing the target

NFS NFS server name or IP address, Shared folder

SMBDomain (if used), Username (if used), Password (if used),SMB server name or IP address, Shared folder

iSCSI

Target portal, Target name, User (if CHAP authentication isenabled), Target secret (if CHAP authentication is enabled),Perform mutual authentication (if CHAP authentication isenabled)

AWS S3/CompatibleService endpoint, Bucket name, Access key ID, Secret accesskey, Path style access

AZUREStorage account name, Secret access key, Storage containername

Considerationl RPO in the policy that is assigned to the HYCU backup controller should always be

lower than any RPO already set for other protected entities in the data protectionenvironment.


98

Procedure1. In the navigation pane, click Virtual Machines.

2. From the list of virtual machines, select your HYCU backup controller, and then clickPolicies. The Policies dialog box appears.

3. Select a suitable policy for your HYCU backup controller.

4. Click Assign to assign the policy to the HYCU backup controller.

If you consider changing the target settings in the policy assigned to the HYCU backupcontroller, keep in mind the following:

l Selection of a different target starts a new backup chain and invokes a full backup.

l Note of the target's configuration must be updated after selection of a different target—to be able to restore the HYCU backup controller if needed.

Restoring the HYCU backup controllerPossible scenarios for restore of the HYCU backup controller are virtual machine restore orcloning, virtual disk restore or cloning, and virtual disk export. The only difference towardsrecovery of ordinary virtual machines is the need of setting up a new, temporary HYCUbackup controller and using that one for restore of the original HYCU backup controller.

To restore the HYCU backup controller, complete the following procedures:

1. Perform the preparation for the restore. For instructions, see “Preparing for a HYCUbackup controller restore” on the next page.

2. Restore the HYCU backup controller by using an approach that suits your environmenttype and your needs. The approach also depends on the HYCU version that theselected restore point was created with.

l Restore to the original cluster where the HYCU backup controller has resided (byusing a restore point created with HYCU version 4.0.x).

For instructions, see “Restoring the HYCU backup controller to the original location”on page 100.

l Restore to a different cluster (by using a restore point created with HYCU version4.0.x):

Sourceenvironment

Targetenvironment

Restoreoption

Additional information

Nutanix clustervSphereenvironment

ExportvDisks

For instructions, see“Exporting virtual disks” onpage 63.

n Note In restorepoints of the HYCU


99

backup controller onlythe Backup restoreinstances are available.

All other combinations of sourceand target environments

CloneVM

For instructions, see“Restoring the HYCU backupcontroller to a differentcluster” on page 101.

l Restore that uses a restore point created with an earlier HYCU version.

The restore approach is based on export of the HYCU backup controller's vDisks.For instructions, see “Exporting virtual disks” on page 63.

Preparing for a HYCU backup controller restoreBefore you start restoring the HYCU backup controller, you need to do the following:

1. Deploy a temporary HYCU backup controller that will perform the restore.

2. Import the target that stores backup images of the original HYCU backup controller.

3. Add the source where you plan to recreate your HYCU backup controller.

Prerequisitesl You know configuration parameters of the target that stores backup images of your

original HYCU backup controller.

l Target that stores backup images of the original HYCU backup controller is accessible tothe cluster where you plan to deploy a temporary HYCU backup controller.

l Only if backup images of the original HYCU backup controller are stored on an iSCSI target.The iSCSI storage device is dedicated to a single HYCU backup controller.

C Caution Disregarding this prerequisite may result in data loss or corruption.Therefore, make sure to avoid the following circumstances:o Several HYCU backup controllers are using the same target simultaneously.

o Appliances other than HYCU and HYCU itself are using the same targetsimultaneously.

Procedure1. Log on to the Nutanix Prism web console (for Nutanix AHV clusters) or the VMware

vSphere Web Client (for Nutanix ESXi clusters and VMware vSphere environments).

2. Deploy a temporary HYCU backup controller that you will use for restoring the originalHYCU backup controller. For instructions, see the corresponding section:

l For deployment to a Nutanix AHV cluster: “Deploying HYCU to a Nutanix AHVcluster” on page 17.


100

l For deployment to a Nutanix ESXi cluster or to a VMware vSphere environment:“Deploying HYCU to a Nutanix ESXi cluster or a vSphere environment” on page 20

3. Only if planning restore to a cluster different from the original. Enable creation of a clone ofthe HYCU backup controller. To do so, in the HYCU config.properties file, set theclone.enabled.for.hycu.dr configuration setting to true.

For general instructions on how to customize HYCU configuration settings, see“Customizing HYCU configuration settings” on page 188.

4. Log on to the HYCU web user interface.

5. Import the target that stores backup images of the original HYCU backup controller:

a. In the Targets panel, clickImport. The Import Target dialog box appears.

b. From the Type drop-down menu, select the type of target.

c. Specify option values and select the options so that they match the original targetconfiguration, and then click Next.

d. Select the name of the HYCU backup controller whose backup images you want toimport.

HYCU notifies you upon successful import of the target. Name of the HYCU backupcontroller appears in the list in the Virtual Machines panel.

n Note The temporary HYCU backup controller is automatically suspended afterthe target is imported.

6. Depending on the cluster that you plan to restore the HYCU backup controller to, addthe corresponding source to HYCU. For instructions, see the appropriate section foryour cluster type:

l “Adding a Nutanix cluster” on page 25

l “Adding a vCenter Server” on page 27

Restoring the HYCU backup controller to the originallocationPrerequisitesl The temporary HYCU backup controller has access to the cluster of the original HYCU

backup controller.

Procedure1. Log on to the HYCU web user interface of the temporary HYCU backup controller.

2. In the Virtual Machines panel, click the HYCU backup controller.

3. In the Details section that appears at the bottom of the screen, select the latest restorepoint.

n Note The Details section appears only if you click a virtual machine. Selecting


101

the check box before the name of the virtual machine will not open the Detailssection.



6. From the Select a storage container drop-down menu, select the storage container thatyou want to use.

7. Keep the Power virtual machine on switch on to turn the restored HYCU backupcontroller on after the restore. The original virtual machine is deleted automatically if itstill exists.

8. Click Restore. Once completed, the process leaves the restored HYCU backup controllerin the suspended state.

9. Log out of the HYCU web user interface.

10. Delete the temporary HYCU backup controller from its cluster. For instructions, seeNutanix or VMware documentation.

11. Log on to the HYCU web user interface of the restored HYCU backup controller.

12. Resume the HYCU backup controller. For instructions, see “Setting power options” onpage 151.

13. Only if restoring to a Nutanix ESXi cluster and the original HYCU backup controller no longerexists. Configure settings for the new network interface that was assigned to the virtualmachine. For example, you can edit the network connection by using the nmtui tool.

n Note Make sure to enter the original IP address of the HYCU backup controller.After editing the connection, delete the old network interface.

Restoring the HYCU backup controller to a differentclusterThis section guides you through a recovery of the HYCU backup controller to anothercluster.

Prerequisitesl The temporary HYCU backup controller has access to the cluster where you plan to

restore the original HYCU backup controller to.

Procedure1. Only if the original HYCU backup controller still exists. Put the original HYCU backup

controller into the suspended state.

C Caution Only one HYCU backup controller can be active on the same sources.Simultaneous activity of the HYCU backup controller and its clone causes failure ofcurrently running backups. The corresponding restore points are then


102

automatically removed by the HYCU cleanup process. As a result, your data may belost.

To do so, follow these steps:

a. Only if the original HYCU backup controller is stopped. Power the HYCU backupcontroller (virtual machine) on.

b. Log on to the HYCU web user interface of the original HYCU backup controller.

c. Suspend activities of the original HYCU backup controller. For instructions, see“Setting power options” on page 151.

d. Wait for the running jobs to complete. For this purpose, in the Jobs, panel, filter theJobs list by the Executing job status. For instructions, see “Filtering data” onpage 117. Once there are no entries left in the filtered list, all jobs are finished.

e. Optional. From the Nutanix Prism web console, remove the original HYCU backupcontroller (virtual machine) from the source. For instructions, see Nutanix orVMware documentation.

f. Only if the original HYCU backup controller is not removed. Ensure that activities of theoriginal HYCU backup controller are not resumed once the original HYCU backupcontroller is

2. Log on to the HYCU web user interface of the temporary HYCU backup controller.

3. In the Virtual Machines panel, click the HYCU backup controller.

4. In the Details section that appears at the bottom of the screen, select the latest restorepoint.




7. From the Select a storage container drop-down menu, select where you want to restorethe HYCU backup controller.

8. Keep the Power virtual machine on switch on to make HYCU turn the restored HYCUbackup controller on after the restore.

9. Click Restore. Once completed, the process leaves the restored HYCU backup controllerin the suspended state.

10. Log out of the HYCU web user interface.

11. Delete the temporary HYCU backup controller from its cluster. For instructions, seeNutanix or VMware documentation.

12. Log on to the HYCU web user interface of the restored HYCU backup controller.

13. Resume the HYCU backup controller. For instructions, see “Setting power options” on


103

page 151.

14. Only if you want to use network settings of the original HYCU backup controller. Configuresettings for the network interface of the virtual machine. For example, you can edit thenetwork connection by using the nmtui tool.

n Note Make sure to enter the original IP address of the HYCU backup controller.

Other HYCU backup controller restore possibilitiesBesides restoring or cloning the entire HYCU backup controller, you can also restore itsvirtual disks, create their clones, or export them to an NFS or SMB share.

Procedures for restoring, cloning, and exporting virtual disks of the HYCU backup controllerare the same to procedures for the same operations with ordinary virtual machines. Youmust select a corresponding option in the initial page in the Restore Options dialogbox: Restore vDisks, Clone vDisks, or Export vDisks. Afterward, in the dialog box, makeyour selections as appropriate. For further instructions, see the corresponding section:

l For restoring virtual disks: “Restoring virtual disks” on page 60

l For creating virtual disk clones: “Cloning virtual disks” on page 61

l For exporting virtual disks to an NFS or SMB share: “Exporting virtual disks” on page 63

n Note In restore points of the HYCU backup controller only the Backup restoreinstances are available.

Recreating HYCU instancesIf you are using HYCU for protection of Nutanix Files shares, your backup environmentincludes at least one HYCU instance that is connected to the HYCU backup controller. In thiscase, depending on the severity of the disaster, you may need to reestablish connections ofHYCU instances to the recovered HYCU backup controller or recreate HYCU instances fromthe HYCU virtual appliance image.

Component that has beenstruck

Components that must be recreated

HYCU backup controllerAll HYCU instances that are connected to the HYCUbackup controller

HYCU instance That particular instance

Prerequisitesl HYCU backup controller recovery is complete and the virtual machine is powered on.


104

Procedure1. Log on to the HYCU web user interface.

2. ClickAdministration, and then select Instances.

3. In the Instances dialog box, take note of the VM name, Hostname, Source, andIP address parameters for each of the HYCU instances, and then do the following foreach HYCU instance depending on its state:

l Virtual machine that acted as the HYCU instance still exists on the source and isvalid:

Follow these steps:

a. Only if the virtual machine is running. From the Nutanix Prism web console, turnthe virtual machine off.

b. From the Nutanix Prism web console, turn the virtual machine on. It willestablish a connection to the HYCU backup controller and will be reconfiguredautomatically.

l Virtual machine that acted as the HYCU instance is corrupted or no longer exists:

Recreate the HYCU instance. Follow these steps:

a. Only if the original HYCU instance still exists. From the Nutanix Prism web console,remove the corresponding virtual machine from the source.

b. Only if you want to use a new name for the HYCU instance. Remove the reference tothe HYCU instance from HYCU by deleting the HYCU instance through the HYCUweb user interface. For instructions, see “Managing HYCU instances” onpage 142.

c. Create a new HYCU instance. It may need not reside on the source that hostedthe original HYCU instance. For instructions, see “Adding a Nutanix Files server”on page 28.

i Important HYCU instance must be created from the same HYCUvirtual appliance image (OVF package) as your HYCU backup controller.

Only if you want to preserve the name of the HYCU instance. Make sure that yournew HYCU instance is configured with the same name, host name, andnetwork settings as the original HYCU instance.

If you realize that you do not need any HYCU instance anymore, for example, due tochanges in your backup environment, you can remove them. For instructions, see “Deletinga HYCU instance” on page 144.

105

Performing daily tasksTo ensure the secure and reliable performance of the data protection environment, HYCUprovides various mechanisms to support your daily activities.

I want to... Procedure

Get an at-a-glance overview of the data protectionenvironment state, identify eventual bottlenecks, andinspect different areas of the data protectionenvironment.

“Using the HYCU dashboard” onthe next page

Track tasks that are running in my environment andget an insight into the specific task status.

“Checking the status of jobs” onpage 107

View all events that occurred in my environment. “Viewing events” on page 108

Configure HYCU to send email notifications whenevents occur.

“Sending email notifications” onpage 109

Obtain reports on different aspects of the dataprotection environment.

“Using HYCU reports” on page 110

View entity details.“Viewing entity details ” onpage 115

Narrow down the list of displayed items by applyingfilters.

“Filtering data” on page 117

Export data that you can view in a table in any of thepanels to a JSON or CSV file.

“Exporting the contents of thepanel” on page 123

View target information, activate or deactivate atarget, increase the size of an iSCSI target, or edit ordelete a target.

“Managing targets” on page 123

View policy information, or edit or delete a policy. “Managing policies” on page 126

Back up data manually.“Performing a manual backup” onpage 128

Mark a restore point as expired.“Expiring backups manually” onpage 129

Chapter 8

8 Performing daily tasks

106

In case of the recognized problems in the Nutanix environment that can degrade theefficiency and reliability of data protection (for example, when storage, vCPU, or memoryutilization is exceeded), you can make adjustments to better meet your data protectiongoals. For details, see “Adjusting the HYCU virtual machine resources” on page 130.

Using the HYCU dashboardThe HYCU dashboard provides you with an at-a-glance overview of the data protectionstatus in your environment. This intuitive dashboard enables you to monitor all dataprotection activity and to quickly identify areas that need your attention. You can use thisdashboard as a starting point for your everyday tasks because it enables you to easilyaccess the area of interest by simply clicking the corresponding widget.

Accessing the Dashboard panel

To access the Dashboard panel, in the navigation pane, clickDashboard.

i Important Your user role defines which widgets you are allowed to see andaccess.

The following table describes what kind of information you can find within each widget:

Dashboard widget Description

Policies

Shows the percentage of policies that are compliant and the exactnumber of compliant and incompliant policies. A policy isconsidered compliant if all entities to which this policy is assignedare compliant with the policy settings. For detailed informationabout policies, see “Defining your backup strategy” on page 42.

Virtual Machines Shows the percentage of protected virtual and physical machines


107

Dashboard widget Description

in your environment, and the exact number of protected andunprotected virtual and physical machines. A virtual or physicalmachine is considered protected if it has an assigned policy and ifthere is at least one valid backup within the defined retentionperiod. For detailed information about protecting virtual andphysical machines, see “Backing up virtual machines ” on page 52.

Applications

Shows the percentage of protected applications, and the exactnumber of protected and unprotected applications. An applicationis considered protected if it has an assigned policy and if there is atleast one valid backup within the defined retention period. Fordetailed information about protecting applications, see “Backingup applications” on page 78.

Backups Shows the backup job success rate for the last seven days.

Targets*Shows the number of existing targets, overall capacity utilization,and the utilization per target type. For detailed information aboutsetting up targets, see “Setting up targets” on page 33.

Controller*

Shows the resource information about the virtual machine wherethe HYCU backup controller resides (storage, vCPU, and memory).For details about what to do if any of these values reaches a criticalvalue (that is, if any of the values that are indicated by circlesbecomes red), see “Adjusting the HYCU virtual machine resources”on page 130.

Jobs

Shows the number of jobs in the data protection environment inthe last 48 hours. It also shows how many jobs succeeded, failed,are in progress or in a queue. For details, see “Checking the statusof jobs” below.

Events

Shows the number of events in the data protection environmentin the last 48 hours. It also shows the number of the eventsaccording to their status. For details, see “Viewing events” on thenext page.

* An infrastructure group administrator only.

Checking the status of jobsYou can use the Jobs panel to check the overall status of jobs.

Accessing the Jobs panel

To access the Jobs panel, in the navigation pane, clickJobs.


108

In the Jobs panel, you can do the following:

l Check processes that are currently running.

l Check completed and stopped processes.

l Check more details about a specific job in the Details section that appears at the bottomof the screen after you select the job.

t Tip To minimize the Details section, clickMinimize or press Spacebar. Toreturn it to its original size, clickMaximize or press Spacebar.

l Virtual machines with attached volume groups only. Check the backup and restore processstatuses of the volume groups attached to the virtual machines. To do so, click an arrownext to the backup or restore job of a virtual machine with attached volume groups,and a list of attached volume group processes and their statuses will be expanded.Keep in mind that volume group processes will not appear all at once, but one afteranother, as the job progresses.

l Generate a report about a specific job by selecting it, and then clickingView Report.To copy the report to the clipboard, in the Job Report dialog box that opens, click Copyto clipboard.

l Cancel a currently running job by selecting it, and then clickingAbort Job.

The following table shows the job information:

Job information Description

NameName of a job that was performed (for example, adding a source,adding a target, running a backup, and so on).

StatusCurrent status of a job (for example, Queued, a progress barindicating the Executing status, OK, or Error).

Started When a job was started.

Finished When a job finished.

n Note If a backup job fails, HYCU automatically schedules backup job retries. Thesuccessive retries are performed in the increasing time intervals (15 minutes, 30minutes, 60 minutes, 1 hour, 2 hours, 3 hours, and so on) until the RPO is reached.When the RPO is reached, the time interval for retrying the backup job becomes thesame as the one specified for the RPO.

Viewing eventsThe Events panel enables you to view all events that occurred in your environment, to checkdetails about the selected event, and to list events that match the specified filter.

Accessing the Events panel

To access the Events panel, in the navigation pane, clickEvents.


109

The following information is available for each event:

Status Status of the event (Success, Warning, Failed)

Message Description of the event

CategoryCategory to which the event belongs (for example, Policies, Backup,Credentials, System in case of an internal event, and so on)

Timestamp Event creation time

To open the Details section where you can find the event summary and more details aboutthe event, click the desired event.

t Tip To minimize the Details section, clickMinimize or press Spacebar. To returnit to its original size, clickMaximize or press Spacebar.

Sending email notificationsYou can configure HYCU to send email notifications when events occur.

PrerequisiteBecause HYCU uses SMTP to send email notifications, an SMTP server must be configured.For details, see “Configuring an SMTP server” on page 151.



Procedure1. In the Events panel, click Email Notifications.

2. In the Email Notifications dialog box, clickNew. The New dialog box appears.

3. In the Subject field, enter a subject of the email message.

4. From the Category drop-down menu, select one or more categories to which theevents belong (for example, Policies, Backup, Credentials, System, and so on).

t Tip You can select all the available categories by selecting the Select All checkbox. If you want to remove any of the selected categories, expand the list, and thenclick the one that you want to remove. To remove all the selected categories, clickClear All.

5. From the Status drop-down menu, select the status of the events (Success, Warning,Failed).

t Tip You can select all the available statuses by selecting the Select All checkbox. If you want to remove any of the selected statuses, expand the list, and thenclick the one that you want to remove. To remove all the selected statuses, click


110

Clear All.

6. In the Email address field, enter one or more email recipients that will get the emailnotifications. If you are entering more than one email address, make sure to press theSpacebar after entering each one.

You can later edit settings for existing email notifications (clickEdit and make therequired modifications) or delete the ones that you do not need anymore (clickDelete).

Using HYCU reportsHYCU reports provide you with a visual presentation of data protection environmentresources and jobs. This comprehensive and precise presentation allows you to have anoptimum view for analyzing data and therefore making the best decisions when it comes toprotecting your data.

Report data can be presented as a table or as a chart. The following report chart types areused to visualize the reports: a bar chart, a heatmap, a line chart, an area chart, or a scatterchart.

ConsiderationKeep in mind that your user group and user role determine what kind of report data youcan view and what report actions you can perform.

After you get familiar with the reports as described in “Getting started with reporting” below,you can continue as follows:

l View reports. For details, see “Viewing reports” on page 112.

l Generate reports. For details, see “Generating reports” on page 113.

l Schedule reports. For details, see “Scheduling reports” on page 114.

n Note When scheduling the reports, you can also choose to send them byemail.

l Export and import reports. For details, see “Exporting and importing reports” onpage 114.

Accessing the Reports panel

To access the Reports panel, in the navigation pane, clickReports.

Getting started with reportingYou can take advantage of the predefined reports or create additional reports to betterunderstand your data protection environment, identify the potential problems, andimprove performance.

For a list of predefined reports, see “Predefined reports” on the next page. For instructionson how to create reports, see “Creating reports” on the next page.


111

Predefined reportsThe predefined reports represented by the icon enable you to obtain reports on the keyaspects of your data protection environment such as data transfer, job status, the numberof backups, and the amount of protected data. These reports cannot be edited or deleted.

Predefined report Description

Entity compliancystatus

List of virtual and physical machines, applications, and shares thatare compliant and uncompliant with backup requirements.

Hourly activities perpolicy

List of assigned policies with the corresponding number of jobsthat were running during each of the last 24 hours.

Hourly activities pertarget*

List of targets with the corresponding number of jobs that wererunning during each of the last 24 hours.

Protected data Total amount of protected data calculated on a daily basis.

Protected data perpolicy

Amount of data protected in the last 24 hours per policy.

Protected data perowner* Total amount of protected data per owner.

Protected data pertarget*

Amount of the data protected in the last 24 hours per target.

Protected datatimeline per target*

Daily amount of protected data per target.

Protected VM sizeper target *

List of protected virtual and physical machines and distribution ofthe corresponding protected data between targets.

VM backup statusList of backups occurred in the last 24 hours including informationsuch as status and duration of backups, backup size, and so on.

VM backup statusper target*

List of targets and related backups occurred in the last 24 hoursincluding information such as status and duration of backups,backup size, and so on.

* Available only to an infrastructure group administrator.

Creating reportsIf none of the predefined reports meets your reporting requirements, you can create a newreport and tailor it to your needs.

PrerequisiteYou have the Administrator user role assigned.


112

Depending on whether you want to create a new report from scratch or edit an existingreport and save it as a new report, do the following:


Create a new report fromscratch.

1. ClickNew. The Report Configuration dialog box opens.

2. Enter a report name and, optionally, its description.

3. Specify the time range for the report.

4. Select the type of report.

5. Select the aggregation value that you want to use toperform a calculation on a set of collected data.

6. Distribute the report tags for the collected data that youwant to include in your report between x-axis and y-axisto determine how the collected data will be presented inthe report.

7. Click Save.

Edit an existing reportand save it as a newreport.

1. From the list of reports, select the one that you want toedit and save as a new report, and then clickEdit. TheReport Configuration dialog box opens.

2. Enter a new name for the report, and then make therequired modifications.

3. Click Save as.

You can later edit any of the created reports (clickEdit and make the requiredmodifications) or delete the ones that you do not need anymore (clickDelete). Youcannot edit or delete the predefined reports represented by the icon.

Viewing reportsYou can view the reports on the current state of your data protection environment or thesaved reports that were generated either manually or automatically.


View a report on thecurrent state of my dataprotection environment.

From the list of reports, select the desired report, and thendouble-click it or clickPreview.

View a saved report.

1. From the list of reports, select the desired report.

2. In the Details section that appears at the bottom of thescreen, select the desired report version, and thendouble-click it or clickView.


113


For details on how to generate reports manually orautomatically, see “Generating reports” below or “Schedulingreports” on the next page.

In the dialog box that opens, besides viewing the report data, you can also do the following:

l Switch between the reports.

l Download the report in the PDF, PNG, or CSV format. To do so, clickDownload, andthen select one of the available formats.

l Only if you have the Administrator user role assigned. If you view a report on the currentstate of the data protection environment, you can save this version of the report byclicking Generate. The saved report is added to the list of report versions.

Generating reportsWhen you generate a report, you are actually saving a copy of the current version of theselected report (a report version) for future reference.

PrerequisiteYou have the Administrator user role assigned.

Procedure1. From the list of reports, select the one that you want to generate.

n Note If none of the available reports meets your reporting requirements, youcan create a new report. For details, see “Creating reports” on page 111.

2. In the Details section that appears at the bottom of the screen, clickGenerate. TheGenerate Report Version dialog box opens.

3. Optional. Enter a description for the report.

4. Click Generate.

t Tip You can save a version of the selected report also by clickingPreviewfollowed byGenerate.

The generated report is added to the list of report versions in the Details section thatappears at the bottom of the screen when you select a corresponding report.


l View the saved reports. For details, see “Viewing reports” on the previous page.

l Delete the saved reports that you do not need anymore. To do so, select the desiredreport version, and then clickDelete.


114

Scheduling reportsYou can use scheduling to generate reports automatically at a particular time each day,week, or month. You can view these reports in the web browser or schedule them to bedelivered by email.

Prerequisitesl You have the Administrator user role assigned.

l Only if you choose to send reports by email. An SMTP server is configured. For details, see“Configuring an SMTP server” on page 151.

Procedure1. From the list of reports, select the one that you want to be generated on a regular basis,

and then clickScheduler. The Report Scheduler dialog box opens.

n Note If none of the available reports meets your reporting requirements, youcan create a new report. For details, see “Creating reports” on page 111.

2. In the Schedule date field, specify the date and the time of day when you want thereport generation to begin.

3. From the Interval drop-down menu, select how often you want the reports to begenerated (daily, weekly, or monthly).

4. Use the Send switch if you want to schedule the automatic delivery of the reports toemail recipients, and then do the following:

a. From the Report format drop-down menu, select a file format for your report (PDF,PNG, or CSV).

b. In the Email address field, enter one or more email recipients that should receivethe reports. If you are entering more than one email address, make sure to pressthe Spacebar after entering each one.

5. Click Save.

t Tip The reports that are generated automatically are marked by in theScheduled column of the Reports panel.


l Edit scheduling options of any of the scheduled reports. To do so, select the report,clickScheduler, make the required modification, and then click Schedule.

l Unschedule any of the reports if you do not want them to be generated automaticallyanymore. To do so, select the report, clickScheduler, and then click Unschedule.

Exporting and importing reportsHYCU enables you to share user-created reports among different HYCU data protectionenvironments by exporting the reports to a JSON file and then importing the reports from aJSON file.


115

i Important Your permissions determine what kind of reports you can view andedit, and therefore also define a different level of access to the reports, which youshould consider before copying reports from one HYCU deployment to another.

Exporting reports

Procedure1. From the list of all reports, select the one that you want to export, and then clickExport.

2. Click OK.

The selected report will be exported to a JSON file and saved to the download location onyour system.

Importing reports

Procedure1. ClickImport. The Import Report dialog box opens.

2. Browse your file system for a report that you want to import.

3. Enter a name for the report and, optionally, its description.

4. Click Import.

A new report will be added to the list of the reports.

Viewing entity detailsYou can view the details about each virtual machine, physical machine, discoveredapplication, and file share in the Details section of the Virtual Machines, Applications, orShares panel. The following details are available:

Summary Shows detailed information about the selected entity.

Restore point

You can view the following information about each restore point:

l Date and time when the restore point was created.

l Restore instances:

o Backup: Available by default unless a backup is expired.

n Full: Visible if a full backup was performed.

n Incremental: Visible if an incremental backup was

performed.

o Archive: Available if a data archive was created.

o Copy: Available if a copy of backup data was created.


116

o Snapshot: Nutanix clusters only. Available if the source

contains a local snapshot that enables you to perform a fastrestore.

o Partial snapshot: Nutanix clusters only. Available if the

source contains a local snapshot that enables you to perform afast restore. Such snapshot contains only a partial set of disks,from which the application items were restored.

i Important If any of the restore instances is colored red, itcannot be used for a restore.

Compliancy

Shows the compliancy status of an entity:

l Success

l Failure

l Undefined

An entity is considered to be compliant with backup requirements ifthe time since the last successful backup is lower than the RPO set inthe HYCU policy and the estimated time to recover is lower than theRTO set in the HYCU policy.

By pausing on a compliancy status indicated by a respective icon,additional information about the backup is available. You can seebackup frequency, the elapsed time since the last successful backup,the time limit you set for a restore, the estimated time required for arestore, the number of copies and failed copies (if the Copy policyoption is enabled), and the backup, snapshot, archive, and/or copyexpiration time. In addition, if the compliancy status of your entity isFailure, this list will also include a reason why it is not compliant.

Backup status For details, see “Viewing the backup status of entities” below.

Restore status

Shows a progress bar indicating the progress of the entity restore.

t Tip If you double-click a progress bar, you are directed to theJobs panel where you can check details about the related job.

t Tip If there are too many items to be displayed on one page, you can movebetween the pages by clicking and. You can also use to set the number ofitems to be displayed per page.

Viewing the backup status of entitiesThe backup status of your entity determines whether it is possible to restore it.


117

LimitationThe Success with errors backup status for virtual machines with attached volume groups isavailable only for a Nutanix AHV cluster.

Backup status of theentity

Restore aVM orvDisks?

Restore VMfiles?

Restore anAPP?

Restore afile share?

Success h h h h

Success with warnings h h ha h

Success with errors hb hc hd x

Error x x x x

a You cannot specify a point in time to which you want to restore data. This backup statusmay occur because disk mapping failed or a virtual machine does not have an NIC, or, incase of applications, at least one database log backup failed (whereas all other databasesare in a consistent state).

b Because not all virtual machine disk files were backed up successfully, the virtual machinecan be partially restored. It may not be possible to turn it on if one of the system disks wasnot backed up.

c Because not all virtual machine disk files were backed up successfully, the individual filescan be partially restored (only the files that are displayed in the Restore Files dialog box).

d An application can be partially restored (only the databases that are displayed in therespective restore dialog boxes).

n Note By pausing on a backup status indicated by an icon, additional informationabout the backup is available. You can see the backup type, backup consistency, theduration and size of the backup, which target was used, and the backup UUID.

If you double-click a backup status icon, you are directed to the Jobs panel where youcan check details about the related jobs.

Filtering dataHYCU provides you with two types of filters that you can apply—the main filter and thedetail filter. After you apply any of the filters, only data that matches the filter criteria isdisplayed and you can easily find what you need.

Applying the main filterApply the main filter when you want to focus on certain aspects of your data protectionenvironment (for example, filtering data in the Virtual Machines panel helps you to focusonly on the virtual machines that you are interested in or responsible for).


118

n Note This type of filter is available in the Applications, Virtual Machines, VolumeGroups, Shares, Policies, Targets, Jobs, Events, and Self-Service panels.

Procedure1. In the selected panel, clickMain Filter. The Main view side panel opens.

2. Select your filter criteria.

3. Click Apply Filters.

See one of the following sections for the details about the available filtering options:

l “Filtering options in the Applications panel” on the next page

l “Filtering options in the Virtual Machines panel” on page 120

l “Filtering options in the Volume Groups panel” on page 121

l “Filtering options in the Shares panel” on page 121

l “Filtering options in the Policies panel” on page 122

l “Filtering options in the Targets panel” on page 122

l “Filtering options in the Jobs panel” on page 122

l “Filtering options in the Events panel” on page 122

l “Filtering options in the Self-Service panel” on page 123

Applying the detail filterApply the detail filter when you want to focus on the information about the restore andbackup data of the selected item.

n Note This type of filter is available in the Applications, Virtual Machines, VolumeGroups, and Shares panels.

Procedure1. From the list of all items in the selected panel, select the item that you want to filter by

restore and backup data.

2. In the Details section that appears at the bottom of the screen, clickDetail Filter.The Detail view side panel opens.

3. Select your filter criteria.

4. Click Apply Filters.

See one of the following sections for the details about the available filtering options:

l “Filtering options in the Applications panel” on the next page

l “Filtering options in the Virtual Machines panel” on page 120

l “Filtering options in the Volume Groups panel” on page 121

l “Filtering options in the Shares panel” on page 121

t Tip If there are too many filtered items to be displayed on one page, you can move


119

between the pages by clicking and. You can also use to set the number offiltered items to be displayed per page.

Filtering options in the Applications panelIn the Main view side panel, select one or more filtering options:

Filtering option Action

Search Enter a search term. You can filter by the name of the application.

SourcesFrom the drop-down menu, select the sources that host the virtualmachines on which the applications are running or the physicalmachines on which the applications are running.

PoliciesFrom the drop-down menu, select the policies that are assigned tothe virtual or physical machines on which the applications arerunning.

OwnersFrom the drop-down menu, select the owners that are assigned tothe virtual or physical machines on which the applications arerunning.

Application types From the drop-down menu, select the application types.

Compliancy Select one or more check boxes to filter by the compliancy status.

Protection Select one or more check boxes to filter by the protection status.

Discovery

Select one or more check boxes to filter by the applicationdiscovery status:

l Success: One or more applications are discovered.

l Failure: No applications were discovered.

l Warning: Application discovery failed because the virtual orphysical machine is offline or not reachable.

In the Detail view side panel, select one or more filtering options:


Restore instances From the drop-down menu, select one or more restore instances.

Restore point date Select the time to filter by when the restore points were created.

Backup status Select one or more check boxes to filter by the backup status.



120

Filtering options in the Virtual Machines panelIn the Main view side panel, select one or more filtering options:


SearchEnter a search term. You can filter by the virtual or physicalmachine name, the HYCU UUID, or the source UUID.

SourcesFrom the drop-down menu, select the sources that host the virtualmachines or the physical machines.

Credential groupsFrom the drop-down menu, select the credentials for the virtual orphysical machines.

PoliciesFrom the drop-down menu, select the policies that are assigned tothe virtual or physical machines.

OwnersFrom the drop-down menu, select the owners that are assigned tothe virtual or physical machines.


Discovery

Select one or more check boxes to filter by the applicationdiscovery status:

l Success: One or more applications are discovered.

l Failure: No applications were discovered.

l Warning: Application discovery failed because the virtual orphysical machine is offline or not reachable.

l Undefined: Information about the application discovery statusis not available.

Protection Select one or more check boxes to filter by the protection status.








121

Filtering options in the Volume Groups panelIn the Main view side panel, select the following filtering option:


SourcesFrom the drop-down menu, select the sources that host the virtualmachines to which the volume groups are attached.







Filtering options in the Shares panelIn the Main view side panel, select one or more filtering options:


Search Enter a search term. You can filter by the file share name.

File serversFrom the drop-down menu, select the file servers that host the fileshares.

PoliciesFrom the drop-down menu, select the policies that are assigned tothe file shares.

OwnersFrom the drop-down menu, select the owners that are assigned tothe file shares.


ProtectionSelect one or more check boxes to filter by the protection status offile shares.







122



Filtering options in the Policies panelIn the Main view side panel, select one or more filtering options:


Search Enter a search term. You can filter by the name of the policy.


Filtering options in the Targets panelIn the Main view side panel, select one or more filtering options:


Search Enter a search term. You can filter by the name of the target.

Target type Select one or more check boxes to filter by the target type.

Health Select one or more check boxes to filter by the health of the target.

Filtering options in the Jobs panelIn the Main view side panel, select one or more filtering options:


SearchEnter a search term. You can filter by the job name or the jobUUID.

Status Select one or more check boxes to filter by the status of the job.

Time range

Specify a time range to limit your search for jobs. You can selectone of the predefined time ranges (Last 1 hour, Last 24 hours, orLast week), or use the calendar to select a start date and hour andan end date and hour of the time range for jobs to be displayed.

Filtering options in the Events panelIn the Main view side panel, select one or more filtering options:


MessageEnter a text string to filter the list to include only the messages withthe specified string.


123


CategoryEnter a text string to filter the list to include only the categories withthe specified string.

Username From the drop-down menu, select the user name.

Status Select one or more check boxes to filter by the status of the event.

Time range

Specify a time range to limit your search for events. You can selectone of the predefined time ranges (Last 1 hour, Last 24 hours, orLast week), or use the calendar to select a start date and hour andan end date and hour of the time range for events to be displayed.

Filtering options in the Self-Service panelIn the Main view side panel, select one or more filtering options:


Group name Enter the group name.

StatusSelect one of the following to filter by the status of the group oruser (that is, which groups or users are allowed to log on to HYCUand which are not).

Exporting the contents of the panelData that you can view in a table in any of the panels can be exported to a file in JSON orCSV format. To export the data to a JSON or CSV file, follow these steps:

1. Navigate to the panel whose data you want to export.

2. Depending on the format of the file to which you want to export the data, clickExport, and then, from the drop-down menu, select Export to JSON or Export toCSV.

t Tip If you want to export only specific data, before selecting the format of a fileto which you want to export data, clickMain Filter, select your filter criteriabased on what kind of data you want to export to a file, and then click ApplyFilters.

3. In the dialog box that appears, select to either open the file or save it to a desiredlocation.

Managing targetsIf you have the proper permissions, you can view target information, edit target properties,activate or deactivate a target, or delete a target if you do not want to use it for storing


124

protected data anymore.



Viewing target informationYou can view information about each target in the list of targets in the Targets panel. Thisallows you to have an overview of the general status of the targets. The followinginformation is available for each target:

Targetinformation

Description

Name Name of the target.

Type Type of target (AWS S3/Compatible, AZURE, SMB, NFS, or iSCSI).

Health

Health status of the target:

l Gray: Shows the initial target status before a health test. It alsoindicates an inactive target.

l Green: The target is in a healthy state with target utilization of lessthan the configured value (by default, 90%).

l Yellow: Target utilization is over the configured value (by default,90%).

l Red: Target utilization is over the configured value (by default, 95%).It also indicates a target error state after a test task (for example, anI/O error occurred, the target is not accessible, the permission isdenied, and so on).

When HYCU checks if there is enough space on the target to perform abackup, it calculates it by using the total provisioned space of all diskson the virtual or physical machine, regardless of whether the backup isfull or incremental.

SizeEstimation of the amount of storage space that should be reserved forthe backup files (in MiB, GiB, or TiB).

UtilizationPercentage of the specified target size that is already used for storingprotected data.

Mode

Mode of the target:

l Read/Write: You can use this target for backing up and restoringdata.

l Read Only: You can use this target only for restoring data.


125

Targetinformation

Description

Status

Status of the target:

l Active: You can use this target for backing up and restoring data.

l Inactive: You cannot use this target for backing up and restoringdata. This status indicates that the target is deactivated due tomaintenance tasks (for example, adding new disks).

For details on how to change the status of the target, see “Activating ordeactivating a target” below.

To open the Details section where you can find the target summary and more details aboutthe target, click the desired target.


Editing a targetProcedure1. In the Targets panel, select the target that you want to edit, and then clickEdit. The

Edit Target dialog box appears.

2. Edit the selected target as required. For detailed information about target properties,see “Setting up targets” on page 33.

C Caution Making any changes to the target location may result in data loss.Therefore, before specifying a new target location, make sure you have alreadymoved the existing backup data to this new location on the same or a differentserver.

3. Click Save.

Activating or deactivating a targetProcedure1. In the Targets panel, select the target that you want to activate or deactivate.

2. Change the status of the selected target by clickingActivate orDeactivate.

3. Only if deactivating the target. Click Yes to confirm that you want to deactivate theselected target.

If you deactivate a target, this target will not be used for backup and restore operationsanymore.


126

Increasing the size of an iSCSI targetHYCU enables you to increase the size of your iSCSI target by extending the HYCU logicalvolume.

Prerequisitesl The size of the target has been increased on the iSCSI server.

l No backup or restore job is in progress on the selected target.

l No other maintenance task is already running on the selected target (such as editingthe target and updating the iSCSI Initiator secret or resetting mutual CHAPauthentication sessions for the targets with CHAP authentication enabled).

l No other size increase of the selected target has already been started.

Procedure1. In the Targets panel, select the target whose size you want to increase, and then click

Extend.

2. Click Yes to confirm that you want to increase the size of the selected target.

You will receive a message that indicates whether increasing the size of the iSCSI targetcompleted successfully.

Deleting a targetYou can delete a target if it does not contain protected data. After deleting a target, nobackup or restore actions including this target are possible anymore.

Procedure1. In the Targets panel, select the target that you want to delete, and then clickDelete.

n Note If the target that you want to delete is used for archiving, make sure thatno data archive with the specified archive target is used by any policy.

2. Click Yes to confirm that you want to delete the selected target.

Managing policiesIf you have the proper permissions, you can view policy information, edit policy properties,or delete a policy if you do not want to use it for protecting data anymore.




127

Viewing policy informationYou can view information about each policy in the list of policies in the Policies panel. Thisallows you to have an overview of the general status of the policies. The followinginformation is available for each policy:

Policyinformation

Description

Name Name of the policy.

Compliancy

Compliancy status of the policy:

l Success

l Failure

l Undefined

A policy is considered compliant if all entities to which this policy isassigned are compliant with the policy settings. For detailedinformation about the compliancy status of entities, see “Viewing entitydetails ” on page 115.

VM CountTotal number of virtual and physical machines that have the particularpolicy assigned to them.

APP CountTotal number of applications that have the particular policy assigned tothem.

DescriptionDescription of the policy (how often backup and restore jobs areperformed).

To open the Details section where you can find the policy summary and more details aboutthe policy, click the desired policy.


Editing a policyTo edit a policy, follow these steps:

1. In the Policies panel, select the policy that you want to edit, and then clickEdit. TheEdit Policy dialog box appears.

2. Edit the selected policy as required. For detailed information about policy properties,see “Creating a policy” on page 44.

i Important vSphere environments only. You cannot edit the policy that isassigned to the vSphere virtual machines or applications in such a way that you


128

enable the Backup from replica or Fast restore option. These options are notavailable for vSphere virtual machines or applications.

3. Click Save.

When editing a policy that is assigned to several virtual machines, one of which is the HYCUbackup controller, make sure that the policy remains applicable also for protecting theHYCU backup controller. For details on protecting the HYCU backup controller, see“Protecting the HYCU backup controller” on page 96.

Deleting a policyTo delete a policy, follow these steps:

1. In the Policies panel, select the policy that you want to delete, and then clickDelete.

2. Click Yes to confirm that you want to delete the selected policy.

Performing a manual backupHYCU backs up your data automatically after you assign a policy to the selected entity.However, you can also back up your data manually at any time (for example, for testingpurposes or if the backup fails).

ConsiderationYou can prevent your manual backups from interfering with the scheduled backupsdetermined by the RPO specified in the policy. To do so, set theexclude.manually.run.backups.regarding.rpo configuration setting to true. This isespecially important if you define backup windows because performing a manual backupcan prevent the backup scheduled in the backup window from starting, which can result indata not being protected until the next backup window or the next manual backup. Fordetails on how to customize HYCU configuration settings, see “Customizing HYCUconfiguration settings” on page 188.

Procedure1. In the Virtual Machines, Applications, or Shares panel, select which entities you want to

back up.

2. ClickBackup to perform the backup of the selected entities.

3. Use the Force full backup switch if you want to perform a full backup. Otherwise,HYCU will perform a full or incremental backup based on the amount of changed data.

4. Click Yes to confirm that you want to start the manual backup.

t Tip In the navigation pane, clickJobs to check the overall progress of thebackup.


129

Expiring backups manuallyIf there is a restore point that you do not want to use for data restore anymore, you canmark it as expired. Each restore point represents data that was backed up at a specifiedpoint in time. Your restore point can contain one or more restore instances—Backup, Copy,Snapshot (Nutanix clusters only), and Archive—that you can mark as expired. This meansthat your expire action can be one of the following:

l Expiring a restore point:

Make sure that all related restore instances are marked for expiration.

l Leaving a restore point, but expiring one or more restore instances:

Make sure the restore instance you want to keep is not marked for expiration.

Considerationsl An expire action cannot be undone.

l If the most recent restore point is marked as expired, the next backup will be a fullbackup.

l When a restore point is marked as expired, any subsequent incremental backups willalso be marked as expired unless the status of the selected restore point is Error. In thiscase, only the selected restore point is expired and not the whole backup chain.

l The Backup and Copy restore instances are always expired together.

Depending on the entity for which you want to expire old backups, access one of thefollowing panels:

l Accessing the Virtual Machines panel

To access the Virtual Machines panel, in the navigation pane, click VirtualMachines.

l Accessing the Applications panel


l Accessing the Shares panel


Procedure1. In the Virtual Machines, Applications, or Shares panel, select the entity for which you

want to expire old backups.

2. In the Details section that appears at the bottom of the screen, select the restore pointthat you want to mark as expired.

3. ClickExpire. The Expire dialog box appears that shows only restore instances thatare applicable to your scenario and that you can mark as expired. The following can beexpired:


130

l Backup and Copy


l Archive

n Note All restore instances are preselected.

4. Leave the default values if you want the restore point to be marked as expired, or clearthe check boxes for restore instances that you do not want to mark as expired.

i Important If you mark Backup and Copy for expiration, the associatedsnapshots will be expired as well.

5. Click Yes to confirm that you want the selected restore instances to be marked asexpired.

After you mark the restore instances as expired, the HYCU cleaning process removesexpired backups from the target.

Adjusting the HYCU virtual machineresourcesWhen storage, vCPU, or memory utilization is exceeded (that is, when the utilization of anyof these resources is greater than 90 percent), their values that are indicated by circlesbecome red in the Controller widget in the Dashboard panel. To adjust the HYCU virtualmachine resources, follow these steps:

1. Log on to Nutanix Prism. For details about the Prism web console, see Nutanixdocumentation.

2. In the menu bar, click Home, and then select VM.

3. Click the Table tab to display the VM Table view.

4. From the list of virtual machines, select your HYCU virtual machine, and then clickPower Off Actions to shut down the virtual machine.

i Important Wait a moment for the virtual machine to shut down completely.

5. Click Update, and then, in the Update VM dialog box, modify the configuration asrequired, and click Save.

6. Click Power on to turn on the virtual machine.

131

Managing usersThe HYCU user management system provides security mechanisms to help preventunauthorized users from accessing protected data. Only users that are given specific rightshave access to the data protection environment. These users can be authenticated either byHYCU (HYCU users) or through an Active Directory server (AD users and AD groups).

Each user that logs on to HYCU belongs to one of the HYCU groups—an infrastructuregroup or a self-service group—and has a user role assigned.

For details on HYCU groups and user roles, see “HYCU groups” below and “User roles” onthe next page.

n Note User management concepts and procedures apply to both virtual andphysical machines.

HYCU groupsFor a consolidated user management experience, HYCU provides two types of groups towhich users can belong.

Group Description

Infrastructuregroup

Created by default during the deployment of the HYCU virtualappliance and already includes a built-in user with the Administratoruser role assigned (represented by)—cannot be edited, deactivated,and deleted.

Users can be added to this group by an infrastructure groupadministrator (an infrastructure group user with the Administrator userrole assigned).

Self-servicegroup

Must be created by an infrastructure group administrator andrepresents a customer or department responsible for a specific set ofentities in the data protection environment.

Users can be added to this group by an infrastructure groupadministrator.

i Important If a specific self-service group is deleted, all datathat is backed up by this group is deleted from the database.

Chapter 9

9 Managing users

132

You can manage users only if you have an Administrator role assigned. However, keep inmind that the scope of user management actions that you can perform differs dependingwhether you belong to the infrastructure or self-service group. As an infrastructure groupadministrator, you can manage users and groups throughout the whole data protectionenvironment, whereas as a self-service administrator, you can manage only the group youbelong to. The following diagram shows which user-related actions you can perform:

Figure 9–1: User management actions performed by the infrastructure and self-service groupadministrators

Depending on the HYCU group to which you belong and the assigned user role, you canperform only specific actions in the data protection environment. For details on user roles,see “User roles” below.

User rolesEach user in a group has an assigned role that determines the scope of actions the user canperform in the data protection environment. This means that access to data andinformation within the data protection environment is limited based on the role that theuser has assigned. If a user is a member of multiple groups, this user can have differentroles assigned in different groups, depending on the business needs, and can switchbetween these groups while being logged on to HYCU.

Depending on the group to which a user belongs, the user can perform the followingactions:

9 Managing users

133

Role Infrastructure group Self-service group

Administrator

l Perform all user managementactions (creating, editing, anddeleting users and self-servicegroups, setting ownership ofvirtual machines and fileshares, enabling and disablingusers and self-service groupsto access HYCU, and addingand removing users fromgroups).

l Perform all administrativeactions in HYCU.

l Perform all reportmanagement actions.

l Assign policies.

l Back up and restore virtualmachines, applications, andfile shares.

l Add and remove users fromgroups.

l Perform all reportmanagement actions.

Viewer

l View information aboutapplications, virtual machines,shares, policies, targets, jobs,events, users, generatedreport versions, and settingsavailable through theAdministration menu inthe data protectionenvironment.

l View information aboutapplications, virtual machines,shares, policies, jobs, events.and generated report versionsin the data protectionenvironment.

BackupOperator

l View the same information asViewer.

l Define a backup strategy.

l Back up virtual machines andfile shares that are not ownedby any self-service group, andback up applications.


l Assign policies.

l Back up virtual machines,applications, and file shares.

RestoreOperator


l Restore virtual machines andfile shares that are not ownedby any self-service group, andrestore applications.


l Restore virtual machines,applications, and file shares.

9 Managing users

134

Setting up a user environmentAs an infrastructure group administrator, you can give users specific rights to access onlycertain data within the data protection environment. Therefore, before users can start usingHYCU for data protection, make sure you have set up an environment that is tailored totheir needs. Depending on the needs, perform one or more of the following actions:

Action Instructions

Create a new user. “Creating a new user” below

Create a new self-service group.“Creating a new self-service group” on thenext page

Set ownership of virtual machines and fileshares.

“Setting ownership of virtual machines” onpage 136

“Setting ownership of file shares” onpage 136

You can also at any time enable or disable specific groups or users from logging on toHYCU. For details, see “Activating or deactivating users or self-service groups” on page 137.

Accessing the Self-Service panel

To access the Self-Service panel, in the navigation pane, clickSelf-Service.

Creating a new userPrerequisiteOnly if you plan to use Active Directory for authentication. Active Directory authentication isconfigured. For details on how to do this, see “Configuring Active Directory authentication”on page 141.

LimitationYou cannot add the Active Directory primary group (usually the Domain Users group) as anAD group.

Procedure1. In the Self-Service panel, clickManage Users, and then clickNew. The Manage

Users dialog box opens.

2. Enter a user name if you are adding a HYCU user or an AD user, or a common name ifyou are adding an AD group.

i Important When entering a name, make sure it complies with the SAMaccount name limitations—name length may not exceed 20 characters and contain

9 Managing users

135

any of the following characters: "/ \ [ ] : ; | = , + * ? < >. In addition, HYCU does notallow the at sign (@) in the name.

If your environment requires it, these limitations can be overridden by editing thead.username.filter.regex configuration setting. However, this is not supportedand could cause authentication issues. For details on how to customize HYCUconfiguration settings, see “Customizing HYCU configuration settings” on page 188.

3. From the Authentication type drop-down menu, select one of the followingauthentication types:

l HYCU

Enter a display name, the user password and, optionally, email address.

n Note The minimum password length is six characters.

l AD user

From the Active Directory drop-down menu, select the Active Directory the AD userbelongs to.

l AD group

From the Active Directory drop-down menu, select the Active Directory the ADgroup belongs to.

4. Click Save. The user is added to the list of all users.

5. Click Close.


l Add users to groups. For details, see “Adding users to groups” on page 138.

l Edit any of the existing HYCU users by clickingEdit User and making the requiredmodifications. Keep in mind that the built-in user, AD users, and AD groups cannot beedited.

l Enable or disable specific users from logging on to HYCU. For details, see “Activating ordeactivating a user” on page 137.

l Delete any of the existing users by clickingRemove User. Keep in mind that the built-in user cannot be deleted.

Creating a new self-service groupProcedure1. In the Self-Service panel, clickNew Group. The New Group dialog box opens.

2. Enter a self-service group name and, optionally, its description.

3. Click Save.


9 Managing users

136

l Add users to groups. For details, see “Adding users to groups” on page 138.

l Edit any of the existing self-service groups by clickingEdit and making the requiredmodifications.

l Allow users belonging to a specific self-service group to see only the policies whosenames start with their group name and the Exclude policy. To do so, in the HYCUconfig.properties file, set the policies.group.specific.synchronized

configuration setting to true. For details on how to customize the HYCU configurationsettings, see “Customizing HYCU configuration settings” on page 188.

n Note Keep in mind that such policies can be edited or deleted only if they arenot assigned to any entity.

l Enable or disable specific self-service groups from logging on to HYCU. For details, see“Activating or deactivating a self-service group” on the next page.

l Delete any of the existing self-service groups by clickingDelete.

Setting ownership of virtual machinesBy setting ownership of virtual machines, you enable specific groups to protect only theassigned virtual machines.



Procedure1. In the Virtual Machines panel, select virtual machines to which you want to assign an

owner, and then clickOwner.

2. From the list of groups, select which group you want to assign as an owner of theselected virtual machines, and then click Assign.

i Important If a virtual machine or an application has backup or restore jobsin progress, or a scheduled backup task in the queue, you cannot assign a newgroup to the relevant virtual machine.

Depending on the needs of a specific data protection environment, you can at any timeremove an owner from the virtual machines by selecting the virtual machines from whichyou want to remove the owner, and then clickingOwner followed byUnassign. Keep inmind that if you change the owner of the virtual machines, all restore points for thesevirtual machines are deleted.

Setting ownership of file sharesBy setting ownership of file shares, you enable specific groups to protect only the assignedfile shares.



9 Managing users

137

Procedure1. In the Shares panel, select file shares to which you want to assign an owner, and then

clickOwner.

2. From the list of groups, select which group you want to assign as an owner of theselected file shares, and then click Assign.

i Important If any backup or restore job for a file share is already in progress,or a scheduled backup task is in the queue, you cannot assign a new group to thisfile share.

Depending on the needs of a specific data protection environment, you can at any timeremove an owner from the file shares by selecting the file shares from which you want toremove the owner, and then clickingOwner followed byUnassign. Keep in mind that ifyou change the owner of the file shares, all restore points for these file shares are deleted.

Activating or deactivating users or self-servicegroupsDepending on the nature of your business, you can at any time enable or disable specificusers or self-service groups from logging on to HYCU by activating or deactivating them. Byactivating or deactivating a self-service group, you enable or disable all users belonging tothe specific self-service group from logging on to HYCU as members of that group.

Activating or deactivating a user

Procedure1. In the Self-Service panel, clickManage Users.

2. From the list of all users, select the one whose status you want to change.

3. Depending on the status of the user, do one of the following:

l If the status of the selected user is Inactive and you want to activate it, clickActivate.

l If the status of the selected user is Active and you want to deactivate it, clickDeactivate.

Activating or deactivating a self-service group

Procedure1. In the Self-Service panel, from the list of self-service groups, select the one whose status

you want to change.

2. Depending on the status of the self-service group, do one of the following:

l If the status of the selected self-service group is Inactive and you want to activate it,clickActivate.

9 Managing users

138

l If the status of the selected self-service group is Active and you want to deactivate it,clickDeactivate.

n Note If a user is a member of several self-service groups and at least one of thesegroups has the Active status, the user is automatically switched to it. If there is morethan one group with the Active status to which the user belongs, the user isautomatically switched to the one that was created first.

Adding users to groupsAs an infrastructure or self-service group administrator, you can add a user with a specificuser role to a group. By doing so, you allow the user to access only the defined dataprotection environment and to perform a set of actions specified by the assigned role.

Considerationsl You can add a user to multiple groups in which the user can have different user roles

assigned. For details on user roles, see “User roles” on page 132.

l If an AD user has multiple user roles assigned based on membership in severalAD groups, the user acquires the role with the highest privilege level. User roles areprioritized in the following order: Administrator > Restore Operator > Backup Operator> Viewer. However, keep in mind that a role assigned to an AD user independently of anAD group always takes precedence over a role within an AD group.

Procedure1. Select the group to which you want to add a new user.

2. ClickAdd to Group. The Add User to Group dialog box opens.

3. In the Username field, enter a user name.

i Important AD user and AD group only. Enter a user name in one of thefollowing formats: user@domain or domain\name.

4. From the User role drop-down menu, select a role that you want to assign to the user(Administrator, Viewer, Backup Operator, or Restore Operator).

5. Click Add User.

Depending on the needs of a specific data protection environment, you can at any timeremove a user from a group by selecting the user that you want to remove and clickingRemove from Group.

Switching to another groupAs a user you can belong to one or more groups and log on to HYCU with all thepermissions associated with the group to which you belong. If you are a member of morethan one group, you can at any time switch to another group (provided that its status is

9 Managing users

139

Active) while being logged on to HYCU. This means that you can select any of the groups towhich you belong and use it for a session.

Procedure1. Click the group under which you are currently logged on to HYCU at the upper right of

the screen.

Figure 9–2: Example of a self-service group, HYCU_group, under which a user, HYCU_group_member, is logged on to HYCU

2. From the list of all groups to which you belong, select the one to which you want toswitch.

t Tip The group under which you are currently logged on to HYCU has next toit.

3. Click Switch.

You are automatically switched to the group you selected.

140

AdministeringAfter you deploy HYCU, you can perform various administration tasks through theAdministration menu to customize HYCU for your data protection environment.


Configure Active Directory authentication.“Configuring Active Directoryauthentication” on the next page

Configure encryption for targets. “Configuring target encryption” on page 142

Manage HYCU instances. “Managing HYCU instances” on page 142

Set the iSCSI Initiator secret.“Setting the iSCSI Initiator secret” onpage 144

Obtain a permanent HYCU license. “Licensing” on page 144

Configure log file settings to troubleshootproblems if HYCU does not perform asexpected.

“Setting up logging” on page 147

Change the HYCU listening port number.“Changing the HYCU listening port number”on page 150

Change network settings. “Changing network settings” on page 150

Set power options. “Setting power options” on page 151

Configure an SMTP server. “Configuring an SMTP server” on page 151

Configure the SSL certificate.“Configuring the SSL certificate” onpage 152

Upgrade HYCU to a new available version. “Upgrading HYCU” on page 153

If for whatever reason you decide that you no longer want to use HYCU for protecting yourdata, you can easily remove it from your system. For details, see “Removing HYCU” onpage 164.

Chapter 10

10 Administering

141

Configuring Active Directory authenticationIn addition to standard HYCU authentication, you can also configure Active Directoryauthentication. This allows users to log on to HYCU with their Active Directory domainaccounts.

PrerequisiteOnly if using LDAPS for user authentication. LDAPS authentication is set up. For details, see“Setting up LDAPS authentication” on page 171.

Accessing the Active Directory dialog box

To access the Active Directory dialog box, clickAdministration, and then selectActiveDirectory.

To configure Active Directory authentication, add one or more Active Directories as yourauthentication sources in HYCU. To do so, follow these steps:

1. In the Active Directory dialog box, clickNew. The New dialog box appears.

2. In the Name field, specify a name for the Active Directory.

3. In the Domain field, enter the FQDN or domain alias name of the Active Directory. If youplan to use AD groups, it is mandatory to enter the FQDN.

ExampleIf you enter mycompany.com as the FQDN and mc as the alias domain name, the userwill be able to log on to HYCU with <Username>@mycompany.com or mc\<Username>.

n Note You can enter more than one FQDN or domain alias name. In this case,make sure to press the Spacebar after entering each one.

4. In the Provider URL field, enter the Active Directory URL in one of the following formats:

l ldap://<LDAPServerHostnameorIPAddress>:<Port>

When using the LDAP protocol, the default port is 389. Entering the port is optionalif the default value is used.

l Only if LDAPS authentication is set up. ldaps://<LDAPServerHostname>:<Port>

When using the LDAPS protocol, the default port is 636. Entering the port isoptional if the default value is used.

n Note You can enter more than one Active Directory URL. In this case, makesure to press the Spacebar after entering each one.

5. Click Save.

You can also edit any of the existing Active Directories (clickEdit and make the requiredmodifications) or delete the ones that you do not need anymore (clickDelete).

10 Administering

142

After Active Directory authentication is configured, the AD user or AD group authenticationtype can be specified when creating a new user. For details, see “Creating a new user” onpage 134.

Configuring target encryptionIf you enabled target encryption when setting up your target, you can get informationabout which algorithm is used, view a list of currently encrypted targets, and export theencryption key to a file.

Accessing the Encryption dialog box

To access the Encryption dialog box, clickAdministration, and then select Encryption.

To export the encryption key to a file, in the Encryption dialog box, click Export.

Managing HYCU instancesAll existing HYCU instances in your data protection environment are listed in the Instancesdialog box. Besides viewing all the existing HYCU instances, you can use this dialog box alsoto create new HYCU instances, view information about each HYCU instance, and deleteHYCU instances.

For details on HYCU instances, see “HYCU instances” on page 30.

Accessing the Instances dialog box

To access the Instances dialog box, clickAdministration, and then select Instances.

Creating a HYCU instance by using the HYCUwebuser interfaceYou can create a HYCU instance by using the HYCU web user interface as an alternative tocreating it by deploying the HYCU virtual appliance in the HYCU Instance mode.

Prerequisitesl Only if creating a HYCU instance on a Nutanix AHV cluster. The HYCU virtual appliance

image is present on the Nutanix cluster in the following format:



l Only if creating a HYCU instance on a Nutanix ESXi cluster.

o A user with specific privileges for vCenter Servers is specified. For details on whichprivileges must be assigned to a vSphere user, see “Assigning privileges to avSphere user” on page 177.

10 Administering

143

o The credentials for the vCenter Server associated with the Nutanix ESXi cluster onwhich your HYCU instance will reside are provided. For details, see “Adding aNutanix cluster” on page 25.

o The HYCU OVF package is imported to the vCenter Server content library and itsformat is as follows:



Procedure1. In the Instances dialog box, clickNew. The New dialog box opens.

2. In the General section, enter a name for the HYCU instance.

3. In the Network configuration section, do the following:

a. Enter a host name for the HYCU instance.

i Important Make sure that you enter a unique host name for each HYCUinstance that you create. The host name may contain only letters, numbers, andhyphens (-). However, keep in mind that it cannot begin or end with a hyphen.The maximum number of characters in the host name is 63, the maximumnumber of characters in the domain name is 253.

b. Use the DHCP switch if you want a dynamic IP address to be assigned to the HYCUinstance. Otherwise, specify the IP address, the netmask, and the gateway.

4. In the Deployment section, do the following:

a. From the Destination drop-down menu, select a Nutanix cluster on which yourHYCU instance will reside.

b. From the Network drop-down menu, select a VLAN.

c. From the Datastore drop-down menu, select a datastore.

t Tip If you select Select automatically, HYCU will select the datastore withthe most available space.

5. Click Save.

Viewing HYCU instance informationYou can view the following information about each HYCU instance:

HYCU instance information Description

VM name Name of the HYCU instance, if known.

Hostname Host name of the HYCU instance.

SourceNutanix cluster on which the HYCU instance resides(visible only if it is added to HYCU).

10 Administering

144

HYCU instance information Description

StatusShows if the HYCU instance is up and running, andcommunicating with the HYCU backup controller.

VersionVersion of the HYCU instance (for example, hycu-4.0.0-3634).

IP address IP address currently assigned to the HYCU instance.

Deleting a HYCU instanceProcedure1. From the list of HYCU instances, select the one that you want to delete, and then clickDelete.

2. In the Remove Instance dialog box, click Yes to confirm that you want to delete theselected HYCU instance.

Setting the iSCSI Initiator secretDuring the HYCU deployment, the HYCU iSCSI client, referred to as the iSCSI Initiator, is setup so that HYCU can use iSCSI targets for storing data.

If you want to configure mutual CHAP authentication between the iSCSI Initiator and theiSCSI target, you must specify the iSCSI Initiator secret (the security key). For details on howto enable mutual authentication, see “Setting up targets” on page 33.

Accessing the iSCSI Initiator dialog box

To access the iSCSI Initiator dialog box, clickAdministration, and then select iSCSIInitiator.

To set the iSCSI Initiator secret, follow these steps:

1. In the iSCSI Initiator dialog box, enter the secret.

2. Click Save.

LicensingAfter you deploy the HYCU virtual appliance, you can start using HYCU immediately with aprebuilt Instant-on license. This license expires automatically after 45 days and cannot bereused. Therefore, make sure to obtain a permanent license within this 45-day period.

The HYCU license is linked to the HYCU backup controller and you can decide on the licensetype or a combination of license types that best suits your environment. The followinglicense types are available:

10 Administering

145

l Standard licenses

o Socket-based licenses

Licenses are based on the number of CPU sockets on all sources that you plan toprotect by using HYCU.

o VM-based licenses

Licenses are based on the number of protected virtual machines on all sources andphysical machines that you plan to protect by using HYCU.

l Nutanix Files licenses

You can use these licenses independently or in combination with standard licenses.

o Socket-based licenses

Licenses are based on the number of CPU sockets on all Nutanix clusters where theNutanix Files server that you plan to protect by using HYCU resides.

o Capacity-based licenses

Licenses are based on the capacity of Nutanix Files shares, which is calculatedautomatically as an overall size (in terabytes) of all protected Nutanix Files shares.

Considerationsl When verifying that your license is valid, HYCU takes into account only the sources

containing the entities with the PROTECTED or PROTECTED_DELETED status. Keep inmind that the protection of the HYCU backup controller is not taken into account.

l Nutanix Community Edition (CE) environment only. No HYCU licenses are required.

Procedure1. Buy a needed number of HYCU licenses. To discuss the options, contact your Sales

representative.

2. Create a license request. For details, see “Creating a license request” below.

3. Request and obtain licenses from the web licensing portal. For details, see “Requestingand retrieving licenses” on the next page.

4. Activate the licenses to start using HYCU. For details, see “Activating licenses” onpage 147.

Accessing the Licensing dialog box

To access the Licensing dialog box, clickAdministration, and then select Licensing.

Creating a license requestTo obtain your HYCU licenses, you should submit a request form to the web licensingportal.

10 Administering

146

Prerequisitesl You bought the required number of HYCU licenses and have an entitlement order

number.

l You added sources that you want to protect to the data protection environment. Forinstructions, see “Adding sources” on page 25.

To create a license request, follow these steps:

1. In the Licensing dialog box, click Download Request.

2. Save the license request file to a temporary location.

Examplelicense.req file:

CN myCompanyPID nutanixbackupND C0F90A56-3FCC-4437-A49C-EFBA9BNRP 3QTY 127AFS 3AFSCAP 4VER V1NHSUD FA8A5061C61F6BA5CE5A9B2C007EENEXT NODE

Requesting and retrieving licensesAfter you create a license request file, you can obtain the licenses from the licensing portal.To do so:

1. Connect to the web licensing portal at:

https://licensing.hycu.com/

2. If you already have a licensing portal account, click Sign in, enter your user name andpassword, and then click Login. Otherwise, create an account and then sign in with anewly created user account.

3. Click the Activate perpetual licenses link, and then enter the entitlement ordernumber. Click Next.

4. Perform the following:

a. Browse for the license request file, and then click Request License.

b. In the Activate perpetual licenses page, specify the license type (Standard licenses,Nutanix Files licenses, or both) and the number of licenses you want to activate. Bydefault, the number of licenses from the license request file is provided. You canspecify a different value that may not exceed the number of purchased licenses.Click Activate Licenses.

https://licensing.hycu.com/

10 Administering

147

Within a few minutes, you should receive an email with a license file license.dat

attached.

Examplelicense.dat file:

CN myCompanyPID nutanixbackupND C0F90A56-3FCC-4437-A49C-EFBA9BD8FC0FNRP 3AFSCAP 5EXP 02.08.2017VER V1NLK D29CB215357FED55304012B02143CA9437ED5D8FC556NEXT NODE

5. Save the license file locally.

Activating licensesAfter you submit your license request for the HYCU licenses to the web licensing portal, you

get an email with a product license file attached. Activate the licenses in HYCU as follows:

1. In the Licensing dialog box, click Upload License.

2. Browse for the license file that you received by email, and then click Upload.

After the licenses are activated, the information related to licensing is updated.

n Note You can always add new licenses for your grown environment. Contact yourHYCU Sales representative.

You can check the information related to licensing at any time. The following information isdisplayed in the Licensing dialog box:

l License type

l Backup controller ID

l Status

l Actual and licensed number of sockets

l Licensed number of sockets for Nutanix Files

l Actual and licensed Nutanix Files capacity

l Actual and licensed number of protected virtual and physical machines

Setting up loggingYou can set up logging to log information at various levels to help you analyze andtroubleshoot the entire HYCU operation and diagnose issues with backup and restoreperformance.

10 Administering

148

Accessing the Logging dialog box

To access the Logging dialog box, clickAdministration, and then select Logging.

In the Logging dialog box, you can do the following:

l Download the existing log file by clicking the Download logs link.

You download logs with the level that was specified at the time they were recorded. Iflogging is not set up, the logs are downloaded with the default settings. The changedlogging level is applied only to the logs that are recorded after you save new loggingsettings.

After you extract the zip file, check the log files at the following location:

/opt/grizzly/logs/

10 Administering

149

l Set up logging. To do so, follow these steps:1. Specify values for the following logging settings:

Logging setting Description

Maximum log file size(MiB)

The maximum size of a log file.The default log file size is 10 MiB, whereas the maximumlog file size is 10 GiB.

Number of log filesThe number of log files.The default number is 9.

Level

The following logging levels are available:

o Informational (default): Informational messagesabout the operation of HYCU are recorded to logfiles.

o Detailed: All activity is recorded to log files.

Nutanix REST calls level(Available only if theDetailed logging level isselected.)

The following levels are available:

o Off (default): Nutanix REST calls logs are notrecorded to log files.

o Informational: Informational messages about theoperations related to the Nutanix REST calls arerecorded to log files.

o Detailed: All activity related to the Nutanix RESTcalls is recorded to log files.

HYCU REST calls level(Available only if theDetailed logging level isselected.)

The following levels are available:

o Off (default): HYCU REST calls logs are not recordedto log files.

o Informational: Informational messages about theoperations related to the HYCU REST calls arerecorded to log files.

o Detailed: All activity related to the HYCU REST calls isrecorded to log files.

2. Use the Keep settings after upgrade switch if you want the custom loggingsettings to remain the same after you upgrade HYCU. As you usually set logging fortroubleshooting purposes and do not need the same logging level for a regular useof the product, by default, this switch is turned off.

3. Click Save.

n Note Keep in mind that the changed logging level is applied only to thelogs that are recorded after you save new logging settings.

10 Administering

150

You can later modify the settings by specifying new values and then clicking Save, or set thedefault values by clicking Default.

Changing the HYCU listening port numberThis section describes the steps you must perform if you want to change the HYCU listeningport number.

Accessing the Management Port dialog box

To access the Management Port dialog box, clickAdministration, and then selectManagement Port.

To change the listening port number of the HYCU web user interface, follow these steps:

1. In the Management Port dialog box, change the existing port number to the desiredone.

i Important Make sure that the port you choose is not used by any otherprocess. If a firewall is configured in your infrastructure, make sure that the port youchose is open.

2. Click Save.

Changing network settingsThis section describes the steps you must perform if you want to change your networksettings.

Accessing the Network dialog box

To access the Network dialog box, clickAdministration, and then selectNetwork.

To change network settings, follow these steps:

1. In the General tab of the Network dialog box, enter a new host name, the IP address,the netmask associated with the chosen IP address, and the IP address of the gatewaythat HYCU should use.

i Important Make sure that the IP address is set correctly so that it accuratelyreflects your network environment.

2. In the DNS Addresses tab, click Add to add a new DNS address.

If you want to delete any DNS address, clickDelete to the right of it.

3. In the Domains tab, click Add to add a new domain.

If you want to delete any existing domain, clickDelete to the right of it.

4. Click Save.

10 Administering

151

Setting power optionsYou can set power options for the HYCU backup controller so that its activities aresuspended or resumed.

Accessing the Power Options dialog box

To access the Power Options dialog box, clickAdministration, and then select PowerOptions.

Power option Description

Suspend

Pauses all HYCU backup controller activities.

If you want the HYCU backup controller activities to automaticallyresume after a specified amount of time, in the Auto resume after field,specify the number of hours (1–168) to pass before the activities areresumed.

All currently running jobs are allowed to complete normally. All jobsthat are in the queue will start when the HYCU backup controller isresumed. While activities are paused, you cannot start any new jobs.

Resume Allows HYCU backup controller activities to continue.

Configuring an SMTP serverBefore enabling HYCU to send email notifications, you must configure an SMTP server thatHYCU will use.

PrerequisiteOnly if you plan to use the STARTTLS or SSL/TLS security mode to secure email traffic. A validSSL certificate is imported to HYCU. For details on how to do this, see “Securing SMTPconnections” on page 172.

Accessing the SMTP Server Settings dialog box

To access the SMTP Server Settings dialog box, clickAdministration, and then selectSMTP Server Settings.

10 Administering

152

Procedure1. In the SMTP Server Settings dialog box, provide the following information:

Required information Description

Username User name of the account on the SMTP server.

Password Password of the account on the SMTP server.

Display name Display name of the email sender.

Hostname or IP address Host name or IP address of the SMTP server.

Port Port number to be used (usually set to 25).

Security modeProtocol used to secure email traffic—can be set to None,STARTTLS, or SSL/TLS.

From email address Email address from which email notifications will be sent.

2. Click Save.

You can now configure HYCU to send email notifications. For details on how to do this, see“Sending email notifications” on page 109.

Configuring the SSL certificateThis section describes the steps you must perform if you want to configure theSSL certificate.

Accessing the SSL Certificate dialog box

To access the SSL Certificate dialog box, clickAdministration, and then selectSSL Certificate.

In the SSL Certificate dialog box that appears, you can view the information about your SSLcertificate, such as the certificate holder's name, the certificate's expiry date, and thestrength of the certificate keys.

Depending on whether you want to create a new self-signed certificate or import a CAcertificate into HYCU, do one of the following:

l “Creating a new self-signed certificate” on the next page

l “Importing a CA certificate” on the next page

n Note It is recommended that you replace the default self-signed certificate with aCA signed certificate.

10 Administering

153

Creating a new self-signed certificateProcedure1. Click Regenerate.

2. Click Yes to confirm that you want to regenerate your SSL certificate.

Importing a CA certificateYou can import only CA certificates that are compliant with the PKCS#7 standard andencoded in the DER or PEM format. The HYCU backup controller holds only one customSSL certificate. When you import a new certificate, the previous certificate is discarded.

n Note If the certificate that you want to import uses a wildcard for the CommonName (CN), make sure that the Certificate Subject Alt Name field exists and contains thelist of all possible host names or FQDNs, and their corresponding IP addresses.Otherwise, the certificate may be recognized as invalid by your browser or hyCLI.

Procedure1. Click Import. The Import dialog box appears.

2. Browse for the following imported files:

l Private key: Click Browse to select the private key associated with the certificate tobe imported.

The private key should be generated with RSA algorithm and should beunencrypted. If it is a .pem file, the private key can be in PKCS#1 or PKCS#8 format,whereas if it is a .der file, it can be in PKCS#8 format only. The recommendedprivate key sizes are 2048 and 4096 bits.

l Public certificate: Click Browse to select the signed public part of the servercertificate corresponding to the private key.

l CA certificate/chain: This field is optional, if the public certificate contains CAcertificate/chain. Click Browse to select the certificate or chain of the signingauthority for the public certificate.

3. Click Import.

i Important Any changes that you make to your SSL certificate will result in anautomatic logoff.

Upgrading HYCUYou can upgrade HYCU when a new software version is available.

10 Administering

154

Prerequisitesl The source where the HYCU backup controller resides is added to HYCU.

l All the HYCU backup controller activities are suspended. For details on how to do this,see “Setting power options” on page 151.

l Jobs that you do not want to be aborted are finished (the upgrade process aborts allcurrently running jobs).

l The size of the HYCU data disk is greater than the size of the HYCU system disk. Forinstructions on how to increase disk size, see “Increasing the size of the HYCU virtualdisks” on page 176.

l Multi-network environments only. Make sure to download the util.migratenetwork.sh

script from the HYCU Support portal and then run it on the HYCU backup controller.

ConsiderationNutanix clusters only. If the HYCU backup controller is part of a Nutanix protection domain(the recommended approach), make sure that the new version of the HYCU backupcontroller virtual machine is included in this protection domain after the upgrade. The oldHYCU backup controller virtual machine will remain on the Nutanix cluster and will berenamed to: <HYCUBackupControllerName>_version_<OldHYCUVersion>. You can safelydelete it and remove it from Nutanix protection domain after you make sure that theupgrade finished successfully.

Proceduresl “Upgrading HYCU on a Nutanix AHV cluster” below

l “Upgrading HYCU on a Nutanix ESXi cluster” on page 156

l “Upgrading HYCU in a vSphere environment” on page 161

Upgrading HYCU on a Nutanix AHV clusterPrerequisitesl A snapshot of the HYCU backup controller is created by using the Nutanix protection

domain. For details, see Nutanix documentation.

l The HYCU system disk is selected as the boot device in the Disks section of the UpdateVM dialog box in the Nutanix Prism web console.

l The state of the HYCU virtual appliance image that you want to use for an upgrade isACTIVE in the Nutanix Prism image service.

For details, see Nutanix documentation.

ConsiderationsOnly if HYCU is used for file share protection.

https://support.hycu.com/hc/en-us

10 Administering

155

l The HYCU instances residing on a Nutanix AHV cluster are upgraded automaticallyduring the HYCU upgrade process if the following is true:

o The Nutanix cluster where the HYCU instances reside is added to HYCU.

o The HYCU virtual appliance image is present on the same Nutanix cluster in thefollowing format:



Otherwise, follow the HYCU upgrade procedure to perform the HYCU instance upgrade.

l After a HYCU instance is upgraded, its MAC address changes. If you need the upgradedHYCU instance to have the same MAC address as before the upgrade, delete the NIC onthe HYCU instance virtual machine and recreate it with the desired MAC address. Fordetails on how to do this, see Nutanix documentation.

Procedure1. Log on to the Nutanix Prism web console, and then upload the HYCU virtual appliance

image that you want to use for an upgrade to your Nutanix AHV cluster as follows:

a. Click , and then select Image Configuration.

b. In the Image Configuration dialog box, click Upload Image.

c. In the Create Image dialog box, provide the following information:

i. Enter a HYCU image name in the format that should correspond to that of theHYCU image file you are uploading.

i Important The HYCU virtual appliance image must be uploaded tothe Nutanix AHV cluster in the following format:


For example: hycu-4.0.0-3634

If you enter the HYCU image name in a different format, you will not be ableto use this image for an upgrade.

ii. Optional. Enter an annotation.

iii. From the Image Type drop-down menu, selectDISK.

iv. From the Storage Container drop-down menu, select a storage container forthe image to be uploaded.

v. In the Image Source section, specify the location of the image file.

vi. Click Save.

vii. Click Close after the image is successfully uploaded.

2. Log on to the HYCU web user interface, and then do as follows:

10 Administering

156

a. ClickAdministration, and then selectUpgrade Software.

b. In the Upgrade Software dialog box, check the current version of HYCU and allavailable versions.

c. From the list of the available versions, select the one to which you want to upgradeHYCU, and then click Upgrade.

d. Click Yes to confirm that you want to upgrade HYCU.

3. Only if HYCU is used for file share protection. If the Nutanix cluster where the HYCUinstances reside is not added to HYCU or the appropriate HYCU virtual appliance imageis not present on the same Nutanix cluster, upgrade the HYCU instances as follows:

a. Remove the existing HYCU instances. For details on how to do this, see “Deleting aHYCU instance” on page 144.

b. Create new HYCU instances with the latest HYCU version. For details on how to dothis, see “Creating a HYCU instance by using the HYCU web user interface” onpage 142.

You will be logged out of HYCU and you can track the upgrade progress in the NutanixPrism web console as follows:

l The old HYCU backup controller virtual machine will remain on the Nutanix AHV clusterand will be renamed to <HYCUBackupControllerName>_version_<OldHYCUVersion>.

l The new upgraded HYCU backup controller virtual machine will replace the old one.

l The upgraded HYCU backup controller virtual machine will be powered onautomatically.

After the upgrade process completes, you can log on to the HYCU web user interface.

i Important Before you log on to HYCU, make sure to perform a hard reload of theHYCU webpage in your browser.

After you make sure HYCU was upgraded successfully, you can safely delete the old HYCUbackup controller virtual machine from the Nutanix AHV cluster.

Upgrading HYCU on a Nutanix ESXi clusterTo upgrade HYCU on a Nutanix ESXi cluster, you can choose one of the followingapproaches:

Upgrade approach Instructions

By importing the HYCU OVFpackage to a content library.

“Upgrading HYCU by importing the HYCU OVFpackage to a content library” on the next page

By deploying the HYCU OVFpackage to a vCenter Serverinventory.

“Upgrading HYCU by deploying the HYCU OVFpackage to a vCenter Server inventory” on page 158

10 Administering

157

If HYCU is used for file share protection, the HYCU instances that are connected to yourHYCU backup controller must also be upgraded. For details, see “Upgrading HYCUinstances” on page 160

Prerequisitesl A snapshot of the HYCU backup controller is created by using the Nutanix protection

domain. For details, see Nutanix documentation.

l Any HYCU snapshots created by using VMware vSphere are removed.

LimitationUpgrading HYCU by using the OVF package imported to a content library is not supportedwith vSphere 6.0.

Upgrading HYCU by importing the HYCU OVF package to acontent library

Procedure1. Log on to the VMware vSphere Web Client, and then do as follows:

a. Navigate to the content library to which you want to import the HYCU OVF package.

b. Right-click your content library, and then select Import Item. The Import LibraryItem dialog box opens.

c. In the Source section, specify the location of the OVF package:


Local file


i Important When you are browsing your file system,make sure to select both the .ovf file and the .vmdk filerelated to the OVF package.

Click OK.

d. In the Destination section, enter a name and description for the item, and then clickOK.

i Important Make sure the item name you enter matches the HYCU OVFpackage name. For example, hycu-4.0.0-3634.



b. Only if the credentials for the vCenter Server are not provided. In the Upgrade Softwaredialog box, do the following:

i. Enter the name of the vCenter Server registered with the Nutanix ESXi cluster onwhich the HYCU backup controller resides.

10 Administering

158

ii. Enter the user name and password of a vSphere user with the requiredupgrade privileges. For details on upgrade privileges, see “Assigning privilegesto a vSphere user” on page 177.

iii. Click Next.

c. Check the current version of HYCU and all available versions, and then, from the listof the available versions, select the one to which you want to upgrade HYCU.

d. Click Upgrade.

e. Click Yes to confirm that you want to upgrade HYCU.


l The old HYCU backup controller virtual machine will remain on the Nutanix ESXi clusterand will be renamed to <HYCUBackupControllerName>_version_<OldHYCUVersion>.





After you make sure HYCU was upgraded successfully, you can safely delete the old HYCUbackup controller virtual machine from the Nutanix ESXi cluster.

Upgrading HYCU by deploying the HYCU OVF package to avCenter Server inventory


a. Right-click your vCenter Server, and then selectDeploy OVF Template.... TheDeploy OVF Template dialog box opens.

b. In the Select template section, specify the location of the OVF package:


Local file



Click Next.

c. In the Select name and location section, enter a name for the HYCU backup

10 Administering

159

controller virtual machine and specify a location where you want to deploy it, andthen click Next.

i Important Make sure the virtual machine name you enter matches theHYCU OVF package name. For example, hycu-4.0.0-3634.

d. In the Select a resource section, select where to run the deployed package, andthen click Next.

e. In the Review details section, verify the package details, and then click Next.

f. In the Select storage section, select where to store the files for the deployedpackage, and then click Next.

g. In the Select networks section, select a destination network, and then click Next.

h. In the Customize template section, enter the values for the following:









Click Next.

i. In the Ready to complete section, review data, and then click Finish.



b. Only if the credentials for the vCenter Server are not provided. In the Upgrade Softwaredialog box, do the following:

i. Enter the name of the vCenter Server registered with the Nutanix ESXi cluster onwhich the HYCU backup controller resides.

ii. Enter the user name and password of a vSphere user with the requiredupgrade privileges. For details on upgrade privileges, see “Assigning privilegesto a vSphere user” on page 177.

iii. Click Next.

c. Check the current version of HYCU and all available versions, and then, from the listof the available versions, select the one to which you want to upgrade HYCU.

10 Administering

160

d. Click Upgrade.

e. Click Yes to confirm that you want to upgrade HYCU.


l The old HYCU backup controller virtual machine will remain on the Nutanix ESXi clusterand will be renamed to <HYCUBackupControllerName>_version_<OldHYCUVersion>.





After you make sure HYCU was upgraded successfully, you can safely delete the old HYCUbackup controller virtual machine from the Nutanix ESXi cluster.

Upgrading HYCU instancesAn upgrade of the HYCU instances residing on a Nutanix ESXi cluster starts automaticallyafter the HYCU upgrade if the following is true:

l The HYCU OVF package is imported to the vCenter Server content library and its formatis as follows:



l The Nutanix ESXi cluster where the HYCU backup controller is deployed is added toHYCU and the credentials for the vCenter Server associated with this Nutanix cluster areprovided. To specify credentials, follow these steps:

1. Access the Sources dialog box by clickingAdministration, and then selectingSources.

2. Select the Nutanix ESXi cluster where the HYCU instance resides, and then clickEdit .

3. In the Edit dialog box, click Next.

4. In the vSphere Credentials dialog box, enter the URL of the vCenter Server to whichyour Nutanix ESXi cluster is registered and the user name and password of a userwith specific privileges for vCenter Servers.

5. In the Summary dialog box, verify that the validation was successful, and then clickSave.

Otherwise, upgrade the HYCU instances manually as follows:

1. Remove the existing HYCU instances. For details on how to do this, see “Deleting aHYCU instance” on page 144.

10 Administering

161

2. Create new HYCU instances with the latest HYCU version. For details on how to do this,see “Creating a HYCU instance by using the HYCU web user interface” on page 142.

n Note If you made any changes to the default user credentials, after the HYCUinstance upgrade, you can use only the default operating system user credentials:User name: hycuPassword: hycu/4u

Later you can make modifications to meet the needs of y our environment.

Upgrading HYCU in a vSphere environmentTo upgrade HYCU in a vSphere environment, you can choose one of the followingapproaches:

Upgrade approach Instructions

By importing the HYCU OVFpackage to a content library.

“Upgrading HYCU by importing the HYCU OVFpackage to a content library” on the next page

By deploying the HYCU OVFpackage to a vCenter Serverinventory.

“Upgrading HYCU by deploying the HYCU OVFpackage to a vCenter Server inventory” on page 163

Prerequisitesl As a vSphere user, you have the required upgrade privileges. For details on upgrade

privileges, see “Assigning privileges to a vSphere user” on page 177.

l Only if importing the HYCU OVF package to a content library. A content library is created inthe VMware vSphere Web Client.

LimitationUpgrading HYCU by using the OVF package imported to a content library is not supportedwith vSphere 6.0.

ConsiderationOnly if the HYCU backup controller is connected to a distributed switch. After the upgrade, theport configured on the upgraded HYCU backup controller is different from the distributedswitch port configured on the old HYCU backup controller. If you need your upgradedHYCU backup controller to use the same port as before, delete the port on the old HYCUbackup controller, and then modify the port number in the new HYCU backup controllersettings. For details on how to do this, see VMware documentation.

10 Administering

162

Upgrading HYCU by importing the HYCU OVF package to acontent library


a. Navigate to the content library to which you want to import the HYCU OVF package.

b. Right-click your content library, and then select Import Item. The Import LibraryItem dialog box opens.

c. In the Source section, specify the location of the OVF package:


Local file



Click OK.

d. In the Destination section, enter a name and description for the item, and then clickOK.

i Important Make sure the item name you enter matches the HYCU OVFpackage name. For example, hycu-4.0.0-3634.






You will be logged out of HYCU and you can track the upgrade progress in the VMwarevSphere Web Client as follows:

l The old HYCU backup controller virtual machine will remain in the vSphereenvironment and will be renamed to <HYCUBackupControllerName>_version_

<OldHYCUVersion>.




i Important Before you log on to HYCU, make sure to perform a hard reload of the

10 Administering

163

HYCU webpage in your browser.

After you make sure HYCU was upgraded successfully, you can safely delete the old HYCUbackup controller virtual machine from the vSphere environment.

Upgrading HYCU by deploying the HYCU OVF package to avCenter Server inventory


a. Right-click your vCenter Server, and then selectDeploy OVF Template.... TheDeploy OVF Template dialog box opens.

b. In the Select template section, specify the location of the OVF package:


Local file



Click Next.

c. In the Select name and location section, enter a name for the HYCU backupcontroller virtual machine and specify a location where you want to deploy it, andthen click Next.

i Important Make sure the virtual machine name you enter matches theHYCU OVF package name. For example, hycu-4.0.0-3634.

d. In the Select a resource section, select where to run the deployed package, andthen click Next.

e. In the Review details section, verify the package details, and then click Next.

f. In the Select storage section, select where to store the files for the deployedpackage, and then click Next.

g. In the Select networks section, select a destination network, and then click Next.

i Important Make sure not to select a vSphere distributed switch(dvSwitch) for the virtual NIC option.

h. In the Customize template section, enter the values for the following:



10 Administering

164







Click Next.

i. In the Ready to complete section, review data, and then click Finish.






You will be logged out of HYCU and you can track the upgrade progress in the VMwarevSphere Web Client as follows:

l The old HYCU backup controller virtual machine will remain in the vSphereenvironment and will be renamed to <HYCUBackupControllerName>_version_

<OldHYCUVersion>.





After you make sure HYCU was upgraded successfully, you can safely delete the old HYCUbackup controller virtual machine from the vSphere environment.

Removing HYCUWhen you remove HYCU from your environment, you also need to perform additionalcleanup tasks.

To remove HYCU, follow these steps:

10 Administering

165

1. Log on to HYCU, and then unassign policies from all entities as follows:

l To unassign policies from virtual machines:

a. In the navigation pane, click Virtual Machines.

b. Select all virtual machines, and then clickPolicies.

c. Click Unassign.

d. Click Yes to confirm that you want to unassign the policies from the selectedvirtual machines.

l To unassign policies from applications:

a. In the navigation pane, click Applications.

b. Select all discovered applications, and then clickPolicies.

c. Click Unassign.

d. Click Yes to confirm that you want to unassign the policies from the selectedapplications.

l To unassign policies from file shares:

a. In the navigation pane, clickShares.

b. Select all file shares, and then clickPolicies.

c. Click Unassign.

d. Click Yes to confirm that you want to unassign the policies from the selected fileshares.

2. Only if HYCU was used for file share protection. Do the following:

a. Remove the existing HYCU instances. For instructions, see “Deleting a HYCUinstance” on page 144.

b. Remove the Nutanix Files snapshots created by HYCU. To do so, on the HYCUbackup controller, run the /opt/grizzly/bin/HycuCleanup.pl script as follows:

sudo perl HycuCleanup.pl -c <NutanixFilesServer> -u <Username> -p<Password> -dnfs -all

In this instance, <NutanixFilesServer> is the name of the Nutanix Files server inthe following format: https://<ServerName>:<Port>.

i Important By running this command, you will also remove all NutanixFiles snapshots whose names start with hycu- (case insensitive).

3. Nutanix clusters only. On the HYCU backup controller, run the/opt/grizzly/bin/HycuCleanup.pl script as follows:

l To remove virtual machine snapshots created by HYCU:

sudo perl HycuCleanup.pl -c <NutanixCluster> -u <Username> -p<Password> -dvms -all

10 Administering

166

In this instance, <NutanixCluster> is the name of the Nutanix cluster in thefollowing format: https://<ServerName>:<Port>.

i Important By running this command, you will also remove all third-partysnapshots created by using Nutanix REST API v3 whose names start with theIP address.

l To remove volume groups created by HYCU:

sudo perl HycuCleanup.pl -c <NutanixCluster> -u <Username> -p<Password> -dvg -all

In this instance, <NutanixCluster> is the name of the Nutanix cluster in thefollowing format: https://<ServerName>:<Port>.

i Important By running this command, you will also remove all volumegroups created by using Nutanix REST API v3 whose names start with HYCU-

(case insensitive).

4. Remove data from targets. To do so, on each target, delete the bkpctrl folder.

5. Log on to the Nutanix Prism web console or the VMware vSphere Web Client, and thendelete the HYCU backup controller virtual machine. For details on how to delete avirtual machine, see Nutanix or VMware documentation.

167

Tuning your data protectionenvironmentAdministration tasks that you perform through theAdministration menu to customizeHYCU for your data protection environment are usually sufficient to successfully manage it.However, sometimes the needs of your organization require additional administrationtasks to be performed for optimal performance, a higher security level, or interaction withexternal applications, as well as for taking advantage of a broader spectrum of HYCUoptions.


Access the HYCU backup controller virtualmachine by using SSH.

“Accessing the HYCU backup controllervirtual machine by using SSH” on the nextpage

Enable HTTPS for WinRM connections.“Enabling HTTPS for WinRM connections”on page 169

Configure FIPS-compliant mode for HYCU.“Configuring FIPS-compliant mode forHYCU” on page 170

Set up LDAPS authentication.“Setting up LDAPS authentication” onpage 171

Secure SMTP connections. “Securing SMTP connections” on page 172

Set up HYCU to use multiple networks.“Setting up HYCU to use multiple networks”on page 173

Increase the size of the HYCU virtual disks.“Increasing the size of the HYCU virtualdisks” on page 176

Assign required backup privileges to avSphere user.

“Assigning privileges to a vSphere user” onpage 177

Use the HYCU REST API to automate tasks.“Using the HYCU REST API Explorer” onpage 179

Use hyCLI. “Using the command-line interface” on

Chapter 11

11 Tuning your data protection environment

168


page 179

Accessing the HYCU backup controller virtualmachine by using SSHYou can perform most administrative tasks of the HYCU backup controller by using theHYCU web user interface or command-line user interface (hyCLI). The only two exceptionsfor which you should use SSH are restarting the HYCU web server (the Grizzly server) or theentire appliance.

i Important Using SSH to perform any tasks other than restarting the HYCU webserver or the entire appliance is not recommended.

After you deploy the HYCU virtual appliance, you can use the following default credentials toaccess the HYCU backup controller virtual machine by using SSH:

User name: hycu

Password: hycu/4u

Changing the default SSH passwordFor security purposes, it is highly recommended that you change the default SSH password.To do so, follow these steps:

1. Open a remote session to the HYCU backup controller virtual machine:

ssh hycu@<HYCUBackupControllerIPAddress>

When requested, enter the default password.

2. Change the password for the hycu user:

passwd

When requested, enter the default password again, and then enter and verify your newpassword.

Disabling SSH accessYou can disable SSH access at any time. To do so, follow these steps:



When requested, enter the password for the hycu user.

2. Shut down the SSH service:


169

sudo service sshd stop


3. Disable the SSH service:

sudo chkconfig sshd off

If requested, enter the password for the hycu user.

After performing this procedure, your SSH connection will be disabled. To re-enable SSH,you need to connect to the HYCU backup controller virtual machine through the NutanixPrism web console.

Managing the HYCUweb serverTo manage the HYCU web server, follow these steps:




2. Perform the desired operation on the HYCU web server:

sudo service grizzly {start | stop | restart}


Enabling HTTPS forWinRM connectionsIf you want to add an additional layer of security, you can configure HYCU to use HTTPS forWinRM connections to virtual machines.

PrerequisiteThe winrm.https.enabled configuration setting is set to true. For details, see “CustomizingHYCU configuration settings” on page 188.

For each virtual machine for which you want to enable HTTPS for WinRM connections, dothe following:

1. Set up a virtual machine for WinRM over HTTPS by using PowerShell:

a. Create a new self-signed certificate:

$cert = New-SelfSignedCertificate -Type Custom -Subject"CN=<Hostname>" -CertStoreLocation "Cert:\LocalMachine\My"-TextExtension @("2.5.29.37={text}1.3.6.1.5.5.7.3.1")

b. Only if an HTTPS WinRM listener already exists. Remove the existing HTTPS WinRMlistener:


170

winrm delete winrm/config/Listener?Address=*+Transport=HTTPS

c. Recommended. Remove the HTTP WinRM listener if it exists:

winrm delete winrm/config/Listener?Address=*+Transport=HTTP

d. Create an HTTPS WinRM listener that uses the self-signed certificate from step 1:

New-Item -Path WSMan:\LocalHost\Listener -Transport HTTPS -Address *-CertificateThumbPrint $cert.Thumbprint -Force

e. Add a new firewall rule to allow incoming connections on TCP port 5986, if it hasnot already been added:

New-NetFirewallRule -DisplayName 'Windows Remote Management(HTTPS-In)' -Name 'Windows Remote Management (HTTPS-In)'-Profile Any -LocalPort 5986 -Protocol TCP

2. Open a remote session to the HYCU backup controller, and then do the following:

a. Run the add_certificate.sh script:

sudo /opt/grizzly/bin/add_certificate.sh <Hostname>

In this instance, <Hostname> is the host name of the virtual machine for which youwant to establish an HTTPS connection.

b. Enter the password to access the trust store. The default password is hycu/4u.

After you run the add_certificate.sh script, it connects to the virtual machine,imports the self-signed certificate, and adds it to the trust store. You get the informationabout the certificate that you must check and confirm. If the certificate is valid andmatches the information of the certificate on the virtual machine, type y followed byEnter. Otherwise, type n followed by Enter to reject the certificate.

Configuring FIPS-compliant mode for HYCUHYCU can be configured to operate in a way that is compliant with the Federal InformationProcessing Standards (FIPS), which establish security requirements for cryptographymodules (which encryption algorithms and methods for generating encryption keys can beused).

HYCU employs a FIPS-compliant security provider that uses a cryptographically strongrandom number generator (RNG). For the RNG to generate truly random numbers, anadequate source of entropy is required. Because HYCU is running on a virtual machine, theamount of entropy that is available to it is limited and therefore an additional hardwaresource of entropy is needed. This source is usually provided by the real CPU or chipset. Toenable access to this hardware entropy source, an additional service (rngd.service) isenabled on the HYCU backup controller.


171

Depending on the nature of your business, you can either enable or disable FIPS-compliantmode for HYCU.

LimitationWhen FIPS-compliant mode is enabled, you cannot assign credentials to Linux virtualmachines, and consequently restore individual files.

Enabling FIPS-compliant mode for HYCUTo enable FIPS-compliant mode for HYCU, as the root user or by using sudo, do thefollowing:

1. Stop the HYCU web server:

systemctl stop grizzly.service

2. Enable FIPS-compliant mode:

/opt/grizzly/bin/enable_fips.sh

3. Start the HYCU web server:

systemctl start grizzly.service

Disabling FIPS-compliant mode for HYCUIf the nature of your business changes, you can easily disable FIPS-compliant mode. To doso, as the root user or by using sudo, do the following:

1. Stop the HYCU web server:

systemctl stop grizzly.service

2. Disable FIPS-compliant mode:

/opt/grizzly/bin/enable_fips.sh -d

3. Start the HYCU web server:

systemctl start grizzly.service

Setting up LDAPS authenticationIf you want to add an extra layer of protection and ensure the confidentiality of data, youcan configure HYCU to use LDAP over SSL (LDAPS) for secure user authentication. For thisauthentication to work, the LDAPS server certificate must be imported to HYCU.

To import the LDAPS server certificate to HYCU, open a remote session to the HYCU backupcontroller, and then do the following:


172

1. Run the add_certificate.sh script:

sudo /opt/grizzly/bin/add_certificate.sh <Hostname> <Port>

In this instance, <Hostname> is the LDAPS server host name and <Port> is theLDAPS port (usually 636).

2. Enter the keystore password. The default password is hycu/4u.

After you run the add_certificate.sh script, it connects to the LDAPS server, importsthe certificate, and adds it to the keystore.

You get the information about the certificate that you must check and confirm. If thecertificate is valid and matches the information of the certificate on the LDAPS server,type y followed by Enter. Otherwise, type n followed by Enter to reject the certificate.

Securing SMTP connectionsIf you are using STARTTLS or SSL/TLS for SMTP connections, you must import an SSLcertificate to HYCU. Depending on the protocol you use to secure email traffic, see one ofthe following sections:

l “Importing an SSL certificate for the STARTTLS security mode” below

l “Importing an SSL certificate for the SSL/TLS security mode” on the next page

Importing an SSL certificate for theSTARTTLS security modeProcedureOpen a remote session to the HYCU backup controller, and then do the following:

1. Run the add_certificate_starttls.sh script:

sudo /opt/grizzly/bin/add_certificate_starttls.sh <Hostname> <Port>

In this instance, <Hostname> is the SMTP server host name and <Port> is the port forauthenticated SMTP connections (587 or 25).


After you run the add_certificate_starttls.sh script, it connects to the SMTP server,imports the certificate, and adds it to the keystore.

You get the information about the certificate that you must check and confirm. If thecertificate is valid and matches the information of the certificate on the SMTP server,type y followed by Enter. Otherwise, type n followed by Enter to reject the certificate.


173

Importing an SSL certificate for the SSL/TLS securitymodeProcedureOpen a remote session to the HYCU backup controller, and then do the following:

1. Run the add_certificate.sh script:

sudo /opt/grizzly/bin/add_certificate.sh <Hostname> <Port>

In this instance, <Hostname> is the SMTP server host name and <Port> is the port forauthenticated SMTP connections (465).


After you run the add_certificate.sh script, it connects to the SMTP server, importsthe certificate, and adds it to the keystore.

You get the information about the certificate that you must check and confirm. If thecertificate is valid and matches the information of the certificate on the SMTP server,type y followed by Enter. Otherwise, type n followed by Enter to reject the certificate.

Setting up HYCU to use multiple networksYou can set up HYCU to operate in a multi-network environment, allowing it to have twonetwork adapters assigned to different VLANs or network segments. This is especiallyuseful if you have a dedicated storage used for backups in a different network than HYCU.For example, HYCU could be located on the 10.0.0.0/16 VLAN and a storage box could belocated on the 192.168.0.0/24 VLAN.

n Note Nutanix clusters only. While the bulk of data traffic during a backup takes placeover the additional network, part of it is still done through the management network.This is because HYCU uses the Nutanix data services IP address to consume datathrough Nutanix Volumes, which must be in the same subnet as the managementnetwork of the CVMs.

For details on this limitation, see Nutanix documentation.

Nutanix Files environment considerationsl The first connection ("Wired connection 1") must correspond to a network segment

where both the HYCU backup controller and the additional HYCU instances can see andestablish a connection to each other.

l Both virtual machines (the HYCU backup controller and one or more connected HYCUinstances) must be able to connect to the Nutanix Files server.


174

l Nutanix AHV cluster only. When upgrading HYCU, all additional network adapters will beremoved from the instance. Make sure to reconfigure the HYCU instance after theupgrade.

l Nutanix ESXi cluster only. When upgrading HYCU, network settings on all additionalnetwork adapters will be set to the default values. Make sure to reconfigure the HYCUinstance after the upgrade.

Depending on the environment in which you want to set up HYCU to use multiplenetworks, perform one of the following procedures:

l “Setting up HYCU to use multiple networks on a Nutanix AHV or ESXi cluster” below

l “Setting up HYCU to use multiple networks in a vSphere environment” on the next page

Setting up HYCU to use multiple networks on aNutanix AHV or ESXi clusterTo set up HYCU to use multiple networks on a Nutanix AHV or ESXi cluster, follow thesesteps:

1. Log on to the Nutanix Prism web console, and then add an additional network adapter:

a. In the menu bar, click Home, and then select VM.

b. Click the Table tab to display the VM Table view, and then, from the list of virtualmachines, select your HYCU virtual machine.

c. Click Update, and then navigate to the Network Adapters (NIC) section.

d. Click Add New NIC, and then, from the VLAN Name drop-down menu, select therequired VLAN.

e. Click Add.

f. Click Save.


2. Configure the network. To do so, depending on how the VLAN is set up, select one ofthe following approaches:

l VLAN has IP address management enabled

Assign the IP address directly from the Nutanix Prism web console.

l VLAN does not have IP address management enabled

Configure the network manually:

a. Open a remote session to the HYCU backup controller virtual machine:


b. Run the sudo nmtui command to edit the respective "Wired connection x".

i Important When configuring the network, assign each connection


175

specifically to a network interface. Note the following:

l The "Wired connection 1" connection must be assigned to the first (for example,eth0) network interface.

l The rest of connections must be named in accordance with the first one ("Wiredconnection 2", "Wired connection 3", and so on).

After the new network adapter is properly configured, you can add a target located on theother VLAN to HYCU.

Setting up HYCU to use multiple networks in avSphere environmentTo set up HYCU to use multiple networks in a vSphere environment, follow these steps:

1. Log on to the VMware vSphere Web Client, and then add an additional networkadapter:

a. Click the VMs tab, and then navigate to your HYCU backup controller.

b. Right-click the HYCU backup controller, and then select Edit Settings.

c. From the New device drop-down menu, selectNetwork, and then click Add.

d. From the New Network drop-down menu, select the required network.

i Important Make sure not to select a vSphere distributed switch(dvSwitch) for the virtual NIC option.

e. Click OK.

For details, see VMware documentation.

2. Configure the network manually:

a. Open a remote session to the HYCU backup controller virtual machine:


b. Run the sudo nmtui command to edit the respective "Wired connection x".

i Important When configuring the network, assign each connectionspecifically to a network interface. Note the following:

l The "Wired connection 1" connection must be assigned to the first (for example,eth0) network interface.

l The rest of connections must be named in accordance with the first one ("Wiredconnection 2", "Wired connection 3", and so on).

After the new network adapter is properly configured, you can add a target located onthe other network to HYCU.


176

Increasing the size of the HYCU virtual disksIf you are running out of disk space on your HYCU backup controller, you can increase thesize of the HYCU virtual disks as needed. To do so, follow the instructions in one of thefollowing sections:

l “Increasing the size of the HYCU disks in a Nutanix AHV cluster” below

l “Increasing the size of the HYCU disks in a Nutanix ESXi cluster or vSphere environment”below

Increasing the size of the HYCU disks in a NutanixAHV clusterTo increase the size of the HYCU system disk and/or data disk in a Nutanix AHV cluster,follow these steps:




4. From the list of virtual machines, select your HYCU backup controller, and then clickPower Off Actions followed by Power off to shut it down.


5. Click Update, and then do the following:

a. Navigate to the Disks section, and then click Edit next to the HYCU disk whose sizeyou want to increase.

b. In the Size (GiB) field, increase the size of the disk as required.

c. Only if increasing the size of both HYCU disks. Repeat steps a and b for the other HYCUdisk.

d. Click Update.

6. Click Power on to turn on the HYCU backup controller.

Increasing the size of the HYCU disks in a NutanixESXi cluster or vSphere environmentTo increase the size of the HYCU system disk and/or data disk in a Nutanix ESXi cluster orvSphere environment, follow these steps:

1. Log on to the VMware vSphere Web Client.

2. Click the VMs tab, and then navigate to your HYCU backup controller.

3. Right-click the HYCU backup controller, and then select Power > Power Off to shut it


177

down.


4. Right-click the HYCU backup controller, and then select Edit Settings.

5. On the Virtual Hardware tab, increase the size of one or both HYCU disks by enteringnew values in the Hard disk 1 and/or Hard disk 2 fields, and then click OK.

6. Right-click the HYCU backup controller, and then select Power > Power On to turn iton.

For details on how to manage a virtual machine in a Nutanix AHV or ESXi cluster, seeNutanix documentation. For details on how to manage a virtual machine in a vSphereenvironment, see VMware documentation.

Assigning privileges to a vSphere userYou can assign required privileges to a user by using the VMware vSphere Web Client. Todo so, follow these steps:

1. Log on to the VMware vSphere Web Client as an administrator.

2. On the Home page, click Roles.

3. Right-click the Roles tab information panel, and then click Add.

4. Type a name for the new role (for example, HYCU).

5. Select the required privileges for the role, and then click OK.

Privilegecategory

Backup privileges Restore privilegesUpgrade and HYCUinstance creationprivileges

Datastore

l Browsedatastore

l Low level fileoperations

l Allocate space

l Allocate space

l Low level fileoperations

Globall Disable methods

l Enable methodsl N/A l N/A

Host > Localoperations

l N/A

l Create virtualmachine

l Delete virtualmachine

l Reconfigurevirtual machine

l N/A

Network l N/A l Assign network l Assign network


178

Privilegecategory


l Configure

vApp l N/A l N/A l Import

Virtual Machine> Configuration

l Disk changetracking

l Settings

l All privileges

l Add existing disk

l Add new disk

l Add or removedevice

l Settings

l Remove disk

l Rename

Virtual Machine> Interaction

l Power On

l Answer question

l Power Off

l Power On

l Power On

Virtual Machine> Inventory

l N/A

l Create new

l Register

l Remove

l Unregister

l Create fromexisting

l Remove

Virtual Machine> Provisioning

l Allow read-onlydisk access

l Allow virtualmachinedownload

l Only if backing upa template. Markas template

l Only if backing upa template. Markas virtualmachine

l Allow disk access l Clone virtualmachine

Virtual Machine> Snapshotmanagement

l Create snapshot

l Removesnapshot

l N/A l N/A

Resource l N/A l Assign virtual l N/A


179

Privilegecategory


machine toresource pool

For details, see VMware documentation.

Using the HYCU REST API ExplorerHYCU provides a REST API that can be used by external applications to interact with theHYCU backup controller, retrieve information from it, and automate tasks. All functionalityexposed through the HYCU user interface is also available through the HYCU REST API. Youcan use the HYCU REST API Explorer to interact with the API and view the expected inputand output formats for each endpoint.

To access the HYCU REST API Explorer, follow these steps:

1. Click at the upper right of the screen, and then select REST API Explorer. The HYCUREST API Explorer opens.

2. In the list of functionality groups, you can expand the desired group by clicking ListOperations. A list of API endpoints is displayed.

3. Click any of the endpoints to show the description, the parameters, and the outputformat. You can fill in the fields, and then click Try it out! to call an API and get outputdata.

Using the command-line interfaceYou can manage your data protection environment also by using the HYCU command-lineuser interface (hyCLI). hyCLI provides the functionality comparable to the HYCU web userinterface and enables you to implement scripts for automating certain tasks.

To enable the usage of hyCLI, follow these steps:

1. Download the hycli.zip package. To do so, click at the upper right of the screen,and then selectDownload hyCLI.

2. Save and extract the hyCLI.zip file to any location on your system.

3. Add the folder containing the extracted files to the PATH environment variable.

n Note hyCLI log files are located at .Hycu/log in the user's home directory. You canchange logging settings for hyCLI in the logging.properties and log4j.properties

files located in the directory containing the extracted files.

For detailed information about hyCLI, see the README.txt file that you can find in thedirectory containing the extracted files.


180

For more information on the hyCLI structure, commands, and usage, run the hycli help

command.

181

Managing HYCU backupcontrollersHYCU Manager is designed to provide you with the visibility you need to proactively monitorall your HYCU data protection environments, allowing you to view and manage many HYCUbackup controllers across many environments from a single console. With HYCU Manager,all registered HYCU backup controller data is consolidated at one place from where youhave the easy accessibility to the collected information.

After you deploy the HYCU virtual appliance in the HYCU Manager mode, you can access theHYCU Manager console and take advantage of this intuitive visualization approach toquickly identify and address potential issues.

Using the HYCU Manager consoleThe HYCU Manager console provides you with an at-a-glance overview of the data collectedfrom all the HYCU backup controllers in all the data protection environments for which youare responsible.

Accessing the Console panel

To access the Console panel, in the navigation pane, clickConsole.

The following image shows an example of the HYCU Manager console:

Chapter 12

12 Managing HYCU backup controllers

182

You can find the following information within each widget:

Console widget Description

Policies

Number of all policies and the exact number of compliant anduncompliant policies in your data protection environments. A policy isconsidered compliant if all entities that have this policy assigned arecompliant with the RPO and RTO requirements.

BackupController

Number of available and unavailable HYCU backup controllers in yourdata protection environments.

BackupsPercentage of successful backups and the exact number of successfuland failed backups in your data protection environments.

TargetsNumber of all targets and the exact number of free and used targets inyour data protection environments.

SharesNumber of all file shares and the exact number of protected andunprotected file shares in your data protection environments.

Virtual MachinesNumber of all virtual machines and the exact number of protected andunprotected virtual machines in your data protection environments.

ApplicationsNumber of all applications and the exact number of protected andunprotected applications in your data protection environments.

i Important By clicking a value in any of the widgets, you are directed to theBackup Controllers panel where you can view a list of the HYCU backup controllerssorted by the value you clicked. For example, if you click the number of compliant


183

policies, the HYCU backup controllers in the Backup Controllers panel are sorted by thepolicy compliancy percentage in descending order.

Managing your HYCU backup controllersYou can use the Backup Controllers panel to add, edit, and remove the HYCU backupcontrollers, as well as to view all the required information about each HYCU backupcontroller.

Accessing the BackupControllers panel

To access the Backup Controllers panel, in the navigation pane, clickBackupControllers.

Adding a HYCU backup controllerProcedure1. ClickAdd. The New Backup Controller dialog box opens.

2. Enter the name of the HYCU backup controller that you want to add.

3. Enter the URL of the HYCU backup controller virtual machine.

4. Enter the user name and password of an infrastructure group administrator.

5. Click Save.

You can later edit any of the existing HYCU backup controllers (clickEdit and make therequired modifications) or delete the ones that you do not need anymore (clickDelete).

t Tip You can update data related to the HYCU backup controller by clicking Synchronize.

Viewing information about HYCU backup controllersYou can view the following information about each HYCU backup controller:

HYCU backupcontroller information

Description

Name

Name of a HYCU backup controller.

t Tip If you click the name of the HYCU backupcontroller, you are directed to the relevant HYCU web userinterface.

Status Status of a HYCU backup controller (active or inactive).

Backups Percentage of successful and failed backups.


184

HYCU backupcontroller information

Description

VM protection Percentage of protected and unprotected virtual machines.

APP protection Percentage of protected and unprotected applications.

Share protection Percentage of protected and unprotected file shares.

Policy compliancy Percentage of compliant and uncompliant policies.

Target utilization Percentage of used and free targets.

You can export data that you view in the Backup Controllers panel to a file in JSON or CSVformat. For details on how to do this, see “Exporting the contents of the panel” on page 123.

Viewing eventsYou can use the Events panel to view all events that occurred in your data protectionenvironments and check details about the selected event, list events that match thespecified filter, configure HYCU to send email notifications when events occur, and exportthe contents of the panel to a file in JSON or CSV format.




View events and check details about theselected event.

“Viewing events” on page 108

Apply filters to events. “Filtering data” on page 117

Configure HYCU to send email notificationswhen events occur.

“Sending email notifications” on page 109

Export event data.“Exporting the contents of the panel” onpage 123

Performing administration tasksAfter you deploy the HYCU virtual appliance in HYCU Manager mode, you can performvarious administration tasks through theAdministration menu.

n Note The procedures for administering HYCU deployed in the HYCU Managermode are the same as for HYCU deployed in the HYCU backup controller mode.Therefore, in most cases, you can follow the same instructions.


185

Keep in mind that a varied set of administration tasks is available depending on theselected deployment mode.


Configure Active Directory authentication.“Configuring Active Directoryauthentication” on page 141

Configure log file settings to troubleshoot problemsif HYCU does not perform as expected.

“Setting up logging” on page 147

Change the HYCU listening port number.“Changing the HYCU listening portnumber” on page 150

Change network settings.“Changing network settings” onpage 150

Configure an SMTP server.“Configuring an SMTP server” onpage 151

Configure the SSL certificate.“Configuring the SSL certificate” onpage 152

Upgrade HYCU to a new available version.

i Important Before upgrading, make sureyou have added a source where your HYCUManager virtual machine resides as described in“Adding sources” on page 25.

“Upgrading HYCU” on page 153

Manage HYCU Manager users. “Managing users” below

In addition, you can do the following:

l Use hyCLI. For details, see “Using the command-line interface” on page 179.

l Use the HYCU REST API Explorer. For details, see “Using the HYCU REST API Explorer” onpage 179.

Managing usersYou can use the Manage Users dialog box to give the specified users access to the HYCUManager console. Managing users includes creating, editing, deleting, and activating ordeactivating users.

Accessing the User Management dialog box

To access the User Management dialog box, from theAdministration menu, selectUser Management.


186

Creating a new user

Procedure1. ClickNew. The New dialog box opens.

2. Enter a user name if you are adding a HYCU Manager user or an AD user, or a commonname if you are adding an AD group.

i Important When entering a name, make sure it complies with the SAMaccount name limitations—name length may not exceed 20 characters and containany of the following characters: "/ \ [ ] : ; | = , + * ? < >. In addition, HYCU does notallow the at sign (@) in the name.

If your environment requires it, these limitations can be overridden by editing thead.username.filter.regex configuration setting. However, this is not supportedand could cause authentication issues. For details on how to customize HYCUconfiguration settings, see “Customizing HYCU configuration settings” on page 188.

3. From the Authentication type drop-down menu, select one of the followingauthentication types:

l HYCU

Enter a display name, the user password and, optionally, email address.

n Note The minimum password length is six characters.

l AD user

From the Active Directory drop-down menu, select the Active Directory the AD userbelongs to.

l AD group

From the Active Directory drop-down menu, select the Active Directory the ADgroup belongs to.

4. Click Save. The user is added to the list of users.

i Important Only if creating a user by using hyCLI. As opposed to creating a new userthrough the HYCU Manager console where this is done automatically, if using hyCLI,you must also add the created user to the infrastructure group and assign this user theAdministrator role.


l Edit any of the existing users by clickingEdit and making the required modifications.Keep in mind that the built-in user, AD users, and AD groups cannot be edited.

l Delete any of the existing users by clickingDelete. Keep in mind that the built-in usercannot be deleted.

l Enable or disable specific users from logging on to the HYCU Manager console:

o If the status of the selected user is Inactive and you want to activate it, clickActivate.


187

o If the status of the selected user is Active and you want to deactivate it, clickDeactivate.

188

Customizing HYCUconfiguration settingsYou can find all HYCU configuration settings in the config.properties.template file in the/opt/grizzly folder on your HYCU backup controller. This file contains a list of all availableconfiguration settings and their default values. If you want to adjust any of theseconfiguration settings to meet your specific data protection environment needs andprovide optimal performance, create a new config.properties file in the same folder, andthen specify the desired configuration settings and their new values.

n Note When you upgrade HYCU, the config.properties file will be kept. However,you may want to check the updated config.properties.template file for newconfiguration settings that you can use with the new HYCU version.

Depending on which configuration settings you want to customize, see one of the followingsections:

l “Snapshot settings” on the next page

l “Utilization threshold settings” on the next page

l “Display settings” on page 190

l “SQL Server application settings” on page 190

l “Settings for aborting jobs” on page 190

l “HTTPS for WinRM configuration settings”

l “Nutanix Files settings” on page 191

l “Data rehydration settings” on page 191

l “HYCU backup controller restore settings” on page 192

Procedure1. Open a remote session to the HYCU backup controller virtual machine:



Appendix A

A Customizing HYCU configuration settings

189

For detailed information about accessing the HYCU backup controller virtual machineby using SSH, see “Accessing the HYCU backup controller virtual machine by using SSH”on page 168.

2. Access and open the config.properties file by using one of the following text editors:

l Vim:

sudo vi /opt/grizzly/config.properties

l Nano:

sudo nano /opt/grizzly/config.properties

3. Edit any of the existing configuration settings as required.

4. Save and exit the config.properties file.

5. Recommended. Restart the HYCU web server (the Grizzly server):

sudo service grizzly restart

Snapshot settingsYou can customize the maximum number of snapshots to be retained by adjusting thesesettings:

Setting Description

max.snapshots.per.vmMaximum number of snapshots that are retained per virtualmachine. The default value is 24.

max.snapshots.per.clusterMaximum number of snapshots that are retained perNutanix cluster. The default value is 2400.

Utilization threshold settingsYou can use the following settings to configure the system and data disks as well as targetutilization thresholds:

Setting Description

disk.almost.full.warning.thresholdIf the HYCU backup controller utilization of thesystem or data disk exceeds the specified value,an event is triggered. The default value is 0.90.

target.utilization.threshold.health.red

If the HYCU backup controller utilization of thetarget exceeds the specified value, its healthstatus indicator becomes red. The default valueis 0.95.


190

Setting Description

target.utilization.threshold.health.yellow

If the HYCU backup controller utilization of thetarget exceeds the specified value, its healthstatus indicator becomes yellow. The defaultvalue is 0.90.

For detailed information about the health status of the target, see “Viewing targetinformation” on page 124.

Display settingsYou can use the following settings to customize the maximum number of displayed items:

Setting Description

items.per.directory.in.flrMaximum number of files that are displayed for eachdirectory when restoring individual files. The default value is1000.

max.backups.displayedMaximum number of backups that are displayed for a virtualmachine. The default value is 100.

SQL Server application settingsYou can use the following setting to customize the backup of SQL Server applications:

Setting Description

sql.translog.compress

During the backup of an SQL Server application, transactionlog compression is enabled by default (the default value is 1).If you want to disable it, make sure to set the value for thissetting to 0.

Settings for aborting jobsYou can use the following settings to configure when a job that has the Executing status willbe aborted automatically:

Setting Description

jobs.abort.deadline.minutesTime (in minutes) within which a job must be completed.The default value is 1440.

jobs.abort.interval.minutes

Time interval (in minutes) at which all jobs that have theExecuting status are retrieved and stopped if they havebeen in this status longer than specified in thejobs.abort.deadline.minutes setting. The default value is 15.


191

HTTPS for WinRM configuration settingsYou can use the following settings to configure HTTPS for WinRM:

Setting Description

winrm.https.enabled

HYCU is preconfigured to use HTTP for WinRM connections tovirtual machines. If you want HYCU to use HTTPS instead,make sure to set the value for this setting to true, and thenperform the procedure described in “Enabling HTTPS forWinRM connections” on page 169.

winrm.fallback.httpOnly if winrm.https.enabled is set to true. If set to true, HYCUuses HTTP for WinRM connections to virtual machines if usingHTTPS fails due to certificate issues.

Nutanix Files settingsYou can use the following setting to configure reindexing frequency for file share backups:

Setting Description

afs.reindex.intervalNumber of incremental file share backups after which a fullreindex is performed, which increases the responsiveness ofthe file restore process. The default value is 5.

Data rehydration settingsYou can use the following settings to configure HYCU to perform data rehydration:

Setting Description

target.azure.blob.rehydration.enable

HYCU is preconfigured to perform datarehydration before performing a restore if someor all of the restore point data is stored in theAzure archive storage tier. During a rehydrationtask, the data is moved from the archive storagetier to the hot storage tier from which HYCU canrestore data. HYCU does not move data back tothe archive storage tier afterward. The defaultvalue is true.

target.azure.blob.rehydration.threadsNumber of blobs that can be rehydrated inparallel. The default value is 20.


192

HYCU backup controller restore settingsYou can use the following settings to enable additional scenarios for disaster recovery(restore of the HYCU backup controller):

Setting Description

clone.enabled.for.hycu.dr

HYCU is preconfigured to prevent creating clones ofthe HYCU backup controller (the virtual machineitself or its virtual disks).

C Caution Do not activate a clone of theHYCU backup controller while the original HYCUbackup controller is still active. If such activationhappens, data loss may occur. All currentlyrunning backups fail and their status is set toError. The corresponding restore points are thenautomatically removed by the HYCU cleaningprocess.

If set to true, cloning of the HYCU backup controlleris enabled and the respective restore optionsbecome available in the HYCU web user interface.

193

Restoring to an environmentwith a different hypervisorThis appendix describes prerequisites, limitations, considerations, and/or additional stepsthat you should perform to successfully restore a virtual machine to an environment with adifferent hypervisor.

VM sourceenvironment

VM targetenvironment

Restore option Additional information

Nutanix ESXi orvSphere

Nutanix AHV Clone VM

“Restoring a virtual machine on aNutanix ESXi cluster or in avSphere environment to a NutanixAHV cluster” on the next page

vSphere Nutanix ESXi Clone VM“Restoring a virtual machine in avSphere environment to a NutanixESXi cluster” on page 197

Nutanix AHV Nutanix ESXi Clone VM

A virtual machine on a NutanixAHV cluster is restored to aNutanix ESXi cluster as describedin “Cloning a virtual machine” onpage 58, and no additional actionsare required.

Nutanix AHV orNutanix ESXi

vSphere Export vDisks

A virtual machine on a NutanixAHV or ESXi cluster is restored to avSphere environment asdescribed in “Exporting virtualdisks” on page 63, and noadditional actions are required.

Considerationsl If during a restore of the selected virtual machine you receive a warning message

indicating that there is a guest operating system mismatch detected (between the guest

Appendix B

B Restoring to an environment with a different hypervisor

194

operating system that is running on the virtual machine and the one specified duringthe configuration of the virtual machine) or a memory size mismatch detected whilecreating a new virtual machine, make sure to modify the virtual machine configurationafter the restore by specifying the appropriate Guest OS or memory. By doing so, youmake sure that the restored virtual machine has the same configuration as it hadbefore the restore. For details on how to do this, see Nutanix or VMwaredocumentation.

For details on how to restore a virtual machine, see “Restoring a virtual machine” onpage 54.

l After restoring a virtual machine with attached volume groups to an environment with adifferent hypervisor, you must reattach the volume groups to the virtual machine. Fordetails on how to do this, see Nutanix and virtual machine operating systemdocumentation.

Restoring a virtual machine on a NutanixESXi cluster or in a vSphere environment to aNutanix AHV clusterPrerequisiteA Nutanix AHV cluster is added to HYCU. For details on how to do this, see “Adding aNutanix cluster” on page 25.

LimitationRestoring virtual machines that use UEFI firmware to a Nutanix AHV cluster is notsupported. For details, see Nutanix documentation.

RecommendationsTo avoid having to perform manual steps after restoring a virtual machine on a NutanixESXi cluster or in a vSphere environment to a Nutanix AHV cluster, you should follow theserecommendations before backing it up:

l Windows virtual machine only. The Nutanix VirtIO package is installed on a virtualmachine. If you have NGT installed on your virtual machine on the Nutanix ESXi cluster,there is no need to install the Nutanix VirtIO package because it is already installed aspart of NGT installation.

l Linux virtual machine on a Nutanix ESXi cluster only. NGT is installed on your virtualmachine.

l Linux virtual machine in a vSphere environment only. The VirtIO drivers are added to theGuest OS kernel.

How to determine the availability of the VirtIO drivers and add them if necessaryTo check if the VirtIO drivers are available in the installed kernel, as the root user, run the


195

following command:

grep -i virtio /boot/config-ùname -r`

The following output confirms that the VirtIO drivers are available:

CONFIG_VIRTIO_BLK=mCONFIG_SCSI_VIRTIO=mCONFIG_VIRTIO_NET=mCONFIG_VIRTIO_CONSOLE=mCONFIG_HW_RANDOM_VIRTIO=mCONFIG_DRM_VIRTIO_GPU=mCONFIG_VIRTIO=m# Virtio driversCONFIG_VIRTIO_PCI=mCONFIG_VIRTIO_PCI_LEGACY=yCONFIG_VIRTIO_BALLOON=mCONFIG_VIRTIO_INPUT=m# CONFIG_VIRTIO_MMIO is not set

To check if the VirtIO drivers are added to the kernel, as the root user, run the followingcommands:

cp /boot/initramfs-ùname -r`.img /tmp/initramfs-ùname -r`.img.gz

zcat /tmp/initramfs-ùname -r`.img | cpio -it | grep virtio

An output similar to the following one appears if the VirtIO drivers are added to thekernel:

97084 blocks

If the output is blank, the VirtIO drivers are not added to the kernel. To add the VirtIOdrivers to the kernel, as the root user, run the following command:

dracut --add-drivers "virtio_pci virtio_blk virtio_scsi virtio_net" -f –v

To check if the VirtIO drivers are added to the kernel, as the root user, run the followingcommands:

cp /boot/initramfs-ùname -r`.img /tmp/initramfs-ùname -r`.img.gz

zcat /tmp/initramfs-ùname -r`.img | cpio -it | grep virtio

An output similar to the following one should appear:

usr/lib/modules/ùname -r`/kernel/drivers/scsi/virtio_scsi.kousr/lib/modules/ùname -r`/.x86_64/kernel/drivers/block/virtio_blk.kousr/lib/modules/ùname -r`/kernel/drivers/char/virtio_console.kousr/lib/modules/ùname -r`/kernel/drivers/net/virtio_net.kousr/lib/modules/ùname -r`/kernel/drivers/virtiousr/lib/modules/ùname -r`/kernel/drivers/virtio/virtio.ko


196

usr/lib/modules/ùname -r`/kernel/drivers/virtio/virtio_pci.kousr/lib/modules/ùname -r`/kernel/drivers/virtio/virtio_ring.ko97084 blocks


If you have not followed the above recommendations, your virtual machine will not bootafter the restore, and you must perform the following additional steps:

1. Make sure that the restored virtual machine is turned off.

2. As the administrator or the root user, log on to the Nutanix AHV cluster by using SSH.

3. List the virtual machine details:

acli vm.get <VMName>

4. Take a note of the current bus and index values in the disk_list section.

5. Clone the existing disk to a new disk on the compatible bus:

acli vm.disk_create <VMName> bus=<BusType>clone_from_vmdisk=vm:<VMName>:<CurrentBus>.<CurrentIndex>

In this instance, <VMName> is the name of the restored virtual machine, <BusType> isscsi, ide, or sata, <CurrentBus> is the bus value from the disk_list section, and<CurrentIndex> is the index value from the disk_list section.

If the original virtual machine has the SATA or SCSI disks, clone them to the SATA disks.For example:

acli vm.disk_create test-vm bus=sataclone_from_vmdisk=vm:test-vm:scsi.0

If the original virtual machine has the IDE disks, clone them to the IDE disks. Forexample:

acli vm.disk_create test-vm bus=ideclone_from_vmdisk=vm:test-vm:ide.0

After you perform the previous procedure for all the disks, follow these steps:




4. From the list of virtual machines, select the restored virtual machine, and click Update.

5. Delete the source disks, and then select the boot disk and click Save.

6. Click Power on to turn on the restored virtual machine.

7. Install the Nutanix Guest Tools software bundle of the latest version on the virtualmachine.


197

8. Recommended for virtual machines that had the SCSI disks. Clone the controller back to theSCSI controller.

For details on how to update a virtual machine on a Nutanix cluster, see Nutanixdocumentation.

Restoring a virtual machine in a vSphereenvironment to a Nutanix ESXi clusterIf after restoring a virtual machine in a vSphere environment to a Nutanix ESXi cluster, thevirtual machine does not boot, perform the following additional steps:

l If the type of controller on the restored virtual machine is not the same as it was on theoriginal virtual machine, do the following:


2. Click the VMs tab, and then right-click the restored virtual machine and select EditSettings.

3. On the Virtual Hardware tab, modify the controller settings so that they match theones on the original virtual machine.

l If the virtual machine uses UEFI firmware, edit the settings of the restored virtualmachine as follows:


2. Click the VMs tab, and then right-click the restored virtual machine and select EditSettings.

3. Linux virtual machines only. On the Virtual Hardware tab, change the controller toVMware Paravirtual.

4. Click the VM Options tab, and then, under Boot Options, change the firmware toEFI.

5. Only if required to manually select the boot file. Access the EFI Boot Manager menu,and then do the following:

a. Select the Enter setup option.

b. Enter the boot maintenance manager by selecting Boot option maintenancemenu.

c. Use the Boot from a File option to browse for a boot file.

d. Find a device whose name contains the GPT string that represents the bootpartition, and then press Enter to open it.

e. Navigate to the EFI boot file that you can find at the following location:

o Windows: \EFI\Microsoft\Boot\bootmgrfw.efi


198

o Linux: /EFI/<OSName>/grubx64.efi

f. Press Enter to resume booting.

Provide feedbackFor any suggestions and comments regarding this product or its documentation, send usan e-mail to:

[email protected]

We will be glad to hear from you!

mailto:[email protected]

www.hycu.com

http://www.hycu.com/

Documents

HYCU User Guide · 2019-06-27 · 4 Contents 1AboutHYCU 10 HYCUkeyfeaturesandbenefits 11 Dataprotectionenvironmentoverview 12 HYCUdataprotection 13 2DeployingtheHYCUvirtualappliance