The seven days retention period you configured might be a part of the object lock configuration for Cloudian (which could be enforced at the bucket level or object level). However, the retention period applied to the objects might not be exactly the same as your configured setting if the backup software has its own retention policy in place, which could be influencing the final retention of the objects.

Some backup software (depending on the vendor and implementation) might add its own retention or additional metadata to objects in the object storage. This could extend the retention period beyond the 7 days you specified in Cloudian. The software might also implement an additional internal retention policy that doesn't fully synchronize with Cloudian’s native retention settings.

Hi @epul

I found the below points can you please consider them.

1. Check Cloudian's Object Lock Configuration: Ensure that the retention period is configured as expected at both the object level and bucket level in Cloudian.


2. Review Backup Software Retention Settings: Check if your backup software has any additional retention policies that could be affecting the retention period of the backup objects.


3. Confirm Versioning and Metadata: Review if any versioning or metadata settings might be causing the retention period to be extended unintentionally.

The retention period adds days see this page for the explanation on block generation - https://helpcenter.veeam.com/docs/backup/vsphere/hiw_immutability_os.html?ver=120

It is 7 days plus additional days due to the chain.

Hi @Chris.Childerhose and @waqasali thanks for the answer, I truly appreciate it,

I found an answer in the article that Veeam Backup adds 10 days for object storage types other than Amazon and IBM. This means the calculation is: 7 + 10 = 17 days. Today is 2024/11/07, so 17 days from now would be 2024/11/24. Is that correct?

Hi @epul  Today is 2024/11/07, so 17 days from now would be 2024/11/23 because today's day would be counted.

Hi @waqasali, but Cloudian Management shows 2024/11/24.

then fine this is good.

Hi @waqasali thanks.

Another questions, 

If the retention in object storage is added, is it possible for data to remain undeleted in the performance tier during the automatic deletion process by Veeam or when moved to the capacity tier? For example, the configuration I have is as follows:

• Backup job retention policy: 14 days
• Target is a Scale-out repository with the following settings:
  • Performance tier is object storage with an immutable retention of 7 days
  • Move to capacity tier after the last 7 days
  • Capacity tier is object storage without immutable retention

 Because I noticed that several repository sizes are larger than the backup size

Hi @epul  reasons for the larger repository sizes delayed in deletion If the immutability period on the performance tier is active deletion might be deferred until that period expires and data duplication when data is moved to the capacity tier it may still exist in the performance tier until confirmed deletion occurs and the metadata overhead the veeam may maintain metadata or temporary data during the move process contributing to the size.

Hi @epul retention and data movement settings can indeed lead to data remaining in the performance tier for specific reasons. backup job retention policy 14 days and performance tier 7 days and older data move to the capacity tier.

Hi @waqasali,

OK, understood. Thank you for your answer, it was very helpful to me.

Hi @epul I’m glad to answer you I try my best for the community as well.