- Newest
- Most votes
- Most comments
You can refer to the following article https://docs.aws.amazon.com/drs/latest/userguide/common-replication-errors.html
Ensure the source machine has access to AWS DRS and that the replication agent is running. For Linux, use the systemctl status command to check the agent's status. Additionally, confirm connectivity to the AWS DRS endpoint on TCP Port 443
If facing a 'Not Converging' error, it could suggest inadequate replication speed. Verify network bandwidth and assess the performance of replicator EBS volumes. Modify EBS volume types if necessary from the AWS DRS console under the Disk settings tab for the source server
For errors like 'Failback Client Not Seen' or 'Failed to Download Replication Software to Failback Client', check network connectivity, including access to the AWS S3 endpoint. Network security appliances or proxies might block software downloads
Snapshot failures might be due to insufficient IAM permissions or API throttling. Ensure appropriate IAM roles and permissions are set and check CloudTrail logs for throttling errors
If there are issues in creating firewall rules or in authentication with the service, ensure that the IAM permissions are correctly set up and that the necessary ports (like TCP Port 443) are open on your replication server
After Failover of source server, Ec2 created from failover has not internet access because of 0 indexed network card interface card, so I attached new interface card at 1 index with ec2. but issue remains same.
Relevant content
- Accepted Answerasked 2 years ago
- asked 2 years ago
- Accepted Answerasked 9 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Could you explain more about the vpc setup?