Cannot apply immutability because blob Case #07499827

[Stabz]

Hello guys,

I have the following error message in a job for two users:

Code: Select all

24/01/2025 15:57:42 :: Failed to process OneDrive: User (https://company-my.sharepoint.com/personal/user). Cannot apply immutability because blob Veeam/Backup365/bkp_all/Organizations/15dc4d5563e/Webs/3dbfb3775/Files/Data/da8c73ca4a094ba983db0a4265e5220b does not have a version yet.

We use a S3 Compatible Storage (Dell ECS).

I opened a case to Veeam Support but currently the case still under investigation after almost 3 month.

I installed the latest version 8.1 but the error persist.

Any idea?

[Mildur]

Hi Philippe

Our RnD team confirmed that they are working on a fix.
I'll keep an eye on the internal RnD ticket.

Best,
Fabian

[Stabz]

Hello,

Ok thank for the feedback Fabian.

[Mildur]

Hi Philippe

It looks like we are expecting a fix available for testing by our QA team early next week.

Best,
Fabian

[Seb.pythoud]

hi.
any news on this issue ?
same problem here.
thx.

[Mildur]

Hi Seb

According to our internal system, the fix is still in development.
As always, please open a case with customer support to verify if you are affected by the same issue.
Also don't forget to share the case number here.

Best,
Fabian

[evgenich]

Hi,
On latest patch we get error Failed to process team files: xxxx. Failed to apply immutability to object because object is already immutable. Object is Word protected and cannot be overwritted.
Why it could happen?
Repo is immutable (S3 Minio), have versioning enabled. Retention time set on bucket level

[Polina]

Hi Evgenii,

It would be a question to support. Please collect all logs, open a case, share your logs with our support and post your case ID here.

Thanks!

[admd]

Hello,

This issue is still happening even after update to 8.1.1
Case #07499827 is opened since november.
Anyone else ?

[Polina]

Hi @admd,

In fact, 8.1.1 is fixing the root cause and the error should be gone after the upgrade.
Are you seeing it on the same objects after the upgrade?

[jjonesasl]

Hi I am running 8.1.1 and also still seeing this issue using S3 (minio) Case 07642807

[admd]

Hi @admd,

In fact, 8.1.1 is fixing the root cause and the error should be gone after the upgrade.
Are you seeing it on the same objects after the upgrade?

Yes on the same objects. On S3 Storage with immuability.
I will try a manual fix with steps provided by support. I have just received them this week.
I will let you know if that's fixing it.

[Stabz]

Hey,
I have update my VBM to version 8.1.1.159 P20250328 and I still have the error.

[Polina]

Hi Philippe,

In such a case, please contact our support, and share your case ID in this thread.

Thanks!

[admd]

Hello all,

Any help today would be appreciated for #07499827.

Regards,

[Stabz]

Hey,
My case is opened since Nov 12, 2024
Case #07499827

[superdevo]

Following. Having the same issue