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

Payment Overdue

PDF

Mode fokus

Ukuran font

Terakhir diperbarui: 2023-09-05 15:08:42

Overdue Payment Policy for Monthly Subscription Billing
Alert description
Alert for expiration: From seven days before your monthly subscribed instance expires, the system will send an expiration alert message to you. Your Tencent Cloud account creator, global resource collaborators, and financial collaborators will be notified by email and SMS.
Alert for overdue payments: From the day when your monthly subscribed instance expires, the system will send an isolation alert message to you. Your Tencent Cloud account creator and all collaborators by will be notified by email and SMS.
Repossession mechanism
After your monthly subscribed instance expires, it will remain available for one day and become unavailable for another seven days. You can renew it within the 8 days. If your balance is sufficient and auto-renewal is enabled, your instance will be automatically renewed upon expiration.
Time
Description
The 1st day after the expiration (within 24 hours)
You can continue using your instance. The system will send you an expiration reminder, and you need to renew it as soon as possible.
The 2nd-8th days after the expiration
You can’t use your instance any more. Your instance will be isolated and moved into the recycle bin, where it will be retained for seven days. You can renew it during this period.
After shutdown, your instance will no longer be billed.
The 9th day after the expiration
The resources will be repossessed by the system and all the data will be cleared and cannot be recovered.
Overdue Payment Policy for Pay-as-You-Go Billing
Alert description
Reminder for overdue payments: Pay-as-you-go resources are billed on every clock-hour. When your account balance becomes negative, your Tencent Cloud account creator, global resource collaborators, and financial collaborators will be notified by email and SMS.
Alert for overdue payments: This feature is disabled by default. To enable it, see Balance Notifications.
Note
After you stop using pay-as-you-go instances, terminate them as soon as possible to avoid fee deduction.
Since your actual resource consumption may change over time, some balance alerts may be inaccurate.
Repossession mechanism
After your pay-as-you-go instance has an overdue payment, it will remain available for one day and become unavailable for another seven days. You can top up your account balance within the 8 days.
Time
Description
The 1st day after the overdue payment (within 24 hours)
You can continue using your pay-as-you-go instance. The system will send you a reminder for the overdue payment, and you need to top up your account  balance as soon as possible.
The 2nd-8th days after the overdue payment
You can’t use your instance any more. Your instance will be isolated and moved into the recycle bin, where it will be retained for seven days. You can top up your account balance during this period.
After shutdown, your instance will no longer be billed.
The 9th day after the overdue payment
The resources will be repossessed by the system and all the data will be cleared and cannot be recovered.
﻿

Bantuan dan Dukungan

Apakah halaman ini membantu?

Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.

masukan

tencent cloud

Data Transfer Service

Payment Overdue

Overdue Payment Policy for Monthly Subscription Billing

Alert description

Repossession mechanism

Overdue Payment Policy for Pay-as-You-Go Billing

Alert description

Note

Repossession mechanism

Bantuan dan Dukungan

Time	Description
The 1st day after the expiration (within 24 hours)	You can continue using your instance. The system will send you an expiration reminder, and you need to renew it as soon as possible.
The 2nd-8th days after the expiration	You can’t use your instance any more. Your instance will be isolated and moved into the recycle bin, where it will be retained for seven days. You can renew it during this period. After shutdown, your instance will no longer be billed.
The 9th day after the expiration	The resources will be repossessed by the system and all the data will be cleared and cannot be recovered.

Time	Description
The 1st day after the overdue payment (within 24 hours)	You can continue using your pay-as-you-go instance. The system will send you a reminder for the overdue payment, and you need to top up your account balance as soon as possible.
The 2nd-8th days after the overdue payment	You can’t use your instance any more. Your instance will be isolated and moved into the recycle bin, where it will be retained for seven days. You can top up your account balance during this period. After shutdown, your instance will no longer be billed.
The 9th day after the overdue payment	The resources will be repossessed by the system and all the data will be cleared and cannot be recovered.