Release Notes
Product Announcements
Rolling back to an existing instance (same region)
SQL Server offers a rollback tool to perform rollback operations on instances, and reconstructs historical data through regular backups and real-time transactions. This document describes how to roll back to other instances in the same region for single database, multiple databases, or all the databases according to a time point or a backup set.
Prerequisites
To utilize the rollback feature, there must be SQL Server instances. For instructions on the creation of instanes, please refer to Creating SQL Server Instance.
In order to use the rollback feature, a database must exist under an instance. For instructions on the creation of a database, see Creating a Database.
Points of Attention
Before initiating a rollback, please ensure there is sufficient storage space for an instance.
Ensure that no other tasks are being performed for the source instance before initiating a rollback.
The version of the target instance database after a rollback must be equal to or greater than the version of the source instance database. For instance, if the source instance is on the 2012 Enterprise version, it cannot be rolled back to a target instance on the 2008R2 Enterprise version. It can only be rolled back to an instance on the 2012 Enterprise version or above.
The architecture of the target instance after a rollback must match the architecture of the source instance. For example, a cloud disk version with two nodes can only be rolled back to a two-node instance of the same cloud disk version, not to a single-node instance of the cloud disk version or to a two-node local disk instance.
For example, a dual-node (cloud disk) instance can only be rolled back to another dual-node (cloud disk) instance instead of a single-node (cloud disk) instance or a dual-node (local disk) instance.
When you choose to overwrite the original database during a rollback operation, if the rollback database instance has a read-only instance, the read-only instance will resynchronize data. During the resynchronization period, operations cannot be performed on the read-only instance. After synchronization is completed, operations can be performed.
The steps are as follows:
1. Log in to the TencentDB for SQL Server console.
2. Select the Region on the top, locate the required instance, and click Instance ID or Manage in the Operation column to go to the instance management page.
3. On the right side, click Rollback, or navigate to Backup Management > Data Backup, locate the corresponding backup file, and click Rollback in the Operation column.
4. In the pop-up rollback settings interface, complete the corresponding configurations based on the selected rollback method and click Save.
Scenario One: Rollback by Time Point
Parameter | Description |
Select the target instance | Select Rollback to Existing instance. |
Target Instance Region | Select the same region as the source instance. |
Target Instance Name | Select the target instance for rollback, with quick search functionality by instance ID/instance name. The system supports fuzzy search and allows selection of cross-AZ instances within the same region. |
Select rollback mode | Select Rollback by Time Point. You can roll back the database to a specific time point from a source database instance. The time range dpends on the log backup retention period you set. |
Set rollback time | Select the rollback time. Please select "Beijing" time for the rollback operation. A uniform rollback time can only be set for databases for the same instance. |
Overwrite original database | Select whether the database to be rolled back needs to overwrite the original database. If you select Yes, once the rollback is successful: the original database will be renamed RESTORE_OLD_*_original database name. The new database obtained after the rollback will use the original database name.If the "Yes" option is left unchecked, after a successful rollback: the original database remains unchanged, while the newly rolled-back database will bear the user-defined name (defaulting to a system-generated name if not specified). |
Select the database to be rolled back | Select the database(s) to be rolled back, supporting single database, multiple databases, or selecting all databases for rollback. You can quickly filter databases by searching their names. If you choose not to overwrite the original database, the selected database(s) can be renamed under the "Rollback Database" section on the right. If no renaming is performed, the system will automatically generate a new database name with the format of a prefix followed by the original database name. The rolled-back database name only supports "letters", "numbers", "_", or "-", must start with a letter, and can contain up to 128 characters. If you choose to overwrite the original database, renaming under the "Rollback Database" section is not required. |
Scenario Two: Rollback by Backup Set
Parameter | Description |
Select the target instance | Select Rollback to Existing instance. |
Target Instance Region | Select the same region as the source instance. |
Target Instance Name | Select the target instance that you want to roll back to. You can perform a quick search based on the instance ID or name. Instances across Availability Zones in the same region are supported. |
Select rollback mode | Select Rollback by Backup Set. |
Select replica set | Select the backup set for rollback. You can restore a new database from the specified backup set. The range of available backup sets is determined by the data backup retention period you have configured. When the backup file is in the form of a single database backup, the database name within the backup file will be displayed in the search bar. |
Overwrite original database | Select whether the database to be rolled back needs to overwrite the original database. If you select Yes, once the rollback is successful: the original database will be renamed RESTORE_OLD_*_original database name. The new database obtained after the rollback will use the original database name. If the "Yes" option is left unchecked, after a successful rollback: the original database remains unchanged, while the newly rolled-back database will bear the user-defined name (defaulting to a system-generated name if not specified). |
Select the database to be rolled back | Select the database(s) to be rolled back, supporting single database, multiple databases, or selecting all databases for rollback. You can quickly filter databases by searching their names. If you choose not to overwrite the original database, the selected database(s) can be renamed under the "Rollback Database" section on the right. If no renaming is performed, the system will automatically generate a new database name with the format of a prefix followed by the original database name. The rolled-back database name only supports "letters", "numbers", "_", or "-", must start with a letter, and can contain up to 128 characters. If you choose to overwrite the original database, renaming under the "Rollback Database" section is not required. |
Related APIs
API | Description |
This API is used to roll back the database by backup set. | |
This API is used to query the list of rollback tasks. | |
This API is used to delete rollback task records. |
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback