When a problem is identified by Zerto Virtual Replication, an alert is issued.

The following topics are described in this section:

All alerts issued by Zerto Virtual Replication are displayed in the Zerto User Interface. An alert status indicator is displayed in the top left of the display and specific details of all issued alerts are displayed in the ALERTS tab under the top MONITORING tab.

The information displayed in the ALERTS tab includes the VPG name, entity name that triggered the alert, the date and time the alert was issued and a description of the alert.

Warnings are indicated by the orange icon and alerts by the red icon.

You can dismiss alerts by selecting the relevant alerts and clicking the ACKNOWLEDGE button. The number of alerts displayed in the title bar alerts indicator is the number of unacknowledged alerts.

If the description of the alert is truncated, hover over the alert to display a tooltip with the complete description.

Alerts form previous versions are displayed with an Unknown link.

Click EXPORT to save the alerts as a Microsoft Excel worksheet.

The Zerto Virtual Replication alerts are grouped into categories where the first three characters of the alert identifies the category:

AWS – Alerts relating to the recovery site being Amazon Web Services (AWS).

BCK – Alerts relating to offsite backup and VBA issues.

LIC – Alerts relating to licensing issues.

STR – Alerts relating to storage issues.

VCD – Alerts relating to issues with vCloud Director.

VPG – Alerts relating to the VPGs and the virtual machines being protected.

VRA – Alerts relating to VRA issues.

ZCC – Alerts relating to Zerto Cloud Connectors used by cloud service providers.

ZCM – Alerts relating to the Zerto Cloud Manager.

ZVM – Alerts relating to the Zerto Virtual Manager.

The S3 bucket used for the replicated data managed by the VRA in AWS is not found.

The VPG is defined with extended recovery but backups have failed for the last 3 days, including attempted retries.

The VPG is defined with extended recovery but backups have failed for the last 7 days, including attempted retries.

The repository is not accessible by the VBA. If the repository stored backup jobs then an error alert is issued, otherwise, a warning is issued.

The VBA is not accessible. If there are VPGs that are affected, these VPGs are listed.

The VPG is defined with extended recovery but a repository cannot be found to specify for the VPG and therefore backups cannot be performed.

The file level restore component is not available or cannot be found so it is not possible to recover files.

Your license restricts you to protecting a maximum number of virtual machines and you have reached 80% of this number or have exceeded this number.

Your license restricts you to protect virtual machines using a maximum number of CPU sockets and you are close to or have exceeded this number.

Your license is close to its expiration date.

Your license is passed its expiration date and you are protecting more virtual machines than the license permits.

Your license is passed its expiration date and you are using more CPU sockets than the license permits.

Your license is passed its expiration date.

You are protecting more virtual machines than the license permits.

You are using more CPU sockets than the license permits.

Error

The hypervisor manager reports that the specified storage holding either a recovery disk or a journal disk is inaccessible.

The storage has too little free space remaining. Until the issue is resolved further protection of the virtual machines being recovered to this storage cannot continue.

This alert is triggered when the free space falls below 30GB or 15% of the storage, whichever is smaller. Thus, with large storage where 30GB is less than 15%, the alert will be triggered when the amount of free space is less than 30GB of the total size. With small storage where 30GB is more than 15%, the alert will be triggered when the amount of free space is less than 15% of the total size.

Recovery operations can still be performed to the last checkpoint written to the journal, before protection was halted.

The storage is close to its minimum of free space. If the issue is not resolved, protection of the virtual machines being recovered to this storage will stop when the limit is reached.

This alert is triggered when the free space falls below 45GB or 25% of the storage, whichever is smaller.

Recovery operations can still be performed.

Error

Cannot obtain backing vCenter Servers for Org vDC {orgvdc_name}.

The underlying vCenter Server for the Org vDC is not found.

Error

The Org vDC is defined in more than one underlying vCenter Server.

Error

The Org vDC storage profile specified exists in vCD but cannot be found in the underlying vCenter Server.

Cannot find provider vDC storage profile {sp_name} in vCenter. It exists in vCD.

The provider vDC storage profile specified exists in vCD but cannot be found in the underlying vCenter Server.

