On 4 July 2013 11:43, Peter Hickman wrote:
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.
On 3 July 2013 20:25, Robert Walker 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 toA 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.
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.
various kinds of replication - both internal streaming and Londiste work
very well for many people, so those technology choices are good ones.
Probably trite to say time = money; I do recognise that the functional
relationship between time and money differs for everybody. In general the
open source ecosystem does have a place for companies that specialise in
building, maintaining and supporting system software to assist in cases
like this.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
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/CA%2BU5nMJ7CSGinY7uT1-mAeesW93UwrdWfJfN%3D5ucKCT%3DQ%3DKMkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
