Problem with restoring database

[Scolpy]

Hello!

I'd a problem when I tried to restore database from backup(that created via Create/Restore Backups tool) - I got this message at the restoring:

Unable to restore database database_name.sql to database_name : ERROR 1064 (42000) at line 1 in file: '/home/username/backups/backup/database_name.sql': You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'Warning: The option '--all' is deprecated and will be removed in a future releas' at line 1

Ho can I resolve this problem?

Thanks!

Yonatan

 

[nobaloney]

Search these forums. The answer is in here.

Jeff

 

[Scolpy]

Search these forums. The answer is in here.

Jeff

I searched all over this forums and i didn't find anything!
Can you please give me URL for related threads?

Thanks!

 

[Scolpy]

I searched all over this forums and i didn't find anything!
Can you please give me URL for related threads?

Thanks!

Finally, I found some threads about this:
http://www.directadmin.com/forum/showthread.php?t=35712

I will have to wait until the next DirectAdmin release?
my site is down over a day and when I restoring via ssh there is encoding problem.

 

[DirectAdmin Support]

Hello,

You can grab a fix from your Clients Section. View your license and follow the instructions to get a pre-release binary set.

The other option is to downgrade to an older version of mysql.

This is the related thread:
http://www.directadmin.com/forum/showthread.php?t=35690

John

 

[Scolpy]

Hello,

You can grab a fix from your Clients Section. View your license and follow the instructions to get a pre-release binary set.

The other option is to downgrade to an older version of mysql.

This is the related thread:
http://www.directadmin.com/forum/showthread.php?t=35690

John

I downgraded to version 5.1.41(changed in versions.txt then, I rebuilt MySQL) but I still can't restore the backup(because the same problem) - what can I do now?

 

[DirectAdmin Support]

Hello,

The fix has nothing to do with restores. It only related to creating backups without the warning in them.

If you can, create the backup again using the new binaries.

If you can't create new backups, then you'll have to manually extract the tar.gz files to edit the sql files, remove the warning, then recompress.

John

 

[nobaloney]

In some cases, as I've written previously, you can just copy over the individual mysql database files, if you still have access to them.

Jeff

 

[Erik H.]

Hello,

The fix has nothing to do with restores. It only related to creating backups without the warning in them.

If you can, create the backup again using the new binaries.

If you can't create new backups, then you'll have to manually extract the tar.gz files to edit the sql files, remove the warning, then recompress.

John

Well,

I will not post the words I have just been screaming over here behind my pc but this is really bad.. Well that will be a nice night manually editing over 150+ tar files....

Was it really not possible to prevent me (as a customer) to get in this situation?

 

[floyd]

Well that will be a nice night manually editing over 150+ tar files....

Take 10 minutes out of your day and write a script to do it.