Skip to main content

Acronis True Image 2018 - Backup hängt sich auf

Thread needs solution

Hallo zusammen,

ich habe ein Problem mit Acronis True Image 2018. Ich habe vor kurzem meine Festplatte von meinem Laptop getauscht von HDD auf SSD. Die Festplatte habe ich geklont, so konnte ich nach Einbau ganz normal weiter machen. Ich hatte im Anschluss die Festplatte etwas aufgeräumt und wollte dann ein Backup machen. Leider seither ohne Erfolg. Das Backup hängt sich immer wieder bei 385 MB auf. Ich hab Acronis neuinstalliert. Ich habe die Festplatte auf die das Backup soll formatiert. Ich finde keine Lösung im Internet die mir hilft.

Über eine Unterstützung würde ich mich sehr freuen. Wenn es geht mit idiotensicherer Anleitung, ich habe nicht das größte Computerverständnis. Vielen Dank vorab!

 

Mit freundlichen Grüßen

Axel Baier

0 Users found this helpful

 I have a problem with Acronis True Image 2018. I recently swapped my hard drive from my laptop from HDD to SSD. I have cloned the hard drive, so I could continue to do normal after installation. Afterwards, I cleaned up the hard disk and wanted to make a backup. Unfortunately, since then without success. The backup is always stuck at 385 MB. I have reinstalled Acronis. I have the hard drive on which the backup is supposed to be formatted. I can not find a solution on the internet that helps me. 
 
About a support, I would be very happy. When it comes to idiot-proof instructions, I do not have the greatest computer literacy. Thank you in advance!

Axel,  welcome to these public User Forums.

Is your computer booting into Windows successfully from the new cloned SSD drive?

Please download the MVP Log Viewer tool (link below) and use this to check the log file for your backup task that gets stuck in the backup process.

Axel, willkommen in diesen öffentlichen Benutzerforen.

Startet Ihr Computer erfolgreich von dem neuen geklonten SSD-Laufwerk in Windows?

Laden Sie das MVP Log Viewer-Tool herunter (Link unten) und überprüfen Sie damit die Protokolldatei auf Ihre Sicherungsaufgabe, die während des Sicherungsvorgangs hängen bleibt.

 

Hallo Steve, vielen Dank für die erste Hilfe.

Laden Sie das MVP Log Viewer-Tool herunter (Link unten) und überprüfen Sie damit die Protokolldatei auf Ihre Sicherungsaufgabe, die während des Sicherungsvorgangs hängen bleibt.

Anbei zwei Screenshots vom letzten Eintrag. Ich weiß nicht, ob das so richtig ist und du hieraus schlau wirst. Ich sehe zwar das ein Fehler entstanden ist, kann aber nicht erklären warum und wie ich ihn beseitigen kann.

Startet Ihr Computer erfolgreich von dem neuen geklonten SSD-Laufwerk in Windows?

Mein Computer startet ganz normal seit dem Klonen. Also bisher ist mit der SSD alles in Ordnung. Soweit ich das beurteilen kann...

Schon mal vielen Dank für die weitere Hilfe und viele Grüße,

Axel

Attachment Size
497997-167319.JPG 466.23 KB
497997-167322.JPG 455.15 KB

Axel, please download the Acronis VSS Doctor tool (link in my signature) as the screen images show that there are VSS issues involved here which is preventing the backup from succeeding.

Axel, bitte laden Sie das Acronis VSS Doctor-Tool herunter (Link in meiner Signatur), da die Bildschirmbilder zeigen, dass es sich um VSS-Probleme handelt, die ein erfolgreiches Backup verhindern.

After running VSS doctor, hopefully, things will be on track again.

If not, often times, VSS issues are related to an issue with native Windows System Protection. As another possibility to try (if VSS doctor does not fix things for you already), you can try the following next.  Just be aware that you will lose existing Windows recovery points in doing this, but can immediately create a new one afterwards and start making new ones as usual again.

The potential fix is often possible by turning off Windows System Protection for the source drive (usually C:), closing the window, and then going back into Windows System Protection and enabling it on C: drive again.  If you see two instances of “C:” drive in Windows System Protection (which is not that uncommon - even on systems not using Acronis), then this is a sure sign of an issue.  You would want to do this for both instances - then, the “false” one should disappear and the correct one should hopefully run with Windows System Protection correctly again.

Axel, bitte laden Sie das Acronis VSS Doctor-Tool herunter (Link in meiner Signatur), da die Bildschirmbilder zeigen, dass es sich um VSS-Probleme handelt, die ein erfolgreiches Backup verhindern.

