Hi.
You can use the built-in replication feature to sync a MySQL instance
on the web server (slave) with the database server (master). Then you
always have a recent snapshot of the database.
You can also use the database on the slave to make your backups.
Temporarily halt replication, make your backup and afterwards let it
continue. It will automatically catch up with the current content.
You'll want to compare the database content once or twice until you
trust the replicated copy enough, before relying on it.
This will usually work fine, because the slave only will have to
execute the queries, which modify the database, which usually are only
a fraction of the full traffic.
The only question is whether your web server will stand up alone as
web and database server, when your database server fails. But it will
definitely be better than having no redundancy at all.
Bye,
Philemon.
On Mon, Dec 10, 2001 at 11:57:26AM +0200, [EMAIL PROTECTED] wrote:
> Hello,
>
> I would like to hear your opinions, recommendations, ideas, etc., about
> the following subjects:
> I have two servers. Both of them have MySQL, PHP, Apache. The first
> server is used as SQL server and the second server is used as Web
> sever. The problem is that it is "mission critical" and very busy (!)
> website, and I want full MySQL redundancy. I want to start using
> MySQL on a Web server and have it synchronized with SQL server.
>
> Another problem: I would like to backup my critical tables every
> hour, but the tables are big and updated all the time, and can not
> be locked. How can it be implemented without affecting users ?
>
> Thank you for your time,
> Igal.
--
[EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
