Skip to Content
Technical Articles
Author's profile photo Rajarajeswari Kaliyaperumal

Performing a Lift-and-Shift of SAP workload to AWS using CloudEndure

Performing a Lift-and-Shift of SAP workload to AWS using CloudEndure

1.What is CloudEndure Migration?

CloudEndure Migration is a new AWS-native migration tool for SAP customers.  CloudEndure Migration simplifies, expedites, and reduces the cost of cloud migration by offering a highly automated lift-and-shift solution.

2.How does CloudEndure works?

CloudEndure Migration conducts continuous, block-level data replication of our source machines into a staging area in our AWS account without causing downtime or impacting performance. When we are ready to launch the production machines, CloudEndure Migration automatically converts our machines from our source infrastructure into the AWS infrastructure so we can boot and run natively in AWS.


1.Implementation begins by installing the CloudEndure Agent on the selected source machines. The agent installation does not require a reboot nor does it impact system performance in any noticeable way.

2.The CloudEndure Agent connects to a self-service, web-based CloudEndure User Console, which then issues an API call to the selected target AWS Region to create a staging area in the customer’s account designated to receive the source machine’s replicated data..The staging area consists of both lightweight EC2 instances that act as Replication Servers and low-cost staging EBS volumes. Each source disk is mapped to an identically sized, low-cost EBS volume in the staging area.

3.The Replication Servers receive data from the CloudEndure Agent running on the source machine and writes this data onto staging EBS volumes. One Replication Server can handle multiple source machines replicating concurrently.

4.After all source disks have been replicated into the staging area, the CloudEndure Agent continues to track and replicate any changes to the source disks. CloudEndure Migration conducts continuous, asynchronous, block-level data replication, which enables replication of any application that runs on supported x86-based Windows and Linux OSs that allow agent installation.

5.Customers configure a Target Machine Blueprint in the CloudEndure Console, which defines where each machine should launch and how it should be provisioned at the time of test or cutover.

6.When the Target Machines are launched, CloudEndure Migration spins up a temporary Machine Converter responsible for modifying the Target Machine to be able to boot and run natively in AWS. This includes injecting the appropriate AWS drivers, making appropriate bootloader changes, modifying network adapters, activating operating systems using the AWS KMS, and more. The conversion process normally takes under a minute, irrespective of the size of the machine, and is executed on all launched machines in parallel.


3.What are the advantages of using CloudEndure migration over other tools?

a.Easy Migrations:

CloudEndure Migration simplifies the process of migrating applications from physical, virtual, and cloud-based infrastructure, ensuring that they are fully operational in any AWS Region without compatibility issues. Getting started is quick and easy regardless of the application type. This enables customers to rapidly execute complex, large-scale migration projects, while significantly reducing risk.

  1. Increased uptime:

Maintain normal business operations throughout the replication process. CloudEndure Migration continually copies source machines  – without taking snapshots or writing any data to disks – which means minimal performance impact and no need to reboot machines. Continuous replication also makes it easy to conduct non-disruptive tests and shortens cutover windows.

  1. Reduced costs:

CloudEndure Migration is a single tool for migrating any application or database from any source infrastructure on supported operating systems to AWS. This includes migrating legacy applications, third-party applications, and line-of-business applications. There is no need to invest in specialized cloud development, OS/application-specific skills, or significant IT resources, resulting in greatly reduced operational costs


4.What are the prerequisites for CloudEndure Migration?

A.To prepare your network for running CloudEndure Migration, set the following connectivity settings:

a.Communication over TCP port 443:

Between the source machines and the CloudEndure user console.

Between the staging area and the CloudEndure user console.

b.Communication over TCP port 1500:

Between the source machines and the staging area.

  1. The CloudEndure Migration agent installation on the source machines has the following requirements:

Root directory—Verify that you have at least 2 GB of free disk on the root directory (/) of your source machine.

/tmp directory (Linux)—You need at least 500 MB of free disk on the /tmp directory for the duration of the installation process.

Available RAM—Verify that the machine has at least 300 MB of free RAM to run the CloudEndure agent.

C.Linux systems have the following requirements:

Python—Use Python 2 (2.4 or above) or Python 3 (3.0 or above).

dhclient—Make sure to install thedhclient package.

Kernels—Verify that you have kernel-devel/linux-headers installed that are the same version as the kernel you are running.

D.For Windows systems, make sure that you are using .NET Framework version 4.5 or above on machines running Windows Server 2008 R2 or later. Use .NET Framework version 3.5 or above on machines running Windows Server 2008 or earlier.

E.Use VPC peering between the source VPC and staging VPC. This is not mandatory, and only used in cases of cross-region or cross-account migration projects.


5.What are the technical steps involved to migrate our SAP workload to AWS using CloudEndure?


1.Register for a CloudEndure Migration account

2.Set up a project and define replication settings.

3.Install a CloudEndure agent on the source Amazon EC2 instances.

4.Monitor replication and update blueprint.

5.Launch test instances.

6.Perform migration cutover.

7.Perform SAP post-migration activities.

8.Perform cleanup activities.

For more detailed steps refer below link.

Sample Video:

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.