Solved Image your system with free Macrium

[whs]

I have been wondering if there is any significant value in upgrading from V4.2 (free) to V5 (free) at this stage. The pe disk isn't really an issue.
Any opinions?

I agree. If it ain't broke, don't fix it. 4.2 works, so why change.

For the moment perhaps, but will support be dropped for 4.2 in the future?

Probably, but I will cross this bridge when we get to it.

 

[kado897]

I agree. If it ain't broke, don't fix it. 4.2 works, so why change.

For the moment perhaps, but will support be dropped for 4.2 in the future?

Probably, but I will cross this bridge when we get to it.

Perhaps its just me but I always like to be on the latest version of software that I use. Sure it has bitten me on the bum occasionally but it is usually worth it.

 

[Corazon]

Same here!

But v4.2 has been working extremely well for me, plus I had just paid to register it before 5.0 came out. (Doh!) Mainly because I wanted the WinPE disc rather than the Linux one.

I'll keep an eye on 5.0 ... someday when the time comes to migrate my Windows 7 system to a new computer, I'll probably upgrade to 5.0 Pro and take advantage of the "restore to dissimilar hardware" feature.

 

[glennc]

It is the Auto Verify option that is missing.

Hello kado897,
If I remember correctly the previous version with the page as shown in the above snippet didn't have auto verfiy, it had to be verified after the image was created. Now I don't even have that. Weird!
Glenn

Yes it has moved to the restore tab, which makes sense as there is a list of images there.
View attachment 179269

That is what I don't understand and concerns me. I found the verify on restore option. I am assuming this verifies that the system image restored is the same as the system image restored from. Not a bad idea. But what is concerning me is that I want the original system image verified with the original system, so I know the image is correct and the same as the original data. This is the option I can't find on v5.0, so I uninstalled it, and reinstalled v4.2 and verified the previous system image I had last stored last week with v5.0. Until I can get Macrium's response, or find the verification of the system image I am saving, I just don't feel comfortable. Like I said, this is the only function I use on Macrium so I don't know but so far v5.0 has nothing to offer me and actually looses a feature??
Thanks for responding and assisting!
Glenn

 

[kado897]

Hello kado897,
If I remember correctly the previous version with the page as shown in the above snippet didn't have auto verfiy, it had to be verified after the image was created. Now I don't even have that. Weird!
Glenn

Yes it has moved to the restore tab, which makes sense as there is a list of images there.
View attachment 179269

That is what I don't understand and concerns me. I found the verify on restore option. I am assuming this verifies that the system image restored is the same as the system image restored from. Not a bad idea. But what is concerning me is that I want the original system image verified with the original system, so I know the image is correct and the same as the original data. This is the option I can't find on v5.0, so I uninstalled it, and reinstalled v4.2 and verified the previous system image I had last stored last week with v5.0. Until I can get Macrium's response, or find the verification of the system image I am saving, I just don't feel comfortable. Like I said, this is the only function I use on Macrium so I don't know but so far v5.0 has nothing to offer me and actually looses a feature??
Thanks for responding and assisting!
Glenn

I think that all that Verify does is check the internal consistency of the image on disk. It is a stand alone function. I don't see how it can relate either to the source which may have changed or the target which does not exist yet.

 

[glennc]

Yes it has moved to the restore tab, which makes sense as there is a list of images there.
View attachment 179269

That is what I don't understand and concerns me. I found the verify on restore option. I am assuming this verifies that the system image restored is the same as the system image restored from. Not a bad idea. But what is concerning me is that I want the original system image verified with the original system, so I know the image is correct and the same as the original data. This is the option I can't find on v5.0, so I uninstalled it, and reinstalled v4.2 and verified the previous system image I had last stored last week with v5.0. Until I can get Macrium's response, or find the verification of the system image I am saving, I just don't feel comfortable. Like I said, this is the only function I use on Macrium so I don't know but so far v5.0 has nothing to offer me and actually looses a feature??
Thanks for responding and assisting!
Glenn

