Skip to main content

The running backup has not shown any progress for some time and may be frozen - routinely

Thread needs solution

I have a client we are backing up with the following Acronis version information - 

Web console service: v.12.0.3779

Backup management server: v.12.4.5916

Backup management console: v.12.0.7968

The whole backup in this case took 25 hours.  The cloud replication part is what took the most amount of time to complete, but now it is at -

 

03:09 AM • 0% completed • Calculating time left

Applying retention rules (SO-HV1.so.local)

Status:

In progress

Device:

XX-HV1.xx.local

Started by:

On schedule

Start time:

Mar 20, 2019, 03:09:19 AM

Duration:

 

0 sec

That started 5 hours ago,  and now leaves me the message it may be hung.  Is there anyway to avoid this pit fall after a long backup.  I now fear I have to kill the job, start again, and hope it is able to apply the retention next time.

 

Or am I missing something.  If it fails this, will it ruin the whole backup, or does it just mean the retention rules will not be properly applied?  For example, if I let it run its next, set for incremental, will that set it back up without running the full starter in the set?

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Dave,

welcome to Acronis forums!

I would strongly recommend that you update your client's components of Acronis Backup 12.5 to the latest build with a lot of bug fixes and performance improvements.

If it fails this, will it ruin the whole backup, or does it just mean the retention rules will not be properly applied?  

If a backup fails, the retention rules cannot be applied: the last backup created by the backup plan always will be kept. The whole backup chain (archive) will remain as it was before the last (failed) backup start.