Zerto Virtual Replication Administration Guide

Zerto Virtual Replication Administration Guide

Version 2.0U3

ZVR-AG-2.0U3-01-20-12-12

Copyright 2012, Zerto Ltd. All rights reserved.Information in this document is subject to change without notice and does not represent a commitment on the part of Zerto Ltd. Zerto Ltd. does not assume responsibility for any printing errors that may appear in this document. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the purchaser's personal use, without the prior written permission of Zerto Ltd.

All other marks and names mentioned herein may be trademarks of their respective companies.ZVR-AG-2.0U3-01-20-12-12

Table of Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Intended Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8OvervZerto Suppo

ChapWhat Zerto Benefi

ChapInitial

ReIn

SpecifPaSeSe

SpecifInHiEnDeSe

SpecifPaIn3

iew of Content in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Virtual Replication Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9rt and Feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

ter 1: Introduction to Zerto Virtual Replication . . . . . . . . . . . . . . . . . . . . . 11is Zerto Virtual Replication? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Virtual Replication Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12ts of Using Zerto Virtual Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

ter 2: Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Configuration for Both Enterprises and Cloud Providers . . . . . . . . . . . . . . . . . . . . . . . . . . 21gister Zerto Virtual Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21stall Virtual Replication Appliances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22ic Steps for Enterprises Managing Protected and Recovery Sites . . . . . . . . . . . . . . . . . . . . 27ir Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28t Up a Peer Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30t Up vCloud Director (If Used) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30ic Steps for Cloud Providers Supplying a Recovery Service to Enterprises . . . . . . . . . . . . . 33stall Cloud Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34de Cloud Information From Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40able the Customer to Pair to the Cloud Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42fine Masking for a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43t Up vCloud Director (If Used) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46ic Steps for Customers Pairing to a Cloud Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52ir to the Cloud Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52stall Virtual Replication Appliances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 3: Protecting Virtual Machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Configuring Virtual Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Protecting a Single Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Protecting a vApp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Moving a Virtual Machine To or From a vApp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Protecting Virtual Machines When VMware vCloud Director is Used . . . . . . . . . . . . . . . . . . . . . 84

ReReRe

ChapSettinSizing

VMWEsCoEs

SettinSite C

DeDeDeDeCoDeDeCoDe

DefiniConfig

CoM4

plication From a vCenter Server to vCloud Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85plication From vCloud Director to vCloud Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90plication From vCloud Director to a vCenter Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

ter 4: Advanced Zerto Virtual Replication Configuration . . . . . . . . . . . . . 92g Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

DK Size Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93AN Sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94timating the Bandwidth Requirements Between Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94llecting Data Characteristics for VMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96timating the Required Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99g Up Information About a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100onfiguration Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101fining the Maximum Bandwidth Used by Zerto Virtual Replication Between Sites . . . . 102fining the Default Script Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102fining the Scaling Used for Performance Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102fining Masking for Newly Paired Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103nfiguring vCloud Director and Provider vDCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103fining the Replication Pause Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105fining the Failover and Move Operation Default Commit Policy . . . . . . . . . . . . . . . . . . . 105nfiguring Email Notifications for Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106fining Zerto Support Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107ng Masking for a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108uring vCloud Director (If Used) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111nfiguring Provider vDCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

asking vCloud Director Organization vDCs and Networks. . . . . . . . . . . . . . . . . . . . . . . . . 115

Chapter 5: Managing Zerto Virtual Replication. . . . . . . . . . . . . . . . . . . . . . . . . 117Managing VPGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Adding a Virtual Machine to an Existing VPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Modifying a VPG Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Forcing the Synchronization of a VPG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Cloning a VPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129DeVP

ModifyEnsur

AdEnEn

RunniCrEx

ManagMUpEdSoUnSuHa

ManagHa

ManagReRe

ChapThe MThe FThe FThe C5

leting a VPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132G Statuses and Synchronization Reasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133ing a Virtual Machine Volume Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

ing Application Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136ding a Checkpoint to Identify a Key Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137suring Application Consistency With Microsoft Volume Shadow Copy Service (VSS) . . 138suring Application Consistency Using APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141ng Scripts Before or After Recovering a VPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141eating a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143amples Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144ing VRAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

aintaining Shadow VRAs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148grading VRAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149iting a VRA Host Password and Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152rting the VRA List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154installing VRAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155pport for VMware Host Maintenance Mode and VRA Maintenance . . . . . . . . . . . . . . . . . 156ndling a Ghost VRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159ing Cloud Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161ndling a Ghost Cloud Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162ing a Zerto Virtual Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163configuring the Zerto Virtual Manager IP Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163store the Zerto Virtual Manager to a Backed Up Version . . . . . . . . . . . . . . . . . . . . . . . . . 166

ter 6: Recovery Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168ove Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

ailover Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169ailover Test Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170lone Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Chapter 7: Testing Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173The Test Failover Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Starting and Stopping Failover Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Viewing Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Live Disaster Recovery Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Basic Verification User Traffic Is Not Run Against the Recovered VMs . . . . . . . . . . . . . . 182Ru

ChapThe MMovinRevers

ChapThe FInitiatReversInitiatInitiat

ChapMonitMonit

SaM

MonitMonit

ThTh

Zerto AlAuFaOuPrToUsVP

Seeing6

n User Traffic Against the Recovered VMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

ter 8: Migrating a Protection Group to the Recovery Site. . . . . . . . . . . . 187ove Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187g Protected Virtual Machines to the Peer Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188e Protection For a Moved VPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

ter 9: Managing Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195ailover Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195ing a Failover From the Protected Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197e Protection For a Failed Over VPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204ing a Failover From the Recovery Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205ing a Failover During a Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

ter 10: Zerto Virtual Replication Reports . . . . . . . . . . . . . . . . . . . . . . . . . 212oring Site Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213oring Virtual Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215ving Details of Virtual Protection Groups to File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217onitoring a Virtual Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218oring Protected Virtual Machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219oring Zerto Virtual Replication Peer Sites and Site Topology . . . . . . . . . . . . . . . . . . . . . . 222e Site List Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222e Topology View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Virtual Replication Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225erts Report Issued by Zerto Virtual Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226dit Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227ilover Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228tbound Protection Over Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229otection Over Time by Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230p Sites Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237G Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 What is Licensed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Chapter 11: How Zerto Virtual Replication Works With VMware Features. . . 242Protecting Virtual Machines in a vApp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Protecting Virtual Machines that Use Thin Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Zerto Virtual Replication and VMware Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

