Paul wrote:
Ed Cryer wrote:
Paul wrote:
Ed Cryer wrote:
I like safety in my backups. So I regularly do both a System image
with Win10's Win7-style app, and then a Macrium Reflect one.
I did two today; Win10 took almost 2 hours, Macrium took 19mins.
1TB spinning HD, C partition occupies it all, apart from a few small
ones for reset etc. Which means that Macrium had even more to write.
Why is this? Why does Windows take so long? It's not doing anything
more than Macrium, and, in addition, it comes from MS themselves,
the creators of this system, the supposed connoisseurs.
Ed
Windows Defender can interfere with your work.
If I turn off WD Real-Time Scan, my hashdeep runs
go three times faster.
Since your ratios are so much larger, I would have
to conclude those runs are backing up a different
set of partitions.
Presumably the Windows 10 built-in was writing to
an external target which was not part of the
backup source itself.
Both the Win10 built-in and Macrium, use a variation
on VHD for storage. Only occupied clusters should be
recorded. While Macrium has compression, you can still
compare the output size and see if something is amiss
in a major way. I don't think Win10 built-in has the
ability to do sector by sector - you might be able
to mis-configure Macrium, but the Win10 one should
remain about as good as these methods can get
(for a *full* backup, not an incremental or differential).
If Macrium is doing incrementals, of course it's faster.
The paid version of Macrium is capable of more trickery
than the free version :-)
Â*Â*Â* Paul
Well, mine's not quite as bad as this:
"I started running Windows 7 Backup, including a system image 2 days
ago.Â* It's only up to 17% completed now. I am running Windows 7
Professional, 64bit.Â* The internal HD is 2 TB, 8 GB RAM & AMD Phenom
II X3 Processor, 2.5 GHz.
...................................
...................................
"
and then this little addition
"I have the same question (14)"
https://goo.gl/nNh8vV
And then there's this one;
https://goo.gl/eQv41v
Our Good Guy would have a ball insulting him. I try to feel sorry for
him but even I find that difficult.
Ed
1) Check health on drives with HDTune.
2) Remove drives from enclosures that prevent health checks.
Â*Â* Plug drive into main system, check SMART health of drive.
Â*Â* Firewire, for example, might not have SMART passthru
Â*Â* in the command set.
3) Use the Task Manager to check for "competing" programs.
Â*Â* Things that seem to be active, when the backup is active.
Â*Â* (MsMpEng).
Slow Copy-On-Write (COW) can be an issue with shadows.
Since many backups are done in "cluster order", we can't
necessarily blame fragmentation for this. Something like
Robocopy, now that could be slower if the source disk was
fragmented.
You can also run the HDTune benchmark, as a means of
identifying problems with storage devices (without
even using SMART). For example, if a drive slips into
PIO mode, because you pinched or kinked the SATA cable
and the error rate in the cable causes the write rate
to gear down, then transfers could be quite slow.
A benchmark curve of sustained performance might
highlight this (4-5MB/sec flat line bench). There
is a sticky recorder of cable errors in SMART,
so SMART will not forget a transgression with
bad cables.
And backing up to DVDs - masochism or what ? Trying
that once in a test (at 5MB/sec) was enough for me
thanks. That, and having to format the discs when
Windows asked me to. I was ready to pitch the computer
out the Windows, and I only had four DVDs to do :-)
Maybe using 100GB BD discs would make this less
painful.
Â*Â* Paul
I blame MS here; including within Win7. When you click on "Take System
Image" it presents you with the option of writing to a DVD; and it does
not much more than just image your C drive.
The point here is that the Macrium image will rescue you from any
trouble, including a total HD fail. It will restore your whole C drive
to the time the image was taken.
So, what does the MS image give you over that? Answer, nothing, well,
virtually nothing more.
So then, yet again Macrium seems to know much more about Windows than MS
does.
Ed