Posted by Leon Poon on 04/22/05 10:11

I think he wants mirror, sort of...



I will do this if I were you:

Select the server wif the most bandwidth. Call this the master.
The other 2 are slaves.


To sync files:
==============

Enable network file system server on the 2 slaves. Export the htdocs
directories.

Setup the master to mount the exports.

Setup file monitoring tools (maybe fam?) on the master to copy new files to
the mounted slave directories when alteration of files in htdocs is
detected.

DO NOT instead mount exports of the master's htdocs on the slaves otherwise
the slaves will be very slow in serving out files.

Of course, you have to enable security - things like IP
restriction/encryption on the NFS.


To sync database:
=================

Use database slaving tools?

If you are using MySQL, see
http://mysql.hjc.edu.sg/doc/mysql/en/replication-intro.html. All updates
from ANY server must be done at the master though.

Or you can just host the SQL server at the master. All queries goes to the
master.



Hope this helps!




-Leon



----- Original Message -----
From: "Drewcore" <drewsph@gmail.com>
To: "php" <php-general@lists.php.net>
Sent: Friday, April 22, 2005 11:45 AM
Subject: Re: [PHP] Re: 1 web site, 3 servers, 3 countries - best practises?


> well, i guess it all depends...
>
> are you talking about having one server in south america that acts as
> your database server, one server in asia that's your web server, and
> then another server in north america that servers some other task?
>
> or are you talking about having a localized database, http, etc,
> server for each location (read: continent/country)?
>
> the first is easy... it'll all just mesh... the second is more difficult.
>
> drew
>
> --
> dc .. drewcore.com
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
>

[Back to original message]