Van, I'll second what Gerald said about mysqlhotcopy.
When we first began using MySQL at my last job, we had terrible
problems with MySQL crashing. Turned out to be due to a 3rd party
backup process attempting to lock and read the database files while
MySQL was attempting to use them.
Using mysqlhotcopy to copy the files elsewhere, and excluding the data
directory from the backup software, gave us a stable solution.
mysqldump might also work well for you, as it can lock
tables/databases and give you a consistent snapshot. Potentially
takes longer to restore from a mysqldump file though.
On 11/13/06, Van <van@stripped> wrote:
> I have a 600M data file that never gets backed up. The following error
> occurs in the cron job:
> tar: /data/mysql/"my_db_name"/"my_large_table_name".MYI: file changed as we read it
> Is there a way I can set this one table to read-only prior to the backup
> without affecting other db writes during this operation?
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1