It says Windows RE Status: Disabled. Edit: OK. I have enabled it, but it still doesn't select the recovery partition. By the way, I originally used PowerShell to test and enable, but enabling it failed using PowerShell. Command Prompt worked for enabling.
I don't know what others do but I just select ''image selected discs on this computer'' and I tick them all
Depends on your disksetup/needs i would say. I got 3 hhd disk in total (+ramdisk also shown in macrium) and only the windows hdd gets backuped. Getting a backup of my e.g. game disk would just spike the time and place for my backups. In worst case i just redownload my favorite game again (since it's an online game no savegames are lost)
I think we each choose our options for backup settings according to our needs and the way we use our computer. Macrium is so versatile
Strange. My only guess is that maybe your Recovery partition isn’t tagged properly? On an MBR disk, it’s supposed to have an ID of 27. If you open Diskpart, select that disk, select the Recovery partition, and type “detail partition”, verify that the Type field shows as 27. If not, run “set id=27”. I’m guessing it will already be correct though, since Disk Management already identified it as a Recovery partition, in which case given that you’ve also enabled WinRE, I don’t currently have other ideas as to why Reflect isn’t selecting it. That’s pretty standard, but some people like myself have a dedicated Data partition that we want to back up separately because it allows us to make faster OS backups prior to changes that might not go so well, and backing the OS and Data partitions up separately allows you to have different schedules and retention policies for each. Obviously in simple cases that won’t apply, but sometimes people just want to understand why something isn’t working as expected even if there’s an easy workaround available.
I don't have a backup schedule as I backup on demand. This is because of the way I use my machines and test things. My data is in 2 places. On a USB drive and also on my Macrium USB drive when I image my whole machine. Just to be sure I also use Karen's Replicator now and again for my pics and docs... just to be sure Yes I agree it's important for people to know why Macrium things aren't working as expected... it could be crucial.
I'm not sure how much thought Macrium has given to this ability... but plain and simple, the RECOVERY partition is NOT NEEDED to backup and restore Windows, especially if you're using REFLECT. There's nothing in that partition that will keep you from running your active Windows operating System... it's only used for attempted repair scenarios, and in that vein, a better option is always Macrium Reflect I guess somewhere along the line someone needs to "declare" whether that partition is really as important as some people think it is and make it part of the BOOT set... so far, it remains reasonably ambiguous.
I agree that in most (all?) non-BitLocker situations, the Recovery partition isn't boot-critical, and even in some BitLocker situations it isn't boot-critical. However, in my experience Reflect has always selected the Recovery partition when that function is clicked, so I'm not sure why Hadron's system is behaving differently, even if it doesn't create a practical problem.
I've just had my first failed Reflect restoration. And the first time with v7. Never had one with v6. I suspect it's my CBT problems. It hasn't fully restored my operating system, leaving programs unregistered, system restore points empty and settings back to default. I am going to see it IFW can save me. JP. You are right. Play safe, and turn CBT off.
OK. IFW restored my computer excactly. Like a good image program. I'm uninstalling CBT. I am sure that's the problem. I place reliability way ahead of speed.
System restore points empty is expected when restoring a backup that was captured within Windows using VSS, because the VSS engine itself excludes those from the snapshots that it generates and that Reflect uses. VSS also excludes the Windows Search database index, as another example, since that can grow quite large and can be rebuilt when it’s missing. Reflect backups captured within Rescue would contain those things because Rescue doesn’t use VSS, since it’s unnecessary when you’re not backing up a live system. If IFW backups captured from within Windows capture those items, it sounds like it might use a proprietary snapshot engine. Anyhow, CBT would definitely not account for missing System Restore points. Can’t explain the others, but there isn’t a lot of detail there.
Interesting, hadn’t heard about that case. Looks like that one has been fixed, but it’s another example of the value of weighing cost vs. benefits when installing software, especially optional components. I personally think very carefully before installing something that will insert itself at a low level of the OS and run persistently. Part of the reason is that if it causes problems later, the symptoms won’t always clearly implicate that component, so having more such components than you need will not only increase the chances of problems, but also the difficulty of diagnosing and resolving them. I’m still surprised CBT has created the number of problems that it has, though, considering that it’s basically just meant to observe activity rather than intervene. If anything I’d have expected more issues around CBT not reliably recording all changed blocks in some cases or not reliably determining when that was a possibility and therefore falling back to the normal “Looking for changes” method. And while I’ve found the CBT use cases described here illuminating, I still think that for a significant portion of Reflect users/use cases, CBT offers a negligible benefit in terms of time saved but seems to introduce a non-negligible amount of risk.
In the first few minutes of the Reflect restoration, I noticed: Microsoft Office, Directory Opus and Internet Download Manager had deactivated. I own all them. Luckily Windows didn't deactivate. I didn't bother messing around trying to get it all activated again. I just went straight to IFW.
You can boot into Rescue Media to create backups, not just perform restores. It’s not the typical way to perform backups of course, but it can be useful in certain situations. For example, if your system was suddenly rendered unbootable, you might boot to Rescue Media and capture a backup of its current state before performing a restore in order to save any data you might have updated since your last normal backup before you overwrite it with a restore. Or of course if VSS is broken, a Rescue Media backup might be your only way to make a backup at all, although of course in that situation you’d want to solve the underlying problem sooner rather than later.
I see what you mean now. When I thought of "Rescue", it didn't relate to me that you meant "Rescue Media". Maybe I didn't think hard enough at the time I posted.
Speaking of threads that might be of interest to people using CBT, keep an eye on this one on the Macrium forum. Two users running the latest release have found that running CHKDSK against mounted images that were captured with CBT shows multiple problems, and restoring that image results in an unbootable system. Still early of course, but this sounds eerily similar to the CBT corruption issue from a while ago. The last FOUR Reflect updates have all contained changes related to CBT, and I personally can’t think of any “benign” explanation for the behavior those users are seeing. It sure sounds like a data-breaking CBT bug. Best case is probably that it’s only triggered on systems that also have some other application installed or something. Anyone who uses CBT care to run CHKDSK against some of their mounted backups that they’re certain were created with CBT? Check the log from the backup in question to look for “CBT Init Success”.
Restore points are not included in the image if the image is created from under Windows, and not from WinPE.
I got stuck in a reboot loop and a black screen after restoring from a CBT enabled synthetic full in Macrium Reflect v7.2.4156 and had to re-install windows from scratch because I didn't have a pristine full backup since I consolidated the CBT enabled incremental backup into the full backup image. This is a serious issue with CBT and it causes the incremental or differential filesystem in the backups to be corrupted. The Macrium forum thread for this CBT issue ois https://forum.macrium.com/Topic28629.aspx.
Macrium Reflect v7.2.4228 Released (April 21, 2019) Download Changelog Spoiler: What's New - Bugfixes v7.2.4228 What's New v7.2.4228 - 21st April 2019 Image file loading speed improvement Reduced the time taken for Reflect to read the indexes back from the previous files in the backup set. This is most noticeable when reading a large number of remote files. Bug Fixes Change Block Tracker Fixed an issue where a TRIM operation on a Registry hive would cause a dead-lock if some third-party software was holding a lock on the Registry. Fixed an issue where CBT could not be enabled on some volumes if the list of file extents for the NTFS $LogFile spanned a 512 byte boundary. Image Guardian Fixed an issue on some Windows 7 systems, where MIG was prevented from using the Microsoft cryptographic functions. MIG could block the creation of SQL backups. This has been resolved. viBoot Creating an Incremental image of an encrypted/password protected image would fail with invalid password. This has been resolved.
