By bitsantos on

We have a populated Drupal 6.x site up and we want to setup MySQL replication on it with another machine with an identical system. What we want to achieve here is to have the web server be only serving requests while another machine on an intranet (which the web server is a part of) has a copy of the site in which users can administer settings and content. The administrative machine is the master in this case while the web server is the slave, copying all of the contents from the master. We've been able to successfully setup the MySQL replication (even the file systems) but we always run into a duplicate error entry involving one of the cache tables stopping the replication. Is there any way around this?

⋅ Categories: Drupal 6.x

Comments

bitsantos’s picture

bitsantos commented

I should probably add that we've also thought that we could achieve the administrative setup with the administrative machine simply connecting directly and using the web server's database, but our client wants the setup I described above also for the sake of having a database backup.

gpk’s picture

gpk commented

Presumably you've had a look here ...
http://drupal.org/search/node/replication

Also I think these posts give clues to how drupal.org does it now. http://buytaert.net/search/node/replication.

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk