From: Sp.Raja
Date: July 27 2004 2:51pm
Subject: Re: Innodb assertion failure after binary backup-restore
List-Archive: http://lists.mysql.com/mysql/169825
Message-Id: <20040727202110.1848905449.spraja@isofttech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Thanks for your replies.

Now I have three ways to go

    1. replication=20
    2. innodb hot backup tool
    3. Make sure that no one is writing in to the database and start backup=
 when modified db pages in "BUFFER POOL AND MEMORY" becomes zero

    #FLUSH TABLES WITH READ LOCK
    still_to_flush=3D1=20=20
    while [ $still_to_flush !=3D 0 ]
    do
        still_to_flush=3D`/usr/local/mysql/bin/mysql -e "SHOW INNODB STATUS=
\G" |  grep "Modified db pages" | awk '{print $4}'`
        sleep 1
    done
    #UNLOCK TABLES

Do you think #3 will work?

Regards,
Sp.Raja

> ------------Original Message------------
> From: "Heikki Tuuri" <Heikki.Tuuri@stripped>
> To: mysql@stripped
> Date: Tue, Jul-27-2004 6:24 PM
> Subject: Re: Innodb assertion failure after binary backup-restore
>=20
> Hi!
>=20
> sync will not help.
>=20
> You can run SHOW INNODB STATUS\G to monitor when InnoDB has flushed its
> buffer pool.
>=20
> Best regards,
>=20
> Heikki
> Innobase Oy
> InnoDB - transactions, row level locking, and foreign keys for MySQL
> InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up=20
> MyISAM
> tables
> http://www.innodb.com/order.php
>=20
> Order MySQL support from http://www.mysql.com/support/index.html
>=20