Veeam 7 reverse inc: Unexpected end of file has occurred

[kte]

Hello, after changing this week all my forward incremental jobs to reverse incremental (veeam7 took a active full) I got 1 job that after 2 days gives this error and I loose all my backups.
The job only contains 1 VM of 250 GB

Error: Unexpected end of file has occurred. The following elements are not closed: OibSummary. Line 1, position 16385.

Case # 00440891

Koen

[foggy]

Koen, you've performed the right step contacting support first. Primarily for future readers: this seems to be an issue with the delimiter in summary.xml metadata file that occurs only on specific number of characters in this file. As a workaround, you can try to exclude or remove one of the VMs form the job (this will change the number of characters in the file and allow to avoid the issue). In your case, however, there is only one VM in the job, so probably you could try to add another one in it to achieve the same result. Thanks.

[kte]

OK I added 2 VM and changed back to reverse incremental

K

[foggy]

Kindly let us know the results, after the job runs.

[kte]

recreated the job and it worked

[foggy]

Thanks for the update, much appreciated.

[kte]

this is the 4th time i got this on 2 or 3 different jobs, i this a bug that ill be fixed soon, because support told me to move the backups to another location and import it again. then it works again for a while after running an active full. this thakes lot of time and every time i add a vm in it i seem to have the issue.

k

[veremin]

Hi, Koen. Your original case seems to have been closed, once proposed workaround appeared to work. Did you open a new one?

Thanks.

[kte]

I seem that support only proposes the work around and don't investigate the issue on why it happens

[veremin]

Based on the original ticket, after having a webex session with our support specialist, everything, according to your response, seemed to be working, so the case was closed as “Closed by Customer.

Typically, new active full backup or job recreation is supposed to solve sporadic issues that can be caused by variety of factors. Though, the situation when the issue keeps occurring suggest that problem isn’t just a temporary but a continuous one. So, I’m wondering why you didn’t re-open a ticket when the issues merged again. It would have helped us not only to address the issue faster, but also to understand the root cause of it.

Thank you for your understanding.

[kte]

it is time consuming, to have 7 to 8 cases opened for veeam, it opened to cases for the same issue for the same customer and i got 2 times the same answer. Another call is allready 2 months under investigation.
And that is only with veeam i have other hw issues and vmware issues @ that customer.
So i need fast fixes so that i can progress an that the backups keep working.

K

[Vitaliy S.]

Koen, if you're not satisfied with a proposed solution given by our support team, I do recommend either to escalate the case or contact our support manager to discuss the situation. To address any issue with a hotfix our support team needs as much information as possible, besides it is our support team (not people behind these forums) who are driving the hotfix creation. Hope this makes sense.

[antspants77]

HI,

Using V7.0.0.839 on WIndows 2012 R2, backing up Windows 2012 R2 Hyper-v.
Same issue as above
Error: Unexpected end of file has occurred. The following elements are not closed: OibSummary. Line 1, position 16385.

Had not changed incremental type.
However had added HyperVRestrictConcurrentSnapshotCreation key due to concurrent backups on same CSV failing, then completing successfully during retry.
Probably not related as appears to be a corruption in the index.(or whatever has the OibSummary)

Running an Active Full will mean twice as many full backup files going to tape.
Creating a new job will mean a long first backup and twice as much disk space.
...unless we delete the old backups and then we can't restore files from a month ago.

So the recreating or active full is not a "fix', it's a workaround and not suitable for many environments.
E.g. reformatting a PC, will "fix" most issues, but most users don't like this either.
We need someone to look at the files that are corrupted and have a fix which both rectifies the current issue and stops in happening again in the future.

[foggy]

Tony, have you already contacted support with that?