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/
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. max_dirty_ pages_pct to small value and flush old dirty blocks)
> (e.g. set innodb_
> ** Changed in: percona-xtrabackup
> Importance: Undecided => Medium
> Status: New => Confirmed
-- conferences. percona. com/
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://