Error

Cannot extract Org vDC information for Org vDC network {network}, message is {msg}.

The network information required by Zerto Virtual Replication cannot be retrieved.

The exception should give more information. For example, vCD 1.5 doesn't let Zerto Virtual Replication retrieve information on specific types of networks.

A problem occurred with Zerto Virtual Replication accessing the provider vDC metadata it has in the recovery site. The problem should fix itself in a few minutes.

Error

Cannot obtain resource pools for Org vDC {orgvdc_name}, exception is {exception}.

The connection to vCD was dropped, so the required resource pools for the Org vDC could not be retrieved.

Error

Failed to fetch orgNetwork due to exception is {exception}, orgNetwork is {network}.

The network information required by Zerto Virtual Replication cannot be retrieved.

The exception should give more information. For example, vCD 1.5 doesn't let Zerto Virtual Replication retrieve information on specific types of networks.

Access to vCD could not be established.

Error

Connected to vCloud {vcd_id} but failed to connect to AMQP-server for notifications. Last connection error: "{error}".

The connection to the AMQP server in vCD failed, even though the connection to vCD itself succeeded.

Error

Access to the datastore cannot be established for the provider vDC.

Error

Failed extracting metadata for Org vDC {orgvdc_name}. Exception {exception}.

The metadata for the Org vDC in vCD could not be extracted. The Org vDC is ignored.

Error

The same MAC address is used by more than one NIC for the virtual machine.

Number of entities {entity_list} in startup section is different from the number of VMs {vm_name} in vApp {vapp_name}.

The list of virtual machines registered to the vApp does not match the actual virtual machines in the vApp.

Unknown entity {entity_name} in startup section of vApp {vapp_name}.

One of the entities registered to the vApp does not exist.

Warning

VPG {vpg_name} journal history is less than {x}% of the configured {n}. {sync_explanation}

During a synchronization, the latest changes in the protection site are added to the journal and older data in the journal is moved to the mirror virtual disk managed by the VRA for the virtual machine. As the synchronization continues and more old data is moved out of the journal, the checkpoints associated with the data are also removed from the journal and new checkpoints are not added to the journal.

This alert is triggered when the journal history configured for the VPG is at least one hour and the journal contains less than 75% of the configured history.

The message specifies that the amount of history is a percentage less than the configured amount.

This alert will automatically be resolved when the journal history is fully populated.

Error

VPG {vpg_name} journal history is less than {x} of the configured {n}. {sync_explanation}

During a synchronization, the latest changes in the protection site are added to the journal and older data in the journal is moved to the mirror virtual disk managed by the VRA for the virtual machine. As the synchronization continues and more old data is moved out of the journal, the checkpoints associated with the data are also removed from the journal and new checkpoints are not added to the journal.

The message specifies that the amount of history is a large percentage less than the configured amount.

This alert will automatically be resolved when the journal history is fully populated.

An unresolvable error has occurred with VPG {0}. The VPG must be deleted {1}.

The VPG has entered an error state which cannot be fixed.

VPG {vpg_name} is missing configuration details.

Some of the VPG configuration is not valid and has to be updated.

Replication of VPG {vpg_name} has paused to enable creating a clone. It will resume in {n} minutes.

A VPG is being synchronized and if the synchronization continues it will cause all the checkpoints in the journal to be removed. During the synchronization, the latest changes in the protection site are added to the journal and older data in the journal was moved to the mirror virtual disk managed by the VRA for the virtual machine. As the synchronization continues and more old data is moved out of the journal, the checkpoints associated with the data are also removed from the journal and new checkpoints are not added. If the synchronization continues for too long, all the checkpoints can be removed from the journal meaning all recovery operations can no longer be performed.

The message is issued when there are 200 or fewer checkpoints present in the journal and the Replication Pause Time is set in the Advanced Settings dialog. Zerto recommends configuring a replication pause time. The synchronization is paused for the time specified in the Replication Pause Time is set in the Advanced Settings dialog, to enable resolving this situation so that recovery can be performed if necessary.

VPG {vpg_name} rollback failed. Error is {exception}.

