Database backup mySQL can't restore

[tvadpro]

I'm running ZC 1.3.7 with the Database backup mySQL mod. Haven't had any problems with this contribution in the past, but on this one particular site, it fails to restore from backups. I always get:

Result code: 1
Error Failure: The database may NOT have been restored properly. Please check it carefully.

[DrByte]

Your host probably doesn't let you have access to the "mysql" binary in order to perform the restore.

You'll likely have to use phpMyAdmin to load the SQL file manually.

[tvadpro]

Thanks Doc! I'll check with IX Webhosting and ask if they can grant me access to the mySQL binary.

Your host probably doesn't let you have access to the "mysql" binary in order to perform the restore.

You'll likely have to use phpMyAdmin to load the SQL file manually.

[tvadpro]

Okay, I checked with IX Webhosting's tech support, and access to the mysql binary was not the problem.

What else would cause Result code: 1 / Error Failure: The database may NOT have been restored properly. Please check it carefully?

Dear Sean!

Both mysql and mysql_dump are present on the server and accessible for php (httpd) user. Below you may find path:

/usr/bin/mysql
/usr/bin/mysqldump

Please let me know should you need further assistance.

[tvadpro]

Anyone have any idea why Database backup MySQL doesn't restore? It doesn't Download without storing on server either -- except when Skip lock tables option is selected. As for restoring, though, it refuses to restore no matter what.

Okay, I checked with IX Webhosting's tech support, and access to the mysql binary was not the problem.

What else would cause Result code: 1 / Error Failure: The database may NOT have been restored properly. Please check it carefully?

[eist1]

I am having the same issue with 1.3.7 and the backup module. I do a backup and it says that it has backed it up (shows the backup file) but try and restore and get the Error 1 error. Also, with the backup file that the module created I tried importing it from MySQL Admin and it errors out, so it is not backing up correctly either. I now am using MySQLAdmin to export and import my database until this is resolved. Hope someone has an answer.

[tvadpro]

I am having the same issue with 1.3.7 and the backup module.

Well, at least we both know we're not the only one.

Did you already ask your hosting provider (as I did) whether the mysql binary is accessible on your server?

Sean

[tvadpro]

We know the problem seems unrelated to server configuration, as eist1 has more than one Zen-Cart site on the same server, but only one of those sites fails to restore from backup via Database Backup MySQL.

I'm stumped as to what causes this -- so stumped that I'm considering a second Zen-Cart installation (subdirectory) on the same server as my problem site -- just on the off chance I might make the mod work on the second Zen-Cart -- and then incrementally change the second one to mirror the first -- until the restore-from-backup breaks, thus isolating the root of this excruciating headache.

Or I might knock my own brains out with a large rock.

Anyone have any idea why Database backup MySQL doesn't restore? It doesn't Download without storing on server either -- except when Skip lock tables option is selected. As for restoring, though, it refuses to restore no matter what.

[DrByte]

Anyone have any idea why Database backup MySQL doesn't restore? It doesn't Download without storing on server either -- except when Skip lock tables option is selected. As for restoring, though, it refuses to restore no matter what.

1. What's with the large font ?

2. "Skip Lock Tables" refers to a database-permissions setting. If your database userID doesn't have permissions to lock tables before doing an export, you need to check that box so that the backup doesn't attempt to do the usual lock-tables action. If your host won't give you control over that permission setting, you'll have to be sure to check the box every time you do a backup.

3. "Result code: 1 / Error Failure: The database may NOT have been restored properly. Please check it carefully?"
This error message occurs when the EXEC() function is called and returns error code #1 from the Operating System back to PHP.
You'll have to dig up what Error code 1 means for your operating system.

You could try running the restore in debug mode to see if it gives you any further information for diagnosis:
a) Simply select a file to restore,
b) click the "restore" button,
c) then add &debug=ON to the URL, press Enter, and click the restore button on the right-side box.
(you might even take note of the suggested EXEC() command syntax posted in the sidebox and try it via command line)
d) Then post the additional output here, masking your passwords with ****** if you care to do so.
_

[tvadpro]

Thanks DrByte!

I'll follow your instructions for restoring in debug mode, but I'll have to wait until late this evening. We're talking about a production site which is busiest 0900-1700 EST. Last time I got error #1 while restoring-from-backup, I soon discovered my address book table was corrupted and several default customer addresses were missing. I don't know if there is a causal relationship between my restore problem and my address book problem, but just in case there is, I'd hate to put the site in maintenance mode during prime-time.

I have no problem checking the skip-lock-tables box before every backup -- I should have also mentioned that even though skip-lock-tables box is checked, the backups I download still contain lock (and unlock) table commands which I must remove manually before I can run the SQL in phpMyAdmin. It's as if the skip-lock-tables box has no function other than to prevent creation of a backup when the database user lacks this permission.

As for the large font, it's just a semi-conscious attention-seeking behavior. My psychiatrist thinks this sort of thing is rooted in my fear of abandonment, like the way my dog goes bananas every time I pick up the car keys. If it annoys you, I'll stop.

1. What's with the large font ?

2. "Skip Lock Tables" refers to a database-permissions setting. If your database userID doesn't have permissions to lock tables before doing an export, you need to check that box so that the backup doesn't attempt to do the usual lock-tables action. If your host won't give you control over that permission setting, you'll have to be sure to check the box every time you do a backup.

3. "Result code: 1 / Error Failure: The database may NOT have been restored properly. Please check it carefully?"
This error message occurs when the EXEC() function is called and returns error code #1 from the Operating System back to PHP.
You'll have to dig up what Error code 1 means for your operating system.

You could try running the restore in debug mode to see if it gives you any further information for diagnosis:
a) Simply select a file to restore,
b) click the "restore" button,
c) then add &debug=ON to the URL, press Enter, and click the restore button on the right-side box.
(you might even take note of the suggested EXEC() command syntax posted in the sidebox and try it via command line)
d) Then post the additional output here, masking your passwords with ****** if you care to do so.
_