A
Aditi_Gupta
Azure Database for MySQL - Single Server is scheduled for retirement by September 16, 2024.
Over the past two years, we've sent recurring notifications (via public channels such as Azure Update and blog posts as well as direct outreach through customer emails, product pages, and Azure Portal banners) about the need to complete migration to Azure Database for MySQL - Flexible Server before this date. As part of our ongoing communication and assistance to migrate customers safely to their new environment, this blog post provides more information on the customer experience for any workloads that remain in production beginning 16th September 2024.
Running a Single Server instance after the sunset date would be a security risk, as no security or bug fix maintenance will occur 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, we will force migrate your Single Server instance, along with its data files, to an appropriate Flexible Server instance in a series of phases. This could lead to server unavailability for servers with security and networking features.
Beginning on 17th September, we will stop non-responsive servers with an auto-migration scheduled but missing mandatory inputs. We will also stop servers with a low TLS version, low client driver version, and service endpoints. You'll then need to navigate to the Azure portal, acknowledge the migration actions, and restart your server. Be sure that you complete the action required to proceed with auto-migration to avoid the need for an involuntary forced-migration, which could lead to server unavailability as only limited features can be migrated.
If you currently have an Azure Database for MySQL single server in production, we strongly recommend that you migrate the instance to Azure Database for MySQL - Flexible Server free of charge before Sep 16th 2024 using one of the following migration tooling options.
You can leverage the Azure Database for MySQL Import CLI (General Availability) to migrate your Azure Database for MySQL single servers 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. This process copies the following properties and files from the single server 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...
Over the past two years, we've sent recurring notifications (via public channels such as Azure Update and blog posts as well as direct outreach through customer emails, product pages, and Azure Portal banners) about the need to complete migration to Azure Database for MySQL - Flexible Server before this date. As part of our ongoing communication and assistance to migrate customers safely to their new environment, this blog post provides more information on the customer experience for any workloads that remain in production beginning 16th September 2024.
Running a Single Server instance after the sunset date would be a security risk, as no security or bug fix maintenance will occur 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, we will force migrate your Single Server instance, along with its data files, to an appropriate Flexible Server instance in a series of phases. This could lead to server unavailability for servers with security and networking features.
Beginning on 17th September, we will stop non-responsive servers with an auto-migration scheduled but missing mandatory inputs. We will also stop servers with a low TLS version, low client driver version, and service endpoints. You'll then need to navigate to the Azure portal, acknowledge the migration actions, and restart your server. Be sure that you complete the action required to proceed with auto-migration to avoid the need for an involuntary forced-migration, which could lead to server unavailability as only limited features can be migrated.
If you currently have an Azure Database for MySQL single server in production, we strongly recommend that you migrate the instance to Azure Database for MySQL - Flexible Server free of charge before Sep 16th 2024 using one of the following migration tooling options.
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 servers 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. This process copies the following properties and files from the single server 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...