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
`pgmoneta-cli s3 restore` downloads the backup metadata and data files from S3, stages them locally, and then restores the backup into the requested target directory using the normal restore workflow.
149
+
142
150
## Per-Server Configuration
143
151
144
152
All S3 configuration settings can be specified within a server's configuration section. This allows you to use different S3 buckets, credentials, or even regions for different PostgreSQL servers.
Copy file name to clipboardExpand all lines: doc/manual/en/09-restore.md
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,18 +96,15 @@ This command take the latest backup and all Write-Ahead Log (WAL) segments and r
96
96
97
97
## Restore from S3
98
98
99
-
If your backups are stored in S3, you first need to download them to the local backup directory using `pgmoneta-cli s3 restore`, then restore normally.
99
+
If your backups are stored in S3, you can restore them directly using `pgmoneta-cli s3 restore`.
This downloads the backup files from S3, verifies `backup.info` integrity via SHA512, and places the backup in the local backup directory.
108
-
109
-
Step 2: Restore the backup
110
-
107
+
This stages the backup files from S3, verifies `backup.info` integrity via SHA512, restores the backup into the requested target directory, and removes the staged local copy after success.
111
108
```
112
109
pgmoneta-cli restore primary 20260316000957 current /tmp
`pgmoneta-cli s3 restore` downloads all files from S3 for the given backup labelinto the local backup directory.
109
+
`pgmoneta-cli s3 restore` downloads all files from S3 for the given backup label, stages them locally, and restores the backup into the requested target directory using the standard restore workflow.
110
110
111
-
Metadata files (`backup.info`, `backup.sha512`, `backup.manifest`) are downloaded as temporary files first, then renamed in order after all data files are restored. `backup.info` is renamed last and its presence marks a complete restore.
111
+
Metadata files (`backup.info`, `backup.sha512`, `backup.manifest`) are downloaded as temporary files first. `backup.info` is verified before file download starts, then renamed into place so the staged backup metadata matches the downloaded objects before the restore workflow runs.
0 commit comments