Macrium Reflect backup sessions very slow - since Window 10 upgrade?

Regressed and on restart Reflect started a differential on the Data drive, just as required. But it looks to be going as slow as previously, around 50 minutes. It hasn't finished yet.

Watching the Data and Backup drives on Task Manager's Performance tab shows the Data drive running at about 60-70% active time, average response time of ~2 ms. The backup drive is about 0-10% active. I would speculate that is Reflect accessing the changes on the Data drive which will, relatively speaking, be few and far between; and when found writing them to the Backup drive.

So it doesn't obviously appear to be the 2004 upgrade.

FWIW I've been Reflect'ing on my laptop. It's a secondary PC, largely cloned from the desktop, used for occasional work when I can't use the desktop so I'm less concerned about being able to recover the data more the system which I take a full backup every so often. Running a differential on the system drive (a partition of the single disc) is taking much the same time as pre-2004.

Odder and odder!

As an extra level of security, my son (lives 15 miles away) & I exchange swap drives every so often so we're maintaining off-site backups of our systems.


- - - Updated - - -

The Data differential completed in 56m 44s, creating a new 4GB file, Read 1.4Gb/s; write 399.1 Gb/s

As soon as that finished, a System differential kicked off. This completed in 20m 42s, creating a new 17GB file, Read 1.4Gb/s; write 481.6Gb/s

Something very strange seems to have happened in the past few days.

My laptop is now doing a full backup, all drives (1 drive, several partitions) which will take a bit over 4 hours, as expected.

If Reflect is taking nearly an hour to create a 4GB file, I would suspect a failing drive, either the source or the backup. I have never understood the quoted read/write rates, but they are clearly not averages.

In reverting to 1909 the desktop lost the Macrium icon associated with the shortcut. Couldn't get it to recreate it so decided to uninstall and reinstall.

Wouldn't uninstall as it said the Installer file didn't exist. It was however looking for the installer file for an earlier version compared to what was actually installed. Tried just installing, same problem. In the end I used Revo to get rid of it and then reinstalled ok.

However the previous log files are no longer there. So have no earlier evidence.

Just tried a run on the D: drive and it's still taking nearly 50 minutes for a 3-4GB file.

Run CrystalDiscInfo - Good
As the drive is a WD Black drive downloaded WD diagnostics and that runs ok. The SMART data is fine.

So no apparent errors happening on that drive, but a backup is taking around 20 times longer.

Backup of the C: drive - SSD - is fine. As are backups on my laptop.

I've run CrystalDiscMark on the drive. Results:
SEQ1M Q8T1: Read 174.50: Write 170.93
SEQ1M Q1T1: Read 174.93: Write 171.34
RND4K Q32T16: Read 0.88: Write 2.34
RND4K Q1T1: Read 0.74: Write 2.00
The drive is a WD WDC2003FZEX SATA drive, black.
I can't compare those figures with anything to know whether they're ok.

All very strange.

- - - Updated - - -

Sorry to be a pain, I'm wondering if there's any way, other than what I've already tried, to check the health of my D: drive, and also what it's performance should be?

Thanks.

Mine seem to be a little lower but not significantly so and may well be due to PC differences. My PC was originally built in March 2011, optical drive, memory, HDD and SSD have been added/changed since then, otherwise unchanged, so not particularly surprising to be a bit slower.

This morning's twice weekly incremental archives took 21m 23s for 20GB file from SSD system drive; 50m 35s for 5GB file from D: WD spinning drive.

Hard Disk Sentinel gives the drive 100% for health & 100% for performance. SMART data shows nothing amiss.

Attachment 282978

When did you last do a full backup of the data drive? You appear to have ~400GB used, so that's a fair bit of stuff for Reflect to plow through looking for changes. Whilst I don't expect it to resolve your issue, I would do a full backup, then (say next day) a differential to see if the time improves. Oh, and in your last post you refer to 'incremental archives', I assume you mean differential (as in previous posts)? Or are you mixing both inc & diff?