ID#5207137 SureBackup Job Exchange 2007 Stuck

[skydok]

Hello,
I have opened already a case but maybe someone can help.

Sure Backup Job is configured with 4 VMs for Exchange Single Item Restore.
Its Exchange 2007 env.
First 3 VMs are restored ok but Last one is stuck on \"Powering ON\".
i tried to change the order of the Machines and still the Last one stays on \"Powering ON\" it doesn\'t matter which VM is Last.

It worked with Exchange 2010 OK but 2007 didn't.

Thank you very much .

[Vitaliy S.]

Could you please tell us what is actually happening to the 4th VM while SB job is trying to power it on? Have you been able to check VM console via vSphere Client?

[skydok]

The VM is UP , there are Pings between all 4 Machines, but in the Job Log it stays as:
[StableIp] Waiting for IP-address during 3600 second(s)
IP-address has been detected in 00:00:00
IP-address has been changed from 169.254.1.127 to 192.168.51.150

But it repeats itself for 10 Hours and more, altough inside the Console everything is fine.


i tried everything but still the same problem.

[Vitaliy S.]

Hmm...Ok, then I guess it's better to continue working with our support team, as deeper log investigation is still required.

[skydok]

Thanks man, i will wait that they contact me.

[zoltank]

I know it's an old thread, but hopefully this might help someone in the future.

I've seen this using SureBackup on my Exchange 2010 backups. It came down to not enough resources on the Veeam server, though I could never figure out if it was CPU, memory, or disk. My solution was to reduce the associated Application Group to the bare minimum of required VMs, and link to the backup job to test the rest.

In my specific case I had a total of 5 VMs in my Application Group: 2 DCs, Exch2010 transport/hub server, 2 Exch2010 mailbox servers. When I started encountering the issue I ended up reducing my Application Group to just 2 VMs: a DC and the transport/hub server. I tested the other DC and the mailbox servers one at a time through the linked backup job. This was there are only ever 3 VMs powered on at a time. This solved my problem, and slightly decreased my SureBackup time as well.