As others seem to have found, absolutely nothing happens when I try an incremental backup of Windows 10 to a wim clone, which was made in Winclone 7 several weeks ago.
I don’t even get an indication that the drive I have the image on is even being accessed, despite the fact that Winclone has successfully selected the image.
In one post, I saw that this is being addressed, but I would have thought that this problem would have manifested itself more widely…
Is there a time frame for the corrective update?
We are in QA right now, and I hope to have the beta released this week.
tim
That will be good. I have an unrelated problem with a VM of BootCamp, and an incremental backup would save me a lot of time.
Here is the beta build of Winclone 7.2 that includes incremental backups scheduling (and a bunch of enhancements to incremental to make it more robust):
https://www.dropbox.com/s/ocvgrl808fpgasm/Winclone_Build-40589_Version-7.2.dmg?dl=0
Your current Winclone 7 license key should be detected. Let me know if you have a change to try it and let me know how it goes.
tim
Dear Tim,
Not great. Yes, I could identify and start the incremental backup (once
I’d figured out to click a couple of times for the BootCamp partition),
but it got to the point where the progress bar hit the end (i.e. it
appeared to have finished), and it just sat doing nothing for 45 minutes
or more. The incremental backup that far had already taken over 2
hours. Also, twice, my CPU had been getting very hot. Core temperatures
were at 100°C, and the fan was going at 2800 rpm. It returned to more
regular temperatures within a minute. This is on a 27’ iMac - late
2015 model, with the fastest i7 and 32 GB ram!
So, I aborted it. By now, of course, my good backup was gone, so I had
to try to do a new one. It seemed to start OK, but then hung after
maybe 30GB had been copied (out of 700GB or so). I would have left it,
but then my CPU again showed maximum usage with all the cores going up
to or close to 100°C! Worse than that, it was just staying like that!
This is not a good idea. It’s OK for a short time, but not prolonged. I
don’t wish to wreck my computer 
So, what to do? I now have lost my good backup (even though it was
several weeks old…), and don’t want to mess things up. I suppose I
could try and go back to 7.1 and see if it is OK, but I can forget about
the incremental backup until this is sorted.
I’d appreciate your view.
Have a great weekend,
John
When you say that the good backup is lost, can you explain a bit further? When you go to restore the image, you should see a dropdown list of any prior backups in that image, and you prior one should be intact.
As for the high CPU, we have done testing on a bunch of different machines and have not seen that. How large were the changes between the first image and when you did the incremental?
tim
When you say that the good backup is lost, can you explain a bit further? When you go to restore the image, you should see a dropdown list of any prior backups in that image, and you prior one should be intact.
Whoops. That is then my fault. Seeing I had probably had a failed
backup, I didn’t realize that the original wim file would still be
there! So, I formatted the drive, and tried to start the new backup.
Oh dear! I should have checked, but I never thought about how this
incremental update would work. It’s not like Time Machine or Carbon
Copy Cloner…
As for the high CPU, we have done testing on a bunch of different machines and have not seen that. How large were the changes between the first image and when you did the incremental?
tim
Although program changes would have been fairly small, although there
would have been a few new additions and maybe some updates, but there
was also a substantial update to Windows 10. I had not used Winclone
since March! A substantial part of the disk is filled with very many
scenery files for flight simulators. These can take up a lot of space,
as they are tiles of data representing the ground and so on.
John
Tim,
As a further, I decided to have another go at a new image, using the 7.2
beta. This time, I did not see any CPU heating problems, nor excessive
use of the CPU until well past the time I noticed it the other day. So I
let it continue, and it was still going when I went to bed! In the
morning, it did an integrity check, and then the file verification
started. It eventually completed, and it had taken something like 13
hours or so to do around 500GB of data. Is that typical?
Regards,
John
what is on a SSD or physical drive? Physical drives do take a long time with file-based backups.
tim
My iMac has a fusion drive, but the Boot Camp partition will be on the
physical drive bit, and I backed up to an external physical drive! So,
I now understand it’s going to be that slow… I saw somewhere (a
forum or FAQ) that you were doing 50GB in around ten minutes (?), so
even allowing for things to be a fair bit slower, I would have figured
my 500GB of data would have taken maybe 3 hours… As I said, it
took around 13 hours. It is what it is, as they say. I’m sure the fact
that I have all these flight sim. scenery directories, with hundreds of
files in each, is not helpful!
John
Yes, the iMacs with the physical drivers are way slower than SSD with WIM based imaging. Block-based imaging is much faster, but doesn’t have the advanced features such as driver injection and incremental. I wonder if it would be faster overall to switch to block based and not do incrementals for your setup.
tim
Certainly something to think about. Thanks for the advice. Now I’ve
done the main one, perhaps the incremental won’t take too long. It will
be interesting to see, as I don’t make substantial changes to my Boot
Camp set up. It is mostly updates, and the occasional additional
software purchase.
Regards,
John
1 Like