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 rotation does not delete unnecessary ones after decreasing backupDepth #31

Open
proninyaroslav opened this issue Jun 26, 2024 · 3 comments

Comments

@proninyaroslav
Copy link
Contributor

proninyaroslav commented Jun 26, 2024

Previously, I used the default depth == 7, but decided to switch to 3. But after the backup, I still see extra folders with system files (backup.4, 5, 6, 7). Can I safely remove them?

@pedroetb
Copy link
Owner

This should be tested first to be sure, but I think it will be safe to remove old directories when you reach at least 4 backups (for depth == 3).

Please, be careful if you test this!

@proninyaroslav
Copy link
Contributor Author

Please, be careful if you test this!

How can I check if the integrity of the backup is broken after this?

@pedroetb
Copy link
Owner

pedroetb commented Jul 3, 2024

Please, be careful if you test this!

How can I check if the integrity of the backup is broken after this?

Looking for a file which has reached the new last stage of backup and had previous changes beyond that stage . If it's not there or it's not at expected state, then there is a problem.

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