You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/tutorial/backup-restore.md
+22-6Lines changed: 22 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,16 +38,14 @@ BACKUP DATABASE my_database TO 's3://my_bucket/my_database/'
38
38
39
39
## Restore
40
40
41
-
### Current Limitation
42
-
43
-
Currently, MyDuck Server supports only a single database (catalog). Therefore, restore operations are performed only at startup. Future updates will enable support for multiple databases, allowing restore operations via SQL commands.
44
-
45
41
### Restore Process
46
42
47
-
To restore a database, download the backup file (`mysql.db`) and attach it during the startup of MyDuck Server.
43
+
To restore a database, download the backup file (`mysql.db`) and attach it.
48
44
49
45
**Note:** Backup files created by either MyDuck Server or DuckDB can be used to restore MyDuck Server.
50
46
47
+
### Restore at Startup
48
+
51
49
#### Docker Usage
52
50
53
51
Use the following Docker command to run MyDuck Server with restore parameters:
@@ -103,4 +101,22 @@ Run MyDuck Server with the following command-line arguments to perform a restore
0 commit comments