During a Failover or Move operation, before committing the recovery the decision was taken to roll back the recovery, either manually or automatically.

VPG {vpg_name} exceeds configured RPO of {n} by more than {m}%.

The IOs are not being replicated fast enough and this is causing the current RPO for the VPG to be between 15% and 25% more than the target RPO specified in the VPG SLA settings.

This alert is triggered when the actual RPO, the time between writing checkpoints to the journal, is more than 15%, but less than 25% more than the target RPO specified for the VPG.

VPG {vpg_name} exceeds configured RPO of {n} by more than {m}%.

The IOs are not being replicated fast enough and this is causing the current RPO for the VPG to be at least 25% more than the target RPO specified in the VPG SLA settings.

This alert is triggered when the actual RPO, the time between writing checkpoints to the journal, is more than 25% of the target RPO specified for the VPG.

VPG {vpg_name} is overdue to be tested. It is configured for testing every {n}.

In order to ensure that the definitions provided for a VPG meet the DR plan, the VPG should be tested every-so-often. The test time specified in the VPG has elapsed and the VPG has still not been tested.

This alert is triggered when the a test has never been performed and it is past the time specified for the testing frequency for the VPG.

VPG {vpg_name} was last successfully tested {n} days ago. It is configured for testing every {m}.

In order to ensure that the definitions provided for a VPG meet the DR plan, the VPG should be tested every-so-often. The testing time is stipulated as part of the VPG definition and this time has elapsed since a test was performed.

This alert is triggered when the last test performed is further in the past than the time specified for the testing frequency for the VPG.

A Failover or Move operation has been performed and the VPG is waiting for the operation to either be committed or rolled back.

{resource_pool} does not have enough resources to support VPG {vpg_name}. Recovery is disabled until this issue is resolved. Details: {details}

The resource pool used for the recovery for the VPG does not have enough resources to recover all the virtual machines in the VPG.

The recovery resource pool has been removed and there is nowhere for the VPG to recover to.

The storage profile that was originally available to the Org vDC is no longer available. Any storage profile that is currently available to the Org vDC does not include the relevant recovery datastores.

Storage profile {sp_name} is disabled in Org vDC {orgvdc_name}, but it serves as the recovery storage profile for VPGs.

The storage profile that was originally available to the Org vDC has been disabled. The VPGs cannot be recovered.

Storage profile with ID {sp_id} is not found in Org vDC {orgvdc_name}, but it serves as the recovery storage profile for VPGs.

The storage profile that was originally available to the Org vDC is no longer available. Any storage profile that is currently available to the Org vDC does not include the relevant recovery datastores. The VPGs cannot be recovered.

Storage profile {sp_name} is not found in Provider vDC {pvdc_name}, but it serves as the recovery storage profile for VPGs.

The storage profile that was originally available to the Provider vDC is no longer available. Any storage profile that is currently available to the Provider vDC does not include the relevant recovery datastores. The VPGs cannot be recovered.

Storage profile {sp_name} is disabled in the Provider vDC {pvdc_name}, but it serves as the recovery storage profile for VPGs.

The storage profile that was originally available to the Provider vDC has been disabled. The VPGs cannot be recovered.

Storage profile {sp_name} of Provider vDC {pvdc} is not found in the underlying vCenter, but it serves as the recovery storage profile for VPGs.

Storage profile {sp_name} of Provider vDC {pvdc} is not found in the underlying SCVMM, but it serves as the recovery storage profile for VPGs.

The storage profile that was originally available to the Provider vDC cannot be found. The VPGs cannot be recovered.

The VPG is replicating to Org vDC {orgvdc_name}, but it cannot be recovered because active recovery datastores have been removed from recovery storage profiles: {sp}

The VPG is replicating to Org vDC {orgvdc_name}, but it cannot be recovered because active recovery storages have been removed from recovery storage profiles: {sp}

The storage profile that is used for recovery no longer includes the datastores that were being used.

The VPG {vpg_name} is protecting the vApp {vapp}. Some vApp networks of this vApp are connected to Org vDC networks for which no mapping is defined. The NICs connected to these vApp networks will be disconnected on failover. Configure network mapping for all networks {networks}.

The VPGs are being recovered in vCD but there is no mapping for the vApp networks. During recovery, the vApps will be created but will not be accessible.

The service profile used to determine the VPG SLA no longer exists. The existing SLA values in the VPG will continue to be used, for example the default journal history and test frequency reminder until you edit the VPG to use a valid service profile.

VPG {vpg_name} includes the following VMs which are no longer protected: {vm_list}.

One or more of the virtual machines in the VPG is no longer being protected. This can occur due to a number of reasons, such as the VRA on the host of a specific virtual machine was removed, or the virtual machine was moved to a different host without a VRA installed.

The network mapping settings for the Org vDC defined in the VPG has become corrupted.

Protected Virtual datacenter {0}, is not part of the ZORG.

Or,

VPG {vpg_name} contains resources that are not assigned to the ZORG {zorg_name}.
resources: {list_of_resources}

The VPG is defined for a specific Zerto Organization, ZORG, but the resources specified for this ZORG in the Zerto Cloud Manager do not include the resources used by the protected virtual machines in the VPG.

VPG {vpg_name} contains resources that are not assigned to the ZORG {zorg_name}.
resources: {list_of_resources}

The VPG is defined for a specific Zerto Organization, ZORG, but the resources specified for this ZORG in the Zerto Cloud Manager do not include the resources assigned for the recovery of the virtual machines in the VPG.

When a virtual machine journal becomes full, Zerto Virtual Replication starts to move data to the recovery disks. Once this begins, the maintained history begins to decrease. If the journal history falls below 75% of the value specified for the Default Journal History parameter, a warning alert is issued in the GUI.

If the journal is not big enough to store all the data for the time specified, as defined in the Journal Size Hard Limit parameter, the time frame for storing data is reduced. When the journal reaches the limit specified in the Journal Size Warning Threshold parameter, an alert is issued.

The amount of time specified for the journal is more than the current amount of time, in minutes.

When a virtual machine journal becomes full, Zerto Virtual Replication starts to move data to the recovery disks. Once this begins, the maintained history begins to decrease. If the journal history falls below one hour, an error is issued, or, if the amount of history defined is only one hour, an error is issued if it is less than 45 minutes.

The RDM {rdm} for the VM {vm_name} in VPG {vpg_name} has an odd number of blocks, which can only be replicated to a target RDM and not to a VMDK.

RDM disks with an odd number of blocks can only replicate to RDM disks of the same size with an odd number of blocks and not to VMDKs.

Hardware version of protected VMs [{vm_names}] are not supported on the recovery site {sitename}.The VPG cannot be recovered.

The hardware version of one or more of the protected virtual machines is not supported by the version of the recovery host on the recovery site. These virtual machines cannot be powered on in the recovery site after a recovery operation.

VPGs {vpg_names} include VMs running Windows 2003 operating system. These VMs drop their domains since guest customization is enabled.

Virtual machines with the Windows Server 2003 operating system being replicated to vCD version 5.5, when guest customization is specified for the VPG, lose the domain setting the virtual machine to be dropped from the domain.

Failover/Move or Failover Test networks do not exist for the following VMs {vm_names}.

The network to use during a recovery operation is not found.

Due to Microsoft default SAN policy, the volumes for the virtual machine in the VPG might become offline upon recovery.

Or:

VM in VPG has several volumes of size 0 : {0}.

One or more of the virtual machines in the VPG has a disk with size 0.

Warning

VPG {vpg_name} journal history is less than {x}% of the configured {n}. {sync_explanation}

During a synchronization, the latest changes in the protection site are added to the journal and older data in the journal is moved to the mirror virtual disk managed by the VRA for the virtual machine. As the synchronization continues and more old data is moved out of the journal, the checkpoints associated with the data are also removed from the journal and new checkpoints are not added to the journal.

This alert is triggered when the journal history configured for the VPG is at least one hour and the journal contains less than 75% of the configured history.

The message specifies that the amount of history is a percentage less than the configured amount.

This warning alert is issued if the alert VPG0003 becomes persistent.

This alert will automatically be resolved when the journal history is fully populated.

Error

VPG {vpg_name} journal history is less than {x} of the configured {n}. {sync_explanation}

During a synchronization, the latest changes in the protection site are added to the journal and older data in the journal is moved to the mirror virtual disk managed by the VRA for the virtual machine. As the synchronization continues and more old data is moved out of the journal, the checkpoints associated with the data are also removed from the journal and new checkpoints are not added to the journal.

The message specifies that the amount of history is a large percentage less than the configured amount.

This error alert is issued if the alert VPG0004 becomes persistent.

This alert will automatically be resolved when the journal history is fully populated.

When a virtual machine journal becomes full, Zerto Virtual Replication starts to move data to the recovery disks. Once this begins, the maintained history begins to decrease. If the journal history falls below 75% of the value specified for the Default Journal History parameter, a warning alert is issued in the GUI.

This warning alert is issued if the alert VPG0037 becomes persistent.

If the journal is not big enough to store all the data for the time specified, as defined in the Journal Size Hard Limit parameter, the time frame for storing data is reduced. When the journal reaches the limit specified in the Journal Size Warning Threshold parameter, an alert is issued.

The amount of time specified for the journal is more than the current amount of time, in minutes.

When a virtual machine journal becomes full, Zerto Virtual Replication starts to move data to the recovery disks. Once this begins, the maintained history begins to decrease. If the journal history falls below one hour, an error is issued, or, if the amount of history defined is only one hour, an error is issued if it is less than 45 minutes.

This error alert is issued if the alert VPG0038 becomes persistent.

Host {host_IP} has no VRA installed, and is part of cluster {cluster_name} that contains hosts with installed VRAs.

The host in the cluster does not have a VRA installed. Any protected virtual machine that is vMotioned to this hosts will cause the VPG to stop protecting all the virtual machine.

You can install a VRA by specifying a static IP address for the VRA virtual machine, which is recommended, or by specifying that the DHCP server should allocate the IP address. The DHCP option was selected when installing the VRA but the DHCP server failed to allocate an IP address to the VRA.

IP of VRA on host {host_ip} changed from {ip1} to {ip2}.

You can install a VRA by specifying a static IP address for the VRA virtual machine, which is recommended, or by specifying that the DHCP server should allocate the IP address. The DHCP option was selected when installing the VRA and the VRA was installed successfully but later on the DHCP server changed the IP address for the VRA.

VRA on host {host_ip} no longer has an IP allocated (original IP was {ip}).

Access to the VRA is not possible via the IP that the Zerto Virtual Manager uses for the VRA.

The local VRA cannot communicate with the peer site VRA to send data for recovery.

Cannot write to journal disk {journal} because datastore is almost full.

The datastore is nearing capacity and has no more room for updates to the journal.

This alert is triggered when the datastore space for the journal falls below 30GB or 15%, whichever is smaller.

The VRA cannot write to the journal.

The recovery disks for the a protected virtual machine managed by the VRA cannot be found. This should never happen.

Recovery disk on virtual machine {vm_name} is missing.

The recovery disk managed by the VRA for the a protected virtual machine cannot be found. This should never happen.

Recovery disks of virtual machine {vm_name} are inaccessible.

After a recovery operation the recovery disks for the recovered virtual machine cannot be accessed because the virtual machine is not powered on.

Recovery disk {disk_name} connected to virtual machine {vm_name} is inaccessible.

After a recovery operation the recovery disks for the recovered virtual machine cannot be accessed.

The datastore for the virtual machines in the recovery site is almost full and no writes can be committed to it for the specified virtual machine.

This alert is triggered when the datastore space for the recovery disk for the specified virtual machine falls below 30GB or 15%, whichever is smaller.

IO error to recovery disk {disk_name} of virtual machine {vm_name}.

There are IO errors generated when writing to the recovered virtual machine recovery disks.

Recovery disks of cloned virtual machine {vm_name} are inaccessible.

The cloned virtual machine is not powered on and the disks for this machine cannot be updated by the VRA.

The disks of the cloned virtual machine are inaccessible.

The disks of the cloned virtual machine are on a datastore that is nearly full, preventing the cloned disks from being updated.

This alert is triggered when the datastore space for the cloned virtual machine falls below 30GB or 15%, whichever is smaller.

