You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Olivier Cuypers e110cb4ec9 Exclude sys & innodb databases on mysql-backup-s3 8 years ago
..
Dockerfile Upgrade alpine version from 3.2 to 3.4 for pgbackup images 8 years ago
README.md Update readme for postgres restore 9 years ago
install.sh Use alpine:3.2 & postgres 9.4 9 years ago
restore.sh postgres-restore-s3 9 years ago

README.md

postgres-restore-s3

Restore a SQL backup from S3 to PostgresSQL

Warning

This will potentially put your database in a very bad state or complete destroy your data, be very careful.

Limitations

This is made to restore a backup made from postgres-backup-s3, if you backup came from somewhere else please check your format.

  • Your s3 bucket must only contain backups which you wish to restore - it will always grabs the 'latest' based on unix sort with no filtering
  • They must be gzip encoded text sql files
  • If your bucket has more than a 1000 files the latest may not be restore, only one s3 ls command is made

Usage

Docker:

$ docker run -e S3_ACCESS_KEY_ID=key -e S3_SECRET_ACCESS_KEY=secret -e S3_BUCKET=my-bucket -e S3_PREFIX=backup -e POSTGRES_DATABASE=dbname -e POSTGRES_USER=user -e POSTGRES_PASSWORD=password -e POSTGRES_HOST=localhost schickling/postgres-restore-s3

Dropping public

If you wish to drop the public schema (drop schema public cascade; create schema public) then set the environment variable DROP_PUBLIC=yes. This is useful for situations where you wish to restore a database which currently has data / schemas in it.