Question regarding Block Generation recommendation in AWS S3 Object Storage

[rin]

Hi Team,

I have a question regarding Block Generation design in AWS S3 Object Storage.

I understand that reducing the Block Generation period (for example, from 30 days to 1 day) is not considered a recommended approach in VBR v13.
https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13

My understanding is that a shorter Block Generation period could make the actual deletion timing closer to the configured immutability period.

Could you help me understand the reason why this approach is not recommended?

Is it mainly because a shorter Block Generation period can no longer guarantee the intended immutability protection for all data blocks, or are there other design considerations behind this recommendation?

Best Regards,
Rin

[david.domask]

Hi Rin,

I advise read the User Guide page on Block Generation first.

Block Generation is about reducing API costs while maintaining the immutability of the chain, and a shorter block generation will increase the API call count to ensure immutability is maintained.

Block Generation has never been recommended to adjust manually without direct guidance from Veeam Support, so that's not just a v13 recommendation; the default values are typically best balance.

v13 (and 13.1) bring additional improvements to the immutability model on Object Storage as well by allowing Immutability based on retention period as opposed to the minimum immutability model, which significantly reduces the overall API calls and reduces excess storage consumption, and in general is our recommendation.

In short, do not touch Block Generation in general, there is no need typically.

[rin]

Hi David,

Thank you for the explanation.

After reviewing the User Guide and your comments, I believe I now understand the design intent much better.

My understanding is:

- Block Generation exists primarily to reduce API calls and object storage costs while maintaining immutability.
- Shortening the Block Generation period increases the frequency of immutability-related metadata operations, resulting in more API calls.
- The default values are chosen as a balance between immutability protection, storage efficiency, cleanup behavior, and API consumption.
- Therefore, Block Generation should not be treated as a tuning parameter for adjusting deletion timing.
- In general, the default configuration is the recommended approach unless Veeam Support specifically advises otherwise.

I also understand that VBR v13 introduced improvements to the immutability model and retention-based immutability handling, which further reduces both API calls and unnecessary storage consumption compared to previous versions.

This answers my question.

Thank you for taking the time to explain the design philosophy behind it.

Best regards,
Rin