@elhefe38
We already noticed in the job setting:
Warning: Files belonging to this job are now tracked. Old backup archives which are untracked will not be automatically deleted. ^^
@duongcuong96
I understood that, this is not my issue. When I created the backup job, I specified that only the latest 2 runs are to be kept. Now, only the last two runs remained “tracked”, but the “expired” files are not correctly deleted on the bucket.
Check wordpress screenshot and backblaze screenshot
-
This reply was modified 4 years, 8 months ago by
elhefe38.
@elhefe38
hmm could you test on a new bucket without any old files?
Thanks!
@duongcuong96
Same behavior with a freshly created bucket.
@elhefe38
Strange, I tried many times but still could not reproduce the reported issue 😐
did you disable deleteBuckets permission?
here are my bucket permissions btw, I just set it to default: https://prnt.sc/1us27rl
@duongcuong96
The only difference I can see is that I use an application key generated with default perms that only had access rights to my backup dedicated bucket, and not the all the buckets. I will try an application key with full permissions.
I however do not understand with the deleteBuckets permission would be needed. Is deleteFiles not sufficient to remove expired backups ?
-
This reply was modified 4 years, 8 months ago by elhefe38.
@elhefe38
did you tried it? Thank you!
@duongcuong96 tried it, identical behavior
-
This reply was modified 4 years, 8 months ago by elhefe38.
@elhefe38
Sorry about the delayde response, I found the “issue”, not exactly an issue I mean,
please check this image: https://prnt.sc/1vvw689
Those files with asterisk(*) are files marked to be removed and they will be remove after about 30 days, that how Backblaze works based on my finding.
So these files without asterisk are the current backup files, in the image, I set keep 3 most recent files so there are 3 files without asterisk.
@duongcuong96
my concern about this is that those deleted-but-still-present files are still counted in the quota and billed… Also when you delete those files from the backblaze UI, they are deleted for good, not just marked with the star. (and I could not find any mention of this on the help). I will try to make use of s3cmd cli to see if the behavior is identical.
@elhefe38
hmm, I would suggest contacting the Backblaze support team and ask if there is a way to just remove them, seems like it happens on Backblaze only.
Please let me know their response!
Thank you!
@duongcuong96 I think I finally understood: when deleting the file, backwpup only marks it as hidden (hence the star next to it). I added a lifecycle rule to the bucket, s.t. hidden files are deleted after one day (which mitigates the issue). The issue seem to be on backblaze’s side, as I can reproduce this behavior using s4cmd.
@elhefe38
great! happy to hear that the issue is sorted out ^^
Btw, In case you find BackWPUp is useful for you, we would really appreciate it if you leave a positive review and rating.
This would encourage us to develop new free features and provide free support 😀
https://ww.wp.xz.cn/support/plugin/backwpup/reviews/#new-post
Thank you so much and have a great weekend!
@duongcuong96 just a follow up from backblaze support: when deleting a file, if you do not supply the versionId, it will only hide the file (i.e. create a new version of the file that is deleted). This is apparently standard in AWS compatible storage, and occurs even when bucket versioning is disabled.
