Skip to main content

Recovery in VMware Workstation

Thread needs solution

Hi all,

I've tried to recover my image into a vitual machine and got following errors.

Can someone help

Tanks

Patrick

--------------------
Details zu den Log-Einträgen
--------------------
Typ:            Fehler
Datum und Zeit: 04.12.2017 08:14:04
Backup-Plan:    [Keine]
Task:           MyRecover_1
Code:           20'250'685(0x135003D)
Modul:          309
Nachricht:     
  Befehl 'Recovery von Laufwerken/Volumes zu neuer VM 'vm:9C3B40F4-36A4-40F8-9E43-0C7E63E3E8CF?type%3dvmww'.' ist fehlgeschlagen.
Zusätzliche Info:

--------------------

Fehlercode: 61

Module: 309

Zeileninfo: 4a8728dc8a1c9510
Felder:  $module : service_process_vs_50073
Nachricht: Befehl 'Recovery von Laufwerken/Volumes zu neuer VM 'vm:9C3B40F4-36A4-40F8-9E43-0C7E63E3E8CF?type%3dvmww'.' ist fehlgeschlagen.

--------------------

Fehlercode: 22

Module: 309

Zeileninfo: 8d165e86fb819666
Felder:  TraceLevel : 1, $module : disk_bundle_vs_50073
Nachricht: TOL: Failed to execute the command. Recovery von Laufwerken/Volumes zu neuer VM 'vm:9C3B40F4-36A4-40F8-9E43-0C7E63E3E8CF?type%3dvmww'.

--------------------

Fehlercode: 32788

Module: 114

Zeileninfo: 28314c961de7d41b
Felder:  $module : disk_bundle_vs_50073
Nachricht: Wiederherstellen der virtuellen Maschine  'SAG' mit ID 'vm:9C3B40F4-36A4-40F8-9E43-0C7E63E3E8CF?type%3dvmww' fehlgeschlagen.

--------------------

Fehlercode: 61

Module: 149

Zeileninfo: 74b50fdfc668f658
Felder:  $module : disk_bundle_vs_50073
Nachricht: Kann das aktuelle Task-Skript nicht verwenden. Die Laufwerkskonfiguration hat sich seit Erstellung des Tasks verändert. Erstellen Sie einen neuen Task.

--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode

Ereignis-Code: 0x0135003D+0x01350016+0x00728014+0x0095003D

--------------------

 

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

Hi Patrick,

The error message indicates inability to create VMware Workstation virtual disks in accordance with the disks present inside the backup. If you're performing recovery into VMware Workstation VM type then you should ensure that the disks/volumes of the machine you recover are properly mapped to virtual disks in the recovery task configuration. To get betted understanding of what might be wrong, please attach screen shots of how you configure recovery task - backup image selection (to see what disks are inside the backup) + virtual disks configuration for the target VM matters the most.

Thank you.

Hi Vasily,

thank you for your help.

By selecting the image again, I got a new error... Archive has been validated successfully. I'm completely confused..

Code: 11'141'156(0x00AA0024)
Zeileninfo: 0x173657EB80C2F597;

Modul: trueimg_remote_full_vs_50073
Nachricht: Unerwartetes Server-Verhalten.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

The error you quoted may appear if the agent selected for performing recovery is unreachable from the management server by its registration name. To workaround the problem try connecting to the agent directly from the management console, e.g. instead of connecting to management server, connect to agent (you can do this from "All machines with Agents" -> right-click on some agent-> "Connect directly") and configure recovery from there.

Thank you.

Sorry I'm really a basic user of Acronis... I don's have any Management Server installed (see below). I don't see what you mean with "connecting to agent"

 

image

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Patrick,

At this point I'd recommended to contact our support team for assistance. It's unclear when the error appears and which steps you performed to get it so far. Probably you're already connecting to locally installed agent or you have virtual appliance deployed somewhere and you're connecting to it - I can only guess what happens unfortunately.

Thank you.