GSP918

Overview

Database Migration Service provides options for one-time and continuous jobs to migrate data to Cloud SQL. It offers various connectivity methods, including IP allowlists, reverse SSH tunnels, VPC peering, and Private Service Connect interfaces. Learn more about connectivity options from the Configure connectivity Guide.

This lab focuses on migrating a stand-alone PostgreSQL database, hosted on a virtual machine, to Cloud SQL for PostgreSQL. The migration utilizes a continuous job from the Database Migration Service and employs VPC peering to establish connectivity.

Using Database Migration Service for database migration requires several preparatory steps on the source database:

• Create a dedicated user: This user must have replication rights.
• Add the pglogical extension: This extension needs to be installed on the source database.
• Grant necessary rights: The dedicated user must be granted rights to the schemata and tables within the database designated for migration, as well as to the postgres database.

Once the setup is complete, you create and run the migration job. The migration process involves:

• Initial Copy: Confirming the successful transfer of the database's initial copy to your Cloud SQL instance.
• Continuous Migration: Exploring how ongoing migration jobs apply real-time data updates from the source to the Cloud SQL instance.
• Promotion: Concluding the job by promoting the Cloud SQL instance to function as a stand-alone database, ready for read and write operations.

What you'll do

• Prepare the source database for migration.
• Create a profile for a source connection to a PostgreSQL instance (e.g., stand-alone PostgreSQL).
• Configure connectivity between the source and destination database instances using VPC peering.
• Configure firewall and database access rules to allow access to the source database for migration.
• Create, run, and verify a continuous migration job using Database Migration Service.
• Promote the destination instance (Cloud SQL for PostgreSQL) to be a stand-alone database for reading and writing data.

Setup and requirements

Before you click the Start Lab button

Read these instructions. Labs are timed and you cannot pause them. The timer, which starts when you click Start Lab, shows how long Google Cloud resources are made available to you.

This hands-on lab lets you do the lab activities in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials you use to sign in and access Google Cloud for the duration of the lab.

To complete this lab, you need:

• Access to a standard internet browser (Chrome browser recommended).

Note: Use an Incognito (recommended) or private browser window to run this lab. This prevents conflicts between your personal account and the student account, which may cause extra charges incurred to your personal account.

• Time to complete the lab—remember, once you start, you cannot pause a lab.

Note: Use only the student account for this lab. If you use a different Google Cloud account, you may incur charges to that account.

How to start your lab and sign in to the Google Cloud console

1. Click the Start Lab button. If you need to pay for the lab, a dialog opens for you to select your payment method. On the right is the Lab setup and access panel with the following:

   • The Open Google Cloud console button
   • The temporary credentials (username and password) that you must use for this lab
   • Other information, if needed, to step through this lab

   Note that the lab timer is located near the top of the page, showing the remaining time.

2. Click Open Google Cloud console (or right-click and select Open Link in Incognito Window if you are running the Chrome browser).

   The lab spins up resources, and then opens another tab that shows the Sign in page.

   Tip: Arrange the tabs in separate windows, side-by-side.

   Note: If you see the Choose an account dialog, click Use Another Account.

3. If necessary, copy the Username below and paste it into the Sign in dialog.

   {{{user_0.username | "Username"}}}

   You can also find the Username in the Lab setup and access panel.

4. Click Next.

5. Copy the Password below and paste it into the Welcome dialog.

   {{{user_0.password | "Password"}}}

   You can also find the Password in the Lab setup and access panel.

6. Click Next.

   Important: You must use the credentials the lab provides you. Do not use your Google Cloud account credentials. Note: Using your own Google Cloud account for this lab may incur extra charges.

7. Click through the subsequent pages:

   • Accept the terms and conditions.
   • Do not add recovery options or two-factor authentication (because this is a temporary account).
   • Do not sign up for free trials.

After a few moments, the Google Cloud console opens in this tab.

