1 of 20

APEX Backup Services for �Hybrid Workloads Overview

Internal Use - Confidential

2 of 20

Agenda

Architecture overview
Use cases and workloads
Why APEX Backup Services

Internal Use - Confidential

3 of 20

Architecture

Internal Use - Confidential

4 of 20

Direct to cloud architecture

CloudCache

(optional)

LAN-speed

RPO/RTO

Direct to cloud

No hardware. No software.

VM

(vSphere, Hyper-V)

NAS

(NFS/SMB)

Linux

VMware Cloud �on AWS (VMC)

DISASTER RECOVERY�customer AWS

EASY RECOVERY�Any location�(server or the cloud)

Internal Use - Confidential

APEX Backup Services is built natively on AWS
We backup up directly to the cloud – and we don’t require any HW/SW to manage like you’d see with legacy on-prem solutions

You can see the key workloads that we support on the left hand side, and we also support VMware cloud on AWS as well as AWS Outposts

Once data is backed up to the cloud… we tier it to reduce costs 🡪 data sits in S3 up to 90 days – after 90 days its sent to Glacier
Servers can be recovered to any location
Important to note that here are no egress costs with APEX Backup Services, no matter how large the data set
And we also support Disaster recovery as a service for VMware environments – which we’ll dive deeper on in future sessions

- we also offer an optional on-premises cache, this is offered as an optional software appliance for workloads that require very low RPO/RTOs – I’ll expand on this on this in the next slide

A picture of the architecture talks to the core value

First – No HW or Software – Direct to cloud backup for key workloads you see on the left-hand side as well as support for VMware Cloud on AWS.

Second - Once that data lands in the Druva cloud it's typically stored in warm storage, but if you need to hold data for longer periods of time, we offer the ability to automatically tier that data to cold storage. It’s our way of passing additional savings on to you.

Third – Disaster recovery in your AWS VPC that is automated, secure, and fast helps you meet RTOs in minutes.

Fifth – An optional on-premises cache feature, offered as a software appliance, to help you meet demanding RPOs, say in a remote office with limited WAN, or demanding RTOs in either remote offices or the data center. This feature helps with those corner cases where direct to cloud cannot meet your RPO/RTOs.

5 of 20

High level architecture for Hybrid Workload

VPC

Backup and Recovery with AWS

VPC

Cloud DR - Customer AWS

Customer Workloads

Failback

Compute

Configuration�Services

Metadata

Data

Archival

Phoenix�DR Proxy

At Disaster Time

Snapshot

Volume

Amazon EC2

Amazon RDS

Amazon DynamoDB

Amazon S3

Amazon Glacier

Amazon EC2

Internal Use - Confidential

6 of 20

Detailed architecture for Hybrid Workloads

Storage Nodes

Authentication Services

VPC

Amazon S3

Amazon S3 Glacier

Deep Archive

Amazon RDS

Amazon �DynamoDB

DR Plan, VPC, Subnet, Elastic IP, Amazon EC2 Configuration

Configuration Services and Policies

Intelligent Tiering for Long-term Retention (LTR) - optional

Cloud Platform

VPC

Amazon EC2

Amazon Elastic Block Store (EBS)

Recovered�Servers

At Disaster Time

Phoenix DR Proxy

AWS IAM Roles

AWS IAM Policies

AWS Direct�Connect

VMware Cloud on AWS

Customer Infrastructure

NAS�(NFS/SMB)

LINUX

Backup/Restore

Hot:

0-30 Days

Deduplicated & Encrypted Blocks

Phoenix

CloudCache (Optional)

Gateway

Customer-AWS Virtual Private Cloud (VPC)

Failback

Metadata

Data

(Deduped, Secured)

VM

(vSphere, Hyper-V)

Snapshots

Volumes

VPC Endpoint

Internal Use - Confidential

On this slide we are showing the architecture for Hybrid Workloads. Applications support includes

File Servers – Linux and Windows

Virtual environments – VMware and Hyper-V

Databases: Oracle and SQL

NAS

APEX Backup Services for Hybrid Workloads also offers Disaster Recovery as a Service (DRaaS)

Built natively on AWS APEX Backup Services utilize AWS microservices. The AWS architecture, also references as the cloud platform, is one platform for Hybrid Workloads as well as SaaS Apps and Endpoints.

Now a bit more about the cloud platform architecture:

EC2 = Compute
RDS = config services
S3 = Data / Glacier = Archive
Shard data – separate metadata into DynamoDB and data into S3

Secure:

S3 buckets are not writable by our authenticated process – so a direct access isn’t possible
In addition, the way object storage works is that you actually CAN'T encrypt an object in S3 after it's been written. You can only encrypt a new version of it; the old version is still there  APEX Backup Services can roll back to the old version
Another layer of protection is that only data is stored in S3 and the way it is stored (sharded) requires a separate system (DynamoDB) to reassemble, as the metadata is stored there

All data is encrypted at rest and in flight

Also APEX Backup Services uses a proprietary digital envelop encryption

- Key is split in two (Key encryption key, data encryption key)

- Like having a safety deposit box where you need 2 keys to open it

Never any 3rd party access…

APEX Backup Services does not have access to any customers data

And that’s true even in the event of a subpoena

- No single point of failure since we triplicate data in AWS for HA

7 of 20

Architecture for SaaS Apps

Internal Use - Confidential

On this slide we are showing the architecture for SaaS Apps Workloads. Applications support includes

M365 – Exchange Online, SharePoint Online, OneDrive and Teams
Google Workspace – Google Drive, Google Sheets, Gmail and Google Doc
Salesforce

Built natively on AWS APEX Backup Services utilize AWS microservices. The AWS architecture, also references as the cloud platform, is one platform for Hybrid Workloads as well as SaaS Apps and Endpoints.

Now a bit more about the cloud platform architecture:

Built natively on AWS APEX Backup Services utilize AWS microservices

EC2 = Compute
RDS = config services
S3 = Data / Glacier = Archive
Shard data – separate metadata into DynamoDB and data into S3

Secure:

S3 buckets are not writable by our authenticated process – so a direct access isn’t possible
In addition, the way object storage works is that you actually CAN'T encrypt an object in S3 after it's been written. You can only encrypt a new version of it; the old version is still there  APEX Backup Services can roll back to the old version
Another layer of protection is that only data is stored in S3 and the way it is stored (sharded) requires a separate system (DynamoDB) to reassemble, as the metadata is stored there

All data is encrypted at rest and in flight

Also APEX Backup Services uses a proprietary digital envelop encryption

- Key is split in two (Key encryption key, data encryption key)

- Like having a safety deposit box where you need 2 keys to open it

Never any 3rd party access…

APEX Backup Services does not have access to any customers data

And that’s true even in the event of a subpoena

- No single point of failure since we triplicate data in AWS for HA

8 of 20

Hybrid Workloads

Internal Use - Confidential

9 of 20

APEX Backup Services for Hybrid Workloads

Use cases

Virtual Servers

VMware / VMware on AWS (VMC)
Hyper-V

File Servers

Windows / Linux

Databases

SQL / Oracle

NAS

CIFS/SMB and NFS

CIFS / SMB / NFS

NAS Storage

Cloud Platform

Internal Use - Confidential

10 of 20

Manage cloud SLAs better with CloudCache

Meet RTO/RPOs from cloud, without costs �& complexity of traditional infrastructure
For VMware, Hyper-V, SQL, file server workloads in remote offices or data centers
Keep hot snapshots, up to 30 days
Enables local LAN speed backup/restore with commodity hardware
Supports bandwidth management - off peak hours sync to cloud (ideal for ROBO)

Production workloads

Virtual appliance

CloudCache

Data Center or Remote Office

Cloud Platform

Internal Use - Confidential

CloudCache is designed to help customer meet RPOs and RTOs when they have insufficient bandwidth for a given backup window… and is typically used in remote offices
It is a no charge feature of Phoenix Enterprise and Elite versions
not intended to be a secondary storage backup solution or to mimic scale-out storage solutions. Its really designed to help customers get data to the cloud or out of the cloud with the right balance of cost and performance.

- Enables customers to keep a Warm copy of their data locally 🡪 for up to 30 days… and can help provide LAN speed back-up and restores

- No hardware lock-in – deployed as an OVA on commodity hardware

Also can be used for initial seeding of data to the cloud

Helps to support bandwidth management with off peak hours sync to cloud

Remove appliance from your environment any time without impacting backups/recovery system

Note: Golden copy of data and metadata in cloud

11 of 20

Snowball Edge

Seamless Procurement

Customers can easily order, track, and return their Snowball edge device directly from the Phoenix dashboard

Zero customer cost

Bundled in Elite / Enterprise license
Minimum data size 40TB (Source)

Ship 100s of PB Securely

Tamper evident enclosures, 256-bit encryption, and industry standard Trusted Platform Modules (TPM)

Cloud Platform

Internal Use - Confidential

12 of 20

Long Term Retention for Hybrid Workloads

Warm snapshots (S3)

Move to Glacier Deep Archive after 15 days

Minimum 1yr retention
Average data recovery 36hrs (defreeze)

12

Internal Use - Confidential

13 of 20

Features delivered via the cloud platform

Internal Use - Confidential

14 of 20

