Files
pg-bkup/docs/how-tos/restore-from-s3.md

49 lines
1.4 KiB
Markdown
Raw Normal View History

2024-08-03 00:49:14 +02:00
---
title: Restore database from AWS S3
layout: default
parent: How Tos
2024-09-30 00:00:21 +02:00
nav_order: 6
2024-08-03 00:49:14 +02:00
---
# Restore database from S3 storage
2024-08-10 09:39:50 +02:00
To restore the database, you need to add `restore` command and specify the file to restore by adding `--file store_20231219_022941.sql.gz`.
2024-08-03 00:49:14 +02:00
{: .note }
It supports __.sql__,__.sql.gpg__ and __.sql.gz__,__.sql.gz.gpg__ compressed file.
2024-08-03 00:49:14 +02:00
### Restore
```yml
services:
pg-bkup:
# In production, it is advised to lock your image tag to a proper
# release version instead of using `latest`.
# Check https://github.com/jkaninda/pg-bkup/releases
# for a list of available releases.
image: jkaninda/pg-bkup
container_name: pg-bkup
2024-08-10 09:39:50 +02:00
command: restore --storage s3 -d my-database -f store_20231219_022941.sql.gz --path /my-custom-path
2024-08-03 00:49:14 +02:00
volumes:
- ./backup:/backup
environment:
- DB_PORT=5432
- DB_HOST=postgres
- DB_NAME=database
- DB_USERNAME=username
- DB_PASSWORD=password
## AWS configurations
- AWS_S3_ENDPOINT=https://s3.amazonaws.com
- AWS_S3_BUCKET_NAME=backup
- AWS_REGION="us-west-2"
- AWS_ACCESS_KEY=xxxx
- AWS_SECRET_KEY=xxxxx
## In case you are using S3 alternative such as Minio and your Minio instance is not secured, you change it to true
- AWS_DISABLE_SSL="false"
2024-10-18 08:48:29 +02:00
- AWS_FORCE_PATH_STYLE="false"
2024-08-03 00:49:14 +02:00
# pg-bkup container must be connected to the same network with your database
networks:
- web
networks:
web:
2024-10-10 21:18:36 +02:00
```