VMware High Availability (VMHA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244DRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Zerto Zerto EnsurZerto VMwaVMwa

ChapEnsurZerto Troub

ZeHo

TroubVPHoVR

HandlUnderCollecCollec7

Virtual Replication and Fault Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Virtual Replication and Host Affinity Rules and CPU Pinning . . . . . . . . . . . . . . . . . . . . . 245ing VPG Integrity When Using VMotion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Virtual Replication and Storage VMotion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246re Host Maintenance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246re Roles and Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

ter 12: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247ing Zerto Virtual Replication is Running. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Virtual Replication Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248leshooting GUI Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251rto Tabs Not Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251st is Not Displayed in List of Hosts in the Manage VPG Dialog . . . . . . . . . . . . . . . . . . . . 251

leshooting VRA Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251G Syncing Take a Long Time Network Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251st is Not Displayed in List of Hosts in the Manage VPG Dialog . . . . . . . . . . . . . . . . . . . . 252A Crashes During Promotion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

ing Lack of Storage Space for Recovered Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . 252standing the Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252ting Logs to Troubleshoot Problems: Running Zerto Virtual Replication Diagnostics . . . 254ting Log Information for the ZertoVssAgent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

About This Guide

Zerto in a viquicklobjectithe reReplic

This gbusinevSphe

Inte

This g

Ove

This gChap

1

2

38

Virtual Replication provides a business continuity (BC) and disaster recovery (DR) solution rtual environment, enabling the replication of mission-critical applications and data as y as possible and with minimal data loss. When devising a recovery plan, these two ves, minimum time to recover and maximum data to recover, are assigned target values:

covery time objective (RTO) and the recovery point objective (RPO). Zerto Virtual ation enables a virtual-aware recovery with low values for both the RTO and RPO.

uide describes how to configure and manage Zerto Virtual Replication to implement ss continuity and disaster recovery (DR) solutions in a virtual environment using VMware re Client console.

nded Audience

uide is for the use of experienced VMware administrators.

rview of Content in This Guide

uide contains the following chapters:ter Title Description

Introduction to Zerto Virtual Replication

Describes the underlying concepts and architecture of Zerto Virtual Replication.

Initial Configuration Describes how to set up the environment for recovery using Zerto Virtual Replication.

Protecting Virtual Machines

Describes how to set up protection for virtual machines.

Zerto Virtual Replication Documentation Set

Zer

The Ze

4 Advanced Zerto Virtual Replication Configuration

Describes the processes available to manage protection and recovery sites using Zerto Virtual Replication.

5 Managing Zerto Virtual Replication

Describes the processes available to manage protection and recovery sites using Zerto Virtual Replication.

6

78

9

10

11

12

ReleasInstalStarteZerto VCmdle

Chapter Title DescriptionAbout This Guide 9

to Virtual Replication Documentation Set

rto Virtual Replication documentation set includes the following documentation:

Recovery Procedures Describes the available recovery procedures and when they are used.

Testing Recovery Describes how to test recovery to ensure the results you want.Migrating a Protection Group to the Recovery Site

Describes the process of migrating protected virtual machines from the protected site to the recovery site.

Managing Failover Describes the process of recovery from the protected site to the recovery site.

Zerto Virtual Replication Reports

Describes the interaction between Zerto Virtual Replication and commonly used VMware features such as VMotion, DRS and HA.

How Zerto Virtual Replication Works With VMware Features

Describes the interaction between Zerto Virtual Replication and commonly used VMware features such as VMotion, DRS and HA.

Troubleshooting Describes how to resolve problems.

e Notes Details specific to this release of Zerto Virtual Replication.lation and Getting d Guide

How to install and set up Zerto Virtual Replication.

irtual Replication ts

How to install and use the Zerto Virtual Replication Windows PowerShell cmdlets, including the cmdlets to use when upgrading Zerto Virtual Replication.

Support and Feedback

Additionally, an API online help is available.The dodocum

Sup

Please

Quick Reference a single sheet with brief descriptions of how to perform the main functions.

Administration Guide This guide: How to implement and manage replication and a disaster recovery (DR) solution in a virtual environment using Zerto Virtual Replication.About This Guide 10

cumentation is available in both PDF and HTML formats. Access the PDF versions of the entation from the StartHere PDF.

port and Feedback

send suggestions to improve the documentation to Zerto support.

Chapter 1: Introduction to Zerto Virtual Replication

Disastthat suchaptea virtuThe fo W Z H B

Wh

Zerto in a viquicklobjectithe reReplicZerto You mpoint ofrom tas recoZerto

1. An exvSphRepli11

er recovery is the process of preparing for recovery or continuation of IT processing tasks pport critical business processes in the event of a threat to the IT infrastructure. This r describes Zerto Virtual Replication general concepts to enable replication and recovery in al environment.llowing topics are described in this chapter:hat is Zerto Virtual Replication?, below.

erto Virtual Replication Architecture, on page 12.ow Zerto Virtual Replication Recovery Works, on page 14.enefits of Using Zerto Virtual Replication, on page 16.

at is Zerto Virtual Replication?

Virtual Replication provides a business continuity (BC) and disaster recovery (DR) solution rtual environment, enabling the replication of mission-critical applications and data as y as possible and with minimal data loss. When devising a recovery plan, these two ves, minimum time to recover and maximum data to recover, are assigned target values:

covery time objective (RTO) and the recovery point objective (RPO). Zerto Virtual ation enables a virtual-aware recovery with low values for both the RTO and RPO.Virtual Replication is installed in both the protected and the disaster recovery (DR) sites. anage the replication from within the vSphere Client console, so you only need to have one f control: All recovery that does not rely on native replication functionality is managed

he vSphere Client console1. Recovery that does rely on native replication functionality, such very available with Microsoft Active Directory or SQL Server, can also be replicated using

Virtual Replication, and whether the native replication functionality is used or not is

tensive API and Windows PowerShell cmdlets are also available enabling management from a script instead of the ere Client console. For details of the APIs, refer to the API online help. For details of the cmdlets, refer to the Zerto Virtual cation Cmdlets guide.

Zerto Virtual Replication Architecture

determined by site considerations, such as increased complexity of having multiple points of control and possible additional costs incurred when using vendor native replication.You configure replication by first pairing the site with virtual machines to be protected with a recovery site. You then define what virtual machines you want replicated in groups, where the virtual machines in the group comprise the application and data you want to protect. You can group different virtual machines together or keep them separate. By creating different replication groupsrecove

Zer

Zerto Zerto VvCentVirtualmachimachiZerto Ccloud complnetwoZerto vmanag

The Zethe prsuppliIntroduction to Zerto Virtual Replication 12

, you can customize the replication requirements for each group to better optimize the ry plan.

to Virtual Replication Architecture

Virtual Replication comprises the following components:irtual Manager (ZVM) A Windows service, which manages the replication between the

er Servers on the protection and recovery sites. Replication Appliance (VRA) A virtual machine installed on each ESX/ESXi hosting virtual nes to be protected or recovered, to manage the replication of data from protected virtual nes to the recovery site.loud Connector A cloud connector routes traffic between the customer network and the

replication network, in a secure manner without requiring the cloud vendor to go through ex network and routing setups, ensuring complete separation between the customer rk and the cloud provider network.Sphere Client console plug-in A plug-in in the vSphere Client console that enables ing recovery using Zerto Virtual Replication from the console.

rto Virtual Replication components are deployed differently, depending on whether both otected and recovery sites belong to the same enterprise or whether a cloud provider es disaster recovery services to an enterprise.


Both the protected and recovery sites belong to the same enterprise The following diagram shows how the Zerto Virtual Replication components are deployed and the communication protocols used between the components, when both the protected and recovery sites belong to the same enterprise.

Zerto Vany ofbranchIntroduction to Zerto Virtual Replication 13

irtual Replication can be installed at multiple sites and each of these sites can be paired to the other sites enabling enterprises to protect multiple data centers as well as remote offices.


A cloud provider supplies disaster recovery services to the enterprise The following diagram shows how the Zerto Virtual Replication components are deployed and the communication protocols used between the components when a cloud provider supplies the disaster recovery to the enterprise.

Whenmust bnetwoadditiand auHow ZZerto sites fPowerthe virprotecmore EmultipNote: ArequirIntroduction to Zerto Virtual Replication 14

a cloud provider supplies disaster recovery as a service (DRaaS), each enterprise network e completely fenced off from the other enterprises. Zerto Virtual Replication enables this

rk separation by installing a cloud connector per enterprise, providing full multi-tenancy. In on, Zerto Virtual Replication is integrated with VMware vCloud Director enabling seamless tomated recovery to and from a vCD.erto Virtual Replication Recovery Works

Virtual Replication sits in the hypervisor layer. You manage the protected and recovery rom the vSphere Client console or via in-house scripts, using Zerto Virtual Replication Shell cmdlets or APIs to perform the required replication. In the protected site you define tual machines that you want to replicate, either individually or together, as a virtual tion group (VPG). The virtual machines that you include in the VPG can come from one or SX/ESXi hosts in the vCenter Server. In this way, you can protect applications that run on le virtual machines and disks as a single unit, in a single VPG.n example of an application that runs on multiple virtual machines includes software that

es a web server and database, both of which run on virtual machines different to the virtual


machine where the application software runs. Under VMware these machines can be bundled together using VMware vAPP. In this case the VPG can include the vAPP.Every write is intercepted by Zerto Virtual Replication and a copy of the write is sent, asynchronously, to the recovery site, while the write continues to be processed on the protected site. For greater efficiency and performance, the write is compressed before being sent to the recovery site with throttling techniques being used to prioritize network traffic.On thevirtuaEveryorder crash-can beFor exrecoveAs wecreatespecifycan spVirtuaenvirowere cTo impmachiand thinformenvirowhen The jobig enperiodjournaIntroduction to Zerto Virtual Replication 15

recovery machine the write is written to a journal under the Virtual Replication Appliance l machine. few seconds, a checkpoint is also written to the journal. These checkpoints ensure write fidelity and crash-consistency to each checkpoint. During recovery you pick one of these consistent checkpoints in the journal and recover to this point. Additionally, checkpoints manually added to the journal by the administrator, with a description of the checkpoint. ample, when an event is going to take place that might result in the need to perform a ry, you can pinpoint when this event occurs as a checkpoint in the journal.ll as the writes being written to the journal, images of the protected volumes in the VPG are d under the Virtual Replication Appliance virtual machine. During a failover, you can that you want to recover the virtual machines in the VPG using the last checkpoint or you ecify an earlier checkpoint, in which case the recovery of the mirror images under the l Replication Appliance are synchronized to this checkpoint. Thus, you can recover the nment to the point before any corruption and ignore the later writes in the journal that orrupted, either caused by a crash in the protected site or for other reasons, such as a virus.rove the RTO during recovery, the user is able to start working even before the virtual

ne volumes on the recovery site have been fully synchronized. Every request is analyzed e response returned either from the virtual machine directly or from the journal if the ation in the journal is more up-to-date. This continues until the recovery site virtual nment is fully synchronized, up until, either the last checkpoint, or an earlier checkpoint, the integrity of the protected site was assured.urnal file size for each VPG is defined as part of the VPG definition and is estimated to be ough to hold all the transactions for the virtual machines specified in the VPG for a defined . After this period, or when the journal is approximately 95% full, the earliest entries in the l are written to the mirror images of the virtual disk volumes under the VRA.

Benefits of Using Zerto Virtual Replication

Ben

Datacinto thinfrasapplicTraditdemanmanagdisk leThe laalso rethese

FullyZerto with vIntroduction to Zerto Virtual Replication 16

efits of Using Zerto Virtual Replication

enter optimization and virtualization technologies have matured and are now well adopted e IT infrastructure. As more and more applications are deployed in a virtualized

tructure, there is a growing need for recovery mechanisms to support mission critical ations deployments while providing complete BC and DR.ional replication and disaster recovery solutions were not conceived to deal with the ds created by the virtualization paradigm. For example, most replication solutions are not ed in the hypervisor layer, considering the virtual machines and disks, but at the physical vel, hence they are not truly virtualization aware.ck of virtualization awareness creates a huge operational and administrative burden. It sults with operational inflexibility. Zerto Virtual Replication has been designed to resolve

issues by being fully virtualization aware.

Virtual Sits in the HypervisorVirtual Replication software sits in the hypervisor level. Protection groups are configured irtual machines and virtual disks, without the need to consider the physical disks.


Focus is on the Application, Not the Physical StorageBy considering the physical disk level and not the virtual disk level, traditional replication is not truly application aware. Even virtual replication recovers block writes at the SCSI level and not at the application level. Zerto Virtual Replication is truly application focused, replicating the writes from the application in a consistent manner.

HardBecaudisks ocan beprotocseparaneed t

FullyZerto ReplicmachiVRA oServeradditi

EfficiWritesare wrasynchAlso, band notraffic

One-When initiatthe adwhat pIntroduction to Zerto Virtual Replication 17

ware Agnosticse Zerto Virtual Replication software manages recovery of virtual machines and virtual nly, it does not matter what hardware is used in either the protected or recovery sites; it

from the same vendor or different vendors. As long as the storage device supports the SCSI ol, any storage device can be used. With Zerto Virtual Replication the logical storage is ted from the physical storage so that the vendor and type of actual storage hardware do not o be considered.

ScalableVirtual Replication sits in the hypervisor level and enables defining software-only Virtual ation Appliances (VRAs) on each ESX/ESXi host to manage the replication of virtual nes on that host. Increasing the number of ESX/ESXi hosts is handled by defining a new n each new ESX/ESXi host. There is no need to install additional software to the vCenter to handle additional ESX/ESXi hosts or virtual machines and no need to consider

onal hardware acquisitions.

ent Asynchronous Replication are captured by the Zerto Virtual Replication software in the hypervisor level, before they itten to the physical disk at the protected site. These writes are sent to the recovery site ronously, thus avoiding long distance replication latency to the production applications.ecause these writes are captured and sent to the recovery site, it is only these delta changes t the whole file or disk that is sent to the recovery site, reducing the amount of network

, which reduces WAN requirements and significantly improves both RPO and RTO targets.

Click Failover and Control of the Recovery Processrecovery is required, the administrator clicks on a button in the vSphere Client console to e failover. This means that control of when a recovery is initiated remains in the hands of ministrator, who can decide when to initiate the recovery and, by selecting a checkpoint, to oint-in-time to recover to.


Near-zero RPOZerto Virtual Replication utilizes continuous data protection, sending a record of every write in the virtual protection group to the recovery site. The transfer of this information is done over an optimized WAN asynchronously. If recovery is required, all the data that was transferred to the recovery site is available resulting is recovery within the requested RPO.

Near-Durinrecoverequesthe remachicontinIn tradmachiwastedthat aLUN cmakesreplica

PolicIn theor as gVPG cprotecVPG.

WANUsingnetwocommZerto the Win a VPis a nechangIntroduction to Zerto Virtual Replication 18

zero RTOg recovery the mirrors of the virtual machines that need recovering are recovered in the ry site from the Virtual Replication Appliance and synchronized to the checkpoint ted for this failover. During this synchronization, users can access the virtual machine on

covery site. Every request is analyzed and the response returned either from the virtual ne directly or from the journal if the information in the journal is more up-to-date. This ues until the recovery site virtual environment is fully synchronized.itional replication architectures, either a complete LUN with all the data for multiple

nes is replicated or a single LUN is used for each machine. In both of these cases, the storage and all the inflexibility, both in terms of planning and operating recovery, means

lthough replication is achieved, either it is has a high RTO or it is prone to errors. A single an be used to store the data for multiple virtual machines and Zerto Virtual Replication sure that only the data relevant to the virtual machine requiring replication is in fact ted. In addition, you can also create VPGs across different LUNs.

y-based protected site you define the virtual machines that you want to recover, either individually roups, as a virtual protection group (VPG). The virtual machines that you include in the an come from one or more ESX/ESXi hosts in the vCenter Server. In this way, you can t applications that run on multiple virtual machines and disks as a single unit, in a single

Optimization Between Protected and Recovery Sites compression to minimize bandwidth and other techniques such as throttling to prioritize rk traffic to reduce the impact on day-to-day operations, you can make sure that the unication between the protected and recovery sites is fully optimized.Virtual Replication also uses signature matching to reduce the amount of data sent across AN. During synchronization of the protected site and recovery site for every virtual machine

G, Zerto Virtual Replication maintains a map of disk sectors so that in the case when there ed to resynchronize sites, the map signatures can be used to ensure that only data where es occurred are passed over the WAN.


WAN ResilienceZerto Virtual Replication is highly resilient to WAN interruptions. In order to reduce storage overhead used for replication purposes, on WAN failure Zerto Virtual Replication starts to maintain a smart bitmap in memory, in which it tracks and records the storage areas that changed. Since the bitmap is kept in memory, Zerto Virtual Replication does not require any LUN or volume per VPG at the source side. Once the WAN connection resumes, Zerto Virtual Replicwere u

SinglWith ZYou dothe nurecoveYou madditiavaila

FullyZerto other Introduction to Zerto Virtual Replication 19

ation uses this bitmap to check whether there were updates to the source disks and if there pdates to the disks, these updates are sent to the recovery site.

e Point of Controlerto Virtual Replication everything is managed from the VMware vSphere Client console. not need to access multiple consoles to configure and manage the replication. This reduces mber of control points and provides a unified method of configuring and managing ry.anage and control both protected and recovery sites from same vSphere Client console. In on to being able to manage the recovery configuration from the console, a full API and is ble to manage recovery from the command line and from scripts.

Compatible with VMware Product LineVirtual Replication runs in the VMware vCenter Server hypervisor and is compatible with VMware features, such as VMotion.

Chapter 2: Initial Configuration

Zerto Zerto ReplicThe coenterpserviceach o

The fo In S S S

1. An exAPIs,

Enterand re

Pair

Set U30.Set UUsed)20

