Restore Database

CloudBase provides comprehensive database backup and restore features, ensuring the security and reliability of your data, and supporting quick recovery in case of accidental data loss or erroneous operations.

Backup Mechanism

Automatic Backup Feature

Feature	Description	Advantage
Automatic Enablement	The system enables the backup feature by default	No manual configuration required; ready to use out of the box
Daily Backup	Automatically performs backups daily in the early morning	Ensures continuous data protection
Retention Period	Backup data is retained for up to 14 days	Provides an adequate recovery time window
Zero Downtime	The backup process does not affect business access	Ensures business continuity

Core Value

• Data Security: Automatic backup mechanism prevents data loss.
• Rapid Recovery: Supports point-in-time data restore
• Business Continuity: The restore process does not affect normal data access
• Flexible Operation: Supports selective restore for single or multiple collections

Backup Policy Details

Backup Schedule

Daily backup time: 2:00 AM - 4:00 AM
Backup frequency: daily
Retention policy: Rolling retention of the last 14 days

Backup Data Scope

• Includes: all collection data, index structures, and document content
• Data Integrity: Ensures the consistency and integrity of backup data

Recovery Point

Time Range	Recovery Precision	Description
Last 24 hours	Minute-level precision	Supports precise point-in-time recovery
2-7 days ago	Hour-level precision	Based on daily backup data
8-14 days ago	Day-level precision	Historical backup data recovery

Restore Data Operation

Operation Process

Step 1: Access the restore feature

1. Log in to the console: Access the Tencent Cloud Development Platform
2. Go to the database: Switch to Cloud Development Platform/Database Management
3. Start the restore: Click the "Database Restore" button

Step 2: Configure restore parameters

Time point selection:

• Select the specific time point for restore
• Display available backup time range

Collection selection:

• Supports restore for single or multiple collections

Step 3: Set restore collection name

Naming rules:

Configuration Item	Description	Example
Default Naming	Original collection name + _bak suffix	users → users_bak
Custom Naming	Manually specify the restored collection name	users_backup_20240115
Naming Restrictions	Must not duplicate existing collection names	The system will automatically check for conflicts

Step 4: Execute the restore task

Task Management:

• Click "OK" to start the restore task
• The system displays the restore progress and status

Concurrency Limit:

• Only one restore task can be executed at the same time
• New tasks must wait for the current task to complete
• Avoid data conflicts and resource contention

Post-Restore Operations

Step 4: Execute the rollback task

1. Check the collection list: Confirm that the restore collection has been created
2. Verify Data Integrity: Spot-check whether key data is correct
3. Test Application Features: Ensure the business logic operates normally
4. Compare Data Differences: Analyze data changes before and after the restore

Follow-up Procedures

Data Switchover:

// If the restored data is correct, consider replacing the original collection
// 1. Back up the current collection (by renaming)
// 2. Rename the restore collection to the original name
// 3. Update the application configuration

Cleanup Tasks:

• Delete unneeded temporary collections
• Clean up test data
• Update relevant documentation and configurations