Backup and Restore offers file and folder backup in all editions of Windows. But its full set of features are only available on high-end editions of Windows, i.e., the Professional, Business, Enterprise, and Ultimate editions.
Microsoft deprecated Backup and Restore in Windows 8.0, recommending to use the File History app for file-based backup and a third-party solution for system imaging. Despite its deprecation, however, it is part of all versions of Windows released thereafter.
The Windows Server counterpart of Backup and Restore is called Windows Server Backup.
Backup types
Backup and Restore supports two different types of backup: File and folder backup, and system image.
File and folder backup
The Backup and Restore app can create backup copies of individual files and folders. These backups are saved to ZIP files. Two methods of file backup are supported. The first, normal backup, stores everything selected for backup. The second, incremental backup stores only files that are changed after a previous backup.
File backup in Windows Vista does not allow users to choose specific files, locations, or users to back up; instead, it backs up content from all users based on categories: audio tracks, compressed files, documents, email, photos, recorded television shows, videos, and additional user files. Users can only choose whether to perform a backup of a certain category.[3] Microsoft hoped that this simplistic approach would prove appealing to users who were easily appalled by "a long tree of checkboxes."[4]
File backup in Windows 7 presents two options for operation: Let Me Choose, which allows users to perform backups of specific folders, libraries, and to create a system image; and Let Windows Choose, which creates backups of all personal data in user folders and libraries, and also creates a system image.[5]
System image
The other method of backup, called Complete PC Backup in Windows Vista or system image in Windows 7, is a block-by-block disk image of the system, saved in a VHD file. The block-based backup is more efficient at performing subsequent differential backups, as only the blocks that have changed need to be backed up.[4][6][7] However, Backup and Restore can also only create system images of disks formatted with the NTFSfile system.[5]
One could later restore the VHD through the Windows Recovery Environment.[7][8] Beginning with Windows Vista SP1, system images can be restored to a machine with a different motherboard, which may have a different disk controller, but the target machine must have the same number of disks.[9]
Alternatively, one could mount the VHD image as a virtual disk, allowing extraction of individual files. The mounted virtual disk has all the features of an actual volume, meaning that the Previous Versions feature of Windows 7 is available on it. In Windows 7 Enterprise and Ultimate, it also possible to boot from the VHD file.[7][8] Finally, hypervisors such as Hyper-V, VMware Workstation, and Oracle VirtualBox support VHD as their disk format, so it is possible to use these backups in virtual machines.
Backup targets
Backups could be stored on the root of any storage device other than the one being backed up or on a network share. However, Backup and Restore does not support backing up to a subfolder of a volume.[10] It also supports CDs, DVDs, and Blu-ray discs as backup destinations,[11] but does not support tape drives.[5]
Backup and Restore is only a frontend for interfacing with the user. The backend component is a Windows service called Windows Backup. This service runs independent of user sessions and can perform scheduled backups even when no users have logged onto the system. Scheduled backups, by default, run every Sunday at 7 P.M.[5]
During a backup, Windows uses the Volume Shadow Copy Service (VSS) to ensure that files are not changed while they are being backed up.[13] VSS ensures both file system-level consistency and app-level consistency for apps registered as VSS writers. In Windows Vista and Windows 7, another Windows component called System Restore also uses VSS. As such, System Restore can use shadow copies that Backup and Restore created during a full system backup.[14]
As mentioned above, Backup and Restore is merely a frontend. Windows ships with an alternative frontend for Windows Backup, the WBAdmincommand-line utility. Only a member of the Administrators groups or the Backup Operators group can run WBAdmin.
Edition comparison
The Home Basic edition of Windows can perform manual file backups. The Home Premium and later editions can automate file backups, create file backups on network locations, create backup schedules, and perform incremental backups of files. The Professional, Business, Enterprise, and Ultimate editions support both the system image and Shadow Copy.[15] The user interface of Complete PC Backup in Windows Vista does not support creating a system image to a network location; however, the WBAdmin command can perform this operation. Unlike Windows Vista Home Premium,[15] however, backing up files to a network share is not available in Windows 7 Home Premium.[16][17] Windows 7 provides a user interface option to create a system image to a network location.
Comparison of the Backup and Restore features across Windows Vista and Windows 7 editions[15][16][17]
With the release of Windows 8, Microsoft deprecated Backup and Restore in favor the new File History feature. Microsoft cited low use as the contributing factor for its deprecation, though the company retained all of its functionality for users who relied on it; the feature was moved to a Windows 7 File Recovery Control Panel applet and all previous points of access were removed.[18] In Windows 8.1, all interface functionality—with the exception of system image creation, which is in a System Image Backup option in File History—were removed.[19] Scheduling system image backups is not supported either. WBAdmin, however, remained available.[20] (As mentioned above, both Backup and Restore, and WBAdmin are merely frontends for the Windows Backup service.) With the release of Windows 10, the Backup and Restore (Windows 7) Control Panel applet was made available again. All editions of Windows 10 are able to store backups on a network location.
File History remains the default and preferred method to back up local content in Windows 10.[21] For the system image functionality, Microsoft recommends using third-party software.[22]
^Sneha (25 August 2009). "Backup destination subfolder selection". Windows 7 IT Pro Forums (TechNet). Microsoft. Archived from the original on 15 October 2010. Retrieved 23 December 2011. Right now, backup does not support backing up to a sub folder of a volume. [...] However, this should not stop you from running backups of multiple computers to a device since every backup creates a <<MachineName>> folder and runs <<MachineName>> machine's backups to it.
^Srivastava, Abhinav (29 October 2009). "Backup fails with error code 2155348010 Windows Backup Forums". TechNet Forums. Microsoft. Archived from the original on 10 June 2011. Retrieved 10 June 2011. The issue is that the Samsung drive has a 4096 byte sector size. Windows server [sic] backup is not designed to run on such disks. We will try and address this issue in a future release. However, some disks with 4096 byte sector size do support and emulation mode for 512 byte sector. [...] If 512 sector size emulation can be enabled then windows backup [sic] will be able to use this disk.
^ abLi, Arthur (28 October 2009). "Windows 7 Home Premium network backup". TechNet Forums. Microsoft. Archived from the original on 3 December 2011. Retrieved 3 December 2011. Frankomali: I had this capability in Vista, and just lost it when I paid for and applied the "upgrade" to Windows 7. Arthur Li: Yes, this is the truth. Windows 7 Home Premium does not support to backup to a network location.