Built-in Backup Tools - Windows 7

The first method of performing backups is to use the built-in backup tools in Windows 7, 8.1, or OS X. These offer both image based backups, as well as file based backups. This is your first line of defense. If your budget is low, the bare minimum that you want to do is at least back up your files and system image to an internal or external drive, or a network share.

Windows 7

Windows 7 includes a built-in utility called Backup and Restore (formerly Backup and Restore Center in Windows Vista) which allows you to perform backups to internal or external disks on your local PC. If you have Windows 7 Professional, Enterprise, or Ultimate, Backup and Restore will also allow you to perform backups to a network share. Backup and Restore allows both file level, and image level backups. Windows 7 also has a built-in feature called Previous Versions, which will leverage both Windows Backups as well as restore points in order to allow you to restore files to a different point in time.

Backup and Restore, when configured to perform both file and system level backups, will actually perform both a file level, and a system level backup. Unlike more sophisticated backup software, it doesn’t leverage the system level backups for file level restores, meaning it is going to take up more space than a backup solution which does just system level. It does allow incremental backups and versioning though. The biggest issue with Windows 7’s built-in Backup and Restore is its inability to backup files and images to a network share for Starter and Home Premium – the two versions most people have. It also can’t backup files that are on a network share. That being said, it’s a great place to start for anyone who wants to back up to an internal or external drive for file and system protection. Let’s run through how to configure it:

  1. Go to the Control Panel, then choose System and Security, and select Backup and Restore
  2. On the Control Panel applet screen, choose Set up backup.

  1. First you will be prompted as to where to save your backups. Your options are any local disk, USB disk, or CD/DVD. If you have Windows 7 Professional, Enterprise, or Ultimate, there will be an additional selection here to choose a network share and enter the necessary credentials to access it. Choose your backup disk and click Next.

  1. Next, you will be asked what to back up. The default selection is to back up all user data saved in libraries and default user folders, as well as a system image. If you keep all of your data in your libraries, this should be fine for you so click Next. If you keep data in other folders, or only want to backup certain locations, select Let me choose and click Next.

  1. If you’ve chosen Let me choose, you will be prompted to select what data files to backup. By default, all user Data files are selected, but you can also expand under Computer and choose what to backup, or just backup everything. Also there will be a selection to include a system image for restoring your entire drive. If you have space on your backup drive, it’s a great idea to include this. Click Next when you’ve selected everything you need to backup.

  1. Next, you will be provided a summary of the backup job which you can review. The summary page will display the default schedule (Sunday at 7pm) and you can change the schedule to perform backups more often. Weekly backups would be the minimum that I would perform. Since the backups are incremental, it’s probably a good idea to bump this up to daily. Choose a time where you are not likely to be using the computer. Once you are happy, click Save settings and run backup, and the system will perform the initial full backup.

That’s it. Your computer is now backing up automatically at whatever schedule you chose. The next thing you should do, assuming you selected to create a System backup, is to create a bootable disk to recover your system. It’s easier to do this now, than when you need it. To do this, simply go to the Backup and Restore applet in the control panel, and choose Create a system repair disc. You will be prompted to place a CD or DVD in your drive and then just select Create disc. A small bootable disc will be burned which will allow you to restore a complete system image from a local disk, or a network share. If you do ever need this, bear in mind that a system restore will completely erase all files on the restore target.

If you want to restore individual files, you have a couple of options. You can use the Backup and Restore applet to browse for files and folders of your backups and choose which ones to restore. If you do a restore this way, and select restore to original location, it will do a standard file copy of the restored files to their original locations. If the original files are still in that location, the standard dialog will appear letting you select whether to replace the originals, copy with a new file name, or do nothing. Be careful if you do this as you will have a good chance of overwriting files you meant to keep.

The other method for restoring files is to use the Previous Versions interface to select which file and folder, and from which date to restore. This is likely the preferred method since it will display graphically all previous versions of the file or folder. To invoke this method, simply browse to the file or folder you wish to restore, right click, and choose Restore previous versions. This will display all versions that are in the backups, and allow you to open the file to view it, copy the file, or restore the file.

Overall, the Windows 7 backup utility is fairly good. With both file level and image level backups available, you can recover from practically any scenario. Its glaring omission is the lack of network support on the home versions of Windows 7, which is really unfortunate. Many people would rather back up their files to a NAS, especially in any house with more than one computer. But if you are running Windows 7 and you just have a single computer, it is worthwhile using this for the price of a single hard drive to back up to. Unfortunately, almost no one used this backup system so it was replaced when Windows 8 was launched.

Plan Your Backups Built-in Backup Tools - Windows 8.1
POST A COMMENT

133 Comments