I think that all that Verify does is check the internal consistency of the image on disk. It is a stand alone function. I don't see how it can relate either to the source which may have changed or the target which does not exist yet.

Not quite following your terminology. Again it is just my guess, but I thought that the system image is created and then I would immediately verify it confirming that the system image was the same as the system that I just imaged. This I thought meant there was no, say corruption or difference between the saved image and the actual files and structure.
Then I thought the verify on restore would restore the system image and check it against the saved system image so as to check for corruption or differences.
I could be totally wrong, but that has been my take on it. I want to know that the system image I just made is exactly the same as the original file it imaged. Thus I know that the system image is the exact same as the system that I may have to restore. I don't want to hope the system image that I just did, might or might not be the same as the system files and structure, until I need to do a restore. Then find out that it was corrupted and I can't restore the system image to my computer with such a catastrophic disaster as to require a system image restore.
Am I making any sense or am I on the wrong track?
Glenn

 

[kado897]

That is what I don't understand and concerns me. I found the verify on restore option. I am assuming this verifies that the system image restored is the same as the system image restored from. Not a bad idea. But what is concerning me is that I want the original system image verified with the original system, so I know the image is correct and the same as the original data. This is the option I can't find on v5.0, so I uninstalled it, and reinstalled v4.2 and verified the previous system image I had last stored last week with v5.0. Until I can get Macrium's response, or find the verification of the system image I am saving, I just don't feel comfortable. Like I said, this is the only function I use on Macrium so I don't know but so far v5.0 has nothing to offer me and actually looses a feature??
Thanks for responding and assisting!
Glenn

I think that all that Verify does is check the internal consistency of the image on disk. It is a stand alone function. I don't see how it can relate either to the source which may have changed or the target which does not exist yet.

Not quite following your terminology. Again it is just my guess, but I thought that the system image is created and then I would immediately verify it confirming that the system image was the same as the system that I just imaged. This I thought meant there was no, say corruption or difference between the saved image and the actual files and structure.
Then I thought the verify on restore would restore the system image and check it against the saved system image so as to check for corruption or differences.
I could be totally wrong, but that has been my take on it. I want to know that the system image I just made is exactly the same as the original file it imaged. Thus I know that the system image is the exact same as the system that I may have to restore. I don't want to hope the system image that I just did, might or might not be the same as the system files and structure, until I need to do a restore. Then find out that it was corrupted and I can't restore the system image to my computer with such a catastrophic disaster as to require a system image restore.
Am I making any sense or am I on the wrong track?
Glenn

As I say you can verify an image well after it has been created so the original data may be completely different to the current state of the source disk so cannot be relying on checking the image against that. Similarly it cannot check against a disk that has not yet been restored. There is an autoverify option in the paid version which runs just after the backup. I have not determined whether that rechecks the image against the source disk but I suspect not.

 

[glennc]

I think that all that Verify does is check the internal consistency of the image on disk. It is a stand alone function. I don't see how it can relate either to the source which may have changed or the target which does not exist yet.

Not quite following your terminology. Again it is just my guess, but I thought that the system image is created and then I would immediately verify it confirming that the system image was the same as the system that I just imaged. This I thought meant there was no, say corruption or difference between the saved image and the actual files and structure.
Then I thought the verify on restore would restore the system image and check it against the saved system image so as to check for corruption or differences.
I could be totally wrong, but that has been my take on it. I want to know that the system image I just made is exactly the same as the original file it imaged. Thus I know that the system image is the exact same as the system that I may have to restore. I don't want to hope the system image that I just did, might or might not be the same as the system files and structure, until I need to do a restore. Then find out that it was corrupted and I can't restore the system image to my computer with such a catastrophic disaster as to require a system image restore.
Am I making any sense or am I on the wrong track?
Glenn

As I say you can verify an image well after it has been created so the original data may be completely different to the current state of the source disk so cannot be relying on checking the image against that. Similarly it cannot check against a disk that has not yet been restored. There is an autoverify option in the paid version which runs just after the backup. I have not determined whether that rechecks the image against the source disk but I suspect not.

