[Bug] DriveBackupV2 Makes More Local Backups Than Limit
Minionguyjpro opened this issue · 5 comments
Describe the bug
I have set up several backups, for a few folders (autoplug (is for a client called AutoPlug), plugins, root (excluding some files and worlds, this includes most of the server config), world, world_nether, world_the_end). I have set the local keep count to 3, and that works for all of them except for the root/server_config one. That one generates like 10 of them which makes my 50GB space for my container being filled completely immediately. This seems like a bug, as it shouldn't happen and just generate 3. There isn't much to see in the logs (it will say that there is no space left on the device), but I will upload the latest one here anyway.
To Reproduce
- Use the same configuration as mine.
- Setup automatic backups.
- Let it make backups for a while.
- Root backup will have more than 3 local backups while it shouldn't.
Screenshots / Videos
No response
Server and Plugin Versions
- Server Software: Purpur
- Server Version: 1.21-2262-458dc18
- Plugin Version: 1.6.3
Logs
Says Forge Server Log. That's incorrect as you can see based on the information above.
Config
Additional Information
No response
It says Even if local-keep-count is set to zero, the plugin needs to temporarily create a local backup, while it is set to 3. Weird...
I think I found the issue in my config using ./ instead of / for the server_config. I will look for a while now but it should work.
EDIT: Nevermind, seems like I did it correctly with the ..
Hello, I'm also using the latest version of this plugin and may have the same experience as you. I set up a temporary local backup that is automatically deleted after uploading to my OneDrive, but instead of being deleted as scheduled, the backup is stored under "My Backups Path/root". After testing, the plugin automatically deletes the files in the My Backups Path and does not delete the backups in the "root". I'm not sure if this is related to fixing this issue.
If you are not already, please try the latest dev build from our GitHub actions. This should be fixed in the latest dev build.
You may need to manually clear old backups to get it working.