Backup Freezes

[Filip]

Okay, let me first give you some background information.

A new customer was running an SBS2008 server on a physical box which we have now replaced with a new server. The new server is running VMware ESXi 6 Update1 and has 3 Virtual machines. One Exchange 2013, a DC and an SQL all running on server 2012 R2.
Everything has been migrated from the SBS2008 to our new servers.

The SBS server has been demoted, all roles removed, ...

So I installed Veeam V9 for the first time on the old SBS2008 server. This went without any hassle.
I added the backup repository, added the vmware host and created a backup job. All settings default.

The backup job starts running but then after a while (random) it just sits there doing nothing. There is no data transfer. The only thing I can do now is kill Veeam backup service and reboot the backup server.
I also have to reboot the VM on which the backup job freezes. i can then do a retry of the backup job and if i'm lucky it will be successfull. Otherwise, I will have to do the same thing over again.

I already submitted a support case for assistance: 01692426
I just wanted to know if anybody else is experiencing this behavior?

Grtz
Filip

[Filip]

And again freezed. This time it's actually finished but the job keeps running.

[haslund]

What kind of patch/service pack level is the SBS server at?

[Vitaliy S.]

The backup job starts running but then after a while (random) it just sits there doing nothing. There is no data transfer. The only thing I can do now is kill Veeam backup service and reboot the backup server.

I would recommend to check out Windows Event log at the time when you see this behavior and wait till our engineer looks through your debug logs.

I also have to reboot the VM on which the backup job freezes.

Why do you do that? Does your backup job fail on this VM on a subsequent run? Do you have AAIP enabled for this job?

[Filip]

What kind of patch/service pack level is the SBS server at?

Server is running Server 2008 SP2 (SBS2008)
There are a couple updates that still need to be installed.

[Filip]

If I don't, the server will sit there for days doing nothing. The job keeps running, I won't get a notification and backups will never complete. And I do want a backup. We are having this problem now for more than a week. I don't have to explain the risks of not having a proper backup.

The latest feedback I got from Veeam is that they escaleted the problem to a Senior. This was yesterday.

I didn't get any feedback today.

Could this be a VMware issue? CBT issue?
The only thing I can see on in the vsphere client are the messages below.

Code: Select all

On the VM:
User logged event: Source: Veeam Backup Action
: Job "Backup Test for Veeam support" Operation
: Started Status: Success ID: 
f933ec64-9621-443a-9764-08cbe5d933a0 
Description: 
user
18/02/2016 19:35:33
HENSDC01
root

On the Host:
User root@192.168.0.253 logged in as Mozilla/4.0 
(compatible; MSIE 6.0; MS Web Services Client 
Protocol 4.0.30319.34209)
info
18/02/2016 19:32:34
root

User root@192.168.0.253 logged out (login time: 
18/02/2016 19:32:34, number of API invocations: 
0, user agent: Mozilla/4.0 (compatible; MSIE 6.0; 
MS Web Services Client Protocol 4.0.30319.34209
))
info
18/02/2016 19:32:59
root

User root@192.168.0.253 logged in as Mozilla/4.0 
(compatible; MSIE 6.0; MS Web Services Client 
Protocol 4.0.30319.34209)
info
18/02/2016 19:34:26
root

[Vitaliy S.]

In order to narrow down the potential root cause (either VMware or current Veeam backup installation), I would recommend to deploy a fresh VBR server in the VM and run a test job to see if this issue confirms or not. This information would also be useful to know for your support engineer.