Lifecycle - Application Migration Service

Lifecycle

The Lifecycle view shows the current state of each server within the migration lifecycle.

Lifecycle states include:

  • Not ready - The server is undergoing the Initial Sync process and is not yet ready for testing. Data replication can only commence once all of the Initial Sync steps have been completed.

  • Ready for testing - The server has been successfully added to Application Migration Service and data replication has started. Test or Cutover instances can now be launched for this server.

  • Test in progress - A Test instance is currently being launched for this server.

  • Ready for cutover - This server has been tested and is now ready for a Cutover instance to be launched.

  • Cutover in progress - A Cutover instance is currently being launched for this server.

  • Cutover complete - This server has been cutover. All of the data on this server has been migrated to the Cutover instance.

The Lifecycle always displays the Launch status, Last test, and Cutover status for each server that has undergone these stages.

Not ready

The Not ready Lifecycle state represents several possible scenarios:

Server undergoing Initial Sync

A source server that has been added to Application Migration Service will automatically begin the Initial Sync process after AWS Replication Agent installation.

Data Replication can only commence after all of the Initial Sync steps have been completed. The server will be in the Not ready Lifecycle state until Initial Sync has been successfully completed.

Initial sync steps include:

  • Initiation

    • Creating Firewall Rules

    • Creating Replication Server

    • Booting Replication Server

    • Resolving Service Manager Address

    • Authenticating with the Service Manager

    • Downloading Replication Software

    • Creating Staging Disks

    • Pairing Replication Server with Agent

    • Establishing Communication between AWS Replication Agent and Replication Server

  • Sync (0% to 100%)

  • Flush backlog (if any)

  • Create first launchable snapshot

You can review the overall progress of the Initial Sync process under the Data replication status view.

Here you can see the percentage of completion, the time left until initial sync is finished, and whether there are any issues (such as a stall).

You can tell that a server has successfully completed the Initial Sync process through several indicators on the main Source Servers page as well as on the Migration dashboard tab for an individual server.

On the main Source Servers page, a newly added server that has completed Initial Sync for the first time will show Ready for testing under the Migration lifecycle column and Healthy under the Data replication status column.

On the individual server view, under the Migration dashboard tab, the Lifecycle section will show the Ready for testing status. The Data replication status section will show the Healthy status.

Note

Servers will automatically undergo Initial Sync every time there is a network disconnect.

Unable to complete initiation

The server will be in the Not ready Lifecycle state until Initial Sync has been successfully completed.

If the Initial Sync process is stalled for any reason, the Data replication status section will indicate that replication has stalled.

Scroll down to Replication initation steps to see the step on which the rror occurred. The step on which Initial Sync failed will be marked with a red "x".

You will have to fix the indicated issue before the Initial Sync process can continue. You will not be able to migrate your server and the server will remain in the Not ready state ,until the issue has been fixed.

Each step has unique troubleshooting methods.

Ready for testing

Once the server has successfully completed the Initial Sync process, it will enter the Ready for testing Lifecycle state.

The Data replication status box will show a Healthy state, indicating that the server is healthy.

You can now launch a Test instance for this server. The server will stay in the Ready for testing Lifecycle state until you launch a Test instance for the server.

Test in progress

Once you have launched a Test instance for your server, the Migration dashboard will show the Test in progress Lifecycle state.

Within the Lifecycle box, you can review the Launch status and Last test information fields for the Test instance.

The Launch status field will show the time of the Test instance launch. While the Testing instance is being launched, the Launh status field will show Waiting.

Once the Test instance has been launched, the Launch status will show Launched. Wait for the instance to boot and then choose View in EC2 console link to open the EC2 Console in a new tab, in order to view and monitor your launched Test instance.

The AWS EC2 Console will open in a new tab and will automatically search for and display your Test instance.

The Last test field will show the date of the last test. You can review the test launch details by clicking on the Job ID.

This will open the job within the Launch History page in a new tab.

On the main Source Servers page, the Migration lifecycle column will show Ready for testing and the Next step column will show Launch test instance.

The server will stay in the Test in progress Lifecycle state until you finalize your testing and mark the server as Ready for cutover.

You can tell that the Test instance was successfully launched through several indicators:

On the Server Details > Lifecycle pane, the Launch status will state Launched.

On the main Source Servers page, the Alerts column will show the Launched status.

Ready for cutover

After you have finalized your testing, the Migration dashboard will show the Ready for cutover Lifecycle state.

The Launch status field will show the time of the last Test instance launch. Click on the View in EC2 console link to open the EC2 Console in a new tab in order to view and monitor your launched Test instance.

The Last test field will show the date the last test was started. You can review the test launch details by clicking on the Job ID. This will open the relevant Job.

The Cutover field will show the date of the last Cutover instance launch, if applicable. You can review the cutover launch details by clicking on the Job ID. This will open the relevant Job.

On the Source Servers page, the Migration lifecycle column will show Ready for cutover and the Next step column will show Terminate test instance; Launch cutover instance.

The server will stay in the Ready for cutover Lifecycle state until you launch a Cutover instance.

Cutover in progress

Once you have launched a Cutover instance for your server, the Migration dashboard will show the Cutover in progress Lifecycle state.

The Launch status field will show the last time of cutover launch. Click on the View in EC2 console link to open the EC2 Console in a new tab in order to view and monitor your launched Cutover instance.

The Last test field will show the date the last test was started. You can review the test launch details by clicking on the Job ID. This will open the Job.

The Cutover field will show the date of the last Cutover instance launch. You can review the cutover launch details by clicking on the Job ID. This will open the Job.

On the Source Servers page, the Migration lifecycle column will show Cutover in progress and the Next step column will show Complete the cutover.

The server will stay in the Cutover in progress Lifecycle state until you complete the cutover.

Cutover complete

Once you have completed your Cutover instance launch for your server, the Migration dashboard will show the Cutover Complete Lifecycle state. This is the final state in the migration lifecycle. This state indicates that you have successfully migrated your source server to AWS.

The Launch status field will show Launched. Click on the View in EC2 console link to open the EC2 Console in a new tab in order to view and monitor your launched Cutover instance.

The Last test field will show the date the last test was started. You can review the test launch details by clicking on the Job ID. This will open the Job.

The Cutover field will show the date you finalized your Cutover instance launch. You can review the cutover launch details by clicking on the Job ID. This will open the Job.

The Application Migration Service Console will automatically stop data replication for the source servers that were cutover in order to save resource costs. On the Source Servers page, the selected source servers' Migration lifecycle column will show the Cutover complete status, the Data replication status column will show Disconnected and the Next step column will show Mark as archived.