Imaging with free Macrium

Hi all,

I just completed my first try at using Macrium Free.

First, to member WHS for linking the ISO download at this forum. I downloaded the WinPE ISO and burnt it to a CD so I didn't need to download the tool to my HDD.

Here's my info before posting my impressions as a first-time Macrium user:

- Windows 7 64-bit Home Premium
- Imaged full-disc mode from a SATA III 1 tb HDD to a USB 2.0 500g HDD.
- The 1 tb HDD is my everyday "C" HDD with the OS and all my data on the HDD, 2 partitions, Sys Reserved and the "main" partition, no customization of partitions, etc.
- Total size imaged from the 1 tb Source HDD: 376 gb
- Total size of the completed image folder/file on the Destination USB 500 gb HDD: 351 gb
- Macrium compression mode: "Medium"
- Total elapsed imaging time: 4 hrs
- Did not tick the "verify" option before starting the process. I wanted to shorten the full disc imaging elapsed time for the first-time use. I understand the recommendation to verify but this is all "learning-curve" activity as I don't need this image for recovery from any emergency situation.

I will test the Recovery step soon to verify that it's a complete bootable replacement HDD (same as a clone) once I recover to a spare HDD.

I'll compare to Acronis 2011 which I use regularly to clone my "C" HDD. I've run one full-disc image with Acronis but it's been a while since I used the Image tool with Acronis.

I liked Macruim's GUI vs Acronis with the Imaging portion of the 2 tools. The Cloning menus are similar and I like Acronis's cloning screen but I use it regularly so am familiar with it.

Macruim's Imaging setup steps, tick buttons, layout, are easier for me to prepare the Image than Acronis 2011. I found the setup process to be more straightforward and easier, for me, to understand the setup choices in preparing the image parameters.

The main thing that I was surprised at once the full-disc image completed, was the size of the image file, 351 gb.

I guess I had expected, with the "Medium" compression method selected, the image file to be approx. 50% of the size of the data on my 1 tb C HDD which is 376 gb.

Since I did image from a larger size HDD to a smaller HDD, I'm wondering if that's the reason the image file is about 93% size of the data on the 1 tb HDD.

Before I imaged with Macrium, I looked at some knowledge base info over at the Acronis Forum to refresh my memory about what they have published about imaging in general.

The parts that caught my eye over there were references to corrupt imaging issues, ie, the need to test all images to be sure that they're working spare recovery items for HDD-replacement scenarios.

The other thing I read was regarding incremental and differential imaging, referring to the same possibility of potentially corrupted files.

They mentioned that the "verify" step when Imaging wasn't sufficient to confirm a working recovery to one's HDD. In other words, they were saying that if one incremental image was corrupt in a chain, that would render that particular backup set (the full-disc initial image in conjunction with subsequent incremental or differential images in that backup set) unusable as a recovery to a HDD.

I was wondering how Macrium images rate with members here regarding testing reliability over time. ie, recovering and verifying a workable HDD from image set[s].

Since I don't have the paid version, I can't use the incremental or differential methods.

My primary goal though, is fulfilled with the free version as I'm wanting to keep 1 or 2 full-disc images for emergency use if I encounter any issues with my regular cloning using Acronis.

I've been cloning monthly with Acronis for about 2 years and haven't encountered any issues but I read over at the Acronis forum that the experienced members don't recommend cloning. They refer to other members encountering problems with the Source HDD when cloning but I've not seen any problems when I clone.

I don't understand that, since, unless I'm wrong about this, the Source HDD is only being read during the cloning process. I don't see how one can encounter an issue with the Source HDD, assuming no power or user interruptions, or other user errors when setting up the cloning process.

Has anyone cloned with Macruim? If so, what's been your experience with the cloning tool with Macruim?

I make at least two clones a week with Macrium Reflect. It's easy to do and I've never had a problem with it except when I made the mistake of also having Speccy running while making the clone (I was using it temporarily to monitor HDD temps while cloning); for some odd reason, they didn't play well together. The fix was easy; don't run Speccy while cloning. Two downsides of cloning are they take longer than imaging and take up the same amount of space as the original. The main advantage is the clone is bootable if it has an OS on it and data can be read directly from the disk.

I also use automatic verification when making images. I'm reasonably certain I can depend on that since I'm not making differential/incremental images. I do run test recoveries to a test drive when making a new recovery disk/USB stick to make sure they work but I don't need to that very often. Running verify after creating an image doubles the time required but, since it is automatic, I just start the image, then walk away until the computer

Lady Fitzgerald said:

I make at least two clones a week with Macrium Reflect. It's easy to do and I've never had a problem with it except when I made the mistake of also having Speccy running while making the clone (I was using it temporarily to monitor HDD temps while cloning); for some odd reason, they didn't play well together. The fix was easy; don't run Speccy while cloning. Two downsides of cloning are they take longer than imaging and take up the same amount of space as the original. The main advantage is the clone is bootable if it has an OS on it and data can be read directly from the disk.

I also use automatic verification when making images. I'm reasonably certain I can depend on that since I'm not making differential/incremental images. I do run test recoveries to a test drive when making a new recovery disk/USB stick to make sure they work but I don't need to that very often. Running verify after creating an image doubles the time required but, since it is automatic, I just start the image, then walk away until the computer

Thanks for the reply.

I have a couple of questions.

- You mentioned the 2 advantages with cloning vs imaging, one being that the clone is bootable. Since I ran my image selecting both partitions (Sys Reserved/MBR) and the main partition, my image will also be bootable after I run the Recovery pocess.

Do I have the right understanding of the above?

- The other thing that I wonder about is the total-time comparisons. When I clone with Acronis, it takes me about 35-40 minutes to clone my 1 tb HDD to my spare (1 tb) HDD.

The total time for my full-disc image with Macrium was 4 hrs.

So for me, assuming that the Macrium cloning process total time is approximately the same as Acronis cloning times, it would be faster for me to clone vs (full-disc) image.

There may be one caveat when comparing my cloning time. I always clone outside of Windows with my Acronis CD. Perhaps that's why my total time is faster than my image time.

btw, I have Speccy too. It's a great utility tool to have on one's PC.