-
Notifications
You must be signed in to change notification settings - Fork 889
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
Deleting backup files on the destination should not cause backup full stop #5026
Comments
After the destination is altered in any way, the local database is no longer consistent with the destination. It is not possible to know if removing everything was intended. In your case, you should be able to continue using the configuration after deleting the database (on the database page of the backup). |
I believe there is a documented way to recover from this type of failure (where some destination backup files are missing or corrupted), which will keep as much valid information as possible and rebuild anything that's missing or corrupted. This is not done automatically however. |
For partial file loss (maybe the destination dropped something), Disaster Recovery in the User's Manual documents ways, but it's best to work with the experts here or on the forum for more help. Total delete situation here leaves no pieces to pick up though. |
Does deleting the database as suggested by @Jojo-1000 solve your problem ? |
I just exported the whole backup settings, deleted and re-imported. Anyway, the reason I bring it up is because it is not user friendly approach. It should suggest recreating back up from scratch by clicking a button or silently do it itself. |
This issue is stale because it has been open for 15 days with no activity. |
This issue was closed because it has been inactive for 15 days since being marked as stale. |
Environment info
Any
Description
Deleting backup files on the destination should not cause backup full stop. Currently backup stops and the window with "please repair" pops up. Repair doesn't work thou. I don't see the reason backup should permanently fail like this.
Steps to reproduce
The text was updated successfully, but these errors were encountered: