1. HPE Helion
CloudSystem
Enterprise ®
Disaster Recovery (DR)
with Zerto Virtual
Replication (ZVR) and
CSrecover
1

2. Forward-looking statements
The content of this presentation is subject to change without notice.
This document may contain forward-looking statements regarding future operations, product development, product capabilities,
and availability dates. This information is subject to substantial uncertainties and is subject to change at any time without prior
notification. Statements contained in this document concerning these matters only reflect Hewlett Packard Enterprise’s predictions
and/or expectations as of the date of this document and actual results and future plans of Hewlett Packard Enterprise may differ
significantly as a result of, among other things, changes in product strategy resulting from technological, internal corporate, market,
and other changes. This is not a commitment to deliver any material, code, or functionality and should not be relied upon in making
purchasing decisions.

3. What rising costs of downtime means to our customers
3
• IT is a critical business driver – needs to stay
always ON
• Almost every industry faces unplanned downtime,
with a deep impact on revenue and reputation
• Besides revenue – downtime takes its toll on staff
productivity, end-user productivity, and disrupts
business
• The most common cause of downtime is failure –
hardware, network, software, application, power,
human breach – it can occur at any level
• Failures often cause data corruption, ability to
recover from corruption is critical
• Ransomware attacks are increasing, reducing
data and application availability

4. What transformation means to our customers
10K APPS
4
Irrespective of the deployment
model, enterprise expectations
around application and service
availability have not changed

5. How do our customers measure availability
–Recovery Point Objective (RPO) and Recovery Time Objective (RTO)
are used to describe availability requirements.
– RPO - describes the point in time to which the data must be recovered
– How much data can my business afford to lose?
– RTO - describes the time from when a failure occurs until the business process must become active again.
– How long can my business afford the business process to be unavailable?
RPO/RTO Relationship
Failure Point
RPO RTO
Primarily Influenced by Technology
(Async vs Sync)
Primarily Influenced by Architecture
(Active/Passive to Active/Active)
System Processing Time
Last Saved Data
Point
Recovery
Complete
Potential for Data
Loss
Time to Recover

6. Spectrum of customer needs for Disaster Recovery (DR)
RPO
(less, or no,
data loss)
Days
Hours
Mins
Secs
Instant
None
Secs
Mins
Hours
Days
Increasing
Availability
Tape
Disk or
Cloud
Backup Recovery
Async
Active/
Passive
Async
Active/
Active
Data Replication
Sync
Active/
Passive
Sync
Active/
Active
RTO (faster recovery)

7. HPE and Zerto enter into a Reseller relationship to offer Disaster
Recovery to CloudSystem Enterprise (CSE) customers
7
3000 Customers
300 Cloud
Providers
50 countries
450 global
employees
100% YoY growth
8 of the 14
top DRaaS
Providers
use Zerto
Virtual
Replication

8. One Strategic Solution – Cloud Continuity Platform
2
Any storage and ESXi Hypervisor, introducing DR Appliance to host ZVM and CSrecover
CSE 10.0
Zerto
CS DR VMware
Customer VM
DCM Zerto Replication Network (WAN)CLM
Data Center 2Data Center 1
DR Appliance
Management
ZVM
Enterprise
(CSA/OO)
Monitoring
DB. MSG
Control
ESXi Host 1
VRA
VRA
CS
Recover
Compute Region A
vCenter A
Management
Enterprise
(CSA/OO)
Monitoring
DB. MSG
Control
ESXi Host 2
VRA
Management
Enterprise
(CSA/OO)
Monitoring
DB. MSG
Control
ESXi Host 3
VRA
Compute
ESXi Host 1
VRA
Compute
ESXi Host 2
DR Appliance
ZVM
Control
ESXi Host 1
VRA
VRA
CS
Recover
Compute Region B
vCenter B
Control
ESXi Host 2
VRA
Control
ESXi Host 3
VRA
Compute
ESXi Host 1
VRA
Compute
ESXi Host 2
VM
VM
VM
VM
VM
VM
VM
VM

9. HPE Helion CloudSystem with Zerto Value Proposition
HPE Helion CloudSystem Enterprise with Zerto Virtual Replication (ZVR)
makes your multi-cloud enterprise environment continuously available and
resilient
9

10. Zerto Revolutionized Disaster Recovery
10
Zerto Hypervisor Based
Replication
Replication was in the wrong
place – the physical layer
Enterprise-class,
Software-Defined
Replication & Recovery
Automation solution
Hypervisor
Security
Networking
Servers
Storage
Replication

