There are various methods to migrate SQL Server databases from Microsoft Azure to Amazon Relational Database Service (Amazon RDS) for SQL Server. For scenarios such as moving SQL Server hosted on an Azure virtual machine to Amazon RDS for SQL Server or running SQL on Amazon Elastic Compute Cloud (Amazon EC2), AWS Database Migration Service (AWS DMS) can be utilized. However, when it comes to migrating Azure SQL databases, which do not support change data capture (CDC), a partner solution called CloudBasic is recommended for Amazon RDS for SQL Server read replicas and disaster recovery. In addition to facilitating migration, CloudBasic can be employed for deploying and testing cross-Region Amazon RDS for SQL Server disaster recovery in an AWS environment (prior to the actual migration cutover). You can find CloudBasic available on the AWS Marketplace.
In this article, we explore a solution using CloudBasic alongside other AWS services to enable a smooth, near-zero-downtime migration of Azure SQL databases into Amazon RDS for SQL Server. This solution also provides an option for fully automated cross-Region disaster recovery for Amazon RDS for SQL Server. The migration strategy is pertinent for the following scenarios:
- Moving databases from an Azure SQL virtual machine to Amazon RDS for SQL Server or SQL on Amazon EC2.
- Migrating Azure SQL databases or an elastic pool to Amazon RDS for SQL Server or SQL on Amazon EC2.
All SQL Server editions in Amazon RDS, including SQL Server Enterprise, Standard, and Web, are supported. Furthermore, CloudBasic ensures a seamless transition between SQL Server versions and editions. Example use cases include:
- Modernization – Upgrading from SQL Server Enterprise 2012 on Azure to the latest SQL Server Enterprise 2019 on Amazon RDS.
- TCO Reduction – Downgrade from SQL Server Enterprise on Azure to SQL Server Standard on Amazon RDS while deploying multiple in-Region and cross-Region read replicas.
Additionally, you can orchestrate a fully automated cutover from Azure to AWS and fully automated cross-Region disaster recovery within AWS by integrating CloudBasic with other AWS services, such as AWS Lambda and Amazon Route 53 (chained Azure[Region]-AWS[Region A] – AWS[Region B] replication), before executing the final cutover from Azure to AWS. When you’re prepared, you can transition to AWS by performing a planned failover. At the time of cutover to the primary AWS [Region A], the fully automated AWS cross-Region solution (AWS[Region A] – AWS[Region B]) will be fully operational.
Solution Overview
The following diagram illustrates the solution architecture.
CloudBasic is a cloud-native solution, launched into your Amazon Virtual Private Cloud (Amazon VPC). You will manage CloudBasic using its web console and API similarly to any other AWS service. The following screenshot displays the read replicas in the CloudBasic console.
Configuring Migration and Cross-Region RDS SQL Server Disaster Recovery with CloudBasic
You can quickly set up new migration and cross-Region read replicas from any version or edition of SQL Server in Azure to any version or edition of SQL Server in AWS, typically without needing advanced options or custom scripts. For complex migration and disaster recovery scenarios, advanced configuration options and scripting capabilities are available in the advanced section of the CloudBasic console.
CloudBasic automatically manages necessary schema conversions, addresses SQL Server version and edition incompatibilities, and creates SQL Server read replicas in Amazon RDS for SQL Server or Amazon EC2 automatically. The following screenshot illustrates a replication job’s connection configuration on the CloudBasic console.
For migrating Azure SQL databases that do not support CDC, CloudBasic defaults the change tracking method to Change Tracking. Other tracking methods can be employed in the cross-Region disaster recovery aspect of the architecture.
The following screenshot displays the configuration of a replication job in CloudBasic using the Change Tracking method.
For continuous replication to function, all tables in the source database must possess primary keys (PKs) or unique indexes. Before starting continuous replication, the Quick Setup wizard assesses all tables and identifies those without PKs or unique indexes. At this point, you can either create PKs for those tables or opt to proceed as is. However, after the initial replication and seeding are completed, tables lacking PKs or unique indexes will be disregarded for continuous data replication.
Following the initial database seeding, the replication job transitions to continuous change tracking with a connection pool defaulted to an automatically determined size based on your CloudBasic instance size and database size. To further optimize the replication process and accommodate larger databases with high transaction rates, you can adjust the connection pool size to minimize latency or lessen the workload on the primary.
Ongoing monitoring of migration pending data and schema changes is facilitated by runtime reports, logs, and system alerts. The following screenshot highlights the replica count of the source and target datasets and the timestamp of the last sync. The pending changes column indicates the number of records yet to be replicated.
Database schemas are monitored for changes. New tables, stored procedures, views, functions, constraints, foreign keys, new columns, altered columns, and more are all replicated.
Summary
Utilizing CloudBasic’s cloud-native Amazon RDS for SQL Server disaster recovery solution for migrating from Azure SQL to AWS offers significant advantages over traditional migration tools. With CloudBasic, the primary focus is on achieving intercloud disaster recovery at the database level by creating Amazon RDS for SQL Server read replicas. This method permits extended testing against the actual AWS environment over a longer timeframe. You can transition whenever you’re ready by executing a planned disaster recovery failover.
To deploy CloudBasic, visit the AWS Marketplace for deployment instructions, and see the CloudBasic deployment guide. Furthermore, you can utilize CloudBasic to set up cross-Region RDS SQL Server read replicas for disaster recovery within the AWS framework. For more insights, check out this authoritative source on the topic, as well as this excellent resource for additional guidance.
Location: Amazon IXD – VGT2, 6401 E Howdy Wells Ave, Las Vegas, NV 89115
Leave a Reply