AWS to Azure Cloud Migration Errors

AWS to Azure Cloud Migration Errors

Share Now
3 min read

Let us see the Case study on “AWS to Azure Cloud Migration Errors”. Recently we worked with one of our customers to migrate 30 Linux servers from AWS to Azure. As per the Azure cloud migration assessment process, we identified the Linux servers are a part of Nitro instances into AWS.

Nitro instances are a great offering from AWS. Which provides enhanced networking capabilities to the server(Instance). It has its own specific drivers for networking as well as storage blocks.

We would give a short description of how to migrate servers from AWS to Azure and AWS to azure migration challenges

AWS to Azure Cloud Migration Errors - know more

AWS to Azure migration step by step includes:

The steps described how to migrate servers from on-premises to the public cloud.
  • The assessment process
  • The Discovery 
  • Modelling the target VM as per the production server information
  • Data transfer from AWS to Azure cloud
  • Inserting all the necessary drivers to support the Azure cloud
  • Booting the target server 
  • Monitor the performance and ensures the network drivers loads correctly.
  • ssh or RDP to the target VM
  • Send the server to the customer for UAT.

We started the POC process to discover the production server and proceed with the migration. The Azure migration started from AWS.

There is a process where we call the target cloud Azure via API to create a disk partition on the target VM so that the next step of data transfer can be started.

The target disk partition for Azure failed with an error “Error making partition number”

We had a troubleshooting session. Thus the cloud migration of a Nitro instance from AWS to Azure is failing with errors because of the device structure on AWS.

The Linux server on AWS has its EBS volume for Nitro instances. Hence the EBS volumes are exposed as NVMe block devices.

The device name is identified as /dev/nvme0n1 instead of /dev/sda1

There are certain AWS AMI who has to prebuild NMVE device drivers.

  • Amazon Linux 2
  • Amazon Linux AMI 2018.03
  • Ubuntu 14.04 or later
  • Red Hat Enterprise Linux 7.4 or later
  • SUSE Linux Enterprise Server 12 SP2 or later
  • CentOS 7 or later
  • FreeBSD 11.1 or later

When the Linux servers from Nitro instances are migrating into Azure, the cloud migration tool or the cloud migration team should be intelligent enough to convert the production server storage device to the standard device structure as /dev/sda1. Therefore these conversions of devices should be into the migration JSON file.

As a result, the target VM see the structure and the disk partition call via API to be made into Azure.

At Lia Infraservices, we perform some manual workaround and made the changes into the migration JSON and started the migration with changed device partitions. In this way, we were able to migrate the Linux server from AWS nitro instance to Azure to avoid AWS to Azure Cloud Migration Error.

You can also check on AWS to Azure Seamless Cloud Migration

Our POC was successful and we used the same approach for all the production servers. The batch of servers from AWS to Azure migration was successful.

Our cloud migration team has dedicated to making any migration project successful.

Request a DEMO with us and we will help you clarify all your queries related to cloud migration.

You might be interested in Checking out our other blog on the: Steps for Cloud Migration process.

Lia Infraservices is a top-notch E-Commerce Website Development Company in Chennai, which helps you to handle your day to day bulk e-commerce business data into the cloud through end to end Cloud Migrations Services in Chennai. The No.1 Mobile App Development Company in Chennai is also involved in building amazing Web Development Services, DevOps, Graphics & UI/UX Design and the popular Digital Marketing Company in Chennai, India.

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

Leave comment

Your email address will not be published. Required fields are marked with *.