We were in the process of migrating VMs from one datacentre to another using Veeam Backup & Replication when our main host crashed with a CPU error. The production VMs had been running on the server for a few hours and hadn’t yet been fully replicated to the replication partner. One of the VMs is Server 2003 so was running in Instant Recovery mode as is couldn’t be migrated using replication like the other VMs.
Thankfully the server rebooted and all the VMs started without issue except the Server 2003 VM. When viewing the console it only displayed a black screen which was worrying as there was no backup of the last 6 hours of changes.
After submitting a case on the Veeam site a member of the support team called within 20 minutes and quickly got the VM up and running again. The issue in our case was that the Veeam B&R software is installed on a VM running on the host that crashed. When the VM restarted the Veeam services didn’t start in the required order. The Veeam vPower NFS service needs to start after the Veeam Backup service.
To fix the issue the only steps required were to restart the Veeam vPower NFS service on the system running Veeam B&R then start the VM.
I know this is old but thanks for posting it! I had a similar issue but my Veeam installation was not on a virtual server. I did reboot the host that was running the published instant recovery VM and that’s when I started having problems. It wouldn’t boot in VMWare, I just got a black screen with a cursor. As soon as I restarted the Veeam vPower NFS service the VM fired right up.