percona-discussion team mailing list archive

[Peter Zaitsev <pz@xxxxxxxxxxx>]

Yasufumi,

I  think  this is wrong approach. We should not have a need to cripple
performance of the system to be able to back it up.

Also  it  would  not  work anyway - you can imagine large and actively
written  to  databases  so time to take backup the database takes much
more than 4GB written to the log file.


Monday, March 23, 2009, 11:22:31 PM, you wrote:

> We will implement it near future.

> But we may also need effort to make checkpoint age younger before the backup.
> (e.g. set innodb_max_dirty_pages_pct to small value and flush old dirty blocks)

> ** Changed in: percona-xtrabackup
>    Importance: Undecided => Medium
>        Status: New => Confirmed



-- 
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501    Skype: peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911
Attend the 2009 Percona Performance Conf
Apr 22-23 http://conferences.percona.com/

-- 
Feature request: handle log file bigger 4GB
https://bugs.launchpad.net/bugs/343936
You received this bug notification because you are a member of Percona
developers, which is the registrant for Percona-XtraBackup.

Status in Open source backup tool for InnoDB and XtraDB: Confirmed

Bug description:
Even with partial backup I got
-rw-r--r--   1 root root 5.8G Mar 16 18:36 xtrabackup_logfile

And trying to --apply-log I have
090316 18:36:08  innobackupex: Starting ibbackup with command: xtrabackup --prepare --target-dir=/mnt/data/tmp/2009-03-16_02-36-36

xtrabackup  Ver alpha-0.3 for 5.0.77 unknown-linux-gnu (x86_64)
xtrabackup_logfile detected: size=6160711680, start_lsn=(1247 2429276453)
InnoDB: Error: combined size of log files must be < 4 GB
innodb_init(): Error occured.
innobackupex: Error: 
innobackupex: ibbackup failed at ./innobackupex-1.5.1 line 427.