Stay organized with collections Save and categorize content based on your preferences.
Database Migration Service uses migration jobs to migrate data from your source database instance to the destination AlloyDB database instance.
Creating a migration job includes:
Database Migration Service wizard helps you create a migration job. The wizard consists of the following panes: Get started, Define a source, Define a destination, Define connectivity method, Configure migration databases, and Test and create migration job. Information on how to populate each pane is provided in the various sections of this page.
You can pause the creation of a migration job by clicking Save and exit. All of the data that was populated until that point is saved in a draft migration job, and you can access this job on the Drafts tab.
To finish creating a migration job, navigate to the tab, and then click the job. The creation flow resumes from where it was left off. The job remains a draft until you click Create or Create and start.
Define settings for the migration jobProvide a name for the migration job.
Choose a friendly name that helps you identify the migration job. Don't include sensitive or personally identifiable information in the job name.
Keep the auto-generated Migration job ID.
Select the source database engine.
Select AlloyDB for PostgreSQL as the destination engine.
Select the destination region for your migration. This is where the Database Migration Service instance is created, and should be selected based on the location of the services that need your data, such as Compute Engine instances and App Engine apps, and other services. After you choose the destination region, this selection can't be changed.
Choose Continuous (snapshot + ongoing changes) as the migration job type.
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 database and how to connect it to the destination AlloyDB database instance. It's best to complete these prerequisites at this step, but you can complete them at any time before you test the migration job or start it. For more information about these prerequisites, see Configure your source.
Click Save and continue.
If you have created a connection profile, then select it from the list of existing connection profiles.
If you haven't created a connection profile, then create one by clicking Create a connection profile at the bottom of the drop-down list, and then perform the same steps as in Create a source connection profile.
It is recommended to create a designated connection profile for your AlloyDB migration.
The speed of data dump parallelism is related to the amount of load on your source database. You can use the following settings:
If you want to use adjusted data dump parallelism settings, make sure to increase the max_replication_slots, max_wal_senders, and max_worker_processes parameters on your source database. You can verify your configuration by running the migration job test at the end of migration job creation.
If your source database is a Cloud SQL instance and has only public IP enabled, make sure to enable its private IP before continuing to the next section. Remember to update the connection profile with the private IP.
Define and create the destination AlloyDB instanceYou will now create a new destination AlloyDB cluster for your migration job. Clusters are the top-level resources in AlloyDB. They contain a single primary instance for read/write access to the database you create during the migration process.
To create a destination cluster:
postgres user. You will need the password to log in to your database.If you want to manage your encryption, you can use a customer-managed encryption key (CMEK). The key must be in the same location as your AlloyDB cluster. For example, for clusters located in us-west1 can use only keys in us-west1.
If you don't see your key, then click ENTER KEY RESOURCE NAME to provide the resource name of the key that you want to use. For example, you can enter projects/my-project-name/locations/my-location/keyRings/my-keyring/cryptoKeys/my-key in the Key resource name field, and then click SAVE.
As part of creating the migration job, Database Migration Service will verify that the CMEK exists, and that Database Migration Service has permissions to use the key.
If Database Migration Service doesn't have these permissions, then information will appear, specifying that the Database Migration Service service account can't use the CMEK. Click GRANT to give Database Migration Service permissions to use the key.
For more information about encryption keys, see Use CMEK in AlloyDB documentation.
--force option. Set up connectivity between the source and destination database instances If you're reusing a source connection profile that was used previously for heterogeneous migrations (for example, from Oracle to Cloud SQL PostgreSQL), then in this step, you must choose a connectivity method. This method will be used for the homogeneous migration from Cloud SQL for PostgreSQL database to AlloyDB. You must select a connectivity method because the heterogeneous connectivity method isn't relevant for this migration job.
From the Connectivity method drop-down menu, select a network connectivity method. This method defines how the newly created AlloyDB instance will connect to the source database. Current network connectivity methods include IP allowlist, VPC peering, reverse SSH tunnel, and TCP proxy through a cloud-hosted VM.
pg_hba.conf file, so that the source can accept connections from these addresses.If you select the reverse SSH tunnel network connectivity method, then select the Compute Engine VM instance that will host the tunnel.
After specifying the instance, Google will provide a script that performs the steps to set up the tunnel between the source and destination databases. You'll need to run the script in the Google Cloud CLI.
Run the commands from a machine that has connectivity to both the source database and to Google Cloud.
If you select the TCP Proxy through the cloud-hosted VM connectivity method, then enter the required details for the new Compute Engine VM instance that will host the TCP proxy.
After specifying the details, the Google Cloud console will provide a script that performs the steps to set up the proxy between the source and destination databases. You'll need to run the script on a machine with an updated Google Cloud CLI.
After running the script, it will output the newly created VM's private IP. Enter the IP and click Configure & continue.
After selecting the network connectivity method and providing any additional information for the method, click CONFIGURE & CONTINUE.
You can select the databases that you want to migrate.
If you want to migrate specific databases, you can filter the list that appears and select the databases that you want Database Migration Service to migrate into a destination.
If the list doesn't appear and a database discovery error is displayed, click Reload. If database discovery fails, the job migrates all databases. You can continue with creating a migration job and fix connectivity errors later.
On this final step, review the summary of the migration job settings, source, destination, and connectivity method, and then test the validity of the migration job setup. If any issues are encountered, then you can modify the migration job's settings. Not all settings are editable.
Click TEST JOB to verify that:
The migration job is valid, and the source and destination versions are compatible.
If the test fails, then you can address the problem in the appropriate part of the flow, and return to re-test.
For more information about reasons why the test may fail and how to troubleshoot any issues associated with the test failing, see Diagnose issues for AlloyDB.The migration job can be created even if the test fails, but after the job is started, it may fail at some point during the run.
Click CREATE & START JOB to create the migration job and start it immediately, or click CREATE JOB to create the migration job without immediately starting it.
If the job isn't started at the time that it's created, then it can be started from the Migration jobs page by clicking START.
Regardless of when the migration job starts, your organization is charged for the existence of the destination instance.
Key Point: When you start the migration job, Database Migration Service begins the full dump, briefly locking the source database. If your source is in Amazon RDS or Amazon Aurora, Database Migration Service additionally requires a short (approximately under a minute) write downtime at the start of the migration.For more information, see Known limitations.
The migration job is added to the migration jobs list and can be viewed directly.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-07-09 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-09 UTC."],[[["Database Migration Service facilitates data migration from a source database to a destination AlloyDB instance through migration jobs, using a wizard with six panes: **Get started**, **Define a source**, **Define a destination**, **Define connectivity method**, **Configure migration databases**, and **Test and create migration job**."],["Creating a migration job involves specifying job settings, selecting a source connection profile, defining the destination AlloyDB instance and its configurations, and setting up connectivity between the source and destination."],["Users can choose between **Continuous** migration (snapshot + ongoing changes) and the type of connectivity method used, such as IP allowlist, VPC peering, reverse SSH tunnel, or TCP proxy through a cloud-hosted VM."],["The process includes testing the migration job to ensure the validity of the setup before creating it, and the migration job can be created without starting it immediately."],["Once a migration job is started, Database Migration Service initiates a full data dump from the source database, which may briefly lock it, and it requires a short write downtime if the source is in Amazon RDS or Amazon Aurora."]]],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4