IO error to clone disk {disk_name} of virtual machine {vm_name}.

There are IO errors generated when writing to the cloned virtual machine recovery disks.

A protected virtual machine in the VPG was removed.

Protected volume on virtual machine {vm_name} is missing.

A protected virtual machine volume was removed.

A protected virtual machine in the VPG is powered off and synchronization of this virtual machine with the recovery site cannot continue. This affects the whole VPG as the synchronization for the whole VPG is halted.

A virtual machine disk cannot be accessed.

A protected virtual machine has had a disk added that is not supported by Zerto Virtual Replication, resulting in the VPG not being protected.

VRA cannot be registered to host {host_name}. Host component failed to load. {host_component}.

Or: Zerto Virtual Manager cannot reload host component on this ESX version.

A problem is preventing the VRA from being installed on the host.

A VRA or shadow VRA was removed even though it had recovery disks that it was managing, creating a ghost VRA.

VM {vm_name} disk {disk_name} cannot be synced because there are IO errors.

A virtual machine disk cannot be synced because of one of its disks.

A recovery disk attached to a virtual machine in a VPG has been removed.

A journal volume attached to a virtual machine in a VPG has been removed.

An error is issued when a VRA on a host that has protected virtual machines, or that is used to recover virtual machines, is powered off. A warning is issued when a VRA on a host that does not have protected virtual machines, or that is not used to recover virtual machines, is powered off.

VRA on host {host_name} does not have enough resources (hosts 4.x) or reserved memory (hosts 5.x).

On ESX/ESXi 4.x: The VRA does not have enough resources.

On ESXi 5.x: The VRA does not have enough reserved memory.

A previous configuration update of the journal for a specific virtual machine in the VPG failed. You need to update the journal size in the VPG for this virtual machine.

A newer version of the VRAs is available. One or more of the VRAs have not been upgraded to this newer version.

The VRAs in the site are being checked that all are fully synchronized with the protected site.

Local {entity} MAC Address Conflict between {site1} and {site2}.

A VRA or Zerto Cloud Connector has the same MAC address as the specified entity.

Local<-->Remote {entity} MAC Address Conflict between {vm1_name} and {vm2_name} from site {site_name}.

There is a MAC conflict between the entity and VRAs or Zerto Cloud Connectors from different sites.

A journal size hard limit is configured and the size of the journal has reached this limit. Older checkpoints in the journal might be removed to enable adding new checkpoints reducing the history saved in the journal.

A journal size hard limit is configured and the size of the journal has reached this limit. Older checkpoints in the journal might be removed to enable adding new checkpoints reducing the history saved in the journal.

An operation required rolling back failed, for example if the installation of a VRA on the host failed and rolling back to the pre-installation state is performed.

Possible causes include a disconnection between the Zerto Virtual Managers on both sites or between a Zerto Virtual Manager and a VRA.

This alert occurs a rollback of a failed operation on a host (such as installing or upgrading a VRA) fails. This can be either due to an internal bug or due to external factors preventing the rollback (for example, an inability to connect to the hypervisor manager, such as VMware vCenter Server and Microsoft SCVMM, or to a VRA).

Wrong password to host {host_name}.

The password the VRA uses to access the ESXi host has been changed and the VRA can no longer access the host.

Zerto Virtual Manager sees a disk on a VRA that it does not recognize.

GhostUnknownVolume.

Zerto Virtual Manager does not find a system disk on VRA {recovery_VRA_virtual_machine_name} on host {host_name}.

GhostSystemDisk.

The Zerto Cloud Connector for {zcc_name} is powered off.

Possible causes include hypervisor manager, such as VMware vCenter Server and Microsoft SCVMM, problems, disk space issues, network issues, wrong configuration.

A ZCC installation failed. The error for that failure should have more information. This can happen due to many reasons; VC problems, out of disk space, network issues, wrong configuration, etc.

A ZCC installation failed. The error for that failure should have more information. This can happen due to many reasons, such as hypervisor manager, VMware vCenter Server and Microsoft SCVMM, problems, out of disk space, etc.

An orphaned Zerto Cloud Connector for {zcc_name} was installed.

The status of the Zerto Cloud Connector is orphaned, for example when one of the specified networks is invalid or inaccessible or that the ports to access the connector are blocked in the Zerto Virtual Manager.

The Zerto Cloud Manager could not connect to the Zerto Virtual Manager using the specified IP and port.

The connection between site {site1} and the hypervisor manager {hv} at {IP} is down.

Or:

The access key and secret access key to access AWS from site {site1} are no longer valid.

The Zerto Virtual Manager running on the specified site cannot connect to either the hypervisor manager, such as VMware vCenter Server or Microsoft SCVMM, or to Amazon Web Services (AWS).

If the disconnection is on the protected site, the protection of the VPGs is compromised. If the status of the VPG was Protecting before the alert, then the VPG should be recoverable to the last checkpoint that was written to the journal. If the VPG was syncing, excluding a Bitmap Sync, or if a virtual machine was being vMotioned, then the corresponding VPG is not recoverable.

If the disconnection is on the recovery site, the recovery of the VPGs is compromised.

The Zerto Virtual Manager has lost communication with a VRA. This means that no new checkpoints can be written to the journals of any protected virtual machines whose recovery is managed by this VRA.

The connection between the local Zerto Virtual Manager and the remote Zerto Virtual Manager is down.

Possible causes include network problems or the Zerto Virtual Manager is down. This error is also shown briefly while the sites are syncing following a failed operation.

At least one peer site has not been upgraded to version {v1}.

At least one of the peer sites is running a version of Zerto Virtual Replication one version lower than the version running on the local site. Any version of Zerto Virtual Replication will work with another site running the same version of Zerto Virtual Replication or one version higher or lower.

Free space on drive {drive} is below the threshold of {x}GB.

The drive where the Zerto Virtual Manager is installed is too full and some space needs to be freed up.

This alert is triggered when the free space used by the Zerto Virtual Manager falls below 2GB.

A new version ({version}) is available for upgrade.

One of the sites is running a later version.

You can upgrade from version N to the next version (N+1) of Zerto Virtual Replication including to any update within the current version. You cannot do an N+2 upgrade directly.

The order you upgrade the sites, protected or recovery, is not relevant as long as paired sites remain only one version apart.

The following table shows what version you can upgrade to based on the current version running at the site.

A new version ({version}) is available for upgrade, but the current site cannot upgrade to it. Possible causes include you have an old peer which the new version will not be able to communicate with or because you have a VRA running an older version which the new version will not be able to communicate with.

You can only upgrade Zerto Virtual Replication to one version higher with full protection maintained. One of the sites is already running a version one version higher but an upgrade to this is also available.

You can upgrade from version N to the next version (N+1) of Zerto Virtual Replication including to any update within the current version. You cannot do an N+2 upgrade directly.

The order you upgrade the sites, protected or recovery, is not relevant as long as paired sites remain only one version apart.

The following table shows what version you can upgrade to based on the current version running at the site.

The local site could not connect to the remote site because the sites are running different versions of Zerto Virtual Replication. Any version of Zerto Virtual Replication will work with another site running the same version of Zerto Virtual Replication or one version higher or lower.

You can upgrade from version N to the next version (N+1) of Zerto Virtual Replication including to any update within the current version. You cannot do an N+2 upgrade directly.

The order you upgrade the sites, protected or recovery, is not relevant as long as paired sites remain only one version apart.

The following table shows what version you can upgrade to based on the current version running at the site.

The Zerto Virtual Manager has entered an error state.

The local site and peer site Zerto Virtual Managers are being synchronized with each other.

The Zerto Virtual Manager cannot collect metadata describing the host. The virtual machine on this host cannot be protected and protected virtual machines cannot be recovered to this host.

The Zerto Virtual Manager cannot collect SCSI adapter information from the host for the virtual machine in the VPG.

The Zerto Virtual Manager cannot communicate with the host to access the details about the host.

The Zerto Virtual Manager cannot communicate with a shadow VRA.

Host {host_name} is not ready. Failed to create folder at host.

The Zerto Virtual Manager cannot communicate with SCVMM. This alert can be issued in the following cases.