I don't know if I am making myself clear, sorry. With 4.2 as soon as the system image is finished, still in the program(Macrium), I chose the verify system image and did it immediately, before doing anything else. This is what I can't do in v5.0. Now I believe that, what you are saying is that this procedure is not the same as the autoverify?
Glenn

 

[kado897]

Not quite following your terminology. Again it is just my guess, but I thought that the system image is created and then I would immediately verify it confirming that the system image was the same as the system that I just imaged. This I thought meant there was no, say corruption or difference between the saved image and the actual files and structure.
Then I thought the verify on restore would restore the system image and check it against the saved system image so as to check for corruption or differences.
I could be totally wrong, but that has been my take on it. I want to know that the system image I just made is exactly the same as the original file it imaged. Thus I know that the system image is the exact same as the system that I may have to restore. I don't want to hope the system image that I just did, might or might not be the same as the system files and structure, until I need to do a restore. Then find out that it was corrupted and I can't restore the system image to my computer with such a catastrophic disaster as to require a system image restore.
Am I making any sense or am I on the wrong track?
Glenn

As I say you can verify an image well after it has been created so the original data may be completely different to the current state of the source disk so cannot be relying on checking the image against that. Similarly it cannot check against a disk that has not yet been restored. There is an autoverify option in the paid version which runs just after the backup. I have not determined whether that rechecks the image against the source disk but I suspect not.

I don't know if I am making myself clear, sorry. With 4.2 as soon as the system image is finished, still in the program(Macrium), I chose the verify system image and did it immediately, before doing anything else. This is what I can't do in v5.0. Now I believe that, what you are saying is that this procedure is not the same as the autoverify?
Glenn

I don't know. I have just posted the question in the Macrium Forum so we will see what they say.

 

[glennc]

As I say you can verify an image well after it has been created so the original data may be completely different to the current state of the source disk so cannot be relying on checking the image against that. Similarly it cannot check against a disk that has not yet been restored. There is an autoverify option in the paid version which runs just after the backup. I have not determined whether that rechecks the image against the source disk but I suspect not.

I don't know if I am making myself clear, sorry. With 4.2 as soon as the system image is finished, still in the program(Macrium), I chose the verify system image and did it immediately, before doing anything else. This is what I can't do in v5.0. Now I believe that, what you are saying is that this procedure is not the same as the autoverify?
Glenn

I don't know. I have just posted the question in the Macrium Forum so we will see what they say.

What a great idea!!! Please let me know what you find out. Much appreciated!
Glenn

 

[kado897]

I don't know if I am making myself clear, sorry. With 4.2 as soon as the system image is finished, still in the program(Macrium), I chose the verify system image and did it immediately, before doing anything else. This is what I can't do in v5.0. Now I believe that, what you are saying is that this procedure is not the same as the autoverify?
Glenn

I don't know. I have just posted the question in the Macrium Forum so we will see what they say.

What a great idea!!! Please let me know what you find out. Much appreciated!
Glenn

It seems I was both right and wrong. The Image is verified against MD5 Checksums created at the time of the backup and stored in an index in the backup.

I was pointed to this article. Understanding Image Verification Failures (Verification)

 

[glennc]

I don't know. I have just posted the question in the Macrium Forum so we will see what they say.

What a great idea!!! Please let me know what you find out. Much appreciated!
Glenn

It seems I was both right and wrong. The Image is verified against MD5 Checksums created at the time of the backup and stored in an index in the backup.

I was pointed to this article. Understanding Image Verification Failures (Verification)

Okay, lets see if I understand this. In the paid for version with the AutoVerify function, after the system image is completed it is read back and verified for corruption with the checksum. Is this the same process as in v4.2 free edition without autoverify, when I did the save system image and then immediately did the verify system image? I don't have a paid license key so I can't get on their forum.
Appreciate any assistance in answering that question. Now I can see the value of also having a restore system image verify.
Thanks
Glenn

 

[kado897]

What a great idea!!! Please let me know what you find out. Much appreciated!
Glenn

It seems I was both right and wrong. The Image is verified against MD5 Checksums created at the time of the backup and stored in an index in the backup.

I was pointed to this article. Understanding Image Verification Failures (Verification)

Okay, lets see if I understand this. In the paid for version with the AutoVerify function, after the system image is completed it is read back and verified for corruption with the checksum. Is this the same process as in v4.2 free edition without autoverify, when I did the save system image and then immediately did the verify system image? I don't have a paid license key so I can't get on their forum.
Appreciate any assistance in answering that question. Now I can see the value of also having a restore system image verify.
Thanks
Glenn

It would seem that both Autoverify and the separate Verify function do the same thing and that is verify the image written against the the index of the image which contains knowledge (MD5 Checksums) of the original data that was backed up. I don't think that this has changed since 4.2.

 

[Corazon]

That's great to know, thanks for sharing kado897

 

[glennc]

It seems I was both right and wrong. The Image is verified against MD5 Checksums created at the time of the backup and stored in an index in the backup.

I was pointed to this article. Understanding Image Verification Failures (Verification)

Okay, lets see if I understand this. In the paid for version with the AutoVerify function, after the system image is completed it is read back and verified for corruption with the checksum. Is this the same process as in v4.2 free edition without autoverify, when I did the save system image and then immediately did the verify system image? I don't have a paid license key so I can't get on their forum.
Appreciate any assistance in answering that question. Now I can see the value of also having a restore system image verify.
Thanks
Glenn

It would seem that both Autoverify and the separate Verify function do the same thing and that is verify the image written against the the index of the image which contains knowledge (MD5 Checksums) of the original data that was backed up. I don't think that this has changed since 4.2.

Thanks you Sir. I can sleep soundly with knowing that my saved system image is verified in v4.2. Why did they remove it from free v5.0???? For me it makes v5.0 kinda useless. I purchased Paragon a ways back when it was on sale and it had the Winpe recovery disk and the seperate verify function. I also (paranoid) will occasionally make a complete system image with Macrium. I have the space and I like having a seperate way of getting back to a working state. Paragon has some issues with my computer that I can work around. For some reason the computer keeps swapping my two hard drives back and forth between drive 0 and drive 1. You have to keep an eye on it so you don't image the backup drive to the C: drive.
Then it also says that both of my drives are bootable system drives after I did a reinstall from the hardrive instead of the recovery disk. Their support act as if I am talking a foreign language and have never responded directly to these issues. So I was considering Macrium 5.0 and maybe get the pro version. But if it ain't completely broke, don't fix it. I am not impressed with Macrium 5.0 and it's issue.
Many thanks!
Glenn

 

[kado897]

Okay, lets see if I understand this. In the paid for version with the AutoVerify function, after the system image is completed it is read back and verified for corruption with the checksum. Is this the same process as in v4.2 free edition without autoverify, when I did the save system image and then immediately did the verify system image? I don't have a paid license key so I can't get on their forum.
Appreciate any assistance in answering that question. Now I can see the value of also having a restore system image verify.
Thanks
Glenn

It would seem that both Autoverify and the separate Verify function do the same thing and that is verify the image written against the the index of the image which contains knowledge (MD5 Checksums) of the original data that was backed up. I don't think that this has changed since 4.2.

Thanks you Sir. I can sleep soundly with knowing that my saved system image is verified in v4.2. Why did they remove it from free v5.0???? For me it makes v5.0 kinda useless. I purchased Paragon a ways back when it was on sale and it had the Winpe recovery disk and the seperate verify function. I also (paranoid) will occasionally make a complete system image with Macrium. I have the space and I like having a seperate way of getting back to a working state. Paragon has some issues with my computer that I can work around. For some reason the computer keeps swapping my two hard drives back and forth between drive 0 and drive 1. You have to keep an eye on it so you don't image the backup drive to the C: drive.
Then it also says that both of my drives are bootable system drives after I did a reinstall from the hardrive instead of the recovery disk. Their support act as if I am talking a foreign language and have never responded directly to these issues. So I was considering Macrium 5.0 and maybe get the pro version. But if it ain't completely broke, don't fix it. I am not impressed with Macrium 5.0 and it's issue.
Many thanks!
Glenn

