Note:
Rollback to the original instance supports the operation of database-level objects.
For instances of SQL Server compatible engines, the rollback of mssql_compatible databases is currently not supported.
Up to 100 databases can be selected for a single rollback task.
Rollback to the original instance allows you to restore existing database objects in the current instance to a specific point in time or backup set. It can also solve the problem of recovering accidentally deleted databases. A detailed description is provided below.
Selecting the Recovery Method and Time Point
Note:
The selectable time for database table recovery is strongly related to your current backup retention policy. For backup settings, refer to Instructions. You can choose to recover to a specific backup set or to any point in time when the system detects data.
Selecting the Database to Recover
You can select an existing database pulled by the current system for recovery. Details are shown in the figure below:
Name after Recovery
The name of the recovered database will have a *_bak_timestamp suffix. The timestamp is a Unix timestamp when a backend task is initiated. After you submit a database table rollback task on the console or via API, the backend will initiate a rollback task within 5 minutes. For example, if the database name selected by you is dbone and the backend initiates the task at 2024-05-30 11:26:25, the new database name after the recovery task is completed will be dbone_bak_1717039585.
Handling Accidental Database Deletion
If a database is deleted due to misoperation, the database table rollback feature can resolve this problem. Since the deleted database cannot be retrieved when a task is initiated, you can start the task by adding a new database. Click Add in the figure below.
Note:
If the added database name does not exist in the selected backup set or PITR time point, an empty database will be recovered.
Was this page helpful?