If you're running an F&F backup AND an image backup because you believe an F&F backup is necessary in order to recover individual files and folders as opposed to restoring the entire system, that is not the case. Restore performance would likely be similar. In my tests on a file server's Data partition, an image backup ran 2.5x faster than an F&F backup.
Macrium reflect free edition 32 bit manual full#
And even if you don't care about full system recovery, an image backup will be significantly faster than an F&F backup when they're backing up the same data set, as would be the case if you're backing up the entire partition. If you expect to use that backup for system recovery purposes, it will not work properly in that context because restoring an F&F backup to certain areas of the C drive will break some file system techniques that Windows applies in various places, such as hard linking. But if you're performing F&F backups of your entire C drive, you absolutely do not want to be doing that, so if that IS what you're doing, then you have a much larger problem here. I must have automatically substituted "Looking for changes" when I read that originally, because "Determining files to copy" only occurs with F&F backups rather than image backups. You said you're backing up your C drive and Reflect is getting stuck on "Determining files to copy". So if you're going to stay behind on releases, I'd recommend at least keeping an eye on the release notes.īut I just noticed a big red flag in your earlier post. After all, the fact that backups are working perfectly does not always mean a restore will. Click to expand.I certainly understand not updating every time, although quickly reading over the release notes since 4063, which was released over a year ago now, there have been multiple bug fixes that could potentially be relevant to you, including some that affect restore/recovery scenarios.