@sfirmes
I am talking about the performance tier.
You confirmed in your post that for barks scenario (see intial post) this is an expected behavior.
So that we have restore points which are not accessible and cannot be restored, even if they are there on the S3 storage (because retention is shorter than immutability).
For v12 there was a PowerShell command to still import those restore points, but this possibility is not available anymore with v13.
Your provided solution is to set the retention equal or higher than the immutability duration.
I can relate to this behavior after your explanation but I would not have expected that, just like barks.
My expectation is that if a restore point cannot be delete because of immutabiliy, that it is still available for restores.
Therefore, I think this behavior needs to be documented.
-> I have not seen this in the docs or can you show a link?
This scenario is documented here as scenario 2: https://helpcenter.veeam.com/docs/vbr/u ... ity-period
It mentions that we have a retention of 17 days but it does not mention that we can only use the last 3 days for restores.
Therefore, my ask to you was to add more details for scenario 2 on the page above:
If my understanding is correct, then the correction or adjustment should be as follows:
* scenario 2: retention 17 days, but only 7 days can be used for restores because only the retention days count for available restore points
-> Is my understanding correct and can you update that page?
For scenario 3 on that page:
-> If there is no retention specified, then how many points are available for restores?
-> Do the immutability of 7 days guarantee 7 days of available restore points?
And a separate question about the block generation period:
-> If I understood this correctly, then those backup points can never be used for restores because this longer retention is only for the optimation of S3 API calls. Correct?
I am talking about the performance tier.
You confirmed in your post that for barks scenario (see intial post) this is an expected behavior.
So that we have restore points which are not accessible and cannot be restored, even if they are there on the S3 storage (because retention is shorter than immutability).
For v12 there was a PowerShell command to still import those restore points, but this possibility is not available anymore with v13.
Your provided solution is to set the retention equal or higher than the immutability duration.
I can relate to this behavior after your explanation but I would not have expected that, just like barks.
My expectation is that if a restore point cannot be delete because of immutabiliy, that it is still available for restores.
Therefore, I think this behavior needs to be documented.
-> I have not seen this in the docs or can you show a link?
This scenario is documented here as scenario 2: https://helpcenter.veeam.com/docs/vbr/u ... ity-period
It mentions that we have a retention of 17 days but it does not mention that we can only use the last 3 days for restores.
Therefore, my ask to you was to add more details for scenario 2 on the page above:
If my understanding is correct, then the correction or adjustment should be as follows:
* scenario 2: retention 17 days, but only 7 days can be used for restores because only the retention days count for available restore points
-> Is my understanding correct and can you update that page?
For scenario 3 on that page:
-> If there is no retention specified, then how many points are available for restores?
-> Do the immutability of 7 days guarantee 7 days of available restore points?
And a separate question about the block generation period:
-> If I understood this correctly, then those backup points can never be used for restores because this longer retention is only for the optimation of S3 API calls. Correct?
Statistics: Posted by vee789 — May 13, 2026 8:33 am
