Root element is missing

[MHegelund]

Hi


After upgrading from Veeam B&R 4 to Veeam B&R 5 I keep getting the following error.

"Initializing target session
Read summary xml error
Root element is missing"

First thing I did was to create a complete new virtual backup server with a clean install of Veeam B&R. That helped for a couple of days, but then I started to get these errors again.

Any idea what might be causing this.

Veeam B&R is running on Server 2008 R2.

[Alexey D.]

Hello,

Could you tell please where do you get this error? Also, are you using v5.0.0 or 5.0.1?

[MHegelund]

It is version 5.01.198 64 bit.

The error is shown when I look at sessions and then look at details on the failed job.

This is the complete text in the VM summary field:
_____________________
0 of 0 files processed

Total VM size: 25,00 GB
Processed size: 0,00 KB
Processing rate: 0 KB/s
Backup mode: NBD without changed block tracking
Start time: 27-12-2010 10:46:44
End time: 27-12-2010 10:46:48
Duration: 0:00:04


Initializing target session
Read summary xml error
Root element is missing.
_________________

[Alexey D.]

I see... Please send all the logs to our support team - we need more information to help you. Thanks!

[MHegelund]

Have created a support ticket now.

[eriktxstate]

Any resolution here? I just saw this last night.

[Gostev]

OP did not post either support case number or resolution, so I cannot look up unfortunately.

[Daveyd]

I guess I will be calling support as well as I just had this same error message last night using 5.0.1.198 (64bit)

[Gostev]

Sounds good, please update with case number and/or resolution. Thanks in advance!

[Daveyd]

I am trying to stop the job that had previously generated those errors since, for whatever reason, it has been backing up 1 VM for the past 7 hours whereas it usually takes a matter of minutes. The job and process have been in the "stopping" state for about an hour now. How do I remedy this?

[Gostev]

Kill the job process (agent) with the Task Manager.

[eriktxstate]

I was told that I need to run a full backup for resolving the issue. I re-ran the job (mistakenly the incremental) last night and it failed again with the same issue.


What's really killing me is I can't say "run a full on this individual machine within this backup job" rather than having to create a whole different backup job. I have to re-run the entire job (128 vm's and 5.4Tb raw in this case) and wait 8 hours.

[spf62]

I just started getting these errors also. But it's only on my SQL servers.
Please respond with any fixes. thanks

[Vitaliy S.]

Based on the responses above, it looks like you should start your backup job from scratch, but I would still recommend to contact our support team with all technical issues you may have. Thanks!

[rreed]

Holy thread resurrection. Just started getting this on a couple VM's in a job that's been working fine for quite a while now. Do we know what the proper fix is?

[foggy]

No case ID in this thread, so cannot track it down. Please contact support directly.

[rreed]

Thanks foggy. Looks like removing the VM/re-adding it did the trick for us here.