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/installation-steps-advanced/BackupRestoreGuide.md
+36-5
Original file line number
Diff line number
Diff line change
@@ -32,27 +32,58 @@ Explanation:
32
32
-`pg_dump -U $DB_USER -d $DB_NAME`: Initiates the PostgreSQL dump, specifying the username and database name.
33
33
-`> reportportal_db_backup.sql`: Redirects the dump output to a file named `backup.sql`.
34
34
35
-
Make sure to replace placeholders like `DB_CONTAINER`, `DB_USER`, and `DB_NAME` with your actual container pod name, PostgreSQL username, and database name.
35
+
Make sure to replace placeholders like `DB_CONTAINER`, `DB_USER`, and `DB_NAME` with your container pod name, PostgreSQL username, and database name.
36
36
37
37
### PostgreSQL Restore Process
38
38
39
-
To restore PostgreSQL database using following command:
39
+
:::important
40
+
Ensure that PostgreSQL is running as a standalone service before starting ReportPortal. Deploy ReportPortal only after the database has been successfully restored
41
+
:::
42
+
43
+
#### 1. Deploy PostgreSQL as a Standalone Service
44
+
45
+
Start the PostgreSQL container using Docker Compose:
40
46
41
47
```bash
48
+
docker compose up -d postgres
49
+
```
50
+
51
+
> This brings up only the `postgres` service defined in your `docker-compose.yml`.
0 commit comments