MYSQL Backup addon error

[Elijah]

ZC 1.3.7

I am getting an error as well when attempting to do a backup. I get "result code: 127" on the first line and "ERROR: Could not locate the MYSQLDUMP backup utility. BACKUP FAILED." on the second line.

I read "Note that LOCAL_EXE_MYSQL and LOCAL_EXE_MYSQL_DUMP are defined in the /admin/includes/languages/backup_mysql.php file." I don't, however, have a "backup_mysql.php" file in the languages folder. Should this have been created during the install of the mod or is this something that I need to create?

Thanks for your help.

[fourbit]

Elijah,

Looks like you don't have everything uploaded. Yes, there is a backup_mysql.php file in the admin\includes\languages\english directory.

Make sure you upload all of the directories with their files in them.

Paul

[Renz]

Having some problems with the MYSQL DB Backup add on,
I have had this feature and I happen to use it religiously that was up until a few days ago when we moved server. At this point the backup button disappeared from the CP, myself and my new host tech have look at this thread and have tried numerous things, he has just emailed me the following as he still cant shed any light on it.

What have we missed, (I even tried a fresh install of the add on)
Thanks in advance zen 138a
RR

These have been checked:

- Path to backup correct - /backups

- backups folder has write permissions

- open base_dir disabled

- register globals on

- php safe mode off

Still doesn't work.

[fourbit]

Howdy RR,

Have you checked the Safe_mode? The code checks that at the server level. So, if it's on there and turned off locally, you will still have an issue with that backup button. Check out post number 38 in this thread. http://www.zen-cart.com/forum/showpo...4&postcount=38

I had to change the code a bit.

Hope this helps.

Paul

[Renz]

Hi Thanks for that

The host said last in his list - php safe mode off I am pretty sure he would be talking at server level not sure how you turn it on/off locally that has not been altered but I can check if you advise on how.

Thanks

RR

[fourbit]

RR,

You can check for that setting in Admin Tools>Server/Version info. Lots of info on server settings there. It will say at the top. But, check a bit further down in the "Configuration - PHP Core" section. It will tell you the Master Value and Local Value for the settings.


Paul

[Renz]

The advice you offered on the code change did the trick for me.....Many Thanks Friend
Regards
RR

[Elijah]

Elijah,

Looks like you don't have everything uploaded. Yes, there is a backup_mysql.php file in the admin\includes\languages\english directory.

Make sure you upload all of the directories with their files in them.

Paul

Hey Paul, thanks for the reply. I do have the backup_mysql.php file in the \english directory, I just thought the it was looking for it in the \languages directory as well. I double checked to make sure I have all files in the correct folders and they look fine, but I am still getting the error message that MYSQLDUMP backup utility cannot be found. Any ideas? My host is myhosting.com.

Cory

[torvista]

I have been locally backing-up and remotely-restoring for some time with no problems during the development phase.

Some problems I have with remote-backup/local-restore:

1) I note that using this to backup the db on my remote hosting server will produce a compressed file when backed up to that server irrespective of whether No Compression is selected or not.

2) A downloaded backup is generated as pure sql correctly.

3) On a local pc, I cannot restore the compressed file produced in 1).
It gives me the error:
Failure: The database was NOT restored. ERROR: FILE NOT FOUND: [D:/My Documents/..etc which points to the right place.

4) The pure sql from the remote, copied manually to that same directory as the 3) error on the local, restores ok.

[DrByte]

Evidently your local pc isn't capable of uncompressing the file properly. If the file is gzipped then you need a way to decompress the gzipped file. Most windoze computers don't do that natively. If you have a tool for doing that, you'll need to properly configure the compression tool filenames in the language file in order for it to use them.