Skip to content

Commit 9e7981e

Browse files
authored
chore: add note re: change in logical restore requirements (supabase#20425)
1 parent a4f86bc commit 9e7981e

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

apps/docs/pages/guides/platform/backups.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,8 @@ When selecting a backup to restore to, select the closest available one made bef
6868

6969
The Dashboard will then prompt for a confirmation before proceeding with the restoration. The project will be inaccessible following this. As such, do ensure to allot downtime beforehand. This is dependent on the size of the database. The larger it is, the longer the downtime will be. Once the confirmation has been given, the underlying SQL of the chosen backup is then run against the project. The PostgreSQL utility [psql](https://www.postgresql.org/docs/current/app-psql.html) is used to facilitate the restoration. The Dashboard will display a notification once the restoration completes.
7070

71+
If your project is using subscriptions or replication slots, you will need to drop them prior to the restoration, and re-create them afterwards. The slot used by Realtime is exempted from this, and will be handled automatically.
72+
7173
{/* screenshot of the Dashboard of the project completing restoration */}
7274

7375
## Point-in-Time recovery

0 commit comments

Comments
 (0)