Protection Group Failover test failed: ‘XXX’ is invalid or exceeds the maximum number of characters permitted
Error: [vm] failed to be created properly, with reason: VM ‘[vm] – testing recovery’ could not be created Message: Memory (RAM) size (xxxxx) is invalid.. Fault: Vim25Api.GenericVmConfigFault.
ERROR: The LTR process on [VPG NAME] failed. Reason: VRA [VRA name] restart will be initiated to allow proper resource allocation
Error: “Protection group move before commit. Failed: Failed to create VM xxxx’.” Following Move operation to Azure failure
Problem: Linux (CentOS7 / RHEL 7) VM Boots with Dracut Emergency Shell and warnings that specific locations do not exist on the file system after failover
Problem: VM loads with BSOD or displaying the message: “STOP: 0x0000007B” and/or “INACESSIBLE_BOOT_DEVICE”
Problem: VM loads with BSOD or displaying the message: “No operating system found” or “Operating system not found.”
Error: “Conversion task for ImportVM was canceled. Internal error message: ClientError:No bootable partition found”
Error: “Failed to Start Operation. Return code after CreateReadOnlyView was RcError” Received when Retention is in Progress
Error: “Object Reference Not Set To An Instance Of An Object” After Migrating To A New Resource Pool, Operations Such As Failover Test And Rollback Will Fail
How to Ensure Bitmap Sync Instead of Delta Sync For Reverse Replication When Performing a “Move” Operation
Error “Invalid configuration for device” of property VirtualVideoCard.videoRamSizeInKB when attempting Failover tasks to vCenter 7.0
Error: “IO error to recovery disk [{Datastore}] Z-VRA-hostname/xxxxxxxx/vmxxxxx/filename.vmdk of virtual machine Z-VRA-hostname.” might show when starting and/or stopping a failover test
Error: “Instance i-xxxxx did not appear in AWS yet.: did not happen after 00:07:00” when Attempting to Failover to AWS
Error “Protection group [VPG Name] failover before commit failed due to pre script failure” when failover/move action with pre-script used
Problem: During a failover, the recovery VM is not started when the protected VM is in a cluster (MSCS or Always On) with RDM or it has Thick Eager Zero VMDK disks
Error: “Failed to get reflection data for VM” when failing to commit a Failover after VM migration to Azure
Error: “A Specified Parameter was not Correct: spec.memoryAllocation.reservation” when Performing a Failover Test/Failover/Move
Error: “Conversion Task For ImportVM Was Canceled. Internal Error Message: ClientError: Unsupported Windows OS” when Attempting Recovery to AWS
Error “Unable To Access S3 Bucket {aa} Which Is Required For Recovery Operations. Make Sure The Following Recovery Have Access To S3: VPC ID {yy} , Subnet Id {tt} , Security Group Id {ff}” when Recovering to AWS
Error: “Failed to power on Failed setting VM vm-xxx to power state On Message: The host does not have sufficient CPU resources to satisfy the reservation”
Problem: Re-IP is Executed Upon Failover When The Recovery VM Wants To Keep The Same Static IP As The Source VMs
Problem: Source VM(s) are deleted after running the VPG configuration wizard post Failover/Move commit