Nochmal vielen Dank Steve. Das Programm ist durchgelaufen und hat Fehler gefunden, die ich nicht verstehe. Anbei die Datei. Was muss ich tun, um das Problem zu beheben?

Vielen lieben Dank schon mal!

Attachment Size
498176-167369.txt 6.54 KB

The potential fix is often possible by turning off Windows System Protection for the source drive (usually C:), closing the window, and then going back into Windows System Protection and enabling it on C: drive again.  If you see two instances of “C:” drive in Windows System Protection (which is not that uncommon - even on systems not using Acronis), then this is a sure sign of an issue.  You would want to do this for both instances - then, the “false” one should disappear and the correct one should hopefully run with Windows System Protection correctly again.

Hallo Bobbo, vielen Dank für den Tip. Tatsächlich waren zwei C: zu sehen. Nach dem ich den einen deaktiviert hatte, verschwand er. Dieser hatte ein Symbol wie ein einfacher Windows Ordner. Das andere C: hatte das normale Festplattensymbol und war deaktiviert. Sollte D: auch aktiviert sein?

Mit dem VSS Tool ist nun ein neuer Fehler aufgetaucht...Ich verstehe das leider nicht.

Attachment Size
498177-167370.txt 6.5 KB

Axel, I don't see any significant issues in the VSS Doctor report files but would suggest doing a Windows restart to clear up any issues from the previous status of System Protection when you had the 2 copies of drive C: showing.  There should be no need to enable System Protection for your D: drive.

Axel, I don't see any significant issues in the VSS Doctor report files but would suggest doing a Windows restart to clear up any issues from the previous status of System Protection when you had the 2 copies of drive C: showing.  There should be no need to enable System Protection for your D: drive.

I restart Windows but i have also the Problem that the Backup stop at 385 MB. Any other ideas?

Axel, one option here is to switch from using VSS for your backup task to using the older Acronis Snapshot method (that was used in ATI 2014 and earlier) and see if this also gives you any issues.

You can make this change by following the advice in KB 59440: Acronis True Image 2017: 'Snapshot for backup' option overview - this is valid for later versions of ATI.

If using Acronis Snapshot works then you have a Microsoft VSS issue.

See KB 46195: Acronis Backup Software: Troubleshooting Snapshot Issues

Hey Steve, "good news" it works. But what can i do to fix mx Mircrosoft VSS issue? Any ideas? Is it okay to made an backup with snapshot?

Axel, good to know that the Acronis snapshot method allows the backup to succeed, though not so good that there is still a VSS related issue here.

One potential factor here is the Snapman.sys driver installed by Acronis True Image and used to interface with VSS, but the only way to check this would be to completely uninstall ATI 2018, including using the Acronis Cleanup Tool (link in my signature), then do a clean install of ATI after doing a Windows restart.

If you have an alternative backup program that also uses VSS, you could check to see if that also gives a similar error, or whether this issue only happens with ATI - if so, the above action would be recommended, but if other programs, including Windows Backup (Windows 7) gives VSS issues, then this will be a Microsoft issue.

Repairing VSS can be difficult to locate the full issue.

Before anything - make sure you have a good backup - an offline backup with rescue media (if the disk is not encrypted with Bitlocker or something similar), is probably the best/safest to start with.

Once you have a good, safe, backup, then you can start troubleshooting.

I would start with running an admin command prompt (right click "cmd" and select "run as administrator" even if logged on with an admin account).  Then run

sfc /scannow

check the results for identified issues and/or repairs

after that then check the OS health with DISM commands.  This article explains it all very well

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

DISM /Online /Cleanup-Image /CheckHealth

if it finds issues, then continue with

DISM /Online /Cleanup-Image /ScanHealth

If the OS repair commands don't resolve issues (make sure you reboot after all of this first), then you may need to try and target VSS specifically.  Unfortunately, the behavior could be from a number of different areas and it's hard to pinpoint them without researching your Windows logs first for more information.

Although, not ideal, you may want to try downloading the full Acronis installer file from your account, right click and run as administrator (even if logged in with an admin account) and try a repair.  Then reboot and see if the behavior is still there or not.  If not, great.  If it is still there, try creating a new test backup job and see if it also occurs in the new job - maybe it's something just in the older or existing backup.

If the error still persist, then I would fully remove Acronis True Image from the system. Then run the cleanup tool by righ-click and "run as administrator" (even if logged in with an admin account already) and complete the cleanup.  Then reboot. After reboot, reinstall Acronis by launching the current installer file with right click and "run as administrator" even if logged on as admin already.  If a completely "fresh" install still has this issue, and none of the Windows repairs helped, then there are likely deeper issues.