Tencent Cloud

Recent Pages

Cutover Description

Last updated: 2024-07-08 16:02:22

Notes
To better distinguish between sessions and improve data security, we recommend you create a separate database account for data migration.
As cutover requires pausing data writes into the source database, we recommend you cut over the business during off-peak hours.
Directions
1. Log in to the DTS console and proceed based on whether incremental migration is involved:
Incremental migration is involved: Go to step 2.
Incremental migration is not involved: Go to step 6.
2. Wait until the Migration Step of the data migration task becomes Syncing Incremental Data, the source-target database data gap is 0 KB, and the source-target database time lag is 0s.
﻿
3. Pause the business in the source database and stop writing new data.
4. Choose the appropriate code below based on your source database type to view whether there is new session information. If the result shows that there is no new session being executed except the connection of the DTS migration instance in 1–5 minutes, the business can be deemed as completely stopped.
MySQL
show processlist  
SQL Server
select * from sys.dm_exec_connections;
PostgreSQL
select * from pg_stat_activity;
MongoDB
use admin
db.runCommand({currentOp: 1, $all:[{"active" : true}]})
5. Stop the incremental migration task.
View the migration task again, wait for at least 1 minute after the source-target database data gap is 0 KB and the source-target database time lag is 0s, and click Complete to stop the incremental migration task.
﻿
﻿
6. After confirming that the data in the source and target databases is consistent, determine the cutover time, route the business system to the target database, and resume the business.