100 002704 A

CONFIDENTIAL - NOT FOR DISTRIBUTION
Symantec Backup
Exec 2012: Install
and Configure
(Lessons)
100-002704-A
COURSE DEVELOPER
Rekha Mohanty
Monica Shah
Hitesh Saikar
Seema Mangaonkar
Divya Singh
Sanjay Levi
Girish Sharangpani
LEAD SUBJECT MATTER
EXPERTS
Ashwin Apte
Jason Butterfield
Jyothi Yanduri
Tim Haynes
Navin Tah
Norbert Geiger
Amit Nazare
TECHNICAL
CONTRIBUTORS AND
REVIEWERS
Copyright 2012 Symantec Corporation. All rights reserved.
Toni Sanders
Renee McHugh
Michael Kalish
Bob Farnsworth
Robert Owen

Symantec, the Symantec Logo, and VERITAS are trademarks or
registered trademarks of Symantec Corporation or its affiliates in
the U.S. and other countries. Other names may be trademarks of
their respective owners.
THIS PUBLICATION IS PROVIDED AS IS AND ALL
EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS
AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE
DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR
INCIDENTAL OR CONSEQUENTIAL DAMAGES IN
CONNECTION WITH THE FURNISHING, PERFORMANCE,
OR USE OF THIS PUBLICATION. THE INFORMATION
CONTAINED HEREIN IS SUBJECT TO CHANGE WITHOUT
NOTICE.
No part of the contents of this book may be reproduced or
transmitted in any form or by any means without the written
permission of the publisher.
Symantec Backup Exec 2012: Install and Configure
Symantec Corporation
World Headquarters
350 Ellis Street
Mountain View, CA 94043
United States
http://www.symantec.com
Table of Contents
Course Introduction
About this course..................................................................................... Intro-2
Symantecs education and support resources ........................................ Intro-7
Lesson 1: Backup Exec Fundamentals
Data backup basics ...................................................................................... 1-3
Symantecs backup solution offerings .......................................................... 1-5
Backup Exec architecture........................................................................... 1-21
Lesson 2: Installing Backup Exec 2012
Installing the Backup Exec server ................................................................ 2-3
Launching Backup Exec 2012.................................................................... 2-34
Updating Backup Exec 2012 ...................................................................... 2-46
Upgrading to Backup Exec 2012................................................................ 2-53
Lesson 3: Storage Devices
Devices and media....................................................................................... 3-3
Configuring storage devices....................................................................... 3-24
Managing devices ...................................................................................... 3-33
Lesson 4: Data Management
Managing media........................................................................................... 4-3
Media catalogs ........................................................................................... 4-24
Lesson 5: Backing Up Data

Backup job basics ........................................................................................ 5-3
Configuring backup jobs............................................................................. 5-19
Running backup jobs.................................................................................. 5-59
Backup and Restore view........................................................................... 5-61
GRT-enabled backups ............................................................................... 5-85
Configuring Backup Exec to determine file backup.................................... 5-91
System State backup ................................................................................. 5-94
Lesson 6: Restoring Data

Restore job basics........................................................................................ 6-3
Running restore jobs .................................................................................. 6-10
Simplified Disaster Recovery: Server Restore workflow ............................ 6-21
Lesson 7: Simplified Disaster Recovery
Simplified Disaster Recovery fundamentals................................................. 7-3
Whats new in Disaster Recovery?............................................................. 7-11
Simplified Disaster Recovery: Backup ....................................................... 7-13
Creating a custom SDR disk ...................................................................... 7-24
Using SDR for disaster recovery ................................................................ 7-36

Table of Contents
iii
Lesson 8: Virtual Machine Conversion

Conversion to virtual machines fundamentals .............................................. 8-3
Virtual conversion options............................................................................. 8-8
Virtual conversion workflows ...................................................................... 8-14
Backup to virtual conversion: Workflow ...................................................... 8-23
Lesson 9: Database Maintenance

Backup Exec database ................................................................................. 9-3

iv

Course Introduction
5
About this course

Course overview
This course sequentially presents the steps to install and configure Backup Exec
2012. It comprises nine lessons, which are listed on the slide.

Intro2

After completing this course, you will be able to:

Describe the basic functions of Backup Exec 2012.
Manage devices and media used by Backup Exec.
Run basic backup jobs.
Explain the new backup and restore workflows.
Restore backed-up data.
List the supported virtual conversion configurations.
Create a custom Simplified Disaster Recovery SDR disk.
Use Simplified Disaster Recovery SDR for disaster recovery.
List the new features and enhancements made to Backup Exec 2012.
List the End of Life Items.
Intro
Course objectives

Course Introduction
Intro3
Data protection: Is backup or restore the priority?

In this course, you learn how to use Backup Exec to perform backup and restore
operations, manage devices, media, and other elements of your backup
environment, and understand features of the product that can help you perform all
of these functions quickly, efficiently, and effectively.
Even as you complete these lessons, maintain a holistic view of the purpose of
Backup Exec. It is a tool that supports your organizations data protection plan.
Consider the following situations:
A medium-sized enterprise provides an eight-hour backup window at night,
but requires failed systems to be restored immediately.
A web-based retailers mission-critical systems must be online constantly,
providing no downtime in which to run a backup.
A global company must use a follow-the-sun backup strategy, which means
that the backup servers are constantly performing backups.
What is the priority for your organizations data protection plan? Is the emphasis
on backing up data quickly, or restoring data quickly? Or is it a combination of the
two, in which you must balance the amount of time spent backing up data with the
time required to restore it? Whatever your situation, you can manage it using
Backup Exec.

Intro4

Data protection plan
By defining data protection in terms of recovery, you can build a backup strategy
to support the data protection plan. The backup strategy must take into account
factors such as:
Number and types of users in an environment
Backup methods to be used to protect user systems
Backup windows, which are times during which backup jobs can be run
Retention periods, which define how long to keep backed-up data
Developing a data protection plan is beyond the scope of this course. But as
you cover this course, you are encouraged to think about backup and
recovery.

Course Introduction
Intro5
Intro
A data protection plan outlines the importance of an organizations data and the
strategies and methods used to protect it. The plan is based on service level
agreements (SLAs), which define factors such as:
Recovery point objectives, which are points in time to which data can be
recovered
Recovery points can be defined in terms of days, hours, minutes, or
seconds.
Recovery point objectives can also define the granularity requirements for
restores, such as the ability to restore a single e-mail message.
Recovery time objectives, which define how quickly data must be recovered
Lab Environment
For the classroom and Virtual Academy versions of this course each lesson has an
accompanying lab exercise. These labs are intended to reinforce the concepts and
practice the tasks discussed in the lessons.
The labs build consecutively upon each other. You must successfully complete
each lab before proceeding to the next one.
Your instructor will explain the structure of the lab environment, and assist
you with any problems that you may encounter during the lab activities.
10

Intro6

Symantecs education and support resources

This topic describes Symantec Education offerings and other Symantec resources
available to help you implement and manage your Backup Exec environment.
For a current list of all Symantec Education training offerings, visit http://
www.symantec.com/business/training.
Backup Exec Tech Center
11
The Backup Exec Tech Center is a cost-effective and time-saving training option
that is used to refresh and supplement the product knowledge you acquired
through product manuals and instructor-led training.
For more information, visit the Backup Exec Tech Center at:
http://techcenter.symantec.com/ecampus/enterprise.
Intro
The Backup Exec Tech Center is an online subscription library of informative selfpaced modules developed around key features, best practices, and common
technical support questions. These modules have been developed by top Backup
Exec experts. New modules are regularly added to the library.

Course Introduction
Intro7
Symantec Connect
Symantec Connect (Sym Connect) is a premier online technical community for
Symantec business customers and partners. It has thousands of members and
continues to grow rapidly.
Symantec Connect has numerous resources that enable IT professionals to be
successful with Symantec products. It is a customer-focused resource, intended to
help you design and implement a utility computing strategy to provide availability,
performance, and automation for storage, servers, and applications.
Symantec Connect provides the following resources:

Technical documents, such as articles, white papers, and product specifications
Interactive services, such as the discussion forum, where members can discuss
current topics, share tips and tricks, and help one another troubleshoot
problems
12
Symantec Connect is responsive to the needs of Symantec customers. Features of

this online community are added based on feedback that members provide.
Access to Symantec Connect is free. Sign up to become a member at: http:/
/www.symantec.com/enterprise/stn.

Intro8

Lesson 1
Backup Exec Fundamentals
13
14

12

Data backup basics

This topic describes the need for data backup.
Data backup: Overview
Whether you are an organization handling large amount of data, or a small to midsize business, a service interruption can mean significant loss to your business.
Hence, you must backup you data or important information on some other location
on a backup media. Your backup media is accompanied with a software which
enquires which files you want to back up, and copies those files onto the backup
media.
15
You can decide on the data you want to back up, the type of backup, and also the
frequency at which you want to carry out the backup. A good backup and recovery
solution reduces the complexity of protecting your companys most valuable
assetits data.
You can back up data that resides on a server, on a virtual server, on a desktop, or
on a critical application server such as, Exchange, SQL, or SharePoint.

Lesson 1 Backup Exec Fundamentals
13
Advantages of data backup

Both individuals and businesses need to plan a data backup strategy to protect
information, such as, business contacts, e-mails, text documents, presentations,
and other valuable information needed in performing business. Unfortunately,
saving your files in your personal computer does not guarantee that all information
is saved.
The slide lists the advantages of data backup. Backing up your data can prevent
data loss when:
Files and folders from your computer are deleted by failure or accident. If the
deleted files are important for your daily tasks or businesses, you need to
perform backup regularly for these files.
Data is destroyed by hard disk error or virus infection. If you have performed a
data backup before the hard disk error, you can restore the data from the
backup as soon as the reformat is completed.
Your computer is physically destroyed by natural disasters such as, floods, fire,
and so on. However, if you have performed a backup for your important data,
you can restore information to a new computer.
16
Because data loss can be a very serious problem to your work or business, data
backup is an important process.

14

Symantecs backup solution offerings

This topic describes Symantecs backup solution offerings and their advantages.
Introduction
Symantec Backup Exec powered by patented V-Ray technology unifies physical

and virtual backups, and includes integrated disaster recovery, data deduplication
and replication technology while offering a choice among on-premise, appliance,
or cloud based solutions.
17
The new, modern and innovative range of Backup Exec solutions are designed to
adapt for any business, large or small, to easily protect increasing amounts of data.
Backup Exec can protect virtual, physical or combined environments. It can
rapidly recover complete virtual machines, systems, applications, databases, files/
folders and even granular objects in minutes - all from a single pass backup. With a
sleek and streamlined administration console, Backup Exec makes it easier than
ever to efficiently manage backup and recovery operations across your physical
and virtual infrastructure.
The four primary solution categories available are, Backup Exec software, Backup
Exec Cloud, Backup Exec appliances, and a combination of two or more
categories. Each category is designed according to your business needs.

15
Backup software
Backup software protects data and reduces storage and management costs through
deduplication and archiving technology. You can recover your virtual and physical
machines, while intelligent archiving helps you identify what to store, what to
delete, and when to move older data to secondary systems.
Backup Exec 2012 Small Business Server Edition is designed for small business
server environments and includes protection for SQL, Exchange, SharePoint,
Active Directory and Hyper-V.
Backup Exec 2012 Server is designed for customers who have a mixed physical
and virtual environments including VMware, Hyper-V, Windows, Linux or Mac
servers. Backup Exec server also provides integrated deduplication or archiving
capabilities and helps to manage multiple backup servers or multi-drive tape
loaders.
18
Backup Exec 2012 V-Ray Edition helps you to protect your virtual environments.
It includes protection for VMware and Hyper-V and the following applications
running in those virtual guest machines: Exchange, SQL, SharePoint, Active
Directory, Oracle, Enterprise Vault and Lotus Domino. It also provides the
flexibility to back up to both disk and tape. You can separately purchase additional
protection for physical servers. The V-Ray Edition is licensed per virtual server.

16

Back up to the cloud

Symantecs back up to the cloud service allows you to perform backups directly to
the cloud and restore full or granular information directly from the cloud. You can
backup and recover directly from the cloud with an online backup and recovery
service, a form of (Software as a Service) SaaS application.
Like other SaaS applications, online backup is an alternative to an on-premise

software application. With a single workflow, the Backup Exec private cloud
services can carry out a local backup and then perform a set copy operation from
the local backup to the cloud deduplication storage. Backup Exec clouds helps you
to remotely manage backup for your offices.
19

17
Backup appliance
A backup appliance is a purpose-built, all-in-one solution that integrates storage
hardware and backup software, providing a standardized backup infrastructure for
one or multiple offices.
The Backup Exec Appliance simplifies the backup problem through a unified
install and configuration process. The hardware and software elements of the
backup solution are integrated, and are installed and configured through a single,
simple process. Software is pre-configured on appliances, often with a simple
licensing model.
20

18

Hybrid backup solution

You may decide deploying a hybrid backup solution, consisting of a combination
of software, appliance, and cloud.
You can perform local backups to a disk appliance, and then with the help of
Symantec Backup Exec.cloud, send a second copy of the data to a secure off-site
storage location in the cloud at a vendors data centre. You can also use backup
software for the data centre and deploy an appliance for a remote office.
21

19
Key benefits
The following are the key benefits of Backup Exec 2012:

Unified virtual and physical backup
Backup Exec 2012 with V-Ray technology offers flexible backup and
recovery capabilities, deduplication, and policy management across
VMware, Hyper-V, and physical server environments. The V-Ray
technology enables backup of entire virtual guests and recovery at the
virtual machine, virtual disk, application, and file or folder level. Backup
Exec 2012 also supports advanced hypervisor features with both VMware
and Hyper-V. V-Ray technology offers unmatched visibility into virtual and
physical machines and applications.
The agentless or agent-based virtual protection gives you the flexibility to
choose the level of recoverability you need in your VMware or Hyper-V
environment.
Backup Exec 2012 provides backup and recovery for the latest Windows
environments and applications, including Windows 2008 R2, Exchange
2010 SP1, MS-SQL Server 2008 R2, and SharePoint 2010.
Backup Exec 2012 provides comprehensive disk and tape storage for
virtual, physical, and application backup.
You can reduce storage by up to 90 percent with deduplication, lowering
storage costs across all your physical and virtual backups.
Backup Exec 2012 includes High Availability for virtual applications with
Virtual Machine Auto-Recovery for VMware.
22

110

23
One product, any recovery

Integrated bare-metal disaster recovery gives administrators the power to
recover an entire server to an entirely different hardware, from backup
copies of that server.
You can convert backups to virtual machines for instant recovery so that if
a server fails, you can get that server back up and running in a VMware or
Hyper-V environment instantly.
Granular recovery for physical and virtual applications eliminates
redundant backups for Exchange, Active Directory, SharePoint, and SQL
Servers in virtual environments.
Eliminates complexity
Streamlined administration console makes it easier to set up backups,
perform disaster recoveries, and convert backups of servers to virtual
machines for instant disaster recovery.
You can easily manage Windows data centres, VMware, Hyper-V
environments, and remote offices from one console.
Backup Exec 2012 eliminates redundant backups for Exchange, Active
Directory, SharePoint, and SQL servers in virtual environments.
Backup Exec 2012 automatically configures backup and restore operations
with intelligent defaults, which helps you protect your data and
applications with minimal effort.

111
Essential Backup Exec components
Backup Exec consists of components that work together to provide complete

backup and restore functionality to the entire network. The components that are
contained in a basic Backup Exec environment include the following:
A Backup Exec server is the heart of a Backup Exec installation.
The server is a Windows server that:
Runs the Backup Exec software and services that control backup and
restore operations
Is attached to and controls storage hardware
Maintains the Backup Exec database, media catalogs, and device catalogs
The Backup Exec Administration Console is the interface you use to control a
Backup Exec server. You can run the Administration Console directly on a
Backup Exec server or from a remote system.
Storage devices attached to the Backup Exec server contain the media on
which backup data is written. Backup Exec supports many different types of
devices and media, including disk-based and tape-based.
Clients are the systems that contain the data which the Backup Exec server
backs up. They include file servers and database servers.
24

112

Operational functionality
You use the Backup Exec Administration Console to interact with Backup Exec
for tasks, such as submitting backups, restoring data, configuring storage, and
monitoring jobs. You can run the Administration Console from the Backup Exec
server, which is a Windows server on which Backup Exec is installed, or from a
remote computer. After backups, restores, or other operations are created, the
Backup Exec server processes the jobs or delegates the jobs for processing in
multi-Backup Exec server environments.
25

113
Core features: Resource-centric

Backup Exec 2012 has a brand-new user interface that features a resource-centric
model. The server-centric model enables you to effortlessly back up and restore
servers and multi-server distributed applications. With Backup Exec's new tabs,
you can navigate throughout the main areas of the application quickly to monitor
and configure backup and restore jobs.
Backup Exec 2012 is resource-centric and focuses on the servers that are being
backed up rather than jobs, policies, and selection lists.
Backup Exec 2012 enables you to simultaneously manage and monitor multiple
servers by creating server groups. Server groups are displayed on the left of the
user interface.
If you select a server group, the servers within the group are displayed. Status
information is available at a glance and includes the server name, server-specific
alerts, the server status, the last 7 days of backups, the last backup, and the next
scheduled backup. You can use the toolbar at the top to add servers, and server
groups, and to perform backups and restores. To view detailed information about a
server, double-click the server name or select the server and click the Details
button.
26

114

Backup Exec 2012 Licensing: Agents
The slide lists the licensing scheme for Backup Exec 2012 agents.
27

115
Backup Exec 2012 Licensing: Options
The slide lists the licensing scheme for Backup Exec 2012 options.
28

116

Backup Execs agents and options

Backup Exec agents and options enhance and extend platform and feature support
for Backup Exec 2012 Small Business Edition, Backup Exec 2012, Backup Exec
2012 V-Ray Edition and Backup Exec Appliance environments.
Backup Exec provides scalable easy-to manage backup and recovery protection for
Windows based environments. Backup Exec agents and options easily expand any
Backup Exec environment to support critical applications, databases, and storage
configurations.
Backup Exec agents
29
Backup Exec provides scalable easy-to manage backup and recovery protection for
Windows based environments. Backup Exec agents and options easily expand any
Backup Exec environment to support critical applications, databases, and storage
configurations.
Agent for Applications and Databases
With Backup Exec 2012, Agent for Applications and Databases integrates and
enables one of the following agents to be installed per server:
Agent for Enterprise Vault provides a disaster recovery solution for
Enterprise Vault archived data.
Agent for Lotus Domino provides seamless backup and restore of Lotus
Domino servers.
Agent for Microsoft Exchange Server supports backup and restore for your
Microsoft Exchange Server data.

117
Agent for Microsoft SharePoint allows backup and restore of all files and
attributes that are associated with a SharePoint installation.
Agent for Microsoft SQL Server supports backup and restore of Microsoft
SQL Server data.
Agent for Oracle Servers provides the ability to initiate backup and restore
operations for Backup Exec or from the RMAN console as a Database
Administrator (DBA).
Agent for Microsoft Active Directory lets you restore the objects and
attributes from Microsoft Active Directory, Active Directory Application
Mode, and Active Directory Lightweight Directory Services while the
Active Directory sever is online.
Agent for VMware and Hyper-V
The new Agent for VMware and Hyper-V combines the Agent for VMware and
Agent for Microsoft Hyper-V into a single sku.
Agent for Microsoft Hyper-V provides complete backup and recovery of
both online and offline Hyper-V virtual machines and the Hyper-V host.
This agent is installed on the Hyper-V host and licensed per Hyper-V host.
Agent for VMware provides the complete backup and recovery of both
online and offline VMware virtual machines. This agent is licensed per
ESX host computer.
Remote Media Agent for Linux
The Remote Media Agent for Linux lets you back up and restore local and
remote servers to tape drives, robotic libraries, or disk-based backup
locations that are attached to a Linux server. This agent requires a Backup
Exec server running on Windows for job and media management functions.
Backup Exec options
The slide displays the Backup Exec options available in Backup Exec 2012:
Deduplication Option provides an integrated data deduplication solution that
optimizes storage and reduces backup redundancy.
Enterprise Server Option combines the Advanced Disk Backup Option,
Central Admin Option, and the SAN Shared Storage Option.
Central Admin Server Option installs the Central Administration server
component of the Central Admin Server Option (CASO). CASO provides
centralized administration and job load balancing for existing or newly
configured Backup Exec servers. Managed Backup Exec servers are
centrally managed and monitored from the central administration server.
Advanced Disk-based Backup Option enables additional disk-based
backup features for Backup Exec servers.
Exchange Mailbox Archiving Option, 10-user license provides archiving of
Microsoft Exchange server e-mails that have been backed up with the Backup
Exec Agent for Microsoft Exchange Server.
File System Archiving Option provides archiving of Windows NTFS data,
which is backed up.
30

118

31
NDMP Option enables Backup Exec to use the Network Data Management
Protocol (NDMP) to initialize and control backups and restores on NetworkAttached Storage (NAS) devices. This option is licensed per NAS device.
Storage Provisioning Option enables support for configuring, managing, and
monitoring a storage array that is attached to the Backup Exec server.

119
Terminology changes in Backup Exec 2012

The table lists the terminology changes in Backup Exec 2012:
Simplified Disaster Recovery (SDR)
Intelligent Disaster Discovery (IDR) is replaced with Simplified Disaster
Recovery (SDR) in BE 2012.
Backup Exec server
The computer on which Backup Exec is installed and where the Backup Exec
services are running.
Managed Backup Exec server (MBES)
The computers that a Central Administration Server manages when the Central
Admin Server Option is installed.
32
Legacy backup-to-disk folder and disk storage

Backup-to-disk folders are now read-only in Backup Exec. You can restore data
from the folders, but you cannot store backup data to them.
Agent for Windows (AW)
Formerly known as Remote Agent for Windows Systems (RAWS).
Agent for Linux (AL)
Formerly known as Remote Agent for Linux or Unix Servers (RALUS)
Agent for Mac (AM)
Formerly known as Remote Agent for Macintosh Systems.

120

Backup Exec architecture

This topic describes the structure of different Backup Exec environments.
Stand-alone Backup Exec server
The slide displays a stand-alone Backup Exec server configuration. In this

configuration, you have a single Backup Exec server that is assigned the standalone Backup Exec server role. Each server runs the Backup Exec software and the
services that control backup and restore operations. Each Backup Exec server
maintains its own Backup Exec database, media catalogs, and device catalogs.
33

121
Central Admin Server Option (CASO) configuration

The Symantec Backup Exec Central Admin Server Option (CASO) enables a
Central Administration server to delegate jobs to managed Backup Exec servers
across the network. Job delegation is the automatic load balancing of jobs across
available managed Backup Exec servers in the CASO environment.
All backup information in the CASO environment can be centralized on the
Central Administration server. The managed Backup Exec servers perform the
actual processing of backup and restore jobs. You create jobs on the Central
Administration server and then delegate the jobs to run on a managed Backup
Exec server.
The jobs are delegated across the available storage devices on the managed
Backup Exec server. Multiple Backup Exec servers can share a storage device
when sharing is enabled. Centralized restore jobs can also be delegated to managed
Backup Exec servers.
34
The Central Administration server can also function as a managed Backup Exec
server and process delegated jobs. A managed Backup Exec server can also run
jobs that are created locally at its local administration console.

122

Central Admin Server Option to the Cloud

The Backup Exec server located at the customers location is configured as the
Managed Backup Exec server, with the CAS located in the private cloud. This
configuration provides Backup Exec Administrators the ability to manage remote
Backup Exec installations from a Central Admin Server located at their central
data center.
This configuration does require secure network connectivity between the cloud
CAS and the remote managed Backup Exec servers when running any jobs,
including backups and restores to storage devices at the remote location. You can
create offsite duplicate copies by establishing a secure VPN between the local
Managed Backup Exec servers and cloud CAS servers using OpenVPN. The set
copy jobs can then execute on the cloud CAS, which copies data from the local
storage device to the shared cloud CAS deduplication storage device.
35

123
Enterprise Server Option configuration

The Enterprise Server Option, or ESO, is new to Backup Exec 2012. It is a
compilation of the Central Admin Server Option, or CASO, Advanced Disk-based
Backup Option, or ADBO, and Shared Storage Option, or SSO.
The Enterprise Server Option is licensed per CAS. ESO eliminates the licensing
requirement of entering SSO licenses for primary and secondary servers. With the
addition of ADBO into that licensing option, there is no dependency on anything
in ADBO upon the SSO or CAS.
ADBO can be used on up to five Backup Exec servers. For a simpler configuration
of managed and distributed servers, previously existing Shared Storage Option
installations are integrated to CASO.
36

124

The Central Admin Server Option is installed as part of the Enterprise Server
Option. After you type license information for the Enterprise Server Option, on
the Configure Options panel, you must expand the Backup Exec Options item,
and then expand the Enterprise Server Option item to select the Central Admin
Server Option for installation. When you select the Central Admin Server
Option for installation, the central administration server is installed. After the
central administration server is installed, you can install managed Backup Exec
servers. Note that you must use the custom installation option in the installation
wizard to install CASO. The typical installation option does not support the
installation of CASO. As you can see, CASO and ADBO installation states are
selected individually. CASO and ADBO are licensed under ESO but the
installation state is still set by the user.
Configuring MBES
37
The Managed Backup Exec Server, or MBES, is licensed with a Backup Exec
license. Note that QuickStart and Small Business Edition licenses do not activate
MBES. When you select the option to install MBES, an updated MBES
configuration dialog box is displayed. If you select the Unrestricted access to
catalogs and backup sets for restore option, MBES is configured as an SSO
Secondary server. The SSO secondary prompt has been moved to this new dialog
box. If you do not select this option, then BE is configured as a plain MBES. The
dialog box has been re-edited with new options that help you understand and
choose the best MBES configuration. The newly added More Information button
launches an online help file detailing all MBES configuration options.

125
Backup Exec in a SAN environment

Some enterprise-level Backup Exec environments operate across a Storage Area
Network (SAN) in which storage devices are shared by multiple servers. The
Backup Exec Central Admin Server Option (CASO) enables you to share storage
devices and media between multiple Backup Exec servers in a SAN environment.
In a CASO configuration contained within a SAN environment:

