This topic tells you how to migrate from a Google Storage Bucket instance of the GCP Service Broker for VMware Tanzu tile to the Tanzu Cloud Service Broker for GCP tile.

About Migrating a Google Storage Bucket Instance

Because the GCP Service Broker for VMware Tanzu (hereafter referred to as the legacy broker) tile is out of support, you must move from Google Storage Bucket instances that were created by the legacy broker over to Cloud Service Broker for GCP.

The Cloud Service Broker for GCP plans are configurable. When migrating, examine the configuration of the plans in use with the legacy broker and create matching plans in Cloud Service Broker for GCP.

You can use any compatible migration tool for migrating between Google Storage Buckets.

Matching Configuration

Both the legacy broker and Cloud Service Broker for GCP allow you to customize service plans. Create plans in Cloud Service Broker for GCP that match the plans used in the legacy broker. It might be useful to create a test service instance and compare the properties in the GCP console. For how to configure plans, see Configure Services with Cloud Service Broker for GCP.

Migrating Data

You might want to migrate data from instances created with the legacy broker to instances created with Cloud Service Broker for GCP.

Migration of data might incur app downtime. The amount of downtime depends on the method chosen.

There are several options for performing a Google Storage Bucket migration, including:

• The gcloud storage cp –recursive command
• The GCP Storage Transfer Service
• Manual data migration
• Options available from other vendors

For more information about the data migration process, see the documentation for the option that you choose.

In general, to migrate data:

1. Create a backup of the Google Storage Bucket instance.
2. Create a Google Storage Bucket instance using Cloud Service Broker for GCP.
3. Replicate the data from a legacy broker Google Storage Bucket instance into the newly created instance.
4. Unbind apps from the legacy broker Google Storage Bucket instance and bind them to the newly created instance.
5. (Optional) After migration is complete, delete the legacy broker Google Storage Bucket instance.

Migrate Data from a Legacy Google Storage Bucket Instance

Important The binding credentials format was changed. You must update the consuming app to handle the credential property. For more information, see Binding Credentials.

The following steps have the Cloud Foundry commands necessary to use the gcloud command. To migrate data from an existing legacy Google Storage Bucket instance to Cloud Service Broker for GCP:

1. Create a backup of the legacy Google Storage Bucket instance.

2. Create a new Google Storage Bucket service instance using Cloud Service Broker for GCP.

3. Configure and run data migration by, for example, using the gcloud storage cp –recursive command. For how to configure data migration in your case, see the documentation for your chosen method.

4. Disconnect the app from the legacy service binding by running:

   cf unbind-service APP-NAME LEGACY-SERVICE-INSTANCE-NAME
   

   Where:

   • APP-NAME is the app using the Google Storage Bucket instance
   • LEGACY-SERVICE-INSTANCE-NAME is the name of the GCP Service Broker for VMware Tanzu that brokered the Google Storage Bucket instance

   For example:

   $ cf unbind-service my-app my-old-instance
   

5. Bind the app to the new service instance by running:

   cf bind-service APP-NAME NEW-SERVICE-INSTANCE-NAME -c '{"PARAMETER-NAME": "PARAMETER-VALUE"}'
   

   Where NEW-SERVICE-INSTANCE-NAME is the name of the Cloud Service Broker for GCP service instance that you created earlier.

   To learn the required parameters, see Binding Credentials.

   For example:

   $ cf bind-service my-app my-csb-gcp-bucket-instance '{"role":"storage.objectAdmin"}
   

   Because Cloud Service Broker for GCP creates new credentials at bind time, this creates new binding credentials for the app.

6. Update the app to consume the new binding credential format. You must update the consuming app to handle the credential property. For the new binding format, see Binding Credentials.

   VMware recommends reviewing all references where the legacy Google Storage bucket was used to verify that the new bucket is now being referenced.

7. Push and start the app by running:

   cf push APP-NAME
   

8. (Optional) After the migration has finished, remove the legacy service instance.