Virtual Replication is configured and managed from within the vSphere Client console1, via tabs. This chapter describes the initial configuration required after installing Zerto Virtual ation.nfiguration steps that must be performed depend on whether you are installing as an rise managing the protected and recovery sites, a cloud provider, supplying recovery

es, or an enterprise, recovering to a cloud provider. The following table outlines the steps for f these configurations,

llowing topics are described in this chapter:itial Configuration for Both Enterprises and Cloud Providers, below

pecific Steps for Enterprises Managing Protected and Recovery Sites, on page 27pecific Steps for Cloud Providers Supplying a Recovery Service to Enterprises, on page 33pecific Steps for Customers Pairing to a Cloud Provider, on page 52

tensive API is also available enabling management from a script instead of the vSphere Client console. For details of the refer to the API online help.

prise managing protected covery sites

Cloud provider supplying a recovery service to enterprises

Enterprise using a cloud provider for recovery

Register Zerto Virtual Replication, below. Wait for cloud provider to provide access details, to enable pairing to the cloud provider.

Install Virtual Replication Appliances, on page 22.Sites, on page 28. Install Cloud Connectors, on

page 34.p a Peer Site, on page Hide Cloud Information From

Customers, on page 40.p vCloud Director (If

, on page 30.Enable the Customer to Pair to the Cloud Provider, on page 42

Pair to the Cloud Provider, on page 52.

Define Masking for a Site, on page 43.

Install Virtual Replication Appliances, on page 53.

Set Up vCloud Director (If Used), on page 46.

Initial Configuration for Both Enterprises and Cloud Providers

After installing Zerto Virtual Replication, both enterprises managing their own protection and cloud R In

Regi

On theuse of descri

After eon the21

providers supplying protection to enterprises perform the following procedures:egister Zerto Virtual Replication, belowstall Virtual Replication Appliances, on page 22

ster Zerto Virtual Replication

very first access to a Zerto tab in vSphere Client console, you have to either register your Zerto Virtual Replication, by entering the license key supplied by Zerto or pair to a site, bed below, where the license has already been entered.

ntering a valid license, the panels for the local site, on the left, and the remote, peer, site, right, are displayed.


The sisite.In thegreen over thThis inVRA i

Insta

The ZeReplicmanagESX/EESX/EIt is revirtuaprotecInitial Configuration 22

te information, specified during the installation is displayed at the top of the panel for the

top middle indicators show the Zerto Virtual Replication status. The status indicators are when there are no problems, yellow for warnings and red for errors. Hovering the mouse e red or yellow indicator, when it is showing, displays the reason for the error or warning. formation is also displayed in the Alerts report, under the Reports item, available after a

s installed and the site is paired with another site.

ll Virtual Replication Appliances

rto Virtual Replication installation includes the installation package for Virtual ation Appliances (VRAs). A VRA is a Zerto Virtual Replication virtual machine that es the replication of virtual machines across sites. A VRA must be installed on every SXi which hosts virtual machines that require protecting in the protected site and on every SXi that will host the replicated virtual machines in the recovery site.commended to install a VRA on every ESX/ESXi host in each vCenter Server, so that if a l machine being protected is moved for example, using VMware VMotion, it is still ted.


Note: When protecting virtual machines in a cluster, it is recommended to install a VRA on every ESX/ESXi host in the cluster so that if protected virtual machines are moved from one host in the cluster to another host in the cluster there is always a VRA to protect the moved virtual machines, or to disable DRS on the virtual machines to be protected. If you are protecting a vApp, you must install a VRA on every ESX/ESXi host in the cluster on both the protected and recovery sites and ensure that DRS is enabled for these clusters.

To insTo insmemoalso k Th If

us Th

suNote: Iinstall1. In

Th2. Cl

ThInitial Configuration 23

tall Zerto Virtual Replication Appliances (VRAs) on ESX/ESXi hosts:tall a VRA, 12.5GB datastore space is required. The VRA requires at least 1GB of reserved ry. The VRA can only be installed on ESX/ESXi hosts version 4.0U1 and higher. You must now the following information to install a VRA:e network used to access the VRA in the protected site.a static IP is used instead of DHCP, the IP address, subnet mask and default gateway to be ed by the VRA.e network settings to access the peer site; either the default gateway or the IP address, bnet mask and gateway.nstalling a VRA requires that SSH is enabled on the host during the installation. After the ation you can close this SSH connection. the vSphere Client console, select the Zerto tab for the vCenter Server.e panels for the local site, on the left, and the remote, peer, site, on the right, are displayed.ick the Manage VRAs button in the local site, left, panel.e Manage VRAs dialog is displayed.


Norig

3. If SiThInitial Configuration 24

te: You can resize the Manage VRAs dialog by dragging the marker symbol in the bottom ht corner of the dialog.

the access to the peer site VRAs is not via the network default gateway, check the Paired te Routing checkbox and click the link.e Configure Paired Site Routing dialog is displayed.


SpTh

4. ClThInitial Configuration 25

ecify the IP address, subnet mask and gateway to access the peer site VRAs and click Save. ese access details then apply to every VRA defined on this site to access the peer site.ick the Install New VRA button.e Configure & Install VRA dialog is displayed.


Specify the following target host details:Host The target ESX/ESXi host for the VRA. The drop-down displays the hosts managed by the vCenter Server which do not have a VRA installed.Password The password used to access the host for the root user. This field is required for ESXi 4.x and 5.x hosts. This field is disabled for ESX 4.x hosts. When the checkbox at the side is checked the password is displayed as asterisks.DajouNeAmdea g

WbothIf thSpCoIf

5. ClThdiaco

1G

2G

3GInitial Configuration 26

tastore The datastore that the VRA will use for mirror virtual machines and for its rnal. You can install more than one VRA on the same datastore.

twork The network used to access the VRA.ount of VRA RAM The amount of memory to allocate to the VRA. The amount specified is

pendent on the number of volumes being protected or recovered. Use the following table as uideline:

hen the VRA is used both for protection and recovery, the number of volumes is the sum of th sites. For example, if four volumes are protected on one site and three on the peer site, e number of volumes is seven and the VRA requires 1GB.the VRA is protecting or recovering more volumes than specified for the amount of RAM, e chances that the VPGs require bitmap syncs will increase due to the load on the VRA.ecify the following VRA network details:nfiguration Either have the IP address allocated via a static IP address or a DHCP server. you select the Static option, which is the recommended option, enter the following:

Address The IP address for the VRA to communicate with the Zerto Virtual Manager. Subnet Mask The subnet mask for the network. The default value is 255.255.255.0.Default Gateway The default mask for the network.

ick Install.e installation starts and the status is displayed in the Status field of the Manage VRAs log. This process includes a number of tasks, which you can see in the vSphere Client

nsole tasks list.

VRA Protecting Volumes

VRA Recovering Volumes

VRA Protecting and Recovering Volumes

B 9 volumes 15 volumes 9 volumesB 56 volumes 90 volumes 56 volumesB 103 volumes 165 volumes 103 volumes

Specific Steps for Enterprises Managing Protected and Recovery Sites

6. RewhNo

7. ClClick tinstallAfter pConfig

Speand

After rconfig P S SInitial Configuration 27

peat steps 4 and 5 to add a VRA to every ESX/ESXi host that hosts virtual machines for ich you want replication.te: It is recommended to install a VRA on every listed ESX/ESXi host.ick Close to exit the dialog. The installation procedure continues.he Manage VRAs button to reopen the Manage VRAs dialog to monitor the VRA ation.airing the sites, click the configuration (cog) button in the local site panel to access the Site uration dialog to install additional VRAs.

cific Steps for Enterprises Managing Protected Recovery Sites

egistering Zerto Virtual Replication and installing VRAs you perform the following to ure Zerto Virtual Replication:air Sites, below.et Up a Peer Site, on page 30.et Up vCloud Director (If Used), on page 30.


Pair Sites

Zerto Virtual Replication is installed on both the protected and recovery sites. You have to pair sites to enable replication between the sites before configuring the replication that you want.

To pair the sites:1. In2. Cl

Th

3. ClTh

4. SpPewhPodu

1. The MagreeInitial Configuration 28

the vSphere Client console, select the Zerto tab for the vCenter Server node.ick the Pair button in the peer site panel.e Manage Sites dialog is displayed.1

ick the Add New Site button.e Add Site dialog is displayed.

ecify the following:er Site Address IP address or host name of the peer site to pair to. The peer site is the site ere the peer Zerto Virtual Manager is installed.rt The TCP port communication between the sites. Enter the port that was specified ring the installation. The default port during the installation was 9081.

anage Sites dialog enables pairing to multiple sites. The number of sites you can pair with is determined by the license ment.


5. Click the Pair button.The sites are paired, the process being reflected in the Status column. Once paired the status changes to Paired meaning that the Zerto Virtual Manager for the local vCenter Server is connected to the Zerto Virtual Manager on the peer server.

6. Click the Close button.After the pairing completes the content of the Zerto tab for the vCenter node changes to present summ

Note: WmultipdisplaInitial Configuration 29

ary information about the paired site.

hen the local site is paired with multiple sites, the peer site panel, on the right, specifies le sites and specific site information, such as the site name and contact information is not

yed.


Set Up a Peer Site

You set up a peer site by installing VRAs in the peer site.

To install VRAs on ESX/ESXi hosts in the peer site: Repeat the procedure, Install Virtual Replication Appliances, on page 22, via a vSphere

ClIf you licensepage 2

Set U

When volumperforIf you ReplicNote: BserverRun Zthe vCconnecinstallprereqthe Zebeing installAMQPare disvCD is

1. As paDurinthe lareflecInitial Configuration 30

ient console opened for the peer site vCenter Server.install a VRA on a peer site before pairing the site, as recommended, you have to enter the to use Zerto Virtual Replication, as described in Register Zerto Virtual Replication, on 1.

p vCloud Director (If Used)

vCloud Director is used, you can have the journals on separate datastores from the recovery es. For example, you might prefer to keep the recovery volumes on storage with better mance, security, and reliability and the journal on less expensive storage1.did not set up access to vCD for the Zerto Virtual Manager when installing Zerto Virtual ation, set it up using the following procedure.efore setting up Zerto Virtual Replication to work with vCD, you must have an AMQP

installed. Zerto provides an AMQP installation kit if you do not have one installed for vCD. ertoAMQPInstallWizard.exe from the kit and when prompted enter the IP or host name of D and the administrator user and password to access this vCD. The Zerto Virtual Manager ts to the vCD and checks whether an AMQP server is installed. If an AMQP server is not ed, Zerto recommends using RabbitMQ, which in turn requires Erlang/OTP as a uisite. Links to the sites to install both Erlang/OTP and RabbitMQ are provided as part of rto AMQP installation. Use these links to install Erlang/OTP and then RabbitMQ before able to continue with the Zerto AMQP installation. If an AMQP server was already ed, change the connection details displayed to those defined in vCD. If you installed the server as part of the Zerto AMQP installation, the default settings for these installations played, with a user and password of guest. At the end of the Zerto AMQP installation, updated with these settings.

rt of recovery after a failover or move operation, the data in the journal is promoted to the recovered virtual machines. g this promotion, the virtual machines can be used, and Zerto Virtual Replication makes sure that what the user sees is test data, whether from the virtual machine disks or from the journal. If the journal is on a slow storage device, this is ted in the response time the user experiences.


To set up access to vCD:1. In the vSphere Client console, select the Zerto tab for the vCenter Server node.2. Click the configuration (cog) button in the local site panel.

The Site Configuration dialog is displayed.3. Click Advanced.

Th

4. Cl

5. Ch6. EnInitial Configuration 31

e Advanced Settings dialog is displayed.

ick the Configure vCD button.

eck the Use vCD checkbox.ter the VMware vCloud Director access details:


Address The IP address or host name of the machine where vCD runs. When connecting to vCD with multiple cells, enter the virtual IP for the network load balancing used by the cells.Username The user name for an administrator to vCD.Password A valid password for the given user name.AMQP-Username The user name for the AMQP server.AMQP-Password A valid password for the given AMQP user name.

7. Cl8. ClNote: Iadd th

To con1. In2. Cl

Th3. Cl

Th4. Cl

5. Ad6. Ad

in7. Se

orInitial Configuration 32

ick Save in the Configure vCD dialog.ick Save in the Advanced Settings dialog.f a proxy server is defined on the machine where the Zerto Virtual Manager is installed, e Zerto Virtual Manager IP address to the Internet Explorer exception list.

figure provider vDCs: the vSphere Client console, select the Zerto tab for the vCenter Server node.ick the configuration (cog) button in the local site panel.e Site Configuration dialog is displayed.ick Advanced.e Advanced Settings dialog is displayed.ick the Configure provider vDCs button.

d the provider vDCs that you want to enable to use Zerto Virtual Replication.d datastores and specify how you want the organization to see these datastores, by clicking

the Presented as column to edit the content.lect what datastores not specifically added to the list are used for: either they are not used they are used for recovery volumes only.

Specific Steps for Cloud Providers Supplying a Recovery Service to Enterprises

Note: If the option Unlisted datastores are used only for recovery volumes is selected, it refers to unlisted datastores of all provider vDCs, even those provider vDCs that have not been added to the upper table.

8. Specify for each datastore added, what it can be used for: Recovery volume, Journal and Preseed.

Onor

9. Cl

SpeRec

After rconfig In H E D SInitial Configuration 33

ly datastores marked as preseeded can be used for preseeded disks. This prevents different ganizations being exposed to datastores of other customers using the preseed option.ick Save.

cific Steps for Cloud Providers Supplying a overy Service to Enterprises

egistering Zerto Virtual Replication and installing VRAs you perform the following to ure Zerto Virtual Replication:stall Cloud Connectors, below.ide Cloud Information From Customers, on page 40.nable the Customer to Pair to the Cloud Provider, on page 42.efine Masking for a Site, on page 43.et Up vCloud Director (If Used), on page 46.


Install Cloud Connectors

A cloud connector is a virtual machine installed on the cloud side, one for each customer organization replication network. The cloud connector routes traffic between the customer network and the cloud replication network, in a secure manner without requiring the cloud provider to go through complex network and routing setups, ensuring complete separation betweEthernWithinprovidincomprovidInitial Configuration 34

en the customer network and the cloud provider network. The cloud connector has two et interfaces, one to the customers network and one to the cloud provider's network. the cloud connector a bidirectional connection is created between the customer and cloud er networks. Thus, all network traffic passes through the cloud connector, where the ing traffic on the customer network is automatically configured to IP addresses of the cloud er network.


The organization networks for disaster recovery are extended to the cloud. The Zerto Cloud Connectors are installed to ensure that these networks have no touch points with the cloud infrastructure network, providing complete network separation between each organization network and the cloud provider infrastructure network. All the traffic to and from the organization is routed through the cloud connector, so that the following is implemented: None of the organizations have direct access to the cloud provider network and cannot see any

pa EaIf the interfacloud

In thenetwoas is tspecifiInitial Configuration 35

rt of the cloud provider network that the cloud provider does not allow them to see. ch organization has no access to the network of another organization.cloud provider wants to institute additional security, considering both cloud connector ces as part of the customer network, he can define a static route that will hop to a different

network, specifically for use by the Zerto Virtual Manager and VRAs in the cloud site.

above diagram the cloud connector interfaces directly to the cloud provider VLAN200 rk, while the Zerto Virtual Manager and VRAs in the cloud site are on a separate network he cloud VC network. The hop to the Zerto Virtual Manager and VRAs in the cloud site is ed as a static route in the cloud connector.


If you change the Zerto Virtual Manager and VRAs cloud network, changing the static route settings for a group to the new network, changes the access for all cloud connectors with the specified group.

To set up static routes:1. In the vSphere Client console, select the Zerto tab for the vCenter Server and in the right

pa2. Cl

Th


nel click the configuration (cog) button.ick the Manage cloud connectors... button.e Manage Cloud Connectors dialog is displayed.

ick the Manage Static Routes button.e Manage Static Routes dialog is displayed.


4. Click Add under Group to define a group. This group will contain a static route to the subnet used by the Zerto Virtual Manager and can be applied to more than one cloud connector.

5. Sp6. Se

7. SpAdSuGa

8. ClYoeaInitial Configuration 37

ecify the name of the group and click Save.lect a group and click Add under Route to define a static route for that group.

ecify the static route:dress The IP address for the static route.bnet Mask The subnet mask for the network.teway The gateway for the network.ick Save.u can defined more than one static route for a group. The static routes are displayed under ch group.


9. ClYou caZerto the ne

To insNote: T1. In

pa2. Cl


ick Save.n use the group in the definition of a cloud connector, described below. If you change the

Virtual Manager network or VRA network, changing the static route settings for a group to w network, changes the access for all cloud connectors with the specified group.

tall a cloud connector:he cloud connector requires 2GB of disk space.

the vSphere Client console, select the Zerto tab for the vCenter Server and in the right nel click the configuration (cog) button.ick the Manage cloud connectors... button.e Manage Cloud Connectors dialog is displayed.


3. Click the Install New Connector button.The Configure and Install Cloud Connector dialog is displayed.

SpOrHodisDaOrco

Clco

4. ClInitial Configuration 39

ecify the following:ganization Name A name used by the cloud provider to identify the enterprise client.st The target ESX/ESXi host for the cloud connector virtual machine. The dropdown plays the hosts which do not have a cloud connector installed.tastore The datastore for the cloud connector virtual machine.ganization Network The network details opened to the customer. Specify the following cloud nnector network details:

Network The name of the network from the list of available networks.Address The IP address for the customer to communicate with the cloud connector. The customer pairs to this IP address.Subnet Mask The subnet mask for the network. The default value is 255.255.255.0.Default Gateway The default gateway for the network.

oud Network The local network details for the cloud provider. Specify the following cloud nnector network details:

Network The name of the cloud-side network from the list of available networks.Address The IP address for the cloud provider to communicate with the cloud connector.Subnet Mask The subnet mask for the network. The default value is 255.255.255.0.Static Route Group The name of the group for which static routes are defined to the Zerto Virtual Manager network and VRA network. If a static route group is not specified, it is assumed that the Zerto Virtual Manager and VRAs are on the cloud network.

ick Install.


The installation starts and the status is displayed in the Status field of the dialog. You can install more than one cloud connector per organization and per Zerto Virtual Manager.

5. Cl6. ReAfter istartin

The cuaddresprovid

Hide

After icustomsee cloprovid

To hid1. In2. Cl


ick Close to exit the dialog. The installation procedure continues.peat the procedure for every customer.nstalling a cloud connector, add the machine to the host boot configuration, so that on g up a host the cloud connector is also powered on automatically.

stomer installs Zerto Virtual Replication and then pairs to the cloud connector using the IP s specified in the Configure and Install Cloud Connector dialog by the cloud er.

Cloud Information From Customers

nstalling a cloud connector, you can supply the Customer Network IP address to the er to use to pair to the cloud provider. However, to prevent the customer from being able to

ud provider information, such as the IP addresses of ESX/ESXi hosts used by the cloud er, you block the customer from seeing this information.

e information about the local site: the vSphere Client console, select the Zerto tab for the vCenter Server node.ick the configuration (cog) button in the local site panel.e Site Configuration dialog is displayed.


3. Click Advanced.The Advanced Settings dialog is displayed.

4. ChbeIPpeNoadpa

5. Cl6. ClNote: FAdvanInitial Configuration 41

eck Masking for new paired sites. Masking enables you to hide information from ing visible from the peer site. Instead of the peer site being able to see a specific ESX/ESXi address and its datastores and NICs, other names can be assigned that are seen by the er site.te: The field is checked before pairing so that the peer sites cannot see any ESX/ESXi IP dresses, datastores or NICs until masking is defined in the Site Management dialog, after iring.ick Save.ick Close.or full details about the Advanced Settings dialog, see the Site Configuration ced Settings, on page 101.


Enable the Customer to Pair to the Cloud Provider

Zerto Virtual Replication is installed on both the customer and cloud provider sites. You have to pair these two sites to enable replication between the sites before configuring replication.On the very first access to a Zerto tab in vSphere Client console, the customer pairs to the cloud provid

The cuthe IPPort fAfter pdisplaInitial Configuration 42

er.

stomer chooses the Start by pairing to a site with a license option and enters provided by the cloud provider in the Pair site address field. leave the value in the ield as 9081.airing, the panels for the local site, on the left, and the remote, peer, site, on the right, are

yed.


Define Masking for a Site

Masking enables you to mask host information from being visible from the peer site. Instead of the peer site being able to see ESX/ESXi IP addresses and datastores and NICs, other names can be assigned that are seen by the peer site.

To spe1. In2. Cl

Th

Th3. Cl

ThNocoInitial Configuration 43

cify site masking information to be visible by the customer site: the vSphere Client console, select the Zerto tab for the vCenter Server node.ick the Site List button in the peer site panel.e Site List dialog for the site is displayed.

is dialog lists all the sites paired with the local site and site information about the sites.ick the Edit button for a site in the list which will have masking defined for it.e Peer Site Configuration dialog for the site is displayed.te: You can also access the Peer Site Configuration dialog by clicking the nfiguration (cog) for the peer site in the topology view.


4. Sp5. In

malimmois

6. Inoramrepr

7. CharsitNoth

8. In9. Fr

Nota

10. InInitial Configuration 44

ecify a name to identify the organization hosting the site. the Max number of protected VMs field specify the maximum number of virtual chines that this organization is permitted to protect. An empty value means there is no it. If the maximum number of VMs is not reached but the maximum storage is reached, no re virtual machines can be protected, unless the value of Max protected storage (GB)

increased. the Max protected storage (GB) field specify the maximum storage that this ganization is permitted to protect. An empty value means there is no limit. If the maximum ount of storage is not reached but the maximum number of protected virtual machines is

ached, no more virtual machines can be protected, unless the value of Max number of otected VMs is increased.eck the Mask vCenter Resources checkbox. Once checked, no vCenter Server resources

e exposed to the peer site. You then use the VC tab to expose resources you want the peer e to see.te: If you want the peer site to protect its virtual machines to vCloud Director only, check e Mask vCenter Resources checkbox without defining any resources. the VC tab, click the Add button for the Cluster & Hosts list.om the displayed Select list, add the ESX/ESXi hosts that you want to hide.te: Once the Mask vCenter Resources checkbox is set, only the information added in the bs in this dialog is displayed in the peer site. the Presented as column, enter the name that you want displayed in the peer site.


Note: Click the copy link to copy the original name to the Presented as column, if you want this specific entry to be visible in the peer site.

11. Repeat steps 9 and 10 for the Resource Pools, Datastores and Networks lists.

12. IndisVPInitial Configuration 45

the Folder field, specify the folder where you want to save recovered virtual machines and ks. The specified folder and any sub-folders are the only folders displayed when creating a G in the peer site.


When creating a VPG in the peer site, the masked values are presented:

The IPthey wWhentargetThe ho

Set U

You se S MInitial Configuration 46

addresses for the host were masked to Cld1. Any other hosts are not displayed because ere not added to the Cluster & Hosts list in the Peer Site Configuration dialog.

the Mask vCenter Resources checkbox is not set, the IP addresses for the hosts in the site with a VRA installed, are displayed.st IP addresses for the target site are displayed.

p vCloud Director (If Used)

t up using vCloud Director by performing the following:etting up vCD and Configuring Provider vDCs, below.asking vCloud Director Organization vDCs and Networks, on page 50.


Setting up vCD and Configuring Provider vDCs

When vCloud Director is used, you can have the journals on separate datastores from the recovery volumes. For example, you might prefer to keep the recovery volumes on storage with better performance, security, and reliability and the journal on less expensive storage1.If you did not set up access to vCD for the Zerto Virtual Manager when installing Zerto Virtual ReplicNote: BserverRun Zthe vCconnecinstallprereqthe Zebeing installAMQPare disvCD is

To set1. In2. Cl

Th3. Cl

Th

1. As paDurinthe lareflecInitial Configuration 47

ation, set it up using the following procedure.efore setting up Zerto Virtual Replication to work with vCD, you must have an AMQP

installed. Zerto provides an AMQP installation kit if you do not have one installed for vCD. ertoAMQPInstallWizard.exe from the kit and when prompted enter the IP or host name of D and the administrator user and password to access this vCD. The Zerto Virtual Manager ts to the vCD and checks whether an AMQP server is installed. If an AMQP server is not ed, Zerto recommends using RabbitMQ, which in turn requires Erlang/OTP as a uisite. Links to the sites to install both Erlang/OTP and RabbitMQ are provided as part of rto AMQP installation. Use these links to install Erlang/OTP and then RabbitMQ before able to continue with the Zerto AMQP installation. If an AMQP server was already ed, change the connection details displayed to those defined in vCD. If you installed the server as part of the Zerto AMQP installation, the default settings for these installations played, with a user and password of guest. At the end of the Zerto AMQP installation, updated with these settings.

up access to vCD: the vSphere Client console, select the Zerto tab for the vCenter Server node.ick the configuration (cog) button in the local site panel.e Site Configuration dialog is displayed.ick Advanced.e Advanced Settings dialog is displayed.

rt of recovery after a failover or move operation, the data in the journal is promoted to the recovered virtual machines. g this promotion, the virtual machines can be used, and Zerto Virtual Replication makes sure that what the user sees is test data, whether from the virtual machine disks or from the journal. If the journal is on a slow storage device, this is ted in the response time the user experiences.


4. Cl

5. Ch6. En

AdvCUsPaAMAM

7. ClInitial Configuration 48

ick the Configure vCD button.

eck the Use vCD checkbox.ter the VMware vCloud Director access details:dress The IP address or host name of the machine where vCD runs. When connecting to D with multiple cells, enter the virtual IP for the network load balancing used by the cells.ername The user name for an administrator to vCD.ssword A valid password for the given user name.QP-Username The user name for the AMQP server.QP-Password A valid password for the given AMQP user name.

ick Save in the Configure vCD dialog.


8. Click Save in the Advanced Settings dialog.Note: If a proxy server is defined on the machine where the Zerto Virtual Manager is installed, add the Zerto Virtual Manager IP address to the Internet Explorer exception list.

To configure provider vDCs:1. In the vSphere Client console, select the Zerto tab for the vCenter Server node.2. Cl

Th3. Cl

Th4. Cl

5. Ad6. Ad

in7. Se

orNoseha

8. SpPrInitial Configuration 49

ick the configuration (cog) button in the local site panel.e Site Configuration dialog is displayed.ick Advanced.e Advanced Settings dialog is displayed.ick the Configure provider vDCs button.

d the provider vDCs that you want to enable to use Zerto Virtual Replication.d datastores and specify how you want the organization to see these datastores, by clicking

the Presented as column to edit the content.lect what datastores not specifically added to the list are used for: either they are not used they are used for recovery volumes only.te: If the option Unlisted datastores are used only for recovery volumes is lected, it refers to unlisted datastores of all provider vDCs, even those provider vDCs that ve not been added to the upper table.ecify for each datastore added, what it can be used for: Recovery volume, Journal and eseed.


Onor

9. Cl

Mask

Whennetwo

To spe1. In2. Cl

ThThco

3. ClTh

4. Inmalimmois

5. InoramInitial Configuration 50

ly datastores marked as preseeded can be used for preseeded disks. This prevents different ganizations being exposed to datastores of other customers using the preseed option.ick Save.

ing vCloud Director Organization vDCs and Networks

vCloud Director is used, the cloud provider can restrict what organization vDCs and rks an enterprise connecting to the vCD can see.

cify masking information for vCloud Director: the vSphere Client console, select the Zerto tab for the vCenter Server node.ick the Site List button in the customer, peer, site panel.e Site List dialog for the site is displayed.is dialog lists all the sites paired with the local site and information about the

mmunication between the sites via the VPGs defined.ick the Edit button for the site for which you want to define masking.e Peer Site Configuration dialog for the site is displayed. the Max number of protected VMs field specify the maximum number of virtual chines that this organization is permitted to protect. An empty value means there is no it. If the maximum number of VMs is not reached but the maximum storage is reached, no re virtual machines can be protected, unless the value of Max protected storage (GB)

increased. the Max protected storage (GB) field specify the maximum storage that this ganization is permitted to protect. An empty value means there is no limit. If the maximum ount of storage is not reached but the maximum number of protected virtual machines is


reached, no more virtual machines can be protected, unless the value of Max number of protected VMs is increased.

6. Check the Mask vCD Resources checkbox. Once checked, no vCD resources are exposed to the peer site. You then use the vCD tab to expose resources you want the peer site to see.Note: If you want the peer site to protect its virtual machines to the underlying vCenter Server only, check the Mask vCD Resources checkbox without defining any resources.

7. Se

8. SenaupThOr

9. Ad10. Sp

us11. ClInitial Configuration 51

lect the vCD tab.

lect the organization from the Select Organization dropdown listbox. The organization mes are those included in the Configure provider vDCs dialog, as described in Setting vCD and Configuring Provider vDCs, on page 47.e organization vDCs and networks for this organization can then be added to the ganization vDC and Organization Networks lists.d the organization vDCs and networks that you want the customer to see.ecify the folder name where preseeded disks are saved. You must have specified disks to e in the Configure provider vDCs dialog, described is the previous section.ick Save.

Specific Steps for Customers Pairing to a Cloud Provider


After installing Zerto Virtual Replication customers using a cloud provider for their recovery requir P In

Pair

Zerto pair thOn theprovid

The cuthe IPPort fAfter pdisplaInitial Configuration 52

ements perform the following:air to the Cloud Provider, below.stall Virtual Replication Appliances, on page 53.

to the Cloud Provider

Virtual Replication is installed on both the customer and cloud provider sites. You have to ese two sites to enable replication between the sites before configuring replication. very first access to a Zerto tab in vSphere Client console, the customer pairs to the cloud er.

stomer chooses the Start by pairing to a site with a license option and enters provided by the cloud provider in the Pair site address field. leave the value in the ield as 9081.airing, the panels for the local site, on the left, and the remote, peer, site, on the right, are

yed.


The sisite.In thestatusHoverthe eritem, a

Insta

The ZeReplicmanagESX/EESX/EIt is revirtuaprotecInitial Configuration 53

te information, specified during the installation is displayed at the top of the panel for the

middle at the top of the Zerto tab indicators show the Zerto Virtual Replication status. The indicators are green when there are no problems, yellow for warnings and red for errors. ing the mouse over the red or yellow indicator, when it is showing, displays the reason for ror or warning. This information is also displayed in the Alerts report, under the Reports vailable after a VRA is installed and the site is paired with another site.

ll Virtual Replication Appliances

rto Virtual Replication installation includes the installation package for Virtual ation Appliances (VRAs). A VRA is a Zerto Virtual Replication virtual machine that es the replication of virtual machines across sites. A VRA must be installed on every SXi which hosts virtual machines that require protecting in the protected site and on every SXi that will host the replicated virtual machines in the recovery site.commended to install a VRA on every ESX/ESXi host in each vCenter Server, so that if a l machine being protected is moved for example, using VMware VMotion, it is still ted.


Note: When protecting virtual machines in a cluster, it is recommended to install a VRA on every ESX/ESXi host in the cluster so that if protected virtual machines are moved from one host in the cluster to another host in the cluster there is always a VRA to protect the moved virtual machines, or to disable DRS on the virtual machines to be protected. If you are protecting a vApp, you must install a VRA on every ESX/ESXi host in the cluster on both the protected and recovery sites and ensure that DRS is enabled for these clusters.

To insTo insmemoalso k Th If

us Th

suNote: Iinstall1. In

Th2. Cl


tall Zerto Virtual Replication Appliances (VRAs) on ESX/ESXi hosts:tall a VRA, 12.5GB datastore space is required. The VRA requires at least 1GB of reserved ry. The VRA can only be installed on ESX/ESXi hosts version 4.0U1 and higher. You must now the following information to install a VRA:e network used to access the VRA in the protected site.a static IP is used instead of DHCP, the IP address, subnet mask and default gateway to be ed by the VRA.e network settings to access the peer site; either the default gateway or the IP address, bnet mask and gateway.nstalling a VRA requires that SSH is enabled on the host during the installation. After the ation you can close this SSH connection. the vSphere Client console, select the Zerto tab for the vCenter Server.e panels for the local site, on the left, and the remote, peer, site, on the right, are displayed.ick the Manage VRAs button in the local site, left, panel.e Manage VRAs dialog is displayed.


Norig

3. If SiThInitial Configuration 55

te: You can resize the Manage VRAs dialog by dragging the marker symbol in the bottom ht corner of the dialog.

the access to the peer site VRAs is not via the network default gateway, check the Paired te Routing checkbox and click the link.e Configure Paired Site Routing dialog is displayed.


SpTh


ecify the IP address, subnet mask and gateway to access the peer site VRAs and click Save. ese access details then apply to every VRA defined on this site to access the peer site.ick the Install New VRA button.e Configure & Install VRA dialog is displayed.


Specify the following target host details:Host The target ESX/ESXi host for the VRA. The drop-down displays the hosts managed by the vCenter Server which do not have a VRA installed.Password The password used to access the host for the root user. This field is required for ESXi 4.x and 5.x hosts. This field is disabled for ESX 4.x hosts. When the checkbox at the side is checked the password is displayed as asterisks.DajouNeAmdea g

WbothIf thSpCoIf

5. ClThdiaco

1G

2G

3GInitial Configuration 57

tastore The datastore that the VRA will use for mirror virtual machines and for its rnal. You can install more than one VRA on the same datastore.

twork The network used to access the VRA.ount of VRA RAM The amount of memory to allocate to the VRA. The amount specified is

pendent on the number of volumes being protected or recovered. Use the following table as uideline:

hen the VRA is used both for protection and recovery, the number of volumes is the sum of th sites. For example, if four volumes are protected on one site and three on the peer site, e number of volumes is seven and the VRA requires 1GB.the VRA is protecting or recovering more volumes than specified for the amount of RAM, e chances that the VPGs require bitmap syncs will increase due to the load on the VRA.ecify the following VRA network details:nfiguration Either have the IP address allocated via a static IP address or a DHCP server. you select the Static option, which is the recommended option, enter the following:

Address The IP address for the VRA to communicate with the Zerto Virtual Manager. Subnet Mask The subnet mask for the network. The default value is 255.255.255.0.Default Gateway The default mask for the network.

ick Install.e installation starts and the status is displayed in the Status field of the Manage VRAs log. This process includes a number of tasks, which you can see in the vSphere Client

nsole tasks list.

VRA Protecting Volumes

VRA Recovering Volumes

VRA Protecting and Recovering Volumes

B 9 volumes 15 volumes 9 volumesB 56 volumes 90 volumes 56 volumesB 103 volumes 165 volumes 103 volumes


6. RewhNo

7. ClClick tinstallAfter pConfigInitial Configuration 58

peat steps 4 and 5 to add a VRA to every ESX/ESXi host that hosts virtual machines for ich you want replication.te: It is recommended to install a VRA on every listed ESX/ESXi host.ick Close to exit the dialog. The installation procedure continues.he Manage VRAs button to reopen the Manage VRAs dialog to monitor the VRA ation.airing the sites, click the configuration (cog) button in the local site panel to access the Site uration dialog to install additional VRAs.

Chapter 3: Protecting Virtual Machines

Virtuaa grouexampvirtuarequirOnce asite. Tsize ofprotecAppliapromoThe fo C P P P

Con

You prmachiThe VsingleESX/Esame csite isprotecprovisNote: Ysite be59

Zerto Virtual Replication Administration Guide

Documents

Transcript of Zerto Virtual Replication Administration Guide