It isn't completely removed in v5. The autoverify is removed but the stand alone verify function which does the same thing is on the restore tab.

 

[glennc]

It would seem that both Autoverify and the separate Verify function do the same thing and that is verify the image written against the the index of the image which contains knowledge (MD5 Checksums) of the original data that was backed up. I don't think that this has changed since 4.2.

Thanks you Sir. I can sleep soundly with knowing that my saved system image is verified in v4.2. Why did they remove it from free v5.0???? For me it makes v5.0 kinda useless. I purchased Paragon a ways back when it was on sale and it had the Winpe recovery disk and the seperate verify function. I also (paranoid) will occasionally make a complete system image with Macrium. I have the space and I like having a seperate way of getting back to a working state. Paragon has some issues with my computer that I can work around. For some reason the computer keeps swapping my two hard drives back and forth between drive 0 and drive 1. You have to keep an eye on it so you don't image the backup drive to the C: drive.
Then it also says that both of my drives are bootable system drives after I did a reinstall from the hardrive instead of the recovery disk. Their support act as if I am talking a foreign language and have never responded directly to these issues. So I was considering Macrium 5.0 and maybe get the pro version. But if it ain't completely broke, don't fix it. I am not impressed with Macrium 5.0 and it's issue.
Many thanks!
Glenn

It isn't completely removed in v5. The autoverify is removed but the stand alone verify function which does the same thing is on the restore tab.

I've got to get this clarified once again, because of my misunderstanding of the full process. From your statement, you are, I believe saying that I could do a full system image, then go to the Restore tab and do a verification of checksum of the image and the original files, and find out that they are not corrupted. I don't have to be running a restore, it is just moved to that tab and functions exactly the same as the v4.2 verify function I used previously. Sorry to make you say it slowly, but I won't understand otherwise!
Once again thanks
Glenn

 

[kado897]

Thanks you Sir. I can sleep soundly with knowing that my saved system image is verified in v4.2. Why did they remove it from free v5.0???? For me it makes v5.0 kinda useless. I purchased Paragon a ways back when it was on sale and it had the Winpe recovery disk and the seperate verify function. I also (paranoid) will occasionally make a complete system image with Macrium. I have the space and I like having a seperate way of getting back to a working state. Paragon has some issues with my computer that I can work around. For some reason the computer keeps swapping my two hard drives back and forth between drive 0 and drive 1. You have to keep an eye on it so you don't image the backup drive to the C: drive.
Then it also says that both of my drives are bootable system drives after I did a reinstall from the hardrive instead of the recovery disk. Their support act as if I am talking a foreign language and have never responded directly to these issues. So I was considering Macrium 5.0 and maybe get the pro version. But if it ain't completely broke, don't fix it. I am not impressed with Macrium 5.0 and it's issue.
Many thanks!
Glenn

It isn't completely removed in v5. The autoverify is removed but the stand alone verify function which does the same thing is on the restore tab.

I've got to get this clarified once again, because of my misunderstanding of the full process. From your statement, you are, I believe saying that I could do a full system image, then go to the Restore tab and do a verification of checksum of the image and the original files, and find out that they are not corrupted. I don't have to be running a restore, it is just moved to that tab and functions exactly the same as the v4.2 verify function I used previously. Sorry to make you say it slowly, but I won't understand otherwise!
Once again thanks
Glenn

No problem Glenn. You are correct in you assumption.

 

[glennc]

Thank you once again! Now I don't know if it is worth upgrading, again. What is your opinion, of course, if you don't mind?
Glenn

 

[kado897]

It is a matter of personal choice really. If you are happy with 4.2 then stick with it until Macrium drops support for it. I think I said in an earlier answer that I generally like to use the latest versions of software that I use as I am then certain of continuing support and can take advantage of any new features. In this case there don't seem to be many new features that are applicable to the free version except for the creation of a PE disk from the WAIK. It was to get a PE disk that I originally bought v4. If the Linux disk can see your backup drives or you can use the PE version in the Hirens boot CD then that is no real advantage.