VPG Statuses

Substatus	Description
Bitmap Syncing	In Azure, standard replication is achieved by a blob level mechanism which tracks changes in the data volumes of protected virtual machines. When the VRA at the Azure site detects a list of changed blocks, a bitmap that is saved persistently in the Azure block blob storage is updated. The bitmap contains references to the areas of the protected disk that have changed but not the actual I/Os.The bitmap is small and scales dynamically in correlation to the size of the changed data.
Committing Failover	Failing over the VPG.
Committing Move	Completing the move, including removing the protected virtual machines.
Creating VPG	The VPG is being created based on the saved definition.
Deleting the VPG	Deleting the VPG.
Delta Syncing	The Delta Sync uses a checksum comparison to minimize the use of network instances. 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: ■ After a VRA on the protected site was upgrade. ■ A Force Sync operation was manually initiated on the VPG. ■ A host protecting virtual machines was restarted and the protected virtual machines on the host had not been moved to other hosts in the cluster or a protected virtual machine was moved to another host without a VRA, and then moved back to the original host. For synchronization to work, the protected virtual machines must be powered on so that the VRA has an active IO stack, which is only available when the virtual machine is powered on. During the synchronization, new checkpoints are not added to the journal but recovery operations are still possible, assuming there are valid checkpoints in the journal. If a disaster occurs requiring a failover during a delta synchronization, you can recover to the last checkpoint written to the journal. Note: Synchronization after a recovery starts after the promotion of data from the journal to the virtual machine disks ends. Thus, synchronization of virtual machines can start at different times, dependent on when the promotion for the virtual machine ends. All synchronizations are done in parallel, whether a delta sync or full sync, etc.
Delta syncing a disk	Synchronization when only delta changes for a disk needs synchronizing. For synchronization to work, the protected virtual machines must be powered on so that the VRA has an active IO stack, which is only available when the virtual machine is powered on. During the synchronization, new checkpoints are not added to the journal but recovery operations are still possible, assuming there are valid checkpoints in the journal. If a disaster occurs requiring a failover during a delta disk synchronization, you can recover to the last checkpoint written to the journal. Note: Synchronization after a recovery starts after the promotion of data from the journal to the virtual machine disks ends. Thus, synchronization of virtual machines can start at different times, dependent on when the promotion for the virtual machine ends. All synchronizations are done in parallel, whether a delta sync or full sync, etc.
Error	Problem situation, for example, when a ZVM is disconnected from a VRA used to protect virtual machines. The VPG cannot be recovered until the problem is resolved,
Failing over - Before commit	Preparing and checking the VPG virtual machines in the recovery site.
Full Syncing	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. For synchronization to work, the protected virtual machines must be powered on so that the VRA has an active IO stack, which is only available when the virtual machine is powered on. During the synchronization, new checkpoints are not added to the journal. Also, recovery operations are not possible. Note: Synchronization after a recovery starts after the promotion of data from the journal to the virtual machine disks ends. Thus, synchronization of virtual machines can start at different times, dependent on when the promotion for the virtual machine ends. All synchronizations are done in parallel, whether a delta sync or full sync, etc.
Full syncing a disk	Synchronization when a full synchronization is required on a single disk. For synchronization to work, the protected virtual machines must be powered on so that the VRA has an active IO stack, which is only available when the virtual machine is powered on. During the synchronization, new checkpoints are not added to the journal. Also, recovery operations are not possible. Note: Synchronization after a recovery starts after the promotion of data from the journal to the virtual machine disks ends. Thus, synchronization of virtual machines can start at different times, dependent on when the promotion for the virtual machine ends. All synchronizations are done in parallel, whether a delta sync or full sync, etc.
Initial Sync	Synchronization performed after creating the VPG to ensure that the protected disks and recovery disks are the same. Recovery operations cannot occur until after the initial synchronization has completed. For synchronization to work, the protected virtual machines must be powered on so that the VRA has an active IO stack, which is only available when the virtual machine is powered on. Adding a virtual machine to a VPG is equivalent to creating a new VPG and an initial synchronization is performed. In this case, any checkpoints in the journal become unusable and only new checkpoints added after the initial synchronization completes can be used in a recovery. The data in the journal however remains and is promoted to the recovered virtual machine as part of a recovery procedure. Note: Synchronization after a recovery starts after the promotion of data from the journal to the virtual machine disks ends. Thus, synchronization of virtual machines can start at different times, dependent on when the promotion for the virtual machine ends. All synchronizations are done in parallel, whether a delta sync or full sync, etc.
Journal storage error	There was an I/O error to the journal. For example, if the journal was full and the size was increased. Once the problem is resolved a synchronization is required.
Moving - Before commit	Preparing and checking the VPG virtual machines in the recovery site.
Needs Configuration	One or more configuration settings are missing.
Promoting	Updating recovered virtual machines in the VPG with data from the journal.
Recovery is possible	Communication with the Zerto Virtual Manager at the protected site is down so continuing protection is halted, but recovery on the remote site is available.
Recovery storage error	There was an I/O error to the recovery storage. For example, the storage is almost full or the virtual machines are turned off and the recovery disks are inaccessible.
Recovery storage profile error	The storage profile in the recovery site specified to be used by the VPG cannot be found.
Rolling back	Rolling back to an initial status, for example, after canceling a cloning operation on the VPG.
Rolling back Failover	Rolling back a Failover operation before committing it.
Rolling back Move	Rolling back a Move operation before committing it.
Site disconnection	Communication with the Zerto Virtual Manager at the remote, recovery, site is down so continuing protection is halted.
Site disconnection. No checkpoints	Communication with the Zerto Virtual Manager at the remote, recovery, site is down and there are no checkpoints to use to recover the VPG at the recovery site.
Syncing	Status while type of synchronization is being evaluated.
User paused protection	Protection is paused to enable solving a Journal disk space problem, for example, by increasing the disk size or cloning the VPG.
Disk Initial Sync	Synchronization when a full synchronization is required on a single disk, for example, when changing the target storage or adding a virtual machine to the VPG. For synchronization to work, the protected virtual machines must be powered on so that the VRA has an active IO stack, which is only available when the virtual machine is powered on. During synchronization, new checkpoints are not added to the journal. Also, recovery operations are not possible during a disk Initial Sync. Note: Synchronization after a recovery starts after the promotion of data from the journal to the virtual machine disks ends. Thus, synchronization of virtual machines can start at different times, dependent on when the promotion for the virtual machine ends. All synchronizations are done in parallel, whether a delta sync or full sync, etc.
VPG has no VMs	A configured VPG where the virtual machines have been removed from it, for example when changing both the storage and host for the virtual machines in the VPG, causes the VPG to be recreated.
VPG waiting to be removed	An attempt to remove the VPG failed and it must be forcibly removed. For details, see Deleting a VPG When the Status is Deleting.
Zerto Virtual Manager paused protection	Protection is paused to enable solving a Journal disk space problem, for example, by increasing the disk size or cloning the VPG.

Status	Substatus	Comment
Deleting	Deleting the VPG
Deleting	VPG waiting to be removed
Failing Over	Committing Failover	The VPG is being failed over.
	Failing over – Before commit	A VPG being failed over is in the initial stage, before committing the failover.
	Rolling back Failover	The failover is being rolled back to prior to the failover.
History Not Meeting SLA	See Not Meeting SLA, below.	The VPG is meeting the RPO SLA setting.
Initializing	Creating VPG
	Initial Sync
	Syncing
	disk Initial Sync
Meeting SLA or Based on Alerts	Bitmap Syncing
	Delta Syncing (When Force Sync is applied)
	Recovery is Possible	After a rollback.
Moving	Committing Move
	Moving – Before commit
	Promoting
	Rolling back Move
Not Meeting SLA	Delta Sync (When Force Sync is not applied)	This status means that the VPG is not meeting the journal history nor RPO SLA settings.
	Delta Syncing a disk
	Error
	Needs configuration
	Site disconnection
	Site disconnection. No checkpoints
	VM not protected
	VPG has no VMs
Recovered	—	The VPG has been recovered.
RPO Not Meeting SLA	See Not Meeting SLA, above.	The VPG is meeting the journal history SLA setting.