Emiliano <[EMAIL PROTECTED]> said:
> Then there's the issue of fetching the database. We can use MySQL
> replication although I've never worked with this; experiences/comments
> welcome. Other options are dumping the database and either the mirrors
> pulling it in or the master pushing them out. In order for MySQL
> replication to work the mirrors may require a MySQL upgrade
> (3.23.15 minimum) and I'll need to know the hostname for your mirror
> since the replication mechanism is in all likelyness going to clobber
> your host entries unless they're in the master database.
for reference :)
mysql replication is tempramental - it needs alot of babysitting in getting it
to work,
- you can tell it to only replicate certain databases (eg. not the
authentications one).. we did not do this for our expo, but it will probably
solve the bigger issue below!
- You cannot send update/insert queries to the slaves (it will destroy the
replication) - this could be done by modifing the local privaliges for a given
database so that local users can not write!
- what ever happened to repligard, I thought that was supposed to solve this
one ???? = it sounded nicer in theory than the mysql replication....
Dbdumping on small databases may be easier - probably on 1-2 seconds down per
week at most????
anyway good luck, I'll see If I get time to look at mirroring here... - I'm
too busy playing with CVS live editing for midgard documents...
have a browse around http://demo.hklc.com/cgi-bin/cvsweb
I've got cool stuff with fasttemplate working really well... - comming
soon......
regards
alan
--
Technical Director
Linux Center (HK) Ltd.
www.hklc.com
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
