Note: This page contains features related to Cloud SQL editions. For more information about Cloud SQL editions, seeIntroduction to Cloud SQL editions.

This page shows you how to use the private VPC peering network connectivity method of Database Migration Service to upgrade a Cloud SQL Enterprise edition instance to Cloud SQL Enterprise Plus edition. Database Migration Service creates a new Cloud SQL instance and migrates data to that instance.

Overview

Cloud SQL Enterprise Plus edition is ideal for applications that require maximum read and write performance. For more information about these improvements, seePerformance enhancements.

To enable these enhancements for your existing Cloud SQL Enterprise edition instances, you must upgrade them to Cloud SQL Enterprise Plus edition using Database Migration Service.

Before you begin

Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

Roles required to select or create a project

• Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
• Create a project: To create a project, you need the Project Creator role (roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.create permission.Learn how to grant roles.

Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

Go to project selector

Verify that billing is enabled for your Google Cloud project.

In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

Roles required to select or create a project

• Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
• Create a project: To create a project, you need the Project Creator role (roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.create permission.Learn how to grant roles.

Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

Go to project selector

Verify that billing is enabled for your Google Cloud project.

1. Enable the Database Migration Service API.

   Enable the API

2. Make sure that you have the Database Migration Admin role assigned to your user account.

   Go to IAM

Requirements

Database Migration Service offers various source database options and network connectivity methods. Different sources work better with some connectivitymethods than with others. On this page, we assume that you're using a Cloud SQL Enterprise edition instance in an environment where you can configure your network to add an inbound firewall rule. Because we can't know the specifics of your environment, we can't provide detailed steps when it comes to your networking configuration.

Retrieve information from the source instance

To upgrade a source Cloud SQL Enterprise edition instance, you must retrieve the following information:

• The instance's private IP address. You use this IP address when youcreate aconnection profile in Database Migration Service.
• The name of the VPC network that allows the Cloud SQL Enterprise Plus edition destination instanceto communicate with the Cloud SQL Enterprise edition source instance directly. You use this VPCnetwork when youcreate a migration job in Database Migration Service.

To retrieve information from the source Cloud SQL Enterprise edition instance, completethe following steps:

1. In the Google Cloud console, go to theSQL Instances page.

   Go to Cloud SQL Instances

2. Click your source instance.
3. In theConnect to this instance section, clickCopy to clipboard in thePrivate IP address field.
4. At the top of the page, clickEdit.
5. Expand theConnections section.
6. In theAssociated networking section, make a note of the name of the VPC network that appears in theNetwork field.

Create a connection profile

A connection profile contains information about the source Cloud SQL Enterprise edition database. Database Migration Service uses the information in the connection profile to migrate data from your source database to the destination Cloud SQL Enterprise Plus edition instance.

To create a connection profile, complete the following steps:

1. In the Google Cloud console, go to theConnection profiles page in Database Migration Service.

   Go to Connection profiles

2. ClickCreate profile.

3. From theDatabase engine drop-down list, selectCloud SQL for MySQL.

4. From theCloud SQL instance drop-down list, select the name of your Cloud SQL Enterprise edition instance.

   Note: Cloud SQL generates the connection profile name and connection profile ID automatically with information about your source instance. We recommend that you don't change these values.

5. In theHostname or IP address field, replace the value with the private IPaddress that you copied inRetrieve information from the source Cloud SQL Enterprise edition instance.

6. To authenticate to your source instance, enter a username and password.

   Note: Cloud SQL populates thePort field automatically with information about your source instance. If this field is empty, then enter the appropriate port number.

7. Select the region where you want to save the connection profile.

   Note: Connection profiles, like all resources, are saved in a region. Region selection doesn't affect which migration jobs can use connection profiles, or which regions can connect to the data location. But region selection can affect availability in the case of regional downtime.

8. If you want to encrypt your data, then enableSSL/TLS encryption for the connection between the source and destination databases. Otherwise keep the default value ofNone.

9. ClickCreate.

Create a migration job

Database Migration Service uses migration jobs to migrate data from your source Cloud SQL Enterprise edition database instance to the destination Cloud SQL Enterprise Plus edition instance.

Creating a migration job includes the following steps:

• Defining settings for the job.
• Selecting the connection profile that you created for your source Cloud SQL Enterprise edition database. This is yoursource connection profile.
• Defining settings for the destination Cloud SQL Enterprise Plus edition instance.
• Setting up connectivity between the source and destination database instances.
• Testing the migration job to ensure that the connection information that you provided for the job is valid.

Define settings for the migration job

1. In the Google Cloud console, go to theMigration jobs page in Database Migration Service.

   Go to Migration jobs

2. ClickCreate migration job.

3. In theMigration job name field, enter a name for the migration job, such asMy Migration Job.

4. From theSource database engine drop-down list, selectCloud SQL for MySQL. Database Migration Service selects theDestination database engine automatically.

5. Select the destination region where the Cloud SQL Enterprise Plus edition instance is created.

6. From theMigration job type drop-down list, selectContinuous because you want ongoing changes in your source Cloud SQL Enterprise edition database to be migrated to the destination Cloud SQL Enterprise Plus edition instance.

7. Review the required prerequisites that are generated automatically to reflect how the environment must be prepared for a migration job. These prerequisites can include how to configure the source Cloud SQL Enterprise edition database and how to connect it to the destination Cloud SQL Enterprise Plus edition instance.

   It's recommended to complete these prerequisites at this step, but you can complete them at any time before you test or start your migration job.

8. ClickSave & continue.

Specify information about the source connection profile

1. From theSelect source connection profile drop-down list, select the connection profile that you created.

2. ClickSave & continue.

Define settings for the destination Cloud SQL Enterprise Plus edition instance

1. In thePassword field, enter an alphanumeric password for the destination Cloud SQL Enterprise Plus edition instance. This is the password for theroot administrator account in the instance.

2. From theDatabase version drop-down list, select the destination instance from the listof supported Cloud SQL versions for the specified database engine.

3. SelectEnterprise Plus.

4. From theChoose region and zone section, select the desired Google Cloud zone for the newCloud SQL Enterprise Plus edition instance (or leave asAny).

5. Select thePrivate IP checkbox.

6. From theVPC drop-down list, select the VPC network that you noted inRetrieve information from the source Cloud SQL Enterprise edition instance.

7. Select the machine shape for the Cloud SQL Enterprise Plus edition instance. The disk size must be equal to or greater than the source database size.

8. Define the storage type and storage capacity for the Cloud SQL instance.

9. To create the new instance, clickCreate & Continue.

10. In the dialog that appears, clickCreate destination & continue.Creating the instance may take several minutes to complete.

    Important: This procedure creates a Cloud SQL Enterprise Plus edition instance. You're charged according to the configuration that you select.

Set up connectivity

1. Choose how you'd like to use to establish connectivity between the source Cloud SQL Enterprise edition and destination Cloud SQL Enterprise Plus edition databases. For this procedure, use theConnectivity method drop-down list to selectSource and destination are using private IP.
2. From theVPC drop-down list, select the VPC network where your source Cloud SQL Enterprise edition instance resides. This is the VPC network that you noted inRetrieve information from the source Cloud SQL Enterprise edition instance.
3. ClickConfigure & continue.

Test, create, and start the migration job

1. Review the settings that you chose for the migration job.

2. Verify that the source has been configuredcorrectly, that the source Cloud SQL Enterprise edition and destination Cloud SQL Enterprise Plus edition instances are able to communicatewith each other, and that the migration job is valid:

   1. ClickTest job.

   2. Verify that you see theYour migration job test was successful! status.

   If the test fails, then you can address the problem in the appropriate part ofthe flow, and return to re-test.

3. To create the migration job and start it immediately, clickCreate & start job.

4. In the dialog that appears, clickCreate & start.

5. In theMigration jobs page, verify that your migration job has a status ofStarting.

6. After a few minutes, confirm that the status changes toRunning.

Verify the migration job

To confirm that Database Migration Service used the migration job to migrate data from your source Cloud SQL Enterprise edition database instance to the destination Cloud SQL Enterprise Plus edition database instance, complete the following steps:

1. In the Google Cloud console, go to theSQL Instances page.

   Go to Cloud SQL Instances

2. Click the read replica entry of your migration job.

   Note: Make sure that the Cloud SQL edition for this entry isEnterprise Plus, and notEnterprise.

3. Click theActivate Cloud Shell icon that appears next to theSearch field.

4. At the prompt, to connect to the destination Cloud SQL Enterprise Plus edition database instance, use thegcloud sql connect command.

   gcloudsqlconnectDESTINATION_INSTANCE_NAME--user=root

   ReplaceDESTINATION_INSTANCE_NAME with the name of the destination Cloud SQL Enterprise Plus edition instance.

5. Optional: If anAuthorize Cloud Shell dialog appears, then clickAuthorize.
6. At theEnter password prompt, enter the password that you provided inDefine settings for the destination Cloud SQL Enterprise Plus edition instance.

7. At themysql prompt, to list the databases and verify that you see your source Cloud SQL Enterprise edition database instance, entershow databases;.
8. At themysql prompt, to see the tables that are associated with this database instance, enteruseSOURCE_DATABASE_INSTANCE_NAME;.
9. At themysql prompt, to see the tables of this instance, entershow tables;.
10. At themysql prompt, to see the information that's replicated from a table in your source Cloud SQL Enterprise edition database instance, enterselect * fromTABLE_NAME;.
11. Verify that you see the correct information in the table.

Promote the migration job

Promoting the migration job replaces the source Cloud SQL Enterprise edition database instance with the destination Cloud SQL Enterprise Plus edition database instance as the primary database.

To promote the migration job, complete the following steps:

1. Return to theMigration jobs page.

2. Click the migration job that you want to promote. TheMigration job details page appears.

3. Stop all writes to the source Cloud SQL Enterprise edition database.

   Important: Before you stop writes to the source database, wait for the replication delay to be minimal.
   You must stop all writes to this database because, by promoting the migration job, the destination Cloud SQL Enterprise Plus edition database becomes your primary database. You can use a script to verify that writing is stopped. For more information, seeFind write activities.

4. Verify that the replication delay is minimal.

5. Click the migration job that you want to promote. This job has a status ofRunning.

6. To promote the migration job, clickPromote.

7. In the dialog that appears, clickPromote.

8. Verify that the migration job has a status ofPromote in progress. After a few minutes, confirm that the status changes toCompleted.

Your new Cloud SQL Enterprise Plus edition database instance is ready to use.

Clean up

To avoid incurring charges to your Google Cloud account for the resources used on this page, use the Google Cloud console to delete your migration job, connection profile, source Cloud SQL Enterprise edition instance, and project if you don't need them.

What's next

• Read more about the key features ofCloud SQL Enterprise Plus edition.
• Read more about performance enhancements forCloud SQL Enterprise Plus edition.
• Read more about region support forCloud SQL Enterprise Plus edition.
• Read more about pricing forCloud SQL Enterprise Plus edition.