Media and catalogs are shared between the Central Admin Server and any
Managed Backup Exec (MBE) servers, when the option Unrestricted access
to catalogs and backup sets for restore is configured on the Managed
Backup Exec server during install. When configured with this model, Backup
Exec allows the restore of data from any Managed Backup Exec server that is
configured with this option as long as the jobs that were run were sent to a
shared device.
A shared device database (ADAMM) resides on one Backup Exec server (the
CASO server), which enables all Managed Backup Exec servers on the SAN to
obtain a single, unified view of all shared devices and media.
The shared ADAMM database also arbitrates all device and media requests
from the SAN Backup Exec servers, maximizing hardware usage.
Jobs can be run normally on each Backup Exec server, but only the CASO
server controls job delegation to the Managed Backup Exec servers.
38

126

The slide displays the Centrally managed Backup Exec server with Unrestricted
access to catalogs and backup sets for restore option.
39

127
BE Appliance: Single-site scenario

A common scenario for the Backup Exec 3600 Appliance is the single site
scenario. In this scenario, the Appliance replaces the traditional Backup Exec
server constructed from hardware and software components from different
vendors, manually combined to form a backup server. The Appliance is deployed
in a single site environment and configured with remote Backup Exec agents
deployed to the physical and virtual protected server resources.
Backup jobs are constructed and assigned to the protected server resources, and
backup data sets are copied, as per the job schedule, to the disk storage system of
the Appliance. From there, backup data is copied offsite. This is accomplished
either by copying backup sets to removable USB media, or by copying backup sets
to a remote resource, such as a network B2D folder. Backup Exec Appliance also
supports tape backup.
40

128

BE Appliance: Sister-site and remote office scenarios

Another scenario for the Backup Exec 3600 Appliance is the sister-site or disaster
recovery site scenario. In this example, a Backup Exec 3600 Appliance is
configured at each site, with remote agents deployed to protect physical and virtual
server resources. Backup data sets from protected servers are captured at each site
and stored to the disk system of the Appliance at that site.
These backup sets are also copied or duplicated between the Backup Exec 3600
Appliances, ensuring that each Appliance contains the complete backup data set
taken from both sites. In such a scenario, one of the Backup Exec 3600 Appliances
must be promoted to the role of central administration server or CAS, to ensure
that catalogs are efficiently managed. Another advantage of the CAS is that the
operations of both Appliances can be controlled and operated from the single CAS
console.
41
The other key scenario supported by the Backup Exec 3600 Appliance is the
remote office scenario. Distributed organizations with server infrastructure at
remote sites struggle to effectively protect and back up servers at remote sites. It
commonly includes the problem of managing tape media at remote sites. This
problem can be addressed by implementing a Backup Exec 3600 Appliance at
each of the remote sites. At each remote site, server backup data is stored to the
Backup Exec 3600 Appliance.

129
In this scenario, a central administration server must be present. In most cases, the
Backup Exec server at the central data center would play this role. In both the
sister site and remote office scenarios, backup data is transferred in deduplicated or
compressed form, reducing bandwidth requirements and speeding up the data
movement process.
When large amounts of backup data need to be replicated to another Appliance or

up stream to a Backup Exec server, it may be beneficial to seed the target
device or server with a bulk of the initial data that needs to be copied. This seeding
process allows each WAN duplication event to only transfer the delta changes.
42

130

43

131
44

132

Lesson 2
Installing Backup Exec 2012
45
46

22

Installing the Backup Exec server

This topic describes how to perform a complete installation of a Backup Exec
server.
Installation overview
47
The recommended method to install a Backup server is to use the installation

wizard provided on the Backup Exec installation DVD. Before installing the
software, you must prepare the following:
The server to which you are installing the software
Ensure that your Backup Exec server meets the requirements as outlined in the
Symantec Backup Exec 2012 Administrators Guide. Refer to the
Administrators Guide and the Symantec Support Web site for technical
information concerning system requirements, upgrading from previous
versions of Backup Exec, Backup Exec database location and options, and
potential conflicts with third-party software.
The backup environment
Verify that your environment is configured properly and that storage devices
are supported and functional.
Administrator requirements
Ensure that you have the necessary account information and rights as well as
the necessary Backup Exec licenses. With Backup Exec 2012, you can install
all the agents and options using the Symantec License Files (.slf). You may

Lesson 2 Installing Backup Exec 2012
23
receive Symantec License Files in an e-mail with your license certificate or

you may need to visit the Symantec Licensing Portal Web site to obtain the
files.
48

24

Installation methods
You can install Backup Exec using the following methods:
Installation wizard
The Backup Exec installation wizard guides you through the process of installing
Backup Exec and its agents and options. After Backup Exec is installed, you can
install additional agents and options from the Backup Exec user interface. The
computer on which Backup Exec is installed is called the Backup Exec server. You
can install additional agents and options on the Backup Exec server or push-install
Backup Exec or the Agent for Windows (AW) to remote computers.
49
You can install AW on a client system joined to an Active Directory network

without a transform. A transform contains changes that you want to make to the
Agent for Windows Windows Installer package when a computer starts, such as
installation path, and which computers to publish to.
If you install Backup Exec through Terminal Services and the installation media is
on a shared drive (network share) you must use a UNC path. Installation by
mapped drives is not supported. You can set up multiple server installations as
Backup Exec processes up to five remote computer installations at the same time.
DVD/ISO
Run Browser.exe from the installation DVD/ISO.

25
Push-installation
Additionally, you can install the Remote Administrator, which lets you
administrate the Backup Exec server from a remote Windows server or
workstation.
50

26

Backup Exec Service Account
Backup Exec services on the Backup Exec server run in the context of a user
account configured for the Backup Exec system services. You can create this
account during installation (by defining a user name and password), or you can use
an existing user account.
51
The Backup Exec services account has rights to perform the following functions:
Authenticate as any user and gain access to resources under any user identity.
Create a token object that can be used to access local resources.
Log on as a service.
Exercise full administrative rights on the Backup Exec server.
Back up and restore files and directories.
Manage auditing and security logs.
Log on as a batch job in Windows 2008 and higher.
If you plan to use an existing account, the slide lists some guidelines that apply to
different environments. You can use Windows security with the Backup Exec
services account. How you configure security depends on how your network is
configured.

27
Backup Exec Database

Each Backup Exec server uses a database (most commonly referred to as the
Backup Exec database) that maintains critical information about the backup
environment served by a Backup Exec server.
The Backup Exec database is a critical component of Backup Exec, so proper
maintenance and protection of the database are essential for any data protection or
disaster recovery plan.
The Backup Exec database runs under MS-SQL Server 2005 Express Edition
which is installed with Backup Exec, unless you choose to use another SQL Server
instance. The database contains the two files, as displayed on the slide, and is
installed in the ..\Program Files\Symantec\Backup Exec\Data\
directory. To protect a Backup Exec server installation, you must configure a
backup job that regularly backs up the database backup files, catalogs, and license
files.
52
The .slf files are located at:

For Windows 2008 and newer: %programdata%\Symantec
Shared\Licenses
For Windows 2003: %CommonProgramFiles%\Symantec
Shared\Licenses

28

Installation logs: bkupinst2012.htm

Backup Exec creates an installation log file, named Bkupinst2012.htm, when
you install Backup Exec and when you install patches. This log file can help you
troubleshoot installation problems. The log file provides links to Technotes for the
most common errors. If you install the Agent for Windows, a log file called
RAWSinst2012.htm is also created.
In addition, the text in the log file uses the following colors so you can identify
warnings and errors:
Black indicates normal operations
Orange indicates a warning message
Red indicates error messages
53
The Bkupinst2012.htm file is located in the following locations:

For Windows 2003: C:\%allusersprofile%\Application
Data\Symantec\BackupExec\Logs?
For Windows 2008 and later: C:\ProgramData\Symantec\Backup
Exec\Logs

29
Installation requirements
This topic discusses the minimum system requirements to run this version of
Backup Exec.
To ensure your system meets all requirements for installing Backup Exec
(including agents and options), refer to the hardware compatibility list (HCL) and
the software compatibility list (SCL), available from the Symantec Support Web
site:
SCL URL: http://entsupport.symantec.com/umi/V-269-1
HCL URL: http://entsupport.symantec.com/umi/V-269-2
54

210

Operating system requirements

The minimum software requirements to run Backup Exec 2012 Media and CASO
servers are listed on the slide.
You cannot install a Backup Exec server on a computer that runs the Microsoft
Windows Server 2008 Server Core operating system. However, you can install the
Backup Exec Agent for Windows on the Microsoft Windows Server 2008 Server
Core operating system.
55
In addition, you cannot install SQL Express or SQL Server 2005 on a computer
that runs the Microsoft Windows Server 2008 operating system and is configured
as a Read Only Domain Controller, or RODC. The Read Only Domain Controller
role does not allow you to use the local accounts, which are required for SQL
Express and SQL Server 2005. When you install Backup Exec on an RODC
computer, you must select a remote SQL instance for the Backup Exec database.

211
Basic hardware requirements

The slide lists the basic hardware requirements for Backup Exec 2012.
RAM and disk space requirements may vary depending on the operations
performed, the agents and options installed, and the specific system configuration.
Symantec recommends a Virtual memory of 20 MB above the Windows
recommended size for total paging file size.
The Backup Exec database and catalogs require additional space on the disk.
Backup Exec requires at least one storage media drive or single-drive robotic
library and the appropriate controller card. You can also use removable storage
devices and non-removable hard drives.
The Library Expansion Option enables support for each additional drive in a
robotic library. In addition, support is included for every single-drive Virtual Tape
Library, or VTL. To support additional drives in each VTL, you can purchase the
Virtual Tape Library Unlimited Drive Option.
56

212

Miscellaneous requirements
57
Before installing Backup Exec 2012, you need to perform the following tasks:
Check the name of the computer on which you want to install Backup Exec.
The name must use only standard ANSI characters. You may encounter errors
if you install Backup Exec on a computer with a name that uses non-standard
characters.
Check the Windows security settings to ensure that they work properly with
the Backup Exec Service Account.
Ensure that third-party software, using Backup Exec ports, is configured
correctly.
Install the storage device hardware such as controllers, drives, and robotic
libraries on the Backup Exec server. Use the appropriate Windows hardware
setup functions to configure your controller and storage devices.
If the drive on which you want to install Backup Exec is encrypted or
compressed, and you want to use a default SQL Express database, verify that
an unencrypted and uncompressed drive is available for the SQL Express
installation.

213
Backup Exec server push-installation requirements

This slide describes the pre-requisites for installing Backup Exec 2012 to remote
computers.
To push-install Backup Exec 2012 to a computer that runs the Microsoft Windows
Server 2003 operating system, you must enable File and Printer Sharing on the
Windows Firewall Exceptions list for the ports listed on the slide. For more
information about the Windows Firewall Exceptions list, refer to your Microsoft
Windows documentation.
During the installation process, Backup Exec sets the Remote Launch and remote
access security permissions for the Administrators group. You must also enable
the Allow remote administration exception group policy for the computer and
Windows Management Instrumentation to which you push the installation.
To push-install Backup Exec to a computer that runs the Microsoft Windows

Server 2008 operating system, you must enable File and Printer Sharing and
Windows Management Instrumentation, or WMI, on the destination computers
Windows Firewall Exceptions list.
58
To push-install Backup Exec to a computer that runs Symantec Endpoint

Protection, or SEP, version 11.0 or later, configure SEP to share files and printers.
The File and Printer Sharing feature is turned off by default.

214

Pre-installation tasks and checks
59
Before installing Backup Exec, perform the following tasks:

1 Install the storage device hardware, such as controller, drives, and robotic
libraries, on the Backup Exec server. Refer to the documentation included with
your storage device hardware for installation instructions.
2 Run the Backup Exec Environment Check on the computer on which you want
to install Backup Exec. The Environment Check analyzes the computer to
ensure that the installation process can complete. If Backup Exec finds
configuration issues that can be fixed during the installation, or that may
prevent the installation, warnings are displayed.
3 Check the Windows security settings and ensure that the settings work
properly with the Backup Exec service account.
4 Verify that an unencrypted and uncompressed drive is available for SQL
Express installation, if the drive on which you want to install Backup Exec is
encrypted or compressed.
5 Ensure that the name of the computer on which you want to install Backup
Exec complies with the ANSI standards.
6 If you want to install Backup Exec to a non-English version of Microsoft
Windows, download the SQL Express Service Pack 4 setup file from the
Microsoft Web site before installing Backup Exec.
7 Finally, exit all other programs.

215
Running the Environment Check utility

The Symantec Backup Exec for Windows Servers Environment Check is a utility
that scans a machine targeted for installation and reports on requirements such as:
System requirements and logon privileges
Third-party software compatibility
Required components compatibility with Backup Exec
Previously installed versions of Backup Exec and Backup Exec options
Storage devices attached to the system and their associated drivers
Each test the utility performs is reported as Passed, Failed, or Warning. Failures
and warnings can prevent Backup Exec from installing correctly, so you must
correct the identified issues and run the Environment Check utility again before
installing the Backup Exec server. The Environment Check utility runs
automatically as part of the installation process, but you can run it manually before
you install Backup Exec or before you back up data with Backup Exec.
60
Symantec recommends running the Environment Check on the Backup Exec

server and on all remote computers that are to be protected.

216

Installing the Backup Exec server

The Backup Exec provides two methods of installation, typical and custom
installation.
A typical installation is a simpler installation method than a custom installation
and is designed for small or uncomplicated environments. For example, if you use
a local Backup Exec server and a few Backup Exec agents or options, then a
typical installation may be the best option for you.
A custom installation is designed for large or complex environments. You can also
use the custom installation method if you prefer to set all of your options. For
example, if you use a remote Backup Exec server or use the Enterprise Server
Option, you must perform a custom installation.
61

217
Typical installation
A typical installation is designed for small or uncomplicated environments. In a
typical installation, Backup Exec 2012 makes several decisions for you, based on
common installation scenarios. With a typical installation, Backup Exec is
installed to a local Backup Exec server and SQL Express is installed with the
default instance. Agents and options are installed if you type the license keys for
them. Before you install Backup Exec, ensure that you have valid license keys for
Backup Exec and any agents or options that you want to install. Note that you can
install a trial version of Backup Exec without a license key.
To perform a typical installation of Backup Exec, perform the following steps:

1 Start the installation program and expand the Backup Exec node, and then
click Install.
2 On the Installation Type screen, select Typical Installation and then click
Next.
62

218

Review the results displayed in the Environment Check screen. The

Environment Check runs automatically when you install Backup Exec. If any
serious issues, stop the installation process, correct the issues, and then start the
installation process again.
4 In the Add Licenses screen, type the serial number. You can either type the
serial number manually, or import your Symantec License Files (.slf) from a
network share or from a local drive. If you install a trial version of Backup
Exec 2012, a serial number is not required.
63

219
In the Service Account screen, type the user name, password, and domain
name for an account with local administrative privileges for the Backup Exec
services to use. Backup jobs use these credentials by default.
6 In the Installation Review screen, review the installation summary and then
click Install. The installation process creates an installation log file named
bkupinst2012.htm on the computer where Backup Exec 2012 is
installed. If you install Backup Exec on remote computers, you can select to
push-install either Symantec Backup Exec or the Agent for Windows on the
selected machine.
64

220

Custom installation
A custom installation is designed for large, complex environments, or for
customers who prefer to set all their options for their environment.
For example, if you use a remote Backup Exec server or use the Central Admin
Server Option, you must perform a custom installation. You can select the
additional options that you want to install in your environment. If you want to
install Backup Exec 2012 for any additional languages, select the language.
In a custom installation, you can select a location to store the Backup Exec
database. However, you cannot change the database location during the upgrade
process. Additionally, you can select how the Symantec Device Driver Installer
must install the device drivers.
65

221
Selecting additional options

You can install agents and options when you install Backup Exec 2012. However,
when you have already installed Backup Exec and want to install additional agents
and options, review the documentation for those agents and options to ensure that
your system meets all minimum requirements. You may stop the Backup Exec
services while you install the additional agents and options. If any active jobs are
running, you are prompted to stop them, or to wait for the jobs to finish
To install additional Backup Exec agents and options to the local Backup Exec
server:
1 Click the Backup Exec button, select Installation and Licensing and then
select Install Options and Licenses on this Backup Exec Server.
2 Select the additional options that you want to install and then click Next.
Agents and options other than the standard features require the purchase of
additional licenses. Installing the trial version enables the agents and options,
which must be purchased separately and are not included as part of the core
product. If you have a licensed version of Backup Exec, you can use a trial version
for most Agents and Options for a period of 60 days.
66

222

Selecting Backup Exec Database

The Backup Exec installation program installs Microsoft SQL Server 2005
Express Edition components that are required to run Backup Exec. Backup Exec
prompts you to do one of the following:
Install the required Microsoft SQL Express components with Backup Exec and
create a default Backup Exec instance, named BKUPEXEC.
Select a Microsoft SQL Server 2005 (SP4) or SQL Server 2008 instance that
already exists on the network on which you want to run Backup Exec.
During the installation process and the upgrade process, Backup Exec stops and
starts the SQL service. Other user-created databases that use the SQL Server
instance are unavailable during the process. To avoid such conflicts, you must
install Backup Exec into its own SQL instance.
67
If you choose to install Backup Exec into an existing SQL 2005 instance, make
sure that SQL 2005 Service Pack 4 or later is installed before you continue with
the installation.
When Backup Exec is installed into an existing instance, the automated Master
database restore feature is not available. To recover the Master database, you must
replace it with the Master database copy that Backup Exec automatically creates
and updates when the Master database is backed up.

223
Note: If you are installing a managed Backup Exec server, it is recommended that
you select a local Microsoft SQL Server 2005 (SP4) instance or later on
which to install the Backup Exec Database for this managed server. Do not
select the same SQL Server instance that is used by the Central
Administration Server.
68

224

Tape Device Drivers

Symantec recommends installing the Symantec tape device drivers for most
supported devices that are attached to the server. If you choose not to install the
Symantec drivers, you can use existing Microsoft or OEM drivers instead.
Use the Symantec Device Driver Installation Wizard to install Symantec tape
device drivers.Before you install Symantec tape device drivers, do the following:
Ensure that Backup Exec supports the tape device.
You can find a list of compatible types of storage at the following URL:
http://entsupport.symantec.com/umi/V-269-2
Run the Windows Device Manager to ensure that it lists the tape device.
69
You can also install Symantec tape device drivers by running tapeinst.exe,
which is located in the Backup Exec installation directory.
You must run tapeinst.exe locally on the Backup Exec server where you
want to install tape device drivers. You cannot use tapeinst.exe to pushinstall tape device drivers to remote Backup Exec servers.

225
Remote Administrator
You can manage your Backup Exec environment from a remote server or
workstation using the Remote Administrator. The Remote Administrator is
essentially a Backup Exec Administration Console that is logged on to the Backup
Exec server you want to manage. All functions performed within the Remote
Administrator console are executed on the Backup Exec server.
The Remote Administrator and the Backup Exec server to which it is connecting
must be the same version of Backup Exec.
70

226

Installing Remote Administrator
You can install the Remote Administrator from the Backup Exec installation DVD.
From the installation DVD browser, select the option to install Symantec Backup
Exec and continue through the program until you reach the option to install the
Remote Administration Console only.
71
To install the Remote Administrator, perform the following steps:

1 From the installation media browser, click Installation.
2 Click Backup Exec.
3 On the Welcome panel, select I accept the terms of the license agreement,
and then click Next
4 On the Installation Type panel, select Custom installation, and then click
Next.
5 Check Local Installation, and then click Install Remote Administration
Console only.
6 Click Next.
7 On the Destination panel, do the following:
a Review the disk space requirements for the installation.
b To change the location where the files are installed, click Change to select
another directory for the installation.
8 Click Next.
9 Review the installation summary, and then click Install.
10 Click Finish.

227
Using Remote Administrator

The Remote Administrator lets you administer the Backup Exec server from a
remote Windows server or workstation.
When you launch the Remote Administrator, you can select which Backup Exec
server you want to access. You may be prompted for a user name and password to
browse some network shares. Provide a domain-qualified user name and password
when prompted.
You can also configure options for low speed connections, logon credentials for
the Backup server, and network (domain) settings.
To run the Remote Administrator, perform the following steps:

1 Click Start > Programs > Symantec Backup Exec.
2 If you are connecting to a Remote Administration Console from a Backup
Exec server, click the Backup Exec button, and then select Connect to Backup
Exec Server.
3 Select the appropriate Backup Exec server options, and click OK.
72

228

Licensing scheme
Before deploying Backup Exec, you must determine the appropriate number of
licenses you require.
When you install Backup Exec, you can choose not to type any serial number in
order to preview the different agents and options available to Backup Exec for 60
days. When this evaluation period expires, you must provide a valid license file in
order for Backup Exec to continue operating.
Robotic library licensing
73
When you install Backup Exec, support for the first drive in every robotic library is
included. For each additional drive in a robotic library, you must purchase a
Library Expansion Option (LEO) license. LEO enables support for multi-drive
tape or optical robotic libraries and library storage systems. When you use the
Advanced Device And Media Management features, the Library Expansion
Option provides extensive configuration and management capabilities that include
unattended backup and restore operations, and bar code reader and portal support.
Device partitioning enables you to assign specific robotic library slots for backup
targets. Backup Exec displays a warning if the number of enabled devices exceeds
the number of licenses.

229
Licensing summary
Select one of the following methods to enter licenses:
Manually entering serial numbers
You can type the serial numbers that are listed on your license certificate. Serial
numbers contain one letter and 10 numbers, such as M0123456789. After you add
your serial numbers, Backup Exec polls the Symantec Web service to verify the
serial numbers.
To enter the serial number manually, perform the following steps:

1 In the Serial Number field, type the appropriate serial number from your
license certificate.
2 Click Add.
3 Repeat the steps for each serial number, for each option or agent that you want
to install.
4 Click Next to validate the serial numbers.
74
Importing a Symantec License File

You can import your Symantec License Files (.slf) from a network share or
from a local drive or USB drive.
Installing a trial version of Backup Exec
A 60-day trial version is available for Backup Exec and many of its agents and
options. If you do not type any serial numbers or import Symantec license files
during the installation process, a trial version is installed, along with the trial
versions of many of the agents and options.

230

Note: An Internet connection is required to validate the serial numbers. If you do

not have an Internet connection, import the licenses from the Symantec
License File or install a trial version.
75

231
Validate the serial numbers and select the products you want to install.
76

232

Basics of an .slf file

You can receive Symantec License Files in an e-mail with your license certificate
or you can visit the Symantec Licensing Portal Web site to obtain the files. From
the Symantec Licensing Portal Web site, you receive one file with all the serial
numbers that have been registered. In an e-mail, you receive multiple files with
one serial number in each file.
After installation, the .slf files can be found at the following locations:
In Windows 2003: %CommonProgramFiles%\Symantec
Shared\Licenses
In Windows 2008 and later: %programdata%\Symantec
Shared\Licenses
77

233
Launching Backup Exec 2012

This topic describes how to use the Backup Exec Administration Console.
Backup Exec Administration Console
You launch Backup Exec by double-clicking the shortcut on the desktop (if you
chose to install the shortcut during installation) or by selecting Start > Programs
> Symantec Backup Exec > Backup Exec 2012.
The Backup Exec Administration Console is the main interface you use to manage
Backup Exec features and monitor Backup Exec activity.
The administration console screen includes the following components:
Backup Exec button
The Backup Exec button is displayed on the upper left side of the administration
console. To display the options in the Backup Exec button, click the Backup Exec
button, select the menu name, and then select an option.
78
Tabs
Tabs appear across the top of your screen and enable you to navigate to Backup
Execs views. The Backup Exec 2012 comprises of the following views or tabs:
Home
Backup and Restore
Storage
Reports

234

Ribbon
You can use the items in a group to initiate actions such as creating a new backup
job or configure storage.
Columns
You can change the location of columns by dragging and dropping them. In
addition, you can right-click a column to select the columns you want to make
visible, configure column settings, or sort the columns.
Selection pane
The Selection pane is where you select items to work with, such as servers to back
up or restore.
Status bar
The status bar appears on the bottom of the administration console and provides
information about the Backup Exec server, jobs running or scheduled to run, alerts,
and services running.
79

235
Home view
The Home view on the Backup Exec administration console is a central location
from which you can quickly access or view the Backup Exec features.
The Home view consists of several customizable panes. These panes provide
critical information in a visual form so that you do not have read too much text.
You can add or remove the panes using the check boxes in the ribbon. You can also
drag and drop the panes, as required. The Home tab contains Backup Exec data
and links to features.
You can configure the layout, and hide or display items in the System Health and
the Support groups.
Layout group
The Home view is available in four different layouts, which you can change using
the ribbon. You can select one of the following layout configurations to display the
items on the Home tab:
80

236

Item
Description
One Column
Displays the Home tab items in one column.
Two Columns
Displays the Home tab items in two columns.
Narrow/Wide
Displays the Home tab items in two columns

with a narrow panel and a wide panel.
Three Columns
Displays the Home tab items in three

columns.
The Reset Home Tab restores the contents of the Home tab to the default
configuration.
System Health group
The items in the System Health group provide overviews of alerts, backup jobs,
backup size data, storage, and the Symantec ThreatCon Level. You can select the
items to display on the Backup Exec Home tab.
Support group
The items in the Support group provide technical support, documentation,

licensing and maintenance contracts, and the Symantec RSS Reader resources.
You can select the items to display on the Backup Exec Home tab.
81

237
Backup and Restore view

The Backup and Restore view provides a list of servers from which you can
backup and restore data. This view combines the Job Setup view and the Job
Monitor view from Backup Exec 2010. The backup and restore view is now the
standard view.
Backup Exec 2012 displays the server list in a Standard view and a Compact
view. You can use the Compact view to display a larger number of servers in the
list.
Backup Exec 2012 is resource-centric and focuses on the servers that are being
backed up rather than jobs, policies, and selection lists. Backup Exec 2012 enables
you to simultaneously manage and monitor multiple servers by create server
groups. Server groups are displayed on the left of the user interface. If you select a
server group, the servers within the group are displayed. Status information
includes the server name, server-specific alerts, the server status, the last 7 days of
backups, the last backup, and the next scheduled backup. You can use the ribbon at
the top to add servers, and server groups, and to perform backups and restores.
82
To view detailed information about a server, double-click the server name or select
the server and click the Details button.

238

83
The different tabs available in the Backup and Restore view are:
The Jobs tab contains information related to scheduled backup and restore jobs
for the server.
The Job History tab contains information related to the backup and restore
jobs run for the server.
The Backup Sets tab lists all the backup sets created for the server. Backup
Exec browses catalogs to display this information.
The Active Alerts tab displays alerts or messages that have resulted from any
kind of server activity. After you respond to an alert, Backup Exec moves it to
the alert history. To view the alert messages that have moved to the alert
history, click the Show Alert History button.
The Credentials tab displays information related to various credentials used to
access the server.
The Properties tab displays the server properties. Note that you can click the
Servers button, to navigate to the earlier level.

