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

Backups are backing up previous backups (Recursively) #1913

Closed
alex-cardenas opened this issue Feb 4, 2023 · 5 comments
Closed

Backups are backing up previous backups (Recursively) #1913

alex-cardenas opened this issue Feb 4, 2023 · 5 comments

Comments

@alex-cardenas
Copy link

Organizr Version: V2.1.2330
Branch: v2-master
WebServer: nginx/1.20.2
Operating System: unraid

Problem Description:

Backups are also backing up previous backups leading to increasingly larger file sizes.


Reproduction Steps:

Go to Settings > Backup
Manually create a backup
Note File size
Manually create another backup
Notice file size increase
Repeat.
I have mine set on cron weekly and to keep 20 backups. I got up to 152gb for my latest backup (for a total backup folder size of 300gb) before I noticed.


Errors on screen? If so paste here:

None
@alex-cardenas
Copy link
Author

FireShot Capture 003 - Settings - Organizr V2 - 192 168 1 3

@HalianElf
Copy link
Sponsor Collaborator

HalianElf commented Feb 7, 2023

Dupe of #1891 , you need to update

@alex-cardenas
Copy link
Author

I'm pulling this from DockerHub (through Unraid) and the last update was in May by rodexus. Every time I open OrganizrV2, I get the update notification but that is within the container and doing any of the following does nothing: clicking the notification's update now button, going to Settings > Main > Github > Force Install Branch, (from Unraid side) Force update; none of those actually update since, I think, it's pulling from dockerhub

@HalianElf
Copy link
Sponsor Collaborator

Restart the container and check the container logs, it sounds like you got a lock file that's preventing the update script from actually working. If there is a lock file, remove it and either restart the container again or click the update popup in the settings.

@alex-cardenas
Copy link
Author

Checking the logs did show a lock file "index.lock" in a .git folder. I removed that it seems to have updated successfully - thank you.

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

No branches or pull requests

2 participants