Direkt zum Inhalt

Acronis Backup 12.5 - Already Stopped / Bereits gestoppt

Thread needs solution

Hi,

 

Machine: Windows Server 2012 R2 Essentials

Acronis Backup 12.5

Backup to: QNAP NAS

Already did chkdsk /r on C:\

 

 

Stops with the error: Already Stopped (Bereits gestoppt)

 

What should we do to solve the issue?

Anhang Größe
activity_log.txt 34.61 KB
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 0
Kommentare: 2016

Hello Lu1z.

In order to find out what file system errors stop the backup process, I recommend that you create Acronis System Report and upload it to the FTP link that I sent you in a Private Message.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 0
Kommentare: 2016

Hello Lu1z,

unfortunately, we did not find any concrete error messages. However, the log shows that failure occurs when backing up disk D (snapshot creation of disk C completes successfully); according to such error messages like "Insufficient system resources to run the requested service" and "Verfügbarer virtueller Speicher 12,4 GB", we can suppose that operation fails when the software tries to lock D drive in order to write its snapshot to NAS.

Thus, I request that you additionally collect Process Monitor logs after reproducing this issue and Acronis VSS Doctor logs and upload them to the same FTP link.

Please also clarify if local backups and backups to another NAS are Ok.

As a temporary workaround, you could set Version 11 backup format (you will need to create a new backup plan with this parameter) to continue backing up your system .

I deactivated the Harddrive Standby Function in the QNAP and changed the BackupFormat in Acronis to V11,... seems to work so far....

 

tbh i dont think its the NAS that is causing the problem since as you say the problem only starts as soon as drive D: is being saved (C and D are on the same Raid array), which would mean the system was already woken up