I decided to use the same basic framework to backup my website (substituting tar for mysqldump) but the resulting file is so big (about 20 meg) that the line
$sData = chunk_split(base64_encode(implode(“”, file($sFilename))));

throws an error. I’m working on fixing it, but any suggestions would be appreciated.

Thanks!

Terry

Aman, that looks like it should work. I can’t test it right now, as my main development machine is down, but the form follows the first example at the link I provided.

$sFilename = “backup-database-” . date(“Y-m-d”) . “.csv”;

$sBackupCommand = “mysqldump -u user database table111 > $sFilename”;

/*user – the main username
database – my database name
table111 – the table to be backed up

Is it correct? */

The part you quoted just creates the filename – the actual backup command for MySQL is on line 56, and for PostgreSQL on line 59. These sample commands will grab all the tables in the database. They work well – I’ve recently had some problems on my development machine, and had to set up another one. I used backups modeled after the script above, and was able to create new test databases pretty quickly.

That being said, if you’re using MySQL, add “–tables [list of tables]” after the [db_name] parameter to selectively dump certain tables – details on mysqldump can be found here. In a similar way, the “–table=[tablename]” option can be added to pgdump (and can also be qualified with a schema name using “–schema=[schemaname]) – more details on pgdump are here.

I hope that helps!

How do I specify my table here which has to backed up?