Windows Server 2003 R2 ACPITABL.DAT Issue on HYPER-V VM restoration

Can you try restoring using Acronis Backup & Recovery 10 virtual edition?

If this fails too then the image is corrupted. You need to take another image of your production and test the restoration again.

One more thing, when you did a test restoration, did you do that on a test server connected to a RAID array? If yes, then is it the same array of your production when you took the image backup? Test also restoration after breaking up the array and then rebuilding it after the restoration.

Thanks Mutawadi for your comments,

Unfortunately I don't have access to the older version.
No RAID array on  the test server - very simple machine.

I have searched the net for the ACPITABL.DAT error - and solutions regarding this came from removing 1 disk from a RAID array to restoring update.sys to a whole range of other solutions.

I believe my problem is connected to the HAL. But the Acronis solution both in the backing up and the restoring end includes UNIVERSAL RESTORE.

If someone can come up with a sure way of progressing beyond ACPITABL.DAT that would be great.

Since it is only a test restoration, and I believe you're testing restoring on a different hardware specification, then why don't you back up the production again with the new Acronis version 11 one and then carry out the restoration.

Client doesn't want to upgrade to the new version.

I can't understand, if the client doesn't want to upgrade to the new version then how are you using the new version to restore the server?

I am using NFR licenses if you really want to know.

Does anyhow have any experience in getting a VM in Hyper V that is suffering from an acpitabl.dat stall to come alive again? Especially when the OS is W2K3-R2?

Acronis' support is not adequate. I have had sub standard technicians just waste my time in the past.

Being a not so skilled Virtualization techie, I could say that VMware is superior to Hyper V.