Windows 7 / Networking

Creating System Restore Snapshots

Shadow Copies for Shared Volumes (SCSV) and Hyper-V snapshots provide you with the ability to return to a specific point in time.

Although Windows client operating systems support the ability to create system restore points, Windows Server 2008 and later operating systems don't. What they do provide is the ability to use Shadow Copies for Shared Volumes (SCSV) as well as Hyper-V snapshots as mechanisms for returning to a specific point in time. You can also utilize the Hyper-V VSS writer and VSS to back up virtual machines (VMs) using Window Server Backup.

ENABLING SHADOW COPIES FOR SHARED VOLUMES

Shadow Copies for Shared Volumes (SCSV) uses the capabilities of the VSS to capture and store copies of folders and files (located on shared network resources) at a specific point in time.

When SCSV is implemented on a volume, both end users and administrators can recover accidentally deleted or overwritten files as well as compare different versions of the same file. Because end users can restore their own files, implementing SCSV can dramatically reduce not only the time but the associated costs of having to recover their folder and files via their IT support desk.

You enable SCSV on a per-volume basis by selecting Server Manager → Tools → Computer Management . The volumes must be formatted using NTFS and should not contain any mounted drives or mount points. If the volume has either, their contents will not be included in the shadow copies. The first shadow copy of the volume is a complete copy of the data; subsequent shadow copies include only the changes made since the last shadow copy was created. The source volume is the volume that contains the data you want to copy. The storage volume is where your shadow copies will be located and if possible should be placed on a separate disk from the one that holds the source volume.

You need at least 300 MB of free space to create a shadow copy on the selected volume. By default, a shadow copy is created at 7:00 AM (Monday-Friday) and at 12:00 PM (Monday-Friday). You can modify the schedule by selecting the Settings button. You can also click the Create Now button to take a manual snapshot between scheduled times.

ENABLE SHADOW COPIES FOR SHARED VOLUMES

To enable Shadow Copies for Shared Volumes on Server01, perform the following steps:

  1. Log in to Server01 with administrative privileges.
  2. Create a shared folder called CorpDocs on a simple volume (E:) on Server01 and share the folder so that administrators have full access.
  3. Create a fi le in the CorpDocs folder named Agenda.txt , enter sample text, and then save and close.
  4. Open Server Manager , and select Tools → Computer Management.
  5. Expand the Storage item and select Disk Management.
  6. Right-click the volume you created the shared folder on and select Properties.
  7. Select the Shadow Copies tab.
  8. Confirm the volume you selected in Step 4 is highlighted and then click Enabled.
  9. Click Yes to confirm you want to enable shadow copies on the volume. A snapshot is taken immediately and the date/time stamp is noted.
  10. Click Create Now to create a second snapshot of the selected volume and then click OK to close.

BACKING UP HYPER-V VIRTUAL MACHINES

VMs, created using Hyper-V, are stored as files on your hard disk. These files contain the VHDs, saved state files, snapshot files, and configuration files. Because these are stored on a volume on your server, Windows Server Backup can be used to protect them in combination with the VSS.

VSS writers are responsible for preparing their data in order to make the shadow copy and are instructed by VSS to quiesce its associated application to ensure a consistent backup is made. By using the Microsoft Hyper-V VSS writer, Windows Server Backup can create the snapshots while the VM is running.

Windows Server Backup supports only a volume-based backup for VMs; therefore, you need to select all volumes that contain your VM files. For example, if you store your VM configuration files on one volume and your VHD files on another, both volumes need to be backed up.

VMs containing dynamic disks need to be backed up offline. Machines running operating systems that do not support VSS and those that do not have Integration Services installed will be put in a saved state while the VSS snapshot is created.

TAKING HYPER-V SNAPSHOTS

Hyper-V snapshots offer another way to capture the state, data, and hardware configurations for a VM at a specific point in time. These snapshots, which can be taken when the VM is running or stopped, are created in the Hyper-V Manager. The snapshot includes the configuration and network settings for the VM as well as the current state of the VHD(s) attached to the machine and any saved state information. Hyper-V uses the VSS to make a copy of the guest machine's hard disk.

By default, a Hyper-V snapshot's data is stored in an automatic VHD (.avhd) file and then it's attached to the VM. When you take a snapshot of a VM, you are basically converting its VHD into a differencing disk.

Although not designed as a recovery option in production environments, you can use Hyper-V snapshots to troubleshoot potential problems with applications or the impact a service pack/upgrade will have on a server.

If you enabled VSS on a volume where the Hyper-V snapshots are stored, they can be backed up by default, as part of a shadow copy created at 7:00 AM (Monday-Friday) and at 12:00 PM (Monday-Friday).

If you have the backup (volume snapshot) Integration Services installed on the guest operating system, a VSS requester is installed that allows the VSS writers in the guest OS to participate in the VM's backup.

The following outlines the steps used to take a snapshot of a VM using the Hyper-V Manager on the host:

  1. Log on to the server with administrative privileges.
  2. Open Server Manager and select Tools → Hyper-V Manager.
  3. Select the VM host that manages the VMs.
  4. Highlight the VM.
  5. Right-click and select Snapshot from the menu.

Each snapshot taken of a VM is documented in a tree structure. The first (root) node represents the first snapshot taken, and the Now node is the current version of the VM that is running. Each snapshot is labeled using the VM's name (as created in Hyper-V Manager) along with a time stamp based on the date/time the snapshot was created.

EXPLORING ENTERPRISE BACKUP SOLUTIONS FOR WINDOWS SERVER 2012

If you are looking for an enterprise backup solution, then System Center 2012-Data Protection Manager should be considered. It provides the ability to not only back up to disk but to tape as well. It can be used to protect and recover Exchange (2007, 2010, 2013), SQL (2008, 2008R2, 2012), SharePoint (2013, 2010), Windows SharePoint Server 3.0, Microsoft Office SharePoint Server 2007, Windows desktops/laptops (Windows 7/8, Windows Vista), virtual servers (Hyper-V Windows Server 2008/2008R2, Windows Server 2012), and file servers (Windows Server 2008/2008R2, Windows Server 2012) within and across Active Directory domains. DPM also provides you with the ability to manage system state and bare metal recovery from a central location. The following vendors also provide enterprise backup solutions for Windows Server 2012:

  • Acronis Backup and Restore
  • Symantec Backup Exec 2012 and NetBackup
  • IBM Tivoli Storage Manager
  • Carbonite
  • CA Technologies ARCserve
  • Commvault Simpana
[Previous] [Contents]

In this tutorial:

  1. Configuring and Managing Windows Server Backups
  2. Configuring Windows Server Backups
  3. Configuring Windows Online Backup
  4. Configuring Role-Specific Backups
  5. Managing VSS Settings Using VSSAdmin
  6. Creating System Restore Snapshots