Skip to content
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

The backup/restore process should be more resilient on intermittent errors #688

Open
DDvO opened this issue Jun 17, 2024 · 0 comments
Open

Comments

@DDvO
Copy link

DDvO commented Jun 17, 2024

Since #685 got closed without handling all points mentioned, I repeat one of the points here:

On any intermittent (e.g., network) error, backup fails (is not resilient to such issues),
and on retry it partially takes, in total, even more space and time.

When using remote (online) storage, both backup and restore should not immediately fail on data transmission errors,
but only after a reasonable (ideally, configurable) number of unsuccessful retires with suitable timeout periods.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant