Heroku Postgres has two levels of backup protection. The first level is called ‘Continuous Protection’, and this involves storing the Postgres Write Ahead Logs (transaction logs) on S3, using the open source utility WAL-E. The Continuous Protection feature allows Heroku to restore or rebuild your database in the event of a failure. The second level is logical backups, using the...
Remora Backup was designed with security and trust as the top priorities. When designing and planning the service, we asked ourselves “what is the least amount of access we need to our customer’s database?”. The answer turned out to be a simple, but powerful Heroku feature called Postgres Credentials. A Postgres database provides many types of access controls, from host-based...
When building Remora Backup, we set out to build a secure, simple, offsite backup service that would continue to run and serve customers for many years into the future. We decided early on to not roll our own backup utility. We would use standard Postgres tools such as pg_backup, as well as simple, open source utilities such as scp for...
We created Remora Backup to answer a question we kept encountering on our own Heroku projects: How do we reliably and securely store an offsite backup of our Postgres data? We love Heroku. We’ve built many projects and businesses over the last 10+ years that run on and rely on Heroku. We also understand that Heroku is built on AWS,...