Autobackup update #6695
Open
Autobackup update #6695
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Found the path bug for #6675, adding the fix and testing |
…perated expired files check to function, more message edits, serverwarnings
|
So, added some extra messages within the backup process. Normally only backup success will be logged. If you do an autobackup from the console a bit more info is given. If the debug level 'backup' is added, the logging will be even more. The bug was in using an absolute path in the backuppath parameter of the autobackup. Tested on windows & linux. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added an option to configure the hour during which the autobackup should be done instead of being determined by the service start time to have more control if wanted.
There is also the extra logging for #6675. I tried to replicate the issue, but it worked every time, on windows and linux.
Hopefully the extra logging will help to determine the issue.
Debug logging for the backup was under the 'db' category, moved it to the 'backup' debug category to keep it clean.
Add "debug": "backup" to the config.json for extra logging besides the default start and file removal logging of the autobackup.