The Storage Team Blog about file services and storage features in Windows Server, Windows XP, Windows Vista and Windows 7.
<This is the second post in a blog series on backup and recovery offerings in Windows 7. >
In the last post, we’ve briefly mentioned that Windows 7 offers both the ability to backup individual folders and to create a system image of your computer, and how they could be used to protect your personal and system files. In this post we’ll focus on system image backup to give you an in depth view on how the technology works, and how the configuration of your OS may affect the image and the implications during recovery.
What is a system image and how does it work?
Just as a brief recap, a system image is in essence a snapshot of an entire drive(s). The backup is done in block level (as opposed to file level) increments and includes all user and system files, configuration data and applications that are present on the drive, plus information regarding disk layout and boot entries. The image can be used to recover a working Windows if your hard disk ever fails, or if you simply want to reimage your OS to an earlier point in time.
During the first backup, the backup engine scans the source drive and copies only blocks that contain data into a .vhd file stored on the target, creating a compact view of the source drive. The next time a system image is created, only new and changed data is written to the .vhd file, and old data on the same block is moved out of the VHD and into the shadow copy storage area. Volume Shadow Copy Service is used to compute the changed data between backups, as well as to handle the process of moving the old data out to the shadow copy area on the target. This approach makes the backup fast (since only changed blocks are backed up) and efficient (since data is stored in a compact manner). When restoring the image, blocks will be restored to their original locations on the source disk. If you want to restore from an older backup, the engine reads from the shadow copy area and restores the appropriate blocks.
Creating a system image
As mentioned in the previous posts, when configuring Windows Backup, a system image is automatically included in the scheduled backup if the backup target is formatted with NTFS file system and has sufficient space. This system image contains only the critical drives that are required for Windows to operate. Examples of critical drives include system volume, boot (OS) volume, and the volume where the Windows Recovery Environment is installed (typically the same as boot volume on a default installation of Windows 7). As seen from the example below, the System Reserved drive, which is the system volume, and the C: drive that represents the boot volume are both included. The G: drive on the other hand, which is purely a data drive, is not included. To back up any data from G:\, you can select the drive or its folders from the tree view above to create a file-based backup.
Using the Windows Backup wizard above is the simplest way to protect your data and system, since the backups will be created automatically on a schedule. However if you want to create an advanced system image that also includes additional data drives on top of the critical drives, or if you want to save a custom system image to an alternate location (e.g. to a set of DVDs that you can easily carry with you on a trip), you can create such images on an ad hoc basis using the “Create a system image” task link on the Backup and Restore control panel.
The steps to create an advanced system image are very similar to creating the regular scheduled backup. First, select where you would like to save the image, which can be the same as or different from the target for the regular scheduled system image backup. Then you can select which drives should be included in the image. Some drives are selected by default since they are required for Windows to run and must be included in the image. However you are free to select any additional drives to include.
After a final confirmation of the source and the target, you are good to go.
Wbadmin.exe is the command line utility for creating system images and supports all functionalities available from the wizard and more. Using wbadmin and task scheduler together you can create advanced system image on a scheduled basis. For more information regarding the wbadmin subcommands, type “wbadmin help” from a command prompt or visit MSDN (note that some subcommands on MSDN are only available for Windows Server 2008 backup).
There are no differences in the system image created using a wizard or command line tool, and you will be able to restore the images using the same procedures (more on system image recovery in a later post). However, the configurations of your source and target disks do have implications on the ability to backup and restore the image. We’ll explore this some more in the next section.
Considerations while creating a system image
Since system image is a critical feature to ensure availability of your system and data after a disaster, it is important to understand how some of the advanced configuration on your system may affect your options during restore.
1. Choosing the backup target
System image is supported on internal\external disks, optical removable media, and network locations (Business edition or above). Aside from the usual tradeoffs when picking a storage location such as performance and reliability, here are some additional recommendations to consider for picking a system image backup target:
More information regarding differences between backup on hard disk, optical media and network locations can be found in Help and Support.
2. Configuration on the source disk(s)
When a system image is created, it captures the data of (at least) all critical drives on the source disks, and also information regarding the state of all disks and partitions that are present in the system in case partitions need to be recreated during restore. Therefore the layout of the disks at the time of backup will have implications on what is included in the backup and also the options available for restore.
3. Multiple machines environment or dual boot machine
If you have any questions regarding your specific configurations, do not hesitate to leave a comment or visit our forum for support.
-- Windows Backup team
Please elaborate further on "Do not store the image on a dynamic disk"!
This makes it impossible to create software raid!
Is this true?
Still no comparison to Acronis. No encryption for backups, no individual file\folder restore, no mounting images as a drive. Shame because quality backup\restore should be built into the OS.
If you store a system image on a dynamic disk, you can use the image for same disk restoration (i.e. no HDD replacement) where the disk partition layout is unchanged. However, if the disk is replaced, restore will not be supported. So to support the latter case, you’re correct that the backup target cannot be part of a software raid. We understand this limitation and will take this into consideration in future releases.
message: check your backup the file or directory is corrupted or unreadable
even same message after going back to original vista basic and cleaninstall windows 7 again.
system restore broken as well
what can be done?
Suggest to followup in windows forums for better traction.
Please run chkdisk /r on the disk and re-run the backup.
Thanks for the feedback. Let me answer all the questions:
1) You can use the bitlocker for encryption.
2) You can use File restore (restore my files) to restore individual files.
3) You can mount the vhd as virtual volume from disk manager.
More details can be found at "Recovering your files using windows 7" blog.
I have created a backup and system image, can I move the system image to a seperate drive as I do not want to create another one as the image was taken just after a clean install with all my programe and settings correct. So I dont want to re-do it and take up more space. Is this possible as at the moment it says it cant be moved as files are in use.
I am surprised to learn recently that incremental system image backup to network is not possible. Which makes Backup & Restore Center useless for my NAS. Why should be forced to have an external HDD? Is incremental system image backup supported if my map my network drive (assign a drive letter?)
> You can use File restore (restore my files) to restore individual files
Then is a System Image basically a superset of a data file backup? (In the case where all the data files are on the C: drive, say.) I think that's a good thing, but I'm puzzled by some of the documentation I've seen.
I am interested in keeping several system image backups that I can selectively restore as I want. For instance,
1. initial windows 7 upgrade
2. #1 + applications installed
3. #2 + user id's
4 #3 + data files
How would I go about creating and archiving different system image backups? Based upon how the shadow volume copy service works, I am confused on how to do this.
Thank you for the good description.
But (there had to be a "but", didn't there), the Windows 7 FAQ for "What backup settings should I use to maximize my disk space" states "By default, Windows automatically saves as many system images as it has free space for without taking up more than 30 percent of space on the backup disk."
I have an external drive I reserve for System Image backups. Why can't I use 100% of the drive for that purpose? "Manage Windows Backup disk space" "change settings" for "System image" doesn't offer any opportunity to change the 30%. Is there a registry setting available? Is there another way to circumvent or reset that limit?
After some more research, I think I may have answered my own question, thought it would be good to get this covered in this blog AND some official documentation.
I think a System Image will always be created when requested if there is room. In other words, the 30% limit probably doesn't apply to the current image.
It appears that the 30% limit is a function of default Volume Shadow Copy size restrictions on the volume where the System Image is being stored, and hence applies only to the storage of older images.
If this is true, then the limit should be able to be changed with either:
a) vssadmin Resize Shadowstorage or
b) Control Panel -> System -> System Protection -> <select System Image storage drive> -> Configure
Confirmation of my reasoning would be welcome.
My understanding was that "System Protection" was about restore points, not system image backups. Backups are under "Control Panel\System and Security\Backup and Restore" on my PC.
I just wanted to add a comment to the "support for multiple images" section. The way this interacts with the volume shadow copy is nonsensical and overly complicates use of what could be a great feature.
When I started experimenting with this new feature, I expected that I could create an image, name it “fresh install with drivers image” and be done. If I were to create a second image, I could name it something different “fresh install with drivers and applications image”. I quickly realized that was not the case. However, I created my first image and figured I could rename the image's directory so I could get more than one image. Then, excited to test this new image out, I booted to my freshly made restore CD to discover it wouldn’t find the image after I renamed the directory. Furthermore, there was no “locate or find image” button.
In summary, I find the current implementation is overly confusing and I haven’t operated a computer without disk images for years (using aftermarket software). I believe life is too short to spend 3 hours searching for a driver issue when you can restore from an image and have a functional machine in 15 minutes (I store all data on a separate partition to enable this functionality).
You are right. If you want to create more space for storing previous versions of System image, shadow copy storage area of target volume needs to be increased.
The methods to increase the size are definitely the same as you have mentioned.