@whitestar_999 - sorry for the delay. After reading your post in the other thread, I can only suggest one thing. You need to create separate Recovery Media for each product and test independently. By that I mean take your product and execute a FULL image, make a few changes then test your DIFFERENTIAL/INCREMENTAL images. Using that products Recovery Media, do whatever restorations you need to do to test its reliability. Keep the products separate. As far as Reflect is concerned, I've never seen it fail to recover any of its images as long as you choose the proper time point in the image chain to recover to... either using a Legacy-MBR or an UEFI-GPT BOOTing environment. It's been pretty solid for me. During some testing I was forced to use the FixBOOT option a few times... mainly because the MBR that was imaged during the test was bogus (Rollback RX) causing an unsuccessful restoration, not the fault of Reflect in any way. If you really need to share a UFD for multiple Recovery environments, use a UDF multi-BOOT setup program (Yumi, Xboot, MultiBootUSB, etc.) which makes the individual apps Recovery Media ISOs available as completely separate operating environments. That way the running Recovery Media environments do not step on each other as FileSystems/FileSpace are concerned... although a good Recovery Media should not be doing that at all.
How long V6 Home will be supported? For backup/restore/fast restore V6 is good, right? i.e nothing new regards these in V7, right?
Major releases are usually supported for at least 1-yr following a new major release. v6 is excellent, v7 will continue with that excellence as well as adding some additional scheduling options (CONTINUOUS BACKUP shortly after initial release) and the ability to fire up any Reflect image in the Hyper-V System supported from W8 on... See HERE for initial announcement...
Froggie, can you please refresh my memory - were there any limitations with respect to Win 7 and the use of the new features? I seem to remember an early comment but I am no longer sure (maybe something to do with the virtual boot?)
Hi Beethoven That's all I run is Win 7 Pro x64. Everything about Macrium runs fine on 4 machines I am involved with.
One of their new v7 features, Instant virtual BOOTing of Backup Images will not function under Windows 7 due to the fact that the needed Hyper-V environment cannot be invoked under Windows 7. It's only supported on W8 and above. All other immediate features PLUS their new Continuous Backup feature which will be available shortly after v7's release should all operate just fine under W7. The Continuous Backup feature will be using the new public release of their CBT (Changed Block Transfer) driver which creates much smaller Incremental images as well as provides for much faster restorations.
Hi Beethoven Apologies. I forgot about the Virtual Boot. I tested it and it was fine under win 8 but not 7. But I have been using the CBT driver on all my Win 7 machines. It is slick. Pete
As I have mentioned before, I only do full images for my system and my wife's. We are both on 64 bit Win 10 Pro. As far as I can tell, I would have NO use for V7...we are on V6. So, will Macrium stop supporting V6 as the post above states? Funny, my last full image is 34GB. I installed some software I decided I did not want and was not too sure it uninstalled well. Since I did a full image BEFORE I installed the software I then did a full restore. It only took 2 1/2 minutes! I was sure surprised at how fast it did the restore.
@MPSAN Yes Macrium will stop support for v.6 a year after v.7 is released (at least it did the same for v.5 a year after v.6 was released). This could cause problems for Windows 10 users as some future upgrade could break compatibility. So this could "force" users to upgrade to v.7 even if there is nothing new in new version that would interest them.
Well, I was afraid of that. Anyway, they do not show an upgrade price except for a 50% discount. If that is 50% off the 4 pack price, that is a lot for an upgrade I do not need!
@MPSAN - If you only do FULL images, you could be using the FREE version (any version) without issues. You'll lose that fast restore but it'll work flawlessly as it always has.
Yes, and I did use the Free one for a while. I purchased the 4 pack a while ago when they had a Black Friday deal. Still expensive but it was a deal. Anyway I bought it because it allowed Passwords and folder/file backup as well as the full image. I never did get into Incremental images. Unless you want to count AX64 where I have so many licenses!
Anyone else having problems with 6.3.1734? That version of Reflect is unable to unmount drives (very first action of cloning); in my Windows 10 setup and in the Windows 8.1 and 10 PE environments. I had to restore the older PE images from an online CrashPlan backup, since it ironically destroyed the partition holding those images on the backup drive...
I'm not sure whether you are replying to my question. If so, I might not have been clear enough: I'm cloning, not imaging. The error I get is about unmounting physical drives (not images) when cloning.
No need to apologise; I was not clear enough (and made it worse by mentioning "images" when referring to ISO files containing the PE stuff).
Depends on the definition of substantially. More defragmenting needed the larger the next incremental, but then they drop back
Just to clarify Peter's response a bit... using Reflect for imaging, it primarily images the surface of your disk, not your individual files. Each additional Incremental (or DIFFERENTIAL) will only reflect the changes in surface utilization since your last image. If you defragment your disk, the defragmenter will rearrange a ton of your disk blocks to result in what you asked for (basic defragmenting, disk consolidation, move high access files to the fastest area of the disk, etc.). This will drastically change the surface utilization of your disk, but all your files will remain the same. As a result, the next Incremental/Differential image taken by Reflect will be substantially larger in size (your surface utilization has changed drastically during the Defrag but your files have not). Following that image, all should return to normal... unless you defrag again. For those that need to defrag (often?), the best time to do it would be just prior to your next FULL Reflect image.
Thanks, @Peter2150 and @TheRollbackFrog! My suspicions are confirmed. Since the time I used Diskeeper, incremental images had increased by a couple of GBs, instead of being lower than a GB.
I just purchase a new HP laptop i3, 4gb ddr4, 500hdd(5400rpm)... so technically this should be faster than my desktop AMD athlon II x2, 250HDD,4 GB ddr3 but I was wrong when I did my first FULL it took more than 30mins, INCREMENTAL @ 5mins, RESTORE is still good @ 3mins, on the other hand with my desktop FULL less than 30min, Incremental 1-2mins, RESTORE 1-3mins. What other factors are causing such slow backups?! I first assume due to the rpm... need clarification! Off topic is Win10 really slow I mean my WIN 7 boots at least 40-25sec, while WIN 10 is more than 40sec and does WIN 8 & 7 compatible mouse conflict with WIN 10?! Experience slowdown/hang with my applications with this laptop forcing me to do a hard reset(was scared it may damage the drive) till I removed the mouse and everything was ok. Diskeeper auto-defrag will always increase incremental images... experienced this with AX64.
