Data Transfer Service
- Release Notes and Announcements
- Announcements
- Product Introduction
- Specification Description
- Preparations
- Network Preparation
- Interworking Between local IDC and Tencent Cloud
- Adding DTS IP Addresses to the Allowlist of the Corresponding Databases
- DTS Service Permission Preparation
- Data Migration
- Migration to MySQL Series
- Migrating to MySQL
- Migrating to MariaDB
- Migrating to TDSQL-C for MySQL
- Migrating to TDSQL MySQL
- Migrating to TDSQL TDStore
- Advanced Operations for MySQL Series Migration
- Processing for MySQL Series Pre-Check Failure
- Migrating to PostgreSQL
- Processing for PostgreSQL Series Pre-Check Failure
- Migrating to MongoDB
- Migration from MongoDB to MongoDB
- Fix for Verification Failure
- MongoDB Data Consistency Verification
- Migrating to SQL Server
- Migration from SQL Server to TencentDB for SQL Server
- Pre-Validation Failure Handling
- Migrating to TencentDB for Redis
- Migration from Redis to Redis
- Fix for Verification Failure
- Migrating to KeeWiDB
- Migration from Redis to KeeWiDB
- Task Management
- Data Sync
- Sync to MySQL series
- Sync to MySQL
- Sync to MariaDB
- Sync to TDSQL-C for MySQL
- Sync to TDSQL for MySQL
- Sync from TDSQL for MySQL to TDSQL for MySQL
- Sync to TDSQL TDStore
- MySQL Series Advanced Sync Operations
- MySQL series Pre Validation Failed Processing
- Synchronize to PostgreSQL
- PostgreSQL Pre Validation does not Pass Processing
- Synchronize to Kafka
- MySQL/MariaDB/Percona/TDSQL-C MySQL Sync to Kafka
- TDSQL MySQL Sync to Kafka
- Task Management
- Data Subscription (Kafka Edition)
- MySQL series Data Subscription
- Consuming MySQL Data
- Advanced Subscription Operations
- Fix for Verification Failure
- Data Subscription for TDSQL PostgreSQL
- Fix for Verification Failure
- MongoDB Data Subscription
- Fix for Verification Failure
- Task Management
- Consumption Management
- Fix for Verification Failure
- Monitoring and Alarms
- Configuring Metric Alarms and Event Alarms via the Console
- Practical Tutorial
- FAQs
- Error Handling
- API Documentation
- Making API Requests
- (NewDTS) Data Migration APIs
- Data Sync APIs
- Data Consistency Check APIs
- (NewDTS) Data Subscription APIs
- DTS API 2018-03-30
- Data Subscription APIs
- Making API Requests
- DTS APIs
- Service Agreement
DocumentationData Transfer ServiceData MigrationMigrating to SQL ServerMigration from SQL Server to TencentDB for SQL ServerPre-Validation Failure HandlingDisk Space Check
Disk Space Check
Last updated: 2024-09-25 11:21:03
Check Details
Check whether the disk space on the server of the source database is sufficient. During migration of a self-built source instance, at least 50 GB disk space should be reserved on the server of the source database. We recommend you reserve a space at least 1.5 times the size of the migration data to avoid errors; otherwise, an error will be reported with the error details: "Check whether the disk space on the destination server is sufficient.".
Fixing Method
If a disk space check error is reported: "Check whether the disk space on the destination server is sufficient," please check the purchased disk space size of the target instance. It is recommended that the disk space of the target instance is not smaller than the disk space of the source instance, preferably 1.5 times the size of the source instance's disk space. You can expand the disk space size of the target instance through the Adjusting Instance Specification feature in the console.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No