Working with Immutability Object Storage: Significant Discrepancy Between Backup Size and Repository Size, Deletion Appears Ineffective

Hi ​@epul ,

I saw in another thread that the lowest number. You can Go for is 1 day for Block Generation. Otherwise it will Change back to the Default of 10 days. 

Maybe ita worth a try. 

https://forums.veeam.com/object-storage-as-backup-target-f52/how-to-reduce-block-generation-days-t87923.html 

Dear All,

Let me ask for advice regarding the significant difference between the backup size and the repository size, which is causing inefficient storage usage and making it seem like deletions are not working properly. Below is my configuration:

• Source Backup: vMWare vCenter

• Destination Repository: Cloudian Object Storage

• Backup Frequency: Once per day

• Full Backup: Once per week

• Rettention: 7 Days

• Immutability: 5 days + 0 days (I modified the registry to set block generation to 0 days

Capture:

Rettention Policy (Job Configuration)

Immutability (Repository Configuration)

Results:

Backup Size 5,20 TB

Repository Size 15,6 TB

 

My Opinion:

1. Could the deletion be failing because the data is still locked by immutability at the time of the deletion? If so, what would be the correct configuration to avoid this issue?
2. Could it be due to a failed checkpoint removal, as shown below:

   

    

 

Thank you for your attention. I truly appreciate your suggestions and assistance.

 

I recommend aligning retention with immutability revisiting block generation settings and running a repository health check to make sure cleanup is working properly.

You can also run it manually by using Veeam PowerShell.

Start-VBRHealthCheck -Repository "YourRepoName"

Thank you all for your responses. What confuses me is that from the beginning, I installed everything with default settings, without changing the registry or reducing immutability. Initially, the retention was set to 7 days and immutability to 7 days as well, without modifying block generation. However, the result is that the repository size is larger than the backup size, even though the repository is only used by a single job.

I previously tested with a small dataset and it was okay — the difference between the backup size and repository size wasn’t too significant. But with a large dataset, the difference is really noticeable.