E
E
Eugene2020-09-18 13:21:00
Backup
Eugene, 2020-09-18 13:21:00

The machine on vmware after recovery from a backup does not start?

Good afternoon, colleagues!

The problem is this:
There were 3 machines on the virtual machine. Backups were made automatically by Veeam Backup & Replication Console.
After the physical machine crashed, I pulled out the backup, uploaded it to the Veeam Backup & Replication Console, raised the virtual machine on another machine and began the process of restoring copies.
Two cars stood up with a bang.
And the third - backup recovery ends successfully, the machine appears in the list. I'm doing a launch. She starts. The status dialog displays the win server 2012 welcome screen prompting you to press ctrl+flt+delete. And this is where the magical things begin.The machine is "kakby" running, everything is correct and good, even pings are coming. I click on the window to load the management console - and I see a simple black screen. I'm trying to launch through the Remote Console application and I get the error "The client generated an error while parsing the server's VNC data stream (error: Internal error). Shutdown in progress." - treatment is offered to turn on the service, but it is active, and other machines on the virtual machine run freely. Can there be any suggestions for a fix? Maybe someone came across...

Answer the question

In order to leave comments, you need to log in

3 answer(s)
C
CityCat4, 2020-09-18
@xslipfanx

Well, either the backup was not restored correctly, or it is damaged. This behavior (there are pings, but the machine does not work) has been encountered a couple of times with hung machines. Either the Windows kernel or some system components are damaged. Try an older copy.

A
Artem @Jump, 2020-09-18
Tag

Try booting in safe mode or recovery mode, check the system files from there, try to boot without unnecessary services.
In general, the standard set of actions is no different from restoring the health of a physical machine.

E
Eugene, 2020-09-18
@xslipfanx

5f64a84c5e025217029705.png
It doesn't let it go any further.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question