tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
TencentDB for SQL Server
    Documentation
    Download PDF

    Rollback to an Existing Instance (Cross-Region)

    Last updated: 2024-01-18 17:23:30
    Download PDF
      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 across different regions for single database, multiple databases, or all the databases according to a time point or a backup set.
      Note:
      Rolling back to another instance across regions refers to realizing cross-region recovery through cross-region backups for the purpose of remote disaster recovery. For example, if an instance in region A has enabled the cross-region backup function and its backup files are stored in region B, when the instance encounters a failure or damage, the cross-region backup files can be restored to an instance in region B by using the rollback function.

      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.
      Cross-region backups must have been enabled. Cross-region backup files must have been generated. Please refer to Cross-Region Backup.

      Points of Attention

      Before initiating a rollback, please ensure there is sufficient storage space for an instance.
      Ensure that no other tasks are 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.

      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. Select the Backup Management tab, and then either click Rollback in the upper right corner of the backup management page or click Rollback in the Data Backup List 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 rollback to the region where other instances are.
      Target Instance Name
      Select the cross-region target instance after a rollback. You can quickly search by instance ID or instance name. Instances across Availability Zones in the selected region are supported.
      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. 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_*_OriginalDatabaseName. The new database obtained after the rollback will use the original database name. If you select No, once the rollback is successful, the original database remains unchanged. The name of the new database obtained after the rollback is user-defined (the default name is system-generated).
      
      Select the database to be rolled back
      Select the database that needs to be rolled back. The rollback of single database, multiple databases and all the databases is supported. The search function is available for quick filtering by database name. The selected databases can be renamed under the Selected Database section on the right. If they are not renamed, the created databases from the rollback will, by default, have system-generated names, with the form of prefixes and the original database names. The database name after rollback can only contain up to 128 characters, including digits, case-sensitive English letters, and special symbols (`-_./()[]()+=::@`). It must begin with an English letter.
      
      Scenario Two: Rollback by Backup Set
      
      Parameter
      Description
      Select the target instance
      Select Rollback to Existing instance.
      Target Instance Region
      Select rollback to the region where other instances are.
      Target Instance Name
      Select the cross-region target instance after a rollback. You can quickly search by instance ID or instance name. Instances across Availability Zones in the selected region are supported.
      Select rollback mode
      Choose Rollback by Backup Set.
      Note:
      You can roll back a new database from a specific backup set, with the selection range determined by the data backup retention period you have set.
      
      Select replica set
      Select the backup set for rollback.
      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_*_OriginalDatabaseName. The new database obtained after the rollback will use the original database name.
      If you select No, once the rollback is successful, the original database remains unchanged. The name of the new database obtained after the rollback is user-defined (the default name is system-generated).
      Select the database to be rolled back
      Select the database that needs to be rolled back. The rollback of single database, multiple databases and all the databases is supported. The search function is available for quick filtering by database name. The selected databases can be renamed under the Selected Database section on the right. If they are not renamed, the created databases from the rollback will, by default, have system-generated names, with the form of prefixes and the original database names.
      Note:
      The database name after rollback can only contain up to 128 characters, including digits, case-sensitive English letters, and special symbols (`-_./()[]()+=::@`). It must begin with an English letter.
      
      5. After confirming the rollback time or backup set and the databases that need to be rolled back, click Save in the pop-up window.
      6. In the Rollback Task List, when the task status changes into In Progress, you can view the rollback progress by clicking on the task icon at the top right corner of the Backup Management page.
      
      
      Contact Us

      Contact our sales team or business advisors to help your business.

      Contact Us
      Technical Support

      Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

      Submit a Ticket
      7x24 Phone Support
      Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
      Privacy PolicyLegalCookie Policy