VPG Statuses:
Status | Description |
|---|---|
| Cleaning up Failover Test | After stopping a failover test for the VPG |
| Delta Sync | The Delta Sync uses a checksum comparison to minimize the use of network resources. A Delta Sync is used when the protected virtual machine disks and the recovery disks should already be synchronized, except for a possible few changes to the protected disks, for example, when the target recovery disk is defined as a preseeded disk or after a VRA upgrade, or for reverse protection after a move or failover. |
| Disconnected from Peer | Communication with the Zerto Virtual Manager at the peer, recovery, site is down so continuing protection is halted (compare with Recovery Possible). |
| Disconnected from Peer No Recovery Points | Communication with the Zerto Virtual Manager at the peer, recovery, site is down and there are no checkpoints to use to recover the VPG at the recovery site. |
| Empty Protection Group | A configured VPG where the virtual machines have been removed from it. |
| Error | Problem situation, for example, when a ZVM is disconnected from a VRA used to protect virtual machines. |
| Failing Over | Failing over the VPG. |
| Full Sync | full synchronization to ensure that the protected disks and recovery disks are the same after some change to the system. This type of sync is the same as an initial sync but occurs after protection started. In general, this type of sync should not happen. |
| Initial Sync | Synchronization performed after creating the VPG to ensure that the protected disks and recovery disks are the same. |
| Move: Before Commit | Preparing the VPG virtual machines in the recovery site. |
| Move: Committing | Completing the move, including removing the source virtual machines. |
| Move: Rolling Back | Rolling back a Move operation before committing it. |
| Needs Configuration | One or more configuration settings are missing, for example, when reverse protection is not specified or a virtual machine is added to a vApp. |
| Pending Remove | An attempt to remove the VPG failed and it must be forcibly removed. |
| Promoting | Updating the recovery machines in the VPG with data from the journal. |
| Protecting | Virtual machines in the VPG are protected. |
| Protecting, Bitmap Sync | Synchronization after WAN failure or when the load over the WAN is too great for the WAN to handle. In these situations, 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. The bitmap is small and scales dynamically, containing references to the areas of the source disk that have changed but not the actual I/O. The bitmap is stored locally on the VRA within the available resources. |
| Recovery Possible | Communication with the Zerto Virtual Manager at the protected site is down so continuing protection is halted, but recovery on the peer site is available (compare with Disconnected From Peer). |
| Removing | Deleting the VPG. |
| Replication Paused | Replication paused to enable solving a Journal disk space problem, for example, by increasing the disk size or cloning the VPG. |
| Rolling Back | Rolling back to an initial status, for example, after cancelling a cloning operation on the VPG. |
| Starting Failover Test | Preparing to start a failover test for the VPG. |
| Sync | Status while type of synchronization is being evaluated. |
| Test | Failover test of the VPG. |
| Updating | Changing the VPG definition. |
| Volume Delta Sync | Synchronization when only delta changes for a volume needs synchronizing, for example, when a virtual machine is added to a VPG using a preseeded disk. |
| Volume Full Sync | Synchronization when a full synchronization is required on a single volume. |
| Volume Initial Sync | Synchronization when a full synchronization is required on a single volume, for example, when changing the target datastore or adding a virtual machine to the VPG without using a preseeded disk. |
VPG Synchronization Triggers:
Trigger | Description |
|---|---|
| Force Sync | The user requested to synchronize the VPG, as described in Forcing the Synchronization of a VPG. |
| Network Congestion | The network bandwidth is not wide enough to handle all the data, causing some of the data to be backed up. |
| Protected Storage Error | An I/O error occurred to a protected virtual machine, after the data was sent to the recovery side. |
| Protected VRA Congestion | The host where the VRA is installed is highly loaded: many updates are made to the protected machines at the same time, causing a time lapse before the updates are passed to the recovery site. |
| Recovery or Journal Storage Error | There was an I/O error either to the recovery storage or journal, for example if the journal was full and the size was increased. Once the problem is resolved a synchronization is required. |
| Recovery Storage Congestion | The recovery datastore is being written to a lot, causing a delay for some of the data passed from the protected site to be written to disk. |
| Recovery VRA Communication Problem | A network error, such as the network being down for a period, requires a synchronization of the VPG between the two sites, for example a Bitmap Sync. |
| VPG Configuration Changed | The configuration of the VPG changed resulting in a synchronization being required. For example, the size of the journal was changed. |