Macrium reflect full verified image restore error

Topic

New Reply

(Hope this is the correct place for this question.)

I have three almost identical laptops with Win 7 on two, and win 10 on the other. I use the latest version of Macrium to image them before applying patches. I do a FULL backup WITH verification for them.

While in the process of doing an image backup for one of them, I was in the restore tab of Macrium (where it starts up) and was looking through previous full verified images when I noticed that one had a triangle with an exclamation point in it (indicating an error).

When I investigated further, Macrium reported that the error was something like it could not find the final file of a multi backup set. I don’t use that. I always do a FULL backup with most of the default settings — except for ticking the verification box and adding a comment.

I explored other images, and found ANOTHER that had the same error indicator.

Wary of what might be going on, for the next backup, right after completing it, I went to the restore tab and picked the full, verified, image I had just created, and it showed that error. I duplicated my backup routine once more to get another full, verified, image, and that one did not show an error, so I think (hope) I have a good backup image I could restore.

My new process is to do a full image with verify, and immediately check in the restore tab if Macrium restore thinks the image is ok too.

Has anyone observed anything like this with their Macrium images? It has happened on at least two laptops, but I BU all three machines to the one external drive (thinking full verification is adequate) so I don’t have other BU hardware to compare.

I haven’t put anything out on the Macrium site, thinking I would start here first.

Any thoughts or observations appreciated.

Chris

Reply | Quote

Replies

If you can slip dual SSD into your laptop, or wire a second remotely you can avoid the insane hassle of f****** backups. what a drag compared to simply mirroring. At SSD speed full 100gig bakup mirror takes 20 minutes. thats my defence against window c***Ware updates

be well, breathe and honor wabi sabi

Reply | Quote

Best to use external drive- virus/malware/ransomware will get both(all) if connected at time of infection. 20 min is all it takes for imaging mine so no time lost when imaging. Quarantine is the name of the game these days.

Just an observation

Reply | Quote

[Bundaburra]

I have been using Macrium (free version) for years, and have never seen what you describe.  I do full backups on a regular basis, always with verification, and only once over the years has a backup finished with a “verification failed” message.  On that occasion I ran the same backup again, and it verified OK.  My backups go to a dedicated external drive, which is only connected when doing backups or restores, but I checked it just now and all the .mrimg backup files on it are apparently good.  On the odd occasion when I have needed to restore, either a full image or individual files, it has always worked correctly.  Do you have the latest version?   (Other tasks > check for updates).  Maybe your external drive is faulty?  Check if it is fragmented?  Run CHKDSK /F on it, and any other diagnostic tools you may have.   Look for other possible causes, before blaming Macrium

Windows 10 Pro 64 bit 20H2

• This reply was modified 4 years, 11 months ago by Bundaburra.

1 user thanked author for this post.

cmptrgy

Reply | Quote

Thanks for your response.

Sorry if it seemed like I was blaming Macrium; not my intent.

I was looking for just that kind of suggestion you made (to check the media — although there are many good images on it), but also trying to understand the Macrium process too.

My thought being that the verification right after the imaging is an integrity check of what has been imaged, and if the verification passes, I thought Macrium would be happy with the image file.

But then immediately using Macrium to get ready to get ready to restore and there seems to be something wrong with the integrity of something just verified puzzles me, and I don’t have an explanation for it in how that might happen — unless the image is not really “closed” and then “reopened” for verification? And then gets really closed once the verification happens?

I will check the external drive, but it is still puzzling to me. [It is also a dedicated BU drive; and as you experienced, Macrium can indicate a verification error too — but then you know something is amiss. Verifying successfully and then indicating a different kind of error is still puzzling.]

Chris

1 user thanked author for this post.

DriftyDonN

Reply | Quote