Failback notes
Using the faillback client to perform a failback to the original source server
When using the failback client, you can fail back to the original source server or a different source server using AWS Elastic Disaster Recovery.
Te ensure that the original source server has not been deleted and still exists, check its status in the AWS DRS console. Source servers that have been deleted or no longer exist will show as having Lag and being Stalled.
Note
After failing back to the original source server, you don't need to reinstall the DRS agent to start replication back to AWS.
![Source servers table showing one server with "Ready" and "Stalled" status, pending actions available.](/images/drs/latest/userguide/images/drs-new-failback4.png)
If the original source server is healthy and you decide to fail back to it, it will undergo a rescan until it reaches the Ready status.
You can tell whether you are failing back to the original or a new source servers in the recovery instance details view under Failback status.
Original server:
![Failback dashboard showing status "In progress" for failback to Original server.](/images/drs/latest/userguide/images/drs-new-failback5.png)
New server:
![Failback dashboard showing completed status and last job details for a new server.](/images/drs/latest/userguide/images/drs-new-failback6.png)