Elastic Disaster Recovery - Source server s-347e6a138abfaa463 failed to process
Description: Source server id: s-347e6a138abfaa463 Source OS: Windows 10 Home Replication agent version: Downloaded from: https://docs.aws.amazon.com/drs/latest/userguide/windows-agent.html Region: us-east-1
Issue: EDR console shows "Some source servers could not be processed: s-347e6a138abfaa463" getting this error after the initial replication is completed and when i try to perform the mock drill it is throwing me error: Source server s-347e6a138abfaa463 failed to process
What I’ve already checked:
- Confirmed agent service status
- Network reachability (curl/telnet) to aws-elastic-disaster-recovery.us-east-1.amazonaws.com
- Staging subnet config and igw is attached (attach route table)
Please advise the root cause and remediation steps as this is a Production issue.
- Newest
- Most votes
- Most comments
Based on the information provided, you're experiencing an issue with AWS Elastic Disaster Recovery (DRS) where your source server is failing to process after initial replication, preventing you from performing a mock drill.
The error "Source server failed to process" could be related to several potential issues:
- Network Connectivity Issues: While you've checked basic connectivity, there might be specific connectivity problems between the replication agent on your source server and the replication server in AWS. The error could be a "FAILED_TO_CONNECT_AGENT_TO_REPLICATION_SERVER" issue.
To troubleshoot this:
- Verify that port 1500 is open for communication between your source server and the replication server in the AWS staging area
- Test connectivity specifically to the replication server IP using:
echo | telnet <replication_server_ip> 1500
echo | openssl s_client -connect <replication_server_ip>:1500
- Check if your replication settings are properly configured as Public or Private
- Replication Agent Issues: The agent might be installed but not functioning correctly.
For Windows, verify the AWS Replication Agent service status with:
Get-Service | Where-Object Name -like "*AWSR*"
- Operating System Compatibility: AWS Elastic Disaster Recovery only supports 64-bit operating systems. Verify that your Windows 10 Home is the 64-bit version by:
- Opening Settings (Windows key + I)
- Click System
- Click About
- Check the System type information
If the issue persists, you might need to try reinstalling the agent:
- Uninstall the current agent by copying the folder
C:\Program Files (x86)\AWS Replication Agent\distto a new location - Run
install_agent_windows.exe --removeas administrator from that new location - Reinstall the agent with the latest version
Check the agent logs for more detailed error messages that could help identify the specific issue.
Sources
Why am I receiving a "FAILED TO CONNECT AGENT TO REPLICATION SERVER" error in my AWS MGN or AWS DRS replication initiation steps? | AWS re:Post
Troubleshooting Elastic Disaster Recovery - AWS Elastic Disaster Recovery
Uninstalling the agent - AWS Elastic Disaster Recovery
Why I am not able to perform failback from AWS to on-premise using failback client iso? | AWS re:Post
answered 9 months ago
Initial Replication is already completed agent is also connected getting error while i try to perform the initial recovery drill.