, November 18, 2004
4:56 PM
To: [EMAIL PROTECTED]
Subject: RE: Multiple processing
heads...
For me having an SQL server fail isnt a
problem, Im lucky in a way as Ive got too many servers and not enough to do
with them ;) if our radius SQL server failed, I could have a replacement up
within 30 minutes
Stuart Harris wrote:
MySQL Supports read-only (one way) replication, we replicate all our
live databases (customer hosting, internal, etc...) to a single
backup DB which has a 'live' copy, it doesn't normally have writes to
it, but it can quickly be used to build up a replacement DB that is
I have it running with multiple servers
connecting to one mysql server ..so all the accounting goes to the same place..
Then I have all the servers synchronize (locally)
with it nightly and fail over to the local one if the primary stopped working?
Im redoing it now because my server
transaction log all I need to know is that Im not going to get
problems with accounting packet duplication or some other weird thing ;)
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cris Boisvert
Sent: 18 November 2004 21:36
To:
[EMAIL PROTECTED]
Subject: RE: Multiple
Can you describe a bit more?
Like:
Redundant database? How?
Redundant radius servers? How?
How many radius servers?
Expected load of requests?
...
--
Regards,
Thor Spruyt
E: [EMAIL PROTECTED]
W: www.thor-spruyt.com
M: +32 (0)475 67 22 65
Bestel nu uw exemplaar van Operationele verkoop (Walter
Can you describe a bit more?
Like:
Redundant database? How?
MySQL Supports read-only (one way) replication, we replicate all our live
databases (customer hosting, internal, etc...) to a single backup DB which
has a 'live' copy, it doesn't normally have writes to it, but it can quickly
be used
6 matches
Mail list logo
