Solved Validating or verifying an image

betaupsilon

New member
Local time
6:47 AM
Messages
179
Hi all,
I used this tutorial (http://www.sevenforums.com/tutorials/24771-system-image-extract-files-using-disk-management.html?) to create a VHD of the image of my system. It worked quite easily. However, I wanted to compare that image against the source partition. I used WINMERGE to do the comparison, but the results were somewhat confusing because 1) there were a number of aborted attempts, & 2) the current system from which the image was created is in a constant state of flux as the computer is being used; hence, there will be system & Appdata files that have changed since the image was created.

Is there a better tool or procedure to gain confidence in the image other than actually doing a full restoration?
 

My Computer

Computer type
PC/Desktop
OS
Windows 7 Home Prem 32 bit
I use another product to make images, not Windows--but:

I wouldn't put a lot of faith in whatever verification or validation scheme you come up with. That is, I would not assume that "perfect" verification or "perfect" validation meant that I could be positive of a successful outcome if I ever needed to restore an image in a critical situation.

I'd put more faith in a test restoration. Not only because that may provide confidence that you have a restorable image, but also because doing a test will familiarize you with the restoration procedure and its choices.

Imaging is a complex process and it seems other things, perhaps never identifiable, can go wrong and defeat a successful restore. You can easily find instances where restoration failed with no explanation to be found.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Ignatz Special; 4 speed manual gearbox; factory air conditioning; one of one
OS
Windows 7 Home Premium SP1, 64-bit
CPU
Intel Skylake i5-6600K, not overclocked
Motherboard
AsRock Z170M Extreme 4, micro ATX
Memory
8 GB HyperX DDR4-2666 (2 x 4 GB)
Graphics Card(s)
none; graphics are integrated on CPU
Sound Card
onboard: Realtek ALC1150; external: USB Behringer UF0-202
Monitor(s) Displays
Dell S2340M 23 inch IPS
Screen Resolution
1600 x 900
Hard Drives
System: Crucial MX100 series SSD, 128 GB;
Data: Samsung Spinpoint 103SJ, 1 TB;
Backup: WD Caviar Green WD30EZRX-00D8PB0, 3 TB
PSU
Rosewill SilentNight 500 watt fanless, semi-modular
Case
Antec Solo II
Cooling
Noctua NH-U12S; Noctua F12 intake, Noctua S12A exhaust
Keyboard
Microsoft 200 6JH-00001 USB
Mouse
Dell or Microsoft optical wired; USB
Antivirus
Microsoft Security Essentials and Malwarebytes Premium
Browser
Pale Moon
Other Info
All fans PWM; speeds at idle: CPU circa 500 rpm; intake circa 600 rpm; exhaust circa 600 rpm; CPU temps 27 idle and 47 C load in a warm room (27 C/81 F) when running Intel Extreme Tuning Utility stress test.
I use another product to make images, not Windows--but:

I wouldn't put a lot of faith in whatever verification or validation scheme you come up with. That is, I would not assume that "perfect" verification or "perfect" validation meant that I could be positive of a successful outcome if I ever needed to restore an image in a critical situation.

I'd put more faith in a test restoration. Not only because that may provide confidence that you have a restorable image, but also because doing a test will familiarize you with the restoration procedure and its choices.

Imaging is a complex process and it seems other things, perhaps never identifiable, can go wrong and defeat a successful restore. You can easily find instances where restoration failed with no explanation to be found.

ignatzatsonic: What you say is entirely correct, but it would be nice to have an alternative & I think I have found one.

Attempting to verify an image against its source is tricky because 2 sticky impediments will hinder the process. The first is UAC priviledges. WINDOWS will fight every step into scanning into protected directories such as \Windows\System32. The 2nd is while attempting to do the comparison while logged into the very system of the source drive the system acts almost as a living entity. During the process many system files are open and constantly changing.

What I have found is BEYOND COMPARE can operate within the WIN-PE mode. This circumvents the impediments previously discussed. To use this tool you want to mount the VHD file of your image via command prompt per Windows 7: Virtual Hard Drive VHD File - Create and Start with at Boot. Now BEYOND COMPARE can be run if installed on a USB flash drive to compare the VHD against the source system drive.

Maybe someone will find this handy as well.
 

My Computer

Computer type
PC/Desktop
OS
Windows 7 Home Prem 32 bit
Back
Top