Error: “Parameter BootGroupIdentifier is irrelevant in the current configuration and must be removed” when attempting to remove VMs from a VPG
Error: “The Number Of Cores For The Protected VM Is Higher Than The Max Number Of Cores Supported By The Selected Instance Size” when Creating a VPG to Azure
Error: “Failed to relocate VM [vm-xxx] volume to [datastore][vmdk_location]” when Updating VPG to Migrate Journal/Recovery Disks Between Datastores
Error: “Datastores only support Thin Provisioning” when Create / Import / Change Recovery Host is Attempted for Any VPG
Error: “Current step is not valid – IP address [X] not in valid for organization network (Gateway [X] Netmask [X])” During Create/Edit VPG in NICs Tab
Error “target device does not exist: host = [Cluster:xx…” When Attempting to Create/Edit a VPG with RDM Disks
Error: “The Target site doesn’t have permissions to replicate into the source Datastore (datastore_name)” when Creating a VPG
Error: “No valid storage can be found for storage cluster [cluster]” when Creating a VPG and Selecting a Datastore Cluster
Problem with Create VPG Completing and Immediately Creating an Additional VPG, the Wizard Starts Over and the Same VM(s) can be Selected for Protection Again
Problem with After an Azure ZCA’s VRA Service Restarts, All VPGs will not Start Necessary Sync and thus do not Replicate
Problem with Updating a VPG to Change the Journal Datastore Does Not Change the Datastore, With No Error Presented to the User
Problem with Recovery Volume Size (X Bytes) Doesn’t Match Protected Volume Size (X Bytes) For VM Protected By VPG
Error: ‘Failed applying configuration to VM (VM-xxx) Message: A general system error occurred: PBM error occurred during PreProcessReconfigureSpec: pbm.fault.PBM Fault’ When Performing Change Datastore
Error: ‘IO error to recovery disk {disk_name} of virtual machine {vm_name}’ After Resizing RDM on Protected VM
Error: “Zerto Settings Contain VM Which Is Not Accessible (vm-xxxx)” after migration of VM from on-prem to a Cloud site
Error “The Org VDC does not support the hardware version of the following virtual machines: [VM: example_servername Version: vmx-XX]. Highest supported version: vmx-YY”
Problem with Change VM Recovery Host resulting with Error “This is not allowed when you change a datastore.”
Alert “VPGs {vpg_names} include VMs running Windows 2003 operating system. These VMs drop their domains since guest customization is enabled” appears when a VPG protects Linux VMs
Error: “The {journal} journal for VM {vm_name} in VPG {vpg_name} has reached its configured limit of {x}. Older checkpoints might be removed and the journal history might be reduced to make space for new data.”