Note: To access Google Cloud products and services, click the Navigation menu or type the service or product name in the Search field.

Activate Cloud Shell

Cloud Shell is a virtual machine that is loaded with development tools. It offers a persistent 5GB home directory and runs on the Google Cloud. Cloud Shell provides command-line access to your Google Cloud resources.

1. Click Activate Cloud Shell at the top of the Google Cloud console.

2. Click through the following windows:

   • Continue through the Cloud Shell information window.
   • Authorize Cloud Shell to use your credentials to make Google Cloud API calls.

When you are connected, you are already authenticated, and the project is set to your Project_ID, . The output contains a line that declares the Project_ID for this session:

Your Cloud Platform project in this session is set to {{{project_0.project_id | "PROJECT_ID"}}}

gcloud is the command-line tool for Google Cloud. It comes pre-installed on Cloud Shell and supports tab-completion.

3. (Optional) You can list the active account name with this command:

gcloud auth list

4. Click Authorize.

Output:

ACTIVE: * ACCOUNT: {{{user_0.username | "ACCOUNT"}}} To set the active account, run: $ gcloud config set account `ACCOUNT`

5. (Optional) You can list the project ID with this command:

gcloud config list project

Output:

[core] project = {{{project_0.project_id | "PROJECT_ID"}}} Note: For full documentation of gcloud, in Google Cloud, refer to the gcloud CLI overview guide.

Verify that the Database Migration API is enabled

The Database Migration API is required to manage the movement of database data through the Database Migration Service.

1. In the Google Cloud console title bar, enter Database Migration API into the Search field, and then click Database Migration API from the results.

The Manage button is visible when the API is enabled.

2. If you see the Enable button, click it to enable the API.

Verify that the Service Networking API is enabled

The Service Networking API is required to configure Cloud SQL to support VPC Peering and connections over a private ip-address.

1. In the Cloud console title bar, enter Service Networking API into the Search field, and then click Service Networking API from the search results.

The Manage button is visible when the API is enabled.

2. If you see the Enable button, click it to enable the API.

Task 1. Prepare the source database for migration

To prepare the source database for the migration through the Database Migration Service, you upgrade the database with the pglogical extension and then create the database migration user.

To upgrade the database with the pglogical extension, you:

• Install and configure the pglogical database extension.
• Configure the stand-alone PostgreSQL database to allow access from Cloud Shell and Cloud SQL.
• Add the pglogical database extension to the postgres, orders and gmemegen_db databases on the stand-alone server.

To create the database migration user, you create a migration_admin user (with Replication permissions) for database migration and then grant them the required permissions to schemata and relations.

Upgrade the database with the pglogical extension

In this section, you download and add the pglogical database extension to the orders and postgres databases on the postgresql-vm VM Instance.

1. In the Google Cloud console, on the Navigation menu (), click Compute Engine > VM instances.

2. In the postgresql-vm VM instance, click SSH.

3. If prompted, click Authorize.

4. In the new terminal window, install the pglogical database extension:

sudo apt install postgresql-14-pglogical Note: pglogical is a logical replication system implemented entirely as a PostgreSQL extension. Fully integrated, it requires no triggers or external programs. This alternative to physical replication is a highly efficient method of replicating data using a publish/subscribe model for selective replication.

5. Download and apply some additions to the PostgreSQL configuration files (to enable the pglogical extension) and restart the postgresql service:

sudo su - postgres -c "gsutil cp gs://spls/gsp918/pg_hba_append.conf ." sudo su - postgres -c "gsutil cp gs://spls/gsp918/postgresql_append.conf ." sudo su - postgres -c "cat pg_hba_append.conf >> /etc/postgresql/14/main/pg_hba.conf" sudo su - postgres -c "cat postgresql_append.conf >> /etc/postgresql/14/main/postgresql.conf" sudo systemctl restart postgresql@14-main

These files in pg_hba.conf add a rule to allow access to all hosts:

#GSP918 - allow access to all hosts host all all 0.0.0.0/0 md5

These commands in postgresql.conf set the minimal configuration for pglogical to listen on all addresses:

#GSP918 - added configuration for pglogical database extension wal_level = logical # minimal, replica, or logical max_worker_processes = 10 # one per database needed on provider node # one per node needed on subscriber node max_replication_slots = 10 # one per node needed on provider node max_wal_senders = 10 # one per node needed on provider node shared_preload_libraries = 'pglogical' max_wal_size = 1GB min_wal_size = 80MB listen_addresses = '*' # what IP address(es) to listen on, '*' is all

The above code snippets were appended to the relevant files and the PostgreSQL service restarted.

6. Launch the psql tool:

sudo su - postgres psql

7. Add the pglogical database extension to the postgres, orders and gmemegen_db databases:

\c postgres; CREATE EXTENSION pglogical; \c orders; CREATE EXTENSION pglogical; \c gmemegen_db; CREATE EXTENSION pglogical;

8. List the PostgreSQL databases on the server:

\l

The output below lists the default postgresql databases, as well as the orders and gmemegen_db databases provided for this lab. You do not use the gmemegen_db database in this lab.

List of databases Name | Owner | Encoding | Collate | Ctype | Access privileges -------------+----------+----------+---------+---------+----------------------- gmemegen_db | postgres | UTF8 | C.UTF-8 | C.UTF-8 | orders | postgres | UTF8 | C.UTF-8 | C.UTF-8 | postgres | postgres | UTF8 | C.UTF-8 | C.UTF-8 | template0 | postgres | UTF8 | C.UTF-8 | C.UTF-8 | =c/postgres + | | | | | postgres=CTc/postgres template1 | postgres | UTF8 | C.UTF-8 | C.UTF-8 | =c/postgres + | | | | | postgres=CTc/postgres (5 rows)

Create the database migration user

In this section you create a dedicated user to manage database migration.

• In psql, enter the commands below to create a new user with the replication role:

CREATE USER migration_admin PASSWORD 'DMS_1s_cool!'; ALTER DATABASE orders OWNER TO migration_admin; ALTER ROLE migration_admin WITH REPLICATION;

Assign permissions to the migration user

In this section, you assign the necessary permissions to the migration_admin user to enable Database Migration Service to migrate your database.

1. In psql, grant permissions to the pglogical schema and tables for the postgres database:

\c postgres; GRANT USAGE ON SCHEMA pglogical TO migration_admin; GRANT ALL ON SCHEMA pglogical TO migration_admin; GRANT SELECT ON pglogical.tables TO migration_admin; GRANT SELECT ON pglogical.depend TO migration_admin; GRANT SELECT ON pglogical.local_node TO migration_admin; GRANT SELECT ON pglogical.local_sync_status TO migration_admin; GRANT SELECT ON pglogical.node TO migration_admin; GRANT SELECT ON pglogical.node_interface TO migration_admin; GRANT SELECT ON pglogical.queue TO migration_admin; GRANT SELECT ON pglogical.replication_set TO migration_admin; GRANT SELECT ON pglogical.replication_set_seq TO migration_admin; GRANT SELECT ON pglogical.replication_set_table TO migration_admin; GRANT SELECT ON pglogical.sequence_state TO migration_admin; GRANT SELECT ON pglogical.subscription TO migration_admin;

2. Grant permissions to the pglogical schema and tables for the orders database:

\c orders; GRANT USAGE ON SCHEMA pglogical TO migration_admin; GRANT ALL ON SCHEMA pglogical TO migration_admin; GRANT SELECT ON pglogical.tables TO migration_admin; GRANT SELECT ON pglogical.depend TO migration_admin; GRANT SELECT ON pglogical.local_node TO migration_admin; GRANT SELECT ON pglogical.local_sync_status TO migration_admin; GRANT SELECT ON pglogical.node TO migration_admin; GRANT SELECT ON pglogical.node_interface TO migration_admin; GRANT SELECT ON pglogical.queue TO migration_admin; GRANT SELECT ON pglogical.replication_set TO migration_admin; GRANT SELECT ON pglogical.replication_set_seq TO migration_admin; GRANT SELECT ON pglogical.replication_set_table TO migration_admin; GRANT SELECT ON pglogical.sequence_state TO migration_admin; GRANT SELECT ON pglogical.subscription TO migration_admin;

3. Grant permissions to the public schema and tables for the orders database:

GRANT USAGE ON SCHEMA public TO migration_admin; GRANT ALL ON SCHEMA public TO migration_admin; GRANT SELECT ON public.distribution_centers TO migration_admin; GRANT SELECT ON public.inventory_items TO migration_admin; GRANT SELECT ON public.order_items TO migration_admin; GRANT SELECT ON public.products TO migration_admin; GRANT SELECT ON public.users TO migration_admin;

4. Grant permissions to the pglogical schema and tables for the gmemegen_db database:

\c gmemegen_db; GRANT USAGE ON SCHEMA pglogical TO migration_admin; GRANT ALL ON SCHEMA pglogical TO migration_admin; GRANT SELECT ON pglogical.tables TO migration_admin; GRANT SELECT ON pglogical.depend TO migration_admin; GRANT SELECT ON pglogical.local_node TO migration_admin; GRANT SELECT ON pglogical.local_sync_status TO migration_admin; GRANT SELECT ON pglogical.node TO migration_admin; GRANT SELECT ON pglogical.node_interface TO migration_admin; GRANT SELECT ON pglogical.queue TO migration_admin; GRANT SELECT ON pglogical.replication_set TO migration_admin; GRANT SELECT ON pglogical.replication_set_seq TO migration_admin; GRANT SELECT ON pglogical.replication_set_table TO migration_admin; GRANT SELECT ON pglogical.sequence_state TO migration_admin; GRANT SELECT ON pglogical.subscription TO migration_admin;

5. Grant permissions to the public schema and tables for the gmemegen_db database:

GRANT USAGE ON SCHEMA public TO migration_admin; GRANT ALL ON SCHEMA public TO migration_admin; GRANT SELECT ON public.meme TO migration_admin;

The source databases are now prepared for migration. The permissions you have granted to the migration_admin user are all that is required for Database Migration Service to migrate the postgres, orders and gmemegen_db databases.

Make the migration_admin user the owner of the tables in the orders database, so that you can edit the source data later, when you test the migration.

6. Run the following commands:

\c orders; \dt ALTER TABLE public.distribution_centers OWNER TO migration_admin; ALTER TABLE public.inventory_items OWNER TO migration_admin; ALTER TABLE public.order_items OWNER TO migration_admin; ALTER TABLE public.products OWNER TO migration_admin; ALTER TABLE public.users OWNER TO migration_admin; \dt

Output

List of relations Schema | Name | Type | Owner --------+----------------------+-------+------- public | distribution_centers | table | migration_admin public | inventory_items | table | migration_admin public | order_items | table | migration_admin public | products | table | migration_admin public | users | table | migration_admin (5 rows)

7. Exit psql and the postgres user session:

\q exit

Click Check my progress to verify the objective. Prepare the PostgreSQL source instance for migration.

Task 2. Create a Database Migration Service connection profile for a stand-alone PostgreSQL database

In this task, you create a connection profile for the PostgreSQL source instance.

Get the connectivity information for the PostgreSQL source instance

In this step, you identify the internal IP address of the source database instance that you migrate to Cloud SQL.

1. In the Google Cloud console, on the Navigation menu (), click Compute Engine > VM instances.

2. In the Instance list, locate postgresql-vm.

3. Copy the Internal IP (e.g., 10.128.0.2) to use to configure a connection profile in the next section.

Create a new connection profile for the PostgreSQL source instance

