Your network consists of a single Active Directory domain. The network contains 20 file servers that
run Windows Server 2008 R2. Each file server contains two volumes. One volume contains the
operating system. The other volume contains all data files.
You need to plan a recovery strategy that meets the following requirements:
• Allows the operating system to be restored
• Allows the data files to be restored
• Ensures business continuity
• Minimizes the amount of time to restore the server
What should you include in your plan?

A.
Windows Deployment Services (WDS)

B.
Windows Automated Installation Kit (Windows AIK) and folder redirection

C.
the Multipath I/O feature and Volume Shadow Copies

D.
the Windows Server Backup feature and System Image Recovery

Explanation:

MCITP Self-Paced Training Kit Exam 70-646 Windows Server Administration:
■Windows Server Backup Windows Server Backup provides a reliable method of backing up and
recovering the operating system, certain applications, and files and folders stored on your server.
This feature replaces the previous backup feature that was available with earlier versions of
Windows.
Windows Server Backup
The Windows Server Backup tool is significantly different from ntbackup.exe, the tool included in
Windows Server 2000 and Windows Server 2003. Administrators familiar with the previous tool
should study the capabilities and limitations of the new Windows Server Backup utility because
many aspects of the tool’s functionality have changed.

Exam Tip: What the tool does
The Windows Server 2008 exams are likely to focus on the differences between NTBACKUP and
Windows Server Backup.
The key points to remember about backup in Windows Server 2008 are:
■ Windows Server Backup cannot write to tape drives.
■ You cannot write to network locations or optical media during a scheduled backup.
■ The smallest object that you can back up using Windows Server Backup is a volume.
■ Only local NTFS-formatted volumes can be backed up.
■ Windows Server Backup files write their output as VHD (Virtual Hard Disk) files. VHD files can be
mounted with the appropriate software and read, either directly or through virtual machine
software such as Hyper-V.
MORE INFO Recovering NTbackup backups
You cannot recover backups written using ntbackup.exe. A special read-only version of ntbackup.exe
that is compatible with Windows Server 2008 can be downloaded from http
://go.microsoft.com/fwlink/?LinkId=82917.
Windows Server Backup is not installed by default on Windows Server 2008 and must be installed as
a feature using the Add Features item under the Features node of the Server Manager console.
When installed, the Windows Server Backup node becomes available under the Storage node of the
Server Manager Console. You can also open the Windows Server Backup console from the
Administrative Tools menu. The wbadmin.exe
command-line utility, also installed during this process, is covered in “The wbadmin Command-Line
Tool” later in this lesson. To use Windows Server Backup or wbadmin to schedule backups, the
computer requires an extra internal or external disk. External disks will need to be either USB 2.0 or
IEEE 1394 compatible. When planning the deployment of disks to host scheduled backup data, you
should ensure that the volume is capable of holding at least 2.5 times the amount of data that you
want to back up. When planning deployment of disks for scheduled backup, you should monitor how
well this size works and what sort of data retention it allows in a trial before deciding on a disk size
for wider deployment throughout your organization.
When you configure your first scheduled backup, the disk that will host backup data will be hidden
from Windows Explorer. If the disk currently hosts volumes and data, these will be removed to store
scheduled backup data. Note that this only applies to scheduled backups and not to manual backups.
You can use a network location or external disk for a manual backup without worrying that data
already stored on the device will be lost. The format and repartition only happens when a device is
first used to host scheduled backup data.
It does not happen when subsequent backup data is written to the same location.
It is also important to remember that a volume can only store a maximum of 512 backups. If you
need to store a greater number of backups, you will need to write these backups to a different
volume. Of course given the amount of data on most servers, you are unlikely to find a disk that has
the capacity to store so many backups.
So that scheduled backups can always be executed, Windows Server Backup will automatically
remove the oldest backup data on a volume that is the target of scheduled backups. You do not
need to manually clean up or remove old backup data.
Performing a Scheduled Backup
Scheduled backups allow you to automate the backup process. After you set the schedule, Windows
Server Backup takes care of everything else. By default, scheduled backups are set to occur at 9:00
P.M. If your organization still has people regularly working on documents at that time, you should
reset this. When planning a backup schedule you should ensure that the backup occurs at a time

