It's not easy but you can configure RHEL (Or CentOS - I don't know which one he runs), GFS (Sistina code), and two servers configured for failover.
Lots of time, work, and a few bucks, for the second server (CentOS is free) but it's doable and it eliminates server hardware issues - but it doesn't eliminate database issues. For that, you still need backups. If he's running Debian or SLES - there are other solutions. Maybe I'm rambling too much... On Dec 29, 10:32 pm, hibikir <[email protected]> wrote: > You don't even have to go for a for-pay database to get less data loss > issues than with MySQL: We run both Postgres and MySQL at work, and > the Postgres databases perform like champs. We'd migrate everything, > but there's a lot of code that would have to end up being rewritten, > if just for the little SQL incompatibilities. > > On Dec 29, 10:23 pm, "XanderF (Naval | Gamer)" <[email protected]> > wrote: > > > Bah. Enterprise-level database software for Enterprise-sized > > databases. > > > Company I work for (?do I need to provide a disclaimer about 'opinions > > of individual, not speaking for company' and such?) moved off from > > MySQL a year or more ago even for our smaller sites due to instability > > and corruption regardless of database size and transaction volume. > > Heck, last TWO companies I worked for moved off MySQL - one to MS-SQL, > > and the other to Oracle SQL. > > > It's just too flakey. > > > On Dec 29, 8:12 pm, Luis <[email protected]> wrote: > > > > Aw, come on. Kicking around mysql isn't nice. It's no postgresql, > > > but it's serviceable. > > > > Bigger sites than BGG run on mysql. > > > > On Dec 29, 9:04 pm, "XanderF (Naval | Gamer)" <[email protected]> > > > wrote: > > > > > No, 'stick of ram' is still it - it's just, with a database issue - > > > > ESPECIALLY using rather shoddy MySQL - ram corruption *could* also > > > > mean database corruption. And with MySQL, database corruption often > > > > means - restore from backup. (mysqlcheck does work - sometimes - > > > > depends on how much got hosed) > > > > > On Dec 29, 7:18 pm, anglotiger <[email protected]> wrote: > > > > > > Did I miss something? I remember him describing it as a memory > > > > > problem - that's potentially a far more serious issue than a just a > > > > > stick of RAM... > > > > > > On Dec 29, 9:10 pm, Luis <[email protected]> wrote: > > > > > > > Aldie said it was a stick of RAM, not drive failures. > > > > > > > On Dec 29, 8:03 pm, BillJ <[email protected]> wrote: > > > > > > > > Data loss. Yikes, I hadn't considered how deep that the loss > > > > > > > might > > > > > > > go. A deep one that goes far back in time would be a scary > > > > > > > outcome. > > > > > > > I have no idea how (or even if) the backup procedure works on > > > > > > > BGG. In > > > > > > > the meantime, I'll keep my fingers crossed.- Hide quoted text - > > > > > > - Show quoted text -- Hide quoted text - > > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BGG Down" 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/BGG_down?hl=en -~----------~----~----~----~------~----~------~--~---
