Toolpack migration Windows XP 2-3

This page shows the Toolpack 2-3 migration guide for Windows XP.

Toolpack Migration Steps

Migrating from MSVC6 installation to MSVC8

If you intend to migrate from MSVC6 to MSVC8 (ie TBToolPack-x.y.zz-msvc8-Setup.exe, instead of TBToolPack-x.y.zz-msvc6-Setup.exe), you will first need to install Microsoft Visual C++ 2005 SP1 Redistributable Package (x86).

Create new database user

Connect to MySQL and create a new user tbdb with all privilege. If you are unable to connect, use an IP Address instead of the [HostName].

mysql -u root -h '[HostName]'
CREATE USER 'tbdb'@'%' IDENTIFIED BY '[DatabasePassword]';
GRANT ALL privileges ON *.* TO 'tbdb'@'%' IDENTIFIED BY '[DatabasePassword]';
exit

Example mysql -u root -h winxp32-01 CREATE USER 'tbdb'@'%' IDENTIFIED BY 'tbdbpw'; GRANT ALL privileges ON . TO 'tbdb'@'%' IDENTIFIED BY 'tbdbpw'; exit

Install ODBC MySQL connector

Install MyODBC for MySQL. Use the Windows MSI installer to make sure the connector properly registers with the ODBC manager.

Enable MySQL database replication

Enable binlog

Binlog file is required for a master to log every statements done on databases and for slaves to be able to read it.

Manually

• Go to your MySQL server directory

• Edit the configuration file (usually my.ini)

• Add the variable log-bin. If you want to specify a filename you have to add =filename. Otherwise it will create the file with the default name

Using MySQL Administrator tool

• Open the MySQL Administrator tool and login

• Go to Startup variables and Log files tab

• Activate Binary Logfile name. If you don't specify a filename, it will create the file with the default name

Set server id

Each MySQL server must have unique server id to be able to communicate. If a slave server has the same server id of a master, replication won't work.

Manually

• Go to your MySQL server directory

• Edit the configuration file (usually my.ini)

• Add the variable server-id= and specify a unique id for it (except 0)

Using MySQL Administrator tool

• Open the MySQL Administrator tool and login

• Go to Startup variables and Replication tab

• Activate Server Id and specify a unique id for it (except 0)

Replicate specific databases

You can configure the replication of one or more specific databases instead of all by default. You can do it on master server side or slave server side.

Master server side

• Go to your MySQL server directory

• Edit the configuration file (usually my.ini)

• If you want to specify databases to be logged

  • Add the variable binlog-do-db=db_name. The value of db_name is the name of the database you want to be logged in the binlog. You can add as many databases as you want by adding the same variable with a different database name.

• If you want to specify databases that won't be logged

  • Add the variable binlog-ignore-db=db_name. The value of db_name is the name of the database you don't want to be logged in the binlog. You can add as many databases as you want by adding the same variable with a different database name.

Final my.ini configuration for Master side should look like this: log-bin server-id=101 binlog-do-db=toolpack_0

Slave server side

• Go to your MySQL server directory

• Edit the configuration file (usually my.ini)

• If you want to specify databases to replicate

  • Add the variable replicate-do-db=db_name. The value of db_name is the name of the database you want to be replicated. You can add as many databases as you want by adding the same variable with a different database name.

• If you want to specify databases that won't be replicated

  • Add the variable replicate-ignore-db=db_name. The value of db_name is the name of the database you don't want to be replicated. You can add as many databases as you want by adding the same variable with a different database name.

Final my.ini configuration for Slave server side should look like this: log-bin server-id=101 replicate-do-db=toolpack_0

Restart MySQL service

net stop MySQL51
net start MySQL51

Warning: You may have a different service name in your system (ex. MySQL, MySQL50, etc.). To open the service control panel, run: services.msc

Disable Release 2-2 Service

tbtoolpack disable 2.2

Toolpack System installation

Now that the prerequisite are installed, we can go back to the migration guide Toolpack migration 2-3.