Veeam365 and problem with Object version invalid

[jfrobs]

31.07.2025 05:55:38 :: Failed to process OneDrive: "The collaborator name". Cannot read the object from object storage because the object version is invalid: -1890210654. :: 0:00:32

I am encountering an issue when backing up veeam365 on my Object first S3 appliance.

I only have this for a single user's OneDrive...and unfortunately, I am not sure what to do.

Any ideas?


Veam365 last version : 8.1.2.180

[Mildur]

Hello,

That sounds like a technical issue. We cannot investigate such issues through a forum topic.
Please provide a support case ID for this issue, as requested when you click New Topic. Without case number, the topic will eventually be deleted by moderators.

The error message could mean that there is a problem with the objects on your object storage. Our support will be able to investigate the root cause for you.

Best regards,
Fabian

[jfrobs]

Thank you for your feedback.

I work with our partner in Switzerland, so I will ask them to open a ticket for me.

regards

[Mildur]

You're welcome.

I found your case number and will keep an eye on it.
May I ask, are there any lifecycle policies configured on the object storage?

Best regards,
Fabian

[jfrobs]

I keep the data for 5 years and immutability for 30 days.

The strange thing is that I only have this problem with one item... a user's OneDrive.
Everything else works perfectly.

[Mildur]

Hi,

I asked because we have seen similar messages when Object Storage lifecycle policies were used.

These policies are managed directly on the object storage and can modify objects outside of Veeam products. This may result in backup and restore issues, which is why lifecycle policies are not supported.

Let's wait for our support team to investigate the logs from your backup server.

Best,
Fabian

[jfrobs]

Hello,

I answered a few questions from support this morning.
I had already uploaded the logs, but they must not have seen them.

At Objectfirst, there aren't many options:



Only versioned for put immuability on the bucket.

And versioning is active on both sides.

[Mildur]

Yes, I have the same settings in my lab with Object First.
As far as I know, Object First does not have lifecycle policies, so you're good from that perspective.

Let's wait and see what support finds out.

Best,
Fabian

[jfrobs]

We ran quite a few tests with support.

In the end, if I create a new bucket, everything is OK.

For me, recreating an empty bucket and redoing a full backup of our tenant is not a solution.
I have no desire to multiply backup buckets...

We need to be able to delete the data corresponding to the user's OneDrive and run a backup of the tenant in order to have a clean backup of their OneDrive.

So yes, I will lose the old backups for this specific user, but that's okay.

However, I don't know how to do this, and in my opinion, with 30-day immutability, we'll have to wait before we can delete the files.

Support hasn't responded to me on this point... I'm waiting for a response, but I get the impression that they don't know themselves.

[Mildur]

Hi,

There is a cmdlet available to delete backups for a single user, and you can specify it to remove only OneDrive backups.

However, due to the error message you received, I can't guarantee that the backup will be deleted as expected. It's highly recommended to verify this cmdlet with your support engineer before proceeding.

Remove-VBOEntityData

Code: Select all

Remove-VBOEntityData -Repository $repository -User $user -OneDrive

Best regards,
Fabian