Resync is failed at Start Replication on Windows Host. (34091)
Description: For a protected workload; respective target instance copy on AWS could be of NVMe type built on a nitro system. If such target is selected for Windows workload especially for W2k12R2; then you may see replication state being inactive post migration.
Resolution:
Get IP of the migrated instance from AWS Console. Log in to the instance remotely and verify if target instance fall among following list. Instances built on the Nitro System
Check the replication state.
Perform a machine restart. Once machine is up and running; login to instance remotely again. Machine should be configured with respective with Consistency Group. Verify the replication state using following command.vxtapinfo.exe status
Perform Resync on respective resiliency group. This would trigger full synchronization for the workload to maintain data integrity.