On Mon, 06 Jun 2011 12:44 +0200, "Johan De Meersman" <vegiv...@tuxera.be> wrote: > > I haven't bothered to look for the "bug", but it seems to me to be quite > reasonable default behaviour to lock the whole lot when you're dumping > transactional tables - it ensures you dump all tables from the same > consistent view.
thanks for the comment. > I would rather take this up with the ZRM people - it should "just work". this, http://bugs.mysql.com/bug.php?id=61414 suggests the same. so, i've already started that discussion as well, http://forums.zmanda.com/showthread.php?t=3703 Excluding 'performance_schema' appears to eliminate the error. And it seems does NOT cause a reliability-of-the-backup problem. > 3.3 came out last week, you may want to have a look at wether it's > already been adressed there. I believe that's an Amanda 3.3 release you're referring to. ZRM is still at 2.2, http://www.zmanda.com/download-zrm.php "ZRM for MySQL, Version 2.2 is the Latest Stable Release" and, i've MySQL-zrm-2.2.0-1.noarch installed. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
