Skip to main content

"The running backup has not shown any progress for some time and may be frozen" error message

Beginner
Posts: 10
Comments: 13

This is just an annoyance but for backup jobs that I have schedule to write to a primary and a secondary storage node, the clients often report an alert that the job is taking too long. When these jobs were backing up quickly (~4min) to just the primary storage node, the alerts never happened. It seems adding the secondary storage node caused the job to run much longer and breached some (hidden?) threshold in Acronis so now it alerts.

If there is a threshold for these alerts, can it be adjusted?

Also, Acronis 12.5 manual doesn't really go into detail on precisely HOW backups to secondary location work in a backup plan. It doesn't say that the backup writes first to the primary location and on completion, replicates to a secondary location or if the backup client writes to both locations simultaneously. 

I'd also like to know from a practical standpoint, if my design is to have every client backup to a primary and secondary storage node (in another site over 10Gb WAN), is it better to create each plan pointing to both locations or should I create another plan to replicate primary storage node contents to the secondary storage node?

thanks

Pete

Forum Star
Posts: 22
Comments: 2531

Top

Hi Pete,

Can you please clarify how many machines are included into the backup plan? The issue may occur when you're backing up several VMs in a backup plan and when there are more than 2 (default - defined in Backup Options->Scheduling->"Limit the number of simultaneously running backups by") machines included. What happens after enabling the 2nd destination is that 2 VMs (from for example 10 total) are first backed up, then replicated to 2nd location, while the remaining VMs are put into waiting queue and this may trigger the alert to pop-up for these machines. Or it could be the case when the retention rules come in play and take a long time to complete the process which also triggers the alert. For proper analysis it makes sense to contact our support team for assistance with the issue.

The 2nd destination option comes in play after backup to 1st location is completed => the backups are copied to 2nd destination by using the archive in 1st location as the source.

For multiple backups replication it makes sense to have a separate "Backup replication" plan which will run on its own schedule, independent from the actual backup plans, and which will replicate all newer backups from the primary location over to secondardy one without touching the original backup sources. The "2nd location" option within the same backup plan (opposed to separate "Backup replication" plan) makes sense when you have only a few plans or multiple locations where the backups need to be replicated.

Thank you.

Beginner
Posts: 10
Comments: 13

Top

I tried this and ran into an issue where I cannot create a replication tasks between storage nodes. See my other post today.

thanks

Pete