Introduction
Zerto provides a business continuity (BC) and disaster recovery (DR) solution in virtual environments, enabling near real-time replication with write-order fidelity and minimal impact on production workloads. It supports multiple hypervisors such as vSphere and Hyper-V, as well as public cloud platforms like Azure, allowing workloads to be protected, migrated, and recovered either within the same hypervisor or across different environments. Zerto is installed at both the protected and recovery sites, with disaster recovery operations managed through a browser-based user interface. Additionally, Zerto can be managed programmatically using RESTful APIs or PowerShell cmdlets.
Zerto helps customers accelerate IT transformation by eliminating the risk and complexity of modernization and cloud adoption, replacing multiple legacy solutions with a single IT Resilience Platform™ that redefines how disaster recovery, retention, and cloud operations are managed. It achieves this by delivering enterprise-class disaster recovery and business continuity software designed for virtualized infrastructure and cloud environments.
ZVM is a Windows service that orchestrates all aspects of replication between the protected and recovery sites, excluding the actual data transfer. It communicates with hypervisor management interfaces like vCenter Server or Microsoft SCVMM to retrieve inventory details such as virtual machines, disks, networks, and hosts. These details are then used by the Zerto User Interface to manage protection. Additionally, ZVM continuously monitors changes in the hypervisor environment and reacts to them as needed.
To help you get started, here’s what you can do next:
To explore what metrics this integration monitors, see Supported Metrics and Default Monitoring Configuration.
To configure and check prerequisites, see Working with Zerto.
Use Cases
Discovery
- Discovers all the high-level components such as Zerto Virtual Manager Local Site, Zerto Virtual Machine, Zerto Volume, Zerto Virtual Protection Group, and Zerto Virtual Replication Appliance.
- Publishes relationships between resources to enable a topological view and simplify maintenance.
- For more information on Heirarchy of Zerto, see Resource Hierarchy
Monitoring
- Provides monitoring related to availability, performance, and usage.
- Generates alerts when defined metric thresholds are breached, notifying users of potential issues.
- For a complete list of supported metrics and details on the default monitoring configurations, see Supported Metrics and Default Monitoring Configuration
Supported Target Versions
- 9.0.41
- 10.0.30
Resource Hierarchy
The following is the resource hierarchy for Zerto integration.
- Zerto Virtual Manager Local Site
- Zerto Virtual Machine
- Zerto Volume
- Zerto Virtual Protection Group
- Zerto Virtual Replication Appliance
Version History
Application Version | Bug fixes / Enhancements |
---|---|
3.0.3 | Support added to Root Resource UUID as a custom attribute along with metric data prescision value changes. |
3.0.2 | Support given to Get Target Response Execute Command Enhancements related to Get Latest Metric Values and Activitylogs |
3.0.1 | Provided fix for VPGs Discovery. |
3.0.0 | Support given to Zerto local site version 10.0.30 Support for native type wise discovery. |
2.0.1 | Metric label support. Missing component alert support. Display Order and Resource Grouping Support. subcategory Updated from Data Protection to Backup and Recovery. |
2.0.0 | Added new metric support on “Zerto Virtual Protection Group” resource "zerto_vpg_Needs_Configuration" "zerto_vpg_Error" "zerto_vpg_EmptyProtectionGroup" "zerto_vpg_DisconnectedFromPeer" "zerto_vpg_RecoveryStorageError" "zerto_vpg_JournalStorageError" "zerto_vpg_ReplicationPaused" Added a new field -“helpIdentifier” in the app configuration for event/alert polling. Changed alert description and summary for the metrics. Added full discovery support. Bulk API enhancements and Handled API exceptions. |
1.0.1 | Bug fix related to zerto events |
1.0.0 | Resource discovery and monitoring implementations. |