About the disconnection problem, see Windows 10: Hyper-V Connection Lost. I think the main purpose of a virtual restore is to check that the image is bootable, without doing a physical restore.
Ok...I had thought that I could add a file to a thumb drive, etc. Anyway, thank you and I will see where to uncheck Enhanced Mode. Is it available in ViBoot?
Yeah, which is why I used the term "installed and usable at the same time." It's not that difficult a process to manually perform the re/un install of Hyper-V each time you want to switch, either. But that does one no good when one has, for instance, a web server running in VMware's software which needs to run 24x7... Yup, I know exactly what you're saying. I was trying to inject a little humor, perhaps, while also being a little insistent that though a full restore and boot/test method would be the most accurate method, using Hyper-V is so close to being just as accurate and would be SO much easier that it might actually be a "better" method because of that.
Think I will be staying with v6 for some time yet. There's an air of 'rushed release' about this, like MB3. Hope Paramount aren't introducing too much (or too little ), and messing up an excellent product.
On my system, V7 is running just as well as v6 was; there is no discernable difference between the two versions as far as my daily backups are concerned. IMO it is entirely unfair to compare the 'fiasco' of MB3 to this upgrade.
You can uncheck Enhanced Mode from the Hyper-V configuration. Go to Hyper-V > Action tab > Hyper-V Configuration > in the left panel, User > Enhanced Mode...
Having been part of Reflect's v6 "unofishul" BETA here on Wilders in early 2015 and involved with the MB3 fiasco, I can say the following... Macrium missed a great opportunity by not offering a similar opportunity here in the Forum for v7. Many, many issues were discovered with v6 here on the Forum before the public release (about a 6-week period)... as a result the public release in Feb. 2015 was an excellent, trouble free release. Those issues were discovered mostly due to the myriad of different configurations (both hardware and software) found among random users... like us! I asked the Macrium Dev Group earlier this year if they would like us to give the pre-release a tumble before the public release date similar to v6. Their answer is below... Hi Froggie Thanks for the offer, it's really appreciated. However, the main new features for 7.0 have been already extensively tested in the past year or more. We're adding the final version of the Changed Block Tracker (CBT) to Reflect as well as including the latest viBoot in the Reflect installer. viBoot will be integrated with the restore view so you can select an image file, click 'Boot' and directly load viBoot with the image file populated. We're also changing Scheduled Tasks to use the Task Scheduler 2.0 API, but this doesn't add any new functionality it simply changes the back end to use TS 2.0 for Vista and above. There will be plenty of updates to v7 and we plan to add continuous backup in v7.1, This will backup every few minutes and is a practical option now that we have the CBT driver to decrease incremental image time. Don't worry, CBT can be turned off if it isn't wanted. Kind Regards Macrium Support It's fairly easy to see that without an outside BETA exposing a new application to different System users and environments, things can be missed along the way. I've always been an advocate for BETA testing (I've been part of many along the way), especially using non-Corporate volunteers... there's very important information to be gathered in this manner. This is the "boat" that Macrium missed this time around. I believe they've learned the hard way but, hopefully, will adjust accordingly in the future. Now, as far as MB3 is concerned... they actually had an outside BETA test going on. The problem is that many issues were discovered and reported during this testing period but not acted upon (report lost...). As a result, the public release was terrible and continues to be so (albeit not quite as bad as the initial release). This is just poor BETA test management and control, and clearly some serious internal pressure to get this thing on the street, even before it was ready (maybe SALES goals/projections... who knows). This is exactly what happened to a Horizon Data Sys BETA test of their Drive Cloner v6 offering, one that guaranteed the imaging of Rollback RX snapshots as well as normal imaging capability. That BETA was horrible, included a developer who wouldn't really talk much with the BETA testers, and the BETA was cancelled without notice or reason with a list of twelve major outstanding issues with the software. A week later it was released publicly... it was a mess. BETA tests are very important due to the System configuration exposure an application can get in this manner. ALPHA testing occurs in the Corporate house, but is usually exposed to Systems that meet a Corporate specification... meaning most are the same. This is why in-house-only BETAs tend to be pretty week in their ability to find all the issues. I believe Reflect v7's release has taught Macrium something (without losing too much customer loyalty, I hope)... at least I hope so. I'm not sure Malwarebytes or Horizon Data Systems has learned much of anything by their experiences.
Bingo and right on. I was spoiled when I was privately testing Shadowprotect. When I found a serious problem they would usually confirm it in a day or two, had a solution in a few more days, and released. I will say MB3 folks have learned a lesson. I was getting nothing but on FUD on the forum and finally one of the Technical managers reached out to me and realized they had a problem. I was testing and sending logs and they identified a lot of problems. I begged and they listen to put together a build for me to test. It was bad, but they finally got it together and the current build is working well for me and quite a few others. But they are working and I think they learned a lesson. Hopefully so has Macrium
Oh and Askmark they are totally comparable as they stem from the same source. A little too much arrogance that they've got it right.
Thank you Froggie for this; CBT was something I really didn't want running on my machine and am relieved to find out from you that it can be turned off. And after some more thought I do think that being able to boot an image from within Reflect will be something I will find useful. The v7 release was done poorly, but this product has served my needs so precisely and reliably over such a long time that the good will I have for this company remains intact.
OK, Thank You. I did it and will see what happens. I must admit, so far, I do not quite see the value of ViBoot if the LAN/Internet and thumbdrive do not work.
...so, what, in V7.1, would a continuous backup be? I mean, in terms of file size and for how long could you go back in time? I will be looking at this.
Hello, A new update has been released, version 7.0.2089... Homepage: https://www.macrium.com/ Download Page: https://www.macrium.com/download/home Release Notes: http://updates.macrium.com/reflect/v7/v7.0.2089/details7.0.2089.htm
Good to see this displays the progress again. I hope they have all of these issues sorted out or are close to it. I still have 10 more machines to upgrade from v6 at work. Including 2 servers that I am not touching until the issues are minimized.
Ok, what did they do now? I see the Release Notes are still there if I use this link, but we seem to be back to 7.0.2079, which I had originally skipped on my desktop but am now stuck with because I attempted to download 2089 and got 2079 instead. This isn't doing a lot for my opinion of version 7.
Viboot works with Macrium 6 with hyper v. All you can do from default is see that your image will boot. Access to the Yes. After installing MR 7 a message said CBT driver installed.
The "tracking" of disk surface utilization needed for proper Incremental imaging as well as DELTA restoration is being done by a dedicated driver... although, in no way, is it like the AX64 implementaion. This tracking is re-initialized following each System reSTART (at first image) and continues until the next System Shutdown/reSTART. Our (some on this Forum) testing has shown this to be a very reliable approach to discovering changes to a disk's surface utilization.
Following up on appster's question, I participated in Isso's AX64 testing until I found that virtualizing my system (by running Shadow Defender) would "brake" AX64's tracker! I'm now using MR6-Free (with differentials) without conflict from Shadow Defender, so I'm curious if I can expect the same from MR7?
MR v6 FREE contains no (CBT) tracking whatsoever... and when they get around to releasing a v7 FREE, my guess is it won't contain tracking as well (it's a special PAID feature). If you decide to ever go for the PAID product, it will have optional tracking available. If you decide to use MR's tracking in that case, there should be no problem as the tracking method gets completely RESET when you reBOOT from your LITE Virtualization (SD) session. AX64 always tried to keep the tracking valid across reBOOTs and this is where their problems lied with both LITE-V and off-line modification of the FileSystem (ie, WinPE/RE-based, LINUX, etc.)
