Recovering backup to Virtual Machine error
I am trying to recover a backup to virtual microsoft virtual machine and just before completion errors with:
cannot open registry key 'Microsoft\Windows NT\CurrentVersion' and the vm is deleted from the path and the restore fails...I have BUR 10 latest build, with universal restore, restoring to a Windows 2008 R2 Server to a folder i.e. c:\foldername (not clustered shared volume)...Plenty of space on server...it appears to be a permission issue on the registry when creating the Microsoft vm?
Any help appreciated.

- Log in to post comments

Just come across the same issue with 11.5
Further digging seems that the registry is corrupt ?!? from the source machine being backed up. Currently I have tried booting a blank VM with the Acronis restore ISO, this fails with the same message.
I am now trying to mount the VHD in compmgnt and restore the partition as the physical disk and boot, this fails for me as the original OS expects SCSI disks, not IDE... can't get past the 7B blue screen, even tho I've got a scrypt that fixes all the other 7B issues I've had.
My plan now is to restore as above to a VHD attached as a physical, run a chkdsk (to correct any issues) then attach the VHD to a virtual, perform a backup of the virtual (using the hyper-v or boot ISO disk) then do a recover and see if it can then inject/tweak the registry to boot from IDE.
It would be lovely if Acronis could let us see what it does to the registry, so I can complete my custom boot CD for P2Ving units !
(as this is my full time job, testing backups by P2Ving them)
- Log in to post comments

you can use 'Apply Universal Restore' function of the Acronis bootable disk to apply necessary drivers (they are located in "C:\Program Files [(x86)]\Common Files\Acronis\UniversalRestore\DriversPack\" once you have the registry fixed.
- Log in to post comments

Perfect ! I can add this to my scrypt / script boot CD that i have, not that many ppl P2V server 2000 and server 2003 much any more.....
Tho i think i have found a bug, which i have logged and am working through.
- Log in to post comments