Comments on: Backing Up a MySQL Database with PHP

By: An Acrobat

An Acrobat — Tue, 19 Jun 2007 14:27:48 +0000

Very helpful article. I’ve added one more twist to it—compression. Just pipe the result to a bz2 file on unix/linux systems, like this: $backup = “location/of/file/mysqldumpâ€ -opt -h $dbhost -P$dbport -u$dbuser —password=$dbpass $dbname | bzip2 -c > $filename.bz2â€;

By: qntmfred

qntmfred — Wed, 13 Jun 2007 20:52:19 +0000

you know, i pondered through this very issue a year ago or so and ended up using the same method. though i felt a little dirty for using the system function. but it was either that or do SELECT INTO OUTFILEs and LOAD DATA INFILEs, which created permissions headaches since my app lives on shared hosting

By: Ryan Campbell

Ryan Campbell — Wed, 13 Jun 2007 20:36:53 +0000

We’ve actually got a mix of a couple methods going on. For the sections where there are multiple db’s, it was planned that way for reasons other than backing up. We’re far from experts on the subject, and so far there have been definite positives and negatives with it. Almost all of the negatives are hardware related. Maybe we’ll go into more detail on our setup one of these days.

By: Reilly Sweetland

Reilly Sweetland — Wed, 13 Jun 2007 19:11:49 +0000

Great tip! I notice you say databases. This seems smart to use a separate database for each user when factoring in this technique, but did you guys know this when deciding to structure it that way? Was there any other reason you guys choose this method as opposed to a single database with multiple tables, or just massive tables with primary keys for users.Â Possibly another post topic? :)