Delete a Backblaze B2 bucket that is not empty
Backblaze refuses to delete a bucket with anything in it, including versions and hide markers you cannot see, and its console points you at a lifecycle rule that takes two days. Bucketree counts what is there, tells you what will go, takes the bucket’s name typed, and does the whole thing.
Thirty days free, then $25 a year.
One confirmation, one list
Every version, every hide marker, every unfinished upload, and any replication job on the bucket with the keys Bucketree made for it, each with a count. Only lines with something on them appear.
Told before it starts
Bucketree names which files and why before it starts, and nothing is deleted. Files under a retention lock or a legal hold cannot be removed by anyone.
A thousand versions a call
Deleting is quick; counting a bucket with a great many versions is the slow part, and both show as they go. Stop means now.
Folders go the same way
A folder in B2 is a name prefix. Deleting one means every file whose name begins that way, and Bucketree says how many and how much.
How it deletes
Everything it removes is gone for good, and the one red line on the page says so. A replication that reaches into another account leaves a rule there pointing at a bucket that no longer exists; Bucketree names it and suggests the better order, which is to remove the job from that account first.
