myVesta

Hello,

There is a problem with importing the backup. The system does not import the MySQL content. The database is created, but it is empty; tables and other data are missing.

I created the backup on Debian 11 with MariaDB 10.6 and tried to import it on Debian 12 with MariaDB 10.11. Could the different versions be the cause? Please check this as soon as possible because backups are important!

The command was: nice -n 19 ionice -c 3 v-restore-user username user.2024-09-02_01-05-38.tar

Best regards

Hello,

I have the same problem I install new debian 12 and MyVestaCp restore from backup with this command v-restore-user admin admin.2014-01-14.tar db created but tables didn t restore
Where is the problem I can t solve

Thank you for your help

Hello,

unfortunately the error is still there. I don't know why the developer ignores my bug reports. You can't complain because myvestacp is free. I hope it will be fixed. a solution would be to use another tool for the database like MyOOS Dumper. https://github.com/r23/myoosdumper/arch ... s/main.zip

best regards

You ask for help without providing any data. Where are the error logs? What's to fix? Export/import works fine. MyOOS Dumper does not work with MariaDB (maybe).

There are no error logs, but anyone can test it themselves. The import works, for example, from Debian 12 to Debian 12 with the same MariaDB version. However, it does not work with my example mentioned above. Of course, the MyOOS Dumper works with MariaDB.

1. Problem with importing MySQL content: The system does not import the content of the MySQL database, even though the database is created.

2. Empty database: After the import, the database is empty; tables and other important data are missing.

3. Version conflict: Check if the different versions of MariaDB (10.6 on Debian 11 and 10.11 on Debian 12) could be the cause of the problem.

Let me put it another way. How should a developer understand what is going on and what to fix? Maybe for a fee?

“At least 4624 active servers powered by myVesta” - your case is an isolated one.

I don't care; I reported the error so that it can be fixed for others as well. I also thought it was in MyVesta's interest to address errors to ensure that MyVesta runs stably and reliably. At least, that's what it says on the website: "Focused on security and stability, with a lot of security improvements."

I successfully imported the database using MyOOS Dumper.

What are the errors to be corrected? To fix them, you have to see them. And what you've described - it doesn't happen to others. How do you reproduce the problem? There's no psychic here.

PS. Here's the deal. You live in Africa, I live in Japan, I bought a car from you, they bring it to me, it doesn't go. Fix it.

Logs can't be empty, all actions on the server are recorded. ALL logs must be examined. Find out what was going on, what was missed. If your logs are empty, that's a problem too.

Hello,
I have already described my problem in detail and outlined the steps for reproduction. Additionally, the user cumhur states that he is also affected by the problem. Therefore, your statement "And what you described does not happen to others" is incorrect.

Hello,


My old server debian 11 and mariaDB 10.5 . New server debian 12 and Mariadb 10.11. As I say before can t restore DB.
I copy all db to new server change grp and owner to mysql but didn t work

I will setup new vds server and try again restore all backup

I will inform you , Hope everything goes well