239
Storage view
The Storage view in Backup Exec 2012 provides information about each storage
device that you configure. It combines the Devices, Media, and CASOs Backup
Exec servers views from Backup Exec 2010. The Storage view is now the standard
view.
You can also see a compact view by selecting the Compact option from the
ribbon.
You can see information about the storage capacity of a device by moving the
mouse pointer over the device capacity field. You can also double-click each
storage device to view details, such as properties, usage, and error statistics
84

240

The slide depicts the storage details view for the selected storage device, which is
Disk storage 0001 in this case. The different tabs available in the Storage view are:
The Jobs tab contains information related to the jobs scheduled for the storage
device.
The Jobs History tab contains information related to the jobs performed using
this storage device.
The Backup Sets tab lists all the backup sets created using the storage device.
The Active Alerts tab displays messages related to the storage device.
The Properties tab displays the storage device properties.
85

241
Sorting and filtering information

You can customize the information that displays on the Backup and Restore tab
and on the Storage tab.
You can do any or all of the following actions:

Choose a default configuration that Backup Exec provides, such as Servers
with Active Jobs or Failed Jobs.
Specify a sort order for the columns that appear in the views.
Specify the values that you want to use to filter the information that Backup
Exec displays.
Specify the columns that you want to appear and the order in which they must
appear.
Create and save a configuration to use again.
86

242

Reports view
The Reports tab enables you to view, run, and manage reports. You can use this
view to create a custom report. Backup Exec 2012 enables you to print or save a
report, as required. Reports can be viewed and printed in the following formats:
PDF
HTML
XML
Microsoft Excel (XLS)
Comma Separated Value (CSV)
87
The different groups available in the Reports view are:

The See Completed group displays scheduled reports that have completed
running. You can view the report later on by double-clicking the report name.
Backup Exec 2012 enables you to print or save a report, as required.
The See Upcoming group displays reports that are scheduled to run on a
specific date and time.
The Custom group displays custom reports that you create using the New
Custom Report Option from the ribbon.
The Archive group displays reports that provide information about the Backup
Exec activities that are related to the Backup Exec Archiving Option.
The Configuration group displays reports that provide information about
configuration changes and statuses of Backup Exec features and options. There
are four standard Configuration reports.

243
88
The Jobs group displays reports that provide information about various
Backup Exec job-related activities. There are 16 standard Job-related reports.
The Media group displays reports that provide information about the various
types of media that Backup Exec uses. There are 10 standard Media-related
reports.
The Devices group displays reports that provide information about the various
types of devices that Backup Exec uses. There are four standard Device-related
reports.
The Alerts group displays reports that provide historical information about the
alerts that Backup Exec generates. There are two standard Alert reports.

244

Backup Exec menus

Backup Exec 2012 provides a simpler user interface to help you manage your
backup environment. The changes to the user interface, in terms of layout,
navigational elements, and usability, are notably visible. Backup Exec 2012
replaces the global configuration menus with resource-centric configurations.
Backup Exec 2012 is uncomplicated and straightforward to use because only those
options that are relevant to the task being performed are displayed.
The task pane that was on the left in earlier versions of Backup Exec is now
replaced with an easy-to-use ribbon at the top in Backup Exec 2012.
The Backup Exec button is displayed on the upper left side of the administration
console. To display the options in the Backup Exec button, click the Backup Exec
button, select the menu name, and then select an option.
89

245
Updating Backup Exec 2012

This topic describes the procedure to update Backup Exec 2012.
Symantec LiveUpdate fundamentals
Symantec LiveUpdate is a Symantec technology that can poll the Symantec Web
server to check if any updates, upgrades, or new versions are available for a given
Symantec product. Using LiveUpdate, you can download Backup Exec updates
automatically or manually. By default, LiveUpdate checks for updates every
Sunday night at 10pm. If there is an update, LiveUpdate notifies you with an alert.
The automatic update option only searches for Backup Exec updates. LiveUpdate
uses HTTP as the primary method to download files from the Internet.
The most recent version of LiveUpdate is installed with Backup Exec. If a

previous version of LiveUpdate is on the server, Backup Exec upgrades it.
90
If Backup Exec updates are available on the Symantec Web server, LiveUpdate
downloads and installs the updates on the Backup Exec server. It also determines if
computers on which the Agent for Windows is installed have the latest updates. If
you do not have the latest updates you receive an alert to install the updates.
LiveUpdate does not update remote agents directly. You must copy or push-install
the updates manually to computers on which remote agents are installed.
Any files installed by LiveUpdate are recorded in Backup Execs installation log
file (Bkupinst2012.htm). You can use the LiveUpdate Administrator Utility
with LiveUpdate. This utility enables an administrator to modify LiveUpdate so

246

that network users can download program and virus definition updates from an
internal server rather than going to the Symantec LiveUpdate server over the
Internet.
91

247
Configuring LiveUpdate
You can configure LiveUpdate settings through the LiveUpdate applet in the
Windows Control Panel. The LiveUpdate configuration dialog box has five tabs:
General settings define how you want to run LiveUpdate, using either the
Interactive Mode or the Express Mode.
FTP settings specify the FTP settings that LiveUpdate uses if it is unable to
communicate using HTTP.
HTTP settings define how LiveUpdate accesses the LiveUpdate Server. You
can select:
The same HTTP proxy server settings as Internet Explorer
Custom HTTP proxy server settings specifically for LiveUpdate
No proxy server
ISP settings enable you to configure LiveUpdate to use your defined Internet
settings or customize Internet Settings specifically for LiveUpdate.
Update Cache sets the maximum amount of disk space used to store updates.
92

248

Identifying available updates

The new Backup Exec 2012 user interface enables you to visually identify the
agents that need patches. You can accomplish this by viewing the alert messages or
by inspecting the patch information reported for the server.
To initiate a patch installation job, use the Update button in the graphical user
interface or, alternatively, the Update menu item.
You can select multiple resources as part of the patch installation job. The patch
installation job dialog box enables you to run a patch installation job immediately
using the Run Now option or schedule the job to run later. The completed patch
installation job, as any other Backup Exec job, is displayed in the job history along
with its job log.
93

249
LiveUpdate Warning alert
In Backup Exec 2012 and earlier versions, the Backup Exec server updates its
clients only after it is patched itself. The Backup Exec server is patched using
LiveUpdate, which puts the Remote Agents out-of-sync with the Backup Exec
server. As a result, an Alert message is generated through the following process:
Instops.dll installed on the AW machine provides a comma-delimited list
of patch GUI IDs.
The Patch list is advertised to the Backup Exec servers.
BEUpdateOps.exe executes a Check For AW Updates task periodically to
verify if AW and the Backup Exec server are synchronized.
If AW and the Backup Exec server are not synchronized, a SOFTWARE
UPDATE WARNING alert is generated and posted.
BEUpdateOps.exe also loads instops.dll to get the information it
needs regarding patches.
94
Backup Exec 2012 generates LiveUpdate alerts that notify you if any of the servers
are not up-to-date and have not installed the most recently available patch. As in
earlier versions of Backup Exec, an alert message is generated for each patch that
needs to be installed. The alert message contains information about the patch that
is to be installed.

250

Scheduling automatic updates

When you schedule automatic updates through Backup Exec, the settings apply
only to updates for Backup Exec. Changes that you make to the LiveUpdate
schedule for Backup Exec do not affect the schedule for any other software
applications that use LiveUpdate.
At the scheduled time, LiveUpdate automatically connects to the appropriate Web

site, and then determines if your files need to be updated. Depending on the
options that you select, Backup Exec either downloads and installs the files in the
proper location or sends an alert to notify you that updates are available.
95
To schedule automatic updates using LiveUpdate:

1 Click the Backup Exec button, select Configuration and Settings, and then
select Backup Exec Settings.
2 In the left pane, select LiveUpdate.
3 Complete the appropriate options.
4 Click OK.

251
Scheduling updates for Remote Agent

Additionally, in Backup Exec 2012, a new Install Utility Job type enables you to
schedule jobs to update existing Agents with the latest patches. The Install Utility
Job also supports installing the Remote Agent to a target system or resource.
Thus, after the LiveUpdate session, the restart of services initiates the Resource
Discovery task for validating the Remote Agent. The process of validating the
remote agent updates the files as displayed on the slide.
The Validate Remote Agent runs on Resource Discovery schedule which, by

default, is set to a specific time once a day. This schedule can be changed. Backup
Exec checks for patches on the Remote Agents that need to be updated. When
missing patches are discovered on the Remote Agents, the Update button is
enabled.
96

252

Upgrading to Backup Exec 2012

This topic describes the Backup Exec 2012 upgrade paths.
Upgrade basics
Backup Exec 2012 introduces a resource-centric, simplified-feature graphical user
interface. This impacts jobs, policies, and selection lists from earlier Backup Exec
versions.
Jobs that contain multiple systems are now split into several jobs. Each job
contains only one system or database application; all non-recurring backup jobs
are converted to backup definitions or backup definitions. Significant schema
changes, new data creation, data mapping, data deletion, existing data
modifications, and data movement occur during the job migration process.
97
After an upgrade completes, the user may have more jobs and scripts. New jobs
have the similar schedule as the old jobs from which they split. However, they do
not have job logs and job history information.

253
Upgrade paths
Backup Exec 2012 and the Agent for Windows 2012 support upgrades from the
following versions of Backup Exec:
Symantec Backup Exec 12.5 for Windows Servers
Symantec Backup Exec 2010
Symantec Backup Exec 2010 R2
When you upgrade from an earlier version to Backup Exec 2012, Symantec
recommends that you install the latest available patches for the Backup Exec
version in use prior to initiating the upgrade process.
Note: With Backup Exec 2012, Symantec Desktop and Laptop Option is a
standalone desktop and laptop backup and recovery solution; it replaces the
Backup Exec Desktop and Laptop Option.
98

254

Upgrade details
When you upgrade, Backup Exec automatically converts your existing definitions,
configurations, and jobs to the current version.
After the migration process completes, Backup Exec displays a Data Migration
report, which displays how the jobs were migrated. Due to the new backup
paradigm, some of the jobs may be combined, split, or moved. The Data Migration
report is available for viewing from the Backup Exec Administration Console at
any time after the migration has completed.
Note: Symantec recommends that you review the Data Migration report
thoroughly to determine how your existing jobs have changed and how you
may need to adjust your jobs manually.
99
Rolling upgrades can be only performed on Backup Exec 2010 R3 Service Pack 2
and later. The Backup Exec 2012 Central Admin Server Option server can
communicate with Backup Exec 2010 R3, with the most recent service packs, for
the purpose of rolling upgrades. Backup Exec 2012 can communicate with Backup
Exec 12.5 Remote Agent for Windows Systems and later.
Note: You need to enter the new Backup Exec 2012 licenses during the upgrade
process.

255
A Remote Administration Console that uses a previous version of Backup Exec

cannot be used with a Backup Exec server on which the current version is
installed. For example, a Backup Exec 2010 Remote Administration Console
cannot manage a Backup Exec 2012 Backup Exec server. Backup Exec 2012
supports installations of the Remote Administration Console for:
Symantec Backup Exec 2010
100 256

Viewing the Data Migration Report

The Data Migration report lists the ways in which your previous jobs were
changed during the migration to Backup Exec 2012. The Data Migration report is
available for viewing from the Backup Exec Administration Console at any time
after the migration has completed.
To view the Data Migration report, click the Backup Exec button, select
Installation and Licensing, and then select Post-Migration Report.
101

257
102 258

Lesson 3
Storage Devices
103
104 32

Devices and media

This topic lists the storage devices that Backup Exec supports.
Supported storage types
105
There are different general categories of devices supported by Backup Exec.

Disk-based storage is a general category of storage mechanisms, in which data
are digitally recorded by various electronic, magnetic, optical, or mechanical
methods on a surface layer deposited of one or more planar, round and rotating
disks (or discs) (also referred to as the media).
In other words, disk-based storage is any hard drive space that is visible to the
BE server across the network. It can be a local hard drive or RAID array or a
network attached storage (NAS) or storage area network (SAN) device.
A deduplication disk is a location on a hard drive that reduces the size of
backups by storing only unique data.
A network storage system maintains copies of digital data across high-speed
local area network (LAN) connections. It is designed to back up files,
databases and other data to a central location that can easily accessed via
standard network protocols and tools.
Tape storage includes external storage devices, usually both readable and
writable, often used for backing up and archiving data.
Storage pools consist of similar types of storage devices that enable loadbalancing of Backup Exec jobs. The workload is shared across the storage
device pool. You can send backup jobs to specific storage devices or to a

Lesson 3 Storage Devices
33
storage device pool. If the specific storage device is busy, the job must wait
until the storage device becomes available.
If you are running Backup Exec in a SAN environment AND you are using the
Central Admin Server Option (CASO), devices can be shared. If you are not using
CASO, you must install the Shared Storage Option (SSO) in order to share
devices.
For a complete and current list of all devices supported by Backup Exec, refer to
the device compatibility list located in the Backup Exec section of the Symantec
Enterprise Support site: http://www.symantec.com/business/
support.
106 34

Disk-based storage
Symantec recommends that you use disk storage to back up data to a disk.
Data backed up to disk can be copied to tape or to cloud-based storage for long
term retention.
Features of disk-based storage include the following:

Automatic discovery of locally accessible disk volumes.
Disk space monitoring. Alerts are sent when the disk space thresholds that you
set are reached.
Storage trending analysis that provides predictions of low disk space for disk
storage and virtual disks.
107
Disk-based storage that you can configure in the Configure Storage wizard are as
follows:
Disk storage includes a location on a locally attached internal hard drive, a USB
device, a FireWire device, or a network-attached storage device.
Disk cartridge storage is storage that usually remains attached to the server while
you remove the media. Disk cartridges use disk cartridge media such as an RDX
device, or devices that are displayed in Windows as removable storage, such as
USB thumb drives.
Deduplication disk storage is a location on a hard drive that reduces the size of
backups by storing only unique data. Deduplication devices are available with
purchase of the Deduplication Option.

35
Storage arrays are disk arrays that contain multiple disk drives that support data
redundancy and failover.
Virtual disks are virtual disk storage media that consist of multiple physical disks
in a storage array.
A vault store is disk storage for the archived data that the Backup Exec Archiving
Option archives from target servers.
In previous versions of Backup Exec, the backup-to-disk feature let you back up
data to a folder on a hard disk. These legacy backup-to-disk folders are now readonly. You can continue to inventory, catalog, and restore data from a backup-todisk folder. You can use remote Simplified Disaster Recovery to perform a disaster
recovery from backup-to-disk folders. You cannot send backup data to a disk
storage folder.
108 36

Disk storage
Disk storage is a location on a locally attached internal hard drive, a USB device, a
FireWire device, or a network-attached storage device to which you can back up
data. You do not need to manage media when you keep backup data on disk
storage.You specify how long you want to keep the data that you back up to disk
storage when you create a backup job. Backup Exec automatically reclaims the
disk space as the backup data expires. If you want to keep the backup data longer
than the period that you specify when you create the backup job, you should create
a duplicate backup job. A duplicate backup job copies the backup data from the
original storage device to tape or to disk cartridge, which you can then send for
long-term or off-site storage.
109
You must use the Configure Storage wizard to create disk storage. In the
Configure Storage wizard, Backup Exec provides a list of disks on which you
can create disk storage. The disks do not appear in the list in the alphabetical order
of the drive letter. Instead, the disk that appears first in the list has the most amount
of disk space. You can select any disk that you want, but the disk that Backup Exec
recommends for use appears at the top of the list. The disk that you use as the
system drive always appears last in the list. Symantec recommends that you do not
configure disk storage on the system drive.
To be eligible for configuration as disk storage, a disk must have at least 1 GB of
disk space and cannot be configured as deduplication disk storage. Although you
can configure disk storage and deduplication disk storage on the same disk, it is
not recommended.
When you create disk storage on a disk that is attached to the network, you must

37
specify the path to an existing share. The Backup Exec service account must have
read and write permissions on the remote computer on which the network share is
located.
Note: Before you create the disk storage on a network share, you must give read
and write permissions to the Backup Exec service account. The Backup
Exec service account is on the Backup Exec server that you want to access
the network share.
When you create disk storage, Backup Exec lets you specify any of the following
locations on a local disk:
Volumes with or without drive letters.
You can create only one disk storage on a volume.
Unformatted partitions.
Backup Exec formats and partitions the drive for you, if necessary.
Drives that do not have partitions.
Backup Exec creates a folder named BEControl on the root of the volume. Do
not delete or edit the contents of the BEControl folder, and do not copy it to
other volumes or drive letters.
In Windows Explorer, the backup files that the disk storage device contains display
with a .bkf file extension. Each disk storage device also contains a file named
changer.cfg and a file named folder.cfg, which store information about
the backup files. Do not delete or edit the changer.cfg or folder.cfg files.
A sub-folder with a prefix of IMG in the name may display in a disk storage
device. This sub-folder appears if the option to enable Granular Recovery
Technology (GRT) was selected for backup, or if you select the disk storage device
as storage for backup data.
110

38

Legacy backup-to-disk folder

In previous versions of Backup Exec, the backup-to-disk feature let you back up
data to a folder on a hard disk. These legacy backup-to-disk folders are now readonly. You can continue to inventory, catalog, and restore data from a backup-todisk folder. You can use remote Simplified Disaster Recovery to perform a disaster
recovery from backup-to-disk folders.
You cannot send backup data to a disk storage folder. Symantec recommends that
you use disk storage to back up data to a disk.
In Windows Explorer, the disk storage folders display in the path you specified
when you added the folders. The disk storage files display with a .bkf file
extension. Each disk storage folder also contains a file named changer.cfg and
a file named folder.cfg, which store information about the disk storage files.
111
Note: Do not delete or edit the changer.cfg or folder.cfg files.

A sub-folder with a prefix of IMG in the name may display under a disk storage
folder.
In previous versions, Backup Exec created this sub-folder when the following
conditions were met in a backup job:
The option to enable Granular Recovery Technology (GRT) was selected.
A backup-to-disk folder was selected as storage for the backup data.

39
Disk cartridge devices

Disk cartridges are a type of storage that usually remains attached to the Backup
Exec server while you remove the media, such as RDX. If you are not sure if the
storage has removable media, you can open the Computer folder on your Windows
computer. The devices that contain removable media are listed.
You can manage how long Backup Exec keeps data that is stored on disk cartridge
media by associating the media with media sets. You create media sets that specify
append periods, overwrite protection periods, and vaulting periods.
You must use the Configure Storage wizard to configure a disk cartridge device
and to create new media sets. When you install Backup Exec, system-defined
media sets are created by default.
112

310

Deduplication disk storage

Deduplication disk storage provides a disk-based backup folder that you can use as
a destination for backup jobs. When you use deduplication disk storage, only
unique data is stored.
Before you create a deduplication disk storage device, you should review the
requirements. Symantec requires a dedicated volume and minimum of 8 GB of
free RAM for deduplication disk storage.
Note: You can create only one deduplication disk storage device per Backup
Exec server.
113
A deduplication disk storage device is added from the Configure Storage wizard.
In the wizard, you can choose to create a new deduplication disk storage device or
to import an existing device from a different Backup Exec server. If you choose to
import an existing device, you must enter information about the user account that
was used to create the device originally on the other Backup Exec server. After you
create a deduplication disk storage device, it appears on the Storage tab. A
deduplication disk storage device cannot belong to any storage pools to prevent a
deduplication job from being sent to a non-deduplication device in a storage pool
if the deduplication disk storage device is busy.
You can pause, enable, disable, rename, refresh, and delete a deduplication disk
storage device. When you use Backup Exec's Delete option on a deduplication disk
storage device, the folder is removed from the Backup Exec Database. However,
the folder and the files in it remain on the disk.

311
Note: When you delete backup sets from a deduplication disk storage device, it
may take up to 48 hours for more space to become available. Backup Exec
cannot always calculate the amount of space that will be made available.
If you use Backup Exec Central Admin Server Option, a deduplication disk
storage device can be shared between multiple Backup Exec servers. Sharing can
be enabled when you add a deduplication disk storage device. You can select new
Backup Exec servers to share deduplication disk storage or remove the sharing
ability for Backup Exec servers at any time.
Deduplication disk storage can be created on a storage array. However, if a
deduplication disk storage device already exists on a Backup Exec server, then
another device cannot be added to a storage array that is connected to that Backup
Exec server.
Deduplication devices are available with purchase of the Deduplication Option.
114

312

Storage array
Storage array is a method for storing information on multiple devices.
After you install the Storage Provisioning Option, use the Configure Storage
wizard to configure a storage array for use with the Backup Exec Storage
Provisioning Option (SPO).
Backup Exec then submits a Configure Storage Array job to create the virtual
disks.
115
Note: In a Central Admin Server Option (CASO) environment, run the

Configure Storage wizard from the central administration server. You can
run the Configure Storage wizard for any managed Backup Exec server
that has SPO installed. Managed Backup Exec servers can share a single
storage array but cannot share a virtual disk on a storage array.

313
Virtual disks
A virtual disk is a logical disk that you create on a storage array to provide virtual
storage to the Backup Exec server.
You can use any of the following to create a virtual disk:
The Configure Storage wizard
The management tools that the vendor of the storage array provides
The Microsoft Storage Manager for SANs management tool
If you create a virtual disk with a tool other than the Configure Storage wizard,
you must configure the virtual disk for use with Backup Exec. After you configure
a virtual disk, Backup Exec uses it as a destination device for jobs. Backup Exec
automatically adds configured virtual disks to the Any virtual disk storage device
pool.
116
In the Configure Storage wizard, you specify the number of virtual disks to
create from the physical disks that are in the storage array. The Backup Exec server
cannot access the physical disks. The Backup Exec server can access only the
virtual disks that you create.
Backup Exec uses a configured virtual disk in the same manner in which it uses a
disk storage device.
Backup Exec does not assign a drive letter to the virtual disk. You cannot browse
for a virtual disk or access it from a command prompt. Since you cannot browse to
the virtual disk, you cannot back it up with Backup Exec. Symantec recommends
that you create a duplicate backup data job to move the data from the virtual disk

314

to another device. For example, you can move the data to a tape device or to
another virtual disk on a separate storage array.
Backup Exec provides three low disk space thresholds for the virtual disks. As
available disk space reaches each threshold, Backup Exec sends an alert. When the
available disk space on the virtual disk reaches the third threshold, the alert warns
you to create more disk space immediately.
117

315
Vault store (for Archive Option)

A vault store is a disk-based container for the archived data that Backup Exec
archives. When you add an archive stage to a backup job, you select a vault store
as the storage device to which you want to send the archived data. A vault store
contains at least one vault store partition that is the physical location where the
archived items are stored. You can create additional vault store partitions for a
vault store when it requires more disk space.
Each vault store has an associated database. The database holds information about
the archives in the vault store and all the items that are stored in each archive. For
example, when an item is archived, the vault store's database is updated with this
information. Single instance storage-related information is contained in the
fingerprint databases for all of the vault stores.
Archiving is available with the purchase of the Backup Exec Archive Option.
118

316

Network storage
Network storage options that you can configure in the Configure Storage wizard
are as follows:
NDMP servers are network-attached storage that supports the Network Data
Management Protocol to allow the use of devices that are attached to the servers.
OpenStorage devices are Network-attached storage used by the deduplication
option, that supports Symantec's OpenStorage technology.
Cloud storage is Networked, online storage in the cloud.
119
A Remote Media Agent for Linux Server lets you back up data from remote
computers to the storage devices that are directly attached to a Linux server. You
can also back up to a simulated tape library on a Linux server. This storage device
requires the purchase of the Remote Media Agent for Linux Servers.

317
OpenStorage devices
OpenStorage is a Symantec technology that allows intelligent disk devices to
integrate with Backup Exec.
Some intelligent disk devices can include multiple logical storage units. However,
each logical storage unit is added as a single OpenStorage device. When you add
an OpenStorage device, Backup Exec can automatically locate the logical storage
units on that device.
120 318
Note: When you delete or erase the media from an OpenStorage device, it may
take up to 48 hours for more space to become available. Backup Exec
cannot always calculate the amount of space that will be made available.
OpenStorage devices are added from the Configure Storage wizard. After you
add an OpenStorage device, it appears on the Storage tab. An OpenStorage device
cannot belong to any storage pools to prevent a deduplication job from being sent
to a non-deduplication device in a storage pool if the OpenStorage device is busy.
OpenStorage devices are used by the deduplication option, that supports
Symantec's OpenStorage technology

If you use Backup Exec Central Admin Server Option, an OpenStorage device can
be shared between multiple Backup Exec servers. Sharing can be enabled when
you add an OpenStorage device. You can select new Backup Exec servers to share
an OpenStorage device or remove the sharing ability for Backup Exec servers at
any time.
121

319
Tape drives and robotic libraries

Tape storage that you can configure in the Configure Storage wizard is as
follows:
Stand-alone tape drives including storage that uses a tape cartridge for reading
and writing data.
Robotic libraries including storage that contains tape drives, slots, and an
automated method for loading tapes.
Virtual tape libraries that are network attached storage configured to emulate tape
libraries.
Tape devices write data to and read data from removable magnetic tapes, such as
Digital Linear Tape (DLT) and Linear Tape-Open (LTO) cassettes.
122 320
Stand-alone tape drives rely on operator intervention to change tapes.

Robotic libraries and tape stackers are high-capacity data storage systems for
storing, retrieving, reading, and writing multiple magnetic tape cartridges. Such
libraries contain storage racks for holding the cartridges and a robotic mechanism
for moving the cartridge to the drives. Some robotic libraries contain a media
access port (MAP), a cartridge access port (CAP), or a mail slot to allow adding
and removing tapes. Consider that some enterprise-level libraries can hold
thousands of tapes and dozens of tape drives. For example, a library can contain
6,000 tapes and 24 drives in one robot.
Many robotic libraries also contain a bar-code reader used to read bar-code labels
on the tapes. This helps Backup Exec inventory and manage the media contained
in the library.

