Built-in Backup Tools Windows 8.1

While Windows 7 and Vista had the Backup and Restore applet, Windows 8 introduced File History as the default backup option. File History is a replacement for Previous Versions from Windows Vista and Windows 7. Unlike Windows 7, File History does allow backup to network shares for all versions of Windows 8 which is a good thing and makes the software far more useful. The downside is that scheduled System Backups have been removed from Windows 8 and 8.1. You can still manually create a system backup, and you can perform a system backup to a network share, but you can’t schedule this to be run. Also, File History only performs a backup of files in your libraries (Documents, Music, Pictures, Videos, and Desktop folders), as well as any files saved locally from OneDrive. Still, the most important information on your computer is your files, so let’s look at how to enable this feature to protect them:

  1. Windows 8.1 adds the ability to enable File History from PC Settings, however the options are just to enable File History and to select a backup target, so these instructions will focus on the Control Panel applet which offers more advanced options. To launch File History, right click the Start button and choose Control Panel. Next expand System and Security and select Save backup copies of your files with File History.

  1. If File History has never been configured before, the system will scan for available disks that it can back up to. You can choose the disk, or use the link Select a network location to configure the disk.

  1. Once configured, simply click Turn On, and File History is enabled.

  1. If you’d like to modify your File History settings, that can be done in the File History applet. To exclude folders, choose Exclude Folders where you can select folders you wish to exclude from the backup. Unfortunately, you can’t add user defined folders here which you do want backed up. To add folders to be backed up, you either have to add that folder to an existing library, or create a new library.

  1. Advanced settings are also available in the File History applet, and these allow you to specify how often to run the File History backup (from ten minutes to daily) as well as specify how much of the PC’s disk to use as an offline cache (2% to 20%) in the event you are travelling and not able to access your backups, as well as to specify how many versions of files to keep.

Unlike Windows 7, File History’s interface is all in the control panel. It’s not as elegant as Previous Versions was, where you could right click any file or folder and see a list of all versions, but the interface is fairly straightforward and does show you a list of all of the backups:

  1. Launch File History by right clicking the Start button and opening the Control Panel. Next expand System and Security and select Restore your files with File History.
  2. The interface that opens up will be a listing of the locations you are backing up. The most recent backup will be displayed by default. To restore a file, navigate to the folder it was in, select the file by clicking it, and then press the green Restore button to restore it to the original location.

  1. If you’d like to restore it to a different location, right click the file and choose Restore To and then browse to your path.
  2. To navigate through your backups, you can use the skip buttons at the bottom of the page. The easiest way to sort though is to navigate to the folder where your file is (or was), and it will display only the backups that have changes in them. If a folder hasn’t been modified since you enabled File History, there will only be one backup for it. This is an easier method than trying to figure out which day you deleted a file.

Overall, File History is a decent built-in utility, but as is often the case, attempts to make the process easier to use often result in a system that is less powerful, and that’s certainly the case with this. Windows 7 lacked network backup for some versions, but overall the Windows 7 backup utility offered more features, especially with the automatic system backup. Previous Versions is also an easier way to find changes made to a file. File History also lacks a method of backing up files outside of your libraries and OneDrive folders which is not ideal by any means. Windows 8.1 forces you to make a system backup manually, and that can be done as so:

  1. Right click the Start button and open Control Panel. Expand System and Security, and then select Save backup copies of your files with File History which won’t actually be used, but is the shortcut to the System image backup.
  2. On the File History applet, click on System Image Backup in the bottom left corner.
  3. Choose a location for your backup. If it’s on a network share, you can optionally enter login credentials if required. Click Next.

  1. Now you will be prompted to confirm, and if you are happy click Finish. The confirmation dialog will estimate how much disk space will be required, and warn you that only a single backup file will be kept. In other words, there is no versioning.

If you are using File History as your backup method of choice, you should definitely create at least one system backup to allow you to restore to a new hard drive or machine if necessary. If you ever need to restore this, you can create a recovery drive by choosing the Recovery option in the File History applet. If you don’t have another computer to create this on if needed, it’s a good idea to create one ahead of time.

It is possible to create full scheduled backups, but only from the command line using wbadmin but this is not something I would recommend for the average user.

Built-in Backup Tools - Windows 7 Built-in Backup Tools - OS X
Comments Locked

133 Comments

View All Comments

  • bernstein - Wednesday, May 21, 2014 - link

    after fifteen years of backupping i can share the following:
    - user initiated (e.g. all usb, some network/cloud) backups agree with less than 0.1% of the human population (but hey it is better than nothing)
    - with consumer hdds, raid5 nas are totally overrated and *in the real world* rarely protect data better than jbod.
    - raid6 is better than jbod. but with consumer disks the only real alternative to jbod is zfs (linux md (which all nas employ) + consumer hdds = shaky unless you have a 24/7sysadmin...)

    so either build/buy a zfs nas or backup to the cloud.
  • bernstein - Wednesday, May 21, 2014 - link

    or buy insanely expensive enterprise disks
  • DanNeely - Wednesday, May 21, 2014 - link

    Are there any consumer grade NASes with ZFS support enabled by default now? The peanut gallery on yesterday's Synology review was arguing for ZFS being a key reason for rolling your own instead of buying an off the shelf NAS.
  • questionlp - Wednesday, May 21, 2014 - link

    There's FreeNAS Mini, which is a 4-bay NAS. I'm actually considering getting one to replace my current file server at home.
  • DanNeely - Thursday, May 22, 2014 - link

    Yikes! At $1k diskless, that's well above the typical price for a consumer nas.
  • bsd228 - Thursday, May 22, 2014 - link

    but none of them have 16G of ECC memory and a processor at this level, with dual intel gig nics and expansion ports to support a 10G or other parts. It appears to be able to transcode 3 HD streams without the benefit of the acceleration shown in this product. So, perhaps a bit of premium, but not that much.
  • CadentOrange - Wednesday, May 21, 2014 - link

    I personally use RAID1 with a 2 bay NAS that's worked fine so far. Granted that I don't have very rigorous needs, but then this isn't for enterprise critical data.
  • Kevin G - Wednesday, May 21, 2014 - link

    I've had good luck with RAID5 on small scale arrays. The main reason to go to RAID6 is due to the chance of a disk failing during the rebuild process. Consumer NAS typically are not under that much load so the rebuild times are short. In an enterprise environment where disk counts are higher in an array as well as the load on the array, using RAID6 makes sense.

    Personally I have an 8 drive RAIDZ2 array in a NAS4Free system that I use at home. Portability and reliability are some of the reasons I went with ZFS. So far it has been purely hands off once I got the system up and running. Admittedly it took a bit longer to get up and running as I'm doing some odd things like hosting virtual machines on the same system.
  • MrBungle123 - Friday, May 23, 2014 - link

    The reason for RAID 6 is because statistically 1 bit out of every 10^14 bits (12TB) is bad on a hard drive... with all drives operational a RAID 5's parity can compensate for said bad bit, with a degraded RAID 5 the sector will be un-recoverable and you'll lose data. RAID 6 has double parity so even with a drive down if (when) a bad sector is encountered it is still possible to recover the data. RAID 5 is obsolete for large arrays.
  • Kevin G - Friday, May 23, 2014 - link

    If you know what sector is bad in RAID5, you can still recover the data.

    The tricker thing is silent corruption where all blocks appear to be OK. There an error can be detected but not necessarily which block contains it.

Log in

Don't have an account? Sign up now