You can upgrade the VMware SQL with MySQL for Tanzu Application Service service and existing service instances. You can also learn about 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.
To upgrade the VMware SQL with MySQL for TAS service, follow the Tanzu Operations 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 SQL with MySQL for TAS:
Review the Release Notes for the version you are upgrading to.
Download the desired version of the product from VMware Tanzu Network.
Go to the Tanzu Operations Manager Installation Dashboard and click Import a Product to upload the product file.
Under the Import a Product button, click + next to VMware SQL with MySQL for TAS. This adds the tile to your staging area.
Click the newly-added VMware SQL with MySQL for TAS 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.
(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.
Go to Tanzu Operations Manager Dashboard > Review Pending Changes. For more information about this Tanzu Operations Manager page, see Reviewing pending product changes.
For the VMware SQL with MySQL for TAS tile, enable the Registering on-demand MySQL broker errand if the errand is not already enabled.
Click Apply Changes.
Upgrading the VMware SQL with MySQL for TAS service and service instances can temporarily interrupt the service. For more information, see Service interruptions.
Important 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 SQL with MySQL for TAS 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 SQL with MySQL for TAS runs this errand when you upgrade the tile. However, this operation can take a long time. You must also ensure that the Register On Demand Service Broker errand is run during upgrades. For instructions for activating and deactivating errands, see Errands.
Service changes, upgrades, and failures at the process, VM, and IaaS level can cause outages in the VMware SQL with MySQL for TAS service.
Read this section if:
An operator updates a stemcell version or their version of VMware SQL with MySQL for TAS.
A developer changes their service instance to provide a different service plan, using
cf update-service or Apps Manager. This process is used to update Service Instances from Percona 5.7 to Percona 8.0. For example:
cf update-service SERVICE-INSTANCE -p PLAN-WITH-8.0
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.