I'll stop replicating mysql tables then... Thanks ;)
-- Chris.
----- Original Message ----- From: "Gary Richardson" <[EMAIL PROTECTED]>
To: "Chris Knipe" <[EMAIL PROTECTED]>
Cc: <mysql@lists.mysql.com>
Sent: Wednesday, March 09, 2005 6:23 PM
Subject: Re: safe way of replication?
I would probably not replica the mysql database in your case.
We run a similar setup. One problem we have is people connecting to the wrong database server and applying updates (for example, they think they are in the master, but it's really the slave and they perform an update or an insert). As you can guess, it causes problems with data integrity. In order to get around this, we remove insert,update,delete from our users on the slave..
out.
On Wed, 9 Mar 2005 17:49:10 +0200, Chris Knipe <[EMAIL PROTECTED]> wrote:Lo all,
Just wondering... Would the below be considered a "safe" way to do replication...
MasterBD: One Database (most Critical)
SlaveDB: Replicating all databases from MasterBD as well as hosting allot of
other 3rd party, or customer DBs.
Basically, the MasterBD holds a single critical database for our company (i.e. main database). The slave DB then becomes a slave for the MasterDB (one way replication), but also hosts allot of other not so critical databases?
So far, this seems to be working, but I am getting a couple of errors or
problems in regards to the mysql table for user authentication... My guess
is that I more than likely just don't need to replicate that DB from the
master.
Would this be considered safe?? Or should I look at a third database server
for deployment?
-- Chris.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]