Backup Question from newbie.

[jorge torralba]

Ok so there is no ontape with mysql :) (informix stuuf )


I have a forum with myisam tables which generates a 5.3 gig .sql file when I back it up with mysqldump. However, for some reason whcih I have not been able to identify yet, the following occurs.

for the most part of the mysldump process, the load average is anout 2.5 however, when it completes the process, the load on the system climbs into the 50's then 100's . Obviously, this brings the entire system down. Since I have not been able to figure out what the problem is I came up with an alternate solution.

RANGEFINDERSQLTAR="/backups/RFF.SQL.TAR"
RANGEFINDERTAR="/backups/RFF.tar"

/sbin/service mysqld stop
tar -cvf $RANGEFINDERSQLTAR /var/lib/mysql/forum_rangefinderforum_com/*
/sbin/service mysqld start

This shuts down mysql and tars up the datadir. It produces a file abot 1.5 gig smaller than the mysqldump without sending the server load up.

My questions:

Will this method produce a backup which can be restores simply by untaring the tar file?

Is it reliable?

What gives with the mysqldump sucking up resources?

Is there a better way to do this?

Thanks,

JT