You are viewing an old version of this page. View the current version.

    Compare with Current View Page History

    Version 1 Next »

    Icon
    Only attempt to migrate the databases between supervisors of the same version; READ CAREFULLY

    If you're doing this to install a new supervisor and want to run the latest version of Qube! on the new supervisor, match versions between the supervisors first, and then upgrade the new supervisor once the databases have been migrated over to it.

    If you're running Qube 6.0 or later, you will need to contact Sales at PipelineFX in order to get your Qube licenses moved over to the new machine.  They'll need a MAC address for the new supervisor host.

    To migrate a Qube supervisor, you need to migrate both the MySQL databases and the job logs if the job logs are stored on the supervisor's local disk.  If your job logs are stored on the network you will not have to move them, simply set the supervisor_logpath on the new supervisor to point to the same network directory as the old supervisor.

    It is recommended that you start moving the job logs before you start migrating the MySQL databases, as the job logs will take longer to move.

    Don't forget to duplicate any settings you've changed in the old supervisor's qb.conf.

    To migrate the MySQL databases: 


    The following instructions use the unix 'ls' command. You may want to install cygwin on the old supervisor if it's a Windows machine if you are following along, otherwise, substitute the equivalent Windows command line commands.

    Build the new supervisor up, install MySQL if it's a Linux host, then install the same version ofQube that you are running on the old supervisor, then stop the supervisor daemon on the new supervisor.

    Now the new supervisor is ready to have the databases copied over. The trick is to build a mysqldump command that will only dump the *qube databases, then send them over the network to the new server.

    First, on the new server you have to grant access to the root user from the old server.

    On the new server, at the mysql> prompt:

    Code:
    GRANT ALL PRIVILEGES ON *.* TO 'root'@'192.168.1.1';

    (replace the ip address in the command with the ip address of your old server)

    Test the access from the OSX host:

    Code:
    mysql -u root -h <newHostName> -B -e "SELECT USER()"


    It should return something like:

    Code:
    USER() root@192.168.1.1


    Now that you can access the MySQL server on the new supervisor from the MySQL server on the old supervisor, it's time to push the dump across from the old supervisor to the new one.

    On the old supervisor:

    You need to build a list of all the *qube databases. The simplest way is to 'cd' into the mysql data directory and list them with "ls"

    jburk-17-mbpro:data jburk$

    Code:
    cd /usr/local/mysql/data


    jburk-17-mbPro:data jburk$

    Code:
    \ls -d *qube
    1qube  2qube  3qube  4qube  5qube  6qube  7qube  8qube  qube


    Note the use of the leading backslash on the 'ls' command. It's to skip any aliases or formatting operators that you usually pass to 'ls', to avoid having slahes on the end of the directory names. The output from the 'ls' command should look like the above.

    Then the mysqldump command will look like:

    Code:
    mysqldump --opt --databases `\ls -d *qube` | mysql -u root -h <linux ip address>

    Those are backticks around the "\ls -d *qube" command. The backtick is the left-leaning single-quote below the ~ character on the keyboard.

    Windows

    Icon
    1. Windows users must specify a port while running this command. Windows mysqlclient uses port 3300 by default whereas Linux and OSX assumes 3306. To specify a port, add "-P 3306" to the end of the above command
    2. If the old supervisor is running on Windows and you have not installed cygwin (or some other *nix shell utility), you cannot pipe commands to other commands, nor can you do command substitution with backticks. In this instance you'll need to hand-enter the list of qube databases, send the output of mysqldump to a file on the old supervisor, then read that file on the new supervisor. The commands would look something like:
    	old supervisor: mysqldump --opt --databases 1qube 2qube 3qube ... qube > some_file.sql
    	new supervisor: mysql -u root < some_file.sql

    The list of qube databases (1qube 2qube 3qube, etc) can be found by looking in c:\Program Files\pfx\qube\mysql\data for all files that contain the word "qube".

    Icon

    If you get a error message:

    [ERROR] mysqld: Can't open file: './<database>/<table>.frm' (errno: 24)

    You need to increase your open_file_limits in my.cnf. On the old supervisor, add:

    open_files_limit = 100000

    to the [mysqld] section of my.cnf

     

    The mysqldump should take quite a while to finish, and will print no output. A way to check if it's doing the right thing while it's running is to login to the mysql server on linux machine, and run

    Code:
    mysql> SHOW DATABASES LIKE '%qube';

    You should start to see some qube databases with numbers in front of them, like 12qube. Run the command every minute or so, and the list of databases should be growing.

    Once the mysqldump command has finished on the OSX server, you'll need to do a bit of maintenance on the new tables on the linux server.

    On the linux server:

    Code:
    mysqladmin -u root flush-privileges
    mysqlcheck -u root --repair --all-databases

    Once that's done, you should start the supervisor (/etc/init.d/supervisor start).

    Verify that the jobs are present:

    Code:
    qbjobs -u all


    Verify that you can see the logs for a random job: :

    Code:
    qbout <someJobId>
    • No labels