I'm curious to know how a backup facility like Macrium Reflect can image a system which is running and is constantly changing. Even if I leave Reflect to get on with its job without my changing any of my user data (e.g by imaging overnight)the system is constantly metamorphosing because, for example, Windows Update runs automatically, as do other packages such as antivirus and Adobe Flash to name just a few.
Some backup systems deal with this by running the backup software from an external bootable carrier (e.g. a bootable Linux CD)so that Windows isn't running during the imaging process.
I guess that Reflect has some way of detecting and dealing with changes which take place during the imaging process. How does it do this ? Or is it a proprietary secret ?
Thank you very much. That's exactly what I wanted to know and, if I may say so, the blog entry is easily readable and the graphics are very good. Furthermore, the idea of collating info from sources such as forum entries into one clear text is superb. I only wish the same paradigm were used elsewhere. You set yourselves apart from at least one big-name backup product which has abandoned its support forum to its users and is now basing its support on the YOYO paradigm (You're On Your Own, bud). Which is one reason why I migrated to Macrium Reflect.