NEW - You can now accelerate your migration and modernization with AWS Transform. Read [Getting Started](https://docs.aws.amazon.com/transform/latest/userguide/getting-started.html) in the *AWS Transform User Guide*. # Manage source servers The **Source servers** page lists all of the source servers that have been added to AWS Application Migration Service (AWS MGN). The **Source servers** page allows you to manage your source servers and perform a variety of commands for one or more servers (such as controlling replication and launching test and cutover instances). The **Source servers** page is the main page of AWS MGN console and you will most likely interact with AWS Application Migration Service predominantly through this page. ## 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 table displays **Active source servers** by default. You can use the dropdown menu above the first row to choose to display: + **Agentless discovered servers** - servers discovered by the agentless replication process, which are not yet replicating. + **Imported servers** - servers whose information was imported into MGN, but an agent is not yet installed on them. + **Archived source servers** - servers whose migration has completed, and the users archived their data. 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 a server is selected, you can interact with the server through the **Actions**, **Replication**, and **Test and cutover** menus. Selected servers are highlighted. + **Source server name** – This column shows the unique server name for each source server. + **Alerts** – This column shows whether any alerts exist for the server. + **No indication** – a healthy server for which a test or cutover instance has not been launched. + **Launched** – a healthy server for which a test of cutover instance has been launched. + **A clock icon with a warning message** – a server that is experiencing a temporary issue such as lag or backlog + **A red x and message** – a server that is experiencing significant issues, such as a stall. + **Replication type** – This column identifies whether the server is being replicated through the default **Agent based** replication or through **Snapshot shipping**. [Learn more about agentless based snapshot shipping replication for vCenter.](agentless-mgn.md) + **Migration lifecycle** – This column shows the migration lifecycle state for each source server. This way you can easily know which lifecycle step the server is undergoing. Migration lifecycle steps include these: [[Learn more about Migration lifecycle steps](migration-dashboard.md#lifecycle)](migration-dashboard.md#initiation). + **Not ready** + **Ready for testing** + **Test in progress** + **Ready for cutover** + **Cutover in progress** + **Cutover complete** + **Disconnected** + **Data replication status** – This column shows the current status of data replication for the server. The information presented in this column changes based on the server's Migration lifecycle state and whether the server is experiencing any issues. This column shows a variety of information, including: + **Not Started** – Data replication has not started. + **Paused** – Data replication has been paused. + **Healthy** – The server is healthy and ready for Test or Cutover instance launch. + **Done** – The server has been successfully cutover and data replication has been stopped as a result. + **Percentage complete** – The percentage of the server's storage that was successfully replicated if the server is undergoing initial sync or a rescan. + **Lag** – Whether server is experiencing any lag. If it is; the lag time is indicated. + **Backlog** – Whether there is any backlog on the server (in MiB). + **Last snapshot** – This column shows the time the last consistent snapshot was taken of the source server. Servers that are still in the initial sync process and those that have been disconnected do not show any info in this field. Healthy servers shows a recent snapshot. Unhealthy servers' last snapshot indicates the last time they were healthy. + **Next step** – This column shows the next step that needs to be undertaken in order to successfully complete a cutover for the server. The information presented in this column changes based on the server's Migration lifecycle state and whether the server is experiencing any issues. This column shows a variety of next steps, including: + **Wait for initial sync to complete** – Data replication is initiating for the server. Wait for the initial sync process to complete. + **Start data replication** – Data replication has not been started or is paused. + **Launch test instance** – The server is ready to launch a test instance. + **Complete testing and mark as 'ready for cutover'** – The server has launched a Test instance that needs to be reverted or finalized. + **Launch cutover instance** – The server had a Test instance launched and finalized and now is ready to launch a cutover instance. + **Finalize cutover** – The server has launched a cutover instance that needs to be finalized. + **Terminate launched instance, Launch cutover instance** – The server is ready for cutover. Terminate the launched Test instance and launch a cutover instance. + **Resolve cause of stalled data replication** – The server is experiencing significant issues such as a stall that need to be addressed. + **Wait for lag to disappear, then X.** – The server is experiencing a temporary lag. Wait for the lag to disappear and then perform the indicated action. + **Mark as archived** – The server has been successfully cut over and can now be archived. **Topics** + [ ## Interacting with the source servers page ](#interracting) + [ # Add a source server ](add-server-server-page.md) + [ # Manage data replication ](server-replication-main.md) + [ # Manage test and cutover instances ](server-test-cutover-main.md) + [ # Source server migration metrics ](source-server-migration-metrics.md) + [ # Filtering the source servers list ](list-filtering.md) # Add a source server To add a server, simply click **Add server**. To run a variety of commands on your source servers, select one or more servers and choose the **Actions**, **Replication**, or **Test and cutover** menu. The **Add servers** prompt opens, allowing you to create a custom installation command by taking these steps: + 1. Select your operating system. The installation command is different for Windows and Linux **Note** If you want to install the AWS Replication Agent on a legacy Windows OS (Windows Server 2003, Windows Server 2008 or Windows Server 2008 R2), you must choose the **Legacy OS: Windows Server 2003 or Windows Server 2008** box. This downloads a unique version of the AWS Replication Agent installer that is only valid for legacy Windows OSs (`AwsReplicationWindowsLegacyInstaller.exe`). **Do not** use this installer file to install the agent on any other OS types. 1. Select your replication preferences for the source server. The selected preferences are added as installation prompts to the custom installation command that is generated by this form. Choose the **Replicate all disks** option to replicate all of the disks of the source server. This is the default option. This option adds the `--no-prompt` prompt to the installation command. Select the **Choose which disks to replicate** option to choose which specific disks you want to replicate. You are prompted to select which disks to replicate during agent installation. 1. Enter the credentials [you previously generated for AWS Replication Agent installation](credentials.md). The form does not send the secret, but does add it to the installation command. 1. If you are adding a Windows source server to AWS MGN, download the installer onto the source server. The installer is downloaded from the AWS Region of your account. If you're adding a Linux source server, skip this step. 1. Copy the generated custom installation command and either input it into the command line on your source server. Proceed with [AWS Replication Agent installation as instructed in the documentation](agent-installation.md). To run a variety of commands on your source servers, select one or more servers and choose the **Actions**, **Replication**, or **Test and cutover** menu. ## Actions menu The **Actions** menu allows you to perform these actions: + **View server details** – Choose this option to see the server details view for the selected server. This option is only available when a single server is selected. + **Add server to application** – Choose this option to easily add servers to an application. + **Disconnect from service** – Choose this option to disconnect the selected server from Application Migration Service and AWS. This option should be used when data replication is complete. On the **Disconnect X server/s from service** dialog, choose **Disconnect**. **Important** This uninstalls the AWS Replication Agent from the source server and data replication stops for the source server. If you need to restart data replication for this server, you need to reinstall the agent. This action does not affect any test or cutover instances that have been launched for this source server, but you can no longer identify which source servers your Amazon EC2 instances correspond to. + **Mark as archived** – Choose this option in order to archive the server. You should only archive servers for which you have already performed a cutover. Archived servers are removed from the main **Source servers** page, but can still be accessed through filtering options. On the **Archive X servers** dialog, select **Archive**. To see your archived servers, open the **Preferences** menu by choosing the gear button. Select the **Show only archived servers** option and click **Confirm**. You are now able to see all of your archived servers. Unselect this option to see your non-archived servers. # Manage data replication You can manage data replication for the source server through these actions on the **Replication** drop-down menu: + **Start data replication** – Restarts data replication for a source server on which data replication has been stopped. If you are using agent-based replication you don't necessarily have to reinstall the agent. + **Stop data replication** – Stops data replication for a source server. Stopping the replication stops billing, deletes existing snapshots and EBS volumes, and terminates replication servers. Configuration is retained, and if you are using agent-based replication the agent is not uninstalled. + **Pause data replication** – Pauses data replication for a source server. Pausing the replication does not stop billing or delete existing snapshots or EBS volumes. Replication servers are not terminated and if you are using agent-based replication the agent is not uninstalled from the source server. + **Resume data replication** – Resume data replication for a paused source server. This syncs any changes since the last synchronization and completes the data replication flow. Choose **Edit** in the **Replication settings **section to access the ** Edit Replication Settings** page, where you can edit the settings for the selected source server. [Learn more about editing replication settings.](replication-settings-template.md) # Manage test and cutover instances The **Test and cutover** menu allows you to manage your test and cutover instances. For a more in-depth step-by-step guide to launching test and cutover instances, see the [Launching test and cutover instances documentation](launching-test-servers.md). + **Launch test instances** – Choose this option to launch a test instance for this server. When the **Launch test instances for X** servers dialog appears, cick **Launch** to begin the test. The AWS Application Migration Service console indicates **1 launch job complete** after the test has been completed successfully. + **Mark as "Ready for cutover"** – Use this option to finalize testing for this server after you have completed all of the necessary tests in preparation for cutover. When the **Mark X servers as "Ready for cutover"** dialog appears, select whether you want to terminate the launched instances used for testing. We recommend that you terminate these instances, as you will be charged for them even though you no longer need them. Check the **Yes, terminate launched instances (recommended)** box and choose **Continue**. The AWS Application Migration Service console indicates that testing has been finalized. The selected source servers' **Migration lifecycle** column shows the **Ready for cutover** status and the launched Test instances are deleted if that option was selected. + **Revert to "ready for testing"** – Choose this option to revert a finalized test for this server if you want to run further tests prior to initiating a cutover. The **Revert testing for X servers** dialog appears. Select whether you want to terminate the launched instances used for testing. We recommend that you terminate these instances, as you will be charged for them even though you no longer need them. Check the **Yes, terminate launched instances (recommended)** box and choose **Revert**. The AWS Application Migration Service console indicates that testing has been reverted. The selected source servers' **Migration lifecycle** column shows the **Ready for testing** status and the launched Test instances are deleted if that option was selected. + **Launch cutover instances** – Choose this option to launch a cutover instance for this server after you have finalized all of your testing and are ready to initiate a cutover. The **Launch cutover instances for X** **servers** dialog appears. Choose **Launch** to begin the cutover. The AWS Application Migration Service console indicates **1 launch job complete** after the cutover has been completed successfully. This changes your source servers' **Migration lifecycle** status to **Cutover in progress**, indicating that the cutover is in progress but has not yet been finalized. + **Finalize cutover** – Choose this option to finalize the cutover for this server after you have successfully performed a cutover. This changes your source servers' **Migration lifecycle** status to **Cutover complete**, indicating that the cutover is complete and that the migration has been performed successfully. In addition, this stops data replication and cause all replicated data to be discarded. All AWS resources used for data replication are terminated. The **Finalize cutover for X servers** dialog appears. Choose **Finalize**. The AWS Application Migration Service console indicates **X servers cutover. Data replication has been stopped for servers** once the cutover has been completed successfully. The AWS Application Migration Service console automatically stops data replication for the cutover source servers to save resource costs. The selected source servers' **Migration lifecycle** column shows the **Cutover** status, the **Data replication** column shows **Disconnected** and the **Next step** column states **Mark as archived**. The source servers have now been successfully migrated into AWS and can be archived. **Note** This action does not uninstall the AWS Replication Agent from the source server. Use the **Disconnect from service** option under the **Actions** menu when you have completed the migration and want to uninstall the agent from your source server. + **Revert to "ready for cutover"** – Choose this option to revert a finalized cutover for this server if you encounter any issues or want to reverse the cutover for any reason. This revert syour source servers' **Migration lifecycle** to the **Ready for cutover** status, indicating that these servers have not undergone cutover. The **Revert cutover for X servers** dialog appears. Click **Revert**. + **Edit launch settings** – Use this option to edit the launch settings for this server. You are redirected to the **Edit launch settings** page. [Learn more about launch settings.](launching-target-servers.md) + **Edit post-launch settings** – Use this option to edit the post-launch settings for the selected source server or group of source servers. [Learn more about post-launch settings.](source-post-launch-settings.md) + **Terminate launched instance** – Choose this option if you want to delete your test or cutover instance for any reason at any time. It can only be selected for a server that has a launched test or cutover instance. When the **Terminate launched instance** dialog appears, click **Terminate**. # Source server migration metrics The source server migration metrics present an aggregated overview of your source servers, focused on three topics: **Alerts**, **Data replication status**, and **Migration status**. ## Understand source server alerts The source server **Alerts** migration metric presents an aggregated overview of the application associated servers alerts. You can look up an individual source server's **Alerts** in the **Source servers** table at the bottom of the page. + A healthy server for which a test or cutover instance has not been launched displays a **Healthy** status. + A healthy server for which a test of cutover instance has been launched displays a **Healthy** status. + A server that is experiencing a temporary issue such as lag or backlog displays a **Lagging** status. + A server that is experiencing significant issues, such as a stall, displays a **Stalled** status. ## Understand data replication status The source server **Data replication status** migration metric presents an aggregated overview of the your source servers' data replication status. You can look up an individual source server's **Data replication status** status in the **Source servers** table at the bottom of the page. Source server **Data replication status** can have one of these values: + **Transferring snapshot** + **Initial sync** + **Finalizing sync** + **Lagging** + **Healthy** + **Stalled** + **Rescanning** + **Not started** + **Initiating** + **Creating snapshot** + **Paused** + **Disconnected** ## Understand the migration lifecycle metric The source server **Migration lifecycle** metric shows an aggregated overview of your source servers' migration lifecycle. You can look up an individual source server's **Migration lifecycle** status in the **Source servers** table at the bottom of the page. Source server **Migration lifecycle** can have one of these values: + **Stopped** + **Not ready** + **Ready for testing** + **Test in progress** + **Ready for cutover** + **Cutover in progress** + **Cutover complete** + **Disconnected** + **Discovered** # Filtering the source servers list You can customize the **Source servers** page through filtering. Filtering allows you to easily filter your servers by one or multiple properties. Click within the **Filter servers** field and choose the filtering property from the **Properties** menu. You can filter by a variety of properties, including: + Alerts – Filter by specific alert (lagging, stalled, launched). + Hostname – Filter by a specific hostname or a specific string of characters. + Migration lifecycle – Filter by the migration lifecycle state. + Data replication status – Filter by the data replication status. + Next step – Filter by next step. + SourceServerID – Filter by specific source server ID or string. + Tags – Filter by tags. Relevant specific tag values appear under the **Tags** category. Choose the value to filter by. You can filter by multiple properties at once in order to narrow down your results. Choose **Clear filters** to clear the current filtering properties selected.