Libraries come in many different sizes and configurations. You can have small
libraries that hold a dozen tapes and have one or two tape drives. You can also
have enterprise-level libraries that hold hundreds of tapes and several tape drives.
When you install Backup Exec, it automatically recognizes all tape storage that is
attached to the Backup Exec server. Tape storage includes tape drives, robotic
libraries, virtual tape libraries, and simulated tape libraries.
When you install Backup Exec, support for the following items is included:
The first tape drive per robotic library.
Every single-drive virtual tape library.
Support for additional tape drives in robots or libraries are available with the
Library Expansion Option and the Virtual Tape Library Unlimited Drive Option.
You can use the Configure Storage wizard to perform the following actions for
tape storage:
Partition robotic library slots.
Replace or add hot-swappable storage on a Backup Exec server without having
to restart the server.
Create media sets to manage the backup data on tapes.
Library Expansion Option
When you install Backup Exec, support for the first drive in every robotic library is
included. The Library Expansion Option enables support for each additional drive
in a robotic library.
Note: Backup Exec includes support for one drive in every robotic library. Each
additional drive in a library requires a Library Expansion Option license.
You can find a list of compatible devices at the following URL:
http://entsupport.symantec.com/umi/v-269-2
You can find license information for the Library Expansion Option at the
following URL:
123

321
Virtual tape library

Virtual tape libraries, or VTLs, are disk arrays that emulate a tape library with
multiple tape drives. These are identified by the VTL label.
Virtual tape library Unlimited Drive Option
When you install Backup Exec, support for every single-drive virtual tape library
is included. The Virtual Tape Library Unlimited Drive Option enables support for
all additional drives in each virtual tape library. To install the Virtual Tape Library
Unlimited Drive Option, add a license.
http://entsupport.symantec.com/umi/v-269-2
124 322

Using the Hot-Swappable Device wizard

Use the Hot-swappable Device wizard to replace or add hot-swappable storage
on a Backup Exec server without having to restart the server.
If you remove and then reconnect Universal Serial Bus (USB) tape devices to the
USB port, you must run the Hot-swappable Device wizard to allow Backup Exec
to rediscover the devices.
For iSCSI-attached devices, you must list the device as a Persistent Target in the
iSCSI control panel applet, and then run the Hot-swappable Device wizard.
Listing the device as a Persistent Target lets Backup Exec rediscover the device
whenever you restart the Backup Exec server.
125
After you start the Hot-swappable Device wizard, you are prompted to close the
Backup Exec Administration Console. The Hot-swappable Device wizard waits
until any jobs that were processing are completed. The wizard pauses the Backup
Exec server and stops the Backup Exec services. You can then add or replace any
storage devices. The wizard detects the new device or replaced device, and adds
information about the device to the Backup Exec Database. The wizard is then
completed, and you can reopen the Backup Exec Administration Console.
Any new storage appears in the Storage tab, and usage statistics for the storage
begin accumulating. You can enable the new storage in a storage device pool.
Any replaced storage appears in the Storage tab, in the All Storage view with a
status of Offline.

323
Configuring storage devices

This topic describes how to configure devices from within the Backup Exec
Administration Console.
Storage view: Overview
The Storage view has replaced the old Devices, Media, and Media Servers views.
On the Storage tab, Backup Exec provides overview information for each storage
device that you configure. You can also double-click each storage device to view
details, such as properties, usage, and error statistics.
126 324

Interpreting Storage view information

In the views, Name indicates the name of the storage device. By default, Backup
Exec provides a name for the storage device based on the type of storage and an
incrementing number, such as Disk storage 0001. You can change the name of the
storage device in the storage properties.
State indicates the state of the storage device, such as if it is online, offline,
disabled, or if services need to be restarted.
Active Alerts indicates that an event or condition in Backup Exec has occurred for
which a message is displayed or a response is required.
Storage Trending indicates the estimate for the number of days of backup that are
left for disk storage and virtual disk storage.
127
Capacity indicates the amount of disk space that is used for disk storage on the
Backup Exec server.
Compression displays the ratio of the uncompressed size of a file over its
compressed size.
Jobs indicates the jobs that have been sent to this storage.

325
Configuring devices using the Configure Storage wizard

This section discusses the different storage objects that the Configure Storage
wizard configures.
Use the Configure Storage wizard to set up different types of storage to which
you can back up data. The Configure Storage wizard creates the storage that uses
the best possible defaults for your environment. However, you can customize the
defaults in the storage properties.
Configure Storage on the Storage tab launches the Configure Storage wizard.
After Backup Exec is installed and the Backup Exec services are started, any
storage that is attached to the Backup Exec server is automatically detected.
However, you must use the Configure Storage wizard to configure the storage for
backups.
128 326
Configuring disk storage using Configure Storage wizard

In Backup Exec 2012, the Configure Storage wizard creates the storage that uses
the best possible defaults for your environment. However, you can customize the
defaults in the storage properties.
The different types of storage that you can configure using the Configure Storage
wizard are as follows:
Disk-based storage
Network storage
Tape storage
Storage pools

This section explains how to configure disk storage using the Configure Storage
wizard.
On the Storage tab, click Configure Storage.
129

327
The Configure Storage wizard displays the different storage options that you can
configure using the wizard. Select Disk-based storage and click Next. The wizard
then displays the different disk-based storage options that you can configure.
Select Disk storage and then click Next.
130 328

On the next screen, type the name of the disk storage and a brief description. Click
Next. Select the location for the disk storage device, and then click Next.
131

329
On the next screen, the wizard displays the Storage configuration summary. Verify
the information data that you provided and then click Next. Read the message in
the window and then click OK.
The disk storage is added and is displayed under All Storage.
132 330

Low disk space thresholds

Backup Exec provides three low disk space thresholds for the virtual disks. As
available disk space reaches each threshold, Backup Exec sends an alert. When the
available disk space on the virtual disk reaches the third threshold, the alert warns
you to create more disk space immediately.
Selecting the low disk space threshold option prevents a job from being written to
the disk-based storage device when the disk space threshold that you specify is
reached.
Jobs that are running when the threshold is reached will complete, but no further
jobs can be written to the disk-based storage device.
133

331
Importing a legacy backup-to-disk folder

You must import an existing backup-to-disk folder into Backup Exec 2012 to
restore data from it. When you import a backup-to-disk folder, you cannot use the
root of a volume or an administrative UNC share as the path. The administrative
shares are ADMIN$, IPC$, and one for each local disk drive letter, such as C$, D$,
and so on.
For example, you cannot use D:\ or \\OtherServer\C$\B2D7, but you can
use D:\B2D. If you create a share named B2DOnMyDriveC on OtherServer,
then you can use \\OtherServer\B2DOnMyDriveC or
\\OtherServer\B2DOnMyDriveC\Dir1.
Use the Configure Storage wizard to import a legacy backup-to-disk folder.
134 332
Re-creating a legacy backup-to-disk folder and its contents

If you have deleted a backup-to-disk folder from Backup Exec, but not from the
disk, you can recreate the backup-to-disk folder and the files in it. You must know
the name and path of the original backup-to-disk folder to retrieve it. If you deleted
a backup-to-disk folder from the disk, you cannot recreate it.

Managing devices
This topic discusses device pools, which is a method of grouping devices for
Backup Exec operations. There are two types of device pools: basic and cascaded.
When referring to devices, note that each drive within a robotic library is treated as
a device. The entire robotic library itself is also considered as a device.
Storage device pools
A storage device pool is a group of similar types of storage devices that enables
load-balancing of Backup Exec jobs. The workload is shared across the storage
device pool. You can send backup jobs to specific storage devices or to a storage
device pool. If the specific storage device is busy, the job must wait until the
storage device becomes available.
135
When you send a job to specific storage devices, Backup Exec cannot
automatically route the job to the next available storage device. When you submit
a backup job to a storage device pool, the job is automatically sent to an available
storage device in that pool. As other jobs are created and started, they can run
concurrently on other storage devices in the storage device pool. By dynamically
allocating storage devices as jobs are submitted, Backup Exec processes jobs
quickly and efficiently. Storage device pools provide fault tolerance if you
configure error-handling rules to resubmit a job that fails because of a storage
device error.

333
When you configure a new storage device, Backup Exec automatically adds it to
the appropriate storage device pool. Backup Exec also detects attached storage
devices and adds them to the appropriate storage device pool. However, you must
edit the properties of the pool and check the check box next to the device before
jobs can use that device in the pool.
You can perform the following actions for the storage device pools that you create:
Edit the storage pool properties to check the check box next to the storage
devices that you want to use in the pool.
View or filter data to display, such as jobs, job history, and active alerts.
You can view any storage device pools that you create on the Storage tab, under
All Storage Pools.
Backup Exec automatically creates some storage device pools and adds any
storage devices that you configure to the appropriate storage device pool. You
cannot edit any properties or storage devices in the storage device pools that
Backup Exec creates. You can select these storage device pools when you select
the storage for a backup job.
Storage device pool example
The slide contains a description of how a storage device pool works. When a
backup job is submitted to a device pool, the job is automatically sent to the first
available storage device in that device pool. If a job is set up to use a specific
device pool and no device in that pool is available, the job waits for the next
available device in that pool, and then uses that device.
As other jobs are created and started, they run concurrently on other storage
devices in the device pool. By dynamically allocating drives as jobs are submitted,
Backup Exec processes jobs quickly and efficiently.
136 334

Creating device pools in Backup Exec

Use the Configure Storage wizard to create storage device pools. You can view
any storage device pools that you create on the Storage tab, under All Storage
Pools.
To create a storage device pool

1 On the Storage tab, in the Configure group, click Configure Storage.
2 Select Storage pools, and then click Next.
137

335
138 336
Follow the on-screen prompts.

Edit the storage device pool properties, and check the check boxes next to the
devices that you want to use in the pool. Then, follow the subsequent steps.

139

337
140 338

Lesson 4
Data Management
141
142 42

Managing media
This topic introduces you to general media-related terms and concepts.

Media basics
www.dictionary.com defines a medium (the singular form of media) as an
intervening substance through which something else is transmitted or carried on
and as something...that occupies a position...midway between extremes. Taken
in context with the more familiar technical definition of media (objects or
devices, such as a disks [or tapes] on which data is stored), these definitions
suitably describe the role of media in a Backup Exec environment.
Media provide dedicated physical storage that is the destination of data in a backup
or duplication operation and is the source of data in a restore operation. Media may
be tapes or disks (fixed or removable).
With the proliferation of data in todays IT environments, media capacity and
performance have become an important consideration for backup administrators.
Because of their storage capacity and improvements in mounting and access
speeds, magnetic tapes (DLT, SDLT, LTO) have become the most common media
for backup operations. When referred to in this course, media usually refers to
tapes, but may also refer to disks. Distinctions are made, as necessary.
Media headers
Data is written to the body of a tape, but information about the datas properties is
written to the media header. This is sometimes referred to as header data.
143 Lesson 4 Data Management
43
Data Lifecycle Management Fundamentals

Data lifecycle management, or DLM, is time-based retention for fixed disk storage
and cloud storage. DLM does not manage removable disk cartridge or tapes.
Data Retention is set in the job.
The DLM process is triggered every four hours by a server or by a low storage
event.
144 44
Generally, backup data is automatically and proactively groomed if all of the

following conditions are satisfied:
The backup set has expired.
The backup set is not on-hold.
No on-hold or unexpired dependent backup sets exist.
The backup set is not in the last copy of the latest recovery chain.

Backup Set Dependencies
The backup set dependencies are as follows:

Full is dependent on itself
Incremental is dependent on previous full/incremental in the set
Differential is dependent on the last full
The following sets may be deleted during grooming, when:
it is NOT the last copy
there is a duplicate, the disk backup can be deleted
All GRT backups sets must be on the same storage
GRT backups of Exchange will not be deleted if dependencies exist, even if
copies exist
45
Benefits of DLM
The numerous benefits of DLM are as follows:

DLM uses time-based retention management policies.
Data is proactively deleted when storage is needed or when the data is expired.
Backup Exec does not delete the last recovery point set for a resource. The last
recovery point set is always maintained. However, you can delete it manually,
if required.
A backup set can be prevented from being deleted by using the Retain
functionality.
146 46

Media sets
You can logically organize media within a robotic library to suit your
environments needs. This is accomplished by organizing media into media sets.
Media sets are used to manage tape and removable disk media.
It is helpful to think of media sets as logical storage objects which implement a
retention policy on media that are assigned to them. A media set comprises a
variable number of physical media. When you define a media set, you must define
an append period and an overwrite protection period. Each tape that is allocated to
a media set adopts that media sets attributes.
Backup Exec uses the criteria you define to determine which media are available
for particular jobs. When a backup or duplication job runs, Backup Exec searches
the available storage devices for media that meet the requirements for the job.
47
System media sets

Cleaning Media lists all cleaning media.
Foreign Media lists all media that is imported from a product other than Backup
Exec.
Retired Media lists all media that you have taken out of service, usually because
of an excessive number of errors. After you associate a media with the retired
media set, Backup Exec does not select it for backup jobs. The media is still
available for restore operations, if it has not been damaged. Retired Media
protects media from being used (overwritten).
You can delete the media that is in Retired Media to remove it from Backup Exec.
You may want to delete media if you have a lot of off-site media that you do not
want to recycle. You can also delete media if you throw away the media.
148 48
Scratch Media lists all media that can be overwritten. New, blank, and erased
media are automatically associate with the Scratch Media set.
Keep Data for 4 Weeks lists all media that you associate with this media set. If
you use the backup job defaults that are set when you install Backup Exec, the
media set Keep Data for 4 Weeks is the default media set for all backup jobs. This
media set protects data from being overwritten for four weeks and allows the
media to be appended to for six days.
You can edit and rename Keep Data for 4 Weeks after installation. Therefore, it
may not continue to appear in the Media view or in the backup job defaults as
Keep Data for 4 Weeks.

Keep Data Infinitely - Do Not Allow Overwrite lists all media that you associate
with this media set. When you associate media with this media set, data is not
overwritten unless you perform any of the following actions on the media:
Erase
Label
Format.
Associate the media with the scratch media set
You can append data to this media for an infinite period (until the media is full).
You can edit and rename Keep Data Infinitely - Do Not Allow Overwrite after
installation. Therefore, it may not continue to appear in the Media view or in the
backup job defaults as Keep Data Infinitely -Do Not Allow Overwrite.
49
Media and data retention

For data recovery purposes, most media is reused multiple times because the
retention period of backups is typically short. For archiving data, media is written
to once, but it is possible that the retention period for the data may exceed the
lifetime of the media, so you must ultimately refresh the media at some point.
The append period and the overwrite protection period can help you devise a
media rotation strategy as explained in the Data Protection Methods lesson.
Append period
Append period is the amount of time that data can be appended to media. It is
measured from the time the media was first allocated. It can be specified in hours,
days, weeks, or years.
150 410
Overwrite protection period

Overwrite protection period is the amount of time that media is protected from
being overwritten. The period is measured from the time of the last write to the
media, that is, at the end of the last append or overwrite job. It can be specified in
hours, days, weeks, or years. When the overwrite protection period is over, the
media becomes recyclable and can be overwritten.
The overwrite protection period begins when the backup job is completed. If there
is an append period, the overwrite protection period begins again each time an
append job completes. Because the overwrite protection period does not begin

until the job completes, the amount of time that is required to complete the job
takes affects when the media can be overwritten. You may shorten the overwrite
protection period to take into account the amount of time a job may run.
For example, you set the overwrite protection period for seven days. You also set
the append period for four days to ensure that data is not overwritten for at least
seven days. The data can be appended to the media for the next four days. The last
data that is appended to this media is retained for at least seven days.
Note: Any media can be overwritten if the overwrite protection level is set to
None.
Your media rotation strategy must balance between the need to save data as long as
possible, and the fact that media are not in infinite supply. The media set rules
allow Backup Exec to identify which media can be written to and which media are
overwrite-protected. You should consider the use of disk storage for backup data.
151

Lesson 4 Data Management
411
How the append and overwrite protection periods relate
152 412
This diagram illustrates how the append period and the overwrite protection period
function over time on a tape. The following is the slides numbered key:
1 The append period begins when the tape is first allocated to a media set.
At this point, no data has been written to the tape, so the overwrite protection
period has not started.
2 The overwrite protection period is measured from the time of the last write to
the media.
3 Another backup job runs, so the overwrite protection periods resets.
Consider that the duration of the overwrite protection period remains the same,
but its start time resets whenever data is appended to the tape.
4 Immediately before the append period ends, another backup job writes data to
the tape, so the overwrite protection period resets again.
5 The append period ends.
While the overwrite protection period is still active, data cannot be added to the
tape, but stored data is still protected.
In the interim between the end of the append period and the end of the
overwrite protection period, the tape remains essentially static, unless it is used
for a restore operation or if it is overwritten, erased, or moved.
After the overwrite protection period expires, the tape becomes recyclable.
This means that fresh data can be written to the beginning of the tape by a new
backup job, thereby deleting any data on the tape. This recycling process
continues until the tape is retired or removed from the system completely.

Overwriting allocated or imported media for tape and disk cartridge media
Media that are associated with a media set are called allocated media. Media that
are imported from another installation of Backup Exec, or from another product
are called imported media. Backup Exec protects allocated and imported media
from being overwritten when full or partial overwrite protection is used. However,
you can let Backup Exec overwrite allocated and imported media before the data
overwrite protection period expires, and without setting the media overwrite
protection level to None.
153
The following methods are available:

Associate the media with the Scratch Media Set. The media is overwritten
when it is selected for an overwrite job.
Erase the media. Erased media is automatically recognized as scratch media
and is overwritten immediately.
Label the media. The Label Media operation immediately writes a new media
label on the media, which destroys any data that is contained on the media.
Format the media. Formatting destroys any data that is contained on the
media.
Change the overwrite protection period for the media set so that it is expired.

413
Media set properties

Properties for media sets provide information about the overwrite protection
period, the append period, and media vaults.
Name displays the name of the media set.
Description displays the description of the media set.
Overwrite protection period displays the length of time in hours, days, weeks, or
years to retain the data on the media before the media can be overwritten.
Append period displays the length of time in hours, days, or weeks, that data can
be added to media.
Media vault to use with this media set displays the media vault that stores the
media that is associated with this media set.
154 414
Move media to this vault after displays the time period after which this media is
reported as ready to be moved to this vault.
Return media from this vault after displays the time period after which this
media is reported as ready to be returned from this vault.

Labeling tape and disk cartridge media
Media labels identify the tape and disk cartridge media that you use in Backup
Exec. When new, blank, or unlabeled tape or disk cartridge media is used during a
backup operation, Backup Exec automatically labels the media. This label consists
of a prefix that identifies the cartridge type, and an incrementing number. For
example, if the media is a 4mm tape, then the prefix is 4M, followed by 000001.
The next media label generated for an unlabeled 4mm tape would be 4M000002,
and so on.
155
Another type of media label used by Backup Exec is the media ID, which is a
unique label assigned by Backup Exec to the individual media used in Backup
Exec. The media ID is used internally by Backup Exec to keep statistics on each
media. Because the media label or barcode label for media can be changed,
Backup Exec must use the media ID to preserve continuity in record keeping for
each individual media. You cannot change or erase the media ID. The media ID
has no effect on the media label, or on your ability to rename, label, or erase
media.
At times, you may need to use the media ID to distinguish the media that have
duplicate media labels. Duplicate labels can be automatically generated in
instances when Backup Exec is reinstalled or media from another Backup Exec
installation is used. Use the media ID to distinguish between duplicate labels. You
can view the media ID in a medias property page.
Write the media label on an external label that is fixed to the outside of the
physical media. Whenever you change the media label, you should also change the
external label to match.

415
The following methods are available in Backup Exec to change a media label:
The Write a new media label on the media option destroys any data on the
media.
The Rename the media option changes the name of the media in the display,
but does not write the new label to the media until an overwrite operation
occurs. The data on the media is viable until the media is overwritten.
The Edit the label option changes the name of the media in the display, but
does not write the new label to the media until an overwrite operation occurs.
The data on the media is viable until the media is overwritten.
156 416

Viewing media properties
To view the properties of any media used by Backup Exec:

1 On the Storage tab, double-click the tape drive that contains the media.
2 In the left pane, click Media Properties.
Media information
The Media information section provides identifiers and other information about
the media. You can edit the media label to change the name of the media, but this
information is updated only in ADAMM at the time of the change; the new label is
not physically written to the media until an overwrite operation occurs.
Note: Do not change the label for bar-coded media. Use the description field.
157
The media ID is the GUID (Globally Unique Identifier) assigned to the media by
Microsoft Windows. The media server stores the media ID in the media catalog
and uses it to track the media. This string is never overwritten, so even if you
change the media label, you never lose statistical information about the piece of
media.

417
Media statistics
The Media statistics section provides information related to the use of the media.
This information includes how many hours the piece of media has been in use, its
available capacity, the number of mounts and seeks the piece of media has
incurred, and error-related information. This information is useful when you
troubleshoot what you suspect to be a media-related error.
158 418

Editing global settings for storage
You can edit the global settings that apply to the robotic libraries, media, and diskbased storage that are in your environment.
To edit global settings:
1 Click the Backup Exec button, click Configuration and Settings, and then
click Backup Exec Settings.
2 In the left pane, click Storage.
3 Select the appropriate options.
Media overwrite protection levels for tape and disk cartridge media
159
The media overwrite protection level is a global setting that supersedes the media
sets overwrite protection period. Although the terms are similar, the media
overwrite protection level and the media overwrite protection period are different.
The media overwrite protection period is a time interval that changes from one
media set to another. The media overwrite protection level specifies whether to
overwrite scratch, imported, or allocated media, regardless of the medias
overwrite protection period.
Use the media overwrite protection level to specify the type of media that you
want to be available for overwrite backup jobs.

419
Setting default media options: How Backup Exec selects media for overwrite
160 420
When Backup Exec is configured to overwrite scratch media before overwriting

recyclable media contained in the targeted media set, Backup Exec performs the
following steps to find available media based on whether your media protection
level is set to full, partial, or none.
1 Backup Exec first searches the scratch media set for overwritable media.
2 If scratch media are not available, Backup Exec searches for recyclable media
in the user media set targeted in the backup operation.
3 If recyclable media from the user media set are not available, Backup Exec
searches for recyclable media in all the other media sets.
4 If recyclable media are not available and the media overwrite protection level
has been configured as full, Backup Exec prompts for recyclable media.
5 If recyclable media are not available and the media overwrite protection level
has been configured as partial or none, Backup Exec searches for media in the
imported media set.
6 If recyclable media are not available, the media overwrite protection level has
been configured as partial, and no imported media are available, Backup Exec
prompts for overwritable media.
7 If the overwrite protection level has been configured as none and imported
media are not available, Backup Exec searches for allocated media.
8 If no allocated media are available and the media overwrite protection has been
configured as none then Backup Exec prompts for recyclable media to be
inserted.

Barcode labeling
If there is a barcode label on the physical cartridge, and if the robotic library has a
barcode reader, the barcode label automatically becomes the media label.
You can change the media label in Backup Exec. However, as long as the media
has a barcode label that can be read, the barcode label takes precedence over the
media label. To use the media label that you entered using Backup Exec, you must
remove the physical barcode label from the media cartridge. Or, you can use the
media in a device that does not have a barcode reader.
161
For example, robotic library 1 has barcode support. During a backup operation,
Backup Exec requests a new media or an overwritable media for the operation. A
new media with the barcode label 'ABCD' is inserted in the robotic library
magazine and the barcode reader scans the barcode ID. Backup Exec selects this
media for the operation and detects that a barcode label has been assigned to the
media. Backup Exec automatically uses the barcode label and continues the
operation.
When you change magazines or insert new media in a magazine, you can use the
Scan operation to quickly update slot information.

421
Creating media sets

You can create a new media set using the following methods:
1 On the Storage tab, expand Tape/Disk Cartridge Media Sets and Vaults.
2 Double-click All Media Sets.
3 Under User Media Sets, right-click a media set, and then click Create media
set.
4 Follow the on-screen prompts.
When creating or modifying media sets, you must specify the media set name, the
overwrite protection period, and the append period for media assigned to this set.
162 422
The default overwrite protection setting is Infinite - Dont Allow Overwrite,

which protects media in the media set from being overwritten unless erased,
formatted, labeled, moved to Scratch Media, or if overwrite protection is set to
None.
The default append period is Infinite - Allow Append, which allows data to be
appended until the media capacity is reached. Consider that this may interfere with
media policies used to send media offsite and regulations that limit the amount of
time to retain data.
The units of time that you specify may be converted. For example, if you enter 14
days, when you next view this property, the time may be displayed as two weeks.
You can rename, delete, or edit existing media set properties by right-clicking the
media set and selecting the appropriate option from the context menu.

Associating media with media sets
When you associate media with a media set, the media uses the append and
overwrite protection period properties of that media set.
Note: Associating scratch or imported media with a media set is not

recommended. Backup Exec automatically associates scratch or imported
media with a media set when a backup job requires it.
163
To associate media with a media set

1 On the Storage tab, expand Tape/Disk Cartridge Media Sets and Vaults.
2 Double-click All Media to display a list of media.
3 Right-click the media that you want to associate with a media set, and then
click Associate with media set.
4 Select a media set from the drop-down list, and then click OK.

423
Media catalogs
This topic describes media catalogs, which are databases that Backup Exec uses to
track the contents of media created during a backup or archive operation.
Before you can restore data or verify data written to media, the media must have a
catalog.
Catalog files
Catalogs are files that Backup Exec uses to track the contents of media
Catalogs are created during backups
Catalogs are used when browsing restore selections
164 424
Catalogs consist of a *.fh and *.xml file stored as flat files in \Backup
Exec\Catalogs
Catalogs are also written to the media during the backup
Backup Exec maintains an index of the catalog files in the Backup Exec Database
(BEDB)

Managing the catalog
165
Catalog defaults determine how Backup Exec uses the catalog. You can configure
Catalog settings, including the following:
Request all media in the sequence for catalog operations
This option forces Backup Exec to catalog media starting with the lowest
known tape number in the tape family. If you clear this options check box, a
catalog job begins on the tape that you specify, and you cannot select the Use
storage media-based catalogs option.
Use storage-based catalogs
This option configures Backup Exec to read the catalog information from the
media, resulting in a faster cataloging operation versus cataloging using the
traditional file-by-file method (which is enabled if you clear this check box).
Truncate catalogs after
This option reduces the size of the catalogs by deleting all file and directory
details after the specified time period; only header information is retained.
Truncated files cannot be restored unless the media is recataloged.
This option does not apply to synthetic backup jobs or true image restore jobs.
Current path
This field displays the path where the catalogs are currently located.
Catalog drive
This setting defines the volume where you want the catalog files to be located.
Catalog path
This setting defines the path on the specified volume for the catalog files.

