Problem: Recovered VMs fail to boot with a Blue Screen in Cross platform Hyper-V to VMware Replication
Error: “Failed to Start Operation. Return code after CreateReadOnlyView was RcError” Received when Retention is in Progress
After Migrating To A New Resource Pool, Operations Such As Failover Test And Rollback Will Fail For “Object Reference Not Set To An Instance Of An Object”
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
Alert: “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 “Progress String Contains Error Code: DOWNLOAD_PART_ERROR. Aborting Importer VM” when Attempting Recovery to AWS
Error: “Instance i-xxxxx did not appear in AWS yet.: did not happen after 00:07:00” when Attempting to Failover to AWS
During a VPG Move Opeation, Error “Failed applying configuration to VM (ID vm-XXXX) Message: The operation is not allowed in the current state”
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: “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
Problem: RE-IP Will Be Executed Upon Failover When The Recovery VM Wants To Keep The Same Static IP As The Source VM’s
Why source VM(s) are deleted after clicking “Done” In the VPG configuration wizard post Failover/Move commit
Problem: For a recovery VM with the OS of Windows Server 2012, not all disks are presented in Disk Management.
FTN-20190918: Patch (V7.0U2P1) – Disks Were Not Removed After Failover Test, Failover and Rollback and Move and Rollback Operations on Microsoft Azure
