Backup-Job Error after upgrading to 8.4 (Index was outside the bounds of the array.)

[aeph]

After upgrading our environment to latest Version (8.4.0.1457) we are getting job errors with this type of message:

ERROR: Failed to process site: XXX. Index was outside the bounds of the array.

And some warnings:

WARNING: Processing team files: XX completed with warning: Index was outside the bounds of the array.

At the moment just teams and sharepoint is affected. Not all sites and teams of a organization is affected.

Also quite strange: Veeam M365 automatically performed a full backup for one of the affected organizations, but this did not resolve the issue. We retried the job several times, yet many errors still remained.

The next day, the errors for this organization were gone, but new organizations were affected instead. After another retry, we were able to successfully complete the daily backup for all organizations.

We are managing around 40 organizations, so it requires significant effort to continuously monitor the status and rerun jobs whenever errors occur.

Someone experiencing the same issue?

Whats interesting: We had this error (veeam-backup-for-microsoft-365-f47/erro ... 02969.html) on some sharepoint sites (400+) and this error seems to be gone.

Case ID: #08080618

[Mildur]

Hi aeph,

Please continue working with our Customer Support team on this issue. I can see they’ve already provided steps to collect additional debug logs.

Right now, the assumption is a “session-level / in-memory state” issue. To confirm this, we’ll need those debug logs.
Once we have the requested log files, our Support team will review them and decide whether the case needs to be escalated to the next tier and/or R&D.

Best regards,
Fabian

[matthew_st]

We have the same error after the update can you tell me how did you resolve that?

[Mildur]

Hi Matthew,

The case had no definite solution or root cause explanation, since the customer solved it themselves by removing and re-adding one of the proxies.

Please keep in mind that just because another user had a similar issue does not mean your environment is affected by the same problem. Applying the same steps used by other customers could make the issue worse for you. That is why it is important to open your own case with our Customer Support team and provide your case number here for our reference.

Please also do not forget our forum policy: technical issues must be resolved with our Customer Support Team, since this is not a support forum.

Best,
Fabian