425
Cataloging media
You can run a catalog operation to do the following:
Log the contents of a media that was created by another installation of Backup
Exec.
Create a new catalog on the local hard drive if the catalog for the storage
device no longer exists.
Before you can restore or verify data on a storage device, a catalog for that device
must exist. If Backup Exec has not used this storage device before, you must run
an Inventory and Catalog storage operation on the device first.
166 426
To catalog storage
1 On the Storage tab, right-click the storage device for which you want to create
a catalog.
2 Click Catalog.

(Optional) View the job log for details about the job.
167

427
Demonstration: Creating Media Sets
This demonstration illustrates how create a media set.
168 428

Demonstration: Associating Media with Media Sets
This demonstration illustrates how to associate media with a media set.
169

429
Demonstration: Cataloging Media
This demonstration illustrates how to run a catalog operation.
170 430

Demonstration: Inventorying Media
This demonstration illustrates how to run an inventory operation.
171

431
Demonstration: Setting Media Set defaults
This demonstration illustrates how to overwrite recyclable media that is contained

in the destination media set before overwriting scratch media.
172 432

173

433
174 434

Lesson 5
Backing Up Data
175
176 52

Backup job basics

This topic describes the basics of backup jobs.
Job functions
Consider that a backup job answers the questions posed in the following table:
177
Job function
Backup job property
Description
What data will be

backed up?
Selections
Identifies which data, from which

systems, is to be backed up.
When will the job run?
Schedule
Defines when the job is to be

submitted; options include Run
now with no recurring schedule,
Submit job on hold, and so on.
Where will the backup

data be stored?
Storage
Defines the destination for backed

up data to be stored.
How will Backup Exec

handle the backup data?
Network, Notification,
Test Run, Verify,
Advanced Open File,
Security, Pre/Post
Commands, Files and
Folders, and
Exclusions
Establishes general settings such

as network, notification, security,
exceptions and so on.

Lesson 5 Backing Up Data
53
Backup methods
There are three basic backup methods available in Backup Exec:
Full backups protect all of the data in the backup jobs selection list.
Differential backups protect only those files included in the selection list that
have been modified or created since the last successful full backup.
Incremental backups protect only those files included in the selection list that
have been modified or created since the last successful full or incremental
backup (whichever is more recent).
Each of these backup methods is discussed in more detail later in this topic.
178 54

Participant activity
Comparing backup methods
179
Full every day
Full and
differential
Full and
incremental
Media storage
requirement
Maximum
Medium
Minimum
Backup window
Longest
Medium
Shortest
Restore recovery
time
Shortest
Medium
Longest
Which backup method would require the most media?

Which backup method would require the least media?
Which backup method would require the longest backup time?
Which backup method would require the shortest backup time?
If you had to do a full restore, which method would be quickest restore time?
Which method would be the longest restore time?

55
Full backups
The first backup you perform in any backup strategy is a full backup. This serves
as a baseline on which subsequent differential or incremental backups are based (if
you choose to use such backup methods). Full backups include all of the data that
was selected for backup.
Full backups also include duplicate backups, which include all selected data.
Duplicate backups do not affect your media rotation strategy because the archive
bit is not reset. Duplicate backups are useful when you need to do the following:
Back up data for a special purpose.
Back up specific data.
Perform an additional backup to take off-site.
Back up data without affecting your media rotation strategy.
180 56
Another option for full backups is to use the Delete selected files and folders
after successful backup option. This option deletes the backed up data from the
volume after a successful full backup to free disk space and to reduce clutter.
The slide lists some advantages and disadvantages of the full backup method. Full
backups illustrate the balance that you must achieve between your backup window
and your recovery requirements that are mandated by your disaster recovery plan.
Specifically, you must consider whether you are able to spend more time and
resources performing the backup in exchange for a quicker and easier restore.

Differential backups
Differential backups include all files that have changed since the last full backup.
The difference between differential and incremental backups is that incremental
backups include any files that have changed since the last full or incremental
backup.
5
Note: In a backup definition that includes a differential task, all of the backup
tasks must use storage devices that the same Backup Exec server can
access.
181
The default method used by Backup Exec is By modified time, which uses the
Windows Change Journal to determine if a file has changed since the last time it
was backed up. If the Change Journal is not available, modified time is used. You
can also configure Backup Exec to use archive bit, or the Backup Exec catalogs to
determine if the file was backed up.
Note: If you use modified time to determine if files have been backed up, the full
and the differential backups must use the same backup selections.
Differential backups allow much easier restoration of an entire device than
incremental backups since only two backups are required. Using fewer media also
decreases the risk of having a restore job fail because of media errors.

57
The slide lists some advantages and disadvantages of the differential backup
method. Consider that using differential backups is generally recommended over
using incremental backups.
182 58

Incremental backups
Incremental backups include only the files that have changed since the last full or
incremental backup. The difference between incremental and differential backups
is that differential backups include any files that have changed since the last full
backup.
Incremental backups take much less time than full or differential backups to
complete. They also require less storage space for backed up data since only any
files that have changed since the last full or incremental backup are backed up.
183
Restoring data from incremental backups requires multiple backups that may
reside on several different pieces of media: the full backup and all successive
incremental backups. The process involves restoring the full backup first and then
applying the incremental backups in their sequential order to roll forward the
data to its most current backed-up state. For example, if you run a full backup on
Monday and incremental backups Tuesday through Friday, you can restore a
crashed system on Friday using the full backup from Monday and then applying
the incremental backups from Monday, Tuesday, Wednesday, and Thursday.
The slide lists some advantages and disadvantages of the incremental backup
method. Consider that incremental backups generally complete faster than the full
or differential methods.

59
New backup terms in Backup Exec 2012

As you have already seen, the Backup Exec graphical user interface is now
upgraded for a better experience. For those who have worked with Backup Exec
2010, a couple of important changes that you will notice while creating a backup
job are listed here:
Policies are now referred to as Backup Definitions in Backup Exec 2012.
Templates can now be configured in the form of Stages.
These will be discussed in detail in the forthcoming slides.
184 510

Backup definition
When you want to back up data, you create a container that is called the backup
definition. The backup definition contains the following elements:
Backup selections: Backup selections include any servers, volumes, or data that
you have selected to back up.
Backup jobs and settings: Backup definitions always contain one backup job that
uses the full backup method, but recurring jobs can also contain additional
incremental or differential backup jobs. Backup job settings can include
configuring encryption, scheduling options, or notifications.
185
Stages: Stages are optional tasks that you can run with backup jobs. Backup
definitions can contain one or more stages. You can create stages that duplicate
your backup data, create virtual machines with your backup data, or archive your
backup data.
Each of the above mentioned elements are discussed in detail over the next few
slides.

511
Backup selections
When you back up a server, Backup Exec includes all of the data on the server in
the backup selections by default. If you want to modify the backup selections, you
can do so from the Selections box on the Backup Job Properties dialog box.
Instead of backing up all of the data on a server, you can select drives, folders,
files, System State, network shares, or databases on the Browse tab.
To include data in the backup, select the check box next to the drive or directory
that you want to back up. You also can include or exclude specific files or specific
types of files using the Selection Details tab.
186 512
The following two slides discuss two important features related to backup
selection:
Dynamic Inclusion
Discover Data to Back Up

Dynamic system and application device protection

Backup Exec 2012 includes dynamic system and application device protection.
Dynamic system and application device protection was known as Dynamic
Inclusion in BE 2010. It means that at the server level, any new resource that is
added will be will be automatically protected. When you select a server resource,
an implicit selection of all of the server's system and application devices is
performed. You can disable the implicit selection of all system and application
devices.
All critical and non-critical system and application devices are dynamically
discovered and automatically protected.
You can explicitly include System and Application devices for protection or can
explicitly exclude them from protection.
187
When new System or Application devices are discovered and protected, during
subsequent protection operations, the newly discovered devices are written to the
job log.

513
Data Discovery
Backup Execs Discover Data to Back Up option detects backup content within a
Windows or Active Directory domain. The data discovery operation searches for
server volumes, databases, or any application data that has not been backed up yet.
The Discover Data to Back Up option performs three main tasks:

It discovers any top-level computers or computer contents.
It discovers any servers that do not have an Agent for Windows installed on
them.
It discovers and validates instances of the Agent for Windows.
188 514
The data discovery operation only discovers the servers that meet the following
criteria:
Belong to the same domain as the Backup Exec server.
Have the Windows Management Instrumentation (WMI) service enabled and
running.
Allow WMI access for the same user that the Backup Exec Management
Service runs under.
Members of the server's Administrators group have this level of access.
Have firewalls that are configured to allow WMI network traffic.
Configuration settings for Data Discovery
To configure Backup Exec to discover data to back up:
click Backup Exec Settings.

In the left pane, select Discover Data to Back Up.

3 Select the appropriate options and click OK.
2
By default, the data discovery operation runs at noon every day. It also runs each
time the Backup Exec services are restarted. Backup Exec cancels the operation if
it is still running after four hours. You can disable the operation or change the
default settings.
189

515
Backup jobs and settings

Backup definitions always contain one backup job that uses the full backup
method, but recurring jobs can also contain additional incremental or differential
backup jobs.
Backup Exec is preconfigured with default options for backup jobs. If you want to
override the default options for a specific backup job, you can modify them when
you create the backup definition. When you create a new backup job, the job
inherits the default settings that you configure.
190 516
The backup job settings include the following:

Schedule
Storage
Network
Notification
Test Run
Verify
Advanced Open File
Advanced Disk-based Backup
Security
Pre/Post Commands
Files and Folders
Linux and Macintosh
Lotus Domino

Microsoft Active Directory

Microsoft Exchange
Virtual Machines
Microsoft SharePoint
Microsoft SQL
NDMP
Oracle
Exclusions
Note: Some backup job settings appear in Backup Exec only if your network is
configured to support them and you have the appropriate Symantec Backup
Exec agent installed.
191

517
Stages
Stages are the additional tasks that you can run with backup jobs as part of the
backup definition. You may choose to add stages to the backup definition to
customize it. You can add one or more stages for virtualization, duplication, and
archiving when you create a backup definition. Stages can also be added to
existing backup definitions.
For example, you may create a backup job that contains any important data that
must be sent off-site. You can add a duplicate stage to the backup definition that
contains that job. The duplicate stage automatically sends the backup data to tape
storage when the backup job is complete. Then you can take the tape off-site to
ensure that your data is safe.
The slide lists the various stages along with their descriptions.
192 518

Configuring backup jobs

This topic describes the basic settings you can configure for backup jobs.
Adding a server
Backup Exec 2012 introduces a method to add servers to the servers list. The Add
a Server Wizard, guides you through the process of adding servers to the Backup
Exec servers list. You can use this wizard to add a remote Windows computer to
the list of servers and simultaneously install or update the Agent for Windows. You
can also add File Servers, Microsoft SharePoint server farms, Microsoft Exchange
Database Availability Groups, Linux computers, Macintosh computers, and
VMware vCenter or ESX Servers. Note that the Agent for Windows is installed or
updated only on Windows computers using this method.
193
If Backup Exec discovers servers using the Discover Data to Back Up option,
they are displayed in the Browse dialog box under the heading Servers without
an Agent for Windows installed. The Data Discovery feature is discussed in
detail later in this chapter.
If you do not want to monitor or back up a server with Backup Exec, you can
remove it from the list of servers. If you remove a server from the list and it has
scheduled jobs pending, the jobs are deleted. The jobs do not run as scheduled. Do
not remove a server from the list if you want to back up the server.

519
Before you can create a backup definition, you must add the servers that you want
to protect to the list of servers. To add servers to the list of servers in Backup Exec,
1 Click the Backup and Restore tab.
2 In the Servers group, click Add.
3 The Add a Server Wizard is displayed.
4 In the Which type of server do you want to add to Backup Exec? screen,
select the appropriate server.
194 520

In the Do you want to establish a trust? screen, select the Allow Backup
Exec to establish a trust with the servers check box.
When you connect to a remote computer from the Backup Exec server, you
must establish a trust between the Backup Exec server and the remote
computer. You must also establish this trust if you want to configure a remote
computer to perform client-side deduplication. You should check the IP
address for the remote computer to ensure that the remote computer is a trusted
source before you establish the trust. After you verify that the remote computer
is a trusted source, you can establish the trust with the Backup Exec server.
Backup Exec issues a security certificate for both the Backup Exec server and
the remote computer. The security certificate is valid for approximately one
year and is automatically renewed during normal operations. However, if the
certificate expires you must re-establish the trust.
6 In the Which servers do you want to add? screen, type the name (or IP
address) of the server or browse for the server.
195

521
In the Which logon account do you want to use to connect to each server?
screen, select the appropriate logon account.
8 In the Do you want Backup Exec to upgrade the Symantec Backup Exec
Agent for Windows, if a version of it is installed on the remote computer?
screen, select the Upgrade and Restart check boxes respectively.
7
Note: Remember that if you select the Restart option, this will restart the remote
computer. Doing this on a production server at the wrong time, will force a
restart of the server while important applications are running or users are
logged in. Deselecting the Restart button will mean that the server must be
restarted manually at a later point in time. Another alternative is to add a
server at a time when the server can be restarted safely.
196 522

Backup Exec installs the Symantec Backup Exec Agent for Windows.
10 After the Symantec Backup Exec Agent for Windows is installed, click Finish.
197

523
Server groups: Overview
Backup Exec 2012 enables you to create Server groups. Server groups help you to
manage and monitor the servers in your network. Note that Server groups are used
for organizing the servers in your environment logically. A server can be a member
of multiple server groups at the same time. You can drag and drop servers into
groups or between groups. The Server group icon displays the rolled up status of
the servers in its group.
198 524

Why server groups?
There could be various reasons for creating server groups, such as:
An entire server group can be backed up at once.
Servers could grouped together based on their geographical location,
application type, data being backed up, and so on.
In case of more than administrators, each administrator can create a server
group for which he/she is responsible.
199

525
Choosing a default configuration
Backup Exec 2012 provides numerous built-in configurations, which you can
select to display the appropriate servers in the servers list. All Servers is the
default configuration. However, you can select specific servers like VMware
vCenter, Hyper-V, Microsoft Exchange, Microsoft SQL, Oracle, NetWare,
Archive, and so on. To select a built-in configuration, in the Backup and Restore
tab, in the Views area, click Sort and Filter, point to Configurations, and then
select the appropriate configuration.
200 526

Adding a Server group

To add a Server group, in the Backup and Restore tab, in the Views area, click
Groups, and then click Add.
The New Server Group dialog box is displayed.
In the Group Name box, enter a name for the Server group.
In the Description box, enter an appropriate description for the Server group.
In the Filter area, use the Name Contains, Server type, and Data sources
options to filter the servers that are displayed in Servers area.
In the Servers area, select the servers that you want to make a part of the Server
groups.
201

527
Job creation methods

You can create a backup job using various options.
Using the Backup button
To create a backup job using the Backup button:
On the Backup and Restore tab, select the server name.
In the Backups group, click Backup.
Select the backup method that you want to use.
Using the right-click server option
202 528
To create a backup job using this method:

On the Backup and Restore tab, right-click the server name.
On the Backup menu, select Back Up to Disk.

Creating a one-time backup

A one-time backup is a job that only runs once without any recurring instances.
You may want to create a one-time backup to create a baseline for a server before
you upgrade it or install new software. After Backup Exec finishes running a onetime backup, it deletes the job rather than saving it with your recurring jobs.
To create a one-time backup:
On the Backup and Restore tab, select the server name.
In the Backups group, click One-Time Backup.
Select the one-time backup method that you want to use.
Using existing backup

If you want to create a backup definition that is similar to an existing backup
definition, you can apply the existing definition's settings to a new definition.
Any backup methods, job settings, and stages are copied into a new backup
definition for the server or servers that you selected to back up. All that you have
to do is select the backup selections. You can override any of the job settings, if
necessary.
To create a new backup from an existing backup:
On the Backup and Restore tab, right-click the server name.
On the Backup menu, select Create a New Backup Using the Settings from
an Existing Backup.
203 Lesson 5 Backing Up Data
529
Creating a backup definition

To back up a single server, in the Backup and Restore tab, select the server. In the
Backup area, click Backup, and then select the backup option that you want to
use.
When you create a backup definition, you must choose the type of storage to which
you want to send the backup sets. Backup Exec 2012 has preconfigured backup
options that combine different types of storage with stages. When you create a
backup definition, you begin by selecting one of these backup menu options. You
can add additional stages to the backup menu option to further customize the
definition.
204 530
Backup menu options are displayed only if your system is configured to support
them. For example, if you do not have a tape storage device, the Backup Up to
Tape option is not displayed in the list of backup menu options. Some of the
common backup menu options are Back Up to Disk, Back Up to Tape, Back Up
to Tape and then Archive, Back Up to Disk and then Convert to Virtual
Machine, Back Up to Disk and then Duplicate to Tape, and so on.
In the Backup Properties dialog box, you need to perform the following tasks:
In the Name field, type a unique name for the backup definition. If you back up
data from multiple servers, Backup Exec appends the server name to the text you
enter in the Name field. Backup Exec uses the server name and the text you
entered to create unique names for each backup definition.
To test or edit the credentials that Backup Exec uses to access backup selections, in
the Selections box, click Test/Edit Credentials.

The Test/edit credentials dialog box opens. When you browse remote selections,
Backup Exec requires a valid logon account to expand the computer contents. If
the default logon account does not enable access to a remote selection, Backup
Exec prompts you to select another existing logon account. You can also create a
new logon account that can access the selection.
Click Test All. After you see the Success status displayed for each of the
selections, click Close.
To change the backup selections, in the Selections box, click Edit.
531
When you back up a server, Backup Exec 2012 includes all of the data on the
server in the backup selections by default. If you want to modify the backup
selections, you can do so from the Selections box on the Backup Job Properties
dialog box. Instead of backing up all of the data on a server, you can select a drive,
a folder, files, System State, network share, or database. You also can include or
exclude specific files or specific types of files.
To expand or collapse the view for an item, click the arrow next to it or doubleclick the item's name. To view the contents of an item, double-click the items
icon. The items contents appear in the right frame of the backup selections view.
You can traverse file levels from either side of the window by clicking folders and
sub-folders as they appear.
206 532
If you select to back up data from more than one server, the selections are
combined in one dialog box. Similar types of content are grouped together. You
can edit the backup selections, but the backup selections apply to each server that
you back up.
For example, if you select to back up two servers, you can either select or clear
System State for both. But you cannot choose to back up System State for one
server and not the other. You cannot select individual files and folders if you
choose to back up multiple servers at once.
Selecting multiple servers is a good way to back up servers in their entirety. If you
want to back up more granular selections for each server, you should select them
separately and create new backup jobs.

When all the critical system components are included in your backup job
selections, the Simplified Disaster Recovery indicator on the selections pane
turned ON. If you clear one or more critical system component files, the indicator
changes to OFF. If you clear any critical system components, it can disqualify
your backup data from being used in certain types of restore scenarios. You must
include all critical system components in your backup selections if you intend to
use any of the following restore scenarios:
Simplified Disaster Recovery
Physical to virtual
Backup set to virtual
Online disaster recovery
533
Backup Exec is preconfigured with default options for backup jobs. If you want to
override the default options for a specific backup job, you can modify them when
you create the backup definition. When you create a new backup job, the job
inherits the default settings that you configure. Some backup job settings only
appear in Backup Exec if your network is configured to support them and you have
the appropriate Symantec Backup Exec Agent installed. To view the Backup
options for a backup job, click Edit.
208 534

Creating a backup definition: Schedule

This section discusses the Backup Options. Schedule lets you configure the time
and the frequency with which you want to run the backup job or jobs. The weekly
and monthly schedules are displayed for your reference.
535
Backup Exec 2012 enables you to add additional full, incremental, or differential
backups to the backup definition. For example, you can edit the backup job and
remove a backup stage, such as incremental and add another backup stage, such as
differential in its place.
Note that you cannot add incremental and differential backup jobs to the same
backup definition.
To remove a backup stage, simply click the X next to it. To add a backup stage,
click the Add Backup Jobs By Method button.
210 536

Creating a backup definition: Storage
Storage lets you specify the storage device that you want to use for a backup job.
You can configure different storage devices for each backup job. For example, you
may select disk storage for a full backup and a device pool for an incremental
backup in the same backup definition. You can also configure compression,
encryption, and data lifecycle management settings for the storage.
211

537
Creating a backup definition: Network
Network lets you specify the network interface that Backup Exec uses to access
remote computers. Backup Exec supports Internet Protocol (IP) version 6. You can
select IPv6 using the Protocol drop-down.
212 538

Creating a backup definition: Notification

Notification lets you configure Backup Exec to notify specified recipients when
the backup job is completed.
213

539
Creating a backup definition: Verify

Verify lets you create a job that verifies whether all of the data was successfully
backed up when the job is completed. A verify job can also help you determine
whether the media you use is defective.
Symantec recommends that you verify all backups. By default, Backup Exec
automatically verifies backups at the end of a job. However, you can also schedule
the verify operation to take place at a later time or disable the verify operation
altogether. You can change Backup Exec's verify options as part of the default
backup settings or for individual backup jobs.
214 540
You can verify backup sets to ensure the integrity of the collection of data and the
media on which it resides. You can verify backup sets if you want to verify only
the data that was backed up in a specific backup job instance. If you want to verify
a job and all of its dependent backup sets, you can verify a job history.

Creating a backup definition: Advanced Open File

Advanced Open File lets you configure the snapshot settings that Backup Exec
uses to process the backup job. Backup Exec can use snapshot technology to
capture any files that are open when a backup runs. You can configure default
options for open files, which your backup jobs inherit when you create them. Or
you can override the default open file settings when you create backup jobs. You
can also enable checkpoint restart which lets you resume interrupted backup jobs.
Microsoft Volume Shadow Copy Service (VSS) enables third-party hardware and
software vendors to create snapshot add-ins for use with Microsoft technology.
The Shadow Copy Components snapshots are created using VSS, which is
reported in the job log.
215
Unlike Windows, Linux does not provide support for volume snapshots. Since
there is no framework, such as VSS, you require a mechanism for taking volume
snapshots on Linux. With Backup Exec 2012, the Agent for Linux adds a
capability that enables backing up of files locked in use, using the Advanced Open
File option for Linux.

541
Creating a backup definition: Security

Security lets you configure encryption settings for the backup job.
Encrypting your backup sets can help protect sensitive data.
Symantec ThreatCon Rating
The Symantec ThreatCon rating is a measurement of the global threat exposure,
delivered as part of Symantec DeepSight Threat Management System.
ThreatCon Level 1
Low: Basic network posture
216 542
This condition applies when there is no discernible network incident activity and
no malicious code activity with a moderate or severe risk rating. Under these
conditions, only a routine security posture, designed to defeat normal network
threats, is warranted. Automated systems and alerting mechanisms should be used.
ThreatCon Level 2
Medium: Increased alertness
This condition applies when knowledge or the expectation of attack activity is
present, without specific events occurring or when malicious code reaches a
moderate risk rating. Under this condition, a careful examination of vulnerable and
exposed systems is appropriate, security applications should be updated with new
signatures and/or rules as soon as they become available and careful monitoring of
logs is recommended. Changes to the security infrastructure are not required.
ThreatCon Level 3

High: Known threat

This condition applies when an isolated threat to the computing infrastructure is
currently underway or when malicious code reaches a severe risk rating. Under
this condition, increased monitoring is necessary, security applications should be
updated with new signatures and/or rules as soon as they become available and
redeployment and reconfiguration of security systems is recommended. People
should be able to maintain this posture for a few weeks at a time, as threats come
and go.
ThreatCon Level 4
Extreme: Full alert
This condition applies when extreme global network incident activity is in
progress. Implementation of measures in this Threat Condition for more than a
short period probably will create hardship and affect the normal operations of
network infrastructure.
217

543
Creating a backup definition: Pre and Post Commands
Pre and Post Commands lets you configure any commands that you want to run
either before the backup job begins or after the backup job is completed.
218 544

Creating a backup definition: Files and Folders
Files and Folders lets you configure how Backup Exec processes file system
attributes such as junction points and symbolic links. Note that tabs for Agent and
options only show when selections of that type are part of the backup. Options for
all backups, set in one place, are automatically applied on all backup tasks, full,
Incremental, and Differential in the respective backup stage.
219

545
Creating a backup definition: Exclusions
Exclusions lets you configure a certain file or types of files that you want Backup
Exec to exclude from the backup job.
220 546

Creating a backup definition: Summary

The summary view displays the synopsis of your selections.
221

547
Adding a stage
Stages are the additional tasks that you can run with backup jobs as part of the
backup definition. You may choose to add stages to the backup definition to
customize it. You can add one or more stages for virtualization, duplication, and
archiving when you create a backup definition. Stages can also be added to
existing backup definitions. For example, you may create a backup job that
contains any important data that must be sent off-site. You can add a duplicate
stage to the backup definition that contains that job. The duplicate stage
automatically sends the backup data to tape storage when the backup job is
complete. Then you can take the tape off-site to ensure that your data is safe.
222 548

To add a new stage, click Add Stage and select the appropriate stage.
549
The summary page displays the relationship between stages. You can also modify
the details for any stage by clicking Edit. For example, to modify the details for
the Duplicate stage, click Edit corresponding to the Duplicate backup stage.
224 550

The options for the duplicate stage are displayed in the Duplicate Options dialog
box. You can modify details pertaining to Schedule, Notification, Verify, and
Security. Click OK to close the dialog box.
551
The Backup job is displayed in the server details view with all the stages for the
job along with the respective details for each stage.
226 552

Creating backup jobs for multiple servers simultaneously

Backup Exec 2012 enables you to create backup jobs for multiple server
simultaneously. To back up multiple servers simultaneously, in the Backup and
Restore tab, hold the CTRL key and select multiple servers. In the Backup area,
click Backup, and then select the backup option that you want to use.
Backing up multiple servers follows the same workflow as previously discussed

except for the backup selections. In the selections area, click Edit to view or
modify the backup selections.
553
The Backup Selections dialog box opens. While working with multiple servers
the selection choices are generic and not server specific. A backup is created for
each selected server. The selections are created for each server based on the types
of resources were selected and what is available on the server. The options are
identical for each job. After creation, the jobs are independent of each other and
are not dependent on the other jobs in any way. Each job can be edited and
managed separately. Click OK to complete the backup selection.
In the Backup Properties window, click OK to schedule the backup job.
228 554

Editing multiple backups simultaneously

Backup Exec 2012 enables you to edit multiple jobs simultaneously. To edit
multiple server simultaneously, in the Backup and Restore tab, and select one or
more servers. In the Backup area, click Edit Backups.
In the Backup Job Selection dialog box, select multiple backup jobs and then
click OK. You can use the Name contains box, to narrow your search. Click OK
after making the appropriate selections.
555
Editing duplicate job options