11. Totally Protected?
11
06:00 09:00 15:00
Backup
12:00
Snapshot Snapshot
12:00 18:00
Snapshot
Power Interruption or
Hardware Failure
Cryptolocker Virus
Infection
File deletion, Application
or Human error
= Data Loss & Downtime
24h+
4h
+

12. Zerto Virtual Replication – Journal based Recovery
12
Re-wind and recover from any point in time
06:00 09:00 18:0000:00 12:00 15:0
0
2 week
Journal
Sites Apps FilesVMs

13. DR Use Cases
13

14. Hybrid Cloud Continuity Platform
2
+200
Hybrid Cloud
DRaaS, Intra-Cloud & Reverse DRaaS
Satellite Offices
Any Distance
Private Cloud
Any Storage ESXi Hypervisor
Public Cloud
DRaaS to AWS or Azure
Future Proof
Support future
technologies
Supported in the first GA Release

15. Benefits
15
Improved TCO with replacement of Storage Replication and SRM
Simplifying DR with Always-On Protection & Virtual Awareness
Flexibility with replication between different SAN vendors
Upgrade from Veeam snapshot recovery for better RPO
Low RPO/RTO with ZVR solution

16. Zerto Differentiation
16

17. Consistent Protection & Recovery
17
• Simple, scalable, protection & recovery of VMs, not
LUNs
• Recover multi-VM application stacks together
• Point in time recovery, write ordering & application
consistency
• Prioritize replication, pre-seeding, reduce initial sync
• Support virtualization features vMotion, svMotion, HA etc
Production
Site
Enterprise Applications
VM
VM
VM VM
vDisk
vDisk
CRM, ERP, SQL, Oracle, SharePoint,
Exchange
CRM VPG VM VM VM VM VM
SQL VPG VM VM VM VM VM
VM
VM
VM
VM
vDisk
vDiskvDisk
VM
RPO 4
seconds
RPO 9
seconds
ERP VPG RPO 6
seconds
VM VM VM VM VM
• LUN Consistency Group evolved = Virtual Protection Group
VM VM
VM
vDisk
VM
vDisk
VM
VM VM
VM
vDisk
vDisk
vDisk vDisk
vDisk

18. Removing Risk with Simple Recovery
18
Disaster Event!
Click Failover
Select Apps
Verify
Start Failover
Recovery Process:

19. Zerto Differentiation
19
Heterogeneous
support
• Any storage and server any
OS
• Multiple Hypervisors
Low RTO/RPO
• Fast Recovery is key
• Operational Recovery is a
plus
Orchestration
Automation
• Automation of DR and test
• API driven
• Cloud enabled, Multi-tenant
Heterogeneous
 Hypervisor
based
 Any storage
 Any OS
 Multiple
Hypervisors
RTO/RPO
 Seconds of
RPO
 Minutes RTO
 Non-disruptive
testing
 Application
level SLAs
Orchestration
 Boot order
Mgt.
 IP address
change
 Failover & Test
automation
 HPE OO
Integration
automation

20. Zerto Differentiation
20
VM
Recovery
• Recover virtual machines
• Application Protection
Groups
Network
Efficient
• WAN Compression a must
• Latency Tolerance
Operational
Recovery
• Recovery From Corruption
• Protect against logical
corruptions with minimum
data loss
WANEfficient
 Built in
compression
 Unlimited
distance
 Bandwidth
throttling
AppRecovery
 Recover
individual VMs
not volumes
 Virtual
protection
Groups for
Application
level recovery
Corruption.Recovery
 Journal based
replication
 CDP
 To 2 weeks
data retention
in journal
 Backup option
for longer
retention

21. Key Takeaways

22. HPE Confidential
Lead with
ZVR
Position ZVR, when you hear this…
DR to another private cloud
Lead with ZVR Lead with ZVR
Need an
alternative to
VMware
SRM?
Need to migrate to CS or
from one hypervisor to
another
Lead with
ZVR
I have a variety of hypervisors
Lead with ZVR Lead with ZVR
I have
different
storage
solutions
I need an offsite backup

23. HPE Confidential
Call to Action
Start the dialog with customers on this new
offering
Invite customers for a POC / Trial Pilot (free
license available)
Take help from your Zerto counterparts –
Regional intros

24. HPE Confidential 24