New installation - How to automate backup

Posted: 2012-01-23, 17:23 (No subject)

Then you have selected only one database on the multidump-screen.
Re-check the databases you want to backup and click "save" again.

**knows MySQLDumper** Joined: 23 Jan 2012 Posts: 6

In fact - selecting =Multidump configuration= leaves only the first database in this array. ANY other selection (even just a single table) in fact leaves all tables in the array...

Posted: 2012-01-23, 17:34 (No subject)

Ok, try replacing the file inc/functions.php with the attached one (remove the extension .txt), re-save your settings and tell me, if this is working.

**knows MySQLDumper** Joined: 23 Jan 2012 Posts: 6

OK - thanks a lot for helping out Smile

Unfortunately the new file did not help, so I started to debug... The problem occurs only when selecting database "=Multidump Configuration=" in Conficuration/Cronscript. If selecting All or just a single DB, it works fine.

Here are my findings, referring to line-numbers in the new functions.php:
Line 396-403 (//remove database we don't want to backup) seems somewhat odd to me. The array $cron_db_array at line 395 already contains exactly the databases I have selected for backup. Still the script wants to remove two databases from $cron_db_array. This would be fine if the keys of the two arrays $cron_db_array and $databases['Name'] refferred to the same databases. But since they don't, we end up removing two of the databases I want included in my backup.

Example data from my system at line 395:
$databases['Name']: Array ( [0] => d7 [1] => information_schema [2] => mysql [3] => mysqldumper [4] => ordet [5] => performance_schema [6] => phpmyadmin [7] => test [8] => upa_portalen )
$dontBackupDatabases: Array ( [0] => mysql [1] => information_schema )
$cron_db_array: Array ( [0] => d7 [1] => mysqldumper [2] => ordet [3] => phpmyadmin )

At line 406 after db's have been removed from $cron_db_array:
$cron_db_array: Array ( [0] => d7 [3] => phpmyadmin )

I ended up commenting out the unset-statement line 406-410, and now the expected DBs get backed up using the crondump. However I'd like you to verify if this is a useable solution as I've not taken the other arrays that get unset here into account...

Posted: 2012-01-24, 11:27 (No subject)

Thanks for your debugging. Yes. It looks like you have found a bug.

But as we don't like this hard to maintain array-massacre Wink

ourselves and since we are working on version 2, where we will do this completely differently, I don't want to investigate more time here. We also do not plan to release a version 1.24.5
If this is working for you, go and use it. Wink

**knows MySQLDumper** Joined: 23 Jan 2012 Posts: 6

Posted: 2012-01-24, 13:21 (No subject)