A connection profile stores information about the source database instance (e.g., stand-alone PostgreSQL) and is used by the Database Migration Service to migrate data from the source to your destination Cloud SQL database instance. After you create a connection profile, it can be reused across migration jobs.

In this step you create a new connection profile for the PostgreSQL source instance.

1. In the Google Cloud console, on the Navigation menu (), click View all products. Under the Databases section, click Database migration > Connection profiles.

2. Click Create profile.

3. Specify the following fields and leave those remaining as their defaults:

Field	Value
Source engine	PostgreSQL
Destination engine	Cloud SQL for PostgreSQL
Profile type	Source
Connection profile name	postgres-vm
Region
Define connection configurations	Define
Hostname or IP address	the internal IP for the PostgreSQL source instance that you copied in the previous task (e.g., 10.128.0.2)
Port	5432
Username	migration_admin
Password	DMS_1s_cool!

4. Click Save.

5. Click Create.

A new connection profile named postgres-vm shows in the Connections profile list.

Click Check my progress to verify the objective. Create a connection profile for the PostgreSQL source instance.

Task 3. Create and start a continuous migration job

To create a new migration job, you must first specify the source database instance by using an existing connection profile. Next, you establish the destination database instance and set up the necessary connectivity between the source and destination instances.

In this task, you use the migration job interface to create a new Cloud SQL for PostgreSQL database instance and set it as the destination for the continuous migration job from the PostgreSQL source instance.

Create a new continuous migration job

In this step you create a new continuous migration job.

1. In the console, on the Navigation menu (), click View all products. Under the Databases section, click Database Migration > Migration jobs.

2. Click Create migration job.

3. Specify the following fields and leave those remaining as their defaults:

Field	Value
Migration job name	vm-to-cloudsql
Source database engine	PostgreSQL
Destination database engine	Cloud SQL for PostgreSQL
Destination region
Migration job type	Continuous

4. Click Save & continue.

Define the source instance

In this step you define the source instance for the migration.

1. For Source connection profile, select postgres-vm.

Leave the defaults for the other settings.

2. Click Save & continue.

Define the destination instance

In this step, you define the destination instance for the migration.

1. For Type of destination instance, select Existing instance.

2. For Select destination instance, select postgresql-cloudsql.

3. Click Select & continue.

4. If prompted to confirm, enter the instance name postgresql-cloudsql.

5. Click Confirm & continue.

Note: Ignore the warning note: Your destination instance will be demoted and converted into a replica for your source database.

Define the connectivity method

In this step, you define the connectivity method for the migration.

1. For Connectivity method, select VPC peering.

2. For VPC, select default.

VPC peering is configured by Database Migration Service using the information provided for the VPC network (the default network in this example).

When you see an updated message that the destination instance was created, proceed to the next step.

3. Click Configure & continue.

Configure migration databases

In this step, you define the source instance for the migration.

1. For Databases to migrate, select All databases.

2. Click Save & continue.

Allow access to the postgresql-vm instance from automatically allocated IP range

In this step you edit the pg_hba.conf PostgreSQL configuration file to allow the Database Migration Service to access the stand-alone PostgreSQL database.

1. Get the allocated IP address range. In the console, on the Navigation menu (), click VPC networks and then right-click VPC network peering and open it in a new tab.

2. Click on the servicenetworking-googleapis-com entry and then click Effective routes view at the bottom.

3. From the dropdown for Network select default and for Region select . Click View.

4. In the Destination IP range column , record the IP range (e.g. 10.107.176.0/24) next to peering-route-xxxxx... route to use in an upcoming step.

5. In the terminal session on the VM instance, edit the pg_hba.conf file as follows:

sudo nano /etc/postgresql/14/main/pg_hba.conf

6. On the last line of the file:

#GSP918 - allow access to all hosts host all all 0.0.0.0/0 md5

Replace the "all IP addresses" range (0.0.0.0/0) with the range recorded in the previous step.

