This topic explains how to upgrade the VMware SQL with MySQL for Tanzu Application Service service and existing service instances. It also explains the service interruptions that can result from service changes and upgrades and from failures at the process, VM, and IaaS level.

For product versions and upgrade paths, see Upgrade Planner.

Upgrade VMware Tanzu for MySQL

To upgrade the VMware Tanzu for MySQL service, follow the Ops Manager process that you use to install the service for the first time. Your configuration settings migrate to the new version automatically.

To upgrade VMware Tanzu for MySQL:

  1. Review the Release Notes for the version you are upgrading to.

  2. Download the Ubuntu Jammy stemcell from Broadcom Support, and import it into the Ops Manager Stemcell Library. For instructions, see Verify stemcell version and apply all changes.

  3. Download the desired version of the product from Broadcom Support.

  4. Go to the Ops Manager Installation Dashboard and click Import a Product to upload the product file.

  5. Under the Import a Product button, click + next to VMware Tanzu for MySQL. This adds the tile to your staging area.

  6. Click the newly-added VMware Tanzu for MySQL tile to review its configuration panes. Click Save on any panes where you make changes.

    To decrease the runtime for service instance upgrades, configure the upgrade-all-service-instances errand in the tile. For instructions about configuring this errand, see Configure service instance upgrades.

  7. (Optional) If you want developers to individually upgrade service instances, go to to the Errands pane and select Off for Upgrade all On-demand MySQL Service Instances.

    By default, the upgrade-all-service-instances errand runs after each upgrade. For more information, see About individual service instance upgrades.

    Important

    As of VMware Tanzu for MySQL v3.2.0, only MySQL 8.0 is supported. When upgrading, you must update any plans previously configured with a “MySQL Default Version” of “5.7”, and specify “8.0”. On upgrade, all previously created MySQL v5.7 service instances are updated to MySQL v8.0, either when the platform operator runs the upgrade-all-service-instances errand or when the developer individually upgrades a service instance by using the cf CLI.

  8. Go to Ops Manager Dashboard > Review Pending Changes. For more information about this Ops Manager page, see Reviewing pending product changes.

  9. For the VMware Tanzu for MySQL tile, enable the Register On-demand MySQL Broker errand if the errand is not already enabled.

  10. Click Apply Changes.

Upgrading the VMware Tanzu for MySQL service and service instances can temporarily interrupt the service. For more information, see Service interruptions.

About individual service instance upgrades

To allow developers to upgrade individual service instances, you must use VMware Tanzu Application Service for VMs v2.7 or later.

After you upgrade the VMware Tanzu for MySQL tile, existing service instances must be upgraded to use the latest version of the tile. Developers cannot create new bindings to service instances that have not been upgraded.

To decrease runtime for service instance upgrades, developers can individually upgrade on-demand service instances using the Cloud Foundry Command Line Interface (cf CLI). Developers can upgrade individual service instances by following the procedure in Upgrade an Individual Service Instance.

Developers can only upgrade individual service instances if you deactivate the upgrade-all-service-instances errand when upgrading the tile. By default, VMware Tanzu for MySQL runs this errand when you upgrade the tile. However, this operation can take a long time. You must also ensure that the register-broker errand is run during upgrades. For more information about the register broker errand, see register-broker.

Upgrading from MySQL 5.7 to 8.0

After upgrading to VMware Tanzu for MySQL v3.x, you can upgrade your service instances from Percona 5.7 to Percona 8.0. Percona 8.0 includes significant changes. VMware Tanzu for MySQL v3.x addresses the major upgrade incompatibilities, but in some cases, client applications that are bound to a service instance that uses Percona v5.7 might have compatibility issues when the service instance is upgraded to use Percona 8.0.

To better understand the possible compatibility issues, consider the following options:

  • Read the compatibility documentation from Percona. This provides details on where application SQL might fail to execute correctly.
  • Consider making a backup of the current (Percona 5.7) database and restoring from the backup to a new 8.0 service instance in a non-production environment. See Backup and Restore. Then connect the relevant application and execute the appropriate tests for functionality and performance, if available.
  • Percona has a set of compatibility testing tools that can be used to run existing queries against an upgraded schema. This process provides a mechanism to thoroughly test the application against the upgraded database. It can highlight potential incompatibility errors and performance changes.
  • MySQL also offers a comprehensive upgrade guide with a special section highlighting best practices.
Note

These tools are an optional source of feedback that can provide additional confidence while evaluating an upgrade from MySQL 5.7 to 8.0. No individual tool can guarantee a successful upgrade. It is your responsibility to fully review your unique database configuration.

About MySQL 5.7 to 8.0 upgrades

Tile versions 3.2 and later only support MySQL 8.0. The version drop-down menu only lists 8.0, but may show a blank version on plans previously configured for MySQL 5.7. You must select 8.0 from the drop-down menu before you can update these plans’ service instances. This forced manual selection prevents you from accidentally upgrading your users from 5.7 to 8.0.

MySQL 8.0 version dropdown

Note

If you change a plan’s MySQL version from 5.7 to 8.0, any subsequent updates to a service instance created with that plan upgrades that instance’s MySQL from 5.7 to 8.0. This includes both batch updates to all service instances through the upgrade-all-service-instances errand, and also individual service instance updates by a cf update-service --upgrade command. Service instances may only be upgraded, downgrades are not supported.

Important When upgrading a highly available (HA) cluster from MySQL 5.7 to MySQL 8.0, VMware recommends that you first validate the HA cluster’s health by running the mysql-diag tool. To run mysql-diag, see Running mysql-diag. (A “highly available (HA) cluster” refers to any service instance created from a tile plan configured with the “HA cluster” topology.) If mysql-diag reports HA cluster is unhealthy, follow mysql-diag’s recommendations to bring the cluster to a healthy state before upgrading the cluster to MySQL 8.0.

Service interruptions

Service changes, upgrades, and failures at the process, VM, and IaaS level can cause outages in the VMware Tanzu for MySQL service.

Read this section if:

  • You are planning an upgrade.
  • You are experiencing a service interruption and are wondering why.
  • You are planning to update or change a service instance and want to know if it might cause a service interruption.

Stemcell or service update

An operator updates a stemcell version or their version of VMware Tanzu for MySQL.

  • Impact: Apps lose access to the MySQL service while Ops Manager updates the service instance they are bound to. The service resumes within 10–15 minutes.
  • Required Actions: None. If the update deploys successfully, apps reconnect automatically.

Plan change

A developer changes their service instance to provide a different service plan, using cf update-service or Apps Manager.

For example:

cf update-service SERVICE-INSTANCE -p NEW-PLAN
  • Impact: Apps lose access to the MySQL service while Ops Manager updates the service instance they are bound to. The service resumes within 10–15 minutes.
  • Required Actions: None. If the plan change deploys successfully, the apps reconnect automatically.

Service broker deployments

Automated backups are not taken during service broker deployments.

When the service broker is unavailable, such as during upgrades and re-deployments, automated backups fail. Automated backups resume according to schedule when the service broker is online again.

For general information about backups, see Backing up and restoring VMware SQL with MySQL for Tanzu Application Service and Configuring automated backups.

check-circle-line exclamation-circle-line close-line
Scroll to top icon