http://www.google.com/#hl=en&source=hp&q=vhd&aq=f&aqi=g10&oq=&fp=b36c7832dbb01be6
VHD, I think is the best thing about Windows 7 that nobody talks or even know about. This not only is a great OS backup tool but you can even boot from it on the fly. Because it's so damn great, I even find it strange why people are still using programs such as Ghost, TrueImage...etc.
VHD alone is such a great backup solution and it gets even better with Differencing VHD solution.
How does differencing VHD work?
Imagine this situation.
You installed Windows, installed updates, important programs, tools, and what-not. Then you make parent VHD of this OS because if shit happens, you can always go back to this one. However, in time, you install more programs, tools, codecs, and anything. You could make another VHD of this but doing so would take more space, time, and effort. Even worse, you're not even sure if this stage of OS is worth keeping it.
In that case, you just make child image of it (Trueimage has something alike). Simply put, it works as a layer and you can either keep this layer or nuke it to go back to the ideal stage. And, of course, you get to choose which one to boot from. So, instead of backing up 30GB of OS then to loading that 30GB of OS only to start over, you can simply delete a few GB or even MB of layered VHD to go back. If you like the layer, you can also merge it to the parent VHD.
Possible usage scenario:
1. Parent VHD file created after installing Windows + drivers + updates + tweaks + crucial programs. (Usually 25+GB thanks to massive Adobe CS4 suite)
2. Child VHD created. (100K + anything you install from this point)
3. Backup of child VHD (100K)
After that you boot from child VHD and everything you do is saved on that child VHD. In other words, parent VHD doesn't get altered. After a while, you realize your Windows is currupted. It could be all those residues of programs you once used then erased, it could be codec curruptions, it could be driver conflicts...etc. It's inevitable you install Windows from scratch. Or, you could bring back image file you created with Ghost, TrueImage, or Windows' own backup solution. This takes time but with VHD, you only need to reboot the system, delete second child VHD then use 3rd fresh child VHD.
How about this? All the updates patches or programs you installed in parent VHD gets outdated. With VHD, you boot from parent VHD once, update everything, and that's it. Now you boot from child VHD and everything is updated as parent VHD is updated. Very simple, isn't it? Now, think about doing that in other image solution such as Ghost and TrueImage.
What more can I say? Think about possibilites you can do with it. I highly recommand it!
EDIT: To clarify misunderstandings and confusions, I'll add a few facts.
1. Although VHD is widely used as a part of VPC solution, people, even experts like JackMDS, seem to think VHD is tied to VPC. This is wrong.
My method does NOT make your PC to run as VPC. There's no hardware emulation and your GPU is not treated as an aged S3 graphics card. You can install, update all the drivers and all the hardware components run as they're supposed to run.
Simply put, when you boot using VHD file, it's just like booting from a physical HDD. It's NOT like running Windows 7 VPC on top of regular Windows 7.
2. VHD files are treated as physical HDDs, thus the name VHD.
3. Limitations: You can't use BitLocker Drive Encryption. You can't use Hibernate function. Windows' own swap file can't be stored on VHD. Also, there's supposed to be 1-3% HDD performance hit though I never felt it.
4. Windows' own System Imaging Backup solution makes use of VHD, though once it's restored, it's not treated as VHD. You can also boot from this VHD file Windows backup solution made by manually attaching boot information; just like VHD files you create your own.
5. A few helpful links to get you started:
http://community.dynamics.com/blogs/cesardalatorre/comments/15471.aspx
http://community.dynamics.com/blogs/cesardalatorre/comments/15471.aspx
http://blogs.msdn.com/knom/archive/2009/04/07/windows-7-vhd-boot-setup-guideline.aspx
http://blogs.technet.com/aviraj/arc...-7-boot-from-vhd-first-impression-part-1.aspx
update: http://www.windows7hacker.com/index.php/2009/05/native-vhd-boot-to-windows-7/
6. Please keep in mind JackMDS thinks VHD=VPC so the confusion we have here. To save yourself from confusions, please disregard what JackMDS says here.
VHD, I think is the best thing about Windows 7 that nobody talks or even know about. This not only is a great OS backup tool but you can even boot from it on the fly. Because it's so damn great, I even find it strange why people are still using programs such as Ghost, TrueImage...etc.
VHD alone is such a great backup solution and it gets even better with Differencing VHD solution.
How does differencing VHD work?
Imagine this situation.
You installed Windows, installed updates, important programs, tools, and what-not. Then you make parent VHD of this OS because if shit happens, you can always go back to this one. However, in time, you install more programs, tools, codecs, and anything. You could make another VHD of this but doing so would take more space, time, and effort. Even worse, you're not even sure if this stage of OS is worth keeping it.
In that case, you just make child image of it (Trueimage has something alike). Simply put, it works as a layer and you can either keep this layer or nuke it to go back to the ideal stage. And, of course, you get to choose which one to boot from. So, instead of backing up 30GB of OS then to loading that 30GB of OS only to start over, you can simply delete a few GB or even MB of layered VHD to go back. If you like the layer, you can also merge it to the parent VHD.
Possible usage scenario:
1. Parent VHD file created after installing Windows + drivers + updates + tweaks + crucial programs. (Usually 25+GB thanks to massive Adobe CS4 suite)
2. Child VHD created. (100K + anything you install from this point)
3. Backup of child VHD (100K)
After that you boot from child VHD and everything you do is saved on that child VHD. In other words, parent VHD doesn't get altered. After a while, you realize your Windows is currupted. It could be all those residues of programs you once used then erased, it could be codec curruptions, it could be driver conflicts...etc. It's inevitable you install Windows from scratch. Or, you could bring back image file you created with Ghost, TrueImage, or Windows' own backup solution. This takes time but with VHD, you only need to reboot the system, delete second child VHD then use 3rd fresh child VHD.
How about this? All the updates patches or programs you installed in parent VHD gets outdated. With VHD, you boot from parent VHD once, update everything, and that's it. Now you boot from child VHD and everything is updated as parent VHD is updated. Very simple, isn't it? Now, think about doing that in other image solution such as Ghost and TrueImage.
What more can I say? Think about possibilites you can do with it. I highly recommand it!
EDIT: To clarify misunderstandings and confusions, I'll add a few facts.
1. Although VHD is widely used as a part of VPC solution, people, even experts like JackMDS, seem to think VHD is tied to VPC. This is wrong.
My method does NOT make your PC to run as VPC. There's no hardware emulation and your GPU is not treated as an aged S3 graphics card. You can install, update all the drivers and all the hardware components run as they're supposed to run.
Simply put, when you boot using VHD file, it's just like booting from a physical HDD. It's NOT like running Windows 7 VPC on top of regular Windows 7.
2. VHD files are treated as physical HDDs, thus the name VHD.
3. Limitations: You can't use BitLocker Drive Encryption. You can't use Hibernate function. Windows' own swap file can't be stored on VHD. Also, there's supposed to be 1-3% HDD performance hit though I never felt it.
4. Windows' own System Imaging Backup solution makes use of VHD, though once it's restored, it's not treated as VHD. You can also boot from this VHD file Windows backup solution made by manually attaching boot information; just like VHD files you create your own.
5. A few helpful links to get you started:
http://community.dynamics.com/blogs/cesardalatorre/comments/15471.aspx
http://community.dynamics.com/blogs/cesardalatorre/comments/15471.aspx
http://blogs.msdn.com/knom/archive/2009/04/07/windows-7-vhd-boot-setup-guideline.aspx
http://blogs.technet.com/aviraj/arc...-7-boot-from-vhd-first-impression-part-1.aspx
update: http://www.windows7hacker.com/index.php/2009/05/native-vhd-boot-to-windows-7/
6. Please keep in mind JackMDS thinks VHD=VPC so the confusion we have here. To save yourself from confusions, please disregard what JackMDS says here.
Last edited: