Migrate an on-premises Microsoft SQL Server database to Amazon EC2 using CloudEndure - AWS Prescriptive Guidance

Migrate an on-premises Microsoft SQL Server database to Amazon EC2 using CloudEndure

Created by Pavel Rubin (AWS)

Environment: Production

Source: Databases: Relational

Target: Amazon EC2

R Type: Rehost

Workload: Microsoft

Technologies: Migration; Databases

AWS services: Amazon EC2

Summary

This pattern provides guidance for migrating a Microsoft SQL Server database from an on-premises data center host to an Amazon Elastic Compute Cloud (Amazon EC2) instance using CloudEndure Migration.

Important    CloudEndure Migration will be discontinued in all AWS Regions except for the AWS GovCloud (US), Mainland China (Beijing), and Mainland China (Ningxia) Regions on December 30, 2022. Learn more

This publication will be removed on September 30, 2022. If you need it for a migration project in progress, please use the PDF link on this page (provided below the title) to download and save the PDF file.

Prerequisites and limitations

Prerequisites

  • An active AWS account

Product versions

  • Microsoft SQL Server versions 2008, 2008 R2, 2012, and 2014 for the Enterprise, Standard, Workgroup, and Developer editions

Architecture

Source technology stack

  • Microsoft SQL Server database in an on-premises data center

Target technology stack

  • Microsoft SQL Server database on an EC2 instance (for a complete list of supported operating system versions, see Amazon EC2 FAQs)  

Source and target architecture

CloudEndure migration:

Network architecture:

Tools

  • CloudEndure Migration - CloudEndure Migration helps you simplify, expedite, and automate large-scale migration to AWS. Continuous Data Replication takes place in the background, without application disruption or performance impact, which ensures that data is synced in real-time and minimizes cutover windows. When migration cutover is initiated, CloudEndure runs a highly automated machine conversion and orchestration process, allowing even the most complex applications and databases to run natively on AWS, without compatibility issues and with minimal IT skills necessary. 

Epics

TaskDescriptionSkills required
Navigate to AWS Marketplace, search for CloudEndure Migration, and subscribe.

For a link to AWS Marketplace and for more information about the steps described in subsequent stories, see the "Related resources" section at the end of this pattern.

General AWS
Register the account and confirm the email.General AWS
Set the account password and accept terms and conditions.

Passwords must be at least 8 characters long and must contain one uppercase letter, one lowercase letter, one digit, and one special character.

General AWS
TaskDescriptionSkills required
Sign in to the CloudEndure user console.

On the CloudEndure console, sign in with the credentials you created in the previous step.

CloudEndure admin
Create a new project.

Choose the plus (+) button in the upper-left corner of the console to create a project.

CloudEndure admin
Enter a project name and select a project type and license package.

Select "Live Migration" as the project type. You can acquire a license through AWS Marketplace.

CloudEndure admin
TaskDescriptionSkills required
On the AWS Identity and Access Management (IAM) console, generate an access key ID and secret access key.

To generate the required AWS credentials to use with the CloudEndure user console, you need to create at least one IAM user and assign the proper permission policy to this user. The user console requires an access key ID and a secret access key.

AWS SysAdmin
Choose "Policies," and then choose "Create policy." AWS SysAdmin
Choose the JSON tab, copy the CloudEndure IAM policy into the field, and then choose "Review policy." AWS SysAdmin
Enter a name and description for the policy, and then choose "Create policy." AWS SysAdmin
Create a new IAM user.

On the IAM console, navigate to Users, choose "Add user," assign the user a name, and then set the "Access type" to Programmatic access.

AWS SysAdmin
Choose "Next: Permissions" and then under "Set permissions for user," choose "Attach existing policies." AWS SysAdmin
Locate the policy you created, check the box to the left of the policy name, and then choose "Next: Review." AWS SysAdmin
Verify that the fields are correct, and then choose "Create user." AWS SysAdmin
Copy the access key ID and secret access key and store them in a safe location. AWS SysAdmin
Sign in to the CloudEndure user console, and select your migration project.AWS SysAdmin
Choose the "Setup & Info" tab from the left menu, and navigate to AWS credentials.AWS SysAdmin
Copy and paste your AWS access key ID and secret access key into the corresponding fields, and then choose "Save."AWS SysAdmin
TaskDescriptionSkills required
In the CloudEndure user console, navigate to "Setup & Info," and then choose "Replication settings." CloudEndure admin
For "Live Migration Source," choose "Other Infrastructure." CloudEndure admin
Define your replication servers.

See the CloudEndure documentation links in the "Related resources" section for detailed instructions.

CloudEndure admin
TaskDescriptionSkills required
In the CloudEndure user console, navigate to "Machines," "Machine Actions," "Add Machines." CloudEndure admin
Locate your agent installation token.

When you run the installer file on a source machine, you are first asked to enter your installation token. The token is a unique string of characters that is automatically generated for you when your CloudEndure account is activated. One installation token enables you to install the agent on as many source machines as your license package and project allow.

CloudEndure admin
For Linux machines, copy the installer command, log in to your source machines, and then run the installer.

For detailed instructions, see the CloudEndure documentation in the "Related resources" section.

CloudEndure admin
For Windows machines, download the installer file to each machine, and then run the installer command.

For detailed instructions, see the CloudEndure documentation in the "Related resources" section.

CloudEndure admin
Wait as the machine undergoes initial data replication.

After the agent is installed, the source machine will appear on the "Machines" tab on the CloudEndure console.

CloudEndure admin
TaskDescriptionSkills required
On the CloudEndure console, choose a machine name from the "Machines" tab to access the "Machine Details" pane.CloudEndure admin
Select the "Blueprint" tab from the menu.

You can configure a variety of Blueprint settings. For detailed instructions, see the CloudEndure documentation in the "Related resources" section.

CloudEndure admin
TaskDescriptionSkills required
On the CloudEndure console, on the "Machines" tab, select the box to the left of each source machine.CloudEndure admin
On the "Launch x Target Machines" menu, choose "Test Mode."

"x" represents the number of machines to launch.

CloudEndure admin
Choose "Continue" when prompted. The machines will be launched.

You can review the launch process on the "Job Progress" tab.

CloudEndure admin
Verify that the test completed successfully.

The "Machine" tab will indicate that testing is complete: The edge of each tested "Source" machine will be marked in green. The orange flag icon under the "Status" column, which previously indicated that the machine had not been tested, will disappear (if no other issues are found). The purple icon, which indicates that a target machine has been launched for the selected source machine, will appear. In the "Live Migration Lifecycle" column, a message will appear stating that the machine has been tested recently.

CloudEndure admin
Test the target machines by choosing each machine's name, opening the "Target" tab, copying the public IP address, and navigating to that IP address.CloudEndure admin
TaskDescriptionSkills required
Schedule a cutover window.CloudEndure admin
On the "Machines" tab, select the box to the left of each source machine.CloudEndure admin
On the "Launch x Target Machines" menu, choose "Cutover Mode."

"x" represents the number of machines to launch.

CloudEndure admin
Choose "Continue" when prompted. The machines will be launched.

You can review the launch process on the "Job Progress" tab.

CloudEndure admin
Verify that the cutover completed successfully.

The "Machines" tab will indicate that the cutover is complete: The edge of each tested source machine will be marked in green. The purple icon, which indicates that a target machine has been launched for the selected source machine, will appear. In the "Live Migration Lifecycle" column, a message will appear stating that the machine has cut over.

CloudEndure admin

Related resources

AWS Marketplace

CloudEndure

CloudEndure documentation

Microsoft SQL Server on AWS

Tutorials and videos