The Edit Multiple Backups dialog box is displayed. The numbers indicate the
count of jobs that have stages. In the Duplicate stage area Click Edit to view or
modify the duplicate job options.
In the Backup Options dialog box, make the necessary modifications. Note that
the changed settings are annotated with a change (green) bar.
230 556

You can click on the change bar to view the affected backups or to undo the
change. Click OK to confirm the change.
231

557
Backup Job Defaults
You can access the backup jobs default settings using the Backup Exec icon,
located in the upper left corner of the console. The jobs default settings are
available for Backup to Disk, Convert to Virtual, and so on. The default contains
the complete gamut of settings for the backup stage. All the options for all agents
are present and the ability to configure full, incremental, and differential strategy
for the target type are also available. Backup Exec 2012 has a unique set of
defaults for each storage type, Disk and Tape, as well as backup stage type Backup
and Duplicate. Multiple default settings are combined when creating a new multistage backup job using the Backup button.
232 558

Running backup jobs

This topic describes methods to manually run backup jobs.
Manually running a backup job
Typically, backup jobs are scheduled to run automatically. There may be times
when you want or need to run a scheduled or a completed backup job manually.
Running a scheduled job immediately
You can run a scheduled job immediately. The job will also run on the next
scheduled occurrence.
To run a scheduled job immediately:
1 On the Backup and Restore tab or the Storage tab, double-click the server or
the storage device where the job is scheduled to run.
2 In the left pane, click Jobs.
3 Right-click the scheduled job that you want to run, and then click Run Now.
Running a job from the Job History
After a job runs, the job moves to the Job History. You can run a completed job
again from the Job History.
To run a job from Job History:
the storage device where the job is scheduled to run.
2 In the left pane, click Job History.
559
234 560
Right-click the scheduled job that you want to run, and then click Run Now.

Backup and Restore view

This topic describes the information displayed and tasks performed in the Backup
and Restore view.
Servers view
You can view a list of servers from the Backup and Restore tab. The Servers
view in Backup Exec 2012 is a resource-centric view, unlike earlier versions of
Backup Exec where servers were displayed as a job-centric view. Using the
Servers view, you can easily identify servers that are backed up successfully,
servers that are yet to be backup up, and servers that are facing issues.
561
The Servers list contains servers and distributed applications that can be backed
up and restored. Servers include Windows servers, Linux servers, Mac servers and
NDMP servers. Distributed applications include SharePoint Farms, Exchange
DAG, Enterprise Vault, vCenter, ESX, and Oracle RAC.
236 562

The servers that are displayed in the list include all the servers that you manually
add to Backup Exec as well as servers that Backup Exec discovers during a Data
Discovery operation. Note that you must add servers to the list so that you can
select them for backups. Windows servers must have the Agent for Windows
installed on them before you can add them to the list of servers. When you add
Windows servers to Backup Exec 2012, you now have the option to install the
Agent for Windows to them remotely.
You can also monitor server activity and job status from the list of servers. By
default, Backup Exec 2012 displays a server's alerts, backup status, and a calendar
of the last seven days of backup jobs. It also displays the date and time of the
previous and upcoming scheduled backups. You can customize the columns on this
list to display additional information.
563
Servers view: Selected server information

Using the Servers view, you can select a particular server and view the following
details:
Active alerts, status, details about the last seven days of backup jobs, details about
the last backup, details about the next backup, server type, operating system
version, Backup Exec version, data source types, backup selections, backup job
details like percent complete, elapsed time, byte count, average job rate, and much
more. If you do not want to monitor or back up a server with Backup Exec 2012,
you can delete it from the list of servers.
238 564

Default Servers List

The Backup Exec 2012 default server list now displays the following information:
A unique icon for each server type
Integrated active alerts, specific to the server
Overall server status
Daily status for the last week
Last backup date and time
Next scheduled backup date and time
In addition, the server list also displays if jobs are in the active state.
565
As discussed, you can view the backup status for last 7 days. The current day is
displayed on the right. You can click the status icon to view the job history for a
particular day. Additionally, you can click a job to display the job log.
240 566

Server Details
You can view details for a particular server by double-clicking the server, or by
selecting the server and clicking the servername Details navigation element.
567
Server Details: Jobs

The Jobs tab contains information related to scheduled backup and restore jobs for
the server. Backup Exec 2012 enables you to view both scheduled and active jobs
in the Server details view. You can also use the standard and compact versions of
the information display and sort and filter available the information displayed.
The current built-in configurations include active jobs and the jobs that are
scheduled to run in the next 24 hours. Note that the active jobs configuration
resembles the Job Monitor from previous versions of Backup Exec, but is specific
for the selected server.
242 568

Server Details: Job History

The Job History tab contains information related to the backup and restore jobs
run for the server. You can right-click a particular job and then, click View Job
Log to view the job details.
569
A new Job Log window opens displaying the detailed job log. You can also click
on the Job History tab to view details.
244570

When a new device is reported in the Backup Job Log, it is automatically included
and added as a Backup Job.
The message in the job information window is displayed as follows:
Resource \\servername\E: was not found in the previous
instance of this job. It will be fully protected in this
job. The backup selections for this job have changed
since the last time it ran.
In this situation, Dynamic Protection was enabled for this server. The E drive had
been added since the job was created, so Backup Exec detected it, included it in the
backup as a full backup, and reported this on the job log.
571
When a device is missing, it is reported in the Backup Job Log as displayed on the
slide.
Resource \\servername\E: was found in the previous

instance of t his job, but it is not present in this
job. The backup selections for this job have changed
since the last time it ran.
246 572

When a critical device is missing, it is backed up and reported in the Backup Job
Log, as displayed on the slide.
Critical Resource \\servername\E: was not included in
the original selections list, but has been included to
ensure complete protection.
Resource \\servername\E: was not found in the previous

instance of this job. It will be fully protected in this
job.
573
Server Details: Backup Sets
The Backup Sets tab lists all the backup sets created for the server. Backup Exec
browses catalogs to display this information. A backup set is a collection of the
data that you back up from a single source of content. For example, a single source
of content can be a server or a Microsoft Exchange dataset. If you select multiple
sources of content, Backup Exec creates multiple backup sets. When you run a
backup job, Backup Exec creates the backup sets and writes them to the storage.
248 574
Backup Exec keeps the backup sets that are stored on disk or on cloud storage for
as long as you specify in the backup job properties. By default, the amount of time
that backup sets are stored on disk is based on the type of backup job and its
schedule. You can keep the backup sets that are on disk from automatically
expiring by retaining the backup sets; Backup Exec retains all dependent backup
sets as well. You can right-click a particular backup set and perform various
actions such as Delete, Retain, Catalog, Duplicate, and Verify.

Server Details: Credentials
The Credentials tab displays information related to various credentials used to

access the server. You should run tests to make sure that you have the appropriate
credentials to access the content that you want to back up. A Backup Exec logon
account stores the credentials of a user account that you use to access a computer.
Logon accounts are discussed in detail later in this chapter.
575
Server Details: Properties
The Properties tab displays the server properties. Server properties such as the
server name, logon account, operating system details, and Backup Exec
information are displayed.
250 576

Viewing details for multiple servers

Backup Exec 2012 enables you to select a Server group and view details for all
servers that are part of the Server group.
251

577
After you click the Server group, you can select multiple servers and view the
details for all the selected servers. Note that the Servers button displays the
number of servers that you select. Click the Servers button to view the details for
all the servers.
252 578

The information displayed for the selected servers include the all the jobs that are
performed for each server, job histories, and alerts. You can use this option to
monitor jobs for one or more servers.
579
Logon accounts: Overview

Backup Exec logon accounts enable Backup Exec to manage user names and
passwords and can be used to browse computers or process jobs. Using Backup
Exec logon accounts enables you to apply credential changes to the jobs that use
them.
Backup Exec logon accounts are used to browse local and remote computers.
Whenever the Backup Exec logon credentials are passed between the Backup Exec
server and the remote computer, the credentials are encrypted.
Backup Exec logon accounts can also be associated with backup data at the device
level such as shares, databases, etc. If you need to edit the credentials, you can edit
the Backup Exec logon account. Any changes are applied to the selected
computers that use the Backup Exec logon account.
254 580
Backup Exec logon accounts are not user accounts. When you create a Backup
Exec logon account, an entry for the account is entered into the Backup Exec
database; no operating system accounts are created. If your user account
credentials change, you must update the Backup Exec logon account with the new
information. Backup Exec does not maintain a connection with the user account.

Logon Account Wizard
To create a new logon account by using the Logon Account Wizard:

Click the Backup Exec button, and then select Configuration and Settings.
Select Logon Accounts, and then select Logon Account Wizard.
The Logon Account Wizard opens. In the Do you want to add a new logon
account or edit an existing logon account? screen, select Add a new logon
account and then, click Next.
581
256 582
In the What credentials do you want to use for this logon account? screen,
enter appropriate credentials, and then click Next.
In the What do you want to name this logon account and what type of
account do you want it to be? screen, enter an appropriate name for the logon
account, select the logon account type, and then click Next.

In the Summary screen, verify the details, and then click Finish.
583
Managing Logon Accounts
To create a new logon account manually:

1 Click the Backup Exec button, and then select Configuration and Settings.
2 Select Logon Accounts, and then select Manage Logon Accounts.
3 Click Add.
4 Enter the appropriate options.
258 584

GRT-enabled backups
This topic provides an overview of how you can use GRT in your backup strategy.
What is Granular Recovery Technology?
Granular Recovery Technology is a backup option that is available with some

Backup Exec Agents. GRT lets you restore certain individual items from backup
sets. For example, you can use the Agent for Microsoft Exchange Server to restore
an email from a backup without having to restore the entire mailbox. Or, you can
use the Agent for Microsoft SharePoint to restore a list without restoring the entire
site. To restore individual items, the Granular Recovery Technology feature must
be enabled when you create a backup job. You can restore either full backup sets or
individual items from GRT-enabled backups.
585
Applications that support GRT
GRT is enabled for backups for the following applications:

Microsoft Exchange Server
VMware and Hyper-V
260 586
When you enable granular recovery for Exchange or SharePoint backups, the
catalog operation runs after the backup operation. The catalog operation runs once
every 24 hours, even if you schedule more than one GRT-enabled backup job to
run in the same period. Because the catalog operation runs at a different time, the
GRT-enabled backup job does not block another scheduled GRT-enabled backup
job from starting on time. When you view the server details, the catalog operation
appears in the Jobs list and Job History separately from the backup operation.
Separate backup and catalog operations for a GRT-enabled backup are not
supported for Exchange and SharePoint databases that are on virtual machines.
The following table lists the individual items you can restore for each application.

261
Applications
Individual items
You can restore the following individual items:

Active Directory objects and attributes
Active Directory Application Mode (ADAM)
and Active Directory Lightweight Directory
Services (AD LDS) objects and attributes
Microsoft Exchange
Server

Mailboxes
Mail messages and their attachments
Public folders
Calendar items
Contacts
Notes
Tasks
The following are examples of the individual

items that can be restored:
Site collections
Sites or subsites
Document or picture libraries
Lists
Individual list items
Documents, pictures, or other files that are
stored in libraries
VMware and Hyper-V
You can restore drives, folders, and files from

virtual machines that run a Windows operating
system.
You can also enable the granular recovery of
Microsoft Exchange, SQL, SharePoint, and
Active Directory application data that resides on
virtual machines.

587
Recommended devices for GRT-enabled backups

When you run a GRT-enabled backup job, Backup Exec creates media with an
IMG prefix (for example, IMG00001). IMG media is a specific media type that
Backup Exec creates only for GRT-enabled backup operations. When you run a
GRT-enabled backup job, the IMG media stores the backup data.
Note: Disk storage does not support encryption for GRT-enabled jobs.
You should consider which device you use for GRT-enabled backups before you
begin. You should also consider any special requirements for the type of data you
back up.
262 588
Symantec recommends that you select a disk storage device for any backups that
are enabled for Granular Recovery Technology (GRT). The disk storage device
should be on a volume that does not have file size limitations. An NTFS drive is an
example of a volume without file size limitations. Some examples of volumes that
have file size limitations include FAT and FAT32 volumes.
If you must use a disk storage device on a volume with file size limitations,
Backup Exec requires a staging location. Backup Exec temporarily stores a small
amount of metadata in the staging location during the backup job. It deletes the
data from the staging location when the backup is finished. The staging location is
not necessary, however, if you use a disk storage device on a volume without file
size limitations as the destination.
The staging location's default path is C:\temp.

The volume that is used for a staging location for backup jobs should meet the
following requirements:
It is local to the Backup Exec server
It does not have any file size limitations
Additionally, Symantec recommends the following to avoid disk space problems:
It should not be a system volume
It should have at least 1 GB of available space
Backup Exec also uses a staging location to restore GRT-enabled data from a tape
or from a disk storage device on volumes with file size limitations. The staging
location must be on a volume that does not have file size limitations and is local to
the Backup Exec server. The staging location is not necessary if you restore GRTenabled data from disk storage on a volume without file size limitations, such as
NTFS.
Backup Exec uses the staging area differently for the following types of restores:
Location of data to be
restored
Staging process
Tape
Backup Exec copies the entire backup set or sets to the

staging area. The staging area must have enough disk space
for the entire backup set or sets from which you want to
restore an individual item.
Before you use a tape device for a GRT-enabled backup,
ensure that sufficient disk space is available to perform a
restore.
Backup Exec deletes the data from the staging area when
the restore job is complete.
Disk storage device

that is on a volume
with file size
limitations (such as
FAT or FAT32)
Backup Exec must copy a small amount of metadata that is

associated with the backup set to the staging area to
complete the restore.
Backup Exec deletes the data from the staging area when
the restore job is complete.
The staging location's default path is C:\temp. You can change the default
backup and restore staging locations in the Backup Exec settings.
589
GRT requirements
Keep in mind the following requirements when you use Granular Recovery
Technology (GRT) for the applications listed:
264 590
Applications
Restrictions
Microsoft Active
Directory
You can run only full backups for GRT-enabled jobs.
Microsoft
Exchange Server
Backup Exec must have access to a uniquely named mailbox

within the Exchange organization for backup and restore of the
Information Store.
Microsoft
SharePoint
You must have a current version of the Agent for Windows

installed on all of the servers that participate in the SharePoint
farm.
VMware and
Hyper-V
You can recover only individual items to virtual machines that

run a Windows operating system.

Configuring Backup Exec to determine file backup

This topic describes how Backup Exec determines if a file is backed up.
Configuring Backup Exec to determine if a file is backed up

Whenever a file is created or changed, a computer's file system notes and records
the change. Computers can use a file's modified time, archive bit, or a Windows
Change Journal to determine when a file is created or changed. If you use the
incremental or the differential backup method as part of your backup strategy,
Backup Exec must know when a file has been modified. Full backups include all
of the data that you selected to back up. Subsequent incremental and differential
backups back up only new files and any files that have changed. The default
method is by modified time, which uses the Windows Change Journal to determine
if a file has changed since the last time it was backed up. If the Change Journal is
not available, modified time is used.
591
Method
Description
By modified time
Backup Exec uses the Windows Change Journal to determine if a

file has changed since the last time it was backed up. If the
Change Journal is not available, modified time is used.
When Backup Exec runs a full backup or incremental backup, the
time the backup launches is recorded in the Backup Exec
Database. The next time you run an incremental or a differential
backup, Backup Exec compares the file system time to the backup
time from the Backup Exec Database. If the file system time is
later than the database time, the file is backed up. If the file's
modified time is older than the previous backup's modified time,
that file is not backed up.
Note: A file's last modified date and timestamp

does not change when the file is copied or
moved. To ensure that the files are protected,
run a full backup after you copy or you move
files. If you have the Advanced Disk-based
Backup Option, you can run synthetic
backups to ensure that any copied or moved
files are protected.
When you run an incremental backup, Backup Exec records a

new time in the Backup Exec Database. The database time is not
updated with differential backups.
Using modified time allows Backup Exec to run differential
backups on the file systems that do not have an archive bit, such
as UNIX.
Backup Exec adds the time of the backup to the Backup Exec
Database only if the full backup job completes successfully. If it
does not complete successfully, subsequent differential or
incremental backup jobs back up all of the data instead of only the
data that changed.
266 592
Using archive bit
Backup Exec uses the archive bit from the file system to
determine if a file has changed since the last time it was backed
up.
When you choose to use the archive bit, Backup Exec turns the
archive bit off when a file is backed up. Turning off the archive
bit indicates to Backup Exec that the file has been backed up. If
the file changes again before the next full or incremental backup,
the bit is turned on again. Backup Exec backs up the file in the
next full or incremental backup. Differential backups include only
the files that were created or modified since the last full backup.
When a differential backup is performed, the archive bit is left
intact.

Method
Description
Using catalogs
Backup Exec uses the Windows Change Journal to determine if a

file has changed since the last time it was backed up.
Backup Exec compares path names, modified times, deleted and
renamed files and folders, and other attributes. If the Change
Journal is not available, Backup Exec compares the file
information to previous Backup Exec catalogs to determine if it
has changed. This method is required for synthetic backups and
true image restore. It is the most thorough method, but it takes
more time to run.
593
System State backup

This describes the system state backup.
System State: Overview
The system-specific data that comprises System State includes the registry, the
COM+ Class Registration database, and boot and system files.
Restoring System State
268 594
Depending on the version of Microsoft Windows, service pack levels, and features
that are installed, you can restore the following system state data:
Active Directory
Automated system recovery
Background Intelligent Transfer Service
COM+ Class Registration database
Dynamic Host Configuration Protocol
Event logs
File Server Resource Manager
Internet Information Service (IIS)
Microsoft Search Service
Network Policy Server
Registry
Remote Storage
Removable Storage Manager

Shadow Copy Optimization Writer

System files
Terminal Server Licensing
Terminal Services Gateway
Windows Deployment Services
Windows Management Instrumentation
If the server is a certificate server, then System State includes the Certificate
Services database.
If the server is a domain controller, then System State includes the Active
Directory services database and SYSVOL directory.
You must restart the computer after you restore System State data.
Note: You should not cancel a System State restore job. Canceling this job can
leave the server unusable.
595
270 596

Lesson 6
Restoring Data
271
272 62

Restore job basics

This topic describes the basic functionality of restore jobs and the guided methods
to restore and search for data.
Restore job fundamentals
The ultimate benefit of Backup Exec with regard to your data protection plan is not
its ability to back up your data, rather in its ability to restore the data. Restoring
data may be a planned or even a routine event, such as recovering a previous
version of a file for a client. However, you may also need to perform restore
operations as the result of a disastrous data loss, such as a server crash. This is
usually a highly stressful situation, so being prepared for data recovery is vital in
your role as a backup administrator.
Backup Exec enables you to retrieve information and restore it to any server or
remote server. You typically restore data that you backed up using Backup Exec,
but you can also recover data from backups that were created with previous
versions of Backup Exec.
Backup Exec provides you with the ability to restore single files, multiple files,
entire directories, and entire systems, including system settings.
273 Lesson 6 Restoring Data
63
Simplified restore
Backup Exec 2012 simplifies the process of finding the correct backup sets for the
restore jobs. After you select to restore data of a specific server, Backup Exec:
Provides restore types to indicate the type of backed-up data available, such as
applications, File System, Exchange, and so on.
Provides restore subtypes to guide which type of data can be restored.
Discovers the required media sets in the correct order for performing the
restore job, which is based on the restore selection list.
In Backup Exec 2012, you can select the point in time to restore the backup,
without navigating through the complete list of full and incremental backup sets,
as in the previous versions of Backup Exec.
274 64

Guided methods to restore and search for data

Backup Exec provides guided Search and Restore methods to assist you when
you search for or restore backed up data. If you have installed the Archiving
Option, you can also search for or restore archived data. Simplified Disaster
Recovery helps in recovering a local computer or a remote computer to its predisaster state.
From Search or Restore, you can:

Restore data to the location from which it was originally backed up or redirect
the restore to another location.
Start the restore job immediately or schedule it to run at a future time.
Specify a network to use as a default network for all restore jobs.
These guided methods to restore and search for data are discussed in detail over
the next few slides.
65
Search
The Search option lets you select multiple servers to search for backup sets. Then,
you can choose to restore the data, or you can copy and save the search criteria and
the results to the clipboard.
Backup Exec creates separate restore jobs for each server to which data will be
restored.
Search supports only the following types of data:

Files and folders
Exchange and SharePoint backup sets for which Granular Recovery
Technology was enabled
Archived file system data and archived Exchange mailbox data
276 66
The Search option on the Backup and Restore tab launches the Search Wizard.

You can search for individual files or folders or you can search for documents,
such as emails from an Exchange server.
67
Restore
The Restore option lets you browse the backup sets from a single server. Then,
you can restore the data.
You can also perform a complete online restore of a Windows computer if the
computer was fully selected for a backup. By default, backup jobs include all
necessary components that are required for a complete restore.
The Restore option on the Backup and Restore tab launches the Restore
Wizard.
278 68
The Restore Wizard guides you through a process that is designed specifically for
the type of data that you want to restore. For example, when you restore
application data, you are prompted only with the options that apply to that
application's data. The Restore Wizard guides you through restoring an entire
server, file and folders, volumes, and application data.


The Simplified Disaster Recovery feature lets you recover Windows computers
after a hard drive failure. The Simplified Disaster Recovery wizards guide you in
preparing for disaster recovery, and in recovering a local computer or a remote
computer to its pre-disaster state.
For more details refer to the Simplified Disaster Recovery lesson.
69
Running restore jobs

This topic describes how to run a restore job.
Selecting data for restore
To restore data from a single server perform the following tasks:

1 Click the Backup and Restore tab.
2 Select the server for which you want to browse the backup sets.
3 Click Restore. The Restore Wizard is displayed.
4 Select the data from the server that you want to restore. Note that the data
restore options displayed depends on the type of backup that you have
performed.
280 610

Selecting data subtype, files, folders, volumes, and target location

5 Select the data sub-type that you want to restore. You can restore backup data,
archived data, or search for files and folders to restore.
6 Next, select the files, folders or volumes to restore.
7 After you select the data to restore, you need to select the location to which you
want to restore the data. You can choose to restore the data to the original
location or redirect the data to a different path. If you choose to redirect the
data to a different path you need to provide the path and the Server Logon
Account credentials for the new server.
281

Lesson 6 Restoring Data
611
Selecting restore options

8 The next screen provides details about file integrity, hierarchy, and security for
the data being restored. You can choose to restore corrupt files, maintain the
original directory structure, restore existing files, and restore security
information.
9 Then, based on the data you have selected for restore, you need to select the
options related to restoring operating system features.
282 612

Selecting additional tasks and adding the restore job name and
schedule
10 You can select any additional tasks to be performed before or after the restore
job is completed.
11 Then, you need to enter the restore job name and the schedule. You can run the
restore job right-away, at a scheduled data and time, or keep it on hold.
However, you cannot maintain recurring schedules for a restore job.
613
Viewing the Restore Summary

12 Finally, after all the restore selections are performed, the Restore Summary
screen is displayed. Note that each restore selection is a link on this screen.
You can click a link to navigate back to the respective section. For example, if
you click the Location to Restore To link, the Which location do you want
to restore data to screen is displayed. Click Finish to complete the restore job
configuration and run the restore job as per the schedule you set.
284 614

Restoring System State to a domain controller

To restore System State to a computer that is a domain controller, you must start
the computer in safe mode. Then, use the Directory Services Restore Mode to
perform the restore.
To replicate Active Directory to the other domain controllers that exist in the
domain, you must perform an authoritative restore of the Active Directory. An
authoritative restore ensures that the restored data is replicated to all of the servers.
Performing an authoritative restore includes running Microsoft's Ntdsutil
utility after Backup Exec restores System State, but before you restart the server.
For more information about authoritative restore and the Ntdsutil utility, see
your Microsoft documentation.
To restore System State to a domain controller:
1 Start the destination server, press F8 when prompted for Startup Options, and
then select the Directory Services Restore Mode option.
2 Do one of the following:
a To open services on Windows 2003, do the following in the order listed:
Right-click My Computer.
Click Manage.
Expand Services and Applications.
b To open services on Windows 2008, do the following in the order listed:
Right-click My Computer.
Click Manage.
615
3
4
5
6
286 616
Expand Configuration.
Click Services.
For each Backup Exec service listed, do the following in the order listed:
Click Properties.
Click the Log On tab, click This account, enter a user account with local
administrators rights, and then click OK.
Right-click the service, and then click Start.
After the Backup Exec services have started, run the Restore Wizard to
restore System State.
In the Restore Wizard, enable the option Mark this server as the primary
arbitrator for replication when restoring SYSVOL in System State.
Restart the server before you restore more data.

Restoring Shadow Copy Components

The Shadow Copy Components use Microsofts Volume Shadow Copy Service to
protect third-party application and user data on Windows computers. You can
restore the items in Shadow Copy Components individually or together.
The following items are contained in Shadow Copy Components:
Backup Exec Deduplication Disk Storage
You can recover the deduplication disk storage by running the Restore Wizard
and selecting Shadow Copy Components.
Distributed File System Replication (DFSR)
617
Restoring individual items using GRT
The table in the slide lists the individual items you can restore for each application.
288 618
Applications
Individual items
Microsoft Active
Directory

Active Directory objects and attributes
Active Directory Application Mode (ADAM) and
Active Directory Lightweight Directory Services (AD
LDS) objects and attributes
Microsoft Exchange
Server

Mailboxes
Mail messages and their attachments
Public folders
Calendar items
Contact list
Notes
Tasks

Applications
Individual items
The following are examples of the individual items that can

be restored:
Site collections
Sites or subsites
Document or picture libraries
Lists
Individual list items
Documents, pictures, or other files that are stored in
libraries
VMware and Hyper-V
You can restore drives, folders, and files from virtual

machines that run a Windows operating system.
You can also enable the granular recovery of Microsoft
Exchange, SQL, SharePoint, and Active Directory
application data that resides on virtual machines.
619
Monitoring and cancelling a restore job

Backup Exec includes features that enable you to manage and monitor jobs. You
can monitor your active jobs and scheduled jobs from the Jobs list, which shows
the type of jobs, the state and status of the jobs, the schedule, and other details.
You can cancel a job that is in progress. It may take several minutes for a job to
cancel. While Backup Exec processes the cancellation of a job, the Cancel
Pending status appears in the Job Status column.
Canceling a restore job while it is in progress may result in unusable data and may
leave the disk in an unusable state. To avoid canceling a restore job, you can
redirect the restore to a noncritical destination. Then, copy the data to a final
destination when the job completes successfully. You should not cancel a System
State restore job. Canceling this job can leave the system unusable.
290 620
To cancel an active restore job:

the storage device where the job is running.
2 In the left pane, click Jobs.
3 Right-click the active job that you want to cancel, and then click Cancel.
4 Click Yes to confirm the cancellation of the job.

Simplified Disaster Recovery: Server Restore workflow

This topic describes the Simplified Disaster Recovery Server restore workflow.
Server Restore workflow: System component restore
You can perform a system component restore through the Restore Wizard, as
displayed on the slide.
This option is used to restore the entire server, or System State or Active Directory
when the target server is online.
291

Lesson 6 Restoring Data
621
You can perform a complete system recovery online.
After selecting the option for an online recovery, the options available are:
Restore a Windows computer that was fully selected for backup (from an SDR
backup)
Restore Active Directory data and/or System State
292 622

Server Restore workflow: Complete System Recovery

The components necessary for a complete online recovery are displayed.
The restore selections allow you to select a point in time backup for restore. Notice
that the Components necessary for a complete online restore are preselected and
grayed out. You can additionally select non-critical components to restore as well.
623
The screens demonstrate a restore of System State.of the Point-in-Time (PIT)

recovery sets.
294 624

Server Restore workflow: System component restore

You can perform a system state restore.
625
Server Restore workflow: System State restore
This is a view of the System State individual component restore. You can now
select individual components to be restored. This is another change in BE 2012.
Earlier, you could not select an individual component of System State for restore
(except ADRA).
296 626

627
298 628

Lesson 7
299
300 72

Simplified Disaster Recovery fundamentals

This topic explains the basics of Simplified Disaster Recovery.
Simplified Disaster Recovery: Overview
Simplified Disaster Recovery, or SDR, is the disaster recovery solution provided in

Backup Exec 2012. Simplified Disaster Recovery is a complete replacement for
Intelligent Disaster Recovery. SDR can be compared to applications such as Bare
Metal Recovery, or BMR, Symantec System Recovery, or SSR, and Norton Ghost
that use the Symantec Recovery Toolkit (SRT). SRT provides a customizable shell
and uses the Microsoft WinPE environment to run a minimal Windows operating
system from a virtual disk.
301
Symantec Backup Exec Simplified Disaster Recovery (SDR) enables you to

quickly and efficiently recover Windows computers after a hard drive failure. The
SDR wizards guide you in preparing for disaster recovery and in recovering a local
or remote computer to its pre-disaster state.
7

Lesson 7 Simplified Disaster Recovery
73
Terminology
The terminology associated with Simplified Disaster Recovery is listed on the

slide.
302 74

Simplified Disaster Recovery: Disk basics

Backup Exec provides you with a generic 32-bit and a generic 64-bit system
recovery DVD called the Simplified Disaster Recovery Disk. You can use either
one to recover a computer. However, keep in mind that some computers contain
storage controllers that can be recognized only with 32-bit drivers. Likewise, there
are also computers that contain storage controllers for which only 64-bit drivers
are available. Use the appropriate Simplified Disaster Recovery Disk for your
environment.
Note: If you downloaded the Backup Exec installation media, make sure that you
downloaded the ISO image for the Simplified Disaster Recovery Disk as
well. ISO images are available for 32-bit and 64-bit computers.
The following are the cases where you must use one over the other:
Use a 32-bit recovery DVD when the computer that you are recovering does not
have a processor that supports 64-bit.
Use a 32-bit recovery DVD to recover to 32-bit or 64-bit hardware using 32-bit
drivers.
Use a 64-bit recovery DVD to recover to 64-bit hardware that only supports 64-bit
drivers.
The 32-bit DVD can be used in most cases. If the DVD cannot restore, boot to the
64-bit DVD.
303 Lesson 7 Simplified Disaster Recovery

75
Simplified Disaster Recovery (SDR) is automatically installed on the Backup Exec

server during the initial installation of Backup Exec. However, the Agent for
Windows is required to protect remote computers with SDR. You must purchase
the Agent for Windows separately, and then install it on the remote computers that
you want to protect. The Agent for Windows is a system service that runs on
remote servers and enhances backup and restore performance.
304 76

You must start a computer with the Simplified Disaster Recovery Disk, and then
use the Recover This Computer link on the Recovery tab to recover the
computer. The recovery disk uses a minimal version of the Windows 7 operating
system and contains many of the drivers that are required to recover your
computer. In addition to the Recovery tab, the Simplified Disaster Recovery Disk
also provides two additional tabs that are called Network and Utilities. These tabs
refer to the network tools and utility tools that you can use to facilitate the recovery
of a computer. To know more about the Simplified Disaster Recovery Disk, refer
to the Symantec Backup Exec 2012 Administrator's Guide.

77
Simplified Disaster Recovery: Disk contents
The Simplified Disaster Recovery Disk consists of Agent for Windows (AW) and
Symantec Tape and Load Drivers (PNP Version).
306 78

Disaster recovery information files

Simplified Disaster Recovery (SDR) works with Backup Exec when you run
backup jobs that include all critical system component selections. For each
computer that you protect with this type of backup job, Backup Exec creates a
disaster recovery information file for that computer. A disaster recovery
information file contains computer-specific information for the computer being
backed up.
Computer-specific information includes details such as hard disk layout, storage

drivers, network drivers, and system version details. It also includes Backup Exec
catalog details such as backup set information and recovery point details. Each
disaster information recovery file uses the file name <computer_name>.DR.
Backup Exec automatically stores each disaster recovery information file it creates
in a default location on the Backup Exec server. Because the files are critical,
Backup Exec also lets you specify an alternate storage location where an
additional copy of each file can be stored. Symantec recommends that you set a
path to an alternate storage location. If the Backup Exec server crashes, you won't
be able to retrieve the disaster recovery information file from the default location
but you can retrieve it from the alternate location.
Each time Backup Exec runs a backup that includes all critical system
components, the disaster recovery information files are automatically updated in
each storage location.
SDR uses the computer-specific information that is contained in the file when you
run the Recover This Computer Wizard. Without a disaster recovery information
file, a local recovery of the computer is not possible with SDR.

79
SDR requirements
The following items are required before you use Simplified Disaster Recovery
(SDR):
Symantec Backup Exec 2012.
Agent for Windows or Backup Exec must be installed on any remote
computers to be backed up with SDR.
Encryption key files for all volumes that you encrypt with Windows BitLocker
Drive Encryption (Windows Vista/Windows Server 2008/Windows Server
2008 R2/Windows 7 only).
A third-party ISO 9660-compliant CD/DVD burning application to burn the
SDR-created bootable CD/DVD image to a CD or DVD.
A writable or rewritable CD/DVD device.
308 710
Note: Backups from previous versions of Backup Exec cannot be restored using
SDR.

Whats new in Disaster Recovery?

This topic discusses the new features in Disaster Recovery in Backup Exec 2012.
New features
In BE 2012, two Simplified Disaster Recovery DVDs are packaged with the
product. Now, you get a 32-bit recovery DVD and a 64-bit recovery DVD.
The wizard flow is redesigned for a more user-friendly experience.
In BE 2012, the SDR backup is used for system protection.
SDR also integrates with the well-known Symantec System Recovery (formerly
BESR) component Restore Anywhere. Restore Anywhere allows you to restore
your backup to any computer with different hardware setup.
BE 2012 has a page called the Simplified Volume Layout that lists the common
actions that you must take in a disaster recovery situation.
Instead of relying on Microsoft provided APIs, BE 2012 now comes with the
Advanced Disk Configuration application for advanced users where they can
redesign their disk layout.
BE 2012 supports recovery of Unified Extensible Firmware Interface-based
computers.
In BE 2012, when you back up a disaster recovery information file to a disk
storage device, a copy of the .DR file is kept with the device.
BE 2012 provides IPV6 support.

711
Simplified Disaster Recovery provides point-in-time recovery. Historically, IDR

always provided recovery of the latest backup. You could always go back to the
latest of the last backup.
BE 2012 supports disaster recovery from duplicate SDR jobs.
310 712

Simplified Disaster Recovery: Backup

This topic discusses the components that Simplified Disaster Recovery protects
and the method to protect computers using Simplified Disaster Recovery.
Simplified Disaster Recovery: Benefits
311
Simplified Disaster Recovery or SDR assures the smooth and streamlined

protection and recovery of a server. SDR ensures that all critical system devices
are always protected and recovered. Newly identified critical system devices are
automatically included in the protection operation. Note that critical system
devices must be full selections in order to be protected and recovered. To protect
and recover a server, SDR requires that you perform Dynamic System for
Application device protection. SDR balances new and existing protection and
recovery methodologies by not requiring the protection of non-critical system and
application devices. It allows devices and applications, such as user-defined data
shares and applications, to be handled with different protection and recovery
methodologies. SDR complements other recovery methodologies by facilitating
the following features and options:
Offline disaster recovery
Server Online Recovery or online disaster recovery
Physical to Virtual (P2V)
Backup-set to Virtual (B2V)

713
Critical system devices required for SDR backups

Simplified Disaster Recovery protects different critical system devices and noncritical system and application devices.
The critical system devices are identified and defined based on their priority for
protection and include the following collection:
312 714
The system volume, that varies depending on the flavor of hardware and operating
system. It includes the BIOS, the EFI partition, the UEFI and utility partition. The
boot volume, that includes the operating system itself. The services volume, that
includes the services required for booting, services required for the operating
system to run and those required to auto start the services, so that the operating
system can be restored to its original functional state. The system state device, that
defines all the parts that make the operating system. It also includes the volumes,
features, and parts of the operating system that are active and running.

Non-critical system and application devices
All the devices that are not defined as critical are included in the non-critical
system and application devices category. This category includes user-defined data
volumes application data volumes application agents, such as ADAM\AD-LDS,
Archive, Exchange, Hyper-V, Lotus, SharePoint, SQL Server, Oracle It also
includes the shadow copy component. Note that earlier, the service state in shadow
copy was critical.
313

715
Dynamic system and application device protection

Backup Exec 2012 includes dynamic system and application device protection.
Dynamic system and application device protection was known as Dynamic
Inclusion in BE 2010. It means that at the server level, any new resource that is
there is automatically protected. When you select a server resource, an implicit
selection of all of the servers system and application devices is performed. You
can disable the implicit selection of all system and application devices. All critical
and non-critical system and application devices are dynamically discovered and
automatically protected.
You can explicitly include System and Application devices for protection or can
explicitly exclude them from protection.
314 716
For Application devices, parent containers are present for granular application
instance and object selections. Older Microsoft SQL Server Instances and Oracle
Database Oracle instances were previously displayed at the device level (such as
the C drive, D drive). In BE 2012, the instances are displayed as a collection. In a
scenario where SQL or Oracle instances come and go, you can clear them at the
root level to exclude them from dynamic inclusion for protection.

Simplified Disaster Recovery: Workflow

This section discusses the Simplified Disaster Recovery workflow.
The key to successfully recovering computers after a disaster is to carefully and
properly prepare those computers before a disaster occurs. Before you can recover
computers, you must prepare the computers for disaster recovery by performing
the steps in the order listed on the subsequent slides.
Backup and Restore Server resource view
The user interface displays the servers that are available for protection.
Creating a Server Resource Backup Job
315
To initiate a server backup operation, navigate through the gallery, select the server
to back up and click Back Up to Disk.Server Backup workflow: Backup
Properties
The Backup Properties page is a visual representation inside the Selections view
as displayed on the slide. The external green button indicates that SDR is enabled.
Note that Shadow Copy Components are no longer present by default.

717
Server Backup workflow: Selection Options
By default, Backup Exec selects all critical system components for you when you
select a computer for backup. Backup Exec makes it easy for you to determine
when a computer is prepared correctly for future disaster recovery operations.
When all critical system components are included in your backup job selections,
the Simplified Disaster Recovery indicator on the selections pane reads ON. If you
deselect one or more critical system component files, the indicator changes to OFF.
Symantec does not recommend deselecting any system critical files from the
backup job; if you do, the system-specific disaster recovery information file cannot
be created.
316 718

Server Backup workflow Selections: Browse
On the Options page, the critical system devices selection details are displayed.
The System State has more devices listed. They include the service state
components that have been added. Also, there is no shadow copy. Typically, every
system has shadow copy that is critical. Now, shadow copy is displayed
conditionally (for Backup Exec Deduplication Storage (PDDE) (x64), Distributed
File System Replication (DFSR), and OSISoft PI Server).
317

719
Note that when non-critical system devices are excluded, SDR is implicitly
enabled.
318 720

Note that SDR can be explicitly disabled and enabled by right-clicking on the
Simplified Disaster Recovery.
319

721
SDR is not available for BE 2010 R3 and prior Remote Agents, non-Windows
applications and clusters. Unlike BE 2012, previous versions do not have the SQL
Server Instances parent node. Also, Shadow Copy Components are present in
previous versions. In this case, the selected system (BE-Nicobar-01-A) has the BE
2010 R3 Remote Agent installed; so, the option to perform Simplified Disaster
Recovery is not displayed.
320 722

SDR requires Backup Operator privileges and Administrator privileges.
321

723
Creating a custom SDR disk

This topic describes how to create a custom Simplified Disaster Recovery disk.
Custom SDR disk: Overview
You can create a custom SDR disk when you want to update the SDR disk by
adding drivers found from the computers that the BE server has backed up, or
when you want to add OEM drivers to the SDR recovery disk.
322 724
You can also create a custom SDR disk when you want to update the SDR disk
with the latest version of BE disaster recovery components after you apply a hotfix
or patch on the BE server. This wizard displays the list of computers backed up by
the Backup Exec server and allows you to select them for driver harvesting. You
can then create a custom bootable SDR CD image and add these drivers to it. This
wizard also allows you to provide any custom drivers (that are not available on any
computers backed up by the BE server) that you want to add to the final CD image.
Before you run the Create Simplified Disaster Recovery Disk Wizard, run a
backup of the computer with all critical system components selected.
When running backup jobs with critical system components selected for
Simplified Disaster Recovery (SDR) preparation, do the following:
Ensure that if the computer is a remote computer, a compatible version of the
Agent for Windows has been installed on it. You can determine the version of
the Agent for Windows by viewing the properties of the Agent for Windows
computer through the Windows Explorer.

Use the Backup Exec Agent for Microsoft SQL to periodically back up the
SQL system database. This item applies only if you installed Backup Exec into
an existing SQL instance.
Avoid including files in or excluding files from the backup using the Selection
Details tab.
Consider creating a custom Simplified Disaster Recovery Disk if you make
considerable hardware changes to the computer.

725
About the Create Simplified Disaster Recovery Disk wizard

The Create Simplified Disaster Recovery Disk Wizard guides you through the
process of creating a custom bootable recovery disk that you use to recover backed
up computers.
If the computer you recover contains a RAID setup, you may first be required to
configure the RAID before starting it with the Simplified Disaster Recovery
(SDR) Disk. Use the computer manufacturer's RAID software to configure the
RAID system before you start the computer with the SDR Disk.
324 726
You can run the Create Simplified Disaster Recovery Disk Wizard locally at
any Backup Exec server in your environment. When you start the wizard from a
particular Backup Exec server, you can create a custom recovery disk from that
Backup Exec server. During the creation of the custom recovery disk, you can
include storage and network drivers from the computers that the Backup Exec
server backs up.
You can also use the Create Simplified Disaster Recovery Disk Wizard to create
a custom recovery disk that contains storage and network drivers from those
computers that are backed up by a different Backup Exec server.
You can add new OEM drivers to a customized SDR Disk image. However, the
drivers that you add must be Windows 7 compatible as SDR uses a minimal
version of the Windows 7 operating system to do the recovery.
Using the Create Simplified Disaster Recovery Disk wizard
From the main Backup Exec user interface, access Configuration and Settings
and click the Create Disaster Recovery Disk menu item to start the wizard.

To use another Backup Exec server for the driver review process, select the
Choose another Backup Exec server option. Click Next to continue.

727
To specify the location of the existing Simplified Disaster Recovery Disk, click
Browse.
326 728

This important screen of the wizard lists all the Backup Exec Server-protected
computers.
Note that on this particular screen, all the systems listed are 32-bit systems. During
the previous process steps, you are asked to provide the details of the source SDR
disk that was part of the product DVD. If you select the 32-bit SDR disk details,
the wizard lists all the 32-bit systems protected by the BE server (as seen on this
screen). If you select the 64-bit SDR disk details, the wizard lists all the 64-bit
systems protected by the BE server. Select the 32-bit computers from which to use
the network drivers and storage drivers. The drivers are used by the wizard to
create a new custom Simplified Disaster Recovery Disk.

729
When you select the drivers, the wizard lists the drivers grouped by type. To add a
Network or Storage driver from the original equipment manufacturer or OEM
media, click Add Driver and navigate to the location of the media. The wizard
collects all the selected drivers to create the custom-bootable image.
328 730

On this screen, specify a location to store the bootable image and click Next.

731
Specify the Startup Options for the custom Simplified Disaster Recovery Disk
and then click Next.
330 732

Review the selections for the Simplified Disaster Recovery ISO image creation
process. Then, click Create image.
331

733
The Simplified Disaster Recovery ISO creation status is displayed.
332 734

Once the Simplified Disaster Recovery Disk CD image is successfully created,

click Finish to exit the wizard.
The process creates a bootable ISO 9660 file. Use a third party image burning
application to burn it to CD media.

735
Using SDR for disaster recovery

This topic discusses disaster recovery using Simplified Disaster Recovery.
Preparing computers for use with SDR
The following are the steps to prepare computers for use with Simplified Disaster
Recovery:
Boot into the system using the provided SDR DVD or using the custom SDR CD
image created using the create custom SDR disk wizard and select the language of
your choice.
Click on the Recover This Computer link on the main dashboard.
334 736
If your backup data for this computer is present on a remote Backup Exec server,
then select the remote recovery option and provide the credentials to connect to the
BE server.
If your backup data for this computer is present on local devices attached to the
computer (devices such as Disk Storage, Tapes, and Autoloaders), then select the
local recovery option and provide the disaster recovery information file.
Follow the wizard screens and create the critical volumes needed to restore the
required backup sets.
After reviewing the summary, click Recover and after the recovery, close the main
dashboard application to reboot into the restored computer.

SDR wizard: Boot process
This is the first screen that you see when you boot from the SDR DVD. The list of
eleven languages that BE supports is displayed. Select the language in which to
boot the SDR. All the text on the subsequent screens is displayed in the chosen
language.

737
SDR wizard: License Agreement
On the License Agreement screen, click Accept to continue.
336 738

SDR wizard: Main dashboard
This is the first screen or the launch page of the wizard. The wizard has three main
tabs Recovery, Network, and Utilities. The Recovery tab contains a single link
Recover This Computer. It also displays a description that states the function of
the link.

739
SDR wizard: Network tab
The Network tab contains the networking tools to start the network. For instance,
after you start the networking service, you may want to map a network drive to
browse for a .DR file, or to provide a driver, and so on. Through the Configure
Network Connection Settings, you can also configure network adapters to assign
a static IP address. You can perform other actions like running the IP config utility,
pinging a remote computer, and setting network card speed.
338 740

SDR wizard: Network adapter configuration
This is the network adapter screen. You can use both IPv4 and IPv6 addresses for
the cards. This originates in the base SDR. The base SDR has now been enhanced
to support IPv6.

741
SDR wizard: Utilities tab
This is the utilities tab view that is especially useful for tech support. For instance,
if the customer is unable to proceed with the recovery steps and calls technical
support for help, you can click the Gather Log Files for Symantec Technical
Support link. A simplified disaster recovery gather logs dialog box is displayed.
Enter the location to copy all the related log files that are required to diagnose the
issue. On the Utilities tab, you can also view individual log files created during the
disaster recovery process, start the command prompt, edit the Windows boot
.ini file, load a driver, or select the keyboard.
340 742

Recover This Computer wizard: Backup data location
When you click Recover This Computer, it launches the Recover This
Computer Wizard. To recover the computer, indicate the location of the backup
data either on backup devices that are attached to a remote Backup Exec server
or on locally attached devices such as tape drives, autoloaders, disk storage
devices, or disk cartridge devices.

743
On this screen, specify the Backup Exec server location to where the files were
backed up. Enter the Backup Exec server name, domain, User name and Password.
Here, you can also Configure network adapter settings and Load network
adapter drivers. Click Next to continue.
342 744

Recover This Computer wizard: Backup set location
One of the most important screens is displayed on the slide. If you are connected to
the media server, the backup sets display all the computers protected by the media
server. When you select a system, it lists all the point-in-time backups. When you
select a particular point-in-time backup set, it groups the required backup sets
together, and disables the check box, so that you are unable to deselect them. By
default, the additional backup sets are selected for restore. If, for instance, you do
not want to restore any of the additional backup set drives displayed on the screen,
clear the Recover the entire computer box and other check boxes and continue
the restore.

745
Recover This Computer wizard: Volume layout

The Recover This Computer Wizard lets you restore the hard drive volumes on
the computer being recovered to the same sizes they were before the disaster
occurred. Using disk geometry information from the disaster recovery information
file, the Recover This Computer Wizard presents the original disk geometry in a
simplified volume layout view. Within the simplified layout view, you can accept
the disk geometry as it originally existed before the disaster, or you can alter the
geometry by changing the volume sizes. Depending on the size of the existing
disks, you can alter volume sizes in megabytes, gigabytes, or terabytes.
The simplified layout view offers you a Preview tab where you can view the disk
geometry as it presently exists. If you decide to alter the disk geometry and change
volume sizes, you can also click the Preview tab to see a graphical representation
of your proposed changes.
344746
If mismatched volumes appear in the simplified volume layout view, you can use
the option Erase hard disks and recreate the volume layout shown above to
automatically create a volume layout on the available hard disks. You can also
manually create a volume layout by using the Advanced Disk Configuration
option.
If you want to make additional changes to the computer's disk configuration,
Symantec recommends that you run Advanced Disk Configuration.

Recover This Computer wizard: Advanced disk configuration

When you recover a computer, the Recover This Computer Wizard restores the
hard drive volumes to the same sizes they were before the disaster. If the hard drive
in the failed computer is larger than the hard drive that was in place before the
disaster, you may end up with unused and unallocated space. You can run the
Advanced Disk Configuration program to alter the volume sizes to reflect the
larger hard drive size.
The following is an example of why the hard drive volumes should be resized:
If the pre-disaster computer hardware contained a 400 GB hard drive with two 200
GB volumes, and you replaced it with a 900 GB model, SDR (using the disaster
recovery information file) rebuilds the hard disk partition table by using the
partition information that is found on the original 400 GB hard drive. As a result,
only 400 GB of space is allocated on the new 900 GB hard drive, with a partition
map that consists of two 200 GB partitions.
You can access Advanced Disk Configuration from within the Recover This
Computer Wizard.
Note: You should be familiar with Microsoft Disk Management concepts before
you run Advanced Disk Configuration.

747
To install network control drivers, on the Volumes layout screen, click Load
Storage Controller Drivers.
346 748

Recover This Computer wizard: Load Storage control drivers
From the Storage Controllers option, you can load drivers for the inactive storage
controller.

749
After selecting the volume layout, click Next.
348 750

Recover This Computer wizard: Summary
Before starting the recovery process, the wizard displays the Recovery Summary
page. It displays all the selections made for recovery of the system. Review the
summary information and click Recover. These steps comprise the pre-restore
steps.

751
Recover This Computer wizard: Recovery
Click Recover to begin the recovery process. After the Recovery begins, the
screen displays the progress of creating partitions and establishing a connection to
the Agent for Windows on the remote computer.
350 752

Recover This Computer wizard: Restoring data
Note that the restore runs as a redirected restore to a temporary machine name. The
wizard processes the restore of the entire C: drive, followed by the D: drive and the
System State.
351

753
Recover This Computer wizard: Hardware discovery
The files and System State restore is followed by Hardware Discovery.
352 754

Recover This Computer wizard: Installing devices
After discovering the hardware, the wizard detects and installs the devices on the
system.

755
Recover This Computer wizard: Disaster recovery process complete
After the SDR process is completed, click the View Hardware Discovery log to
view the Hardware Discovery log and the View Recover this computer wizard
log to view the wizard log. Click Finish to go back to the main Disaster Recovery
screen.
354 756

Recover This Computer wizard: Exiting the wizard
Click Yes to exit out of the wizard. This will restart the computer.

757
Performing final tasks
When the system reboots, it runs a quick Setup and then reboots again. Then, the
system is fully restored and ready to login.
356 758


759
358 760

Lesson 8
Virtual Machine Conversion
359
360 82

Conversion to virtual machines fundamentals

This topic explains the basic concepts of virtual machine conversion and describes
the supported virtual conversion configurations.
Introduction: Terminology
The common terms associated with physical to virtual conversion are listed on the
slide.
361

Lesson 8 Virtual Machine Conversion
83
Conversion to virtual machine basics
Physical to Virtual is the process of converting a physical machine into a virtual

machine for Hyper-V or VMware environments for business continuity purposes.
The source for the conversion can be a running physical machine or existing SDR
backup sets. The end result of the conversion process is a virtual machine that can
be turned on and used when the physical server goes down. The supported virtual
platforms for conversion targets are VMware and Hyper-V.
362 84
Backup Exec provides the ability to convert to virtual machines in the following
ways:
Back up a physical computer and simultaneously convert it to a virtual
machine.
Back up a physical computer and schedule a conversion to a virtual machine to
run after the backup job runs.
Convert existing backup sets to a virtual machine.
The newly created virtual machine is bootable and is identical to the physical
computer from which the virtual machine was converted. Conversion to a virtual
machine enables business continuity for both Hyper-V and VMware
environments.
Backup to Virtual is the process of converting an existing backup set into a virtual
machine for Hyper-V or VMware environments for business continuity purposes.
Physical to Virtual now uses the same datasource but writes to multiple data
targets. One of the targets is backup, so the backup is created on media such as a
tape or disk. The other target is conversion, which can happen either to a virtual
machine or to a virtual disk.

Job requirements
The virtualization feature of Backup Exec 2012 uses the Simplified Disaster
Recovery technology in the background. The backup job must include the system
drive and System State of the protected system. The Simplified Disaster
Recovery status must be displayed as ON, as indicated in the screen shot. The
only supported devices for virtualization jobs are disks and deduplication devices.
363 Lesson 8 Virtual Machine Conversion

85
Supported virtual machine options
For Physical to Virtual and Backup to Virtual, VMware ESX 4.0 and later and
Hyper-V are the supported hypervisors. VMware workstation and VMware server
are not supported.
364 86

