Since AWS acquired CloudEndure in 2019, our new colleagues have supplied CloudEndure Migration and CloudEndure Catastrophe Restoration. CloudEndure Migration can transfer functions from any bodily, digital, or cloud-based infrastructure to AWS at no cost. This enhances AWS Server Migration Service (AWS SMS), which is an agentless service for migrating on-premises workloads to AWS. CloudEndure Catastrophe Restoration is a separate enterprise continuity providing, designed that will help you reduce downtime and knowledge loss. It repeatedly replicates the contents of your on-premises, digital, or cloud-based techniques to a low-cost staging space within the AWS Area of your selection, inside the confines of your AWS account. This supply is on the market to all AWS prospects and companions.
Just lately, we launched AWS Software Migration Service (AWS MGN), which we now advocate as the first migration service for lift-and-shift migrations to AWS. We encourage prospects who’re presently utilizing CloudEndure Migration or AWS SMS to modify to AWS MGN for future migrations. AWS MGN allows organizations to maneuver functions to AWS with out having to make any modifications to the functions, their structure, or the migrated servers.
With AWS MGN, you possibly can reduce time-intensive, error-prone handbook processes by mechanically replicating complete servers and changing your supply servers from bodily, digital, or cloud infrastructure to run natively on AWS. The service simplifies your migration by enabling you to make use of the identical automated course of for a variety of functions. By launching non-disruptive assessments earlier than migrating, you might be assured that your most crucial functions similar to SAP, Oracle, and SQL Server will work seamlessly on AWS.
AWS MGN reduces general migration prices as a result of there isn’t a have to put money into a number of migration options, specialised cloud improvement, or application-specific expertise. It’s because AWS MGN can be utilized emigrate any utility from any supply infrastructure that runs supported working techniques.
How AWS MGN Works
Emigrate to AWS, you put in the AWS MGN Replication Agent in your supply servers after which view and outline replication settings within the AWS MGN console. AWS MGN makes use of these settings to create and handle a staging space subnet with light-weight Amazon Elastic Compute Cloud (EC2) situations, that act as replication servers used to duplicate knowledge between your supply servers and AWS.
Replication servers obtain knowledge from the agent operating in your supply servers and write this knowledge to the Amazon Elastic Block Retailer (EBS) volumes. Your replicated knowledge is compressed and encrypted in transit and at relaxation utilizing EBS encryption. AWS MGN retains your supply servers updated on AWS utilizing steady, block-level knowledge replication. It makes use of your outlined launch settings to launch situations if you conduct non-disruptive assessments or carry out a cutover.
If you launch check or cutover situations, AWS MGN converts your supply servers in addition and run natively on AWS. After confirming that your launched situations are working correctly on AWS, you possibly can decommission your supply servers. You possibly can then select to modernize your functions by utilizing AWS providers and capabilities.
AWS MGN – Getting Began
To get began, create the replication settings template within the AWS MGN console. This template will decide how knowledge replication will work for every newly added supply server. Earlier than you configure your template, be sure that you meet the community necessities for operating AWS MGN.
Within the AWS MGN console, select Get began to create the template.
The replication settings configured on this template shall be utilized to every newly added supply server. You possibly can change the settings at any time for any particular person supply server or group of supply servers.
Replication servers are light-weight EC2 situations which might be used to duplicate knowledge between your supply servers and AWS. They’re mechanically launched and terminated as wanted. You need to use knowledge routing and throttling settings to manage how knowledge is routed out of your supply servers to the replication servers.
After you create your template, you possibly can add your supply servers. To edit your template, within the left navigation pane, select Settings. You possibly can edit particular person server replication settings after you add your supply servers.
So as to add supply servers to AWS MGN, set up the AWS MGN Replication Agent on them. You possibly can set up the agent on servers operating Linux and Home windows. For extra data, see including supply servers within the documentation.
For instance, obtain the
aws-replication-installet-init.py agent installer with the
wget command and run the set up script in your Linux supply server.
After the AWS Replication Agent is put in, the server shall be added to AWS MGN console and bear the preliminary sync course of.
The Supply Servers web page shows a listing of supply servers. Every row within the listing represents a single server. The migration lifecycle column reveals the present state of every supply server. After the preliminary sync course of has been accomplished efficiently, knowledge replication will begin mechanically.
After you’ve gotten added your supply servers, you need to configure the launch settings for every server. The launch settings are a set of directions that decide how a check or cutover occasion shall be launched for every supply server on AWS.
You have to configure the launch settings earlier than you launch check or cutover situations. To entry the launch settings, select the host title of a supply server after which navigate to the Launch settings tab.
After you’ve gotten added your supply servers and configured their launch settings, you might be able to launch a check occasion. You have to check the migration of your supply servers to AWS earlier than you provoke a cutover, to confirm that your supply servers operate correctly within the AWS setting.
To launch a check or cutover occasion for a single supply server or a number of supply servers, on the Supply Servers web page, choose the checkbox for every server for which you wish to launch a check occasion.
You possibly can check one supply server at a time or a number of supply servers concurrently. For every supply server, you’ll be knowledgeable of the success or failure of the check. Select Launch check situations to start out the check, after which select Launch.
When the check has began, the console will show a Launch job began message. To view the precise job for the check launch, select View job particulars.
Use the Migration dashboard tab to watch the progress in relation to the migration lifecycle.
As a greatest apply, carry out a check a minimum of one week earlier than you intend emigrate your supply servers. This enables you time to determine and resolve issues earlier than the cutover takes place. After you launch the check situations, use SSH (Linux) or RDP (Home windows) to hook up with your occasion and be sure that the whole lot is working appropriately.
After you’ve gotten finalized the testing of your supply servers, you might be prepared for a cutover. It’s a greatest apply to schedule the cutover time prematurely. After the cutover motion is carried out, the server is taken into account migrated, and you need to redirect your customers out of your authentic supply servers to the migrated ones.
If you’re fully performed together with your migration and carried out a profitable cutover, you possibly can finalize the cutover. This can change your supply servers’ migration lifecycle standing to Cutover full, indicating that the cutover is full and that the migration has been carried out efficiently.
Monitoring and Troubleshooting
You possibly can monitor AWS MGN utilizing Amazon CloudWatch, Amazon EventBridge, and AWS CloudTrail, which gather uncooked knowledge and course of it into readable, near-real-time metrics. For extra data, see Monitoring Software Migration Service within the documentation.
For those who encounter any points and wish to launch new check or cutover situations, you possibly can revert the check or cutover motion. This can revert your supply servers lifecycle standing to the earlier stage, indicating that these servers haven’t undergone cutover. Throughout a revert, additionally, you will have the choice to delete your check or cutover situations for cost-saving functions. For extra data, see Troubleshooting within the documentation.
AWS Software Migration Service (AWS MGN) is now obtainable within the US East (N. Virginia), US West (Oregon), US East (Ohio), Asia Pacific (Tokyo), Asia Pacific (Sydney), Asia Pacific (Singapore), Europe (Eire), Europe (Frankfurt), and Europe (Stockholm). In case your most well-liked AWS Area shouldn’t be presently supported by AWS MGN, think about using CloudEndure Migration. For those who can not set up an agent in your servers, think about using AWS Server Migration Service (AWS SMS).
Though the usage of AWS MGN is free for 90 days, you’ll incur expenses for any AWS infrastructure that’s provisioned throughout migration and after cutover. For extra data, see the AWS MGN pricing web page.
Get began with the AWS Software Migration Service right this moment. Please ship suggestions by way of your AWS Assist contacts.
For an outline of AWS MGNadvantages, service, and community structure particulars, watch the video.