tencent cloud

Data Transfer Service

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Data Migration
Data Sync
Data Subscription (Kafka Edition)
Strengths
Supported Regions
Specification Description
Purchase Guide
Billing Overview
Configuration Change Description
Payment Overdue
Refund
Getting Started
Data Migration Guide
Data Sync Guide
Data Subscription Guide (Kafka Edition)
Preparations
Business Evaluation
Network Preparation
Adding DTS IP Addresses to the Allowlist of the Corresponding Databases
DTS Service Permission Preparation
Database and Permission Preparation
Configuring Binlog in Self-Built MySQL
Data Migration
Databases Supported by Data Migration
Cross-Account TencentDB Instance Migration
Migration to MySQL Series
Migrating to PostgreSQL
Migrating to MongoDB
Migrating to SQL Server
Migrating to Tencent Cloud Distributed Cache
Task Management
Data Sync
Databases Supported by Data Sync
Cross-Account TencentDB Instance Sync
Sync to MySQL series
Synchronize to PostgreSQL
Synchronization to MongoDB
Synchronize to Kafka
Task Management
Data Subscription (Kafka Edition)
Databases Supported by Data Subscription
MySQL series Data Subscription
Data Subscription for TDSQL PostgreSQL
MongoDB Data Subscription
Task Management
Consumption Management
Fix for Verification Failure
Check Item Overview
Cutover Description
Monitoring and Alarms
Supported Monitoring Indicators
Supported Events
Configuring Metric Alarms and Event Alarms via the Console
Configuring Indicator Monitoring and Event Alarm by APIs
Ops Management
Configuring Maintenance Time
Task Status Change Description
Practical Tutorial
Synchronizing Local Database to the Cloud
Creating Two-Way Sync Data Structure
Creating Many-to-One Sync Data Structure
Creating Multi-Site Active-Active IDC Architecture
Selecting Data Sync Conflict Resolution Policy
Using CLB as Proxy for Cross-Account Database Migration
Migrating Self-Built Databases to Tencent Cloud Databases via CCN
Best Practices for DTS Performance Tuning
FAQs
Data Migration
Data Sync
FAQs for Data Subscription Kafka Edition
Regular Expressions for Subscription
Error Handling
Common Errors
Failed Connectivity Test
Failed or Alarmed Check Item
Inability to Select Subnet During CCN Access
Slow or Stuck Migration
Data Sync Delay
High Data Subscription Delay
Data Consumption Exception
API Documentation
History
Introduction
API Category
Making API Requests
(NewDTS) Data Migration APIs
Data Sync APIs
Data Consistency Check APIs
(NewDTS) Data Subscription APIs
Data Types
Error Codes
DTS API 2018-03-30
Service Agreement
Service Level Agreements
ドキュメントData Transfer ServiceCutover Description

Cutover Description

PDF
フォーカスモード
フォントサイズ
最終更新日: 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.
前の記事へ: Check Item Overview次の記事へ: Supported Monitoring Indicators

ヘルプとサポート

この記事はお役に立ちましたか？

フィードバック