Skip to content

Commit caa1597

Browse files
authored
Update how-to-upgrade.md
1 parent 3b0320d commit caa1597

File tree

1 file changed

+10
-5
lines changed

1 file changed

+10
-5
lines changed

articles/mysql/flexible-server/how-to-upgrade.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ This feature enables customers to perform in-place upgrades of their MySQL 5.7 s
3030
## Prerequisites
3131

3232
- Read Replicas with MySQL version 5.7 should be upgraded before Primary Server for replication to be compatible between different MySQL versions, read more on [Replication Compatibility between MySQL versions](https://dev.mysql.com/doc/mysql-replication-excerpt/8.0/en/replication-compatibility.html).
33-
- Before you upgrade your production servers, we strongly recommend you to test your application compatibility and verify your database compatibility with features [removed](https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html#mysql-nutshell-removals)/[deprecated](https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html#mysql-nutshell-deprecations) in the new MySQL version.
33+
- Before you upgrade your production servers, we **strongly recommend** you use the official Oracle [MySQL Upgrade checker tool](https://go.microsoft.com/fwlink/?linkid=2230525) to test your database schema compatibility and perform necessary regression test to verify application compatibility with features [removed](https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html#mysql-nutshell-removals)/[deprecated](https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html#mysql-nutshell-deprecations) in the new MySQL version.
3434
- Trigger [on-demand backup](./how-to-trigger-on-demand-backup.md) before you perform major version upgrade on your production server, which can be used to [rollback to version 5.7](./how-to-restore-server-portal.md) from the full on-demand backup taken.
3535

3636

@@ -137,15 +137,20 @@ To perform a major version upgrade of an Azure Database for MySQL 5.7 server to
137137
The server will be unavailable during the upgrade process, so we recommend you perform this operation during your planned maintenance window. The estimated downtime depends on the database size, storage size provisioned (IOPs provisioned), and the number of tables on the database. The upgrade time is directly proportional to the number of tables on the server. To estimate the downtime for your server environment, we recommend to first perform upgrade on restored copy of the server.
138138

139139

140-
- **When will this upgrade feature be GA?**
141-
142-
GA of this feature will be planned by December 2022. However, the feature is production ready and fully supported by Azure so you should run it with confidence in your environment. As a recommended best practice, we strongly suggest you run and test it first on a restored copy of the server so you can estimate the downtime during upgrade, and perform application compatibility test before you run it on production.
143-
144140
- **What happens to my backups after upgrade?**
145141

146142
All backups (automated/on-demand) taken before major version upgrade, when used for restoration will always restore to a server with older version (5.7).
147143
All the backups (automated/on-demand) taken after major version upgrade will restore to server with upgraded version (8.0). It's highly recommended to take on-demand backup before you perform the major version upgrade for an easy rollback.
148144

145+
- **I'm currently using Burstable SKU, does Microsoft plan to support major version upgrade for this SKU in the future?**
146+
147+
Burstable SKU is not able to support major version upgrade due to the performance limitation of this SKU.Microsoft is still working on a way to make this SKU available for major version upgrade
148+
149+
If you need to perform a major version upgrade on your Azure MySQL Flexible Server and are currently using Burstable SKU, one temporary solution would be to upgrade to General Purpose or Business Critical SKU, perform the upgrade, and then switch back to Burstable SKU.
150+
151+
Please note that upgrading to a higher SKU may involve a change in pricing and may result in increased costs for your deployment. However, since the upgrade process is not expected to take a long time, the additional costs should not be significant.
152+
153+
149154

150155
## Next steps
151156
- Learn more about [how to configure scheduled maintenance](./how-to-maintenance-portal.md) for your Azure Database for MySQL - Flexible Server.

0 commit comments

Comments
 (0)