A
Aditi_Gupta
Azure Database for MySQL - Single Server is scheduled for retirement by September 16, 2024.
We have sent recurring notifications over the past two years to complete the migration to Azure Database for MySQL Flexible Server, both via public channels such as Azure Update and blogs as well as direct outreach through customer emails, product pages, and Azure Portal banners. As part of our ongoing communication and assistance to migrate customers safely to their new environment, this blog provides more information on the customer experience for any workloads that remain in production beginning 16th September 2024.
Running the Single Server instance post sunset date would be a security risk, as there will be no security and bug fixes maintenance on the deprecated Single Server platform. To ensure our commitment towards running the managed instances on a trusted and secure platform post the sunset date, your Single Server instance, along with its data files, will be force-migrated to an appropriate Flexible Server instance in a phased manner. This could lead to server unavailability for servers with security and networking features.
Starting 17th September, non-responsive servers which have an auto-migration scheduled and have not provided mandatory inputs will be stopped. Additionally servers with low TLS version, low client driver version and service endpoints will also be stopped. You'll be required to come to the Azure portal, acknowledge the migration actions and restart your server. Ensure to complete the action required in order to proceed with auto-migration, to avoid involuntary forced-migration later which could lead to server unavailability as only limited features can be migrated.
If you currently have an Azure Database for MySQL - Single Server production server, we strongly recommend you migrate your Azure Database for MySQL - Single Server instance to the Azure Database for MySQL - Flexible Server service free of charge by using one of the following migration tooling options before Sept 16th, 2024.
You can leverage the Azure Database for MySQL Import CLI (General Availability) to migrate your Azure Database for MySQL - Single Server instances to Flexible Server using snapshot backup and restore technology with a single CLI command. Based on user inputs, this functionality will provision your target Flexible Server instance, take a backup of the source server, and then restore it to the target. It copies the following properties and files from the Single Server instance to the Flexible Server instance:
In-place auto-migration (General Availability) from Azure Database for MySQL – Single Server to Flexible Server is an in-place upgrade during a planned maintenance window for select Single Server database workloads. If you have a Single Server workload without complex features (Service endpoints/VNet Rules, Virtual network configuration, Double Infrastructure Encryption, Read Replicas) enabled, please raise an Azure support ticket to get an auto-migration scheduled at the earliest.
Azure Database Migration Service (DMS) (General Availability) is a fully managed service designed to enable seamless online and offline migration from Azure Database for MySQL - Single Server to Flexible Server. DMS supports cross-region, cross-version, cross-resource group, and cross-subscription migrations.
Take advantage of one of these options to migrate your Single Server instances to Flexible Server before Sept 16th to avoid any disruption to business continuity! Read more about the post sunset date experience here - What's happening to Azure Database for MySQL single server? | Microsoft Learn.
For more questions on Azure Database for MySQL Single Server retirement, see our Frequently Asked Questions.
Continue reading...
We have sent recurring notifications over the past two years to complete the migration to Azure Database for MySQL Flexible Server, both via public channels such as Azure Update and blogs as well as direct outreach through customer emails, product pages, and Azure Portal banners. As part of our ongoing communication and assistance to migrate customers safely to their new environment, this blog provides more information on the customer experience for any workloads that remain in production beginning 16th September 2024.
Running the Single Server instance post sunset date would be a security risk, as there will be no security and bug fixes maintenance on the deprecated Single Server platform. To ensure our commitment towards running the managed instances on a trusted and secure platform post the sunset date, your Single Server instance, along with its data files, will be force-migrated to an appropriate Flexible Server instance in a phased manner. This could lead to server unavailability for servers with security and networking features.
Starting 17th September, non-responsive servers which have an auto-migration scheduled and have not provided mandatory inputs will be stopped. Additionally servers with low TLS version, low client driver version and service endpoints will also be stopped. You'll be required to come to the Azure portal, acknowledge the migration actions and restart your server. Ensure to complete the action required in order to proceed with auto-migration, to avoid involuntary forced-migration later which could lead to server unavailability as only limited features can be migrated.
If you currently have an Azure Database for MySQL - Single Server production server, we strongly recommend you migrate your Azure Database for MySQL - Single Server instance to the Azure Database for MySQL - Flexible Server service free of charge by using one of the following migration tooling options before Sept 16th, 2024.
Azure Database for MySQL Import CLI
You can leverage the Azure Database for MySQL Import CLI (General Availability) to migrate your Azure Database for MySQL - Single Server instances to Flexible Server using snapshot backup and restore technology with a single CLI command. Based on user inputs, this functionality will provision your target Flexible Server instance, take a backup of the source server, and then restore it to the target. It copies the following properties and files from the Single Server instance to the Flexible Server instance:
- Data files
- Server parameters
- Compatible firewall rules
- Server properties such as tier, version, SKU name, storage size, location, geo-redundant backups settings, public access settings, tags, auto grow settings and backup-retention days settings
- Admin username and password
In-place auto-migration
In-place auto-migration (General Availability) from Azure Database for MySQL – Single Server to Flexible Server is an in-place upgrade during a planned maintenance window for select Single Server database workloads. If you have a Single Server workload without complex features (Service endpoints/VNet Rules, Virtual network configuration, Double Infrastructure Encryption, Read Replicas) enabled, please raise an Azure support ticket to get an auto-migration scheduled at the earliest.
Azure Database Migration Service (DMS)
Azure Database Migration Service (DMS) (General Availability) is a fully managed service designed to enable seamless online and offline migration from Azure Database for MySQL - Single Server to Flexible Server. DMS supports cross-region, cross-version, cross-resource group, and cross-subscription migrations.
Conclusion
Take advantage of one of these options to migrate your Single Server instances to Flexible Server before Sept 16th to avoid any disruption to business continuity! Read more about the post sunset date experience here - What's happening to Azure Database for MySQL single server? | Microsoft Learn.
For more questions on Azure Database for MySQL Single Server retirement, see our Frequently Asked Questions.
Continue reading...