Direkt zum Inhalt

Major Lesson Learned and why does 'Creating image backup...' take so long?

Thread needs solution

(Currently I'm using TI2014 latest.)

After installing a new 5TB drive in a so-called Windows 8.1 Pro "server" backup destination on the network we now have more room. I learned that doing a Quick Format caused a weird write failure when acronis did it's full backup of the "server". I though I had a faulty hard drive. I did a FULL format and the backups working good now. I'm not trusting Quick Formats anymore.

Anyway, I have to edit the the backup destination paths on each of the TI schedules for everyone's workstation. No big deal, you just click the little gear and edit settings. Suprisingly backups would randomly fail - I'd get strange TI error messages in which the knowledgebase explanation didn't really seem to relate to the cause.

What I think is going on is that when you edit a backup setting, the acronis scheduler is still trying to use and old path or setting even though I just changed it!

So I think that TI does not properly clear it's scheduler correctly when you edit a backup profile. This may be due to the "running a missed backup a bootup". This is just a suspicion. But it definitely backed up to the new path and proceed to backup to the old path during the same backup.

So the hard lesson I learned is that if I want to make a change to a backup profile, it is *more* reliable to add a fresh one rather then editing an existing one.

With that said, when you do add a new backup profile, you get a spinning wheel dialog saying "Creating image backup...". First of all, it is not running the backup. This dialog should say "Creating image backup profile...". And it can take up to a full minute. Can someone enlighten me why this takes so long? Again I suspect it is having to deal with the acronis scheduler which may be the holdup.

Thanks.

0 Users found this helpful

First it is commonly recommended here on the Forums that it is best to create new backup tasks when requirements change rather than to edit an existing task. That is sound advice however if one does edit a task I think that after one has edited the task one should shutdown the app, shutdown the computer and restart before attempting to run the edited backup task.

Second, your question concerning the delay at start of backup is I believe related to the fact that the app is running VSS to make a snapshot of the system which it then uses to create the backup thus allowing the user to continue using the computer while the backup task is running.

When you create a new task, the backup will run automatiacally at that time UNLESS you take special steps when saving the task.
Check this link.

https://forum.acronis.com/forum/71342