elhefe38

@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.

@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.

@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.

@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.