Overview
You can perform actions from the migration jobs list or from the single migration page. You can perform an action on multiple jobs simultaneously on migration jobs that all have the same status.
| User action | Description |
|---|---|
| Start | Start migration jobs that were created without being started. |
| Stop |
Stop a running migration job at any time. The data migration is halted, and the migration job status changes to In some cases, if you stop a migration job, then the source database must retain the data until you resume the migration job. The retention period for the source database may be limited. If the migration job is paused for longer than this retention period, and then the migration job is resumed, this can cause the migration job to fail. If this occurs, then delete or restart the migration job. Monitor your database server's disk size. You can choose to delete the migration job, which will stop all network traffic. |
| Resume | If a migration was stopped during the CDC phase, then it can be resumed. Resuming the migration job resumes replication of the events that were accumulated during the stopped time. |
| Restart |
If a migration job failed or stopped, and it isn't recoverable, then it can be restarted from the beginning. If the replication has failed because of an error on one or more source or destination database tables, then restarting the migration job will wipe all data from any destination database tables that are defined by the migration job. If new tables were created on the source server since starting the migration job, then restarting the migration job won't replicate the new tables into the destination instances until the conversion workspace is modified and the tables are added to the migration job's allowlist. |
| Edit | See Modify a migration job. |
| Delete | A migration job can be deleted. |
| Promote | See Promote a migration. |
Modify a migration job
You can modify the following information about a migration job:
- The version of the conversion workspace.
- Configuration information for the source, such as the database tables and schemas in the source that Database Migration Service will migrate to the destination. Database Migration Service uses this configuration information to migrate the correct data from the source into the destination.
Modify the version of the conversion workspace
Go to the Migration jobs page in the Google Cloud Console.
Click the display name of the migration job that you want to modify. An overview page appears for the migration job.
Click EDIT OBJECTS.
From the Define a conversion workspace version menu, select the latest version of the conversion workspace.
In the Select objects to migrate section, select or clear the check boxes to change the tables and schemas in the source that Database Migration Service will migrate into the destination.
Click Save or Save and Restart.
If you click Save, then Database Migration Service will move only historical data for the schemas and tables that you select. Any schemas and tables that exist in the previous version of the conversion workspace will continue to migrate with the updated configuration information.
If you clear any check boxes for tables and schemas, but they exist in the previous version of the conversion workspace, then the schemas and tables will no longer be migrated. However, their data won't be removed from the destination.
- If you click Save and Restart, then Database Migration Service will start the migration from the beginning, after cleaning any tables that you select in the destination.
Modify configuration information for the source
Go to the Migration jobs page in the Google Cloud Console.
Click the display name of the migration job that you want to modify. An overview page appears for the migration job.
Click EDIT OBJECTS.
In the Select objects to migrate section, select or clear the check boxes to change the tables and schemas in the source that Database Migration Service will migrate into the destination.
Click Save or Save and Restart.
If you click Save, then Database Migration Service will move only historical data for the schemas and tables that you select.
- If you click Save and Restart, then Database Migration Service will start the migration from the beginning, after cleaning any tables that you select in the destination.