Hey Heroku guys, just bumping this thread. To summarize: do we need to do automated regular backups to protect against Postgres or some other part of Heroku infrastructure going down, or is the database guaranteed to be reliable?
I'm guessing we do, and if so how do we do that since an hourly dump of postgres via cron isn't reliable enough or scalable? (i.e. you can lose up to an hour of data, and more as the dump starts to take longer with a large dataset.) Thanks. On Nov 12, 9:54 am, Paul Dowman <[email protected]> wrote: > Hi, > > I'm having trouble understanding database disaster risk and recovery > options. (I'm not asking about archiving a copy of the database). I > don't see any mention of RAID, and while your marketing page mentions > replication there's nothing in the docs about it (http:// > docs.heroku.com/search?q=replication) so I don't understand if and how > we can enable this. > > So is it guaranteed that the data will remain available (unless our > app does something to screw it up)? i.e. there won't be any > unrecoverable failure of the Heroku platform that results in data > loss? > > Or do we need to manage this ourselves? All I can find in your > documentation is instructions on how to manually back up the database. > Obviously that can be done by cron, but a) cron runs hourly at most > and b) a full dump of a database isn't a good way to keep it > continuously backed up unless the dataset is tiny. > > Again, I'm just talking about disaster recovery from a platform > failure. Obviously there's a risk that I'd screw up my own data with a > bug or bad migration, but I'm OK with taking a snapshot less > frequently to guard against that. > > Thanks, > Paul -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
