You need a slightly different way of doing things. If you have a successful Backup Definition created and are using it in one of the many ways to do so, a slight change must be made. 1. With the Reflect User Interface in front of you and the BACKUP TAB selected on the left, <select> your Backup Definition in the RIGHT hand pane (don't open it, just select it> 2. From the ToolBar appeariing above your Definition area, <click> on the 2nd Icon from the RIGHT ("Create a shortcut of the selected file). 3. A small window will open. From the "Backup type" DropDown, select the "Prompt" option (it must be "Prompt" or the ShortCut being created will do whatever image you select here without the ability to comment). In the "Target" DATA field, enter the name you'd like to call your DeskTop SHortCut, then <click> OK. 4. EXIT Reflect. On your DeskTop you will find a Macrium ShortCut with the name you just gave it when you created it. For a quick test, feel free to <double-click> that ShortCut. Up will come a window that will allow you to select the type of image you wish to create and set your COMMENT to anything you wish. If you <click>ed FINISH at this point, your imaging operation would start using your selected backup definition information. If you don't want to image at this point, just <click> CANCEL. The DeskTop ShortCut may be placed as well on your START menu or your TaskBar as needed. That's about the easiest way to perform MANUAL images and comment them for later reference that I've found along the way.
Thanks both of you for your help. I got it now. Reflect looks like really good reliable backup software, I just wish it was more user-friendly.
You ar welcome! If you know the basic actions, and have a repetitive practice, then he is user-friendly enough It is important, if only be reliable in the work.
I cloned my BitLocker enabled HDD to SSD in Windows 10 with MR. the C: shows Bitlocker on. Macrium shows BitLocker unlocked on the original HDD, and no icon at all on the cloned SDD. https://imgur.com/a/wBvJr4S
7.1 Free > updated 7.1.3147 to 7.1.3169 thru internal updater....(tried Diff n' Full). Edit: ran 7.1.3169 stand alone installer (Full completed + Verify)
yes, working fine. I am encrypting the drive with BitLocker at the moment, taking longer than lunch. all seems well. thanks.
Nice. To satisfy my curiosity, when you boot Win10 on the SSD does the OS partition get assigned the drive letter C: or H: ?
Thank you for heads up. I've never used CBT driver and also checked my logs. It seems that all is good with my images.
I thought the options I had selected would use the CBT driver (Incrementals forever, Enable Changed Block Tracking for Incremental Backups checked in the options) but I see no mention of it in the logs, so I guess I am unclear on what actually causes that driver to be used.
The CBT driver must be installed/activated upon installation... I believe it's installed by DEFAULT. What it provides is a tracking mechanism for all changes made AFTER THE 1st IMAGE (which becomes the reference for all that follow) following a System RESTART. If you only make one image between your System reBOOTs/reStarts, CBT will never come into play and the original Reflect "Looking for changes" process is invoked instead. When active, it produces smaller and faster Incremental images and faster restores when using those CBT images. It's very beneficial for users that make multiple Incremental images during a single System session (like every <n> minutes, hourly, etc.)... I'm sure Server admins probably love this feature. Typical users may not even notice it's even there.
Ok, so this is only for an ongoing session and if I run a backup each day and shut down each night this never happens is what I am getting. That would make sense. Thanks for the explanation. Sounds like I don't need to be worried about corrupt backups from this issue then.
Thank you Kent! === Why on earth Macrium didn't give this one an higher version number than 7.1.3196 is beyond me. You cannot have two different versions with the same version number.........
So, if I do not restart for a few days and create more than one Incremental per day or create more than one Differential backups per day. Then CBT driver participates in the backup? https://knowledgebase.macrium.com/display/KNOW7/Corrupt+Incremental+Image+Files
Argh, my bad! My fault. Easily to confuse 7.1.3169 with 7.1.3196. Thanks for pointing that out bjm_ !!! And apologies to all for this misreading by me!
The CBT will definitely participate in any Incrementals done (after the 1st) since your System was reStarted. The Differentials will only use CBT if the FULL image they are being run against occurred during the same System uptime as those Incrementals. If the FULL was done before that System session, no CBT will be used for any Differentials since that time. You can always test an Incremental chain (CBT didn't affect all INCs in that time frame, it just may have affected some) by mounting the last Incremental in the chain and see if it mounts without FileSystem errors. If it does, the whole chain is fine. If it doesn't, dump those Incs and continue under the new version.
So, with Macrium Free. CBT only participates if/when a Full and Differential(s) are created in the same System session?
CBT isn't included in Reflect Free. But the most concise and accurate explanation of CBT is probably this: When CBT is installed, enabled application-wide, and enabled for the volume being imaged, an image backup will use CBT if it is appending to an image that was captured in the same Windows session. That even accounts for cases where disk rotations are in use and therefore the general "second and subsequent Incremental" rule may not apply since the Incrementals might be added to different sets.