View All Comments

  • patrickjchase - Thursday, May 22, 2014 - link

    ZFS RAIDZ implements strong checksums within each drive, such that it can reliably detect if a drive is returning bad data and ignore it. In some respects it's actually stronger than RAID6 in terms of its ability to deal with silent corruption. That's why NonSequitor wrote "double parity OR checkums" (RAID6 is double-parity, RAIDZ is single-parity augmented with strong per-disk, per-chunk checksums).

    If you're halfway competent then it's not "extremely likely" that you'll encounter unreadable sectors during a RAID5 rebuild. There's a reason why both good RAID controllers and ZFS implement scrubbing (i.e. they can periodically read every disk end to end and remap any unreadable sectors). If you do that every couple days then the likelihood of encountering a new (since the last scrub) unreadable sector may or may not be high depending on your rebuild time.

    For example I have a 5-disk RAID5 array that I use for "cold" storage. I scrub it daily, and rebuilding to a hot-spare takes 6 hours (I've tested it several times, verifying the results against separate copies of the same files), which means that the maximum delay between the most recent scrub and the end of a rebuild is 30 hrs. The scrubs have only found one bad sector in ~2 years, so I respectfully submit that the likelihood of an additional failure within 30 hours of a scrub is pretty darned low.
    Reply
  • beginner99 - Thursday, May 22, 2014 - link

    exactly. anything above 2 TB drives becomes really problematic in this regard. With 4 TB drives it's almost guaranteed a RAID-5 rebuild will fail. IMHO if you do RAID, do RAID-1. Reply
  • patrickjchase - Thursday, May 22, 2014 - link

    RAID1 has exactly the same problems as RAID5 - In the case of silent corruption it can't determine which disk is bad, and it's vulnerable to a single disk failure during a rebuild. The likelihood of such a failure is obviously lower (now you only have to worry about 1 other disks instead of 2 or more) but not hugely so. RAID6/RAIDZ2 is statistically much better until you get up to really high drive counts.

    The "big boys" with truly mission-critical data do N-way replication, i.e. all critical data is replicated (n>=3) times on different systems.
    Reply
  • jimhsu - Wednesday, May 21, 2014 - link

    +1 to crashplan. For my most important data, I have n+2 backups: n being the number of computers I have (meaning that Onedrive automatically syncs them); 2 being a crashplan online subscription as well as a local crashplan backup. I also have restore previous versions running, and use it on occasion, but don't consider it a backup per se. Reply
  • pjcamp - Wednesday, May 21, 2014 - link

    I plowed through all the competitors a few years ago, and Crashplan was the one I selected. It had the cheapest unlimited storage with version history, and the (for me) killer feature that there exists a Linux client. I have a FreeNAS box that I use for media storage. I can mount it as a drive on my Linux machine and the Crashplan client will back it up just as if it were a local drive. There is also an Android client that gives you access to all your files, functioning as a sort of personal Dropbox, without sharing but with better security.

    I've had occasion to use my backups a couple of times and found it easy and speedy, much more so than I expected for a cloud service.
    Reply
  • cknobman - Wednesday, May 21, 2014 - link

    Everything in my house goes to a personally built server onto dedicated RAID storage drives. No accounts other than my personal administrator account have access to do anything but read.

    Those drives are then backed up to the cloud via CrashPlan.

    Simple, effective, and as foolproof as I can get for now.
    Reply
  • uhuznaa - Wednesday, May 21, 2014 - link

    One thing to note with Time Machine: You don't need to use the fancy interface for restoring files. Just browse your backup disk with the Finder (or on the command line), there's a directory for every backup from which you can just copy things over.

    To CrashPan: I used that for a while, but found it to be utterly uncontrollable. The log files are a joke, the status mails arrive at random times (or not at all) and are useless ("Files: 117k, Backed Up: 99.9%") and often enough when a backup didn't run for some reason it's impossible to debug because there's no real error reporting. It may work somehow, but it has all the marks of something I don't want to rely on.
    Reply
  • NCM - Wednesday, May 21, 2014 - link

    Yes, that's indeed a big point for Apple's TimeMachine — that and it being included free with every Mac. If necessary you can just go digging into a TM archive and pull out what you need. Reply
  • SkateboardP - Wednesday, May 21, 2014 - link

    Hi Brett,

    great guide but can you or others please check if the OneDrive backupsolution is throttled and capped at 355kb/s under win8.1 (Desktop)? I read that many people complaining about that. Thanks.
    Reply
  • plext0r - Wednesday, May 21, 2014 - link

    I've been using Duplicati for a few years and it has been good. "It works with Amazon S3, Windows Live SkyDrive, Google Drive (Google Docs), Rackspace Cloud Files or WebDAV, SSH, FTP (and many more)." It uses rsync under the covers and I use it to backup to my RAID-5 NAS in the basement. I also perform offsite backups (rotate 1TB disks to and from my workplace). Reply

Log in

Don't have an account? Sign up now