Change example

Signed-off-by: Xuanwo <[email protected]>

Author: Xuanwo

docs/en/guides/90-community/02-rfcs/20250109-disaster-recovery.md

@@ -47,29 +47,29 @@ RESOTRE DATABASE
 For example, users can backup the `test` table to an external stage:
 
 ```sql
-BACKUP TABLE test INTO @backup_stage/table/test/2025_01_09_08_00_00/;
+BACKUP TABLE test INTO 's3://bucket_bucket/table/test/2025_01_09_08_00_00/';
 ```
 
 `BACKUP` supports both full and incremental backups. The full backup will back up all metadata and data, while the incremental backup will only back up the changes since the last full or incremental backup.
 
 `BACKUP` will perform incremental backups by default. Users can specify the `FULL` keyword to perform a full backup:
 
 ```sql
-BACKUP TABLE test INTO @backup_stage/table/test/2025_01_09_08_00_00/ FULL;
+BACKUP TABLE test INTO 's3://bucket_bucket/table/test/2025_01_09_08_00_00/' FULL;
 ```
 
 The backup will store all relevant metadata and data in the backup storage, ensuring that users can restore it even if the entire databend cluster is lost.
 
 Users can restore the `test` table from the external stage in another databend cluster:
 
 ```sql
-RESOTRE TABLE FROM @backup_stage/table/test/2025_01_09_08_00_00/;
+RESOTRE TABLE FROM 's3://bucket_bucket/table/test/2025_01_09_08_00_00/';
 ```
 
 `RESTORE` also supports `DRY RUN` to preview the restore operation without actually restoring the metadata and data.
 
 ```sql
-RESOTRE TABLE FROM @backup_stage/table/test/2025_01_09_08_00_00/ DRY RUN;
+RESOTRE TABLE FROM 's3://bucket_bucket/table/test/2025_01_09_08_00_00/' DRY RUN;
 ```
 
 Users can use `DRY RUN` to check and validate the backup without affecting the existing metadata and data.
@@ -83,23 +83,23 @@ Databend will provide a set of system functions to manage the backups:
 SELECT list_backups(
     -- full identifier of the database or table,
     'test',
-    location => '@backup_stage/table/test/'
+    location => 's3://bucket_bucket/table/test/'
 );
 
 -- delete backup in given location
 SELECT delete_backup(
     -- full identifier of the database or table,
     'test',
     -- the location to search the backups.
-    location => '@backup_stage/table/test/2025_01_09_08_00_00/'
+    location => 's3://bucket_bucket/table/test/'
 );
 
 -- vacuum backup in given location to meet the retention policy.
 SELECT vacuum_backup(
     -- full identifier of the database or table,
     'test',
     -- the location to search the backups.
-    location => '@backup_stage/table/test',
+    location => 's3://bucket_bucket/table/test/',
     -- keep recent 30 days backups
     RETENTION_DAYS => 30,
     -- keep at least for 7 days.