Upgrading VMware Tanzu SQL with MySQL for VMs

Note: In v2.9 and later, MySQL for VMware Tanzu is named VMware Tanzu SQL with MySQL for VMs.

Page last updated:

This topic explains how to upgrade the VMware Tanzu SQL with MySQL for VMs 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 Tanzu SQL for VMs

To upgrade the Tanzu SQL for VMs 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 Tanzu SQL for VMs:

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

  2. Download the Ubuntu Xenial stemcell from VMware Tanzu Network, 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 VMware Tanzu Network.

  4. Navigate 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 Tanzu SQL for VMs. This adds the tile to your staging area.

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

    Note: 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. If the following conditions all apply, select the Force path style access to bucket checkbox:

    • You are upgrading from v2.8.x or v2.9.0 to v2.9.1 or later.
    • You use S3-compatible storage to store backups. See Back Up to Amazon S3 or Ceph in Configuring Automated Backups.
    • The S3-compatible bucket, such as Minio, requires a path-style URL instead of a virtual hosted-style URL.

    The Force path style access to bucket checkbox is on the Backups pane. For more information, see Back Up to Amazon S3 or Ceph in Configuring Automated Backups and v2.9.1 in Release Notes.

  8. (Optional) If you want developers to individually upgrade service instances, navigate 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 below.

  9. Navigate to Ops Manager Dashboard > Review Pending Changes. For more information about this Ops Manager page, see Reviewing Pending Product Changes.

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

  11. Click Apply Changes.

Upgrading the Tanzu SQL for VMs service and service instances can temporarily interrupt the service. For more information, see Service Interruptions below.

About Individual Service Instance Upgrades

Note: For developers to be able to upgrade individual service instances, you must use VMware Tanzu Application Service for VMs v2.7 or later.

After you upgrade the Tanzu SQL for VMs 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 disable the upgrade-all-service-instances errand when upgrading the tile. By default, Tanzu SQL for VMs 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.

Service Interruptions

Service changes and upgrades and failures at the process, VM, and IaaS level can cause outages in the Tanzu SQL for VMs service, as described below.

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 Tanzu SQL for VMs.

  • Impact: Apps lose access to the MySQL service while Ops Manager updates the service instance they are bound to. The service should resume 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.

  • Impact: Apps lose access to the MySQL service while Ops Manager updates the service instance they are bound to. The service should resume within 10–15 minutes.
  • Required Actions: None. If the plan change deploys successfully, 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 redeployments, 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 Tanzu SQL with MySQL for VMs and Configuring Automated Backups.