Image your system with free Macrium

[QUOTE=alan10;2594272]

eldinv said:

When I double the big image it tells me the image is part of a multi-part image.

/QUOTE]
I get exactly the same error message if I change the backup extension from MRIMG to BIN.

I strongly suspect that if I deleted or uninstalled Macrium Reflect, or if I lost it by using CopyWipe,
Then all I would get are error messages - Neither Windows nor the MRIMG backup would have the intelligence to browse or restore a backup file.

To browse or restore a backup file you need Macrium to be installed, or to be running a Macrium Boot Rescue CD.

It looks like you have set a maximum image size and it has split it into more than one file.

alan10 said:

mjf said:

Accepting that some people want to use the Macrium clone capability, it may be useful to document any potential problems.

This one is a doozie.

What's the doozie?

On a later comment... Using Windows inbuilt imaging or Macrium it is safe to copy out files from a mounted image but of course don't alter the image. When moving images you need to be clear what you mean by "move". Moving within a partition is a directory (file system) entry change and I have never experienced a problem. Moving across partition boundaries is a physical move and I would not recommend it.

alan10 said:

mjf said:

alan10 said:

This one is a doozie.

What's the doozie?

On a later comment... Using Windows inbuilt imaging or Macrium it is safe to copy out files from a mounted image but of course don't alter the image. When moving images you need to be clear what you mean by "move". Moving within a partition is a directory (file system) entry change and I have never experienced a problem. Moving across partition boundaries is a physical move and I would not recommend it.

What does doozy mean? doozy Definition. Meaning of doozy. OnlineSlangDictionary.com

Macrium expects all Incremental and Differential backups to reside in the same folder as their corresponding FULL backup. You can move the folder with no problems.
If you move only some of the backups to a different folder then expect trouble,
but this is POSSIBLY mitigated if the Windows Service "Distributed Link Tracking Client" is running at the time the moving is performed.

I'll clarify. I am talking about one of (NOT incremental or differential) images - (made by Windows imaging and Macrium free. Macrium free is what the sticky is about).
Singling out my comment as a doozy (doozie your spelling) makes an unnecessary comment. Let me make it simple. There appear to be some concerns with Macrium cloning. If so then this a good place to document them.

You could give THIS a try. It will attempt a file level restore from a corrupted image

LF. a flash drive works. I have done it.

LF is right. Macrium recovery does not care from where the image comes as long as you can properly point to it. This is not Windows imaging where moving an image would be fatal.

whs said:

LF is right. Macrium recovery does not care from where the image comes as long as you can properly point to it. This is not Windows imaging where moving an image would be fatal.

I save my images to an internal HDD and then copy/move them to an external HDD.

When I only had the Linux Restore Disc, I discovered that it would not recognise my external HDD (i.e. I could not browse to it, as it didn't appear in the file browser).

I have moved an image from an internal HDD to an external HDD and back to an internal HDD again and successfully restored using that image.