Thursday, July 4, 2013
On 3 July 2013 20:25, Robert Walker <lists@ruby-forum.com> wrote:
-- A robust solution is to use database replication and then run your
backups off the replica, This way you have at least two servers that are
kept synchronized constantly, Backups of the replica will also not
impact the performance of the application accessing the source database.
We tried that, we use PostgreSQL and londiste, but when it decided to break it stayed broken. I spent weeks trying to get things to work again once it failed. That was only 2 databases, what would happen for the >25 databases that we have?
Unless someone dumps a large amount of cash in my lap I have to improve the situation we are in with what we have to hand rather than throwing money around.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CALxYQy6aUX59zG%2Bq1xN8BRBaq34nEShJi6aMVuk%2BSyXZQtsMkA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment