AWS DRS "Last recovery result" accuracy

The discrepancy you're experiencing with the AWS Disaster Recovery Service (DRS) "Last Recovery Result" display is a known issue.

Here's what we know about the accuracy of the "Last Recovery Result":

• Inconsistent Reporting: The console sometimes displays inaccurate information, particularly in the Source Servers section, where it might show all servers as "Failed" even when some have successfully recovered.

• Job Details vs. Overview: As you've noticed, the detailed job description often provides more accurate information than the overview in the Source Servers section. In your case, seeing 5/9 successful in the job details is likely more accurate than the blanket "Failed" status.

• Delayed Updates: There can be a lag between the actual recovery status and what's displayed in the console. Sometimes, refreshing the page or waiting for a few minutes can update the status more accurately.

• Individual Server Status: Checking the status of each server individually often provides more reliable information than the overview.

• CloudWatch Metrics: For more accurate data, some users rely on CloudWatch metrics associated with their DRS jobs, as these tend to be more up-to-date and precise.

• AWS Support: If this inconsistency is critical for your operations, it's recommended to open a support ticket with AWS. They can provide the most current information on this issue and any potential workarounds or upcoming fixes.

To get the most accurate picture of your recovery results, it's best to:

1. Check individual server statuses
2. Review the detailed job description
3. Verify EC2 instances in the target region
4. Use CloudWatch metrics if available
5. Allow some time for console updates