#GSP918 - allow access to all hosts host all all 10.107.176.0/24 md5 Note: The above step is not required to make the migration work, but it is good practice to make the source database more secure during the migration process. It also restricts access after the migration when the migrated database becomes the source of truth.

7. Press CTRL+O, ENTER, CTRL+X to save the file and exit the nano editor.

8. Restart the PostgreSQL service to make the changes take effect. In the VM instance terminal session:

sudo systemctl start postgresql@14-main

Test and start the continuous migration job

In this step, you test and start the migration job.

1. In the Database Migration Service tab you opened earlier, review the details of the migration job.

2. Click Test job.

3. After a successful test, click Create & start job.

4. If prompted to confirm, click Create & start.

Review the status of the continuous migration job

In this step, you confirm that the continuous migration job is running.

1. In the Google Cloud console, on the Navigation menu (), click Database migration > Migration jobs.

2. Click the migration job vm-to-cloudsql to see the details page.

3. Review the migration job status.

   • If you have not started the job, the status shows as Not started. You can choose to start or delete the job.
   • After the job has started, the status shows as Starting and then transition to Running to indicate that the initial database dump is in progress.
   • After the initial database dump has been completed, the phase status will be CDC to indicate that continuous migration is active.

When the job phase changes to CDC, proceed to the next task.

Note: Continuous migration jobs remain in a running status to ensure that the destination database continues to receive data updates from the source. A completed status is achieved after you promote the destination database to be a stand-alone database for reading and writing data. You perform that in Task 5.

Click Check my progress to verify the objective. Create, start, and review a continuous migration job.

Task 4. Confirm the data in Cloud SQL for PostgreSQL

Check the PostgreSQL databases in Cloud SQL

1. In the Google Cloud console, on the Navigation menu (), click Cloud SQL.

2. Expand the instance ID called postgresql-cloudsql-master.

3. Click the instance postgresql-cloudsql (PostgreSQL read replica).

4. In the Replica instance menu, click Databases.

Notice that the databases called postgres, orders and gmemegen_db have been migrated to Cloud SQL.

Connect to the PostgreSQL instance

1. In the Replica instance menu, click Overview.

2. Scroll down to the Connect to this instance section and click Open Cloud Shell.

The command to connect to PostgreSQL pre-populates in Cloud Shell:

gcloud sql connect postgresql-cloudsql --user=postgres --quiet

3. Run the pre-populated command.

4. If prompted, click Authorize for the API.

5. When prompted for a password, which you previously set, enter:

supersecret!

You have now activated the PostgreSQL interactive console for the destination instance.

Review the data in the Cloud SQL for PostgreSQL instance

1. To select the database in the PostgreSQL interactive console, run the following command:

\c orders;

2. When prompted for a password, enter:

supersecret!

3. Query the distribution_centers table:

select * from distribution_centers;

(Output)

longitude | latitude | name | id -----------+----------+---------------------------------------------+---- -89.9711 | 35.1174 | Memphis TN | 1 -87.6847 | 41.8369 | Chicago IL | 2 -95.3698 | 29.7604 | Houston TX | 3 -118.25 | 34.05 | Los Angeles CA | 4 -90.0667 | 29.95 | New Orleans LA | 5 -73.7834 | 40.634 | Port Authority of New York/New Jersey NY/NJ | 6 -75.1667 | 39.95 | Philadelphia PA | 7 -88.0431 | 30.6944 | Mobile AL | 8 -79.9333 | 32.7833 | Charleston SC | 9 -81.1167 | 32.0167 | Savannah GA | 10

4. Exit the PostgreSQL interactive console by typing:

\q

Update stand-alone source data to test continuous migration

1. In Cloud Shell, type the following commands to connect to the source PostgreSQL instance:

