docs: update backup doc

Author: tianzhou

content/docs/change-database/rollback-data-changes.md

@@ -14,18 +14,48 @@ You can manually delete the data in `bbdataarchive` database/schema.
 
 </HintBlock>
 
-Prior backup is only feasible when meeting **any** of the following conditions:
+## Supported Databases
+
+| Database   | Prerequisites                                                                         | Prior Backup | 1-click Rollback |
+| ---------- | ------------------------------------------------------------------------------------- | ------------ | ---------------- |
+| MySQL      | Create a `bbdataarchive` **database** on the instance where your database is located. | ✅           | ✅               |
+| PostgreSQL | Create a `bbdataarchive` **schema** on the database.                                  | ✅           | ✅               |
+| Oracle     | Create a `bbdataarchive` **database** on the instance where your database is located. | ✅           | ❌               |
+| SQL Server | Create a `bbdataarchive` **database** on the instance where your database is located. | ✅           | ✅               |
+
+## Supported Operations
+
+We are working on removing more limitations preventing backup and 1-click rollback.
+
+### Enhanced experience
+
+<HintBlock type="info">
+
+Applicable to `MySQL`.
+
+</HintBlock>
+
+Prior backup is feasible when meeting **any** of the following conditions:
+
+1. The SQL size is less than 2M.
+
+1-click rollback is feasible when meeting **any** of the following conditions:
+
+1. The changed table has primary key.
+
+### Classic experience
+
+<HintBlock type="info">
+
+Applicable to `PostgreSQL`, `Oracle`, `SQL Server`.
+
+</HintBlock>
+
+Prior backup is feasible when meeting **any** of the following conditions:
 
 1. No more than 5 statements and every statement is either `UPDATE` or `DELETE`.
 1. All statements are `UPDATE` for the same table with `PRIMARY KEY` or `UNIQUE KEY` in `WHERE` clause.
 
-| Database   | Prerequisites                                                                         | 1-click Rollback |
-| ---------- | ------------------------------------------------------------------------------------- | ---------------- |
-| MySQL      | Create a `bbdataarchive` **database** on the instance where your database is located. | ✅               |
-| PostgreSQL | Create a `bbdataarchive` **schema** on the database.                                  | ✅               |
-| Oracle     | Create a `bbdataarchive` **database** on the instance where your database is located. | ❌               |
-| SQL Server | Create a `bbdataarchive` **database** on the instance where your database is located. | ✅               |
-
 ## Create backup
 
 You can toggle **Prior Backup** switch before or after creating the issue.

content/docs/reference/error-code/advisor.md

@@ -390,7 +390,4 @@ The comment missing classification. Check [Comment classification](/docs/securit
 
 <h3 id="2001">2001 - Unable to create backup</h3>
 
-[Prior backup](/docs/change-database/rollback-data-changes) is only feasible when meeting **any** of the following conditions:
-
-1. No more than 5 statements and every statement is either `UPDATE` or `DELETE`.
-1. All statements are `UPDATE` for the same table with `PRIMARY KEY` or `UNIQUE KEY` in `WHERE` clause.
+See [Supported backup operations](/docs/change-database/rollback-data-changes/#supported-operations).