# AWS DRS source servers page The **Source servers** page lists all of the source servers that were added to AWS Elastic Disaster Recovery. It allows you to manage your source servers and perform commands for one or more servers, such as controlling replication and launching Initiate recovery job instances. You are likely to interact with AWS Elastic Disaster Recovery predominantly through this page. **Topics** + [Interacting with the Source Servers page](interracting.md) + [Source servers page command menus](command-menus.md) + [Filtering on the source servers page](list-filtering.md) # Interacting with the Source Servers page The **Source servers** page shows a list of source servers. Each row on the list represents a single server. The **Source servers** page provides key information for each source server under each of the columns on the page. The columns include: + **Selector column** – This blank checkbox selector column allows you to select one or more source servers. When you select a server you can interact with it through the **Actions**, **Replication**, and **Initiate recovery job** menus. Selected servers are highlighted. + **Hostname** – This column shows the unique server hostname for each source server. + + **Ready for recovery** – This column shows whether the server is ready for recovery. You can use this column to easily tell whether a server is ready or not and the server's exact status. You can learn more about the server's status by reviewing the **Data replication status** column. + A server that is ready shows the green checkmark and **Ready**. + A server that is ready, but is experiencing a non-critical issue such as lag shows the blue info sign and **Ready** and displays the lag duration to the right. + A server that is still undergoing initial sync shows a gray circle with three dots and **Initial sync**. + A server that is disconnected shows the gray warning sign and **Disconnected**. + A server that is not ready due to a significant error, such as a stall, shows a red **X** and **Not Ready**. Servers that have one or more marketplace licenses assigned to them may not be able to launch if there was an error reading their license information. + **Data replication status** – This column shows the current status of data replication for the server: + **Initiating** – The server has just been added to AWS Elastic Disaster Recovery and replication is being initiated. + **Initial sync** – The server is undergoing the initial sync process. The console displays the percentage of the server data that has been synced and the step the server is undergoing in the initial sync process. You can learn more about the exact state of the server in the server info view. + **Rescanning** – The server is undergoing a rescan. The console displays the percentage of the server data that has been rescanned successfully. + **Healthy** – The server is healthy and is ready to initiate a recovery job. + **Lag** – The server is experiencing lag. The console displays the amount of lag time. You can learn more about the exact state of the server in the server info view. + **Stalled** – The server is stalled due to a replication error. You can learn more about the specific cause of the stall in the server info view. + **Disconnected** – The server has been disconnected from AWS Elastic Disaster Recovery. + **Last recovery result** – This column shows the result of the last recovery job launch. The column is empty if no recovery job has ever been launched for the server: + **Successful** - Recovery launch job was completed successfully. The console indicates how long ago the job was completed. + **Failed** – Recovery launch job failed. The console indicates how long ago the job failed. You can learn more about why the job failed in the job history. + **Pending** – Recovery launch job is pending. The console indicates how long ago the job was initiated. + **Pending actions** – This column shows any pending actions that need to be performed on the server. This column appears empty unless there is an actionable pending action. Actions include: + **Initiate drill** – The source server is healthy, but no drill instances have been launched for the source server. Initiate a drill by launching a drill instance. + **Resolve cause of stall** – The source server is stalled. Resolve the cause of the stall for the server to return to healthy function. + **Reinstall AWS Replication Agent** – The AWS Replication Agent was removed from the source server. Reinstall the agent for replication to resume. + **Error: Missing permissions to retrieve marketplace licenses from the source account, cannot launch this server** – The marketplace license belongs to a different AWS account, permissions to get information about this marketplace license are missing. [Create a Failback and in-AWS right-sizing role for trusted account](adding-trusted-account.md#trusted-accounts-failback-role) using the target account AWS account ID. + **Warning: server uses marketplace product, drill recommended** – This source server uses one or multiple marketplace licenses. Doing a drill is strongly recommended as some marketplace incompatibilities can only be identified during launch. [Learn more here.](marketplace-license-requirements.md) # Source servers page command menus You can perform a variety of actions, control data replication, and manage your drill and recovery instances for one or more source servers through the command menu buttons. Select one or more servers on the **Source servers** page and choose the **Actions**, **Replication**, or **Initiate recovery job** menu to control your source servers. **Topics** + [Actions menu](#server-actions-main) + [Initiate recovery job menu](#server-initiate-recovery-main) + [Replication menu](#server-replication-main) ## Actions menu The **Actions** menu allows you to perform the following actions: + **Add servers** – Choosing this option redirects you to the AWS Replication Agent installation instructions. + **Create extended source servers** – Choose this to start a wizard to create extended source servers from source servers replicating into staging accounts, in multi-account setups. + **Edit DRS launch settings** – Choose this option to edit a single or multiple selected source servers for their DRS launch settings. + **Edit EC2 launch template** – Choose this option to edit a single or multiple selected source servers for their EC2 launch template. + **Edit post-launch action settings** – Choose this option to activate or deactivate post-launch actions for a single or multiple selected source servers. + **View server details** – Choose this option to enter the source server's **Server details view.** + **Disconnect from AWS** – Choose this option to disconnect the selected server from AWS Elastic Disaster Recovery and AWS. When the **Disconnect X server/s from service** dialog appears, click **Disconnect**. **Important** This uninstalls the AWS Replication Agent from the source server and data replication will stop for the source server. This action does not affect any Drill or Recovery instances that have been launched for this source server, but you are no longer able to identify which source servers your Amazon EC2 instances correspond to. + **Delete server** - Choose the **Delete server** option to permanently delete a source server from AWS Elastic Disaster Recovery. This removes all information related to the server from the AWS Elastic Disaster Recovery service. You can only delete servers that have been disconnected from AWS. You need to reinstall the AWS Replication Agent on a deleted source server to add it back to AWS Elastic Disaster Recovery. When the **Delete X servers** dialog appears, click **Permanently delete**. Then, if the servers have associated recovery instances, you can either: + delete them, keeping the EC2 instances intact, + terminate them, which deletes the EC2 instances. ## Initiate recovery job menu The **Initiate recovery job** menu allows you to start drills and recoveries by launching drill and recovery instances as part of the overall failback process. You can learn more about the entire failback and failover process with AWS Elastic Disaster Recovery in the [Performing a failback and failover with AWS Elastic Disaster Recovery documentation](failback.md). + **Initiate drill** – Choose this option to launch a drill instance for this server or group of servers for the purpose of testing your recovery solution. You should perform periodic drills in order to ensure that you are ready for recovery. [ Learn more about launching Drill instances in AWS Elastic Disaster Recovery](preparing-failover.md#recovery-drill-overview). + **Initiate recovery** – Choose this option to launch a Recovery instance for this server or group of servers for the purpose of recovering the server in the event of a disaster. [Learn more about launching Recovery instances in AWS Elastic Disaster Recovery](failback-preparing-failover.md#failback-launching-instances). ## Replication menu The **Replication** menu allows you to perform the following actions: + **Stop replication** – You can stop replication of a source server at any time. After you stop the replication, you will no longer be charged for the ongoing replication and the staging area infrastructure. Changes will not be reported by the agent to the replication server, and all saved snapshots will be deleted, leaving this instance unprotected. The agent remains installed during this process. If you want to replicate this EC2 instance again, simply click the **Start replication** button. This triggers an initial sync. + **Start replication** – You can start replication of a previously stopped source server. After you start the replication, the agent replicates the selected instances. # Filtering on the source servers page You can customize the **Source servers** page through filtering by recovery readiness. In the **Filter source servers....** field, choose the filtering property from the menu. You can filter by a variety of properties, including: + Any recovery readiness – Filter by specific alert (lagging, stalled, launched) + Not ready – Filter by a specific hostname or a specific string of characters + Ready – Filter by the recovery lifecycle state + Initial sync – Filter by the data replication status + Ready with lag + Disconnected