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

backup won't work if old newJoplinBackup.7z file is there #40

Closed
th-ros opened this issue Apr 22, 2022 · 4 comments
Closed

backup won't work if old newJoplinBackup.7z file is there #40

th-ros opened this issue Apr 22, 2022 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@th-ros
Copy link

th-ros commented Apr 22, 2022

Hello,
today I recognized that no backups were created if the file newJoplinBackup.7z is still in the backup directory.

My Joplin is running all the time on my Notebook and I made backups every hour on a network drive. Today I recognized the file newJoplinBackup.7z in the backup directory which was many days old an since this date no backups were made anymore.

After some tests I found the solution: I removed the file and everything works fine.

So I think this is a bug and should be solved. I think the old newJoplinBackup.7z was the result of a interuppted backup by a shutdown during the backup was running.

Greeting and thx for the nice plugin, Thomas

@JackGruber JackGruber added the bug Something isn't working label Apr 22, 2022
@JackGruber
Copy link
Owner

Sorry for the late response. I can not currently reproduce the behavior.
What are / or were your backup settings?

@th-ros
Copy link
Author

th-ros commented Jul 12, 2022

My backup settings are these. Drive h:\ is a network drive.
my Joplin backup settings

@JackGruber
Copy link
Owner

Ok, tnx. I try to replicate it with this settings.

@JackGruber
Copy link
Owner

The behavior that the backup does not run if the newJoplinBackup.7z already exists in the backup directory I could not reproduce. But I have found a other bug during the investigation.
If the file was existing from a privues aborted backup, the newly created backup could then contain old and new backup data.
To prevent this the file is now deleted to the begin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants