Recovery über die Management Console schlägt fehl
Hallo.
Ich habe ein Problem mit dem Recovery, welches ich aus der Management Console ausführen möchte.
Wenn ich das Recovery anstarte, läuft erstmal alles wie es soll. Der PC startet neu und dann versucht er beim booten das Recovery Menü zu starten und bricht dann mit der Fehlermeldung ab (siehe Screenshot):
Failed to open ramdisk Program Files\Common Files\Acronis\BackupAndRecoveryAgent\agent_ramdisk64.dat
Ramdisk bootstrap tool failed with 1
Error 1
In der Management Console bekomme ich die Meldungen, die im Screenshot zu sehen ist. Auf dem PC ist nur der Agent installiert.
Benutzt wird die Build Version 16180.
Ich hoffe, dass jemand eine Lösung für mein Problem hat.
-------------------------------------------------------------------------------------
Hello.
I have a problem with the recovery that I want to execute from the Management Console.
When I start the recovery, everything goes as it should. The PC restarts and then tries to start the recovery menu while booting and then aborts with the error message (see screenshot):
Failed to open ramdisk Program Files \ Common Files \ Acronis \ BackupAndRecoveryAgent \ agent_ramdisk64.dat
Ramdisk bootstrap tool failed with 1
Error 1
In the Management Console I get the messages that can be seen in the screenshot. Only the agent is installed on the PC.
Build version 16180 is used.
I hope someone has a solution to my problem.
Allegato | Dimensione |
---|---|
Photo-0.jpg | 27.63 KB |
Photo-1.jpg | 1 MB |


- Accedi per poter commentare

Hallo Peter,
die Management Console hat auch die Build Version 16180.
Da ich keine Boot CD benutze, kann diese auch nicht beschädigt sein.
Muss ich denn eine Boot CD benutzen, wenn ich das Recovery über die MC starte? Das wäre ja sehr doof.
Der PC besitzt 8 GB RAM. Das reicht auf jeden Fall aus.
------------------------------------------------------------------------------------------------
Hi Peter,
the Management Console also has build version 16180.
Since I don't use a boot CD, it can't be damaged.
Do I have to use a boot CD when I start recovery from the MC? That would be very stupid.
The PC has 8 GB of RAM. That is definitely enough.
- Accedi per poter commentare

Hello PW!
Since I don't use a boot CD, it can't be damaged.
Do I have to use a boot CD when I start recovery from the MC? That would be very stupid.
That's why I suggested a reinstallation of the agent where you are trying to restore. Looking at the files and the KB it suggests similar software components (contents of ProgramFiles\CommonFiles\Acronis\BackupAndRecoveryAgent) are loaded when you start recovery from the MC with a restart and when you would use a bootable media. If this component is corrupted somehow a reinstall would most likely fix it.
If it doesn't work, you could try using a bootable media to see if it works at all. I'm thinking of the unlikely scenario where the HDD has bad sectors at the exact spot agent_ramdisk64.dat is supposed to be and therefore can't load it.
-- Peter
- Accedi per poter commentare

Hi Peter.
Thank you for your answer.
I've tried everything. Agent repaired and reinstalled. No success.
But I think I know what the problem is. The recovery should be done on a Siemens Panel PC 677D with RAID 1.
I had huge problems with the Linux-based boot CD that the hard disks or the RAID volume was not recognized.
For whatever reason?! I can only restore backups to the Siemens 677D Panel PC with the Windows PE Boot CD.
And I assume that Linux will be used there for a recovery via the MC.
None of this is satisfactory.
- Accedi per poter commentare

Hello PW,
thank you for posting on Acronis forums!
I strongly recommend that you use Acronis Universal Restore and prepare the necessary drivers for the target system to boot as described in this KB article: https://kb.acronis.com/content/35681
If the Linux-based Acronis Bootable Media does not detect the source/target RAID volume, please create and use for restoration the Win-PE-based Bootable Media with the necessary drivers
- Accedi per poter commentare