MPSAN, you need to be concerned about the broken BOOT path even more so than the missing driver. I don't know your System config (UEFI-GPT, Legacy-MBR) but when you restored that image, did you restore all the partitions needed for the entire BOOT path and not just your C: partition?
Only on my test System, not on my most important System Yea, they've fixed a lot of stuff in v7 (mostly broken by v7 ) , but there are still issues... especially off in the "fringe" areas of using this update (scripting, Task Scheduler modification, etc.). If you're just doing basic imaging (as well as scheduled imaging) from the Reflect UI interface, all should be pretty well. Most of the license upgrade issues have been dealt with, I believe, and NFR licenses were just activated for upgrade within the last few days. Hopefully the dust is settling. But most users, here at least, are not really affected by any new features in v7... there's still no reason to jump in that I can see. "Continuous Incrementals" might be the area that snapshotters (Server Mgrs and Rollback RX converts) might be most interested in (that's the one that will make the biggest use of the new CBT driver)... but that isn't available quite yet. So unless, you absolutely require the need to BOOT your image into a virtual System directly from the Reflect UI (viBOOT... W8 & 10 only with Hyper-V installed <not supported by older processors>)... there's really nothing new here in v7... yet. Even before their promise for "Continuous Incrementals" soon after the v7 release... I asked for a simple change to the Reflect UI scheduling System (2-yrs ago, BTW, and fully supported by the Windows Task Scheduler) to offer an HOURLY option... they opted not to even offer it in v6 AND it's still not available under v7. Possible it'll be part of "Continuous Incrementals"... that's probably where it makes the most sense. Overall, I don't think v7 brought much to the table as a release, especially for those who had to pay for the upgrade... what the future will bring, who can say. v6 has been a fairly solid product... no reason not to "hang" for a while.
Thanks Froggie. OK, I'll stick with the known. But will check out 'Continuous Incrementals' when it comes.
PD, I have played with a makeshift "Continuous Incrementals" under v6 using the BETA CBT driver and WTS (Windows Task Scheduler) manual changes (changes to HOURLY and multi-HOURLY <every 2-hrs>, etc.). With CBT the INCs run very quickly (no more "Looking for changes" process and only changed blocks rather than changed clusters that are found in the "Looking for changes" phase) and the restorations are also very quick (smaller INC images). It's a bit of a pain in v6 as once you make those direct WTS changes, you can no longer make changes under the Reflect UI for that scheduled operation. I'm sure the new "Continuous Incrementals" option to come will make that whole setup much easier, and most likely, all be managed under the standard Reflect UI...
If you don't have a clock to beat, cost wise, that's probably a good decision. Plus, there's always license discounts along the way...
I've already done several restores under v7. No issues at all. One thing that was interesting, is I didn't remove the CBT driver from V6. It upgrade when I upgraded to V7 with the NFR license. But the driver was still it's original location. So I used the special driver tool the gave us. It did the uninstall but left the driver in the SVI folder. Checked in the gui and cbt was no longer available. Restore fixed that. I am checking something but need to wait until noon to test. Will report back.
Oh one other thing. CBT works fine on incrementals, but not on differentials. Wonder if the marketing types got carried away
If you're running a DIFFERENTIAL against a FULL that was created prior to your last System reStart... it cannot use CBT since the CBT reference begins at the 1st image following the reSTART. If the 1st image following the reStart is a FULL or DIFF, then the next INC should be able to use CBT... IF it was implemented in a reasonable way. Otherwise, it'll only come into play, with INCs, starting with the 2nd INC taken after the System reStart.
Okay, that makes sense, but also makes the feature next to useless to me, as I will almost always have a restart between a full and differential. I posted on the forum and will see what they say. Also I am testing a schedule thing but had to restart. I copied the xml file from the system I have v6 on but it ignored some of the settings on V7. Rebuilt and testing.
The 'feel good' restore FELT GOOD... Just did not notice any real speed increase so am assuming that CBT is not active for the schema I am using. Will have to check out if I need to do something in there rather than just in the overal settings. But other than that Build 7023 is workig OK here.
Just finished a quick test. If your 1st image after a reSTART is a FULL, then any DIFFs between then and the next reSTART will be handled by CBT. If your first image after a reSTART is a FULL followed by an INC, the INC will be a "Looking for changes" version with any INC following that before the next reSTART will be handled by CBT. More to come...
Should one have both of the 'Enable Delta Indexes...' and 'Enable Chnaged Block Tracking...' options checked or one or the other, i.e., are they mutually exclusive? The program allows both to be enabled at the same time but am wondering if that should be the case if one wants to use CBT? Regards, Baldrick
OK, I am using 64 bit Win 10 Pro with a GPT formatted SSD and 3 TB GPT formatted HDD. The HDD is where I save my images. I always do a FULL image and include all Partitions. When I do a restore I ALWAYS restore all the Partitions. That is because it is fast. In fact I have been asked why I just don't use the free version if this is all I do.
@MPSAN - That's a good question about the FREE version in your case ... except there's no FREE version for v7 yet and if there was, CBT most likely would not be available. I'm still concerned as to why you lost that BOOT path on the restore... I hope it was only a 1-up failure. @Baldrick - the most efficient use of CBT is with both of those options in use (Delta Indexess and CBT).
So far this is what I found... On 2-27 BEFORE V7 , using V6.3.1745, there was NO mrcbt driver and all was good. On 2-28 I installed V7 and it too was good as I did do a full restore that proved that image made with V7 was good. It also DID have the mrcbt driver. On 3-3 I updated to 2023 OK and did a backup...again, always full with all partitions included. Also, I even always recreate rescue media. I played with a config of a small program and did not like it and decided to restore my Image...all partitions and it would not boot as described above. My 2-28 V7 image would restore and boot windows. My 2-28 Image HAD mrcbt but the build 2023 removed it!
OH, I had answered that before. I wanted Passwords and we wanted to try file and folder backups. I think I will try an image now that it is all working and then go back to V7 before 2023 and try the update again.
OK, I am going to try the restore and update now and see if it boots up with the removed mrcbt, or will 2023 remove that driver. One thought I had was to try my reflectdlfull and see if it will do anything. I mean, I think that will take me to 2023, but when it sees that I already have it will it do anything? OK, cover me I'm Going in!
Well...I restored my good 2-28 backup with V7 before Build 2023. I then booted and when I brought up MR it told me that there was a new update and I got 2023. I then looked after the update and mrcbt was STILL there! I did a full image and then booted from rescue and told it to restore and ALL WAS OK! SoI guess I will never know why 2023 removed mrcbt before! Anyway, I think I will now leave well enough alone...except, perhaps I will remove the boot macrium WA5K folder and AIK and AIK kits. THEN I can see what I break!
Hi MPSAN You are working on the assumption that computers are logical. They are not. I am not joking. I've learned that only about 50% of the time a logical thing works. For the rest you have to go to the "dark side" the illogical. Scary how many times it has worked. Pete
And sometimes we even needed a power up/down on "big Iron"! I guess my age is showing when VM and MVS were the OS! Who could forget the great MVS command set! I remember d,,,all to display the drives.
TRF, When I had downloaded V6, I had selected "Download Reflect installer & PE". Now if I want to do a fresh install of V7, I have to download "PE" again or just installer?
