Welcome to WebmasterWorld Guest from 184.108.40.206 , register , free tools , login , search , pro membership , help , library , announcements , recent posts , open posts Pubcon Platinum Sponsor 2014
quick and dirty mysql backup question can i copy the main directory and tar/compress it? seoboy
i've got a big mysql database (4G+) that has hit its default size cap, meaning i'm going to have to reorganize the database to accomodate the larger size (doh!). before i start the process, i kinda want to backup the db.
i know the preferred way to do this is via mysqldump but i think that will take forever given the db size. can i just copy the db data files to a new backup directory and tar -czvf that directory?
what are the major risks associated with this quick and dirty approach?
i'm trying to avoid having to get in my car and go down to the hosting center to physically download backups, in order to clear space... :)
thanks in advance for any input!
If you shut down the database before tarring it you'll be all right.
You can also use mysqlhotcopy - it's a perl script that does something similar while your database is running. It basicly flushes tables and locks them for the current process. VectorJ
rsync also works well for backing up the database files. Run rsync to back everything up, then lock down the database and run rsync once more to get everything current. martin
> ...then lock down
I'm not sure how good rsync is at diffing binary files but I wouldn't count on this speeding things up.
Old thread, but this is a current topic for me and you can never talk too much about backing stuff up, so I'm bumping it.
I'm not sure how good rsync is at diffing binary files
I wouldn't count on this speeding things up.
Between 100 and 400 times faster.
wrote 4394533 bytes read 104210 bytes 101095.35 bytes/sec total size is 628733048 speedup is 139.76 Finished at Sun Feb 18 07:44:33 GMT 2007
I'm doing a read lock flush, then rsync to a spare server.
Fastest backup system I've ever had for MySQL, and a lot less messy and more reliable than syncronisation which I've also played with (under MySQL 4.* anyway).
edited by: trillianjedi at 11:49 am (utc) on Feb. 18, 2007] mack
Rsync is possible the only option when you're database is really big. Once had to back up an 80+ gig mysql db and rsync was the only option that seamed to work.
Started process, went to sleep, woke up to backup completed.