# AWS DRS Recovery Instances page Recovery Instances page ## Recovery instances overview You can manage your recovery instances on the **Recovery instances** page. This page displays all of the recovery instances that you launched in AWS for your source servers and those that you added directly to Elastic Disaster Recovery. It allows you to monitor the data replication status of your recovery instances, view recovery instance details, start reversed replication, edit recovery instance failback settings for on-premises failback, view post-launch actions run results, and terminate recovery instances. # Monitoring recovery instances You can monitor your recovery instances on the **Recovery instances** page. It displays all of your recovery instances and sorts them by **Instance ID**, **Reversed direction launch state**, **Data replication status**, **Pending actions**, **Replicating to source server**, **Last launch result**, and **Launched from source server.** You can sort your recovery instances alphabetically in descending or ascending order by choosing the arrow next to the various category headers (with the exception of data replication status). You can filter the recovery instances page by the properties in the **Filter by property of value** box. ## Recovery instance categories Here is a breakdown of each category header: ### Instance ID The **Instance ID** category displays the ID of the recovery instance. Choose an Instance ID to open the recovery instance details view. [Learn more about the recovery instance details view. ](recovery-instances-details.md) ### Reversed direction launch state The **Reversed direction launch state** displays the current state of the reversed direction launch for the recovery instance. Possible states include: + **Not started** – Reversed replication has not been started for the recovery instance. + **Synchronizing** – Reversed replication has been started for the recovery instance and is currently in process. + **Ready** – Reversed replication has completed initiation and is ready to be launched. + **Completed** – Failback process to the on-premises server has been successfully completed. This value does not appear for in-AWS launch flows. + **Error** – There was an error during the reversed replication process. You can learn more about the cause of the error in the **Data replication status** and **Pending actions** columns. ### Data replication status The **Data replication status** category displays the current data replication status of the recovery instance. Possible states include: + **Not started** – Data replication has not started for the recovery instance. This indicates that failback has not started for the instance. + **Initiating** – Data replication is initiating. This indicates that reversed replication has been initiated for the instance. + **Initial sync** – The recovery instance is undergoing the initial sync process after reversed replication has been initiated. The Elastic Disaster Recovery Console displays the percentage completed and the time left. + **Rescanning** – The recovery instance is undergoing a rescan. The AWS Elastic Disaster Recovery Console displays the percentage completed and the time left. + **Healthy** – The data replication process has been completed and the recovery instance is ready for launch. + **Lag** – The recovery instance is currently experiencing lag. Open the recovery instance details view to learn more. + **Stalled** – The recovery instance is experiencing a stall. Open the **Recovery instance details** view to learn more. + **Completed** – The failback process has been completed and as a result data replication has been successfully completed and stopped. This value is only relevant to on-premises failback and does not appear in in-AWS flows. + **Disconnected** – The recovery instance has been disconnected from AWS Elastic Disaster Recovery. As a result, data replication has stopped. ### Pending actions The **Pending actions** column provides additional details, when relevant, about the next actions that should be performed to progress the current flow or to initiate the reversed replication. Possible values include: + **Launch for failback on \$1region\$1** – This status indicates that reversed replication has reached a healthy state. To launch for failback, choose the link under **replicating to source server**. + **Use failback client** – To start the replication back to the on-premises server, use the Failback Client. This value is only relevant to on-premises failback. + **Start reversed replication to \$1region name\$1** – Choose **start reversed replication** to initiate reversed replication to the specified region. This value only applies to in-AWS and cross-region replications. ### Replicating to source server The **Replicating to source server** category identifies the source server to which the recovery instance is replicating. When you start reversed replication it is managed through this source server. Launch operations are performed by navigating to this source server and initiating the operation from that screen. These are displayed in order: + The source server region + The source server's ID Choose the source server links to view the source server details of the source server that is associated with the specific recovery instance. [Learn more about the server details view](server-details.md). If the source server is located in another region (marked by an external icon), choosing the link opens the source server's details page in a different tab. ### Last launch results This category indicated the results of the last launch. Possible values include: + Launch successful + Failback successful + Launch failed + Failback failed ### Launched from source server The **Launched from source server** column identifies the source server from which the recovery instance was launched. These are displayed in order: + The source server hostname + The source server's ID Choose the source server links to view the source server details of the source server that is associated with the specific recovery instance. [Learn more about the server details view](server-details.md). ## Recovery instances actions The recovery instances page allows you to perform actions that include viewing recovery instance details, adding recovery instances, editing the failback replication settings, terminating recovery instances, and continuing the failback process. ### Actions menu Actions available on the **Actions** menu: #### View instance details Select a recovery instance and choose the **View instance details** option under the **Actions ** menu to open the **Recovery instance details** view. [Learn more about the recovery instance details view. ](recovery-instances-details.md) #### Edit failback replication settings Select one or more recovery instances and choose the **Edit failback replication settings** option under the **Actions** menu to edit the failback replication settings the selected recovery instances. The failback replication settings configure the replication to the on-premises servers during an on-premises failback process. This does not apply to in-AWS replication, which is managed on the **replicating to source server** source servers. [Learn more about Failback replication settings.](recovery-instances-details.md#recovery-instances-details-failback-replication-settings) #### Stop failback Select one or more recovery instances that are in the **Synchronizing** state and choose the **Stop**option under the **Actions** menu to stop the failback process for the selected recovery instance or instances. This returns the instances' **Reversed replication launch state** to **Not started ** and stops any ongoing failback process. The Failback client indicates that the failback has been stopped. To restart failback, reboot the machine in the Failback Client. Note that the **Stop failback** state is only relevant to on-premises flows. On the **Stop failback for recovery instances** dialog choose **Stop failback**. #### Terminate recovery instances Select one or more recovery instances and choose the **Terminate recovery instances** option under the **Actions** menu to terminate the recovery instance or instances. This removes all of the resources associated with the selected recovery instance or instances from Elastic Disaster Recovery and terminates all related EC2 resources. Perform this action if you no longer need the recovery instance, for example, if it was for a drill. On the **Terminate recovery instances** dialog choose **Terminate**. #### Disconnect from AWS Select one or more recovery instances and choose the **Disconnect from AWS** option under the **Actions** menu to disconnect the recovery instance or instances from AWS. This deletes the AWS Replication Agent from the recovery instance or instances, but keeps the recovery instance Elastic Disaster Recovery resources and the EC2 resources intact. You may want to disconnect from AWS if you do not want to perform a launch for the specific recovery instance or instances and do not want to accrue additional costs for data replication, but still want the recovery instance to appear in the Elastic Disaster Recovery Console. On the **Disconnect X recovery instances from service** dialog choose **Disconnect**. #### Delete recovery instances Select one or more recovery instances and choose the **Delete recovery instances** option under the **Actions ** menu to delete the recovery instance or instances. This removes all of resources associated with the selected recovery instance or instances from Elastic Disaster Recovery but does not terminate all related EC2 resources and the instance keeps running on Amazon EC2. You may want to delete the recovery instance or instances if you already failed over into AWS, but then decided to permanently keep your workload in AWS instead of failing back to your original source servers and do not want to incur any more costs associated with Elastic Disaster Recovery resources. You may also want to delete the recovery instance or instances if you performed an in-AWS launch but do not want to start reversed replication back to the original region. Note that you can only delete recovery instances that have already been disconnected from AWS. On the **Delete recovery instance** dialog choose **Delete**. **Note** Launch of a new recovery instance from the same source server cleans up all the previous recovery instances, regardless if they have been disconnected and deleted from DRS. ### Failback Select one or more recovery instances that are in the **Ready** state and choose the **Complete failback** option to continue the failback process after performing a failback with the Elastic Disaster Recovery Failback Client. This action stops data replication and starts the conversion process. This finalizes the failback process and creates a replica of each recovery instance on the corresponding source server. **Important** Ensure that you complete the [entire failback process with the Elastic Disaster Recovery Failback Client ](failback-performing.md) prior to choosing the Failback option. On the **Continue with failback for X instances** dialog choose **Failback.** # Recovery instance details view The recovery instance details view provides an overview of the recovery instance, including the instance's reversed direction launch process, post-launch action runs and data replication status. It allows you to control instance tags and the instance's failback settings. You can access the recovery instance details view by choosing the instance ID of a recovery instance under the **Instance ID** column. You can also access the recovery instance details view by selecting a recovery instance and choosing the **View instance details ** option under the **Actions** menu. The recovery instance information page displays the **Instance ID** at the top. The **Overview** panel provides an overview of the failback process, including: + **EC2 instance** – the ID of the recovery instance in EC2. Choose **View in EC2** to open the AWS EC2 Console. + **Pending actions** – information derived from the **Pending actions** column (for example, **Launch for failback on \$1region\$1**). + **Replicating to source server** – the source server to which the recovery instance is replicating. Choose the source server ID to open the **Source server details view** page for the specific source server. + **Launched from source server** – the source server from which the recovery instance was launched. Choose the source server ID to open the **Source server details view** page for the specific source server. + **Post-launch actions status** – displays the status of the last post-launch actions run on this instance. The recovery instance details page is divided into these sections: + **Launch dashboard** - see the current status of failback or reversed direction replication and launch. + **Instance information** - view information about the underlying EC2 instance. + **Tags** - manage the tags of the recovery instance. + **Failback replication settings** - configure settings for failback to on-premises servers. Not relevant for in-AWS launches. + **Post-launch actions status** - the progress or result of the last post-launch actions run. ## Launch dashboard The **Launch** dashboard provides a detailed overview of the reversed direction launch process. ### Reversed direction launch state The **Reversed direction launch state** panel provides an overview of the reversed direction launch process, including: + The current state of the failback. + **Launch target** – the server into which the recovery instance is launching. This indicates whether the recovery instance is launching into the original server or to a new server. Note that for in-AWS flows this value is always a new server, unless your are using the ** Launch into existing instance** capability. + **Last job ID** – the ID of the last failback job started for the recovery instance. + **Last job started** – the date and time the last failback job was started for the recovery instance. + **Last job finished** – the date and time the last failback job was finished for the recovery instance. + **Last launch results** – the results of the most recent launch. ### Data replication status The Data replication status panel displays the current data replication status state for the recovery instance, including: + **Replication progress** – the progress of the replication of the recovery instance in percent completed. + **Total replicated storage** – the total amount of storage replicated in GiB. + **Lag** – the total Lag time, if any. + **Backlog** – the total backlog amount and time to clear, if any. + **Elapsed replication time** – time elapsed since replication began. + **AWS replication agent last seen** – the date and time connectivity was last established between the recovery instance and the AWS Replication Agent. + **Failback client last seen** – the date and time connectivity was last established between the recovery instance and the Failback client. + **Replication start time** – and date and time replication was started for the recovery instance. ### Events and metrics The Events and metrics section contains external links to monitor your recovery instance in AWS CloudTrail. [Learn more about monitoring DRS with CloudTrail](https://docs.aws.amazon.com/drs/latest/userguide/logging-using-cloudtrail.html#logging-using-cloudtrail-). ## Instance information The **Instance information** tab displays general server information, hardware, and network information: + **Last updated** + **AWS recovery instance ID** + **Created in recovery job** + **Hostname** + **Fully qualified domain name** + **CPUs** + **Disks** + **Primary network interface** + **Operating system** information ## Tags The Tags section displays tags that have been assigned to the server. A tag is a label that you assign to an AWS resource. Each tag consists of a key and an optional value. You can use tags to search and filter your resources or track your AWS costs. Learn more about AWS tags in [Tag your Amazon EC2 resources](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html). Choose **Manage tags** to add or remove tags. On the **Manage tags** page choose **Add new tag ** to add a new tag. Add a tag **Key** and an optional tag **Value**. **Save** your added tags. To remove a tag, choose **Remove** to the right of the tag you want to remove, and then choose **Save**. ## Failback replication settings The Failback replication settings tab allows you to edit various failback replication settings for the recovery instance prior to performing a failback. Choose **Edit** to edit the settings. You can configure the failback replication settings for multiple recovery instances at once. The **Selected recovery instances** box displays the recovery instances for which you are updating the settings. ### Network bandwidth throttling You can control the amount of network bandwidth used for data replication per server. By default, Elastic Disaster Recovery uses all available network bandwidth on five concurrent connections. Choose **Throttle bandwidth** if you want to control the transfer rate over TCP Port 1500 of data sent from your recovery instances to your source servers during failback. On the the **Throttle network bandwidth (per instance, in Mbps)** enter the bandwidth in Mbps. Otherwise, choose **Do not throttle bandwidth**. ### Use private IP By default, data is sent from the recovery instance to the source servers over the public internet, using the public IP that was automatically assigned to the replication servers. Transferred data is always encrypted in transit. Choose the **Use private IP** option if you want to route the replicated data from your recovery instance to your source servers through a private network with a VPN, AWS Direct Connect, VPC peering, or another type of existing private connection. Use this option if you want to: + Allocate a dedicated bandwidth for replication + Use another level of encryption + Add another layer of security by transferring the replicated data from one private IP address (source) to another private IP address (on AWS) **Important** Data replication does not work unless you have already set up the VPN, AWS Direct Connect, or VPC peering in the AWS Console. **Note** If you selected the default subnet, it is highly unlikely that the private IP is activated for that subnet. Ensure that Private IP (VPN, AWS Direct Connect, or VPC peering) is activated for your chosen subnet to use this option. Choosing the **Use Private IP** option does not create a new private connection. ### Saving failback replication settings Once you have configured your failback replication settings, choose **Save failback replication settings. ** ## Post-launch actions status The **Post-launch actions** view displays the current run status of post-launch actions. The status includes: + **Order** - the running order of the action. + **Name** - the name of the action is a link to the detailed run status in the AWS Systems Manager console. + **Run result** – provides the current action run status. + **Start time** – the time when the action script started to run. This column is empty for actions that have not yet started running. + **End time** – the time when the action script run ended. This column is empty for actions that have not yet completed running. + **Details** – error messages are displayed in this column. + **Link** – provides a link to resources created by this action if there are any, or to the action run logs in the AWS Systems Manager console.