Skip to main content

Extreme slowness when creating backup

Thread needs solution
Beginner
Posts: 1
Comments: 2

​I've been using Acronis for years with no problems, I'm currently on 2019, Build 17750.

I'm backing up an internal PCIe SSD (224GB in size, about 80% full) + an internal HDD (1.8TB in size, about 80% full) to a internal separate HDD backup drive (5.45TB in size, also about 80% full).

There's nothing unusual about this for me, I've been doing it for years and Acronis usually manages to create a full backup of about 450GB in size 2-3 hours including validation.

A few weeks ago I noticed the backup was taking much long to complete - up to 24 hours - here's a screenshot of a backup that had been running for over an hour:

I first uninstalled and reinstalled the software, scrubbing the registry in-between - this made no difference.

I ran VSS doctor (log attached) and it shows an error with Disk I/O load, but I don't know what this means:

I'd be very grateful for any advice.

0 Users found this helpful
Legend
Posts: 102
Comments: 22824

#1

Terence, welcome to these public User Forums.

I'm backing up an internal PCIe SSD (224GB in size, about 80% full) + an internal HDD (1.8TB in size, about 80% full) to a internal separate HDD backup drive (5.45TB in size, also about 80% full).

If you are running an SSD (or other drives) at less than 20% free space then this is going to cause this type of performance issue simply because of the lack of free space to use for both caching of data and also to store snapshot data by VSS.

Most SSD makers recommend allocating around 20% of the drive capacity for over-provisioning to help meet performance needs.

Beginner
Posts: 1
Comments: 2

#2

Thanks for your insight.

I cleared unwanted data off my pc so now all three drives have more than 50% free space:

But Acronis is still taking way too long to create backups.  I've had a backup running for 50 minutes and it says there is nearly 15 hours remaining:

I've also run chkdsk on all three drives and found no errors.

I note that VSS Doctor shows this error, might this be the culprit?  Any ideas what this means?

Grateful for any other input.

Legend
Posts: 102
Comments: 22824

#3

Terence, the first suggestion, if not already done would be to perform a Windows Restart to see if that clears the error issue.  I have not seen any other reports of VSS Doctor giving the error in your image.  I assume that you are using the matching version of VSS Doctor for the installed .NET version?

For the estimated backup time remaining, that is notoriously inaccurate and I would expect it to change to a much shorter time as the task proceeds.

Beginner
Posts: 1
Comments: 2

#4

Thanks for responding Steve.

I've restarted numerous times, including immediately before the current backup.

I'm using what I assume is the correct version of VSS Doctor, the one for .NET Framework 4.5 (I have an up-to-date Windows 10 installation with .NET Framework 4.8).

I take your point about the time remaining number being inaccurate, but I was first alerted to this problem when I found the backup was still running over 12 hours after it was started, so I think it's genuinely slow, not just a perception.

I may have to chalk this up to experience; it doesn't impact PC performance, so as long as the backup happens it's not a real problem if it takes a long time, more of an irritation.  Maybe it will be fixed by wiping the disk and doing a fresh system install - but it's not bothering me enough to bother with that!

Thanks for your advice.

Terence