[FeatureRequest] Remove-VBOEntityData for expired object in immutable repository

[dejan.ilic]

We have data that I want to remove before Backup for M365 decides it is time to do it.
The repository is immutable, but the retention time has passed.

Unfortunately, the remove-vboentitydata doesn't seem to check the immutability and only throws an error.
Remove-VBOEntityData: Unable to use an immutable object storage repository for a data management job.

Please allow removal of expired data on immutable repositories also.

[Polina]

Hi Dejan,

I have to say that this is not going to happen. We cannot allow for on-demand data removal from immutable repositories. You will have to wait intil the retention does its job.

[nirah47840]

We have data that I want to remove before Backup for M365 decides it is time to do it.
The repository is immutable, but the retention time has passed.
basketball stars
Unfortunately, the remove-vboentitydata doesn't seem to check the immutability and only throws an error.
Remove-VBOEntityData: Unable to use an immutable object storage repository for a data management job.

Please allow removal of expired data on immutable repositories also.

I’ve run into the same issue, would be great if Veeam allowed Remove-VBOEntityData to clean up expired data even on immutable repositories, as long as it's past retention.

[dejan.ilic]

In my case the data is not valid and drawing unnecessary costs (stored in the cloud) while I await for the retention to kick in.
As long as it is past the retention date for immutability I would like to be able to remove the data.

This would also make the product more consistent with what can be done in VBR for example.

Hi Dejan,

I have to say that this is not going to happen. We cannot allow for on-demand data removal from immutable repositories. You will have to wait intil the retention does its job.

[Polina]

But, the retention task already cleans up data that has past the specified retention period.

@dejan.ilic
How long is the wait time before retention does its job?
How do you identify which objects have already fully passed the retention period and can/should be removed?

[dejan.ilic]

I set up 30 days retention and that time has passed.
I noticed that the software seems to take much longer (at least twice) the retention time before it deletes from the repository.

It is easy for me to identify the objects as I have stopped using the particular repository as all content should expire (due to switching to new repository in another datacenter).
The repository is still connected to the server, but not used in any job, so the server still manages the data and the retention should work.

I have a Case # 07705705 on this issue.

[t7MevELx0]

Can Veeam confirm whether `Remove-VBOEntityData` simply refuses to process any repository that has immutability enabled, based solely on the repository configuration, without checking whether the relevant objects’ Object Lock expiration dates have passed?

We are running VB365 8.5.0.1014. If the cmdlet remains unavailable even after the affected objects are no longer locked, then I would like to +1 this feature request. Veeam also does not support using S3 lifecycle policies to clean up repository data, so there is no supported on-demand method for removing expired or otherwise unnecessary entity data from an immutable repository. The only Veeam-aware cleanup tool available is therefore unusable.

It would make sense for `Remove-VBOEntityData` to evaluate the underlying object locks and remove only data that is no longer immutable, rather than rejecting the entire repository because immutability is enabled.

Case #08223317 — Clarification of Remove-VBOEntityData Behavior on Immutable Repositories

[Polina]

Hi t7MevELx0,

Using Remove-VBOEntityData on immutable repositories is restricted by design. Cleanup is performed by retention only.

Thanks!