Upgrading to Pivotal Scheduler v1.2
This topic explains how to upgrade Pivotal Scheduler. It also explains how Pivotal Scheduler v1.2 automatically migrates data from a MySQL for Pivotal Platform v1 database to a MySQL for Pivotal Platform v2 database. MySQL for Pivotal Platform v1 has reached its End of Availability. This migration removes dependency on MySQL for PCF v1.
Pivotal recommends backing up your MySQL for Pivotal Platform database before installing Pivotal Scheduler v1.2. This is because upgrading your Pivotal Scheduler installation from v1.1 to v1.2 triggers automatic migration of your data to a MySQL for Pivotal Platform v2.x database.
To back up your MySQL for Pivotal Platform database, do one of the following:
- If you are backing up a MySQL for PCF v1.x database, see Perform Manual Backup.
- If you are backing up a MySQL for Pivotal Platform v2.x database, see Manual Backup.
Pivotal Scheduler v1.2.3 and later requires a Xenial stemcell. If you are using any of the following BOSH add-ons with your PCF deployment, you must update the add-on definition to include the Xenial stemcell before you deploy Pivotal Scheduler v1.2.3:
- File Integrity Monitoring for PCF Add-on. For update instructions, see Updating FIM Add-on for PCF to Run with Xenial Stemcells.
- ClamAV for PCF Add-on. For update instructions, see Updating ClamAV Add-on for PCF to Run with Xenial Stemcells.
- IPsec for PCF Add-on. For update instructions, see Updating IPsec Add-on for PCF to Run with Xenial Stemcells.
During the upgrade, Pivotal Scheduler automatically migrates your data from MySQL for PCF v1.x to MySQL for Pivotal Platform v2.x. Pivotal Scheduler detects your MySQL for PCF v1.x service binding and automatically migrates the MySQL for PCF v1.x database instance to a MySQL for Pivotal Platform v2.x instance.
The errand migrates the database and executes smoke tests. When the migration has completed successfully, the errand removes the service binding to the MySQL for PCF v1.x instance.
To upgrade from Scheduler for PCF v1.1 to v1.2, do the following:
Install MySQL for Pivotal Platform v2.3 or later in the same PCF environment as your MySQL for PCF v1.x service instance. In the Security pane in the MySQL for Pivotal Platform v2.x tile, set TLS Options to Optional or Not Configured. For information about installing MySQL for Pivotal Platform v2.x, see Installing and Configuring MySQL for Pivotal Platform.
Add the new database details to the Scheduler Configuration. Update the configuration for the Pivotal Scheduler tile under Scheduler Configuration > Database Source to include the MySQL for Pivotal Platform service name and the desired service plan name in order to trigger the migration. For example,
db-small. MySQL for PCF plans can be found in the settings for the MySQL tile or by checking the output of
plansusing the cf cli.
Upgrade Pivotal Scheduler to v1.2 with all errands enabled. For general information about upgrading a tile, see Upgrading PCF Products.
Note: All Post-Deploy Errands must be enabled to migrate from a MySQL for PCF v1.x database to MySQL for Pivotal Platform v2.x database. These settings are in the Pivotal Scheduler Errands pane of the Pivotal Scheduler tile.