Skip to content

Commit ae36cb8

Browse files
author
Sudheesh Narayanaswamy
committed
What new Jan 2022
1 parent 32dfcd5 commit ae36cb8

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

articles/mysql/flexible-server/whats-new.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,19 @@ ms.date: 10/12/2021
1616
[Azure Database for MySQL - Flexible Server](./overview.md) is a deployment mode that's designed to provide more granular control and flexibility over database management functions and configuration settings than does the Single Server deployment mode. The service currently supports community version of MySQL 5.7 and 8.0.
1717

1818
This article summarizes new releases and features in Azure Database for MySQL - Flexible Server beginning in January 2021. Listings appear in reverse chronological order, with the most recent updates first.
19+
## January 2022
20+
- **Migrate from locally redundant backup storage to geo-redundant backup storage for existing flexible server**
21+
22+
Azure Database for MySQL - Flexible Server now provides the added flexibility to migrate to geo-redundant backup storage from locally redundant backup storage post server-create to provide higher data resiliency. Enabling geo-redundancy via the server's Compute + Storage blade empowers customers to recover their existing flexible servers from a geographic disaster or regional failure when they can’t access the server in the primary region. With this feature enabled for their existing servers, customers can perform geo-restore and deploy a new server to the geo-paired Azure region leveraging the original server’s latest available geo-redundant backup.
23+
24+
- **Bug fixes**
25+
26+
27+
Restart workflow struck issue with servers with HA and Geo-redundant backup option enabled is fixed.
28+
29+
- **Known issues**
30+
31+
When you are using ARM templates for provisioning or configuration changes for HA enabled servers, if a single deployment is made to enable/disable HA and along with other server properties like backup redundancy, storage etc. then deployment would fail. You can mitigate it by submit the deployment request separately for to enable\disable and configuration changes. You would not have issue with Portal or Azure cli as these are request already separated.
1932

2033
## November 2021
2134
- **General Availability of Azure Database for MySQL - Flexible Server**
@@ -41,7 +54,7 @@ This article summarizes new releases and features in Azure Database for MySQL -
4154

4255
- **Known issues**
4356

44-
On servers where we have HA and Geo-redundant backup option enabled, we found an rare issue encountered by a race condition which blocks the restart of the standby server to finish. As a result of this issue, when you failover the HA enabled Azure database for MySQL - Flexible server MySQL Instance may get stuck in restarting state for a long time. The fix will be deployed to the production in the next deployment cycle.
57+
On servers where we have HA and Geo-redundant backup option enabled, we found an rare issue encountered by a race condition which blocks the restart of the standby server to finish. As a result of this issue, when you failover the HA enabled Azure database for MySQL - Flexible server MySQL Instance may get stuck in restarting state for a long time. The fix will be deployed to the production in the next deployment cycle.
4558

4659
## October 2021
4760

0 commit comments

Comments
 (0)