I have configured my bucket with immutability.
I have configured my object storages with a 7-day immutability in Veeam.
The retention policy of the backup job in Veeam is 7 days for one backup and 30 days for another.
My question now is in Backblaze, I have to configure the lifecycle rules. What should I configure here to avoid receiving an astronomical bill for the occupied TBs:
In the documentation, it says this:Keep all versions of the file (default)
Keep only the last version of the file
Keep prior versions for this number of days:
Use custom lifecycle rules:
So, I conclude that during those 7 days, Backblaze will keep versions of files hidden, but if "Keep all versions of the file" is selected, will they still remain after the 7 days? Would it be better to configure a "custom lifecycle rule" to hide after one day and delete after 8 days?Object Lock and Versioning
By default, Backblaze B2 Buckets have versioning enabled, so as you upload successive objects with the same name, previous versions are preserved automatically. None of the Object Lock modes prevent you from uploading a new version of a locked object; the lock is specific to the object version to which it was applied.
You can also hide a locked object so it doesn’t appear in object listings. The hidden version is retained and can be revealed using the Backblaze web UI or an API call.
As you might expect, locked object versions are not subject to deletion by lifecycle rules—any attempt to delete a locked object version via a lifecycle rule will fail.
If I have 7 days of immutability in the object storage and Veeam starts deleting after 7 days, will I have any problems? Should I give Veeam an extra day in the retention policy? I understand that with the 30-day backup there should be no issues because it has a 30-day retention policy.
I'm not sure if I'm getting this right, does anyone know the correct way to configure it?