-
Notifications
You must be signed in to change notification settings - Fork 873
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backup job fails with "Directory not found" error #8245
Comments
There is evidence that the issues started when we upgraded from 2.2.30 to 2.2.32. Hopefully that helps narrow down the problem. |
Hi .
It is already fixed in 2.2.34 could you try it ?
On Mon, Apr 30, 2018, 19:10 Predrag Gruevski ***@***.***> wrote:
There is evidence that the issues started when we upgraded from 2.2.30 to
2.2.32. Hopefully that helps narrow down the problem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8245 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGaah6sFuf4yrNbm7s31C9PDadxHCzcks5ttzdsgaJpZM4Tswen>
.
--
Best regards,
Andrey Lomakin, R&D lead.
OrientDB Ltd
twitter: @Andrey_Lomakin
linkedin: https://ua.linkedin.com/in/andreylomakin
blogger: http://andreylomakin.blogspot.com/
|
Hi @Laa, thanks for the speedy reply. It doesn't seem like 2.2.34 is listed on the website: https://orientdb.com/releases/ Is there a different location where I should download it from? |
Hm ... We released 2.2.34 .
Could you dowload it from maven repository .
On Mon, Apr 30, 2018, 19:29 Predrag Gruevski ***@***.***> wrote:
Hi @Laa <https://github.com/laa>, thanks for the speedy reply.
It doesn't seem like 2.2.34 is listed on the website:
https://orientdb.com/releases/
Is there a different location where I should download it from?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8245 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGaahy93FSwedBwQUvqRaOZKRE9oy6Nks5ttzvXgaJpZM4Tswen>
.
--
Best regards,
Andrey Lomakin, R&D lead.
OrientDB Ltd
twitter: @Andrey_Lomakin
linkedin: https://ua.linkedin.com/in/andreylomakin
blogger: http://andreylomakin.blogspot.com/
|
Thanks, I'll give it a shot. |
Hey @Laa, I upgraded to 2.2.34 and now there's a different problem. While the generated backup file is valid, and can be loaded onto a new server just fine, it is missing a large amount of data. A diff between the real database and the database restored from backup shows that the backup only contains 70-75% of the data of the original data. The missing data is data that was originally created at least a few days prior to the backup, and was not modified during the backup process. Any advice would be much appreciated -- thanks in advance! |
@obi1kenobi I do not get it completely. Could you provide a detailed example? |
Using the OrientDB automatic backup plugin:
We don't do any additional processing of the backup file. Attempting to load the generated backup file produces a database that OrientDB loads just fine, but appears to be incomplete as I described. I'll keep an eye on the situation and if it happens again, I'll try to get you log files that you can look at. In the meantime, I think there's at least one bug (at least in 2.2.32, not sure if it was fixed in 2.2.34 since I can't find a changelog) that you should be able to easily reproduce. If the backup process fails, I would expect no backup file to be generated, but 2.2.32 would still output a "backup.zip" file with whatever fraction of the backup managed to complete. This behavior hides the error and makes monitoring more difficult -- it means that the monitoring system has to read OrientDB log output and parse it for error messages, rather than just looking for the backup file to be generated and complaining if it doesn't find it. Thanks for looking into this! |
@obi1kenobi issue with removing of the backup file in case of error is fixed. |
Thank you -- looking forward to the next release :) |
OrientDB Version: 2.2.32
Java Version: Open JDK 8
OS: Linux
OrientDB is configured to do periodic backups of a given database.
Expected behavior
Actual behavior
Steps to reproduce
Unfortunately, I am not quite sure how to reproduce the issue. However, given that the error now appears regularly, perhaps it is related to the size of the database?
The text was updated successfully, but these errors were encountered: