Thanks for your replies.
Now I have three ways to go
1. replication
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=1
while [ $still_to_flush != 0 ]
do
still_to_flush=`/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" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Tue, Jul-27-2004 6:24 PM
> Subject: Re: Innodb assertion failure after binary backup-restore
>
> Hi!
>
> sync will not help.
>
> You can run SHOW INNODB STATUS\G to monitor when InnoDB has flushed its
> buffer pool.
>
> Best regards,
>
> 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
> MyISAM
> tables
> http://www.innodb.com/order.php
>
> Order MySQL support from http://www.mysql.com/support/index.html
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
