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

Retrying Task (Redis)

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-07-08 20:31:48

Overview

After a sync task is started, if it is interrupted due to an exception, you can manually retry it.
For Redis migration links, the task retry mechanism is to execute the data migration task again after the task interruption, with the previously migrated data cleared or overwritten.
This document describes manual retry operations. You can also set automatic retry when configuring the task as instructed in Migration from Redis to TencentDB for Redis. The manual and automatic retry mechanisms are the same.

Note

Only the tasks in the Task error (error) status can be retried.

Directions

Note
As the retry operation will clear or overwrite the data in the target database, you need to configure the target database read/write policies for DTS.
For tasks created after the retry feature was released in June 2023, such policies can be set in the task configuration stage
For tasks created before the retry feature was released in June 2023, such policies need to be set on the Task Details page.

Configuring target database read/write policies for new tasks

Below are brief instructions. For detailed directions, see Migration from Redis to TencentDB for Redis.
1. Log in to the DTS console, select Data Migration on the left sidebar, click Create Migration Task, and purchase a task.
2. In the task list, select the purchased task and click Configure in the Operation column.
3. In the Set source and target databases step, set the automatic retry time.

4. In the Set migration options and select migration objects step, set the target database read/write policy.
Target Database Write Mode
Clear target instance: This option indicates that when you sync the data from the source database to the target database, the existing data in the target database will be cleared to allow for the synced data to be written.
Overwrite: This option indicates that when you sync the data from the source database to the target database, keys in the target database will be overwritten by those in the source database.
Enable Target Database Read/Write: To use the task retry feature, you must enable this option to allow DTS to write data to the target database.

5. Verify the task and start it.

Configuring target database read/write policies for existing tasks

1. Log in to the DTS console, select Data Migration on the left sidebar, select a target task, and click the task ID.
2. On the Task Details page, modify the Target Database Write Mode and Target Database Read/Write parameters.


Retrying the task

1. Select Data Migration on the left sidebar and select a target migration task.
2. In the Operation column, click More > Retry.




ヘルプとサポート

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

フィードバック