November 21, 2014

xtrabackup-1.2

Dear Community,

The notice is hereby given that next version 1.2 of XtraBackup software is released.

The list of changes in this version includes:
Changelog:

  • XtraBackup supports now XtraDB 10
  • tar4ibd supports variable page size and fast_checksum of XtraDB
  • Supported 32bit platform for Centos 5, Centos 4, Debian lenny and etch, Ubuntu Karmic, Jaunty, Intrepid, Hardy, FreeBSD


Fixeb bugs in this release:

The binary packages for as well as source code of the XtraBackup is available on http://www.percona.com/percona-builds/XtraBackup/XtraBackup-1.2/.

Debian and RPM are available in Percona repository.

Since now debian packages in Percona APT repository are signed by our private key.

To check authenticity of the packages you need to install the public key:

To verify source code, you have to install the key in trastedkeys.gpg:

The project lives on Launchpad : https://launchpad.net/percona-xtrabackup and you can report bug to Launchpad bug system:
https://launchpad.net/percona-xtrabackup/+filebug. The documentation is available on our Wiki.

For general questions use our Pecona-discussions group, and for development question Percona-dev group.

For support, commercial and sponsorship inquiries contact Percona.

About Aleksandr Kuzminsky

Aleksandr is a consultant and data recovery specialist.
He is a former Percona employee.

Comments

  1. milly says:

    Hi, when I use the xtrabackup binary of xtrabackup1.2 to do the incremental backup, have a error.how to resovle it?
    OS: centos , MYSQL :MYSQL 5.1.30

    ./bin/xtrabackup Ver 1.2 Rev undefined for 5.1.45 pc-linux-gnu (i686)
    xtrabackup: cd to /home/caoincre
    xtrabackup: Error: cannot open ./xtrabackup_checkpoints
    xtrabackup: error: xtrabackup_read_metadata()
    xtrabackup: This target seems not to have correct metadata…
    xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(48425)
    xtrabackup: Temporary instance for recovery is set as followings.
    xtrabackup: innodb_data_home_dir = ./
    xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
    xtrabackup: innodb_log_group_home_dir = ./
    xtrabackup: innodb_log_files_in_group = 1
    xtrabackup: innodb_log_file_size = 2097152
    xtrabackup: Starting InnoDB instance for recovery.
    xtrabackup: Using 104857600 bytes for buffer pool (set by –use-memory parameter)
    InnoDB: The InnoDB memory heap is disabled
    InnoDB: Mutexes and rw_locks use InnoDB’s own implementation
    InnoDB: Warning: innodb_file_io_threads is deprecated. Please use innodb_read_io_threads and innodb_write_io_threads instead
    InnoDB: The first specified data file ./ibdata1 did not exist:
    InnoDB: a new database to be created!
    100510 23:25:41 InnoDB: Setting file ./ibdata1 size to 10 MB
    InnoDB: Database physically writes the file full: wait…
    InnoDB: Error: all log files must be created at the same time.
    InnoDB: All log files must be created also in database creation.
    InnoDB: If you want bigger or smaller log files, shut down the
    InnoDB: database and make sure there were no errors in shutdown.
    InnoDB: Then delete the existing log files. Edit the .cnf file
    InnoDB: and start the database again.
    xtrabackup: innodb_init(): Error occured.

  2. Marc says:

    Same problem.

Speak Your Mind

*