Replicating to mysql5.1 from 5.0 master?

--=-EUDinHvE0n/g/YrBvUyp
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

Hi All

as per my mail yesterday we are busy migrating and upgrading a
current MySQL database this weekend.

All tests on the new system has been done,etc...

However, in order to minimize downtime, it was decided to setup
the new "master" server (Mysql 5.1) to be a slave to the current
production master server (Mysql 5.0).

Due to differences within the 2 versions, we had to exclude the
mysql database from the backup and restore.

However I am now not 100% sure about the following:

When setting up the replication, should we still
exclude the mysql database from the replication and manually do any
changes if required or can we replicate all databases without any
problems?

We are switching over to the new system on Friday and I do
not want to break something now that will compromise the go-live.

Any suggestions would be greatly appreciated. (My feeling is
to exclude the mysql database from replication but not too sure).


Machiel Richards
Relational Database Consulting (Pty) Ltd

MYSQL / POSTGRES specialist
20 Stirrup Lane, Woodmead Office Park, Van Reenens Road, Woodmead, South
Africa
Office: 0861 RDC RDC (0861 732 732)
Mobile: +27 72 238 6008
Fax: 0861 RDC FAX (0861 732 329)
E-Mail: machielr@rdc.co.za


--=-EUDinHvE0n/g/YrBvUyp--

Re: Replicating to mysql5.1 from 5.0 master?

--0015174c1230a7d343049c64d3b9
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Feb 16, 2011 at 10:23 AM, Machiel Richards wrote:

> Due to differences within the 2 versions, we had to exclude the
> mysql database from the backup and restore.
>

Yep :-)


> When setting up the replication, should we still
> exclude the mysql database from the replication and manually do any
> changes if required or can we replicate all databases without any
> problems?
>

Ah :-)

If you use statement-based replication, I would hazard a guess that grant
statements will replicate perfectly fine and will work as expected on both
sides (you DON'T pilfer with the authentication tables manually, do you?).
If you use row-based replication, I would definitely exclude the mysql
database.

The question is, however: how often do you need to change privileges or
routines during this migration period? I would assume rarely to not at all;
so why not just leave the mysql database out of the replication, just in
case ? You presumably already set it up manually on the new server, so just
let good enough alone.


--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

--0015174c1230a7d343049c64d3b9--