Components of the Zerto Platform - Zerto

Software-only Protection at Any Scale

Simple, scalable data protection with an easy-to-deploy, low footprint, software-only architecture.

Architecture Guide for Zerto

Zerto brings together disaster recovery and data protection into a single and simple cloud data management and protection solution across on-premises, hybrid, and multi-cloud environments.

Zerto’s Components

Zerto’s award-winning VMware-based replication and journaling technology lets you seamlessly migrate workloads and perform disaster recovery on Google Cloud VMware Engine without refactoring your applications.

Zerto consists of five main components which allow us to easily protect, recover, and move applications at any scale.

Zerto Manager in different environments

from left to right: virtualized (ZVM), cloud (ZCA), containerized (ZKM)

Click outside of the image to exit the popup

Click to enlarge

The Zerto Managers

A Zerto Manager operates everything needed for the replication between the protected and recovery sites, except for the actual replication of data.

It interacts with the platform it protects and orchestrates recovery, monitors changes, and collects information on entities available for protection within that environment.

In virtualized environments, it is referred to as a Zerto Virtual Manager (ZVM), while in containerized environments it is called the Zerto Kubernetes Manager (ZKM).

In public cloud environments, such as Azure and AWS, Zerto uses an all-in-one instance called a Zerto Cloud Appliance (ZCA) that combines management and replication.

Zerto Manager Overview

Watch the video

Zerto Platform: ZVM Overview

To exit, click outside the image

Virtual Replication Appliances

A Virtual Replication Appliance (VRA) is a purpose-built software appliance installed on each host where virtual or Kubernetes applications are to be protected from or to, delivering a true scale-out architecture.

This appliance continuously replicates the data from protected entities to its local and/or remote target, where it then stores the data in the journal.

This same scale-out appliance handles copying data from the journal to a long-term retention repository.

In public cloud environments, Zerto scales replication using a cloud-native scale-out architecture.

Zerto Replication Appliance Overview

Watch the video

Zerto Platform: VRA Overview

To exit, click outside the image

Zerto Replication Appliance (VRA) in different environments

(from left to right: virtualized, cloud, containerized)

Click outside of the image to exit the popup

Click to enlarge

Protection Groups enable application consistency

Click outside of the image to exit the popup

Click to enlarge

Protection Groups

Zerto protection, mobility, and backup are all configured through the creation of Protection Groups (PGs).

Today, there are very few scenarios where an application is run on a single server or container. Instead, most applications have multiple VM or microservice dependencies. Using the traditional method of protecting individual components results in significant challenges to recovering your complete application.

Zerto Protection Groups differ by allowing you to protect one or more components together in a consistent fashion, ensuring every point in time that is inserted into Zerto’s journal is from the same point in time for all components within the Protection Group. This allows easy recovery of an entire application, and all its dependencies, to a consistent point in time.

Zerto Protection Groups Overview

Watch the video

Zerto Platform: Virtual Protection Groups (VPGs) Overview

To exit, click outside the image


In addition to Protections Groups, Zerto’s replication appliances store all protected data in the journal.

The journal stores all changes for a user-defined period, up to 30 days, and allows you to recover to any point in time within that journal, ensuring your recovery point objective (RPO) is always as low as possible.

How the Journal Works

Watch the video

Zerto Platform: How does the Journal Work?

To exit, click outside the image

Data flow in Zerto’s journal

Click outside of the image to exit the popup

Click to enlarge

Long-Term Retention (LTR) Architecture

Click outside of the image to exit the popup

Click to enlarge

Long-term Retention Repositories

In addition to flexible options for short-term recovery scenarios using the journal, most organizations that have compliance requirements need long-term retention (LTR) as an integral part of their data protection platform.

Compliance standards often require you to keep and recover data for longer than 30 days. Using the data already protected by Zerto, combined and stored in a journal, allows you to offload point-in-time copies to secondary storage targets as often as you want without impacting production.

Recovery from LTR Repositories

Watch the Demo

Zerto Platform: Recovery from Long-term Retention (LTR) Repositories

To exit, click outside the image