Skip to main content

Repklikation - Gastbetriebssystem startet nicht

Thread needs solution

Hallo,

folgendes Szenario:
ML350p Gen8 mit ESxi 5.5. (6 CPU, 32 GB HSP) -> Replikation auf HP Z230 (4 CPU, 8GB HSP)
Acronis Backup für VMWare (9.0.1000.7)

Problem:
Auf den HPZ230 wird eine Replikation des Server 2012 (Gastbetriebssystem auf ML350p) über Acronis ohne Fehler durchgeführt. Beim Start dieser Replikation auf dem HP Z230 kommt die Meldung:
"Windows failed to start. A recent Hardware or Software Change might be the cause." File: \Windows\system32\winload.exe Status: 0xc0000001

Das System wird auch mehrmals täglich auf ein NAS gesichert. Die Wiederherstellung dieser NAS-Sicherung auf den ML350p funktioniert.

Kennt jemand dieses Problem mit der Replikation?

Schönen Gruß
Markus Arnold

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Kurt,

The issue appears to be related to the specifics of the replicated source VM and/or differences in configuration on the replica VM. The VM is replicated by Acronis Backup for VMware "as is" preserving all the original settings and without patching the bootability (which is done when you perform full VM restore). Can you please clarify whether you tried to perform recovery of the same VM to HP Z230 host? Does the restored machine boot in this case? If the restored VM boots properly then it makes sense to compare the .vmx of the restored VM with the .vmx of the replica of the same VM (which doesn't boot) in order to figure out what might be wrong.

Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager

Hello Vasily,

thank you for your advice. Restore the VM from the NAS to the Z230 host works and the guest System starts well. So the problem is the replication. I'd tried it with different adjustments (specilly in the advanced in Point 3 of the replication process), but it doesn't work (the same problem). What I've found is in the datastore of the replicated machine is, that the size of the vm-disk is less than the original (see attached file).
For me the first thing is good, that if there is a Hardware problem, the restore to the Z230 works. But perfect where, that the replication works, so the System works as we had it planned.

Best regards
Markus
(IT technical from Kurt)

Attachment Size
277884-120358.pdf 500.32 KB
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Kurt,

On the screen shots there are different sizes shown - for original VM it's showing the provisioned size of the disk (500GB), while for the replica VM there is actual size shown (80GB) + provisioned size is shown as well correctly. Therefore the problem is likely unrelated to the disk sizes - they look normal. I'd recommended to contact our support team for assistance with this case as it will require additional investigation. Remember to attach the log from View->Show Logs->Save All To File. This log should be captured after running replication task for the 1st time (remove the currently existing replica VM before reproducing the problem).

Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager