- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on Changing External Network Links
- Interface Authentication Upgrade Announcement
- Maintenance Time Change from Local Time to Beijing Time
- Account Type and Permission Changes
- Product Architecture Name Change
- Disk Storage Space Composition Change
- Ending Support for Classic Network [2022.12.31]
- Backup Billing Start [2022.07.10]
- Ending Sale for Basic Edition 1-Core Specification [2022.03.07]
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Constraints and Limits
- Usage Specifications and Suggestions
- Maintaining Instance
- Renaming Instance
- Setting Instance Remarks
- Setting Instance Tag
- Setting Instance Project
- Modify Instance-level Character Set Collation
- Modify System Time Zone
- Setting Instance Maintenance Information
- Multi-AZ Disaster Recovery
- Restarting Instance
- Terminating Instance
- Migrating Across AZs
- Manual Primary-Secondary Switching
- Recycle Bin
- Adjusting Instance Configuration
- Read-Only Instance
- Network and Security
- Account Management
- Database Management
- Data Security
- Parameter Configuration
- Monitoring and Alarms
- Backup and Restoration
- Log Management
- Publish-Subscribe
- SSIS
- Data Migration (New)
- Data Migration (Legacy)
- Best Practice
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance Management APIs
- CreateCloudDBInstances
- CreateCloudReadOnlyDBInstances
- ModifyInstanceEncryptAttributes
- UpgradeDBInstance
- RollbackInstance
- RestoreInstance
- RestartDBInstance
- ResetAccountPassword
- ModifyDBRemark
- ModifyDBName
- ModifyDBInstanceProject
- ModifyDBInstanceName
- ModifyAccountPrivilege
- InquiryPriceUpgradeDBInstance
- InquiryPriceCreateDBInstances
- DescribeZones
- DescribeRollbackTime
- DescribeRegions
- DescribeProductConfig
- DescribeFlowStatus
- DescribeDBs
- DescribeDBInstances
- DescribeAccounts
- DeleteDB
- DeleteAccount
- CreateDBInstances
- CreateDB
- CreateAccount
- TerminateDBInstance
- RecycleDBInstance
- CloneDB
- DescribeDBCharsets
- ModifyDatabaseMdf
- ModifyDatabaseCT
- ModifyDatabaseCDC
- DescribeDBsNormal
- ModifyInstanceParam
- DescribeInstanceParams
- DescribeInstanceParamRecords
- OpenInterCommunication
- DescribeDBInstanceInter
- DescribeBusinessIntelligenceFile
- DeleteBusinessIntelligenceFile
- CreateBusinessIntelligenceFile
- CreateBusinessDBInstances
- CloseInterCommunication
- Network Management APIs
- Backup APIs
- RunMigration
- ModifyMigration
- DescribeMigrations
- DescribeMigrationDetail
- DescribeBackups
- DeleteMigration
- CreateMigration
- CreateBackup
- ModifyBackupStrategy
- StartIncrementalMigration
- StartBackupMigration
- ModifyIncrementalMigration
- ModifyBackupMigration
- DescribeUploadBackupInfo
- DescribeIncrementalMigration
- DescribeBackupUploadSize
- DescribeBackupMigration
- DescribeBackupCommand
- DeleteIncrementalMigration
- DeleteBackupMigration
- CreateIncrementalMigration
- CreateBackupMigration
- DescribeBackupFiles
- Extended Event APIs
- Database APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- Overview
- Model Selection
- Pricing and Selection
- Connection and Network
- Account and Permission
- Backup and Rollback
- Data Migration
- Publish/Subscribe
- Read-Only Instance
- Version and Architecture Upgrade
- Disk Space and Specification Adjustment
- Monitoring and Alarms
- Log
- Parameter Modification
- Features
- Performance/Space/Memory
- Service Agreement
- Performance Evaluation
- Glossary
- Contact Us
- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on Changing External Network Links
- Interface Authentication Upgrade Announcement
- Maintenance Time Change from Local Time to Beijing Time
- Account Type and Permission Changes
- Product Architecture Name Change
- Disk Storage Space Composition Change
- Ending Support for Classic Network [2022.12.31]
- Backup Billing Start [2022.07.10]
- Ending Sale for Basic Edition 1-Core Specification [2022.03.07]
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Constraints and Limits
- Usage Specifications and Suggestions
- Maintaining Instance
- Renaming Instance
- Setting Instance Remarks
- Setting Instance Tag
- Setting Instance Project
- Modify Instance-level Character Set Collation
- Modify System Time Zone
- Setting Instance Maintenance Information
- Multi-AZ Disaster Recovery
- Restarting Instance
- Terminating Instance
- Migrating Across AZs
- Manual Primary-Secondary Switching
- Recycle Bin
- Adjusting Instance Configuration
- Read-Only Instance
- Network and Security
- Account Management
- Database Management
- Data Security
- Parameter Configuration
- Monitoring and Alarms
- Backup and Restoration
- Log Management
- Publish-Subscribe
- SSIS
- Data Migration (New)
- Data Migration (Legacy)
- Best Practice
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance Management APIs
- CreateCloudDBInstances
- CreateCloudReadOnlyDBInstances
- ModifyInstanceEncryptAttributes
- UpgradeDBInstance
- RollbackInstance
- RestoreInstance
- RestartDBInstance
- ResetAccountPassword
- ModifyDBRemark
- ModifyDBName
- ModifyDBInstanceProject
- ModifyDBInstanceName
- ModifyAccountPrivilege
- InquiryPriceUpgradeDBInstance
- InquiryPriceCreateDBInstances
- DescribeZones
- DescribeRollbackTime
- DescribeRegions
- DescribeProductConfig
- DescribeFlowStatus
- DescribeDBs
- DescribeDBInstances
- DescribeAccounts
- DeleteDB
- DeleteAccount
- CreateDBInstances
- CreateDB
- CreateAccount
- TerminateDBInstance
- RecycleDBInstance
- CloneDB
- DescribeDBCharsets
- ModifyDatabaseMdf
- ModifyDatabaseCT
- ModifyDatabaseCDC
- DescribeDBsNormal
- ModifyInstanceParam
- DescribeInstanceParams
- DescribeInstanceParamRecords
- OpenInterCommunication
- DescribeDBInstanceInter
- DescribeBusinessIntelligenceFile
- DeleteBusinessIntelligenceFile
- CreateBusinessIntelligenceFile
- CreateBusinessDBInstances
- CloseInterCommunication
- Network Management APIs
- Backup APIs
- RunMigration
- ModifyMigration
- DescribeMigrations
- DescribeMigrationDetail
- DescribeBackups
- DeleteMigration
- CreateMigration
- CreateBackup
- ModifyBackupStrategy
- StartIncrementalMigration
- StartBackupMigration
- ModifyIncrementalMigration
- ModifyBackupMigration
- DescribeUploadBackupInfo
- DescribeIncrementalMigration
- DescribeBackupUploadSize
- DescribeBackupMigration
- DescribeBackupCommand
- DeleteIncrementalMigration
- DeleteBackupMigration
- CreateIncrementalMigration
- CreateBackupMigration
- DescribeBackupFiles
- Extended Event APIs
- Database APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- Overview
- Model Selection
- Pricing and Selection
- Connection and Network
- Account and Permission
- Backup and Rollback
- Data Migration
- Publish/Subscribe
- Read-Only Instance
- Version and Architecture Upgrade
- Disk Space and Specification Adjustment
- Monitoring and Alarms
- Log
- Parameter Modification
- Features
- Performance/Space/Memory
- Service Agreement
- Performance Evaluation
- Glossary
- Contact Us
How do I back up TencentDB for SQL Server?
TencentDB for SQL Server has rich backup capabilities to guarantee the data security and prevent data loss or corruption. You can manage and view backups on the Backup Management page in the console. Specifically, you can configure automatic backup, manual backup, data backup, log backup, backup file format (unarchived files or archive file), instance backup, multi-database backup, and cross-region backup. You can also customize the backup policy, backup retention period (7–1,830 days), and backup cycle. For more information, see Backup Overview.
How do I configure automatic backup?
You can do so on the Backup Management page in the TencentDB for SQL Server console. For more information, see Configuring Automatic Backup.
How do I create a backup manually?
You can do so on the Backup Management page in the TencentDB for SQL Server console. For more information, see Creating Manual Backup.
How do I view and modify backup policies?
You can do so on the Backup Management page in the TencentDB for SQL Server console. For more information, see Configuring Automatic Backup.
How long can TencentDB for SQL Server retain a backup?
The retention period of TencentDB for SQL Server automatic backups is seven days by default and can be customized. The validity period is subject to the configured number of backup days. For more information, see Configuring Automatic Backup.
If not manually deleted, manual backups will be retained for the same period as automatic backups. You can delete them as instructed in Deleting Manual Backup.
Can I delete backups manually?
You can't delete automatic backups manually, but you can set the retention period for them so that they are deleted automatically upon expiration.
Manual backups can be manually deleted from the backup list in the TencentDB for SQL Server console. If they are not manually deleted, they will be retained for the same period as automatic backups.
Can I disable data and log backups?
No. However, you can lower the backup frequency and delete manual backup files that are no longer used in the TencentDB for SQL Server console to reduce the backup space usage.
Why can't I initiate a manual backup task?
You need to check the automatic backup time you configured. If the instance is performing the daily automatic backup task, you cannot initiate a manual backup task.
How do I cancel a backup task?
Backup tasks in TencentDB for SQL Server cannot be canceled.
Is a database available during the backup time period?
A backup window is a custom time period for daily automatic backup, during which the TencentDB for SQL Server instance will be backed up. Based on such regular backups, TencentDB for SQL Server allows you to roll back the instance to a backup point within the retention period. During the backup window, the business won't be affected, but you cannot restart or manually backup the instance in the TencentDB for SQL Server console.
How do I back up a database?
Log in to the TencentDB for SQL Server console, click the ID of the target instance in the instance list, select the Backup Management tab, click Backup Task Settings, and set Upload Backup File to Unarchived files. Then, the .bak file of each database in the instance will be directly uploaded to COS without being archived. For more information, see Setting Backup Task.
How do I set to perform a backup task on the replica instance in TencentDB for SQL Server?
Log in to the TencentDB for SQL Server console, click the ID of the target instance in the instance list, select the Backup Management tab, click Backup Task Settings, and set Execute Backup Task to On the replica node. For more information, see Setting Backup Task. You can configure this option only for 2017/2019 Cluster Edition instances.
How do I download backup files of TencentDB for SQL Server?
The TencentDB for SQL Server console provides the list of backup files that can be downloaded over the private or public network.
Log in to the TencentDB for SQL Server console, click the ID of the target instance in the instance list, select the Backup Management tab, and click Download in the Operation column of a backup file in the backup list to get its private/public network download addresses. You can also directly click Download to download the file. For more information, see Downloading Backup.
Can I use a third-party tool to automatically back up TencentDB for SQL Server?
TencentDB for SQL Server cannot be backed up with third-party tools. For security considerations, third-party tools cannot be granted the permissions of data directories on the physical machine. You can initiate backup tasks only in the console.
Can I download or restore backup files that exceed the retention period?
Expired backup sets will be automatically deleted and cannot be downloaded or restored.
We recommend that you configure a backup retention period based on business needs or download the backup files locally in the TencentDB for SQL Server console.
You can also manually back up instance data in the console. Manual backups will be retained permanently.
Note:
Manual backups will also take up the backup space. We recommend that you plan the usage of the backup space appropriately to reduce costs.
Can I download the backup files of an isolated instance?
Yes.
A pay-as-you-go instance will be isolated and moved into the recycle bin 24 hours after expiration. At this time, rollback and manual backup will be prohibited, but automatic backup can still be downloaded by clicking More in the Operation column of the instance. Excessive backup space of the instance will continue to be billed until the instance is eliminated.
Will backup files still be retained after a TencentDB for SQL Server instance is deleted?
After a TencentDB for SQL Server instance is deleted, all its backup files will be deleted automatically. To retain the data, back up the data first before deleting the instance.
How is the TencentDB for SQL Server backup space billed?
TencentDB for SQL Server offers a certain amount of backup space free of charge by region, which is equivalent to the sum of storage spaces of all Basic Edition, Dual-Server High Availability Edition, and Cluster Edition primary instances in a region. For the pricing of backup space beyond the free tier, see Backup Space Billing.
What should I do if the free tier of the backup space is exceeded?
If the size of backup files exceeds the free tier of the backup space, you can increase the storage space or reduce the backup space usage.
Instance backup files will use the backup space. Each TencentDB for SQL Server instance provides a certain free tier of backup space, and excessive usage will incur additional fees.
How do I reduce the backup space cost?
Delete manual backups that are no longer used. You can do so on the Instance Management > Backup Management page in the TencentDB for SQL Server console.
Reduce the frequency of automatic data backup for non-core businesses. You can adjust the backup cycle and backup file retention period in the console, which should be at least twice a week.
Note:
The rollback feature relies on the backup cycle and retention days of data backups and log backups. Rollback will be affected if you reduce the automatic backup frequency and retention period. You can select the parameters as needed. For more information, see Rolling back Databases.
Shorten the retention period of data and log backups for non-core businesses. A retention period of seven days can meet the needs in most cases.
Business Scenario | Recommended Backup Retention Period |
Core businesses | 7-1,830 days |
Non-core, non-data businesses | 7 days |
Archival businesses | 7 days. We recommend that you manually back up data based on your actual business needs and delete the backups promptly after use |
Testing businesses | 7 days. We recommend that you manually back up data based on your actual business needs and delete the backups promptly after use |
How do I view the backup space usage of TencentDB for SQL Server?
Log in to the TencentDB for SQL Server console and select Database Backup to view the backup space statistics and trends of all instances in each region under your account as well as the real-time backup space statistics of each instance. For more information, see Viewing Backup Space.
How do I roll back a TencentDB for SQL Server instance?
The retention period of TencentDB for SQL Server data backups is seven days by default and can be customized. The retention period of log backups is the same as that of data backups. You can roll back the instance data to any time point within the configured backup retention period. For more information, see Rolling back Database.
How do I clone a database in a TencentDB for SQL Server instance?
TencentDB for SQL Server provides the database cloning feature for you to quickly clone an existing database to your current instance. You need to specify the new database name during cloning, while other information such as account permissions of the new database is the same as that of the source database. For more information, see Cloning Database.
What can I do with downloaded data and log backups?
You can use backup files to restore data to other TencentDB or self-built databases at any time. For more information, see Cold Backup Migration.
Can I restore a downloaded backup to another TencentDB for SQL Server instance?
In the TencentDB for SQL Server console, you can use the cold backup migration feature to restore a database to another TencentDB for SQL Server instance from the downloaded backup file. For more information, see Cold Backup Migration.
How do I restore a backup of a self-built database to TencentDB for SQL Server?
In the TencentDB for SQL Server console, you can directly upload the backup file of a self-built database or download it from COS to restore it to TencentDB for SQL Server through the cold backup migration feature. For more information, see Cold Backup Migration.
Can I restore a full backup of TencentDB for SQL Server to a self-built database?
TencentDB for SQL Server supports full backup. After downloading a backup file, you can restore it to a self-built database as needed. For more information, see Downloading Backup.
What are the differences between direct backup upload and backup download from COS in cold backup migration?
Direct backup upload: You can upload a local backup file to COS and download and restore it to TencentDB for SQL Server. Backup files uploaded to COS don't use any backup space. However, they can be retained for only 24 hours and will be deleted automatically after then.
Backup download from COS: You can download a backup file from your COS bucket and restore it to TencentDB for SQL Server.
If I directly upload a backup file in cold backup migration, will the file use my backup space?
Backup files uploaded in backup and restoration scenarios are directly uploaded to COS for relay and don't use your backup space. Once successfully uploaded, they will be retained for only 24 hours and will be deleted automatically after then.
Yes
No
Was this page helpful?