After restore on vsphere System don't start
After restore (on vspehere) on new virtual machie and diffrent datastore system loops trying to automatic repair and restarting.
I have found that after restore drive letters are diffrent:
Original machine
Restored machine:
How to avoid this? Is the problem why windows don't start? How to repair it now?

- Log in to post comments

Hi Marek,
The drive letters should be preserved assuming that you've captured the backup in agent-less mode (via Agent for VMware) and recovery was also done in agent-less mode. If the backup was captured via agent-based backup, then there could be inconsistencies if you perform recovery in agent-less mode, and such issues should be investigated with help from our support team. Remember to clarify how the backup was captured (was it agent-based or agent-less backup) when submitting support request.
The workaround for the issue (to get the machine up and running) should be to perform recovery via Acronis Backup bootable media: create VM manually, boot it from Acronis Backup bootable media (.iso), and run Recovery wizard.
Thank you.
- Log in to post comments

Yes. Backup was made agent-backup - because i have SQL on the server so I wanted to be possible to secover separate databases.
And the restore was made by agentless.
Is there any procedure to assign correct disk letters in this case? I tried to change letters in diskpart but they comes back to bad values after restart.
- Log in to post comments

Hi Marek,
From the current state it's actually not clear whether the drive letters were actually changed and whether this is the cause of the boot problem. Note that these letters are applicable to particular Windows installation, e.g. they are recorded in Windows registry, so if you run Diskpart within WinRE or WinPE environment (which I assume you did on restored system, since it doesn't boot normally), the drive letters would be different than when you perform regular boot into Windows.
It is likely that the problem is related to some kind of BSOD (not the drive letters assignment) which causes the system reboot and the details of this BSOD can be checked by disabling reboot on crash on pre-boot stage: press F8/F12 when Windows boots up to get its boot menu.
To get the system properly restored I'd still recommended to run recovery via bootable media (as suggested in my previous comment). To troubleshoot the original problem it makes sense to contact our support team - remember to capture the actual BSOD message (if any).
Thank you.
- Log in to post comments

ps. Oter workaround is maybe to use "run as vm" and then finalize. With one server i have manage to restore this way but i don't know if for other servers also it works and also finalize is muuuuch slower than simple restore.
- Log in to post comments