Directadmin backup

Status
Not open for further replies.
S

sogi

New member
Joined
Mar 16, 2010
Messages
3
Hello all.

We are doing backups through DirectAdmin backup function.
In result from this process is also database dump eg. mysite_dat.sql.

From version mysql-5.1.44-freebsd7.0-x86_64 we can find error:

Warning: The option '--all' is deprecated and will be removed in a future release. Please use --create-options instead.

on the top of every dump.
This makes this dump unusable.
Can you help us with it? How we can solve this issue?

Thanks in advance.
 
that warning is into the .sql file without a # at the start of the line?

is just a warning shouldnt cause errors on restore
 
hi i have some error

please fix for me

i want to backup and change server

now i can't to work annything

thank

i user da 1.35.1 with mysql 5.1.44
 
i use DirectAdmin 1.35.1

and MySQL 5.1.44

When i use admin backup and tranfer

i have complete with my backup

but i want to restore my backup

i have error from tickket directadmin

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

when i see database .sql from backup

i have see


Warning: The option '--all' is deprecated and will be removed in a future release. Please use --create-options instead.
-- MySQL dump 10.13 Distrib 5.1.45, for unknown-linux-gnu (x86_64)
--
-- Host: localhost Database: abtnakha_note
-- ------------------------------------------------------

when i edit for frist line i can restore with command

but i want to complete restore from directadmin

please help to fix issue for me

Thank
 
Last edited:
yes when edit .sql and command restore

can work

but i want to restore with da

becluse i want to restore about 500 - 600 user

u can see

i can't edit every database ( about 1-1200 db )

Thank
 
i see, well im thinkin about to install mysql 5.0 on server where u wanna restore backups, then make the restore and then update mysql to 5.1 if needed

you had mysql 5.0 on the server where you made the backups right?
 
a

SeLLeRoNe said:
i see, well im thinkin about to install mysql 5.0 on server where u wanna restore backups, then make the restore and then update mysql to 5.1 if needed

you had mysql 5.0 on the server where you made the backups right?
Click to expand...

do you think that this is normal operation or everybody can work like you?
so answer is - no...

can somebody tell me, if DA creators know about this problem and working on it? is workaround/patch available?

thanks.
 
well.. i dont think is a normal operation... i sayd just a way to workaround the problem till someone with more competence give another way to fix it.

Just wanted to be helpfull.

Sorry.
 
Hello,

I'm about mid-way working through a few new features so can't release the next version quite yet. However, for anyone who is affected by this issue, you can grab the pre-release binaries with this fix by logging into your Clients Section, click your license, and follow the pre-release binary install instructions.

Note that due to some of the new features, you'll need to run:
Code: 
cd /usr/local/directadmin/scripts
./update.sh
after updating so that some key new user files are created (or you might get some read-errors for user files and domain files).

Also keep in mind that the new features are not yet completed, so they're also not tested. If you encounter any issues with changing User IPs or assigning IPs to users, let me know (related to the new features).

Note that an alternative to grabbing the pre-release binaries is to downgrade your version of MySQL from 5.1.44, to an older one, that doesn't throw this warning. I'm not exactly clear on which version it was introduced with, but it's somewhere around 5.1.44 or 5.1.43.

Also, this fix only applies to the system that creates the backups. Any backups created with this warning would need to be created to not have the error in the sql file. The fix does not modify the restore process, only the backup process.

EDIT: Note, if you get segfaults with user creation with these binaries, grab them again. I had found a bug with the new feature that was not yet discovered because it wasn't finish.
Again, these are pre-release binaries, so they may be buggy. For a simpler solution which is less likely to have issues, please downgrade mysql to an older version as I'm not sure what other issues may exist in these DA binaries (they're untested)

John
 
When im using MySQL Administrator to restore the database file is working good.
But from directadmin panel its not working.

So i wil stay using MySQL Administrator till they fix the problem.
 
maybe mysql admin ignore that problem... dunno exactly why but seems is just the mysql server version issue like the other thread
 
I dont think is the version from mysql.

Its on version :

MySQL 5.1.45
MySQL 5.1.44
MySQL 5.1.43
MySQL 5.0.90


Memby the fault is here in phpMyAdmin 3.3.1
 
so yes, when you make a mysql dumb (when directadmin backup do that) mysql will automatically put that line in dump cause directadmin backup use some prefix that will be deprecate soon.

As sayd up, next release will change the prefix on mysql dump for dont cause that warning/error anymore
 
b

DirectAdmin Support said:
Hello,

I'm about mid-way working through a few new features so can't release the next version quite yet. However, for anyone who is affected by this issue, you can grab the pre-release binaries with this fix by logging into your Clients Section, click your license, and follow the pre-release binary install instructions.

Note that due to some of the new features, you'll need to run:
Code: 
cd /usr/local/directadmin/scripts
./update.sh
after updating so that some key new user files are created (or you might get some read-errors for user files and domain files).

Also keep in mind that the new features are not yet completed, so they're also not tested. If you encounter any issues with changing User IPs or assigning IPs to users, let me know (related to the new features).

Note that an alternative to grabbing the pre-release binaries is to downgrade your version of MySQL from 5.1.44, to an older one, that doesn't throw this warning. I'm not exactly clear on which version it was introduced with, but it's somewhere around 5.1.44 or 5.1.43.

Also, this fix only applies to the system that creates the backups. Any backups created with this warning would need to be created to not have the error in the sql file. The fix does not modify the restore process, only the backup process.

EDIT: Note, if you get segfaults with user creation with these binaries, grab them again. I had found a bug with the new feature that was not yet discovered because it wasn't finish.
Again, these are pre-release binaries, so they may be buggy. For a simpler solution which is less likely to have issues, please downgrade mysql to an older version as I'm not sure what other issues may exist in these DA binaries (they're untested)

John
Click to expand...

John,
when you are expecting release of newer version? Only for my own information and to look forward to that :)
 
Status
Not open for further replies.
Back
Top