More about Cloud Migration
- Petabyte-Scale Storage Success Stories With Cloud Volumes ONTAP
- Azure StorSimple EOL: Using Cloud Volumes ONTAP for Hybrid Cloud Management
- 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?
- 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
August 16, 2018
Topics: Cloud Volumes ONTAP AzureData MigrationAWSAdvanced7 minute read
AWS and Azure both offer hyperscale, reliable, and secure hosting environments for enterprise workloads in the cloud. Many organizations have already adopted a “cloud first” policy to leverage these benefits and have gone all-in with either an AWS or Azure migration. But what if something changes and a company wants to leave that cloud service provider?
Let us explore some of the use cases where organizations would want to migrate data between the two clouds, whether it’s migration from AWS to Azure or an Azure to AWS migration. We’ll also look at how NetApp’s Cloud Volumes ONTAP can be a key part to a cloud migration strategy for moving between the AWS and Azure clouds.
Why Move from One Cloud to Another?
There are a number of reasons why a company would move from AWS to Azure or vice versa. In fact, before beginning a migration, some organizations looking ahead even require a transition-out plan as part of their cloud adoption strategies in case they ever need to move from their first cloud of choice.
Reasons why users in Azure or AWS would want to switch to the competing cloud service provider include:
1. Changes in the terms and conditions: Initial cloud adoption for enterprises often depends on a unique value proposition offered by a vendor. However, changes in the terms and conditions of a cloud service provider over time could lead to cloud lock-in concerns for organizations.
2. Application portability: Another example of cloud lock-in possibility is the use of heterogeneous platforms used by different cloud vendors which can affect application portability. For example, workloads that use AWS community-contributed Amazon Machine Images (AMIs) or applications configured to make Amazon S3 API calls might limit the ability for enterprises to use other services outside of AWS. In such a case, it might be desirable to migrate out. Another lock-in example is how Azure Site Recovery provides automated mechanisms for moving workloads from AWS to Azure, but requires multiple complex manual steps or third-party tools to migrate in the opposite direction.
3. Contract renewal: Organizations often reevaluate hosting options during the contract renewal period to explore differentiating features offered by competing service providers. With new products and features being introduced by cloud service providers, customers have more choices than ever before to choose an optimal hosting platform for their applications.
4. Cost-benefits: Services offered at premium rates by one service provider could be available at competitive rates with a different provider. For example, Azure Hybrid Benefit along with reserved instances can provide up to 80% cost saving and offers a great value proposition for organizations with pre-existing investments in Microsoft licenses. AWS, on the other hand, provides Microsoft Licensing on AWS, in which customers can use their Microsoft licenses with or without Software Assurance to reduce cloud hosting charges.
5. Compliance standards: The compliance standards to be met for hosting data and application with a cloud service provider or on-premises varies across different industry sectors. Any instance of non-compliance flagged during an audit could lead to re-hosting or migration of application/data to a compliant platform.
6. Data consolidation: In hybrid cloud architectures, a company’s data could exist across public/private clouds or on-premises deployments. Consolidation of data and seamless management is important for optimizing the spend on data storage and operations. One example of this is in the case of M&A (Mergers & acquisitions), where companies with different platforms need to consolidate.
Cloud Migration Challenges between AWS and Azure
Data is the nexus of enterprise IT, and migration from AWS to Azure and vice versa is one of the most challenging aspects when implementing multicloud architectures. Let’s look at some of the challenges.1. Data Migration: The fact that AWS and Azure use proprietary storage offerings and APIs make the data migration process complex. Leveraging third party tools for data transfer could lead to integration challenges as both the platforms use diverse technologies in the backend. And the entire process of transitioning between the two clouds may not be a feasible option for business-critical applications due to time and cost constraints involved.
2. Secure Data Transfer: Secure transfer of data between AWS and Azure should be done using a process that meets industry-specific governance and compliance standards. Direct download and upload of data can lead to security concerns as the data at rest and in transit should always be encrypted. While Azure Site Recovery offers a feasible solution for large scale secure migration between AWS and Azure, it requires additional infrastructure to be set up in AWS, which may not be feasible in cost-sensitive environments.
3. Access Control Privileges: When data is migrated between AWS and Azure platforms, administrators need to ensure that consistent data access and protection policies are applied in the destination as well. Security and access control are configured using different sets of tools and policies in AWS and Azure. While AWS depends on IAM user policies and resource-based policies for Amazon S3 access, Azure storage uses RBAC assigned to Azure AD users. Hence, redesign and reconfiguration of the entire system might be required to maintain the same level of security after migration. Management of data across AWS and Azure environments using unified tools and interfaces is also a major challenge.
4. Other Challenges: There are a few other additional challenges to the migration process between platforms. It will be necessary to find a way to evaluate the costs and calculate the differences. You’ll also need a way to measure and maintain the same or acceptable performance and SLAs of different devices, instances, VMs, storage types, etc. on the new platform.
Addressing Cloud Transition Challenges with NetApp
NetApp Cloud Volumes ONTAP provides comprehensive data management technology for cloud and hybrid deployments that can seamlessly access data no matter where it is hosted, whether it’s AWS, Azure, or on-premises. This is relevant in data migration scenarios where the focus is moving to the right platform with the least amount of operational hassles.
Cloud Volumes ONTAP’s unified approach with visibility and management capabilities across diverse platforms addresses many of the data migration challenges discussed earlier. It is also helpful in transitioning out scenarios where customers might want to move data back from cloud to on-premises for specific use cases.
Moving with Cloud Volumes ONTAP
When performing a data migration from AWS to Azure or from Azure to AWS, enterprises can rely on Cloud Volumes ONTAP (formerly ONTAP Cloud). Cloud Volumes ONTAP is built on AWS storage or Azure storage to provide CIFS/NFS/iSCSI-based services for target workloads. Data-optimization capabilities such as thin provisioning, data deduplication, data compression, data tiering to Amazon S3, data tiering to Azure Blob, and data cloning are built into Cloud Volumes ONTAP to help manage storage and cut the costs of using native cloud offerings.SnapMirror® data replication technology provides enterprise class data migration and synchronization capabilities, and as such is one of the key features in play when moving data between AWS and Azure. It can be used for replicating data between different NetApp systems, thus aiding rapid migration of data between systems deployed on-premises and as well as in the different public cloud platforms. It’s also a critical part of a DR and backup solution.
Cloud Sync: NetApp’s Cloud Sync offers effective data migration and synchronization service between NFS/CIFS formats on-premises or in the cloud, Amazon S3, Amazon EFS, Azure Blob or IBM Object storage. It can be used for initial cloud onboarding, migration and synchronization of data across hybrid or multicloud environments, and for our topic of moving between AWS and Azure and vice versa.
Conclusion
AWS and Azure are the cloud service providers of choice for many enterprises. However, at some point after an initial Azure or AWS cloud migration, organizations may want to switch between service providers and perform a migration from AWS to Azure or from Azure to AWS. This can be due to many reasons, such as cloud lock-in, contract renewal, compliance requirements, and other use cases we’ve discussed in this blog.
Flexibility of tools and solutions that can be used across both AWS and Azure platform are crucial for a hassle-free migration experience with minimal time and effort. NetApp helps in faster, secure and easier migration of data between cloud service providers. If you want a better way to move between AWS and Azure, try Cloud Volumes ONTAP.