Requirements for conversion to virtual machines

Before you use the conversion to virtual machine feature, review the following
requirements:
For conversion in a Hyper-V environment:
Windows Server 2008 SP2 or R2 is required on the Backup Exec server.
The Agent for Windows must be installed on the Hyper-V host to which
the conversion is sent.
The maximum disk size is 2 TB.
For conversion in a VMware environment, VMware ESX 4.0 or later is
supported.
The option Simplified Disaster Recovery must have a status of ON on the
Browse tab of the Backup Selections dialog box.
Only basic disks are supported. Dynamic disks are not supported.
Only Windows servers are supported.
Note: The Agent for VMware and Hyper-V is not required for conversion to
virtual machines.

87
Virtual conversion options

This topic discusses the different virtual machine conversion options.
Physical to Virtual conversion
Physical to Virtual is always done parallel to backup; there is no stand-alone

Physical to Virtual. During the conversion process of either Physical to Virtual or
Backup to Virtual, the disk geometry is the same as that of the source.
366 88
Physical to Virtual supports FULL and incremental backup methods. The Physical
to Virtual FULL conversion results in a new virtual machine or new virtual disks.
The Physical to Virtual incremental or differential conversion updates the existing
virtual machine or disks created during the previous FULL conversion. For the
Physical to Virtual to result in a virtual machine that is functional and viable, you
must ensure that all critical resources are selected and the conversion process runs
only for Simplified Disaster Recovery or SDR jobs.

Physical to Virtual conversion: Error handling
During a Physical to Virtual conversion, backup is considered the primary task. A

backup job continues even if the conversion fails. If the backup job fails, the
conversion also fails. If the conversion process fails for any reason during a job
run:
The backup job continues to run and back up the remaining data.
Only conversion is skipped for the remaining data and the job is marked as a
failed job.
In such a case, the conversion process does not run until the next FULL
backup.
After the physical server fails and the user switches over to the virtual machine
created by the conversion process, the subsequent conversion jobs will detect this
switch and keep failing the job. The user has to create a new backup job to protect
the failed-over virtual machine.

89
Backup to Virtual conversion

Similar to Physical to Virtual, the key to Backup to Virtual is an SDR job. So,
when an SDR backup runs, the metadata is collected, which is to do a Backup to
Virtual at a later stage or a conversion when the Physical to Virtual job runs.
Therefore, select only sets from an SDR job should be selected for a Backup to
Virtual. Always perform Backup to Virtual after the backup. You can run Backup
to Virtual jobs only through the workflow either as a linked job or on a schedule.
Linked jobs are limited to only FULL backups. For instance, if you have weekly
fulls and daily incrementals, the Backup to Virtual job is initiated when the weekly
full runs. For the incrementals, the Backup to Virtual job is not initiated. So, there
are no incremental updates to the VM. If the Backup to Virtual is scheduled, it
updates both fulls and incrementals.
The scheduled jobs have the sets starting from the last FULL backup.
368 810

Virtual conversion principle: One Data Source Multiple Targets

The purpose of the virtual conversion principle of one data source multiple
targets is to perform a backup and conversion simultaneously. The created
secondary NDMP data stream extensions allow the system being backed up to
broadcast its data to more than one source. The source system (Agent for
Windows) simultaneously sends backup data to multiple servers. Currently, the
source system sends data to a backup stream and Physical to Virtual, and only one
additional data stream to a virtualization environment, where it creates a virtual
machine and restores data in that virtual machine. The Physical to Virtual data
stream is considered a secondary data stream, so a dropped connection does not
affect the primary backup stream. But if the primary backup is affected, it affects
the secondary data stream and results in a failed backup. There is no caching, so
the data moves as fast as the slowest data stream. Also, there is no option to select
NIC cards for secondary data streams.
One Data Source Multiple Targets: Example
The diagram on the slide is a representation of a one data source multiple targets
example. For the backup, one data stream flows to the BE Media Server and the
other flows to the virtual host environment. The virtual host environment can be an
ESX server or Hyper-V server. The Media Server controls both of them through
the NDMP protocol.
8

811
Virtual machine conversion limitations

Some of the Physical to Virtual Backup to Virtual limitations are as follows:
Conversion support is limited to Windows source servers only. There is no support
for UNIX or Linux systems.
Physical to Virtual Backup to Virtual supports basic disks only. There is no
dynamic disk support.
For VMware, the block size of the data store defines the maximum supported disk
size.
For Hyper-V, the maximum LUN size is 2 terabytes.
370 812
For VMware cold conversion, even though there is an option to create thin disks,
the disks are sparse and cannot be used on the ESX host. If you want to use the
disks with ESX, Symantec recommends that you use the thick disk.

Virtual machine conversion for SBE
There is no Physical to Virtual support for SBE. Only Backup to Virtual is

supported for SBE. Hyper-V is the only supported virtual target environment.
There is no support for VMware. SBE only supports B2V and P2V in Hyper-V.
Only a Windows 2008 R2 media server can use Backup to Virtual. The Hyper-V
role must be enabled to make the disks bootable and to get the integration
components ISO (vmguest.iso).
371

813
Virtual conversion workflows

This topic describes the process and workflows for virtual machine conversion.
Physical to Virtual workflow
This section explains the Physical to Virtual workflow. This screen shot displays
the state after you add a server for backup. In the drop-down menu, the highlighted
task Back up to Disk and Simultaneously Convert to Virtual Machine is a
Physical to Virtual and the task above it, Back Up to Disk and then Convert to
Virtual Machine is a Backup to Virtual task.
372 814

This is the Backup Properties window, which is the selections screen. Here,
select the resources that you want to back up. The Backup stage and the Physical
to Virtual stage or Convert to Virtual Simultaneously stage are displayed here.
Selecting the Back up to Disk and Simultaneously Convert to Virtual Machine

or the Backup to Deduplication Disk Storage and Simultaneously Convert to
Virtual Machine option runs the conversion simultaneously with the backup job.
Because two operations are performed at the same time, this job may take longer to
run than a regular backup job. A large backup window is recommended for this
option.
A conversion from a full backup creates the new virtual machine. Incremental and
differential backups are not converted. Although the backup runs simultaneously
with the conversion, the backup is the primary job. Therefore, if the backup fails,
then the conversion fails also. However, if the conversion fails, the backup
continues to run. For a conversion failure, the job is marked as a success with
exceptions. In the case of a failed conversion, the conversion process runs again
during the next full backup.
Selecting the Backup to Disk and then Convert to Virtual Machine or Backup
to Deduplication Disk Storage and then Convert to Virtual Machine option
lets you schedule the conversion to run after the backup job. These options require
a smaller backup window than the simultaneous conversion options. A conversion
from a full backup creates the new virtual machine. Incremental and differential
backups are not converted.

815
Alternatively, you can add a stage to a backup job to convert to a virtual machine.
Two types of stages are available: Convert to Virtual Machine After Backup
and Convert to Virtual Machine Simultaneously with Backup.
374 816

For Physical to Virtual, ensure that the SDR job is enabled as indicated on the
slide. Because the SDR job is enabled, the critical resources are automatically
selected and dimmed.

817
Physical to Virtual workflow for VMware: Warm standby
Here is the Physical to Virtual workflow for VMware. On the Conversion

Settings page, select your virtual target and virtual method.
376 818

This is the Disk Configuration screen. The disks map to the source. If the source
has a SCSI controller or an IDE controller, it maps exactly to the same controller
as on the physical box. Change the controller to a SCSI or IDE, as required. Then
select the disk type either thick or thin. Use the Browse button to select different
datastores for the individual disks. The disk name is static and automatically
generated. It cannot be changed.

819
Physical to Virtual workflow for Hyper-V
For the Hyper-V Physical to Virtual, the target Hyper-V system has to be Windows
2008 R2.
378 820

Physical to Virtual workflow for Hyper-V: Warm standby

In a warm standby for Hyper-V, on the Conversion Settings page, select Hyper-V
as the virtual target. Under Virtualizations Environment Options, select the
Hyper-V server and a path on the Hyper-V Server. Under Virtual Machine
Options, the name of the VM is automatically pre-populated. It is the name of the
physical machine with the prefix VM. So, there is a mapping between the
converted and the physical machine.
Under Server Configuration, the source physical configuration is displayed. This

includes the physical RAM on the Source and the CPU count. The default values
are taken by the system. If you provide incorrect values, the system automatically
selects the maximum and minimum default values, thus preventing a job failure.

821
Now, click the Edit Disk Configuration tab. Hyper-V has a limitation that the
boot disk always has to be an IDE, so the disk to boot the system is identified and
put on IDE. You cannot change the controller for Hyper-V. Select the disk type to
be either fixed or dynamically expanding. Hyper-V allows you to change the
virtual disk name, so change the virtual disk name and select a path.
380 822

Backup to virtual conversion: Workflow

This section describes the Backup to Virtual workflow.
Backup to Virtual workflow
The slide displays the Add Stage of a backup set. Select the Convert to Virtual
Machine stage.
381

823
This is the Convert Backup to Virtual Stage. You can see both the Convert
Backup to Virtual and Convert to Virtual Simultaneously options here. You can
make the Physical to Virtual stage go to VMware or the Backup to Virtual stage go
to Hyper-V; the reverse also holds true.
382 824

For scheduling of the Backup to Virtual job, selecting the According to schedule
option results in a schedule-based backup selecting all the backups and giving you
sets from the last chain starting from the full.
If you select the Convert to virtual immediately after source task completes,
the source is Full.

825
Converting to a virtual machine from a point-in-time

Backup Exec 2012 enables you to perform a manual point-in-time conversion of a
backup to a virtual system. A conversion to a virtual machine from a point in time
converts existing backup sets from a backup job in which the Simplified Disaster
Recovery option was enabled. The Simplified Disaster Recovery option enables all
of the critical system components for a virtual machine conversion to be included
in the backup job.
Note: The option Convert to virtual machine from point-in-time becomes

available for selection only after you run at least one full backup that
includes all critical system components.
384 826
The option to convert to a virtual machine from a point in time is useful in a

disaster recovery situation in which you want to quickly recover a failed server.
The backup sets contain all of the necessary components of the system.
Additionally, you can select application data or user data to include in the
conversion.
On the Backup and Restore tab, select the server that contains the backup sets
you want to convert. Then click Convert and select Convert to Virtual from
Point-in-Time.

Backup Exec automatically assigns a name for the conversion job, which can be
changed. In the left pane, click Edit to select a different backup set to convert.
The right pane displays the target storage and schedule. Click Edit to modify these
settings.

827
This slide displays the Point-in-time selection options. The available backups are
listed in the drop-down list at the top. The options listed on this screen are
separated into two groups: Components necessary for a complete online restore
and Application data or non-system user data. Note that the components
necessary for a complete online restore are selected by default, and cannot be
modified. If you select the Name check box at the top, it will include all resources
on that system.
386 828


829
388 830

Lesson 9
Database Maintenance
389
390 92

Backup Exec database

This topic describes the Backup Exec database and its maintenance. Proper
maintenance of the Backup Exec database prevents it from increasing enormously
is size. This ensures that the Backup Exec server performance is not compromised.
It also describes the process to change the location of the Backup Exec database.
Protecting Backup Exec
Each Backup Exec server uses a database (most commonly referred to as the
Backup Exec database) that maintains critical information about the backup
environment served by a Backup Exec server.
391
The Backup Exec database is a critical component of Backup Exec, so proper

maintenance and protection of the database are essential for any data protection or
disaster recovery plan.
The Backup Exec database runs under MS-SQL Server 2005 Express Edition
which is installed with Backup Exec, unless you choose to use another SQL Server
instance. The database contains the two files, as displayed on the slide, and is
installed in the ..\Program Files\Symantec\Backup Exec\Data\
directory.
To protect a Backup Exec server installation, you must configure a backup job that
regularly backs up the database backup files, catalogs, and license files. Backup
Execs catalog is a database of all backed up data.

Lesson 9 Database Maintenance
93
Automatic database maintenance

The database maintenance option enables you to manage the Backup Exec
database. Each database maintenance operation is performed independently on
each database. The Backup Exec database maintains a record of the files and data
that you have configured.
Informational alerts are generated each time database maintenance is performed.

These alerts provide details about the type of database maintenance performed and
the time taken to complete the process. If the database maintenance process fails,
the alert indicates where the failure occurred and the reason for the failure.
392 94
You can configure database maintenance using the following method:

select Backup Exec Settings.
2 In the left pane, click Database Maintenance.
3 Select the appropriate options.
4 Click OK.
To enable database maintenance ensure that the Enable Backup Exec database
maintenance check box is marked. However, database maintenance is enabled
only if Backup Exec installs its own SQL database instance.
The Database Maintenance options let you manage the Backup Exec database. You
do not have to select all the options; however, each option performs a different
process that enables you to protect and maintain your database.

You can manage the Backup Exec Database to optimize space and performance.
To conserve disk space, you can enable automatic deletion of database data,
including job history, job logs, alert history, reports, and audit logs. Considering
that report data includes information about report jobs, the report itself is not
deleted.
You can select one of the following options related to maintaining job history data:
Keep job history for data on media that have current overwrite protection
periods: If this option is selected, all job history data for any media to which
an overwrite protection policy is currently assigned is maintained. After the
overwrite protection policy of a media expires, its job history data can be
deleted.
Keep job history for specified number of days: This option, if selected,
specifies the number of days to keep job history data in the database before it is
deleted. The job history data includes summary statistics for a job and details
about media, devices, and backup sets that were used to process the job.
You can also specify the number of days to keep the following data in the Backup
Exec database:
Job logs: A job log includes detailed information about the job.
Alert history: Alert history data includes property and response information for
the alert.
Reports: Report data includes property information about report jobs that were
generated. The report itself is not deleted.
Audit logs: The audit log includes information about operations that are
performed in Backup Exec.
Additional database maintenance tasks
Automatic database consistency checks are not enabled by default. A database

consistency check checks the physical and logical consistency of data in the
database. Symantec recommends that you periodically perform a consistency
check, preferably at a time of minimal Backup Exec activity.
Symantec recommends that you regularly back up the Backup Exec database. To
create a data dump ensure that the Save contents of database to the Backup Exec
data directory check box is marked. This check box is marked by default.
A data dump is a flat file (BEDB.bak) in ..\Data directory that contains a
dump of an active SQL database file. This file is maintained until the next database
maintenance operation is performed, and then this file is overwritten. Selecting
this option enables you to recover the database in the event of a failure.
If you choose to automatically optimize the database size, Backup Exec
reorganizes fragmented pages and decreases the size of the physical database to ten
percent more than the amount of disk space actually used.
393 Lesson 9 Database Maintenance

95
Using Backup Exec Utility

This topic describes how you can manually maintain the Backup Exec database.
You use the Backup Exec Utility (..\Program Files\Symantec\ Backup
Exec\BEUtility.exe or BEUtility) to perform manual maintenance on
the Backup Exec database.
Backup Exec Utility also enables you to perform configuration and maintenance
on a Backup Exec server, such as running diagnostics and managing services.
394 96
With the Backup Exec Utility, you can perform the following tasks:
Add, remove, and configure logical groups of Backup Exec servers.
With logical groups, you can perform operations on all of the computers in a
group at the same time. These operations include, starting or stopping services
and configuring application service security, such as changing service account
information.
Configure startup options for one or more of the servers in a group.
Start immediate database utility operations on the Backup Exec database
(BEDB).
You can start database dumps and run database consistency and data integrity
checks.
Perform operations for the Backup Exec Archiving Option.

Maintaining a database
To maintain a Backup Exec database using the Backup Exec Utility, perform the
following tasks:
1 Select the Backup Exec server on which database maintenance has to be
performed.
2 Select a database maintenance task to be performed from the Task pane.
Database tasks are listed in the Task pane of the BEUtility interface and are
enabled when you select a Backup Exec server on which to perform
maintenance.
The following table provides a synopsis of the commonly used database tasks:
Task/Function
Description
Check Database
Consistency
Checks the validity of the database
Age Database
Deletes old information from the database
Compact Database
Removes unused space from the database
Dump Database
Backs up the database
Rebuild Indices
Rebuilds the database indices if the

indices become corrupt
Repair Database
Repairs a database

97
Task/Function
Description
Recover Database
Repairs a database
Change Database
Access
Grants or revokes a user's database access
New Backup Exec

Database Location
Changes the Microsoft SQL Server

instance that the database uses
Copy Database
Copies an existing database from a

computer using a specific name to another
computer that uses the same name
CAUTION
396 98
Improper use of BEUtility can result in configuration changes

that may prevent Backup Exec from running.

Checking database consistency

Always check the consistency of the Backup Exec database before you back it up.
By performing a consistency check, you determine whether a database is valid or
not. If the consistency check finds problems, correct them before backing up the
database.
To perform a consistency check on a Backup Exec database, using BEUtility,

perform the following steps:
1 Select the relevant Backup Exec server from either the Backup Exec Server
Groups subnode or from the All Backup Exec Servers subnode.
2 Select Database Tasks > Check Database Consistency from the Task pane.
3 After the operation completes, click Close on the Operation Progress screen.

99
Dumping a database
Dumping a database is another term for backing up a database. Dumping the
Backup Exec database means that you copy the database in its current state to a flat
file (BEDB.bak) in the ..\Data directory.
You can schedule a daily backup (dump) of the Backup Exec database when you
configure automatic database maintenance. But there are times when you may
want to manually back up the database.
For example, you must back up the database prior to upgrading Backup Exec or
before you perform maintenance on the Backup Exec server.
Use the Dump Database function of BEUtility to manually back up the database
to your hard drive. After dumping the database, back up the Backup Exec server so
that you can recover the database if the Backup Exec server fails.
398 910
To dump the database, using BEUtility, perform the following steps:

1 Select a Backup Exec server from either the Backup Exec Servers Group
subnode or from All Backup Exec Servers subnode.
2 Select Database Tasks > Dump Database from the Task pane.
3 After the operation finishes, click Close on the Operation Progress screen.

The database is copied to a flat file (BEDB.bak) in the C: \Program Files

\Symantec \Backup Exec\Data directory.

911
Recovering and repairing a database

This section describes tasks involved with recovering the Backup Exec database.
You can use BEUtility to recover the Backup Exec database.
The following table provides a description of repairing and recovering a Backup

Exec database:
400 912
Task
Description
Repair Database
Repairs database problems found during a

database consistency check
Recover Database
Restores a lost or corrupted database

Repairing a database
Before you back up the Backup Exec database, run a consistency check to ensure
that the database is valid. If the consistency check encounters a problem, such as a
database mismatch, you must repair the database before you back it up. This is
accomplished using the Repair Database option.
To repair a Backup Exec database, using BEUtility, perform the following

steps:
1 Select the relevant Backup Exec server from either the Backup Exec Server
Groups subnode or from the All Backup Exec Servers subnode.
2 Select Database Tasks > Repair Database from the Task pane.

913
402 914
After the operation finishes, click Close on the Operation Progress screen.

Recovering a database
If your Backup Exec database becomes corrupted or fails completely, you can
restore using the Recover Database option, provided you have backed up the
database to the Backup Exec ..\Data directory.
To recover a database using BEUtility, perform the following steps:

1 Select a Backup Exec server for which you want to recover the database.
2 Select Database Tasks > Recover Database from the Task pane.
3 Select the Database instance to be recovered and select the appropriate
Recovery method option.
The following table discusses the available options:
Option
Description
Use best recovery

method for current
configuration (Default
option)
This option attempts to fix and recover the existing

database before performing one of the following:
Deleting the database and creating a new database
Deleting the database and recovering from the
previous database dump
Drop existing database

and reload from backup
This option deletes the existing database and restores

the database from the backup file (BEDB.bak).
When you select this option, the existing database is
deleted and is replaced with the copy of the database
that was dumped to the Backup Exec data directory.

915
Option
Description
Drop existing database

and reload from base
This option deletes the existing database and creates,

in its place, a new and empty database,
BEDB_Dat.bak
Note: The Drop existing database and reload from backup and Drop existing
database and reload from base options must be used only as last resort
with guidance from Symantec technical support. Due to the impact of
selecting, Drop existing database and reload from base all media
immediately becomes imported.
After the Drop existing database and reload from base option is selected, an
empty database is created. As a result:
Existing selections are lost.
B2D folders have to be created again.
All existing media becomes imported.
All media sets have to be re-created.
404916

After the operation finishes, on the Operation Progress screen, click Close.

917
Defining the database location

This topic describes the method to change the location of a Backup Exec database
and copy the database to a new location.
New Backup Exec Database Location option lets you change the Microsoft SQL
server instance that the Backup Exec Database uses. The new location can be on
another computer running Microsoft SQL server, or on the same computer running
a different instance of SQL server
406 918

Updating configuration for a new server name

Update Configuration for New Backup Exec Server Name lets you update a
Backup Exec server computer name without reinstalling Backup Exec. You can
also update the domain name if you placed the Backup Exec server in a different
domain.
Using Update Configuration for New Backup Exec Server Name does not
change the Backup Exec server name that is included inside existing backup
definitions. If you use this task to update the Backup Exec server name, you must
recreate all of the backup definitions for that Backup Exec server. Otherwise, the
backup jobs fail.
Additionally, when you create a restore job that restores data to the original
Backup Exec server, you must redirect all restore data to the newly named Backup
Exec server.
To update the configuration for a new Backup Exec server name:
1 Select a Backup Exec server from either a Backup Exec server group or from
All Backup Exec Servers that you have renamed.
2 In the task pane, under Services Tasks, click Update Configuration for New
Backup Exec Server Name.
3 Change any of the options as appropriate.
4 Click OK.
5 When the operation finishes, click Close.

919
Changing the location of a Backup Exec database
408 920
Consider changing the location of a Backup Exec database if:

Your Backup Exec environment increases in size.
With the increase in number of client machines, the amount of disk space
required by the Backup Exec database increases, as well. Therefore, you may
need to move the database to a larger volume.
You want MS-SQL server to manage the database instead of SQL server
Express Edition.
If you have another server running a full version of MS-SQL server, you can
have that server manage the Backup Exec database, but you may need to move
the database to the other server.
You install the Backup Exec Central Administration Server Option (CASO).
Under CASO, you can move all media server databases to a central location.
You are using the Backup Exec Archive Option. This is because the Backup
Exec Archive Option adds several additional databases that are not present
otherwise. In such a case, you may consider using a full version of SQL.

Changing the BEDB location: Requirements
When you change the location of the Backup Exec database, the new location must
meet the requirements listed on the slide.

921
Setting the database location

You establish the initial Backup Exec database location when you install Backup
Exec on the media server.
After Backup Exec is installed, you can change the MS-SQL Server instance that
the database uses by performing the following steps within BEUtility:
1 Select a Backup Exec server for which you want to change the database
location.
2 In the task pane, select Database Tasks > New Backup Exec Database
Location.
410 922

Select a Destination SQL Server instance from the drop-down box.

Click OK. A message is displayed stating that the Backup Exec services will
be shut down.
5 Click Yes to continue.
6 After the operation completes successfully, click Close.
3
411

Lesson 9 Database Maintenance
923
412 924


100 002704 A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

100 002704 A

Uploaded by

Copyright:

Available Formats

CONFIDENTIAL - NOT FOR DISTRIBUTION

Copyright 2012 Symantec Corporation. All rights reserved.

Copyright 2012 Symantec Corporation. All rights reserved.

CONFIDENTIAL - NOT FOR DISTRIBUTION

Copyright 2012 Symantec Corporation. All rights reserved.

Lesson 5: Backing Up Data

Lesson 6: Restoring Data

CONFIDENTIAL - NOT FOR DISTRIBUTION

Lesson 8: Virtual Machine Conversion

Copyright 2012 Symantec Corporation. All rights reserved.

Lesson 9: Database Maintenance

CONFIDENTIAL - NOT FOR DISTRIBUTION

Symantec Backup Exec 2012: Install and Configure

Copyright 2012 Symantec Corporation. All rights reserved.

About this course

Copyright 2012 Symantec Corporation. All rights reserved.

CONFIDENTIAL - NOT FOR DISTRIBUTION

Symantec Backup Exec 2012: Install and Configure

After completing this course, you will be able to:

Copyright 2012 Symantec Corporation. All rights reserved.

CONFIDENTIAL - NOT FOR DISTRIBUTION

Data protection: Is backup or restore the priority?

Copyright 2012 Symantec Corporation. All rights reserved.

CONFIDENTIAL - NOT FOR DISTRIBUTION

Symantec Backup Exec 2012: Install and Configure

Data protection plan

CONFIDENTIAL - NOT FOR DISTRIBUTION

Copyright 2012 Symantec Corporation. All rights reserved.

Copyright 2012 Symantec Corporation. All rights reserved.

CONFIDENTIAL - NOT FOR DISTRIBUTION

Symantec Backup Exec 2012: Install and Configure

Symantecs education and support resources

Copyright 2012 Symantec Corporation. All rights reserved.

CONFIDENTIAL - NOT FOR DISTRIBUTION

Copyright 2012 Symantec Corporation. All rights reserved.

Symantec Connect provides the following resources:

Symantec Connect is responsive to the needs of Symantec customers. Features of

CONFIDENTIAL - NOT FOR DISTRIBUTION

Symantec Backup Exec 2012: Install and Configure

Copyright 2012 Symantec Corporation. All rights reserved.

Backup Exec Fundamentals

CONFIDENTIAL - NOT FOR DISTRIBUTION

Copyright 2012 Symantec Corporation. All rights reserved.

CONFIDENTIAL - NOT FOR DISTRIBUTION

Symantec Backup Exec 2012: Install and Configure

Data backup basics

Copyright 2012 Symantec Corporation. All rights reserved.

CONFIDENTIAL - NOT FOR DISTRIBUTION

Advantages of data backup

Copyright 2012 Symantec Corporation. All rights reserved.

CONFIDENTIAL - NOT FOR DISTRIBUTION

Symantec Backup Exec 2012: Install and Configure

Symantecs backup solution offerings

Copyright 2012 Symantec Corporation. All rights reserved.

Symantec Backup Exec powered by patented V-Ray technology unifies physical

CONFIDENTIAL - NOT FOR DISTRIBUTION

Copyright 2012 Symantec Corporation. All rights reserved.

CONFIDENTIAL - NOT FOR DISTRIBUTION

Symantec Backup Exec 2012: Install and Configure

Back up to the cloud

Copyright 2012 Symantec Corporation. All rights reserved.

Like other SaaS applications, online backup is an alternative to an on-premise

CONFIDENTIAL - NOT FOR DISTRIBUTION