MySQL version for mysql-zrm on Debian Sarge

Discussion in 'HOWTO-Related Questions' started by Hans, Sep 28, 2006.

  1. Hans

    Hans Moderator ISPConfig Developer

    Hello Falko,

    First, i want to thank you for your great how to called "MySQL Backup And Recovery With mysql-zrm On Debian Sarge".
    I am really interested in this so i like to give it a try.

    Before i start with it, i need to know if it is necessary to update the MySQL-version on my server and if so how can i do this?

    The MySQL part of my ISPConfig server has been setup according these commands:

    apt-get install mysql-server mysql-client libmysqlclient12-dev

    And if i check the output of my phpinfo file it says:

    Client API version 4.0.24

    So, I guess this is the version of the MySQL, i am running on my server.


    You mentioned in your how to "MySQL Backup And Recovery With mysql-zrm On Debian Sarge" that this backup system needs MySQL 4.1 at least.
    So my conclusion is: i have to update my MySQL software form 4.0.24 to 4.1.

    - How can i do this on Debian Sarge (Unofficial 64 bit) ?

    I found this in the forums:
    apt-get install mysql-server-4.1 mysql-client-4.1 libmysqlclient14-dev
    Is this all i need before i proceed?

    - Is updating no problem for websites with databases using the current version of MySQL?
    - Will an update effect my databases and will i be able to login again?

    Please let me know as i am not an expert at this point.
     
    Last edited: Sep 28, 2006
  2. Hans

    Hans Moderator ISPConfig Developer

    MySQL update from 4.0.24 to 4.1

    I could not wait to start with Falko's how to so i did:

    apt-get install mysql-server-4.1 mysql-client-4.1 libmysqlclient14-dev

    And it worked perfectly!!! :)

    unbelievable that this is all (thanks to Debian).
     
  3. falko

    falko Super Moderator ISPConfig Developer

    I guess it also works with MySQL 4.0, but I didn't test, and the Zmanda web site says that they only tested with 4.1, 5.0, and 5.1 beta. :)
     
  4. Hans

    Hans Moderator ISPConfig Developer

    Works great

    Falko,
    i want to know that the MySQL backup system works great.

    I updated to MySQL 4.1 (for sure) and just tested it !

    Thanks for your great how to.
     
  5. nenad

    nenad ISPConfig Developer ISPConfig Developer

    Are those errors something that I should be worried about?

    ----------------------------------------------------------
    Tue Nov 7 22:17:26 2006: INFO: backup-set=dailyrun
    Tue Nov 7 22:17:26 2006: INFO: backup-date=20061107221726
    Tue Nov 7 22:17:26 2006: INFO: backup-date-epoch=1162934246
    Tue Nov 7 22:17:26 2006: INFO: retention-policy=7D
    Tue Nov 7 22:17:26 2006: INFO: mysql-version=4.1.11-Debian_4sarge7-log
    Tue Nov 7 22:17:26 2006: INFO: backup-directory=/var/lib/mysql-zrm/dailyrun/20061107221726
    Tue Nov 7 22:17:28 2006: ERROR: Copy from /var/lib/mysql/master.info to /var/lib/mysql-zrm/dailyrun/20061107221726 failed
    Tue Nov 7 22:17:28 2006: ERROR: Error backing up master.info
    Tue Nov 7 22:17:28 2006: ERROR: Copy from /var/lib/mysql/relay-log.info to /var/lib/mysql-zrm/dailyrun/20061107221726 faile
    Tue Nov 7 22:17:28 2006: ERROR: Error backing up relay-log.info

    Tue Nov 7 22:17:28 2006: INFO:
    Tue Nov 7 22:17:28 2006: INFO: backup-level=0
    Tue Nov 7 22:17:38 2006: INFO: logical-databases=ispconfigdb mysql test web36_db1 web4_db1 web4_db2 web8_db1
    Tue Nov 7 22:17:38 2006: INFO: read-locks-time=00:00:10
    Tue Nov 7 22:17:38 2006: INFO: flush-logs-time=00:00:01
    Tue Nov 7 22:17:38 2006: INFO: backup-time=00:00:12
    Tue Nov 7 22:17:38 2006: INFO: backup-size=4.15 MB
    Tue Nov 7 22:17:38 2006: INFO: next-binlog=mysql-bin.000076
    Tue Nov 7 22:17:38 2006: INFO: /var/lib/mysql-zrm/dailyrun/20061107221726/backup.sql=e7c66f2c218479765ca343be8ee8ea03
    Tue Nov 7 22:17:38 2006: INFO: backup-status=Backup done but with errors
    Tue Nov 7 22:17:38 2006: INFO: Backup done but with errors
    -----------------------------------------------------------------

    and

    ---------------------------------------------------------------------
    server201:~# mysql-zrm-scheduler --now --backup-set dailyrun --backup-level 0
    Logging to /var/log/mysql-zrm/mysql-zrm-scheduler.log
    Use of uninitialized value in concatenation (.) or string at /usr/bin/mysql-zrm line 1305.
    INFO: mysql-zrm-version
    INFO: backup-set=dailyrun
    INFO: backup-date=20061107230239
    INFO: backup-date-epoch=1162936959
    INFO: retention-policy=7D
    INFO: mysql-version=4.1.11-Debian_4sarge7-log
    INFO: backup-directory=/var/lib/mysql-zrm/dailyrun/20061107230239
    cp: cannot stat `/var/lib/mysql/master.info': No such file or directory
    ERROR: Copy from /var/lib/mysql/master.info to /var/lib/mysql-zrm/dailyrun/20061107230239 failed
    ERROR: Error backing up master.info
    cp: cannot stat `/var/lib/mysql/relay-log.info': No such file or directory
    ERROR: Copy from /var/lib/mysql/relay-log.info to /var/lib/mysql-zrm/dailyrun/20061107230239 failed
    ERROR: Error backing up relay-log.info
    INFO:
    Use of uninitialized value in pattern match (m//) at /usr/bin/mysql-zrm line 1077.
    INFO: backup-level=0
    INFO: logical-databases=ispconfigdb mysql test web36_db1 web4_db1 web4_db2 web8_db1
    INFO: read-locks-time=00:00:02
    INFO: flush-logs-time=00:00:00
    INFO: backup-time=00:00:02
    INFO: backup-size=4.15 MB
    INFO: next-binlog=mysql-bin.000078
    INFO: last-backup=/var/lib/mysql-zrm/dailyrun/20061107230217
    INFO: /var/lib/mysql-zrm/dailyrun/20061107230239/backup.sql=d83be38ee7111245ff9c07ca18b1038c
    INFO: backup-status=Backup done but with errors
    INFO: Backup done but with errors
    Use of uninitialized value in hash element at /usr/bin/mysql-zrm line 1986.
    ERROR: /usr/bin/mysql-zrm did not finish successfully
    server201:~#
    ---------------------------------------------------------------------------------------------
     
  6. nenad

    nenad ISPConfig Developer ISPConfig Developer

    Is because of this:

    http://forums.zmanda.com/pipermail/mysql-zrm-bugs/2006-September/000013.html

    And this:
    was because of this:
    /etc/mysql-zrm/mysql-zrm.conf
    Code:
    replication=1
    so I changed it to
    Code:
    replication=0
     

Share This Page