Not reconnecting after power outage.

[rob7676]

Hello all,

I backing up 10 VM's running 2003 & 2008 with Veeam 6 with the latest patch, each as VM as a single backup. Recently we had a power outage that lasted longer than our battery backups could support so we lost the servers briefly. Once we regained power and booted the VM's back up, the servers were running fine and didn't think anything of it until the next day when I had 4 servers that their backup failed due to not connecting to the VM. Upon further investigation, I noticed from within the backup job, the VM appeared to be offline yet it was in fact running. Not sure if this was the correct way to handle it, but I remove the VM from the job and added it back, then ran the job again; everything was fine again. Now my question is, why did it not re-establish the connection to some of the VM's and not all?

Thanks
Rob

[Gostev]

Hi, no immediate ideas, but debug logs may give a clue. Thanks.

[rob7676]

Hi, no immediate ideas, but debug logs may give a clue. Thanks.

Where would I find the logs?

[Gostev]

Detailed info on that is provided when you click New Topic.

[tsightler]

Does this happen to be standalone ESX server rather than vCenter?

[rob7676]

Does this happen to be standalone ESX server rather than vCenter?

Standalone.

[tsightler]

So most likely the hard reboot caused the moRef ID's to change on the VMs in question. Veeam doesn't track VMs by name, but rather uses the "Managed Object Reference ID". In the absence of a vCenter database the moRef ID is generated by the local ESX host, however these ID's are not guaranteed to be consistent across reboots. It seems to be especially common with ESXi that the ID's are different on a reboot.

[rob7676]

Would it be better to run it through vCenter? I originally had it configure that way but we were having some issues with vCenter which have been taken care of.

[tsightler]

IMO it's always better to use vCenter. vCenter provides much more consistent moRef ID's as they are stored in the SQL database and generally they will not change unless the VM is unregistered and re-registered (thus technically being a different VM).

[rob7676]

Thank you for your help, I will be sure to set it up this way again.