Migrating Data from MySQL for PCF v1 to v2
Page last updated:
The MySQL for PCF v1 tile has been deprecated. Although Spring Cloud Services v2.0 supports MySQL for PCF v1, Pivotal recommends that operators now switch to MySQL for PCF v2 for use with Spring Cloud Services. See below for information about migrating your installation of Pivotal Spring Cloud Services from use of the MySQL for PCF v1 tile.
Note: Ops Manager administrators can use Role-Based Access Control (RBAC) to manage which operators can make deployment changes, view credentials, and manage user roles in Ops Manager. Therefore, your role permissions might not allow you to perform every procedure in this operator guide. For more information about roles in Ops Manager, see Understand Roles in Ops Manager.
Important: Migration of MySQL for PCF service instances will incur downtime for users of Spring Cloud Services (during the migration, the Spring Cloud Services service broker cannot service requests). Be sure to take this into account when planning the migration.
system org and
p-spring-cloud-services space, the Spring Cloud Services broker uses one (1) MySQL service instance, called spring-cloud-broker-db, to store information about Spring Cloud Services service instances.
Install the MySQL for PCF v2 tile.
Following the instructions in Migrating Data from MySQL for PCF v1 to v2, migrate the Spring Cloud Services broker’s data to a MySQL for PCF v2 service instance. Pivotal recommends using a small plan (such as the provided
db-smallplan) to create a MySQL for PCF v2 service instance for use by the Spring Cloud Services service broker.
Use the Service Instances dashboard to verify that the migration succeeded.
Return to the Installation Dashboard.
If you are using Ops Manager v2.3 or later, click Review Pending Changes. For more information about this Ops Manager page, see Reviewing Pending Product Changes.
Click Apply Changes.
The Spring Cloud Services service broker will now use MySQL for PCF v2 to store service instance information.