Comments on: Automated off-site MySQL backups with cron and PHP

By: admin

admin — Thu, 18 Aug 2011 16:46:46 +0000

@Travis — thanks for looking into that!

By: Travis

Travis — Fri, 12 Aug 2011 21:33:49 +0000

@admin: I’ve done some more digging and it looks like mysqldump already takes care of locking and unlocking tables. http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html Like I said, I’m new to this, so maybe I didn’t read that right, but that’s what I got out it..

By: admin

admin — Wed, 27 Jul 2011 06:27:36 +0000

@Travis: That is probably a really good idea, especially once your database starts increasing in size and taking longer to dump. One of these days I’ll get around to updating the script

By: Travis

Travis — Thu, 30 Jun 2011 03:15:27 +0000

What about the need to turn the site off before the backup taken? Or lock the tables then unlock them when the dump is done?

mysql> FLUSH TABLES WITH READ LOCK;

mysql> UNLOCK TABLES;

I’m new to this so be easy on me.

By: John

John — Wed, 17 Mar 2010 22:01:29 +0000

Okay, so before I continue this argument, I want to acknowledge that we’re arguing pointless optimizations here that won’t add to actual performance in any significant way…

How about:

// 7 days * 24 hours * 60 minutes * 60 seconds =
$one_week = 604800;

By: admin

admin — Sat, 13 Mar 2010 19:47:55 +0000

That would certainly work. However, it’s been my experience that a little bit of processing power (in this case, very little) is a good tradeoff for extended readability. This thing only runs once a day

By: John

John — Fri, 12 Mar 2010 23:11:50 +0000

I know its a pedantic optimization, but shouldn't

$one_week = 60 * 60 * 24 * 7;

$one_week = 604800;