export VM_NAME=postgresql-vm export PROJECT_ID=$(gcloud config list --format 'value(core.project)') export POSTGRESQL_IP=$(gcloud compute instances describe ${VM_NAME} \ --zone={{{ project_0.default_zone|(zone) }}} --format="value(networkInterfaces[0].accessConfigs[0].natIP)") echo $POSTGRESQL_IP psql -h $POSTGRESQL_IP -p 5432 -d orders -U migration_admin Note: The above is an alternative approach to accessing the stand-alone database on the VM instance.

2. When prompted for a password, enter:

DMS_1s_cool!

3. In psql, enter the following commands:

\c orders; insert into distribution_centers values(-80.1918,25.7617,'Miami FL',11);

4. Close the interactive psql session:

\q

Connect to the Cloud SQL PostgreSQL database to check that updated data has been migrated

1. In Cloud Shell, type the following commands to connect to the destination Cloud SQL PostgreSQL instance:

gcloud sql connect postgresql-cloudsql --user=postgres --quiet

2. When prompted for a password, which you previously set, enter the password for the Cloud SQL instance:

supersecret!

You have now activated the PostgreSQL interactive console for the destination instance.

Review data in Cloud SQL for PostgreSQL database

1. In Cloud Shell, select the active database in the PostgreSQL interactive console:

\c orders;

2. When prompted for a password, which you previously set, enter:

supersecret!

3. Query the distribution_centers table:

select * from distribution_centers;

(Output)

longitude | latitude | name | id -----------+----------+---------------------------------------------+---- -89.9711 | 35.1174 | Memphis TN | 1 -87.6847 | 41.8369 | Chicago IL | 2 -95.3698 | 29.7604 | Houston TX | 3 -118.25 | 34.05 | Los Angeles CA | 4 -90.0667 | 29.95 | New Orleans LA | 5 -73.7834 | 40.634 | Port Authority of New York/New Jersey NY/NJ | 6 -75.1667 | 39.95 | Philadelphia PA | 7 -88.0431 | 30.6944 | Mobile AL | 8 -79.9333 | 32.7833 | Charleston SC | 9 -81.1167 | 32.0167 | Savannah GA | 10 -80.1918 | 25.7617 | Miami FL | 11

Note that the new row added on the stand-alone orders database, is now present on the migrated database.

4. Exit the PostgreSQL interactive console:

\q

Click Check my progress to verify the objective. Test the continuous migration of data from the source to the destination.

Task 5. Promote Cloud SQL to be a stand-alone instance for reading and writing data

1. In the Google Cloud console, on the Navigation menu (), click View all products. Under the Databases section, click Database Migration > Migration jobs.

2. Click the migration job name vm-to-cloudsql to see the details page.

3. Click Promote.

4. If prompted to confirm, click Promote.

When the promotion is complete, the status of the job updates to Completed.

4. In the Google Cloud console, on the Navigation menu (), click View all products. Under the Databases section, click Cloud SQL.

Note that postgresql-cloudsql is now a stand-alone instance for reading and writing data.

Click Check my progress to verify the objective. Promote Cloud SQL for PostgreSQL database to be a stand-alone instance for reading and writing data.

Congratulations!

You configured a continuous Database Migration Service job to migrate databases from a PostgreSQL instance to Cloud SQL for PostgreSQL.

Next steps / Learn more

Learn more about data migration, Cloud SQL databases, and Database Migration Service:

• Database Migration Service documentation
• Cloud SQL for PostgreSQL documentation
• Types of migration

Google Cloud training and certification

...helps you make the most of Google Cloud technologies. Our classes include technical skills and best practices to help you get up to speed quickly and continue your learning journey. We offer fundamental to advanced level training, with on-demand, live, and virtual options to suit your busy schedule. Certifications help you validate and prove your skill and expertise in Google Cloud technologies.

Manual Last Updated on May 20, 2026

Lab Last Tested February 19, 2026

Copyright 2026 Google LLC. All rights reserved. Google and the Google logo are trademarks of Google LLC. All other company and product names may be trademarks of the respective companies with which they are associated.