Unique global, source-side deduplication

Increase savings with global, deduplication & compression

Dedupe across all workloads and data sources
Deduplication across warm & cold storage tiers

Only move changed blocks – every time (source dedupe + incr. forever)
Scale on-demand

No more under/over-provisioning
Eliminate hardware bottlenecks with cloud-based metadata

Data center

Remote office

No hardware here

Cloud Platform

Internal Use - Confidential

backups are incremental forever and only unique blocks are sent to the cloud to be backed up 🡪 which helps to reduce bandwidth
And we use our patented global and app-aware source-side deduplication 🡪 so customers only pay for the data that they backup vs for paying front end capacity
Capacity can be scaled on demand 🡪 which means you no longer need to worry about under or over provisioning hardware

Increase savings with global, app-aware deduplication

Reduces bandwidth & storage beyond the data center

Granular, block-level dedupe based maximizes efficiency

Only move the blocks that changed

Source-based deduplication that works on first backups

Incremental forever further reduces

Eliminate bottlenecks with cloud-based metadata

Infinite scale means no bottlenecks for backups or restores

No storage-based garbage collection

Goodbye backup storage management

15 of 20

Stringent privacy and security standards

APEX Backup Services

Powered by

Internal Use - Confidential

16 of 20

Simple, scalable, & secure data protection

Global availability
On-demand scale and capacity
Extensive regional storage options
Robust security model

15+ AWS storage regions

Internal Use - Confidential

17 of 20

Your data is secure and better isolated

SaaS-based data protection

Maintains a Zero Trust architecture model

No SSH access to production nodes

You control the key to your data

Multi-layered access controls
Industry standard envelope encryption

Immutable and encrypted data storage

Data sharding adds security

Backup data is isolated from your network
APEX Backup Services runs on AWS infrastructure for strong network security

Mgmt Console

Bastion

Cloud Ops

Endpoints

Multi-Factor

Admin

VPN connection

Envelope Encryption

Amazon S3

Amazon DynamoDB

Amazon EC2

Other Svcs

Customer backup sources

TLS

APEX Backup Services

Internal Use - Confidential

18 of 20

Save costs and reduce TCO

One license metric

Post-dedupe storage consumption

What drives your TCO?

Eliminate HW/SW at multiple sites
Extreme storage efficiency
Eliminate tape for long-term retention �w/ intelligent tiering
Administration made easy

Other benefits

Improve security of backup/ archival data
Analytics and re-use of backup data

TCO Calculator (tco.druva.com)

Internal Use - Confidential

Your TCO will be much lower with APEX Backup Services. Many of our customers see up to 50% or better TCOs.

We also have a quick 5 step TCO calculator that you can utilize on the Druva website – included a screen shot of what that looks like on the right

What are the drivers that makes this happen?

First, eliminating the hardware and software that customers might have across multiple sites

Second - storage efficiency - extreme storage efficiency that we get with global deduplication, compression, forever-incrimentals, and the ability to dedupe across workloads.

Third, our intelligent tiering for long-term retention enables a simple and highly cost-effective cold storage option that lets customers eliminate tape for long-term retention - by that I mean by 5, 10, 20, 30-year type retention which becomes one more area of cost savings

Fourth, but not least importantly, is the administration savings. Customers talk about as much as 30 hrs./wk. or more, but this dependent on your team and previous products used.

19 of 20

Why APEX Backup Services

Facts to remember

Lower TCO
No stranded capacity
No maintenance fees or multi-year commitments

Deploy in minutes + bi-weekly updates
No more SW, HW, and security management

High performance
Scale with AWS
Data isolation & envelope encryption protects you

APEX Backup Services

Performance scale

security

TCO

Time to value

Internal Use - Confidential

What I hope you’ll remember about APEX Backup Services

FIRST - Performance, Scale and Security - we solve your over deployed/ underperforming architecture problem and help you meet your RPOs and RTOs at a fraction of the cost. We leverage AWS to offer infinite scale, and provide you with data isolation and envelope encryption to make your

data more secure.

SECOND – Lower TCO

Eliminating stranded capacity

Global, source-based deduplication across workloads that our customers tell us performs better than on-premises solutions drives more savings.

THIRD – Ease of use AND value-add services

Deploy and start using in minutes. Enjoy 2x / month no-touch updates to your platform

You have no infrastructure to deploy or manage, no maintenance support contracts or multi-year commitments

No administrative overhead can also reduce your initial spend on infrastructure.

Use value add services that let you do more with your data in the cloud

DRaaS for data center and cloud workloads

Storage Insights to lower costs

And ecosystem integrations like ServiceNow

Now is the time to future-proof your backup strategy

20 of 20

Internal Use - Confidential