You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 17, 2019. It is now read-only.
--non-stop is not that tolerant of db servers dropping connections or other random issues that could occur when something is running for extended periods of time. mogbak itself is very good about resuming a backup that it crashed on but if --non-stop crashes it's not going to automatically start.
Need to get better about rescuing database exceptions and handling them in a sane manner -- perhaps pause and retry later if it can't connect..etc
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
--non-stop is not that tolerant of db servers dropping connections or other random issues that could occur when something is running for extended periods of time. mogbak itself is very good about resuming a backup that it crashed on but if --non-stop crashes it's not going to automatically start.
Need to get better about rescuing database exceptions and handling them in a sane manner -- perhaps pause and retry later if it can't connect..etc
The text was updated successfully, but these errors were encountered: