More about Cloud Migration
- Refactoring Applications to Kubernetes in Cloud Migrations
- The War Over the Cloud Has Ended (and the Winner Might Surprise You)
- Modern Data Estate: What IT Leaders Need To Know
- Strategies for AWS Migration: The New 7th R Explained
- Cloud Computing Deployment Models and Architectures
- Cloud Adoption Strategy: What’s the Best Approach for Your Organization?
- What is Cloud Migration? Strategy, Process and Tools
- Hybrid Cloud Strategy: A Winning Model for Enterprises
- Google Cloud Architecture and Building Your Own Solution Architecture
- SnapMirror in the Cloud: New Use Cases for NetApp’s Data Replication Technology
- 8 Digital Transformation Technologies and Their Business Impact
- What Is Digital Transformation in Banking?
- Digital Transformation in Healthcare: 4 Key Trends
- Digital Transformation: Examples from 5 Industries
- The Future of Cloud Computing: 5 Trends You Must Know About
- 5 Types of Digital Transformation and the Technologies that Power Them
- Digital Transformation Strategy: 6 Tips for Success
- Kubernetes Data Mobility with Cloud Volumes ONTAP
- Application Migration to Azure: 4 Approaches and One Migration Tool
- Cloud First Strategy: Challenges, Considerations, and Best Practices
- Application Migration to AWS: Free Tools to Ease Your Migration
- Why Cloud Adoption Fails and 6 Tips for Success
- Cloud Application Migration: A Practical Guide
- AWS Snowball vs Snowmobile: Data -Migration Options Compared
- AWS Snowball Edge: Data Shipping and Compute at the Edge
- AWS Snowmobile: Migrate Data to the Cloud With the World’s Biggest Hard Disk
- AWS Snowball Family: Options, Process, and Best Practices
- AWS Cloud Adoption Framework (CAF): 6 Migration Perspectives
- Top 3 Cloud Adoption Frameworks: Your Path To The Cloud
- AWS Snowball Pricing Simplified
- Azure Cloud Adoption Framework: The 9 Methodologies Explained
- Cloud Roadmap: Mapping Out Your Path To The Cloud
- Hybrid Deployment on Google Cloud: Meet Google Anthos
- 3 Ways to Create an Azure Migrate Project
- Azure Migration Step by Step: Discover, Migrate, Optimize, and Monitor
- Migrate from VMware to Azure: The Basics and a Quick Tutorial
- Migrate SQL Server to Azure: Options, Tools, and a Quick Tutorial
- Migrate Databases to Azure: 3 Quick Tutorials
- 4 Ways to Migrate SQL to Azure
- Azure Migration Program: 4 Key Elements
- Azure Migrate: Key Components and a 4-Step Migration Plan
- Cloud Journey: 6 Stages of Cloud Adoption
- 5 Azure Data Migration Tools You Should Be Using
- Azure Migration Tools: One-Click Migration for VMs and Data
- Typical Mistakes and Misconceptions Business Leaders Have About Hybrid and Multicloud
- Google Cloud PostgreSQL: Managed or Self-Managed?
- AWS Storage Gateway: Connecting Your On-Premise Storage to the Amazon Cloud
- Azure PostgreSQL: Managed or Self-Managed?
- Cloud Scalability: How Cloud Volumes ONTAP Stores Petabytes of Data
- AWS Migration: Understanding the Process and Solving 5 Key Challenges
- Google Cloud Pricing vs AWS: A Fair Comparison?
- VMware Cloud Services: A New Option for Hybrid Cloud Management
- AWS PostgreSQL: Managed or Self-Managed?
- Google Cloud MySQL: MySQL as a Service vs. Self Managed in the Cloud
- Azure MySQL: MySQL as a Service vs. Self-Managed in the Cloud
- AWS MySQL: MySQL as a Service vs. Self Managed in the Cloud
- Cloud Adoption for Financial Companies
- VMware on AWS: Architecture and Service Options
- VMware on Google Cloud: A Deployment Roadmap
- VMware on Azure: One-Step Migration to the Cloud
- Better in the Cloud: Workloads Gartner Says You Should Move to the Cloud Now
- 3 Cloud Migration Approaches and Their Pros and Cons
- Oracle on Google Cloud: Two Deployment Options
- How to Upload Files to Azure Blob Storage with AzCopy, PowerShell, and More
- Oracle on Azure: Fully Managed vs Self Managed
- Azure SQL Server: Managed Service vs Self Managed
- Google Partners with NetApp on New Bare Metal Solution in the Cloud
- AWS Database Migration Service: Copy-Paste Your Database to Amazon
- SQL Server on Google Cloud: Two Deployment Options
- GCP Migration with Cloud Volumes ONTAP
- SQL Server in AWS: Two Deployment Options
- Azure Database Migration Service: Automate Your Cloud DB Migration
- Azure Managed Service Provider: How to Save Time and Reduce Cloud Overhead
- Hybrid Cloud Storage: The Best of Both Worlds
- Hybrid Cloud Storage Solutions for AWS Compared: Storage Gateway vs Cloud Volumes ONTAP
- AWS Oracle: Two Options for Migrating Your Oracle DB to Amazon
- Migrating Physical Server to AWS: Now Free with AWS CloudEndure
- Azure Hybrid Cloud:
Azure in Your Local Data Center
- What Is a Lift and Shift Cloud Migration?
- Azure StorSimple EOL: Using Cloud Volumes ONTAP for Hybrid Cloud Management
- Google Cloud Migration Tools: Copying 1GB or 500TB? Learn How
- VMC on AWS Vs. Cloud Volumes ONTAP
- AWS Cloud Migration Services: Don’t Migrate Alone
- 5 Steps to the Cloud: AWS Migration Checklist
- Setting up Storage Gateway with Amazon EC2
- VMware Cloud on AWS: How Fujitsu Saves Millions Using Cloud Volumes ONTAP
- SQL Server End of Life Challenges and How Cloud Volumes ONTAP Can Help
- The Cloud Tiering Service Architecture: How We Get Cold Data from Your Data Center to the Cloud
- Cloud Data Integration 101: Benefits, Challenges, and Tools
- Google Cloud Migration: Why and How to Make the Move
- What’s the Easiest Way to Start Using the Cloud? Three Cloud Onboarding Approaches
- AWS vs Azure vs Google Cloud: Choosing the Best Cloud Provider for You
- Cloud Migration Tools: Transferring Your Data with Ease
- Azure Migration Strategy: Four Steps to the Cloud
- 11-Step Azure Migration Checklist
- AWS Migration Strategy: The 6 Rs in Depth
- Officeworks Adopts a Cloud-First Strategy with Cloud Volumes ONTAP
- Azure Migration: The Keys to a Successful Enterprise Migration to Azure
- Cloud Volumes ONTAP: Cloud Migration Case Studies
- One Cloud Out of Many: Why Enterprises Are Turning to Multicloud and Hybrid Cloud Architectures
March 30, 2020
Topics: Cloud Volumes ONTAP Data MigrationAWSElementary6 minute read
When migrating to AWS, a common challenge is the need to migrate physical, non-virtualized servers to the Amazon environment. CloudEndure was a third-party solution developed to make migration of physical resources easy. In 2019, Amazon acquired CloudEndure and provided free access to the solution to all its customers, to ease and encourage migration of non-virtualized workloads to the Amazon cloud.
In this post, we’ll explain how CloudEndure works, how to install the agent on your on-premise machines to begin the AWS migration process, and explain the terms and conditions of the AWS free CloudEndure license. In addition, we’ll show how NetApp Cloud Volumes ONTAP can help you migrate large storage volumes effortlessly to AWS.
In this article, you will learn:
- What is the CloudEndure migration service for physical servers
- How CloudEndure works
- Installing the CloudEndure agent
- Terms of the free CloudEndure license
- Migrating storage to AWS with Cloud Volumes ONTAP
CloudEndure Migration: An AWS Service for Migrating Physical Servers to the Cloud
AWS acquired CloudEndure, a Disaster Recovery as a Service (DRaaS) product that lets you seamlessly move physical server workloads to the cloud. Amazon CloudEndure Migration is a free, highly automatic, lift-and-shift migration solution.
CloudEndure Migration is not affected by compatibility issues, does not affect performance of production workloads, and does not require long cutover periods. This is also known as a lift and shift approach to cloud migration. However, if you want to re-architect your applications for the cloud, do not make the changes on-premises. Wait with architectural changes until after workloads are running correctly in AWS.
CloudEndure continually replicates source machines into a staging area in your AWS account, without taking snapshots or writing any data to disk. You can easily perform non-disruptive tests to see how workloads behave in the cloud. When you are ready to start the production machines, it automatically converts your machines from their source infrastructure into AWS infrastructure, so they can boot and run natively in AWS.
Source: Amazon Web Services
CloudEndure Migration supports common databases, such as Oracle and SQL Server, and enterprise applications like SAP.
Before you start migrating workloads using CloudEndure, we recommend checking out our articles on planning your AWS Migration Strategy and our 5-Step AWS migration Checklist.
How CloudEndure Migration Works
CloudEndure is based on an agent which you install on the source machines you would like to migrate. No reboot is needed, and there is no functionality impact on your local environment. The agents use an API call to generate a staging area on your AWS account, ready to receive replicated data.
CloudEndure Migration’s automatic rehosting process works in three stages:
- Initial replication—after the agent is installed, entire machines are replicated to the staging area.
- Configuration and testing—set up target machines and run realistic tests, without disrupting the on-premises production environment.
- Cutover—when you are ready, CloudEndure automatically converts machines to run in AWS.
Each source disk on your on-premises machines maps into an identically sized EBS volume in the Staging Area. After all source disks are fully replicated, the CloudEndure agent can track and continuously replicate subsequent changes to the source disks. Continuous replication occurs at the block level, meaning that CloudEndure can replicate virtually almost any program running on x86-based Windows or Linux operating systems.
When the target machines are launched for testing or production, CloudEndure automatically configures them to allow them to boot up and run natively on AWS. This process involves injecting the appropriate AWS drivers, making appropriate bootloader changes, modifying network adapters, and triggering operating systems with AWS Key Management Service (KMS). Conversion takes less than a minute, irrespective of machine size, and can be performed on multiple machines in parallel.
Source: Amazon Web Services
Installing the CloudEndure Agent
Follow the process below to install the CloudEndure agent and start replicating on-premises servers to AWS.
1. Create an IAM user that will provide CloudEndure access to your AWS account.
2. Register for a free CloudEndure Migration account.
3. Log into the CloudEndure User Console and provide the AWS key ID and secret access key for the IAM user you created.
4. Configure replication settings, including details of the migration source, and details of the target, including subnet, security group, VPN, Direct Connect usage, and encryption.
5. CloudEndure will prompt you to install the agent on your source machines. It will provide installation instructions as shown below.
Source: Amazon Web Services
6. Run the installer. For large-scale migrations affecting hundreds or thousands of machines, use the unattended installation parameter, together with a standard deployment tool to remotely install the agent on your machines.
7. When installation finishes, CloudEndure adds source machines to the CloudEndure User Console, and starts replicating data. This occurs in two stages: first sync, which involves duplicating each disk’s data to an EBS volume, and continuous data replication.
8. Select Machines from left-hand navigation and click Details to see exactly at what stage replication is for each machine.
9. To understand the overall status of your migration, click Machines and watch the Data Replication Progress column in the list of machines. When this column says Continuous Data Replication, and the Migration Lifecycle column says Ready for Testing, this means machines are functioning properly on the cloud and ready for testing and cutover.
Terms of the Free CloudEndure License
AWS provides a free CloudEndure Migration license which you can use for 90 days after initial setup of the agent, with no limitation on number of tests, data volumes or number of machines migrated.
After 90 days, if your migration is still not complete, you can still migrate at no cost by reinstalling the CloudEndure agent on the machines that have not yet been migrated. This will give you an extra 90 days to perform replication, testing and cutover for the remaining machines.
While the use of CloudEndure Migration is totally free, you may incur fees for AWS infrastructure provisioned during migration and after cutover, for example computing (EC2) and storage (EBS) resources.
Migrating Storage to AWS with Cloud Volumes ONTAP
NetApp Cloud Volumes ONTAP, the leading enterprise-grade storage management solution, delivers secure, proven storage management services on AWS, Azure and Google Cloud. Cloud Volumes ONTAP supports up to a capacity of 368TB, and supports various use cases such as file services, databases, DevOps or any other enterprise workload.
In particular, Cloud Volumes ONTAP assists with cloud migration. NetApp’s data replication tools SnapMirror® and Cloud Sync service will get your data to the AWS cloud.