when the most recent day’s changes to data are always captured. Only members of the local
Administrators group can configure and manage scheduled backups.
To configure a scheduled backup, perform the following steps:
1. Open Windows Server Backup. Click Backup Schedule in the Actions pane ofWindows Server
Backup. This will start the Backup Schedule Wizard. Click Next.
2. The next page of the wizard asks whether you want to perform a full server backup or a custom
backup.
Select Custom and click Next. As you can see in Figure 12-3, volumes that contain operating system
components are always included in custom backups. Volume E is excluded in this case, because this
is the location where backup data will be written.

Figure 12-3Selecting backup items
3.The default backup schedule is once a day at 9:00 P.M. You can configure multiple backups to be
taken during the day. You are most likely to do this in the event that data on the server that you are
backing up changes rapidly. On servers where data changes a lot less often, such as on a Web server
where pages are only updated once a week, you would configure a more infrequent schedule.
4.On the Select Destination Disk page, shown in Figure 12-4, you select the disk that backups are
written to. If multiple disks are selected, multiple copies of the backup data are written. You should
note that the entire disk will be used. All existing volumes and data will be removed and the backup
utility will format and hide the disks prior to writing the first backup data.

5.On the Label Destination Disk page, note the label given to the disk you have selected to store
backups. When you finish the wizard, the target destination is formatted and then the first backup
will occur at the scheduled time.
An important limitation of Windows Server Backup is that you can only schedule one backup job. In
other words, you cannot use Windows Server Backup to schedule jobs that you might be used to
scheduling in earlier versions of Windows, such as a full backup on Monday night with a series of
incremental backups every other day of the week. You can configure Windows Server Backup to
perform incremental backups, but this process is different from what you might be used to with
other backup applications.

Figure 12-4Selecting a destination disk
Performing an Unscheduled Single Backup
Unscheduled single backups, also known as manual backups, can be written to network locations,
local and external volumes, and local DVD media. If a backup encompasses more than the space
available on a single DVD media, you can span the backup across multiple DVDs. Otherwise, if the
calculated size of a backup exceeds the amount of free space available on the destination location,
the backup will fail. You will perform a manual backup in a practice exercise at the end of this lesson.
When performing a manual backup, you must choose between using one of the following two types
of Volume
Shadow Copy Service backup:

■VSS Copy BackupUse this backup option when another backup product is also used to back up
applications on volumes in the current backup. Application log files are retained when you perform
this type of manual backup. This is the default when taking a backup.
■VSS Full BackupUse this backup option when no other backup products are used to back up the
host computer. This option will update each file’s backup attribute and clears application log files.
When performing a single backup, you can also back up a single volume without having to back up
the system or boot volumes. This is done by clearing the Enable System Recovery option when
selecting backup items.
You might use this option to back up a specific volume’s data when you are going to perform
maintenance on the volume or suspect that the disk hosting the volume might fail, but do not want
to wait for a full server backup to complete.
Full Server and Operating System Recovery
Also known as Bare Metal Recovery, full server recovery allows you to completely restore the server
by booting from the Windows Server 2008 installation media or Windows Recovery Environment.
See the note on building a recovery solution for more information on how to set up a local Windows
Recovery Environment on a Windows Server 2008 computer. Full server recovery goes further than
the Automated System Recovery (ASR) feature that was available in Windows Server 2003 because
full server recovery will restore all operating system, application, and other data stored on the
server. ASR did not provide such a complete recovery and it was necessary to further restore data
from backup after the ASR process was complete.
An operating system recovery is similar to a full server recovery except that you only recover critical
volumes and do not recover volumes that do not contain critical data. For example, if you have a file
server where the disks that host critical operating system volumes are separate from the disks that
host shared folder volumes and the disks that host the critical operating system volumes fail, you
should perform an operating system recovery.

Figure 12-13Select Windows Complete PC Restore