BE 11d (rev. 7170) Admin Guide (English).pdf - Symantec

March 2007
Symantec Backup Exec TM 11d for
Windows Servers
Administrator’s Guide

Symantec Legal Notice
Copyright © 2007 Symantec Corporation. All rights reserved. Symantec, Backup Exec, and the
Symantec logo 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.
The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be reproduced in
any form by any means without prior written authorization of Symantec Corporation and its
licensors, if any.
THE DOCUMENTATION 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 DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS
SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be “commercial computer software” and
“commercial computer software documentation” as defined in FAR Sections 12.212 and DFARS
Section 227.7202.
Symantec Corporation
20330 Stevens Creek Boulevard
Cupertino, CA 95014
http://www.symantec.com
2 Administrator’s Guide

Administrator’s Guide - Table of Contents
Chapter 1. Introducing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
What’s new in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
What’s new in Backup Exec agents and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Backup Exec agents and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Media server options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Client protection options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Groupware agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Online database agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Disaster recovery option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Storage options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
How Backup Exec works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Chapter 2. Installing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Before you install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Checking your environment before installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
About the Backup Exec services account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Changing Windows security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
About Microsoft SQL Server 2005 Express Edition components
installed with Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
About Backup Exec’s standard features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Installing Backup Exec to a local computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Installing Backup Exec options to the local computer . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Installing Backup Exec to remote computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Installing Backup Exec options to remote computers . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Installing the Remote Agent for Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Installing the Remote Agent and the Advanced Open File Option to a
remote computer in the backup selections list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3

Installing the Remote Agent and Advanced Open File Option in an
Active Directory network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Push-installing the Remote Agent and the AOFO using the command line . . . 103
Installing the Remote Agent to an Itanium-based or x64-based
operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Using a command prompt to install the Remote Agent on a remote
32-bit computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Using a command prompt to uninstall the Remote Agent from a
remote 32-bit computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Using a command script to install the Remote Agent and AOFO on an
Itanium-based or x64-based operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Using a command script to uninstall the Remote Agent and AOFO on an
Itanium-based or x64-based operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Installing the Backup Exec Remote Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Installing Backup Exec using the command line (silent mode) . . . . . . . . . . . . . . . . . 111
Command line switches for Backup Exec silent mode installation . . . . . . . . . . . 112
Installing the Remote Administrator using the command line . . . . . . . . . . . . . . 116
Uninstalling Backup Exec using the command line . . . . . . . . . . . . . . . . . . . . . . . . 117
Creating and using installation parameter files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Using a clone CD image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Creating a clone CD image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Installing locally using a clone CD image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Installing to a remote system using a clone CD image . . . . . . . . . . . . . . . . . . . . . . 121
About the installation log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Repairing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Starting and stopping Backup Exec services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Uninstalling Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Uninstalling Backup Exec options from the local media server . . . . . . . . . . . . . . . . . 125
About updating Backup Exec with LiveUpdate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Scheduling automatic updates using LiveUpdate . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Running LiveUpdate manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Viewing installed updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
4 Administrator’s Guide

Viewing license information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Upgrading from previous versions of Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Upgrading Backup Exec options on remote computers . . . . . . . . . . . . . . . . . . . . . 130
Chapter 3. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Before starting Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Starting Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
Using the Getting Started with Backup Exec page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Using the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Using Backup Exec dialog boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Frequently asked questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Backup Exec defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Changing default preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Changing device and media job defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Chapter 4. Configuring Backup Exec settings and options . . . . . . . . . . . . . . . . . . . . . . . 145
Configuring logon accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Default backup exec logon account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Backup Exec System Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Creating a Backup Exec logon account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Editing a Backup Exec logon account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Changing a Backup Exec logon account password . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Replacing a Backup Exec logon account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Deleting a Backup Exec logon account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Changing your default Backup Exec logon account . . . . . . . . . . . . . . . . . . . . . . . . . 154
Creating a new Backup Exec System Logon Account . . . . . . . . . . . . . . . . . . . . . . . . 154
Copying configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Copying logon account information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Configuring the audit log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Viewing the audit log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Administrator’s Guide - Table of Contents 5

Configuring database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Configuring columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Hiding a column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Displaying a column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Rearranging columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Sorting columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Chapter 5. Managing devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
Viewing storage devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Viewing media in storage devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Configuring storage devices by using the Device Configuration Wizard . . . . . . . . . 171
Adding devices by using the Hot-swappable Device Wizard . . . . . . . . . . . . . . . . . . . . 173
Installing Symantec device drivers by using the Symantec Device Driver
Installation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Pausing and resuming devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Renaming a robotic library or device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
About device pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Creating device pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Adding devices to a device pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Setting priorities for devices in a device pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Deleting devices from a device pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Deleting device pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Retargeting a scheduled job from a deleted device pool or media set . . . . . . . . . 181
Renaming a device pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Viewing device pool properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
About cascaded drive pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Requirements for using cascaded drive pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Creating a cascaded drive pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Adding drives to a cascaded drive pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Deleting drives from a cascaded drive pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Deleting a cascaded drive pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
6 Administrator’s Guide

Renaming a cascaded drive pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Viewing properties of a cascaded drive pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Running diagnostics on a media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Viewing media server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Viewing a media server’s general properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Viewing a media server’s system properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Viewing a media server’s active job and alert statistics . . . . . . . . . . . . . . . . . . . . . 192
Viewing a media server’s installed licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Viewing the location of Backup Exec databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Viewing storage device properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Viewing a device’s general properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Viewing a device’s configuration properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Viewing a device’s SCSI information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Viewing a device’s statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Viewing a device’s cleaning properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Viewing and specifying types of media for a device . . . . . . . . . . . . . . . . . . . . . . . . 205
About robotic libraries in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Enabling robotic library support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Configuring a robotic library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Viewing robotic library properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Creating robotic library partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Redefining robotic library partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
About backup-to-disk folders and files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Requirements for creating a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . 219
Requirements for creating a removable backup-to-disk folder . . . . . . . . . . . . . . . 220
Creating a backup-to-disk folder by using the Backup-to-disk Wizard . . . . . . . . . . . 221
Creating a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Configuring advanced options for a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . 225
Setting defaults for new backup-to-disk folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Sharing an existing backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Administrator’s Guide - Table of Contents 7

Renaming a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Changing the path of a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Deleting a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Recreating a backup-to-disk folder and its contents . . . . . . . . . . . . . . . . . . . . . . . . 231
Pausing and resuming a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Renaming a backup-to-disk file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Deleting a backup-to-disk file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Recreating a deleted backup-to-disk file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Using Microsoft’s Removable Storage feature with Backup Exec . . . . . . . . . . . . 234
Using media in drives managed by Removable Storage . . . . . . . . . . . . . . . . . . . . . 235
Monitoring Backup Exec and Removable Storage . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Removing the Backup Exec pool from Removable Storage . . . . . . . . . . . . . . . . . . 237
Creating utility jobs to help manage devices and media . . . . . . . . . . . . . . . . . . . . . . . 237
Inventorying media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Inventorying all drives when Backup Exec services start . . . . . . . . . . . . . . . . . . . 240
Erasing media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Erasing backup-to-disk files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Retensioning a tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Formatting media in a drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Labeling media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Ejecting media from a drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Setting up cleaning jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Importing media to a robotic library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Exporting media from a robotic library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Locking the robotic library’s front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Initializing the robotic library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Unlocking the robotic library’s front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Exporting expired media from a robotic library . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
8 Administrator’s Guide

Chapter 6. Managing media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
About media in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Media overwrite protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Default media set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Creating media sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Running the Media Set Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Deleting a media set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Renaming a media set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Changing general media set properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Media overwrite protection levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Setting the search order for overwritable media . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
About overwriting allocated or imported media . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Setting defaults for media management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Auditing media operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Media labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Imported media labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Bar code labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280
Bar code rules in mixed media libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Renaming media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
About WORM media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Cataloging media while reviewing devices or media . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Creating a restore job while reviewing media or devices . . . . . . . . . . . . . . . . . . . . . . . 286
Media locations and vaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Creating media vaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Configuring vault rules for media sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Finding media in a location or vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Renaming a media vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Deleting a media vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Moving media to a vault or to the offline media location . . . . . . . . . . . . . . . . . . . . . . . 290
Scanning bar code labels to move media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Administrator’s Guide - Table of Contents 9

Scheduling a job to move media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Using the Vault Wizard to move media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Using the drag and drop method to move media . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Using the Move to vault task to move media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Removing damaged media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Deleting media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Associating media with a media set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Viewing general media properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Viewing media statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Media rotation strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Son media rotation strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Father/son media rotation strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Grandfather media rotation strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Chapter 7. Preparing for backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305
About backup strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Choosing a backup strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Understanding backup methods and their advantages . . . . . . . . . . . . . . . . . . . . . 308
Understanding the archive bit and backup methods . . . . . . . . . . . . . . . . . . . . . . . 312
Understanding modified time and backup methods . . . . . . . . . . . . . . . . . . . . . . . . 313
Selecting data to back up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
About using fully qualified computer names in backup selections . . . . . . . . . . . . . . 316
About the Computer Name node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
About the Favorite Resources node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Adding a Windows system to the Favorite Resources node . . . . . . . . . . . . . . . . . 319
Deleting a Windows system from the Favorite Resources node . . . . . . . . . . . . . . 320
About the Domains node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Adding an Active Directory domain to the Active Directory Domains node . . . 321
About the Oracle Real Application Clusters node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
About the NDMP Devices node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
10 Administrator’s Guide

About the Microsoft SharePoint Server Farms node . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
About the User-defined Selections node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Adding a user-defined selection to the User-defined Selections node . . . . . . . . 323
About the Workstation Agents node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Selecting Distributed File System (Dfs) links for backup . . . . . . . . . . . . . . . . . . . . . . . 324
Including or excluding files for backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
About selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Creating selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Holding jobs that back up a selection list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Merging and replacing selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Deleting selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Editing selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Editing the Excludes selection list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Setting priority and availability windows for selection lists . . . . . . . . . . . . . . . . . 334
Creating separate selection lists for each computer or resource . . . . . . . . . . . . . 335
Creating a custom filter for Backup Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . 336
Filtering backup selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Searching selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Viewing the history for backup selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Viewing a summary for a selection list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Using resource discovery to search for new resources . . . . . . . . . . . . . . . . . . . . . . . . . 339
About the Backup Exec Shadow Copy Components file system . . . . . . . . . . . . . . . . . 341
How the Shadow Copy Components file system is affected by upgrades . . . . . . 343
Chapter 8. Backing up data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Creating a backup job by using the Backup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Preventing the Backup Wizard from launching from the Backup button . . . . . 348
Creating a backup job by setting job properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Selections options for backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Changing the order for processing backup selections . . . . . . . . . . . . . . . . . . . . . . . 351
Administrator’s Guide - Table of Contents 11

Changing and testing logon accounts for resources . . . . . . . . . . . . . . . . . . . . . . . . 352
Device and media options for backup jobs and templates . . . . . . . . . . . . . . . . . . . 354
General options for backup jobs and templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Advanced options for backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Pre/post commands for backup or restore jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Scheduling jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
About the scheduling calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Scheduling a job to run on specific days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Scheduling a job to run on recurring week days . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Scheduling a job to run on recurring days of the month . . . . . . . . . . . . . . . . . . . . 372
Scheduling a job to run on a day interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Setting the effective date for a job schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Setting the time window for a scheduled job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Restarting a job during a time interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Excluding dates from a schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Configuring default schedule options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Using Backup Exec’s Windows Explorer interface to back up data . . . . . . . . . . . . . . 377
Setting up Backup Exec to create backups from Windows Explorer . . . . . . . . . . 378
Submitting a backup job from Windows Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Archiving data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Duplicating backed up data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Verifying a backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Creating a test run job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Setting test run default options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Chapter 9. Customizing backup options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389
Setting default backup options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Setting default pre/post commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Specifying backup networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
About using IPv4 and IPv6 in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
12 Administrator’s Guide

Setting default backup network and security options . . . . . . . . . . . . . . . . . . . . . . . 400
Changing the backup network for a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Using Backup Exec with firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Browsing systems through a firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Encryption keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Encryption types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Restricted keys and common keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Pass phrases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
About using encryption with compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
About encryption key management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Creating an encryption key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Selecting an encryption key for a backup job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Setting a default encryption key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Removing the default status from an encryption key . . . . . . . . . . . . . . . . . . . . . . . 412
Replacing an encryption key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Deleting an encryption key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
About restoring encrypted data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
About cataloging media that contains encrypted backup sets . . . . . . . . . . . . . . . 414
Chapter 10. Policies and templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Creating a new policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Editing a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Deleting a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .418
Using an example policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Using templates in policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Migrating templates from previous versions of Backup Exec . . . . . . . . . . . . . . . . 421
Adding a backup template to a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Setting the schedule for a template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Adding an export media template to a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Importing a template into a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Administrator’s Guide - Table of Contents 13

Editing a template in a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Deleting a template from a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Setting template rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Changing template rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Deleting template rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Creating jobs using policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Viewing the policies that protect selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Editing the next occurrence of a policy-based job . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Deleting a job created from a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Renaming a job created from a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
About duplicate backup set templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Adding a duplicate backup template to a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Chapter 11. Administrating Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .439
Copying jobs, selection lists, and policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Monitoring jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Viewing and changing active jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Cancelling an active job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Placing an active job on hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Viewing and changing scheduled jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Viewing and changing completed jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Viewing the Backup Exec System Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Filtering jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
About managing custom filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Creating a custom filter for jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Creating a custom filter for current jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Creating a custom filter for jobs in the job history . . . . . . . . . . . . . . . . . . . . . . . . . 470
Creating a custom filter for the calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Deleting Custom Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Editing Custom Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
14 Administrator’s Guide

Error-handling rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Creating a custom error-handling rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Custom error-handling rule for recovered jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Cluster failover error-handling rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Setting thresholds to recover jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Chapter 12. Restoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Restore jobs and the catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Setting catalog defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Catalog levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Restoring data by using the Restore Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Preventing the Restore Wizard from launching from the Restore button . . . . . 487
Restoring data by setting job properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Device options for restore jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
About restoring file permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Restoring System State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
About restoring Shadow Copy Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
About restoring utility partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
About restoring EFI system partition data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Restoring Distributed File System (Dfs) links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
About restoring media created with other backup software . . . . . . . . . . . . . . . . . 506
Selecting data to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .508
Creating a restore selection list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Including or excluding files for restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Searching for files to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Name and resource options for catalog search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Date modified options for catalog search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Restore jobs and media libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Changing and testing resource credentials for restore jobs . . . . . . . . . . . . . . . . . . . . 516
Redirecting a restore job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .517
Administrator’s Guide - Table of Contents 15

Using redirected restore for Active Directory,
Active Directory Application Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Setting defaults for restore jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Specifying the restore network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
Canceling a restore job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Chapter 13. Alerts and notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .527
Viewing alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Filtering alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Creating custom filters for alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Viewing alert properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Viewing the job log from an alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Responding to active alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Configuring automatic responses for alert categories . . . . . . . . . . . . . . . . . . . . . . 536
Clearing informational alerts from the Active Alerts pane . . . . . . . . . . . . . . . . . . 539
Configuring alert category properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Enabling or disabling alerts from the Active Alerts pane . . . . . . . . . . . . . . . . . . . 542
Deleting alerts from the alert history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Setting up notification for alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Configuring SMTP for email or mobile phone text message notification . . . . . 543
Configuring MAPI email for notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Configuring VIM email for notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Configuring a pager for alert notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Configuring recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Configuring SMTP email or mobile phone text messaging for a
person recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Configuring MAPI mail for a person recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Configuring VIM mail for a person recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Configuring a pager for a person recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Configuring a net send recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Configuring a printer recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
16 Administrator’s Guide

Configuring a group recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Scheduling notification for recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Editing recipient notification properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
Editing recipient notification methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
Removing recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Assigning recipients to alert categories for notification . . . . . . . . . . . . . . . . . . . . . . . 564
Assigning notification recipients for completed jobs . . . . . . . . . . . . . . . . . . . . . . . . . . 565
About SNMP notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Installing and configuring the SNMP system service . . . . . . . . . . . . . . . . . . . . . . . 571
Adding Windows Management Instrumentation capability . . . . . . . . . . . . . . . . . . . . 572
Uninstalling WMI providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
Chapter 14. Reports in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
Viewing reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Running a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Running and viewing a new report job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Scheduling report jobs and setting notification recipients . . . . . . . . . . . . . . . . . . 582
About custom reports in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Filter criteria and filter expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Creating a custom report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Setting filters for custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Grouping fields in custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Sorting fields in custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Setting graph options in custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Example graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Previewing custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Copying custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Editing custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .600
Deleting custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Setting default options for reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Administrator’s Guide - Table of Contents 17

Viewing report properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
Available reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Active Alerts Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
Active Alerts by Media Server Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Alert History Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Alert History by Media Server Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Audit Log Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Backup Job Success Rate Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Backup Resource Success Rate Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Backup Set Details by Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
Backup Sets by Media Set Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
Backup Size By Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Configuration Settings Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
Current Job Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Daily Network Device Utilization Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Device Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Device Usage by Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Error-Handling Rules Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Event Logs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Event Recipients Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Failed Backup Jobs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Job Distribution by Device Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Jobs Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
Machines Backed Up Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
Managed Media Servers Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
Media Required for Recovery Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
Media Set Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Media Vault Contents Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
Missed Availability Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
Move Media to Vault Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
18 Administrator’s Guide

Operations Overview Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Overnight Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Policy Jobs by Resource Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
Policy Jobs Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
Policy Properties Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Policy Protected Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Problem Files Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Recently Written Media Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Resource Backup Policy Performance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Resource Risk Assessment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Resources Protected by Policy report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Restore Set Details by Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Retrieve Media from Vault Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Robotic Library Inventory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
Scheduled Server Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Scratch Media Availability Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
Test Run Results Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Chapter 15. Disaster preparation and recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Key elements of a disaster preparation plan (DPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Returning to the last known good configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
Creating a hardware profile copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Creating an emergency repair disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Using Windows’ Automated System Recovery and System Restore to
recover a Windows XP or Windows Server 2003 system . . . . . . . . . . . . . . . . . . . . 658
Manual disaster recovery of Windows computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Manual disaster recovery of a local Windows 2000/XP/Server 2003
computer (includes non-authoritative and authoritative restore of
Active Directory for a domain controller) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Disaster recovery of a remote Windows 2000/XP/Server 2003 computer
(includes non-authoritative and authoritative restore of Active Directory
for a domain controller) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Administrator’s Guide - Table of Contents 19

Chapter 16. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .667
Hardware-related questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Backup questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
Restore questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Improving Backup Exec performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Before calling Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Finding version and revision information for your
Backup Exec installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Backup Exec diagnostic utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Using Symantec DirectAssist for troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . 683
Chapter 17. Symantec Backup Exec Workstation Agents . . . . . . . . . . . . . . . . . . . . . . . . .685
About the Backup Exec Windows 98/Me Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Installing the Backup Exec Windows 98/Me Agent on the workstation . . . . . . . 686
Configuring the Backup Exec Windows 98/Me Agent . . . . . . . . . . . . . . . . . . . . . . 687
Publishing drives and directories that use the Backup Exec
Windows 98/Me Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
Configuring the network protocol for the Backup Exec
Windows 98/Me Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
About the Backup Exec 8.x and 9.x Agent for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Requirements for running the Backup Exec 8.x and 9.x Agent for Unix . . . . . . 692
Modifying the /etc/services files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
Installing the Backup Exec 8.x and 9.x Agent for Unix on the workstation . . . . 693
About the agent configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
Loading the Backup Exec 8.x and 9.x Agent for Unix . . . . . . . . . . . . . . . . . . . . . . . 698
About troubleshooting workstation agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Chapter 18. Using Symantec Backup Exec with Server Clusters . . . . . . . . . . . . . . . . . . .701
How Backup Exec works in a Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . 702
Requirements for installing Backup Exec on a Microsoft Cluster Server . . . . . . . . 703
20 Administrator’s Guide

Installing Backup Exec on a Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . 704
Upgrading Backup Exec on a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
Installing additional Backup Exec options on a Microsoft cluster . . . . . . . . . . . . 706
Uninstalling Backup Exec from a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . 707
Creating device pools for Microsoft Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
Using checkpoint restart on Microsoft Cluster Server failover . . . . . . . . . . . . . . . . . 709
Enabling or disabling checkpoint restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
Specifying a different failover node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
Designating a new SAN SSO primary server and
central administration server in a Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . 714
Configurations for Backup Exec and Microsoft Cluster Servers . . . . . . . . . . . . . . . . . 715
Two-node cluster with locally attached storage devices . . . . . . . . . . . . . . . . . . . . . 716
Two-node cluster with tape devices on a shared SCSI bus . . . . . . . . . . . . . . . . . . . 717
Multi-node clusters on a fibre channel SAN with the SAN SSO . . . . . . . . . . . . . . 720
Using the Central Admin Server Option with Microsoft clusters and SAN SSO . . . 723
Backing up Microsoft Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
About Backing up Windows 2000 and Windows Server 2003
features in a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
Backing up local disks in a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Backing up shared disks in a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Backing up database files in a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
About Restoring data to a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
About Restoring Windows 2000 and Windows Server 2003
features to a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Restoring the cluster quorum for Windows 2000 and
Windows Server 2003 computers to a Microsoft cluster . . . . . . . . . . . . . . . . . . . . 730
Restoring the cluster quorum to a Windows 2000 or
Windows Server 2003 node running Active Directory to a Microsoft cluster . . 732
Specifying a new drive letter for the cluster quorum disk . . . . . . . . . . . . . . . . . . . 734
Using Backup Exec with Veritas Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Requirements for installing Backup Exec with the CASO option
on a Veritas Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Administrator’s Guide - Table of Contents 21

Installing Backup Exec with the CASO option on a Veritas Cluster Server . . . . . . . 737
Requirements for clustering Backup Exec using Veritas Cluster Server . . . . . . . . . 738
Clustering Backup Exec using Veritas Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . 739
About Backing up Veritas Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
About Backing Up Windows 2000 and Windows Server 2003
features in a Veritas cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
Backing up local disks in a Veritas cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
Backing up shared disks in a Veritas cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
Backing up database files in a Veritas cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
About Restoring data to Veritas Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
About Restoring Windows 2000 and Windows Server 2003
features to a Veritas cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
About backup job failover with Veritas Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . 745
Disaster recovery of a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
Using IDR to prepare for disaster recovery of a cluster . . . . . . . . . . . . . . . . . . . . . 747
Recovering nodes on the cluster using IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Recovering Backup Exec on a Microsoft Cluster using IDR . . . . . . . . . . . . . . . . . . 749
Recovering the entire cluster using a manual disaster recovery procedure . . . 749
Restoring the Microsoft Cluster data files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Recovering all shared disks in a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . 753
Recovering all shared disks in a Veritas cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
Recovering Backup Exec in a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
Troubleshooting clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
Chapter 19. Symantec Backup Exec Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . .759
Requirements for the TSM feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
Backup Exec as a TSM client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
TSM Backup Exec components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
Preparing the TSM server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
Allocating storage space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
Creating the bexpi.dsm storage volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
22 Administrator’s Guide

Running the BEX.MAC macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
Enabling TSM support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Changing the defaults for Backup Exec for Windows Servers . . . . . . . . . . . . . . . . . . 768
Changing passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
BEX.MAC macro command details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
Troubleshooting TSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Viewing TSM-related errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
TSM problem resolutions for Backup Exec for Windows Servers . . . . . . . . . . . . 775
Appendix A. Symantec Backup Exec Central Admin Server Option . . . . . . . . . . . . . . . . 779
How CASO works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
Requirements for installing CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
Choosing the location for device and media data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
Installing the central administration server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
Installing a managed media server from the central administration server . . . . . . 786
Installing a managed media server across a firewall . . . . . . . . . . . . . . . . . . . . . . . . 792
Upgrading an existing CASO installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
Upgrading an existing central administration server . . . . . . . . . . . . . . . . . . . . . . . 796
Upgrading an existing managed media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
Changing a Backup Exec media server to a central administration server . . . . . . . 799
Changing a media server to a managed media server . . . . . . . . . . . . . . . . . . . . . . . 801
Changing a managed media server to a stand-alone media server . . . . . . . . . . . . . . 802
Running the Backup Exec Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
Uninstalling Backup Exec from the central administration server . . . . . . . . . . . 803
Uninstalling Backup Exec from a managed media server . . . . . . . . . . . . . . . . . . . . . . 803
Configuring CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
Reducing network traffic in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Setting defaults for managed media servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Setting communication thresholds and active job status updates . . . . . . . . . . . . 808
Copying logs and histories to the central administration server . . . . . . . . . . . . . 810
Administrator’s Guide - Table of Contents 23

Configuring alerts in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Configuring notification in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Enabling managed media servers to use any available
network interface card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
About catalog locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Changing the catalog location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
About job delegation in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
Grouping managed media servers in pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
Restricting the backup of a selection list to specific devices . . . . . . . . . . . . . . . . 820
Creating a media server pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
Adding managed media servers to a media server pool . . . . . . . . . . . . . . . . . . . . . 821
Renaming a media server pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
Deleting a media server pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
Removing a managed media server from a media server pool . . . . . . . . . . . . . . . 823
Viewing general properties for a media server pool . . . . . . . . . . . . . . . . . . . . . . . . 823
Viewing active job and alert statistics for a media server pool . . . . . . . . . . . . . . . 824
Applying settings to all managed media servers in a pool . . . . . . . . . . . . . . . . . . . 825
Copying jobs instead of delegating jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
Requirements for duplicate backup data and synthetic backup jobs in CASO . . . . 826
How centralized restore works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
How CASO restores data that resides on multiple devices . . . . . . . . . . . . . . . . . . 828
Best practices for centralized restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
Restoring from the central administration server . . . . . . . . . . . . . . . . . . . . . . . . . 831
Administering managed media servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
Managing jobs in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
Recovering failed jobs in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
Pausing and resuming a managed media server . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
Displaying the actual state of a paused storage device . . . . . . . . . . . . . . . . . . . . . 837
Disabling and enabling communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
Stopping and starting Backup Exec services for CASO . . . . . . . . . . . . . . . . . . . . . 838
24 Administrator’s Guide

Connecting to a remote managed media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
Viewing managed media server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
Disaster Recovery in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
Appendix B. Symantec Backup Exec Advanced Open File Option . . . . . . . . . . . . . . . . . . 843
About the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
Supported snapshot technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Requirements for using the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . 847
Installing the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
Installing and uninstalling the Advanced Open File Option to
remote windows computers using the command line . . . . . . . . . . . . . . . . . . . . . . . 849
Setting defaults for the Advanced Open File Option for backup jobs . . . . . . . . . . . . 850
Using Snap Start on a Veritas Storage Foundation volume . . . . . . . . . . . . . . . . . . 855
Best practices for using the Symantec Volume Snapshot Provider . . . . . . . . . . 856
Symantec Volume Snapshot Provider cache file location . . . . . . . . . . . . . . . . . . . 856
Adjusting the Symantec Volume Snapshot Provider cache file size . . . . . . . . . . 857
Changing the default settings for the Symantec Volume Snapshot Provider . . . . . 858
Checking the job log when using the AOFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
Appendix C. Symantec Backup Exec Advanced Disk-based Backup Option . . . . . . . . . 865
Installing the Advanced Disk-based Backup Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
About the synthetic backup feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
What you can back up with synthetic backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
Requirements for synthetic backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Best practices for synthetic backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
Collecting additional information for synthetic backup and
true image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
Creating a synthetic backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
Creating a synthetic backup by using the Policy Wizard . . . . . . . . . . . . . . . . . . . . 872
Creating a synthetic backup by copying the example policy . . . . . . . . . . . . . . . . . 873
Creating a synthetic backup by adding templates to a policy . . . . . . . . . . . . . . . . 874
Administrator’s Guide - Table of Contents 25

About true image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Requirements for running true image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882
Best practices for true image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883
Creating a policy for true image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883
Creating a policy for true image restore by using the Policy Wizard . . . . . . . . . . . . 884
True image catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
Restoring a backup set enabled for true image restore . . . . . . . . . . . . . . . . . . . . . . . . 885
Troubleshooting tips for true image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
About offhost backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
Requirements for offhost backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
Requirements for offhost backup when using the
Veritas Storage Foundation for Windows Provider . . . . . . . . . . . . . . . . . . . . . . . . 890
Best practices for using offhost backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891
Setting offhost backup options for backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
Browsing remote computers for installed snapshot providers . . . . . . . . . . . . . . . 894
Restoring offhost backup data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
Troubleshooting the offhost backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
Appendix D. Symantec Backup Exec Active Directory Recovery Agent . . . . . . . . . . . . .901
Requirements for the Active Directory Recovery Agent . . . . . . . . . . . . . . . . . . . . . . . 901
Installing the Active Directory Recovery Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
About the Active Directory Recovery Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
About restoring individual Active Directory and ADAM objects . . . . . . . . . . . . . . . . 905
Restoring individual objects from an Active Directory backup . . . . . . . . . . . . . . 906
Restoring individual objects from an ADAM backup . . . . . . . . . . . . . . . . . . . . . . . 908
About recreating purged Active Directory and ADAM objects . . . . . . . . . . . . . . . . . . 908
Recreating purged Active Directory objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
Recreating purged ADAM objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
Resetting the Active Directory computer object account . . . . . . . . . . . . . . . . . . . 911
26 Administrator’s Guide

Appendix E. Symantec Backup Exec Remote Agent for Windows Systems . . . . . . . . . 913
Requirements for the Remote Agent for Windows Systems . . . . . . . . . . . . . . . . . . . . 914
Installing the Remote Agent for Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
Backing up data using the Remote Agent for Windows Systems . . . . . . . . . . . . . . . . 915
Stopping and starting the Remote Agent for Windows Systems . . . . . . . . . . . . . . . . 916
The Remote Agent Utility for Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
Starting the Remote Agent Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
Viewing activity on the remote computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Publishing the remote Windows computer to media servers . . . . . . . . . . . . . . . . 919
Appendix F. Symantec Backup Exec Remote Agent for NetWare Systems . . . . . . . . . 923
Requirements for installing the Remote Agent for NetWare Systems
on a NetWare server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924
About installing the Remote Agent for NetWare Systems on a NetWare server . . 924
Publishing NetWare servers to the NetWare agents list . . . . . . . . . . . . . . . . . . . . 925
Adding BESTART to the Autoexec.ncf file on the NetWare server . . . . . . . . . . . 926
Unloading the Remote Agent for NetWare Systems . . . . . . . . . . . . . . . . . . . . . . . . 926
About backing up NetWare servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
About backing up the NetWare Directory Services (NDS) . . . . . . . . . . . . . . . . . . . 928
Backing up NetWare servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
About restoring NetWare servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 932
Restoring NetWare servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 932
Setting default options for the Remote Agent for NetWare Systems . . . . . . . . . . . . 933
Saving configuration information for the NetWare server . . . . . . . . . . . . . . . . . . . . . 935
Disaster recovery of NetWare servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
Appendix G. Symantec Backup Exec Remote Agent for Linux or Unix Servers . . . . . . 937
Requirements for the Remote Agent for Linux or UNIX Servers . . . . . . . . . . . . . . . . 938
Installing the Remote Agent for Linux or UNIX Servers . . . . . . . . . . . . . . . . . . . . . . . 939
About creating the beoper group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940
Administrator’s Guide - Table of Contents 27

Installing Remote Agent for Linux or Unix Servers by using the
installation script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940
Installing Remote Agent for Linux or Unix Servers using
the SSH (Secure Shell) protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943
Publishing Linux and UNIX hosts to a media server . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
About editing the ralus.cfg file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945
About ralus.cfg format components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945
About file and directory exclusions in ralus.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946
Creating a Linux or UNIX logon account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946
Backing up Linux and UNIX servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947
About protecting Novell Open Enterprise Server components on
SUSE Linux Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
Requirements for Novell Open Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . 949
Backing up OES components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
Restoring Novell OES components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 951
Setting Linux/Unix properties for Remote Agent restore jobs . . . . . . . . . . . . . . . 951
Uninstalling the Remote Agent for Linux or Unix Servers . . . . . . . . . . . . . . . . . . . . . 952
Manually uninstalling the Remote Agent for Linux or Unix Servers . . . . . . . . . . . . 953
Manually starting the Remote Agent for Linux or Unix Servers . . . . . . . . . . . . . . . . 954
Manually stopping the Remote Agent for Linux or Unix Server daemon . . . . . . . . 954
The Remote Agent for Linux and Unix Servers and the
Backup Exec 8.x and 9.x Agent for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955
Troubleshooting the Remote Agent for Linux or Unix Servers . . . . . . . . . . . . . . . . . 956
Appendix H. Symantec Backup Exec Remote Agent for Macintosh Systems . . . . . . . .959
Requirements for the Remote Agent for Macintosh Systems . . . . . . . . . . . . . . . . . . . 960
Installing the Remote Agent for Macintosh Systems . . . . . . . . . . . . . . . . . . . . . . . . . . 961
Installing the Remote Agent for Macintosh Systems using
the installation script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
Installing the Remote Agent for Macintosh Systems by
using the SSH (Secure Shell) protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
Publishing Macintosh computers to a media server . . . . . . . . . . . . . . . . . . . . . . . . 965
28 Administrator’s Guide

About editing the ralus.cfg file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965
About ralus.cfg format components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
About file and directory exclusions in ralus.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
Creating a Macintosh logon account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
Backing up Macintosh computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969
Uninstalling the Remote Agent for Macintosh Systems . . . . . . . . . . . . . . . . . . . . . . . . 971
Manually starting the Remote Agent for Macintosh Systems daemon . . . . . . . . 972
Manually stopping the Remote Agent for Macintosh Systems daemon . . . . . . . 972
The Remote Agent for Macintosh Systems and the
Backup Exec 8.x and 9.x Agent for Macintosh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
Troubleshooting the Remote Agent for Macintosh Systems . . . . . . . . . . . . . . . . . . . . 974
Appendix I. Backup Exec Desktop and Laptop Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
How the Desktop and Laptop Option Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
What’s New in DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .980
Before you install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
System Requirements for the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . 986
Installing the Backup Exec Desktop and Laptop Option . . . . . . . . . . . . . . . . . . . . . . . . 987
Deploying the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
Desktop Agent Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
Preparing for a Manual Push Deployment of the Desktop Agent . . . . . . . . . . . . . 991
Post Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .993
Setting a Recovery Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
Checking Data Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
Changing DLO Service Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
About Administrator Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
DLO Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
Configuring DLO to Use a Specific Port for Database Access . . . . . . . . . . . . . . . 1006
Using Backup Exec Retrieve With DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
Updating DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
Updating the DLO Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
Administrator’s Guide - Table of Contents 29

Updating the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
Upgrading From NetBackup Professional to DLO . . . . . . . . . . . . . . . . . . . . . . . . . 1010
Using the DLO Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
Showing the Task Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
Using the DLO Overview View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
Connecting to DLO on a different Backup Exec Media Server . . . . . . . . . . . . . . . . . 1018
Configuring DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
About DLO Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
Creating a New Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
Copying a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
Modifying a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
About Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
Default Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034
Adding a Backup Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
Defining General Backup Selection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
Including and Excluding Files or Folders from a Backup Selection . . . . . . . . . . 1038
Revision Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
Setting Options for a Backup Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
Using DLO Macros in Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
Modifying a Backup Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046
Deleting Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046
Using Delta File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
Enabling Delta File Transfer for a Backup Selection . . . . . . . . . . . . . . . . . . . . . . 1049
Adding a new Maintenance Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
Configuring a Maintenance Server for Delegation . . . . . . . . . . . . . . . . . . . . . . . . 1050
Changing the Default Maintenance Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052
Reassigning a File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052
About DLO Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
Supported Storage Location Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
Using Hidden Shares as Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054
30 Administrator’s Guide

Creating DLO Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055
Configuring a Remote Windows Share or NAS Device for
DLO Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057
Deleting DLO Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059
About Automated User Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060
Creating Automated User Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1061
Modifying Automated User Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063
Changing the Priority of Automated User Assignments . . . . . . . . . . . . . . . . . . . 1064
Viewing Automated User Assignment Properties . . . . . . . . . . . . . . . . . . . . . . . . . 1064
Deleting Automated User Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065
Configuring Global Exclude Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065
Specifying Files and Folders to Exclude from all Backups . . . . . . . . . . . . . . . . . . 1066
Specifying Email to Exclude from All Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067
Specifying Files and Folders to Exclude from Compression . . . . . . . . . . . . . . . . 1069
Specifying Files and Folders to Exclude from Encryption: . . . . . . . . . . . . . . . . . . 1070
Specifying Files and Folders to Exclude from Delta File Transfer . . . . . . . . . . . 1071
Excluding Files that are Always Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1072
Using DLO Macros to Define Global Excludes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073
Managing Desktop Agent Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074
Manually Creating New Network User Data Folders . . . . . . . . . . . . . . . . . . . . . . . 1074
Adding a Single Desktop User to DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075
Importing Multiple Desktop Users Who Have Existing Network Storage . . . . 1076
Modifying Desktop Agent User Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077
Enabling or Disabling DLO Access For a Desktop User . . . . . . . . . . . . . . . . . . . . . 1077
Deleting a User from DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
Moving Desktop Agent Users to a new Network User Data Folder . . . . . . . . . . 1079
Migrating A Desktop User to a New Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1080
Viewing a List of Desktop Agent Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
Managing Desktop Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
Modifying Computer Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
Administrator’s Guide - Table of Contents 31

Enabling or Disabling a Desktop Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085
Deleting a Desktop Computer from DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085
Backing up a Desktop from the Administration Console . . . . . . . . . . . . . . . . . . . . . . 1086
Setting Blackout Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086
Restoring Files and Folders from the DLO Administration Console . . . . . . . . . . . . 1088
Searching for Files and Folders to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1091
How to Recover DLO Servers and User Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093
Recovering Data for a Single User Using DLO Emergency Restore . . . . . . . . . . 1094
Recovering Data for a Single User without Using DLO Emergency Restore . . 1095
Recovering a Damaged or Corrupt media server . . . . . . . . . . . . . . . . . . . . . . . . . . 1096
Recovering a damaged or corrupt File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096
Monitoring DLO Job Histories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1098
Viewing the DLO Job History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1098
Setting Job History View Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1100
Viewing History Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1101
Searching History Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103
Monitoring Alerts on the DLO Administration Console . . . . . . . . . . . . . . . . . . . . . . . 1105
Configuring Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109
Managing DLO Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1110
Configuring Alerts for Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
Configuring Alert Notification Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
Configuring Recipients for Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116
Configuring SMTP Mail for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116
Configuring MAPI Mail for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . 1118
Configuring VIM Mail for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119
Configuring a Pager for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121
Configuring a SNMP Trap Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124
Configuring a Net Send Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125
Configuring a Printer Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127
Configuring a Group Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128
32 Administrator’s Guide

Scheduling Notification for Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1129
Editing Recipient Notification Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1130
Editing Recipient Notification Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131
Removing Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131
DLO Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1132
Running a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133
Viewing Report Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134
Maintaining the DLO Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1136
Clustering the Desktop and Laptop Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1136
DLO Command Line Interface Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139
DLO Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139
Commands in Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1140
About the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157
Features and Benefits of the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157
System Requirements for the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1158
Installing the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1158
Configuring the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160
Connecting to the media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160
Using local accounts on desktop computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160
Using Alternate Credentials for the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . 1161
Resetting Dialog Boxes and Account Information . . . . . . . . . . . . . . . . . . . . . . . . . 1163
Changing Your Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163
Disabling the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164
Enabling the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164
About the Desktop Agent Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165
Using the Desktop Agent to Back Up Your Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168
Managing Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169
File Grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1170
Modifying Backup Selections in the Standard View . . . . . . . . . . . . . . . . . . . . . . . 1170
Adding Backup Selections in the Advanced View . . . . . . . . . . . . . . . . . . . . . . . . . . 1172
Administrator’s Guide - Table of Contents 33

Modifying Backup Selections in the Advanced View . . . . . . . . . . . . . . . . . . . . . . 1177
Deleting Backup Selections in the Advanced View . . . . . . . . . . . . . . . . . . . . . . . . 1178
Backing up Outlook PST files Incrementally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1179
Backing Up Lotus Notes NSF Files Incrementally . . . . . . . . . . . . . . . . . . . . . . . . . 1180
Using the Desktop Agent when Lotus Notes is not
Configured for the Current User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1182
Deleting Lotus Notes E-mail Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1182
Modifying Desktop Agent Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1182
Changing Backup Job Schedule Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1183
Setting Customized Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1185
Moving the Desktop User Data Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187
Customizing Connection Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1188
Synchronizing Desktop User Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1190
How Synchronization Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192
Resolving Conflicts with Synchronized Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194
Viewing the Desktop Agent Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1195
Starting a Pending Job in the Status View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196
Suspending or Cancelling a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196
Viewing Usage Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1197
Restoring Files Using the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1199
Searching for Desktop Files to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1202
Restoring Microsoft Outlook Personal Folder Files . . . . . . . . . . . . . . . . . . . . . . . . 1203
Restoring Deleted Email Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204
Restoring Files with Alternate Stream Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204
Restoring files using Backup Exec Retrieve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204
Monitoring Job History in the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205
Viewing Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1206
Searching for Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207
Log file grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209
34 Administrator’s Guide

Using DLO with Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209
Troubleshooting the DLO Administration Console . . . . . . . . . . . . . . . . . . . . . . . . 1210
Troubleshooting the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214
Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1216
Appendix J. Symantec Backup Exec Agent for Microsoft Exchange Server . . . . . . . . 1219
About the Backup Exec Exchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219
Requirements for using the Exchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1220
Installing the Exchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1223
Recommended configurations for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1223
Exchange mailbox access requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224
Backup strategies for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1225
Automatic exclusion of Exchange data during volume-level backups . . . . . . . . 1228
Reviewing the circular logging setting for Exchange . . . . . . . . . . . . . . . . . . . . . . 1229
About restoring individual mailboxes and folders from the Information Store . . 1230
Snapshot and offhost backups with the Exchange Agent . . . . . . . . . . . . . . . . . . . . . 1231
Troubleshooting Exchange Agent snapshot and offhost jobs . . . . . . . . . . . . . . . 1233
Configuring a snapshot backup with the Exchange Agent . . . . . . . . . . . . . . . . . . 1233
Configuring an offhost backup with the Exchange Agent . . . . . . . . . . . . . . . . . . 1234
Continuous protection for Exchange data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235
Viewing the CPS console from Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1238
About using recovery points to restore individual items to a point in time . . . 1238
Best practices for continuous protection of Exchange . . . . . . . . . . . . . . . . . . . . . 1239
Setting default backup and restore options for Exchange data . . . . . . . . . . . . . . . . 1240
Backing up Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1245
About selecting individual mailboxes for backup . . . . . . . . . . . . . . . . . . . . . . . . . . 1252
Backing up individual Exchange mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255
About restoring Exchange data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1258
Requirements for restoring Exchange 2000, 2003, and 2007 . . . . . . . . . . . . . . . 1259
Requirements for restoring Exchange Server 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . 1259
Administrator’s Guide - Table of Contents 35

About restoring Exchange 2003 and Exchange 2007 data using
the recovery storage group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1260
About restoring Exchange data from snapshot backups . . . . . . . . . . . . . . . . . . . 1262
Restoring Exchange data from continuous protection backups . . . . . . . . . . . . . 1263
About restoring individual Exchange mail messages and folders
from Information Store backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264
About restoring Exchange mailboxes and public folders from
mailbox backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1265
Restoring Exchange data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1267
About redirecting Exchange restore data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1273
About redirecting Exchange storage group and database restores . . . . . . . . . . 1273
About redirecting Exchange Server 5.5 database restores . . . . . . . . . . . . . . . . . 1274
About redirecting restores of mailboxes or public folders that
were backed up separately from the Information Store . . . . . . . . . . . . . . . . . . . . 1275
Redirecting Exchange restore data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1277
Preparing for disaster recovery of Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . 1280
Disaster recovery for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281
Disaster recovery for Exchange Server 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
Appendix K. Symantec Backup Exec Agent for Microsoft SharePoint Portal Server 1287
Requirements for the SharePoint Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1288
Installing the SharePoint Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1288
Using the SharePoint Agent with SharePoint Portal Server 2001 . . . . . . . . . . . . . . 1289
Backing up SharePoint Portal Server 2001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1290
Backing up the SharePoint Portal Server database . . . . . . . . . . . . . . . . . . . . . . . . 1290
Backing up folders and documents from a SharePoint Portal workspace . . . . 1291
About restoring SharePoint Portal Servers and
SharePoint Portal workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1291
Restoring a SharePoint Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1292
Restoring a SharePoint Portal workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1292
Restoring previous versions of documents from workspace backups . . . . . . . 1293
Redirecting SharePoint Portal Server restore jobs . . . . . . . . . . . . . . . . . . . . . . . . 1294
36 Administrator’s Guide

Redirecting restored workspace data to another workspace . . . . . . . . . . . . . . . . 1295
Redirecting restored workspace data to a file path . . . . . . . . . . . . . . . . . . . . . . . . 1296
Disaster recovery of a SharePoint Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . 1297
Uninstalling and reinstalling the SharePoint Portal Server software . . . . . . . . 1298
Best practices for SharePoint Portal Server 2001 . . . . . . . . . . . . . . . . . . . . . . . . . 1298
Using the SharePoint Agent with SharePoint Portal Server 2003
and Windows SharePoint Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299
Selecting SharePoint resources for backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299
Adding a server farm to the backup selections list . . . . . . . . . . . . . . . . . . . . . . . . 1300
Disabling or enabling communication between a Web server
and Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1301
Changing the name of a farm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1302
Deleting a farm from the Microsoft SharePoint Server Farms node . . . . . . . . . 1302
Backing up SharePoint resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1303
About selecting SharePoint resources for restore . . . . . . . . . . . . . . . . . . . . . . . . . 1304
Restoring SharePoint resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304
Restoring SharePoint document libraries (Web storage system-based) . . . . . . 1306
Restoring previous versions of documents from document library
(Web storage system-based) backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306
Restoring individual documents (Microsoft SQL Server-based)
from full database backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307
Redirecting a restore job for SharePoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308
Redirecting the restore of document library (Web storage system-based)
data to another document library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1309
Redirecting the restore of individual documents to a file path . . . . . . . . . . . . . . 1310
Setting default options for SharePoint Portal Server 2003 . . . . . . . . . . . . . . . . . 1311
Appendix L. Symantec Backup Exec Agent for Lotus Domino Server . . . . . . . . . . . . . 1313
Lotus Domino Agent requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314
Installing the Lotus Domino Agent on the media server . . . . . . . . . . . . . . . . . . . . . . 1315
Viewing and selecting Lotus Domino databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1316
Configuring default Lotus Domino options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318
Administrator’s Guide - Table of Contents 37

Backing up Lotus Domino databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318
Automatic exclusion of files during volume-level backups . . . . . . . . . . . . . . . . . 1319
Supported Lotus Domino database configurations . . . . . . . . . . . . . . . . . . . . . . . . 1319
About Lotus Domino transaction logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1320
Selecting backup options for Lotus Domino databases . . . . . . . . . . . . . . . . . . . . . . . 1321
Restoring Lotus Domino databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1323
Selecting Lotus Domino databases for restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324
Selecting restore options for Lotus Domino databases . . . . . . . . . . . . . . . . . . . . . . . 1326
Redirecting restore jobs for Lotus Domino databases . . . . . . . . . . . . . . . . . . . . . 1327
Preparing for disaster recovery on a Lotus Domino server . . . . . . . . . . . . . . . . . . . . 1328
Disaster recovery of a Lotus Domino server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1329
Disaster recovery of a Lotus Domino server using archive logging . . . . . . . . . 1330
Disaster recovery of a Lotus Domino server using circular logging . . . . . . . . . 1332
Frequently asked questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1333
Appendix M. Symantec Backup Exec Agent for Microsoft SQL Server . . . . . . . . . . . . 1335
Requirements for using the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337
Installing the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337
Using Backup Exec logon accounts for SQL resources . . . . . . . . . . . . . . . . . . . . . . . . 1337
Backup strategies for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1339
Consistency checks for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1343
Using snapshot technology with the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1344
Using AOFO with the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1345
Using the ADBO with the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346
Setting backup options for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1347
Automatic exclusion of files during volume level backups . . . . . . . . . . . . . . . . . 1352
Backing up SQL databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1352
About backing up SQL filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354
Displaying filegroups on the backup selections pane . . . . . . . . . . . . . . . . . . . . . . 1355
Backing up SQL filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1355
38 Administrator’s Guide

Backing up SQL transaction logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1357
About SQL 2005 database snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358
Creating database snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1360
Setting restore options for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1362
About restoring SQL databases and filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1366
Restoring from SQL database backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1367
Restoring from SQL transaction logs up to a point in time . . . . . . . . . . . . . . . . . 1368
Restoring from SQL 2000 or SQL 2005 transaction logs up to
a named transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1369
Restoring from SQL filegroup backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1370
Restoring the entire database, a missing primary filegroup,
or a filegroup containing a deleted or changed table . . . . . . . . . . . . . . . . . . . . . . 1371
Restoring a missing or corrupted nonprimary filegroup . . . . . . . . . . . . . . . . . . . 1372
Restoring the SQL master database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1374
Redirecting restores for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1376
Reverting SQL 2005 databases using database snapshots . . . . . . . . . . . . . . . . . . 1381
Setting default backup and restore options for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . 1383
Preparing for disaster recovery of SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1388
Disaster recovery of SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1390
Recovering SQL manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1392
Appendix N. Symantec Backup Exec Agent for
Oracle on Windows or Linux Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397
About the Backup Exec Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397
Installation and configuration requirements for the Oracle Agent . . . . . . . . . . . . . 1398
Configuring the Oracle Agent on Windows computers . . . . . . . . . . . . . . . . . . . . . . . . 1399
Configuring the Oracle Agent on Linux computers . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404
Configuring database access on the media server for Oracle operations . . . . . . . . 1408
Editing an Oracle server name or logon account on the media server’s
list of authentication credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1409
Deleting an Oracle server name or logon account from the media server’s
list of authentication credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1411
Administrator’s Guide - Table of Contents 39

About upgrading the Backup Exec Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1411
About using the legacy Backup Exec Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 1412
What to do when Oracle instance information changes . . . . . . . . . . . . . . . . . . . . . . 1413
About backing up Oracle resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1413
About backing up Oracle RAC resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414
Backing up Oracle resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1415
About performing a DBA-initiated backup job for Oracle . . . . . . . . . . . . . . . . . . 1417
Configuring DBA-initiated job settings for Oracle . . . . . . . . . . . . . . . . . . . . . . . . 1419
Deleting a job template for DBA-initiated jobs for Oracle . . . . . . . . . . . . . . . . . . 1420
Setting application defaults for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421
About restoring and recovering Oracle resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1422
About DBA-initiated restore and recovery for Oracle . . . . . . . . . . . . . . . . . . . . . . . . 1424
Restoring Oracle data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1424
Redirecting a restore of Oracle data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427
Troubleshooting the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429
Disaster recovery of the Oracle instance or database . . . . . . . . . . . . . . . . . . . . . . . . . 1432
Disaster recovery scenario 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1432
Disaster recovery scenario 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1434
Appendix O. Symantec Backup Exec Agent for SAP Applications . . . . . . . . . . . . . . . . 1439
About the SAP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1440
How the SAP Agent works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1440
About using the SAP Agent with RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1441
Requirements for using the SAP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1442
About installing the SAP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1443
About SAP Agent security and privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444
About encrypting SAP data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444
Generating alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1445
About preserving the integrity of the SAP Agent catalog . . . . . . . . . . . . . . . . . . 1445
Before backing up SAP data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1446
40 Administrator’s Guide

Configuring biparam.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1447
Configuring DBA-initiated job settings for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . 1448
About system level backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1450
About backing up and restoring with the SAP Agent . . . . . . . . . . . . . . . . . . . . . . . . . 1450
Requirements for submitting jobs from remote computers . . . . . . . . . . . . . . . . 1451
Restoring data with BRRESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1451
About redirecting SAP restore jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1451
Backing up with RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1452
Restoring with RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1454
Migrating the SAP Agent catalog from _backint.mdb to _backint.xml . . . . . . . . . . 1455
Backing up a clustered SAP database on Microsoft Cluster Server . . . . . . . . . . . . . 1456
Backing up MaxDB databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1457
Restoring MaxDB databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1458
About performing disaster recovery using the SAP Agent . . . . . . . . . . . . . . . . . . . . 1459
SAP disaster recovery prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1459
Recovering a remote SAP database server from a disaster . . . . . . . . . . . . . . . . . 1460
Recovering a combination SAP database server and media server . . . . . . . . . . 1461
Appendix P. Symantec Backup Exec Agent for DB2 on Windows Servers . . . . . . . . . . 1463
About the Backup Exec DB2 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1463
Installation and configuration requirements for the DB2 Agent . . . . . . . . . . . . . . . 1464
Configuring the DB2 Agent on Windows computers . . . . . . . . . . . . . . . . . . . . . . . 1465
Configuring database access on the media server for DB2 operations . . . . . . . 1469
Editing a DB2 server name or logon account on the
media server’s list of authentication credentials . . . . . . . . . . . . . . . . . . . . . . . . . . 1471
Deleting a DB2 server name or logon account from the
media server’s list of authentication credentials . . . . . . . . . . . . . . . . . . . . . . . . . . 1472
Backing up DB2 resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1472
About DBA-initiated jobs for DB2 operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1475
Using the DB2 database archive logging methods . . . . . . . . . . . . . . . . . . . . . . . . . 1476
About the db2.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1477
Administrator’s Guide - Table of Contents 41

Editing a db2.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478
Example db2.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1479
Configuring DBA-initiated job settings for DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1480
Deleting a job template for DBA-initiated jobs for DB2 . . . . . . . . . . . . . . . . . . . . 1482
Setting application defaults for DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1482
Restoring DB2 data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484
Redirecting a restore of DB2 data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1486
About troubleshooting DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1488
Appendix Q. Symantec Backup Exec Agent for Microsoft Data Protection Manager 1489
How to install the DPM Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1489
About the DPM backup selections tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1490
About Backing Up DPM Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1491
About Backing up DPM protected servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1491
About Backing up DPM replicas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1492
About Backing up DPM shadow copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1492
About Backing up a DPM server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1493
About the DPM restore selection tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1494
About Restoring DPM databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495
About Restoring DPM protected server data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495
About Restoring DPM shadow copy data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1496
Recovering a DPM server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1497
Appendix R. Symantec Backup Exec Intelligent Disaster Recovery Option . . . . . . . . 1501
Requirements for using IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1502
Installing the IDR option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1503
Using an evaluation version of the IDR option . . . . . . . . . . . . . . . . . . . . . . . . . . . 1503
Preparing computers for IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1504
Getting started with IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1505
Manually setting data paths for the *.dr files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1507
About creating and updating recovery media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1509
42 Administrator’s Guide

Requirements for running the IDR Preparation Wizard . . . . . . . . . . . . . . . . . . . 1510
About running the IDR Preparation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1511
About creating recovery media after a disaster . . . . . . . . . . . . . . . . . . . . . . . . . . . 1511
Creating the Intelligent Disaster Recovery nonbootable CD image only . . . . . 1516
Updating bootable media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517
Copying the disaster recovery files to a diskette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1519
Preparing IDR media by using other media servers . . . . . . . . . . . . . . . . . . . . . . . 1520
About preparing to recover from a disaster by using IDR . . . . . . . . . . . . . . . . . . . . . 1521
About changing hardware in the computer to be recovered . . . . . . . . . . . . . . . . 1523
About using IDR to recover IBM computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1524
About recovering a computer and using the Disaster Recovery Wizard . . . . . . . . 1525
About encrypted backup sets and the Disaster Recovery Wizard . . . . . . . . . . . 1525
Performing an automated restore by using the Disaster Recovery wizard . . . 1526
Installing network drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1533
About altering hard drive partition sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1533
Performing a manual restore by using the Disaster Recovery Wizard . . . . . . . 1534
About Microsoft SQL Server recovery notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1536
About Microsoft Exchange recovery notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1536
About SharePoint Portal Server recovery notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 1537
About Citrix Metaframe recovery notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1537
About using IDR with the Central Admin Server Option . . . . . . . . . . . . . . . . . . . 1537
About using IDR with Veritas Storage Foundation for Windows . . . . . . . . . . . . 1537
Best Practices for IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1538
Appendix S. Symantec Backup Exec Library Expansion Option . . . . . . . . . . . . . . . . . . 1539
Setting up robotic library hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1540
Configuring multi-drive robotic libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1540
Installing the Library Expansion Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1542
Starting Backup Exec after installing the Library Expansion Option . . . . . . . . . . . 1542
Viewing robotic libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1544
Administrator’s Guide - Table of Contents 43

Appendix T. Symantec Backup Exec SAN Shared Storage Option . . . . . . . . . . . . . . . . 1547
Requirements for the SAN Shared Storage Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 1548
Installing the SAN Shared Storage Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549
About devices in the shared storage environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 1551
Monitoring drives in the shared storage environment . . . . . . . . . . . . . . . . . . . . . 1552
Viewing media in the shared storage environment . . . . . . . . . . . . . . . . . . . . . . . . 1552
Using drive pools with the SAN Shared Storage Option . . . . . . . . . . . . . . . . . . . 1553
Using device operations with the SAN Shared Storage Option . . . . . . . . . . . . . 1554
Sharing robotic libraries between Backup Exec for NetWare Servers
and Backup Exec for Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1555
Scheduling and viewing jobs in a SAN SSO environment . . . . . . . . . . . . . . . . . . 1560
Sharing media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1561
Cataloging media in SAN SSO environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1561
Media rotation in SAN SSO environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1562
Designating a new database server and setting up servers . . . . . . . . . . . . . . . . . . . . 1563
Tips for maintaining the database server and the ADAMM database . . . . . . . . 1563
Creating a standby primary database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1564
Starting and stopping Backup Exec Services on multiple servers . . . . . . . . . . . 1565
Troubleshooting and recovering failed components . . . . . . . . . . . . . . . . . . . . . . . . . 1566
Checklist for troubleshooting devices that have gone offline . . . . . . . . . . . . . . . 1566
Resetting the SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1568
Bringing devices online after an unsafe device removal event . . . . . . . . . . . . . . 1568
Best practices for SAN SSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1569
Appendix U. Symantec Backup Exec NDMP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1571
Requirements for using the NDMP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1571
About installing the NDMP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1572
Configuring the NDMP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1572
Configuring Backup Exec to use the NDMP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 1572
Backing up NDMP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1574
Restoring NDMP data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1576
44 Administrator’s Guide

Setting default backup and restore options for NDMP . . . . . . . . . . . . . . . . . . . . . . . . 1577
Appendix V. Accessibility and Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1579
Keyboard navigation and shortcuts in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . 1580
General keyboard navigation within the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1580
Keyboard navigation within dialog boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1581
Keyboard shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1582
Support for accessibility settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1586
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1587
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1599
Administrator’s Guide - Table of Contents 45

46 Administrator’s Guide

Chapter
Introducing Backup Exec
1
Symantec Backup Exec for Windows Servers is a high-performance data management
solution for Windows® servers networks. With its client/server design, Backup Exec
provides fast, reliable backup and restore capabilities for servers and workstations
across the network.
Backup Exec is available in configurations that can accommodate multi-platform
networks of all sizes.
Backup Exec configurations for multiple platforms
Backup Exec Edition Description
Symantec Backup Exec TM
for Windows® Servers
Installs on and protects many Microsoft operating systems.
For a complete list, see “System requirements” on page 79.
The Backup Exec suite includes agents and options for backing up
and restoring data on heterogeneous networks of all sizes.
For more information, see “Backup Exec agents and options” on
page 62.
Backup Exec workstation agent software protects unlimited remote
workstations running on Windows XP Professional, Windows 2000
Professional, Windows Me, and Windows 98.
Stand-alone tape drives are supported. Backup Exec also includes
support for a single drive robotic library. To enable support for
additional robotic library drives, you must purchase the Library
Expansion Option.
47

Backup Exec configurations for multiple platforms
Backup Exec Edition Description
Small Business Server
Edition (SBSE)
QuickStart Edition (QSE)
(OEM release only)
Related Topics:
“Backup Exec agents and options” on page 62
Supports Microsoft Small Business Server for Windows (Server
2005, 2003 or Windows 2000) and Standard Edition operating
systems. SBSE also includes Backup Exec agent software for
workstations running on Windows XP Professional, Windows 2000
Professional, Windows Me, and Windows 98.
The following Backup Exec agents and options are included:
◆ Exchange Agent
◆ SQL Agent
◆ Intelligent Disaster Recovery Option
◆ Advanced Open File Option
◆ Desktop and Laptop Option
You can purchase SBSE versions of the following options:
◆ Library Expansion Option
◆ Remote Agent for Windows and NetWare Systems
Note With SBSE, the Remote Agent for Windows and NetWare
Systems only supports Windows servers. For NetWare
servers or other databases, you must upgrade to the Backup
Exec for Windows Servers Edition.
Stand-alone tape drives are supported. Backup Exec also includes
support for a single drive robotic library. To enable support for
additional robotic library drives, you must purchase the Library
Expansion Option.
Installs on and protects any supported version of Microsoft
Windows Server 2003 or Windows 2000. Also includes Backup Exec
agent software for workstations running on Windows XP
Professional, Windows 2000 Professional, Windows Me, and
Windows 98.
Stand-alone tape drives are supported. Backup Exec also includes
support for a single drive robotic library. To enable support for
additional robotic library drives, you must purchase the Library
Expansion Option.
48 Administrator’s Guide

What’s new in Backup Exec
Chapter 1, Introducing Backup Exec
What’s new in Backup Exec
This release of Backup Exec includes the following new features and capabilities.
For information about new features in the Backup Exec agents and options, see “What’s
new in Backup Exec agents and options” on page 53.
New and updated features in Backup Exec
Use this new feature: To:
Additional operating system
and processor support
Install Backup Exec on computers that use the following
operating systems and processors:
◆ Microsoft Windows Storage Server 2005
◆ Microsoft Windows Small Business Server 2005
◆ Microsoft Windows Server 2003 R2
◆ Microsoft Windows XP Professional x64 Edition
◆ Microsoft Windows Server 2003 x64 Edition
◆ Intel Xeon EMT64
◆ Intel Pentium EMT64
◆ AMD Athlon
◆ AMD Opteron servers
Additional hardware support Use Backup Exec with the following hardware:
◆ Write once, read many (WORM) tape devices, which are used
to archive data that requires a long retention period
See “About WORM media” on page 283
◆ Iomega REV 1000 as a backup-to-disk automation device
◆ Microsoft's software-based iSCSI initiator
◆ SAS & SATA tape drives
Data encryption Encrypt the data that you back up with Backup Exec using
encryption keys.
See “Encryption keys” on page 407.
Automatic Environment
Check
Determine whether the computer meets the minimum
requirements for installation before you install Backup Exec.
The Backup Exec Environment Check runs automatically during
installation.
See “Checking your environment before installing” on page 72.
Push install Push-install Backup Exec and its options to up to five servers
concurrently.
49

What’s new in Backup Exec
New and updated features in Backup Exec
Use this new feature: To:
Symantec LiveUpdate Use Symantec LiveUpdate to receive updates, upgrades, and new
versions of Backup Exec. LiveUpdate installs automatically with
Backup Exec.
See “About updating Backup Exec with LiveUpdate” on page 125.
Job hold for all jobs Place all the jobs in the queue on hold so that you can make
changes to your environment. See “Placing a scheduled job or the
job queue on hold” on page 452.
Job view filters Use filters to limit the jobs that appear in Job Setup, Job Monitor,
and Alerts. In addition, new settings enable you to specify more
criteria for custom filters.
List of media associated with
a job
View a list of all the media that was used in a job. The list appears
in the job log, Job History, restore view and summary panes. This
feature simplifies the process of determining the media that is
required for a restore operation.
System Summary View the System Summary in the Job Monitor for more
convenient access.
Security information restore Restore only security information for files. Use this feature if
security information for files or directories is lost or damaged,
but the files remain intact.
View by Media restore view Select data from spanned media sets. If a backup set spans
multiple media, the view shows all of the media that is required
to restore the backup set.
Date range for restore
selections
Narrow restore view results by specifying backup date ranges.
See “Selections options for restore jobs” on page 490.
Updated job scheduler The job scheduler provides a graphical representation of run
days and excluded days. See “Scheduling jobs” on page 368.
Fully qualified domain name
support
Set up direct access to a share by entering its fully qualified
computer name. See “Selecting Distributed File System (Dfs)
links for backup” on page 324.
IPv6 support Use the IPv6 protocol for backup and restore networks. IPv4
support is still available.
50 Administrator’s Guide

New and updated features in Backup Exec
Use this new feature: To:
Chapter 1, Introducing Backup Exec
What’s new in Backup Exec
Active Directory browse Browse to the Active Directory domains in the backup selection
tree. See “About the Domains node” on page 321.
Custom reports Create custom reports that contain information to meet the
specific requirements of your organization. You can design the
graphical layout of the report or use a standard report format.
See “About custom reports in Backup Exec” on page 583.
Media operations audit Keep track of when media is overwritten, appended, erased,
formatted, or labeled. Backup Exec records the operations in the
Backup Exec database.
See “Auditing media operations” on page 278.
Media vaulting Move media to a vault in the Export Media Template. You can
choose a vault to which you want to move the media after it is
removed from robotic library slots.
You are also prompted to export media from a device when you
move media from a device to a vault using drag-and-drop.
New media vault job Automate moving media to a vault with a job.
See “Moving media to a vault or to the offline media location” on
page 290.
Backup-to-disk
enhancements
Backup-to-disk folder
sharing
Reserve disk space for backup-to-disk folders to prevent disk-full
errors and to provide early warning when the media reaches a
specific capacity threshold.
See “Configuring advanced options for a backup-to-disk folder”
on page 225.
Backup Exec features enhanced support for sharing existing
backup-to-disk folders between computers in CASO or SAN
environments.
See “Sharing an existing backup-to-disk folder” on page 228.
Selection list management Edit multiple selection lists simultaneously. Either change the
properties of each list separately, or apply the same properties to
all of the lists.
See “Editing selection lists” on page 332.
51

What’s new in Backup Exec
New and updated features in Backup Exec
Use this new feature: To:
Selection list filters Filter backup selection lists on any of the following criteria:
VCS media server failover
support
◆ Selection list name
◆ Selection list description
◆ Resource type
◆ Policy
◆ Selection lists that are not protected
See “Filtering backup selection lists” on page 337.
Use failover clustering of media servers using Veritas Cluster
Server. VCS is available with Storage Foundation for Windows.
See “Using Backup Exec with Veritas Cluster Server” on
page 735.
Automatic alert responses Set up automatic responses for specific types of alerts. See
“Configuring automatic responses for alert categories” on
page 536.
HTML installation log View the Backup Exec installation log, bkupinst, in HTML
format. With this new format, the log can provide links to tech
notes for the most common error conditions. Error messages are
displayed in red and warning messages in orange to facilitate
troubleshooting.
HTML job log View the job log using Internet Explorer.
Job log location Specify a destination other than the Backup Exec data folder for
the job log. For example, you may want to have Backup Exec post
the job log to a network share so it can be viewed remotely.
Job history View additional details, such as the job rate and error codes, in
the Job History pane.
52 Administrator’s Guide

What’s new in Backup Exec agents and options
This release of Backup Exec includes these new options:
■ “Symantec Backup Exec NDMP Option” on page 68
■ “Remote Agent for Macintosh Systems” on page 64
■ “Symantec Backup Exec Agent for DB2 on Windows Servers” on page 66
Chapter 1, Introducing Backup Exec
What’s new in Backup Exec
■ “Symantec Backup Exec Active Directory Recovery Agent (ADRA)” on page 63
The following Backup Exec options have been updated with new features and
capabilities:
Updated Backup Exec options
For more information on this
option:
Agent for Microsoft SQL
Server
See:
“Agent for Microsoft SQL Server enhancements:” on page 54
Agent for Lotus Domino Server “Agent for Lotus Domino Server enhancements” on page 55
Central Admin Server Option “Central Admin Server Option enhancements” on page 55
Agent for Microsoft Exchange
Server
Advanced Disk-based Backup
Option
Agent for Oracle on Windows
or Linux Servers
Remote Agent for Linux or
Unix Servers
“Agent for Microsoft Exchange Server enhancements” on
page 56
“Advanced Disk-based Backup Option enhancements” on
page 57
“Agent for Oracle on Windows or Linux Servers enhancements”
on page 58
“Remote Agent for Linux or Unix Servers (RALUS)
enhancements” on page 58
Agent for SAP Applications “Agent for SAP Applications enhancements” on page 59
Agent for Microsoft
SharePoint Portal Server
Intelligent Disaster Recovery
Option
“Agent for Microsoft SharePoint Portal Server enhancements”
on page 60
“Intelligent Disaster Recovery Option enhancements” on
page 60
Desktop and Laptop Option “Desktop and Laptop Option enhancements” on page 60
53

What’s new in Backup Exec
Agent for Microsoft SQL Server enhancements:
Updated SQL Server Agent options
Use this new feature: To:
Updated SQL Server support Back up and restore Microsoft SQL Server 7.0, Microsoft SQL
2000, and Microsoft SQL Server 2005.
SQL Express Use SQL Express instead of MSDE 2000.
SQL database redirected
restores
Restore SQL databases to destinations other than where they
originated. See “Redirecting restores for SQL” on page 1376.
Data stream copy Direct a copy of the actual data streams being sent to media by a
SQL database to a local directory for later use.
SQL 2005 database
snapshots
Use SQL 2005 database snapshots to quickly revert a SQL 2005
database back to the state it was in when the database snapshot
was created, without performing a full restore of the host
database.
Full Copy-only backups Back up the entire SQL 2005 database or filegroup without
affecting the original baseline backup set that is required to run
future differential or log backups.
See “Backing up SQL databases” on page 1352.
Retain replication settings Keep replication settings during a redirected restore of the SQL
2005 database.
SQL backup verification Perform a redundancy check to verify the integrity of the SQL
backup. This option works with the Verify Only Restore Job
option. See “Setting restore options for SQL” on page 1362.
Restore pre-check You can verify the integrity of the SQL data on the media and
make sure that the destination SQL database can accept the data
before the database is deleted or overwritten during a restore job.
See “Setting restore options for SQL” on page 1362.
Corrupt database restore Restore as much data as possible from a corrupt database backup.
See “Restoring a missing or corrupted nonprimary filegroup” on
page 1372.
Related Topics:
“Symantec Backup Exec Agent for Microsoft SQL Server” on page 1335
54 Administrator’s Guide

Agent for Lotus Domino Server enhancements
Chapter 1, Introducing Backup Exec
What’s new in Backup Exec
Updated R7 support. Back up Lotus Domino/Notes R7 databases in a Microsoft Cluster Server
cluster in both Active-Active and Active-Passive configurations.
Related Topics:
“Symantec Backup Exec Agent for Lotus Domino Server” on page 65
Central Admin Server Option enhancements
Updated Central Admin Server options
Use this new feature: To:
CASO catalog enhancements Choose to distribute, centralize, or replicate catalogs in the
CASO environment. A distributed catalog provides increased
performance, default centralized restore capability, and
decreased network traffic. You can browse the catalog and
perform restore operations for the managed media server from
both the managed media server and the central administration
server.
See “About catalog locations” on page 814.
Support for intermittent
network connections
Network traffic and low
bandwidth allowances
Keep device and media data in a database on managed media
servers that do not have a persistent network connection to the
central administration server. Operations can continue
uninterrupted on the managed media server even when there is
not a network connection to the central administration server.
Although the central administration server cannot delegate jobs
to the managed media server in this configuration, you can
create policies and selection lists, make the appropriate
associations, and then copy all of them from the central
administration server to the managed media server.
Configure defaults on the managed media server to
accommodate a low bandwidth network connection or to reduce
network traffic.
See “Reducing network traffic in CASO” on page 805.
CASO job monitoring Monitor jobs that are created on the local managed media server,
as well as jobs that have been delegated to the managed media
server from the central administration server. You can also hold,
delete, run, cancel, and change the priority order of the jobs that
are created on the local managed media server.
55

What’s new in Backup Exec
Updated Central Admin Server options
Use this new feature: To:
MMS job status configuration Adjust the number of seconds that a managed media server waits
between sending job status updates to the central administration
server. With many backup jobs running, you can preserve
network bandwidth by adjusting the amount of time between job
update statuses. The default is 10 seconds, which is close to
real-time monitoring.
See “Reducing network traffic in CASO” on page 805.
Related Topics:
“Symantec Backup Exec Central Admin Server Option” on page 62
Agent for Microsoft Exchange Server enhancements
Agent for Microsoft Exchange Server enhancements
Use this new feature: To:
Public folders restore redirection Redirect the restore of public folder sets to a server and
public folder other than the original source.
See “About redirecting restores of mailboxes or public
folders that were backed up separately from the
Information Store” on page 1275.
Granular restores of messages and
folders
Restore individual mail messages and folders from
Information Store full, copy, and incremental backups.
Granular restore from incremental backups is
performed from jobs that are associated with policies.
See “About using recovery points to restore individual
items to a point in time” on page 1238.
56 Administrator’s Guide

Agent for Microsoft Exchange Server enhancements
Use this new feature: To:
Continuous backup of Exchange
Server
Related Topics:
“Symantec Backup Exec Agent for Microsoft Exchange Server” on page 64
Advanced Disk-based Backup Option enhancements
Advanced Disk-based Backup Option enhancements
Use this new feature: To:
Chapter 1, Introducing Backup Exec
What’s new in Backup Exec
Use Backup Exec Continuous Protection Server (CPS) to
provide continuous backup of Exchange Server. The CPS
backup job provides complete recovery to any point in
time of the Information Store, including the latest
complete transaction log.
See “Continuous protection for Exchange data” on
page 1235.
Enable recovery points for granular restore of
individual messages or folders.
See “About using recovery points to restore individual
items to a point in time” on page 1238.
True image restore Restore volumes and directories and include data that is
contained in them at the point of any incremental or full
backup. Files that were deleted before the time of the selected
backup are not restored. With True Image Restore, Backup Exec
automatically restores data sets sequentially, beginning with
the most recent set and going backward until the last full data
set is restored.
See “About true image restore” on page 880.
Microsoft Change Journal and
synthetic backups
Use the Microsoft Change Journal, if it is available, when you
add job templates to a policy for synthetic backup jobs.
See “Best practices for synthetic backup” on page 870.
Related Topics:
“Symantec Backup Exec Advanced Disk-based Backup Option (ADBO)” on page 63
57

What’s new in Backup Exec
Agent for Oracle on Windows or Linux Servers enhancements
Agent for Oracle on Windows or Linux Servers enhancements
Use this new feature: To:
Updated Oracle Agent Use the new Oracle Agent in place of all previous versions of the
Oracle Agent.
RMAN support Back up databases with Oracle's Recovery Manager (RMAN).
The RMAN recovery catalog is used to manage the backup,
restore, and recovery of Oracle databases.
Backup Exec or RMAN console
job configuration
Oracle Real Application
Cluster support
Related Topics:
“Symantec Backup Exec Agent for Oracle® on Windows and Linux Servers” on page 66
Remote Agent for Linux or Unix Servers (RALUS) enhancements
The RALUS Agent now supports:
■ HP-UX
■ Novell Open Enterprise Server 1.0 on SUSE Linux
■ Macintosh OS X
Initiate backups and restores from the Backup Exec media
server or from the Oracle RMAN console.
◆ For information about backing up Oracle data, see “About
backing up Oracle resources” on page 1413.
◆ For information about restoring Oracle data, see “About
restoring and recovering Oracle resources” on page 1422.
Back up and restore standard Oracle databases, as well as
Oracle Real Application Cluster (RAC) installations. Multiple
data stream support is also available for increased performance
during backups and restores. See “About backing up Oracle RAC
resources” on page 1414.
Related Topics:
“Requirements for the Remote Agent for Linux or UNIX Servers” on page 938
58 Administrator’s Guide

Agent for SAP Applications enhancements
Agent for SAP Applications enhancements
Use this new feature: To:
Related Topics:
“Symantec Backup Exec Agent for SAP Applications” on page 66
Chapter 1, Introducing Backup Exec
What’s new in Backup Exec
Updated SAP Agent Use the new SAP Agent in place of all previous versions of the
SAP Agent.
Updated SAP support Use the latest version of SAP, including NetWeaver and
BRTools 6.40.
RMAN support Back up and restore Oracle databases by generating RMAN
scripts and invoking RMAN with them. BRTOOLS is required to
protect log files and configuration files.
59

What’s new in Backup Exec
Agent for Microsoft SharePoint Portal Server enhancements
Individual document restore. Restore individual documents from full SharePoint backups.
See “Restoring individual documents (Microsoft SQL Server-based) from full database backups” on
page 1307.
Related Topics:
“Symantec Backup Exec Agent for Microsoft SharePoint Portal Server” on page 1287
Intelligent Disaster Recovery Option enhancements
Intelligent Disaster Recovery Option enhancements
Use this new feature: To:
Dissimilar hardware support Recover systems to newer, more powerful hardware platforms.
New recovery wizard Use the new disaster recovery wizard to restore the computer
with its most recent backups. See “About recovering a computer
and using the Disaster Recovery Wizard” on page 1525.
Related Topics:
“Disaster recovery option” on page 67
Desktop and Laptop Option enhancements
Desktop and Laptop Option enhancements
Use this new feature: To:
Updated operating system
support
DLO now supports Microsoft Windows XP Professional x64
Edition. You can install and run the Desktop Agent on these
platforms in 32-bit compatibility mode. All features and
functions of the Desktop Agent are available on these
platforms.
Delta file transfer Configure DLO for delta file transfer. After the initial backup of
a file, subsequent backups transmit only those parts of the file
that have changed.
See “Using Delta File Transfer” on page 1048.
60 Administrator’s Guide

Desktop and Laptop Option enhancements
Use this new feature: To:
Related Topics:
“Symantec Backup Exec Desktop and Laptop Option” on page 64
Chapter 1, Introducing Backup Exec
What’s new in Backup Exec
Lotus Notes support Back up Lotus Notes NSF email files at the message level.
See “Backing Up Lotus Notes NSF Files Incrementally” on
page 1180.
Updated database Configure the media server to use Microsoft SQL Server 2005 or
Microsoft SQL Server 2005 Express Edition for the
administration database.
Global exclude Use expanded Global Exclude options to specify the attributes
of files that you want to exclude from backups, or that you do
not want to compress, encrypt, or back up with Delta File
Transfer. You can also exclude attachments to emails or
specific email folders from backup jobs.
See “Configuring Global Exclude Filters” on page 1065.
Easier configuration Configure default settings from one integrated dialog box.
See “DLO Default Settings” on page 1000.
Alert functionality
enhancements
Use any of the following methods to receive alerts:
- SMTP
- MAPI
- Lotus Notes email
- Paging
- Printing
- Active Directory
Active Directory support Use Active Directory settings to configure Connection Policies
and Automated User Assignments.
61

Backup Exec agents and options
Backup Exec agents and options
Several Backup Exec options are available to provide protection for your network.
Options are categorized as follows:
■ Media server options on page 62
■ Groupware agents on page 64
■ Online database agents on page 65
■ Disaster recovery option on page 67
■ Storage options on page 67
Media server options
These options allow greater control of storage resources and alternate backup
techniques on Backup Exec media servers.
Backup Exec media server options
Option Description
Symantec Backup Exec Central
Admin Server Option
Symantec Backup Exec Advanced
Open File Option
Maximizes your Backup Exec for Windows Servers
investment by providing centralized administration and
load balanced job processing functionality for existing or
newly configured Backup Exec for Windows Servers media
servers.
See “Symantec Backup Exec Central Admin Server Option”
on page 779.
Ensures that all files on your network are protected even if
they are being used. Whether used alone or in combination
with specific database agents, this option handles open files
at the volume level and is seamlessly integrated with Backup
Exec. You do not need to know which files are open ahead of
time; just set a scheduled backup to use this option.
See “Symantec Backup Exec Advanced Open File Option” on
page 843.
62 Administrator’s Guide

Backup Exec media server options
Option Description
Symantec Backup Exec Advanced
Disk-based Backup Option
(ADBO)
Symantec Backup Exec Active
Directory Recovery Agent (ADRA)
Client protection options
Chapter 1, Introducing Backup Exec
Perform the following types of backup:
Backup Exec agents and options
◆ Synthetic backup - Assembles, or synthesizes, from one
previous full or incremental backup and subsequent
incremental backups. This feature eliminates the need to
run full backups, and because the synthesis is performed
on the Backup Exec media server without accessing the
remote computer, the overall backup window and the
network bandwidth requirements are reduced.
◆ Offhost backup - Lets you move the backup operation
away from the remote computer to a Backup Exec media
server in a fiber connected SAN environment. Moving
the backup from the remote computer to a media server
performs better backups and frees the remote computer
as well.
See “Symantec Backup Exec Advanced Disk-based Backup
Option” on page 865.
Restores Active Directory or Active Directory Application
Mode (ADAM) objects and attributes without having to
perform an authoritative or non-authoritative full restore.
See “Symantec Backup Exec Active Directory Recovery
Agent” on page 901
These options provide protection for remote Microsoft Windows servers, Novell
NetWare servers, Linux and UNIX servers, and Macintosh systems on the network, as
well as automated protection of desktop and laptop systems.
Backup Exec client protection options
Option Description
Symantec Backup Exec Remote
Agent for Windows and NetWare
Systems
The Symantec Backup Exec Remote Agent for Windows and
NetWare Systems (Remote Agent) is installed as a separate,
add-on component that must be used for the backup and
restore of remote Windows or NetWare resources.
See “Symantec Backup Exec Remote Agent for Windows
Systems” on page 913 or See “Symantec Backup Exec
Remote Agent for NetWare Systems” on page 923.
63

Backup Exec agents and options
Backup Exec client protection options
Option Description
Symantec Backup Exec Remote
Agent for Linux or Unix Servers
(RALUS)
Remote Agent for Macintosh
Systems
Symantec Backup Exec Desktop
and Laptop Option
Groupware agents
Lets Windows Server network administrators perform
backup and restore operations on Linux, Unix and Solaris
workstations and servers that are connected to the network.
This agent must be running on these computers before
backup or restore operations can be performed.
See “Symantec Backup Exec Remote Agent for Linux or Unix
Servers” on page 937.
Enables Windows Server network administrators to perform
backup and restore operations on Macintosh computers that
are connected to the network.
See “Symantec Backup Exec Remote Agent for Macintosh
Systems” on page 959
Lets you protect all business data. It provides continuous
backup protection whether users are in the office or on the
road. Users can synchronize files between their desktop and
laptop.
See “Backup Exec Desktop and Laptop Option” on page 977.
Groupware agents provide non-disruptive protection for corporate email messaging and
knowledge base applications.
Backup Exec groupware agents
Agent Description
Symantec Backup Exec Agent for
Microsoft Exchange Server
Provides a fast and flexible way of protecting your Exchange
2000 and 2003 Server data. Restore individual mail
messages and folders from Information Store full, copy, and
incremental backups. Granular restore from incremental
backups is performed from jobs that are associated with
policies.
See “Symantec Backup Exec Agent for Microsoft Exchange
Server” on page 1219.
64 Administrator’s Guide

Backup Exec groupware agents
Agent Description
Symantec Backup Exec Microsoft
Agent for SharePoint Portal
Server
Symantec Backup Exec Agent for
Lotus Domino Server
Online database agents
Chapter 1, Introducing Backup Exec
Backup Exec agents and options
Protects all of the files and attributes associated with an
installation of SharePoint Portal Server 2001 or 2003.
Backup Exec, which offered the first complete backup and
recovery solution for SharePoint Portal Server, lets you back
up and restore individual workspaces and documents.
Restores can be made to the original SPS information store
or redirected to another SPS information store without
affecting other workspaces.
See “Symantec Backup Exec Agent for Microsoft SharePoint
Portal Server” on page 1287.
Provides seamless online backup protection for versions 5, 6
and 7. Using Lotus Domino APIs, the Agent for Lotus
Domino now fully supports transactional logging, providing
users with uncompromising data protection of the entire
Lotus Domino server.
See “Symantec Backup Exec Agent for Lotus Domino Server”
on page 1313.
These options allow for protection and recovery of mission-critical database
applications.
Backup Exec online database agents
Agent Description
Symantec Backup Exec Agent for
Microsoft SQL Server
Protects active databases and verifies all of your SQL v7.0
and SQL 2000 data automatically. SQL 7.0, SQL 2000 and
SQL 2005 users can customize their data protection needs
down to the filegroup level. For fast point-in-time backups,
you can use this option to run transaction log backups with
truncation. Redirected restores allow you to easily restore
SQL data to other SQL servers on the network.
See “Symantec Backup Exec Agent for Microsoft SQL
Server” on page 1335.
65

Backup Exec agents and options
Backup Exec online database agents
Agent Description
Symantec Backup Exec Agent for
Oracle® on Windows and Linux
Servers
Symantec Backup Exec Agent for
SAP Applications
Symantec Backup Exec Agent for
DB2 on Windows Servers
Symantec Backup Exec Agent for
Microsoft Data Protection
Manager
Provides seamless online backup protection for Oracle
database versions 9i (9.2 and later) and 10g and Oracle RAC.
Integrating Oracle backup with the advanced features of
Backup Exec provides data protection of both individual
table spaces as well as complete Oracle databases. You can
also include archived redo files and control files without
taking them offline.
See “Symantec Backup Exec Agent for Oracle on Windows or
Linux Servers” on page 1397.
Provides superior data protection by allowing backups of
critical data while the application is still online and in use.
The SAP Agent, certified by SAP, is a reliable solution that
provides both local and remote protection of the latest
versions of SAP databases using the SAP (BC-BRI
BACKINT) interface while enabling you to efficiently
manage your data.
See “Symantec Backup Exec Agent for SAP Applications” on
page 1439.
Allows backup and restore on Microsoft Windows servers.
Backup and restore jobs can be started from the Backup
Exec Administration Console or from a DB2 command line
processor.
See “Symantec Backup Exec Agent for DB2 on Windows
Servers” on page 1463.
Lets network administrators perform backup and restore
operations between Microsoft Data Protection Manager
(DPM) and Backup Exec.
See “Symantec Backup Exec Agent for Microsoft Data
Protection Manager” on page 1489.
66 Administrator’s Guide

Disaster recovery option
Chapter 1, Introducing Backup Exec
Backup Exec agents and options
Backup Exec’s Intelligent Disaster Recovery Option (IDR) Provides a recovery solution
for both local and remote Windows systems. This option eliminates the need to
manually re-install the entire operating system after a system crash. Using diskettes,
CD-R/CD-RW, or bootable tape, IDR gets you back online fast by allowing you to restore
from your last complete backup set - including full, incremental, differential and
working set backups.
See “Symantec Backup Exec Intelligent Disaster Recovery Option” on page 1501.
Storage options
These options allow you to extend Backup Exec’s capabilities to use larger media storage
devices or share storage resources over a SAN.
Backup Exec storage agents
Option Description
Symantec Backup Exec Library
Expansion Option (LEO)
Symantec Backup Exec SAN
Shared Storage Option (SAN SSO)
Supports multi-drive tape or optical robotic libraries and
library storage systems. When utilizing the Advanced
Device And Media Management (ADAMM) features, the
Library Expansion Option provides extensive configuration
and management capabilities which include unattended
backup and restore operations, and bar code reader and
portal support. Device partitioning lets you assign specific
robotic library slots for backup targets.
See “Symantec Backup Exec Library Expansion Option” on
page 1539.
Lets Backup Exec operate in a Storage Area Network (SAN),
providing a high performance LAN-free backup solution.
SAN SSO lets multiple distributed media servers share
common, centralized storage devices connected over a SAN.
This configuration provides greater efficiency and fault
tolerance. In addition to increasing performance and backup
speeds in the SAN environment, the Shared Storage Option
load balances backup activity across multiple Backup Exec
media servers and centralizes management tasks while
lowering the total cost of hardware ownership.
See “Symantec Backup Exec SAN Shared Storage Option” on
page 1547.
67

Backup Exec agents and options
Backup Exec storage agents
Option Description
Symantec Backup Exec NDMP
Option
Enables Backup Exec to use the Network Data Management
Protocol (NDMP) to initialize and control backups and
restores on supported NetApp Network Attached Storage
(NAS) devices.
See “Symantec Backup Exec NDMP Option” on page 1571
68 Administrator’s Guide

How Backup Exec works
Chapter 1, Introducing Backup Exec
How Backup Exec works
In Backup Exec, backup, restore, and utility operations, called jobs, are submitted using
the Administration Console. Administrators can run the Administration Console from
the media server (a Windows server with storage hardware attached) or from a remote
system. After jobs are created, they are processed by the Backup Exec server
components running on the media server. All interaction to the Backup Exec system,
such as submitting jobs, viewing results, and performing device and media operations,
can be done through the Administration Console.
Backup and restore functionality for the entire network
Disk or NAS
Back up to disk,
storage arrays or
network attached
storage provides faster
backups and
recoveries.
Application servers (local or
remote)
Protect business-critical
application and database
servers like Exchange, SQL,
Oracle, SAP, or Lotus Domino.
File servers (local or remote)
Protect business-critical data
(including open files) on file
servers, web servers, or
network shares.
Tape storage
Tape drives or
libraries provide long
term storage, disaster
recovery, and a
method for archiving
data.
Backup Exec media server
Desktops & laptops (local or
remote)
Protect the business critical
information that is not
contained on corporate
servers.
69

How Backup Exec works
Through the Administration Console, you configure settings, called default options, that
you want Backup Exec to use for most jobs. However, you can override these default
options while setting up a specific job such as a weekly backup of selected workstations.
You can create a once-only job, such as a restore of a particular file to a server, or you can
schedule recurring jobs, such as daily backup jobs.
Wizards guide you through most Backup Exec operations, including the creation of a
backup or restore job, setting up media rotation jobs, and setting media overwrite
protection.
You can monitor a job’s progress through the Job Monitor, or use Backup Exec’s
Calendar to quickly view all jobs scheduled to run for the day, week, or month.
The media server contains media and device databases designed to simplify the process
of organizing and allocating storage devices attached to your media server and to aid in
preventing media from being accidentally overwritten. Through Backup Exec’s device
management functions, you can logically group storage devices together in device pools.
Through the media management function, you can organize, track, and troubleshoot all
of the media in your library. You can define the following:
■ Overwrite protection periods to ensure that media is not accidentally overwritten.
■ Set up automatic media labeling.
■ View media statistics such as the media’s age, hours of use, number of mounts, bytes
written and read, and errors encountered, which are automatically tracked by
Backup Exec.
After a job has been processed, the job’s results are stored in a job history database. A
record of the data that was backed up is kept in Backup Exec’s catalog. The job history is
a report of what happened during the processing of the job (statistics, errors, and so on),
and the catalog file is the record from which restore selections are made.
70 Administrator’s Guide

Installing Backup Exec
Chapter
Several methods are available for installing Backup Exec. You can:
■ Use the installation wizard, which guides you through the installation process.
■ Use the command line, which is called silent mode installation. The silent mode
installation uses the Setup.exe program on the Backup Exec CD.
2
■ Use a clone CD image, which enables you to copy your installation settings from one
computer onto a CD. You can then use that CD to install Backup Exec on additional
servers using the same settings.
You can install Backup Exec and its options on a local computer, a remote computer, or
both. Additionally, you can install the Backup Exec Remote Administrator Console,
which allows you to administrate the media server from a remote Windows server or
workstation.
Before you install
Before you install Backup Exec, you should:
■ Run the Backup Exec Environment Check on the computer on which you want to
install Backup Exec. The Environment Check analyzes the computer to make sure
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 appear. Although the Environment Check runs automatically during
installation, you may want to run it manually before you install Backup Exec or
before you back up data with Backup Exec.
71

Before you install
■ Install the storage device hardware (controller, drives, robotic libraries) on the
media server. Refer to the documentation that is included with your storage device
hardware for installation instructions. Use the appropriate Windows hardware
setup functions to configure your controller and storage devices. Refer to your
Microsoft Windows documentation for more information.
■ Check your Windows security settings to make sure they work properly with the
Backup Exec service account.
■ If the drive on which you want to install Backup Exec is encrypted or compressed,
and you would like to use a default SQL Express database, verify that an
unencrypted and uncompressed drive is available for SQL Express installation.
■ Exit all other programs.
Checking your environment before installing
The Symantec Backup Exec for Windows Servers Environment Check is a utility that
runs on a computer automatically during installation and that reports the following:
■ If the computer meets the minimum requirements for installation, such as the
operating system, disk and memory space, sufficient logon account privileges.
For more information, see “System requirements” on page 79.
■ If third-party software that uses Backup Exec ports is configured correctly.
■ If required components are installed, and if they are versions that are compatible
with Backup Exec.
■ If previous versions of Backup Exec and Backup Exec options are installed.
■ If storage device hardware and associated drivers are properly installed and
recognized by the Windows operating system.
■ If the computer meets the minimum requirements for installation of the Desktop
and Laptop Option.
One of the following results are reported for each item:
Environment Check results
Result Description
Passed There are no incompatibilities to prevent the Backup Exec installation. For
hardware, this result indicates that the hardware configuration is
recognized by Backup Exec.
72 Administrator’s Guide

Environment Check results
Result Description
Chapter 2, Installing Backup Exec
Before you install
Warning An incompatibility with Backup Exec exists, but can be resolved during the
Backup Exec installation.
Failed An incompatibility with Backup Exec exists, and it will cause the
installation to fail. Action is required before you can successfully install
Backup Exec.
Although the Environment Check runs automatically during installation, you may want
to run it manually before installing Backup Exec or before backing up data with Backup
Exec.
To check your environment before installing
1. From the CD browser, click Installation, and then click Start the Backup Exec for
Windows Servers Environment Check.
2. Click Next.
3. Do any of the following:
To check the
configuration of the local
computer
To check the
configuration of a remote
computer
4. Click Next.
Check Local Environment Check.
5. If you checked Remote Environment Check in step 3, do one of the following:
To select the name of a
computer from a list
Check Remote Environment Check.
◆ Click Add Server From List.
◆ Select the computer from the list, and then click Next.
73

Before you install
To add the name of a
computer manually
To remove the name of a
computer from the list of
computers on which the
Environment Check runs
6. To save the results of the Environment Check, check Save Results To.
7. To change the location where the Environment Check results are saved, click
Change Path to browse to a new location.
8. Click Finish.
About the Backup Exec services account
All Backup Exec services on the media server run in the context of a user account
configured for the Backup Exec system services. You can create this account during the
Backup Exec installation, or you can use an existing user account. To create a service
account for Backup Exec during installation, enter the name and password of an
Administrator account for the Backup Exec services to use.
If this computer is in a domain, enter a Domain Administrators account, or an
equivalent account that is part of the Domain Admins group. In the Domain list, select
or enter the Domain name.
If this computer is in a workgroup, enter an Administrators account, or an equivalent
account that is part of the Administrators group on the computer. In the Domain list,
select or enter the computer name.
The account that you designate for Backup Exec services, whether it is a new account or
an existing user account, is assigned the following rights:
■ Authenticate as any user and gain access to resources under any user identity.
■ Create a token object, which can then be used to access any local resources.
■ Log on as a service.
◆ Click Add Server Manually.
◆ In the Domain field, type the name of the domain.
◆ In the Computer Name field, type the name of the computer.
◆ Click OK.
◆ Type the user name and password for this computer.
◆ Click OK.
◆ Select the computer from the list.
◆ Click Remove.
■ Administrative rights (provides complete and unrestricted rights to the computer).
■ Backup operator rights (provides rights to restore files and directories).
74 Administrator’s Guide

Chapter 2, Installing Backup Exec
Before you install
■ Manage auditing and security log.
Due to security implementations in Microsoft Small Business Server, the service
account must be Administrator.
On a computer that runs Windows Server 2003 or Windows XP, you cannot install
Backup Exec with a service account that has a blank password. If you attempt to do so,
the following error message appears when Backup Exec services are created:
The given password is not correct for account [server]\[username].
You can configure Windows to allow for blank passwords. For more information, see
your Windows documentation.
Changing Windows security
You can set up Windows security with the Backup Exec service account to protect your
data. Depending on how the Windows network is configured, change security properties
for the following scenarios:
■ Servers in one domain.
■ Servers and selected workstations in one domain.
■ Servers in more than one domain.
■ Servers and workstations in more than one domain.
The following procedures give the Backup Exec service account administrative rights in
the appropriate domains and workstations. You must grant the Backup Exec service
account administrative rights to give Backup Exec access to the administrative shares
(for example, C$) and the ability to protect the Windows registry.
■ For Windows 2000, use the Active Directory Users and Computers tool and
Domain and Trusts tool in the Active Directory administrative tools group.
To back up servers (only) in one domain
❖ When prompted for a user name in the Service Account window, add the name of an
existing or new Service Account (for example, Administrator) as a member of the
local Administrators group for the Domain. It is highly recommended that you also
enter a password.
75

Before you install
To back up servers and selected workstations in one domain
1. Add the name of an existing or new Service Account (for example, Administrator) as
a member of the Global Domain Admins group.
2. Ensure that on each workstation in the domain you want to back up, the Global
Domain Admins group is a member of the workstation’s local Administrators group.
To back up servers in more than one domain
1. Establish a One Way Trust Relationship between the Host Domain (the domain in
which the media server resides) and the Target Domains (the domains that are to be
backed up):
■ In the Host Domain, permit the Target Domains to trust the Host Domain.
■ In each Target Domain, trust the Host Domain.
2. In each Target Domain, add the Host Domain’s name of an existing or new Service
Account (for example, Administrator) in the local Administrators group.
To back up servers and workstations in more than one domain
1. Establish a One Way Trust Relationship between the Host and Target Domains:
■ In the Host Domain, permit the Target Domains to trust the Host Domain.
■ In each Target Domain, trust the Host Domain.
2. In each Target Domain, add the Host Domain’s name of an existing or new Service
Account (for example, Administrator) in the Local Administrators group.
3. On each workstation to back up, add the Host Domain’s name of an existing or new
Service Account (for example, Administrator) in the Local Administrators group.
About Microsoft SQL Server 2005 Express Edition components
installed with Backup Exec
The Backup Exec installation program installs Microsoft SQL Server 2005 Express
Edition components that are required to run Backup Exec. These components include
SQL Server 2005 core components and Microsoft Data Access Components (MDAC)
version 2.8.
76 Administrator’s Guide

Chapter 2, Installing Backup Exec
Before you install
Note The installation of SQL Server 2005 Express Edition components may take up to
30 minutes to complete. During that time, the installation progress bar is not
updated.
If you are running applications that use earlier versions of these components, problems
may occur due to the upgraded drivers. If problems occur, contact the vendor of the
incompatible software to obtain a version that is compatible with the MDAC.
Caution The MDAC version that Backup Exec installs as part of the installation is
incompatible with a clustered version of Microsoft SQL Server 7.0. Do not
install Backup Exec on a clustered version of SQL 7.0 server.
Backup Exec prompts you to do one of the following:
■ Install the required SQL Server 2005 Express Edition components with Backup Exec
and create a default Backup Exec instance.
■ Select a Microsoft SQL Server 2000 (with service pack 3a or later) or SQL Server
2005 instance that already exists on the network on which you want to run Backup
Exec.
If you choose to install Backup Exec into an existing SQL 2000 instance, make sure that
SQL 2000 Service Pack 3a 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.
When Backup Exec is installed into an existing instance, the Cluster Configuration
Wizard is not available.
Note If you are installing a managed media server, it is recommended that you select a
local Microsoft SQL Server 2000 (SP3a) instance on which to install the Backup
Exec database for this managed media server. Do not select the same SQL Server
instance that is used by the central administration server.
77

Before you install
About Backup Exec’s standard features
When you enter a Backup Exec license key, you can select additional features that are
available for install. The following additional features are included with the Backup Exec
license key:
Backup Exec’s standard features
Feature Description
Tape Device Drivers Installs the Symantec tape device drivers for all supported tape devices
that are attached to the server.
Online
Documentation
Enable Robotic
Library Support
Tivoli Storage
Manager Option
Installs the Backup Exec Administrator’s Guide in a pdf file format.
Enables support for multi-drive tape or optical robotic libraries and library
storage systems.
Enables the TSM server’s storage resources to appear as a tape robotic
library in a list of target devices on the Backup Exec server. Backup Exec
administrators can then direct the output of any Backup Exec job to the
TSM server by selecting the name of the TSM robotic library as the
destination when submitting the job. For more information, see “Symantec
Backup Exec Tivoli Storage Manager” on page 759.
Create Clone CD Captures the Backup Exec installation program and your installation
settings, such as account information, additional options, and destination
directory. After the CD image has been created, it can be copied to a CD.
You can then use that CD to install Backup Exec on additional servers
using the same settings. For more information, see “Using a clone CD
image” on page 119.
Copy Server
Configurations
DLO (support for 5
users included with
Backup Exec)
Managed Media
Server
Enables you to copy server configurations, logon account information,
jobs, policies, and selection lists to remote media servers. This feature is
selected automatically if you enter a CASO license key.
Enables up to five desktop users to install the Desktop Agent for free
automated file protection.
Makes a stand-alone media server into a managed media server that is
controlled by the central administration server. You cannot select this
feature if you entered a CASO license key.
78 Administrator’s Guide

Chapter 2, Installing Backup Exec
System requirements
All other options and agents require the purchase of additional licenses. Installing an
Evaluation version enables many options that must be purchased separately and are not
included as part of Backup Exec.
System requirements
The following are the minimum system requirements for running this version of Backup
Exec:
Minimum System Requirements
Item Requirements
Operating system You can install and run Backup Exec on the following operating systems:
Additional
application support
◆ Microsoft Windows 2000 Server (with Service Pack 4 and Update
Rollup 1 for Service Pack 4)
◆ Microsoft Windows Server 2003
◆ Microsoft Windows Server 2003 x64 Editions
◆ Microsoft Windows Server 2003 R2 Editions
◆ Microsoft Windows Storage Server 2003 (with Service Pack 1)
◆ Microsoft Windows Storage Server 2005
◆ Microsoft Windows XP (with Service Pack 2)
◆ Microsoft Windows XP Professional x64 Edition
◆ Microsoft Windows Small Business Server 2000 (with Service Pack 4)
◆ Microsoft Windows Small Business Server 2003 (with Service Pack 1)
◆ Microsoft Windows Small Business Server 2005
You can use Backup Exec with the following applications:
◆ Microsoft Windows Microsoft Management (MOM) 2005
◆ Microsoft Windows Data Protection Manager
Internet browser Internet Explorer 6.0 or later. Service Pack 1 is required for SQL Server
2005 Express.
Processor Intel Pentium, Xeon, AMD, or compatible.
79

System requirements
Minimum System Requirements
Item Requirements
Memory Required: 256 MB RAM
Recommended: 512 MB RAM (or more for better performance)
Note RAM requirements may vary depending on the operations
performed, the options installed, and the specific computer
configuration.
For the Central Admin Server Option: 512 MB RAM required, 1 GB
recommended.
Virtual Memory Recommendations: 20 MB above the Windows
recommended size for total paging file size (total for all disk volumes).
Installation disk
space
696 MB (Typical installation)
805 MB (Includes all options)
Note Disk space requirements may vary depending on the operations
performed, the options installed, and the specific system
configuration. Backup Exec database and catalogs require additional
space.
Other Hardware ◆ Network interface card or a virtual network adapter card.
◆ CD-ROM drive.
◆ (Recommended) A mouse.
◆ (Optional for pager notification) Modem supported by Microsoft
Windows.
◆ (Optional for printer notification) Printer supported by Microsoft
Windows.
Storage Hardware 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. For a complete
list of supported devices, refer to the Backup Exec hardware compatibility
list:
http://support.veritas.com/menu_ddproduct_bewnt_view_cl
.htm
Support for a single robotic library drive is available when you purchase
Backup Exec. To enable support for additional robotic library drives, you
must purchase the Backup Exec Library Expansion Option.
80 Administrator’s Guide

Installing Backup Exec to a local computer
Chapter 2, Installing Backup Exec
Installing Backup Exec to a local computer
The Backup Exec CD includes an installation program that guides you through the
installation process.
If you are upgrading from a previous version of Backup Exec, see “Upgrading from
previous versions of Backup Exec” on page 129.
If you want to install Backup Exec to a non-English version of Windows, you must
download the SQL Express SP1 setup file from the Microsoft Web site before you install
Backup Exec if all of the following are true:
■ You want to use a local Backup Exec SQL Express instance.
■ You have non-English SQL Server instances on the computer on which you want to
install Backup Exec.
In addition, if you upgrade from a previous version of Backup Exec that uses a
non-English version of Windows, you must download the SQL Express SP1 setup file
from the Microsoft Web site.
Note If you install Backup Exec through Terminal Services and the installation media is
on a shared drive (CD-ROM or network share), you must install it using a UNC
path. Installation via mapped drives is not supported in this situation.
To install Backup Exec to a local computer
1. From the installation CD browser, click Installation, and then click Start the
Backup Exec Installation.
2. On the Welcome panel, click Next.
3. Click I accept the terms of the license agreement, and then click Next.
4. Check Local Install, and then click Install Backup Exec software and options.
5. Click Next
For first-time installations and upgrade installations, the Backup Exec Environment
Check runs automatically after you click Next.
6. Review the results of the Environment Check.
7. Do one of the following:
■ If the Environment Check does not reveal any issues that may prevent a
successful installation of Backup Exec, click Next.
81

Installing Backup Exec to a local computer
■ If the Environment Check reveals issues that may prevent a successful
installation of Backup Exec, click Cancel to exit the wizard. Correct the issues
before you attempt to install Backup Exec again.
8. Do one of the following:
If you have serial
numbers for Backup Exec
and its options
If you have license keys
for Backup Exec and its
options
◆ Go to https://licensing.symantec.com to activate the product.
After you activate the product, Symantec sends license keys to
you. License keys are required to install Backup Exec and its
options. You can access the Web site from any computer that
has Internet access.
◆ When you receive your license keys, go to step 9
9. Select one of the following methods to enter license keys:.
To enter license keys
manually
To import license
keys from a file
To install an
evaluation version
Go to step 9.
◆ Type a license key into the license key field.
◆ Click Add.
◆ Repeat for each license key for each option or agent that you want
to install.
◆ Click Import.
◆ Select the besernum.xml file.
◆ Leave the license key field blank.
◆ Proceed to step 9.
10. Click Next.
The license keys that you entered are saved to the besernum.xml file, which is
located in the Windows or WINNT directory.
11. Select any additional features to install.
For a description of the standard features that are available for installation with
Backup Exec, see “About Backup Exec’s standard features” on page 78.
All features that you do not select have a red X in the feature icon. To enable any of
these options, click the X, and then click This feature will be installed on
hard drive. If the feature icon is shaded, the option is not
available for change.
82 Administrator’s Guide

12. Do one of the following:
To change the directory
where the Backup Exec
files are installed
To accept the default
directory (recommended)
Chapter 2, Installing Backup Exec
Installing Backup Exec to a local computer
Symantec recommends that you do not select a mount point as the destination
directory because if you delete the mount point, Backup Exec is uninstalled.
13. Click Next.
14. Provide a user name, password, and domain for an Administrator account that the
Backup Exec system services can use, and then click Next.
See “About the Backup Exec services account” on page 74 for more information.
15. On the Symantec Backup Exec Database panel, do one of the following to select a
location to store the Backup Exec database:
To create a local Backup
Exec SQL Express
instance
To use an existing SQL
Server 2000 or SQL
Server 2005 instance
During the installation process, Backup Exec stops and starts the SQL Server
instance that you select several times. This might affect other applications that use
the SQL Server instance.
16. Click Next.
Click Change to select a new directory.
Proceed to step 12.
◆ Click Create a local Backup Exec SQL Express instance to
store the database on.
◆ To change the location of the Backup Exec SQL Express
instance, click Browse.
◆ Select the location, and then click OK.
◆ Click Use an existing SQL Server 2000 (SP3a or later) or SQL
Server 2005 instance on the network to store the database
on.
◆ Select the instance.
Note 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.
83

Installing Backup Exec to a local computer
Backup Exec attempts to connect to the instance.
17. If the Select path to SQL Express setup file panel appears, perform the following
steps to identify the location of the SQL Express SP1 setup file:
■ Click Browse.
■ Navigate to the location where you downloaded the SQL Express SP1 setup file.
■ Click OK.
■ Click Next.
18. If prompted, select how the Symantec Device Driver Installer should install device
drivers for the tape storage devices that are connected to the server, and then click
Next.
It is recommended that you select Use Symantec device drivers for all tape devices.
19. If you are prompted, enter information or choose settings for additional options that
you want to install. Click Next after each selection.
20. Read the Backup Exec installation review, and then click Install.
The installation process takes several minutes to complete. During the process, the
progress bar may not move for several minutes.
21. When the installation is complete, you can view the readme, create a shortcut to
Backup Exec on the desktop, and restart the computer.
22. Click Finish to close the installation wizard.
23. If Restart System appears, restart the computer in order for the configuration to
take effect.
An installation job log named bkupinst.htm is created in the Application Data
folder on the computer where Backup Exec is installed. This file lists any errors that
may have occurred during installation. The last line of the log indicates if the
installation was successful and if you must restart the computer.
After installing Backup Exec on the media server, Backup Exec Workstation Agent
software can be installed and configured on remote workstations on the network.
Related Topics:
“Getting Started” on page 131
84 Administrator’s Guide

Chapter 2, Installing Backup Exec
Installing Backup Exec options to the local computer
Installing Backup Exec options to the local computer
You can install additional options, such as the Library Expansion Option, when you
install Backup Exec by following the procedures described in “Installing Backup Exec to a
local computer” on page 81. However, if you have already installed Backup Exec and want
to install additional options, you should first review the documentation for that option to
ensure that you have met all minimum requirements.
If you have installed the Evaluation version of Backup Exec or have installed the Not For
Resale (NFR) edition, you can install evaluation versions of the additional options.
Note If you install Backup Exec through Terminal Services and the installation media is
on a shared drive (CD-ROM or network share) you must install using a UNC path.
Installation via mapped drives is not supported.
The Backup Exec services are stopped while the additional options are installed. If any
active jobs are running, you are prompted to stop them, or to wait for the jobs to finish.
Note If the Central Admin Server Option is installed, and you want to install additional
options on a managed media server, you can pause the managed media server to
prevent the central administration server from delegating jobs to it. When the
installation is complete, un-pause, or resume, the managed media server.
For more information see “Pausing and resuming a managed media server” on
page 836.
To install Backup Exec options to the local computer
1. Start Backup Exec for Windows Servers or verify that it is running.
2. On the Tools menu, click License Keys and Installation.
3. On the Welcome panel, click Next.
4. Verify that Local Install and Additional Options are selected, and then click Next.
5. Select one of the following methods to enter license keys:
To manually enter
license keys
◆ Type a license key into the license key field.
◆ Click Add.
◆ Repeat for each license key for each option or agent that you want
to install.
85

Installing Backup Exec options to the local computer
To import license
keys from a file
To install an
evaluation version
6. Click Next.
7. Verify that the additional options are selected for installation, and then click Next.
8. If you are prompted, enter information or choose settings for additional options that
you want to install. Click Next after each selection.
9. Read the Backup Exec installation review, and then click Install.
The Backup Exec services are stopped while the additional options are installed. If
any active jobs are running, you are prompted to stop them, or to wait for the jobs to
finish.
When the installation is complete, the services are restarted.
10. Click Finish.
◆ Click Import.
◆ Select the besernum.xml file.
◆ Leave the license key field blank.
◆ Proceed to step 6.
Related Topics:
“Installing Backup Exec to remote computers” on page 87
“Installing Backup Exec options to remote computers” on page 92
86 Administrator’s Guide

Installing Backup Exec to remote computers
Chapter 2, Installing Backup Exec
Installing Backup Exec to remote computers
If you are installing Backup Exec through Terminal Services and the installation media
is on a shared drive (CD-ROM or network share) you must install using a UNC path.
Installation via mapped drives is not supported.
You can install Backup Exec to as many as five remote computers concurrently.
Note You can also use Microsoft’s Add or Remove Programs utility to install Backup
Exec to a remote computer. See your Microsoft documentation for more
information.
If the remote computer uses Windows XP SP2 or Windows Server 2003 SP1, you should
enable the following ports to enable file and print sharing across the firewall:
■ 135 (RPC)
■ 445 (TCP)
■ 103X (mostly 1037)
■ 441 (RPC)
To install Backup Exec to a remote computer
1. Do one of the following:
To install Backup
Exec for the first
time
To install Backup
Exec to a remote
computer after you
have already
installed it on the
local computer
2. Check Remote Install. If you do not need to install Backup Exec to the local
computer, uncheck Local Install.
3. Click Next.
◆ From the installation CD browser, select the option to install
Symantec Backup Exec.
◆ Click Next.
◆ Click I accept the terms of the license agreement.
◆ Click Next.
◆ On the Tools menu, click License Keys and Installation.
◆ Click Next.
87

Installing Backup Exec to remote computers
4. Right-click Backup Exec Servers, and then do one of the following:
To browse to the remote
computer on which you
want to install Backup
Exec
To add a remote
computer manually
5. On the Remote Computer Logon Credentials panel, complete the fields as follows:
6. Click OK.
◆ Click Add Remote Computer.
◆ Browse the list to select all of the remote computers that you
want to install an option to.
◆ Click Next.
◆ Click Add Remote Computer Manually.
◆ Type the domain and computer name or IP address.
◆ Click OK.
User Name Type the user name for an account that has administrative rights
on the remote computer.
Password Type the password for an account that has administrative rights
on the remote computer.
Domain Select the domain in which the remote computer is located.
Use this user name and
password when
attempting to connect to
additional computers
during the installation
Check Use this user name and password when attempting to
connect to additional computers during the installation to avoid
entering credentials separately for each remote computer that
you have selected.
7. On the Remote Installation Types panel, select one of the following options, and
then click Next:
Remote install with
licensed options
Select this option to enter license keys for the remote computers.
During the installation process, you are prompted for the license
keys for the remote computers.
If you select this option to install Backup Exec for Windows Servers
to a remote computer, then you are prompted to select a
destination folder.
You can accept the default destination folder on the remote
computer, or make changes.
After selecting this option, continue with step 8 on page 89.
88 Administrator’s Guide

Remote install using the
same install settings as
the local computer
Remote install from
clone file settings
8. Select one of the following methods to enter license keys:.
To manually enter
license keys
To import license
keys from a file
To install an
evaluation version
9. Verify that the additional options are selected for installation.
Chapter 2, Installing Backup Exec
Installing Backup Exec to remote computers
10. In the Destination Folder field, type the path to the folder on the remote computer to
which the Backup Exec media server files will be installed.
The default location is C:\Program Files\Symantec\Backup Exec
11. Click Next.
Select this option to install remotely using all of the installation
options that are installed on the local computer. When you use this
option, you cannot change any settings on the remote computer.
For example, if you have installed the Intelligent Disaster Recovery
option locally, this option is also installed remotely.
This option is available only when you select both local and remote
install options.
After selecting this option, continue with step 9 on page 89.
Select this option to install remotely using the clone file settings
that may be contained on a clone CD image or that could also be
contained in a previously created parameter file (see “Creating and
using installation parameter files” on page 118). When this option
is selected, you can browse to a parameter file.
After selecting this option, continue with step 9 on page 89.
◆ Type a license key into the license key field.
◆ Click Add.
◆ Repeat for each license key for each option or agent that you want
to install.
◆ Click Import.
◆ Select the besernum.xml file.
◆ Leave the license key field blank.
◆ Proceed to step 9.
89

Installing Backup Exec to remote computers
12. On the Remote Service Account Information panel, complete the options as follows:
User Name Type the user name for an Administrator account that the Backup
Exec services can use.
If the remote computer is in a domain, use a Domain
Administrators account or an equivalent account that is part of
the Domain Administrators group.
If the remote computer is in a workgroup, use an Administrators
account or an equivalent account that is part of the
Administrators group on the computer.
Password Type the password for an Administrator account that the Backup
Exec services can use.
Domain If the computer is in a domain, select the domain in which the
remote computer is located.
If the computer is in a workgroup, select the computer name.
13. Click Next.
14. On the Symantec Backup Exec Database panel, do one of the following to select a
location on which to store the Backup Exec database:
To create a local Backup
Exec SQL Express
instance
To use an existing SQL
Server 2000 or SQL
Server 2005 instance
◆ Click Create a local Backup Exec SQL Express instance to
store the database on.
◆ To change the location of the database, click Browse.
◆ Select the location, and then click OK.
Note 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.
When Backup Exec is installed into an existing instance, the
Cluster Configuration Wizard is not available.
◆ Click Use an existing SQL Server 2000 (SP3a or later) or SQL
Server 2005 instance on the network to store the database
on.
◆ Select the instance.
Backup Exec attempts to connect to the instance.
90 Administrator’s Guide

Chapter 2, Installing Backup Exec
Installing Backup Exec to remote computers
15. On the Symantec Tape Device Drivers panel, read the message, and then click Next
to continue with the installation. After Backup Exec is installed, you can install
device drivers for the tape storage devices. See step 24.
16. If you are prompted, enter information or choose settings for additional options
being installed. Click Next or OK after each selection.
17. Review the features to be installed, and then click Next.
All options that are not to be installed have an X in the feature icon. To enable any of
these options, click the icon to clear the X, and then follow the prompts to install it.
If the feature icon is shaded, the option is not available for change.
18. Read the Backup Exec installation review, and then click Install.
When Backup Exec is being installed to a remote computer, if the Microsoft Data
Access Components (MDAC) version on the remote computer needs to be updated to
the version that ships with Backup Exec (MDAC v2.8), you are prompted to restart
the remote computer. Go to step 19.
If the MDAC version does not need to be updated, continue with step 23.
For more information on the MDAC version that is installed with Backup Exec, see
“About Microsoft SQL Server 2005 Express Edition components installed with
Backup Exec” on page 76.
19. If the MDAC version on the remote computer must be updated, restart the remote
computer. Right-click the computer name, and then click Reboot Computer.
20. After the computer has restarted, right-click the computer name and select the
Retry Install option. Verify the credentials when prompted.
21. To restart the remote computer now, on the Remote Installation Status dialog box,
right-click the server name, and then click Reboot Computer. You can also wait, and
restart the remote computer after you exit the installation wizard.
The installation status column displays the message that the computer is rebooting.
22. When the installation status indicates that the reboot is 100% complete, right-click
the server name again, and click View Install Log or View Push Log.
An installation job log named bkupinst.htm is created in the Application Data
folder on the computer where Backup Exec is installed. This file lists any errors that
may have occurred during installation. The last line of the log indicates if the
installation was successful and if restarting the computer is required.
23. Click Next, and then click Finish to exit the wizard.
91

Installing Backup Exec options to remote computers
If you did not restart the remote computer, you may need to do it now in order for
the configuration to take effect.
24. (Optional) To install device drivers for the tape storage devices that are connected to
the server, see “Configuring storage devices by using the Device Configuration
Wizard” on page 171
Related Topics:
“About the Backup Exec services account” on page 74
Installing Backup Exec options to remote computers
You can install the following options to remote computers:
■ Remote Agent for Windows or NetWare Systems
■ Advanced Open File Option (AOFO)
■ Desktop and Laptop Option (DLO) Desktop Agent
These features are push-installed to remote computers from a media server. Push
installations save time by eliminating the need for local access at the target computer
for the installation to be successful. You can install Backup Exec to as many as five
remote computers concurrently.
There are special considerations that you should be familiar with before you install
Backup Exec options on remote computers. Review the following table:
Special considerations for installing Backup Exec options to remote computers
Item Consideration
AOFO Before you install the Advanced Open File Option to a remote computer,
enable the remote registry. Make sure that the logon account that is used
has permissions to modify remote server registries.
92 Administrator’s Guide

Remote Agent for
Windows Systems
Chapter 2, Installing Backup Exec
Installing Backup Exec options to remote computers
Special considerations for installing Backup Exec options to remote computers
Item Consideration
You cannot push-install the Backup Exec Remote Agent for Windows
Systems to a remote Windows XP Professional computer when the
operating system on the remote computer is in the ForceGuest
configuration and the remote computer is not in a domain. ForceGuest is
a configuration that limits incoming users to Guest-level access. Instead,
you must locally install the Remote Agent on the Windows XP computer
by using the installation CD, or over the network by following the
procedure in “Installing Backup Exec using the command line (silent
mode)” on page 111.
You can also turn off ForceGuest. At the remote computer, do the
following:
◆ Click Start > Settings > Control Panel > Tools > Folder Options.
◆ Click the View tab.
◆ Uncheck Use simple file sharing.
Terminal Services If you install Backup Exec agents and options through Terminal Services
and the installation media is on a shared drive (CD-ROM or network
share) you must install using a UNC path. Installation via mapped drives
is not supported.
Windows XP SP2 To push-install a Backup Exec option to a computer that runs Windows
XP SP2, you must enable the following ports to enable File and Printer
Sharing under the Windows Firewall exceptions list:
◆ 135 (RPC)
◆ 445 (TCP)
◆ 103X (mostly 1037)
◆ 441 (RPC)
For instructions on how to enable File and Printer Sharing, see the
Windows XP documentation.
During the installation process, Backup Exec sets the Remote Launch and
Remote Access security permissions for the Administrator’s group.
93

Installing Backup Exec options to remote computers
To install a Backup Exec option to a remote computer
1. Do one of the following:
To install Backup
Exec for the first
time
To install Backup
Exec to a remote
computer after you
have already
installed it on the
local computer
2. Do one of the following:
To install:
◆ Backup Exec Remote
Agent for Windows
Systems
◆ Advanced Open File
Option
◆ Desktop and Laptop
Options’s Desktop
Agent
To install the Backup
Exec Remote Agent for
NetWare Servers
◆ From the installation CD browser, select the option to install
Symantec Backup Exec.
◆ Click Next.
◆ Select I accept the terms of the license agreement.
◆ Click Next.
◆ Check Remote Install. Uncheck Local Install if you do not need to
install any Backup Exec options to the local computer.
◆ Click Next.
◆ On the Tools menu, click Install Remote Agents.
◆ Click Next.
Right-click Windows Remote Agents.
Right-click NetWare Remote Agents.
94 Administrator’s Guide

3. Do one of the following:
To browse to the remote
computer on which you
want to install Backup
Exec options
To add a remote
computer manually
Chapter 2, Installing Backup Exec
Installing Backup Exec options to remote computers
4. On the Remote Computer Logon Credentials panel, complete the options as follows:
5. Click OK.
◆ Click Add Remote Computer.
◆ Browse the list to select all of the remote computers that you
want to install an option to.
◆ Click Next.
◆ Click Add Remote Computer Manually.
◆ Type the name or IP address of the computer, and the domain.
The domain is not necessary for NetWare systems.
◆ Click OK.
User Name Type the user name for an account that has administrative rights
on the remote computer.
Password Type the password for an account that has administrative rights
on the remote computer.
Domain Select the domain in which the remote computer is located. This
option is not available for NetWare systems.
Use this user name and
password when
attempting to connect to
additional computers
during the installation
Check Use this user name and password when attempting to
connect to additional computers during the installation to avoid
entering credentials separately for each remote computer that
you have selected.
6. In the Features pane, click the selection box next to the option that you want to
install, and then select This feature will be installed on hard
drive.
All features that are not to be installed have an "X" displayed in the feature icon. To
enable any of these options, click the icon to clear the X, and then follow the
prompts to install it. If the feature icon is gray, the option is not available for
change.
95

Installing Backup Exec options to remote computers
7. Do one of the following:
If you are installing the
Remote Agent for
Windows or NetWare
Systems, or AOFO
8. When the Publish Remote Agent Information dialog box appears, select the
appropriate options as follows:
9. Click OK.
10. Click Next.
Go to step 8.
If you are installing DLO Go to step 11.
Enable the Remote
Agent to publish
information to the
media servers in the list
If you want this remote computer to display in the media server’s
backup selection list, verify that Enable the Remote Agent to
publish information to the media servers in the list is checked.
Names or IP addresses Type the name or IP address of a media server that will use an
alternate network to back up the computer on which the Remote
Agent is installed.
Add Click Add to add the media server on the displayed list.
Edit To change a media server name or IP address, select the media
server in the displayed list, and then click Edit.
Remove To delete a media server name or IP address from the list of media
servers to publish to, select the media server in the displayed list,
and then click Remove.
11. Read the installation review, and then click Install.
The Remote Installation Status dialog box appears, and selected options are
installed on the remote computer.
12. When the installation status indicates that the reboot is complete, right-click the
server name again, and click View Install Log or View Push Log.
13. When the installation is complete, click Next, and then click Finish. You may need
to restart the computer in order for the configuration to take effect.
96 Administrator’s Guide

Chapter 2, Installing Backup Exec
Installing the Remote Agent for Windows Systems
An installation job log named bkupinst.htm is created in the Application Data
folder on the computer where Backup Exec is installed. This file lists any errors that
may have occurred during installation. The last line of the log indicates if the
installation was successful and if restarting the computer is required.
Note If there are problems installing the Backup Exec Remote Agent using this method,
you can try to manually install the Remote Agent (see “Using a command prompt
to install the Remote Agent on a remote 32-bit computer” on page 105.)
Related Topics:
“Push-installing the Remote Agent and the AOFO using the command line” on page 103
Installing the Remote Agent for Windows Systems
You can install the Remote Agent for Windows Systems by using many methods,
depending on your environment.
Note You cannot push install the Remote Agent to Itanium-based computers. The
Remote Agent can only be installed locally on an Itanium-based computer or by
using a mapped drive.
Before you install the Remote Agent, you should review the special considerations in the
following topic:
“Special considerations for installing Backup Exec options to remote computers” on
page 92.
The methods for installing the Remote Agent and the Advanced Open File Option
(AOFO) are listed in the following table:
Methods for installing the Remote Agent
To use this method: Go to:
Install the Remote Agent from the
Backup Exec installation CD by taking
the CD to the remote computer and
running the Backup Exec installation
browser.
Push-install the Remote Agent and
the AOFO to one or more remote
computers from the media server.
“Installing Backup Exec options to the local computer” on
page 85
“Installing Backup Exec options to the local computer” on
page 85
97

Installing the Remote Agent for Windows Systems
Methods for installing the Remote Agent
To use this method: Go to:
Push-install the Remote Agent and
the AOFO to a remote computer that
is displayed in Backup Exec
Resources.
Use a Microsoft Active Directory
network to centrally manage the
installation of the Remote Agent and
the AOFO to computers in the
network.
Push-install the Remote Agent and
the AOFO to a remote computer by
using a command line install, also
known as silent install.
Install the Remote Agent and the
AOFO by typing a UNC path or
mapping a drive letter to the Backup
Exec media server.
Install the Remote Agent to a 32-bit
operating system through a
command prompt.
Install the Remote Agent and the
Advanced Open File Option (AOFO) to
an Itanium-based or x64-based
operating system by using command
script files.
“Installing the Remote Agent and the Advanced Open File
Option to a remote computer in the backup selections list”
on page 99
“Installing the Remote Agent and Advanced Open File
Option in an Active Directory network” on page 99
“Push-installing the Remote Agent and the AOFO using
the command line” on page 103
“Installing the Remote Agent to an Itanium-based or
x64-based operating system” on page 104
“Using a command prompt to install the Remote Agent on
a remote 32-bit computer” on page 105
“Using a command script to install the Remote Agent and
AOFO on an Itanium-based or x64-based operating
system” on page 107
98 Administrator’s Guide

Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections
Installing the Remote Agent and the Advanced Open File Option
to a remote computer in the backup selections list
As you are making backup selections, you can install the Remote Agent and the
Advanced Open File Option (AOFO) on computers that you want to back up.
To install the Backup Exec Remote Agent and the Advanced Open File Option to a remote
computer in the backup selections list
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the View by Resource tab, do one of the following:
If the remote computer
has been added to
Favorite Resources
If the remote computer
has not been added to
Favorite Resources
4. Right-click the computer that you want to install the Remote Agent and the AOFO
to, and then click Install Remote Agent/Advanced Open File Option.
5. On the Installation wizard, click Next.
6. Continue with step 4 on page 95.
Installing the Remote Agent and Advanced Open File Option in an
Active Directory network
You can centrally manage the installation of the Backup Exec Remote Agent for
Windows Systems and the Advanced Open File Option (AOFO) to computers in an Active
Directory network. You configure the installation once, and then use a Group Policy
Object to assign that installation to computers in an Organizational Unit. The options
are installed automatically whenever a computer in the Organizational Unit is started.
Note Review your organization’s deployment plans before you implement a rollout of
the Backup Exec Remote Agent and Advanced Open File Option to client
computers.
Chapter 2, Installing Backup Exec
◆ Expand Favorite Resources.
◆ Expand Windows Systems.
◆ Expand Domains.
◆ Expand Microsoft Windows Network.
◆ Expand the appropriate domain.
99

Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections
You should also review your Group Policy Desktop Management and Active
Directory documentation.
First, create a transform for the Remote Agent and/or AOFO. A transform contains
changes that you want to make to the Remote Agent’s Windows Installer package when
a computer starts, such as installation path, which computers to publish to, and whether
to install AOFO. You must create separate transforms for 32-bit computers and 64-bit
computers.
Then, create a distribution point (share) that contains the source file of the Remote
Agent that you want to install. You must copy the transform that you create, and the
Backup Exec RAWS32 or RAWS64 directory, to the distribution point.
Finally, configure a Group Policy Object to assign the transform and the RAWS32 or
RAWS64 directory in the distribution point to computers in an Active Directory
Organizational Unit. The software is installed automatically when the computers in the
Organizational Unit are started.
Requirements to create a transform are:
■ The computer on which you want to create the transform must have Microsoft
Windows 2000 or Windows Server 2003.
■ The computers on which you want to install the Remote Agent must be running MSI
3.1.
■ Only assignment to computers is supported. Assignment to users is not supported.
■ Create separate transforms for 32-bit and 64-bit computers, which should not be in
the same Organizational Unit. Information in the MSI file and in the transform are
specific to each platform.
To create the transform
1. Do one of the following:
■ From the Backup Exec CD browser, click Installation, and then click Start the
Backup Exec Remote Agent Installation.
■ From a media server on which Backup Exec is installed, go to \Program
Files\Symantec\Backup Exec\Agents\RAWS32, and double-click
Setup.exe.
2. On the Welcome panel, click Next.
3. On the Install Type panel, click Create a Transform to use Active Directory to
install the Remote Agent, and then click Next.
100 Administrator’s Guide

Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections
4. Select the options that you want to include in the transform, and then click Next.
The configuration that you specify in the transform becomes the default setting for
a client computer in the Active Directory network when it performs Setup.
5. Enter the path where the Remote Agent will be installed on client computers, and
then click Next.
To change the default path, click Change.
The path should not be a removable drive or a network drive.
6. Enter the media server name or IP address of all of the media servers that you want
the Remote Agent to publish to after the transform has been applied, and then click
Next.
The computer that the Remote Agent is installed on is displayed in the media
server’s backup selection tree under the Favorite Resources node.
7. Enter a file name and a path where the transform will be created, and then click
Next.
Use a meaningful file name for the transform. For example, the name could include
the names of the options in the transform and the platform you plan to apply the
transform to, such as RemoteAgentDefaultPathNoPublishing.
8. To create the transform, click Create.
9. After the transform is created, continue with the next procedure to set up a
distribution point for the source files.
To create a software distribution point (share)
1. Create a shared folder, and then set permissions so that client computers that will
run the installation have access to the shared folder.
2. Copy the RAWS32 or RAWS64 directory from \Program
Files\Symantec\Backup Exec\Agents\RAWS32 or \RAWS64 on the Backup
Exec installation CD to the shared folder.
3. Copy the transform from the path where it was created to the RAWS32 or RAWS64
directory on the shared folder.
4. Continue with the next procedure to configure a Group Policy Object to deploy the
source files.
Chapter 2, Installing Backup Exec
101

Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections
To configure a Group Policy Object to deploy the software
1. From the Active Directory snap-in that manages users and groups, click Properties,
and create a new Group Policy Object or edit an existing one.
Refer to your Microsoft Windows documentation for information on creating a
Group Policy Object.
2. Under Computer Configuration, expand Software Settings.
3. Right-click Software Installation, click New, and then click Package.
4. On the File Open dialog box, browse to the software distribution point by using the
Universal Naming Convention (UNC) name, for example, \\server name\share name,
select the package file, and then click Open.
5. Select the package file Symantec Backup Exec Remote Agent for Windows
Systems.msi, and then click Open.
6. When prompted, apply the Advanced Option.
7. After Active Directory checks the msi package, click the General Properties tab, and
make sure the correct versions of the options are being installed.
8. Click the Deployment tab, and set up the configuration for your environment.
Make sure the option Make this 32-bit x86 application available to WIN64 machines
is not selected.
If you want the Remote Agent to be uninstalled if the computer is removed from the
Organization Unit, select the option Uninstall this application when it falls out of
the scope of management.
9. Click the Modifications tab, click Add, browse to the share, and select the transform
that you created.
10. Select Open, and make any other changes necessary, and then click OK.
11. Close all of the dialog boxes.
When a computer in the Organizational Unit that you specified is started, the
transform is processed and the options that you specified are installed.
View the installation log that is created on the destination computers to verify the
installation of the Remote Agent and/or the AOFO.
102 Administrator’s Guide

Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections
Push-installing the Remote Agent and the AOFO using the
command line
You can use silent mode installation, also known as command line installation, to
push-install the Backup Exec Remote Agent for Windows Systems and the Advanced
Open File Option (AOFO) to one or more remote computers. You can also push-install
the Remote Agent and the AOFO to more than one remote computer at a time by
creating a command file that reads the remote computer names from a .txt file.
To push-install the Remote Agent and the AOFO using the command line
1. Open a Windows command prompt.
2. Change to the drive containing the Backup Exec CD.
3. Change directories to \WINNT\INSTALL\BE.
4. To use a command file to read a list of remote computers to install to, go to step 6;
otherwise, continue with step 5.
5. Type one of the following:
Chapter 2, Installing Backup Exec
■ To install the Remote Agent, type:
SETUP /PUSHRAWS: /USER: /DOM:domain /PASS:password
/SVR: -S
■ To install the Advanced Open File Option, type:
SETUP /PUSHRAWS: /USER: /DOM:domain /PASS:password
/SVR: /AOFO: -boot -S
For the switch /SVR:, type the name of the remote computer that you want to
install to.
If you use the command line switches without the -S switch, the Backup Exec
installation program launches with the command line parameters as defaults for the
installation options. For example, if -S had been left in the above example, the
Backup Exec installation program launches with the user name, domain, and
password appearing on the installation dialog boxes.
6. (Optional) To install the Remote Agent or the AOFO using a command file that reads
server names from a .txt file, use the following sample script, substituting the
correct values for the variables:
for /f %%I in do call :sub1 %%I
goto :eof
103

Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections
:sub1
Echo Pushing to %1
call ..\BE\setup.exe /PUSHRAWS: /DOM:DOMAIN
/USER:administrator /PASS:password /SVR:%1 -S
if "%errorlevel%" == "0" goto :good
echo %1 failed with error %errorlevel%
goto :eof
:good
echo %1 completed successful
goto :eof
7. Press Enter.
Backup Exec creates an installation log in C:\Documents and Settings\All
Users\Application Data\Symantec\Backup Exec\Logs\bkupinst.htm.
This file lists any errors that may have occurred during installation, and is the only
source of feedback when you run setup.exe. The last line of the log indicates if the
installation was successful and if you must restart the computer.
Installing the Remote Agent to an Itanium-based or x64-based
operating system
The installation program for the Remote Agent is separate from the Backup Exec
installation program. In addition, the installation procedure for a Remote Agent to an
Itanium-based or x64-based operating system differs from the installation procedure for
the Remote Agent to a 32-bit computer. The installation of the Remote Agent to a 32-bit
computer Remote Agent can be a local- or push-install to a remote computer. You can
install the Remote Agent locally on an Itanium-based computer or by using a mapped
drive.
A Remote Agent license key is not required during the installation. However, you must
enter a Remote Agent license key on the media server.
After you install the Remote Agent, use the Windows Add/Remove Programs feature to
uninstall the option.
104 Administrator’s Guide

Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections
To install the Remote Agent to an Itanium-based or x64-based operating system
1. On the remote computer, type a UNC path, or map a drive letter to the Backup Exec
media server using one of the following paths:.
To an x64-based
operating system
To an Itanium-based
operating system
2. Double-click setup.exe, and then click Next.
3. Do one of the following:
To install the Remote
Agent and the Advanced
Open File Option
To install only the
Remote Agent
4. Click Install.
Backup Exec creates an installation log in C:\Documents and Settings\All
Users\Application Data\Symantec\Backup Exec\Logs\bkupinst.htm.
Using a command prompt to install the Remote Agent on a
remote 32-bit computer
To use a command prompt to install the Remote Agent on a remote computer
1. At a remote computer, map a drive letter to the Backup Exec media server RAWS32
directory using the following path:
\Program Files\Symantec\Backup Exec\Agents\RAWS32
2. Open a command prompt and type the drive letter that you mapped in step 1.
Chapter 2, Installing Backup Exec
\Program Files\Symantec\Backup
Exec\Agents\RAWSX64
\Program Files\Symantec\Backup
Exec\Agents\RAWSIA64
Click Complete.
◆ Click Custom.
◆ Select the Remote Agent.
◆ Click Next.
105

Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections
3. Do one of the following:
To install the Remote
Agent without publishing
enabled
To install the Remote
Agent with publishing
enabled
Run the following command:
setup.exe /RAWS32: -s -boot
Run the following command:
setup.exe /RAWS32: -s /ADVRT:
The Remote Agent is installed on the remote computer in the following directory:
\Program Files\Symantec\Backup Exec\RAWS32
The Remote Agent installation log file is installed by default in C:\Documents and
Settings\All Users\Application Data\Symantec\Backup
Exec\Logs\bkupinst.htm.
Using a command prompt to uninstall the Remote Agent from a
remote 32-bit computer
To use a command prompt to uninstall the Remote Agent from a remote 32-bit computer
1. At the remote computer, map a drive letter to the Backup Exec media server
RAWS32 directory using the following path:
\Program Files\Symantec\Backup Exec\Agents\RAWS32
2. Open a command prompt, and then type the drive letter that you mapped in step 1.
3. Run the following command: setup.exe /RAWS32: -s -u
The -s parameter is used to run the operation in silent mode, without the benefit of
a user interface. The -u parameter specifies an uninstall operation.
The Remote Agent is uninstalled from the remote computer.
Related Topics:
“Publishing the remote Windows computer to media servers” on page 919
106 Administrator’s Guide

Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections
Using a command script to install the Remote Agent and AOFO on
an Itanium-based or x64-based operating system
You can use command script files to install the Remote Agent and the Advanced Open
File Option (AOFO) on a Itanium-based or x64-based operating system. The command
script files are included in the Remote Agent installation directory.
The command script file setupaa64 installs the Remote Agent. The command script file
setupaofo64 installs the Remote Agent and the AOFO.
To use a command script to install the Remote Agent and AOFO to an Itanium-based or
x64-based operating system
1. Map a drive letter to the Backup Exec media server using one of the following paths:
To an x64-based
operating system
To an Itanium-based
operating system
Chapter 2, Installing Backup Exec
Scripts do not support UNC paths.
2. Do one of the following:
■ To install the Remote Agent, double-click setupaa64.
■ To install the Advanced Open File Option, double-click setupaofo64.
The command script installs the option automatically on the remote server in one of
the following directories:
On an x64-based
operating system
On an Itanium-based
operating system
\Program Files\Symantec\Backup
Exec\Agents\RAWSX64
\Program Files\Symantec\Backup
Exec\Agents\RAWSIA64
\Program Files\Symantec\Backup
Exec\Agents\RAWSX64
\Program Files\Symantec\Backup
Exec\Agents\RAWSIA64
3. If you installed the Advanced Open File Option, you must restart the remote
computer.
Backup Exec creates an installation log in C:\Documents and Settings\All
Users\Application Data\Symantec\Backup Exec\Logs\bkupinst.htm.
107

Installing the Backup Exec Remote Administrator
Using a command script to uninstall the Remote Agent and AOFO
on an Itanium-based or x64-based operating system
One command script file, Uninstallaaofo64, is available to uninstall both the Remote
Agent and the AOFO. The uninstall command script removes both options together. You
cannot remove the options separately using the command script.
To use a command script to uninstall the Remote Agent and Advanced Open File Option to
an Itanium-based or x64-based operating system
1. Map a drive letter to the Backup Exec media server using one of the following paths:
To an x64-based
operating system
To an Itanium-based
operating system
2. Double-click Uninstallaaofo64.
Both the Remote Agent and the Advanced Open File Option are removed from the
computer.
3. Restart the remote computer.
\Program Files\Symantec\Backup
Exec\Agents\RAWSX64
\Program Files\Symantec\Backup
Exec\Agents\RAWSIA64
Installing the Backup Exec Remote Administrator
The Backup Exec Remote Administrator allows you to administer the media server from
a remote Windows server or workstation.
You cannot manage a Backup Exec 10.x server using an 11d version of the Remote
Administrator. To remotely administrate both Backup Exec 10.x and 11d media servers,
install the Remote Administrator for both versions on the same computer but in
different directories.
To support the Remote Administrator, the media server requires that the Backup Exec
system services must be running.
Note The Remote Administrator and the media server to which it is connecting must be
the same version.
108 Administrator’s Guide

To install the Backup Exec Remote Administrator
Chapter 2, Installing Backup Exec
Installing the Backup Exec Remote Administrator
1. From the installation CD browser, select the option to install Symantec Backup Exec.
2. Click Next to continue with the installation.
3. Select I accept the terms of the license agreement, and then click Next.
4. To install the Administration Console as a Remote Administrator, select Install
Remote Administration Console only, and then click Next.
5. Click Next to install the Backup Exec program files in the default directory, or click
Change to select another directory for the installation, and then click Next.
6. Click Install.
7. Click Finish.
The Remote Administrator is installed. You can begin using Backup Exec. For more
information, see “Getting Started” on page 131.
To run the Remote Administrator
1. Click Start.
2. Point to Programs, and then click Symantec Backup Exec for Windows Servers.
If you are connecting to a remote administration console from a media server, from
the Network menu, click Connect to Local Media Server to break the connection.
Click Connect to Media Server to connect to another media server.
3. Select the appropriate options as follows:
Server Select the name of the media server or type the name of the
server if you are running the Remote Administrator from a
media server. The media server should appear in the list if the
Backup Exec naming services are running on both machines.
Each Windows 2000 server in the domain that has Backup Exec
installed will automatically appear in the list box.
109

Installing the Backup Exec Remote Administrator
Low speed connection
(RAS)
Select this option to minimize the amount of information
initially retrieved from the media server to which you are
connecting. When this option is selected, views such as the
device and media views will not automatically be expanded when
the Administration Console is loaded. This reduces the time
required to connect to the remote media server. Information for
each view is updated when the view is selected.
This option is useful if you are connecting to the media server
over a modem line.
User name Type an administrator user name for the server to which you are
connecting.
On Windows Server 2003 and Windows XP, you cannot log on to
the remote administration console with a user name that has a
blank password, unless you set Windows to allow blank
passwords. The error message "Logon failure: user account
restriction" displays. For more information, see your Windows
documentation.
Password Type the password.
Domain From the drop-down list, select the domain to which the user
belongs, or type the appropriate domain name if it does not
appear in the list.
Services Click this to access the Backup Exec Services Manager to stop
and start services or to set the logon credentials used to run the
services.
The status of the local services appear at the bottom of this dialog box. If you try to
connect to a server and the connection fails, this dialog box displays the services
status for the server you attempted to connect to.
4. Click OK.
The Administration Console connects to the services running on the media server.
You should now be able to operate the media server as though you were running the
Administration Console from there.
You may be prompted for a user name and password to browse some network shares
even if you are logged into the Remote Administrator computer under an account
that is valid for those shares. Provide a domain-qualified user name and password
when prompted (for example, domain1\howard).
For workgroup accounts, when logging in between different workgroups, you can
provide only a user ID when prompted, and leave the workgroup line blank.
110 Administrator’s Guide

Chapter 2, Installing Backup Exec
Installing Backup Exec using the command line (silent mode)
Installing Backup Exec using the command line (silent mode)
Installing Backup Exec using the command line is referred to as Silent Mode Installation.
This method of installation uses the setup.exe program on the Backup Exec CD, a series
of command switches, and the -S switch.
Requirements for Command Line Installation include:
■ Backup Exec installation CD.
■ Administrator privileges on the computer where you want to install, configure, or
uninstall Backup Exec.
To install Backup Exec using the command line (silent mode)
1. Open a Windows command prompt.
2. Change to the drive containing the Backup Exec CD.
3. Change directories to \WINNT\INSTALL\BE.
4. Type setup /TS: and the appropriate switches. For example:
setup /TS: /USER: /DOM:domain /PASS:password /SNO:license
key -S
For descriptions of the switches, see “Command line switches for Backup Exec silent
mode installation” on page 112.
If you use the command line switches without the -S switch, the Backup Exec
installation program launches with the command line parameters as defaults for the
installation options. For example, if -S had been left in the above example, the
Backup Exec installation program launches with the user name, domain, password,
and license key appearing on the installation dialog boxes.
5. Press ENTER.
An installation job log named bkupinst.htm is created in the Application Data
folder on the computer where Backup Exec is installed. This file lists any errors that
may have occurred during installation, and is the only source of feedback when
running setup.exe. The last line of the log indicates if the installation was successful
and if restarting the computer is required.
111

Installing Backup Exec using the command line (silent mode)
Command line switches for Backup Exec silent mode installation
The command line switches used for silent mode installation of Backup Exec are
described in the following table. Note the following general rules for using these
switches:
■ Substitute values appropriate for your environment for values shown in italics; for
example substitute your password for password.
■ Enclose the value in quotation marks if it contains spaces, such as “Operations
Weekly Backup”.
Note Additional switches appearing in BOLD are required.
Command Line Switches for Silent Mode Installation of Backup Exec
Switch Additional Switches Description
/TS: Installs Backup Exec using the options
specified with the additional switches.
The /USER:"user" /DOM:"dm"
/PASS:"pw" is required.
/USER:"user"
/DOM:"dm"
/PASS:"pw"
Required. Specifies an existing user,
domain, and password for the Backup
Exec system service account. Silent
mode installation will not create a user.
Note When using /PASS:, if a quote is
needed as part of the password,
specify it as \". For example, if the
password is pass"word, type it as
/PASS:pass\"word. If the
characters \" are used as part of
the password, you must precede
each character with a \. For
example, if the password is
pass\"word, type it as
/PASS:pass\\\"word.
/DEST:"path" Specifies the path where Backup Exec
will be installed. Otherwise, the default
path Program
Files\Symantec\Backup Exec is
used.
/DOCS: Installs online documentation.
112 Administrator’s Guide

Chapter 2, Installing Backup Exec
Installing Backup Exec using the command line (silent mode)
Command Line Switches for Silent Mode Installation of Backup Exec (continued)
Switch Additional Switches Description
/NOINSTALL: Allows you to select all install options
without actually installing the Backup
Exec software. This option can be used in
conjunction with the /CPF: or /XML:
switches.
/SNO:license key Specifies one or more license keys to use
for installing Backup Exec and additional
options. License keys are not required to
install the Remote Administrator. You
may specify up to 99 license keys. If none
are specified, then an Evaluation copy of
Backup Exec is installed.
The following examples show how the
/SNO switch can be used:
/SNO:s1
/SNO:s1 s2 s3 s4
/SNO:s1 /SNO:s2 /SNO:s3 /SNO:s4
/TD:NEW or ALL /TD:NEW installs tape drivers only for
drives that do not have drivers loaded.
/TD:ALL installs tape drivers for all
drives.
Note To install the Symantec tape
drivers, the Windows driver
signing policy must be set to
Ignore. See your Microsoft
Windows documentation for
instructions on changing the
driver signing policy.
/CPF:"file name" Creates a file containing all of the
installation parameters provided. This
file is encrypted.
/XML:"file name" Creates an XML file containing all of the
installation parameters provided.
Note The XML file is not encrypted,
which exposes parameters such as
the password.
113

Installing Backup Exec using the command line (silent mode)
Command Line Switches for Silent Mode Installation of Backup Exec (continued)
Switch Additional Switches Description
/DBSERVER:
/DBINSTPATH:
Installs the Backup Exec database to the
specified SQL server.
Installs the default instance of SQL
Express in the specified folder.
/NOUPDATE: Skips the installation of Symantec
LiveUpdate.
/DISADVRT Installs the Remote Agent without
publishing it.
Note The following switches are designed for use with Not For Resale, Open Option, and
Evaluation versions of Backup Exec only.
/LOADER: Installs the Library Expansion Option.
/IDR: Installs the Intelligent Disaster Recovery
Option.
/R3: Installs the Backup Exec Agent for SAP
Applications (SAP Agent).
/AOFO: Installs the Advanced Open File Option.
/TSM:IP address:port Installs the IBM ADSM/TSM Option.
/SSO: Installs the SAN Shared Storage Option
with this server as the primary server.
/SSO:server name Installs the SAN Shared Storage Option
with this server as the secondary and the
as the primary.
/SHAREPT: Installs the Agent for Microsoft
SharePoint Portal Server.
/EXCH: Installs the Agent for Microsoft
Exchange Server.
/LOTUS: Installs the Agent for Lotus Domino.
/ORACLE: Installs the Agent for Oracle on Windows
Servers and/or the Linux/Unix Agent for
Oracle Server.
114 Administrator’s Guide

Chapter 2, Installing Backup Exec
Installing Backup Exec using the command line (silent mode)
Command Line Switches for Silent Mode Installation of Backup Exec (continued)
Switch Additional Switches Description
/SQL: Installs the Agent for Microsoft SQL
Server.
/NTA: Installs the Remote Agent for Windows
Systems.
/NWA: Installs the Remote Agent for NetWare
Servers.
/DLO: Installs the Backup Exec Desktop and
Laptop Option.
/DLO5: Installs the five-user version of the
Backup Exec Desktop and Laptop Option.
/ADBO: Installs the Advanced Disk-based Backup
Option.
/CASO: Installs the Central Admin Server
Option.
/MMS: Creates a managed media server for use
with the Central Admin Server Option.
/CASOPVLLOCAL: /CASOPVLLOCAL: indicates that
device and media data will be stored
locally on the managed media server.
Use this switch with /MMS:.
/CASOPVLLOCAL: indicates that
device and media data will be stored on
the central administration server. Use
this switch with /MMS:.
/RALUS: Installs the Remote Agent for Linux and
Unix Servers.
/ADR: Installs the Active Directory Recovery
Agent.
/DPM: Installs the Microsoft Data Protection
Manager Agent.
/NDMP: Installs the NDMP Option.
/DB2: Installs the Agent for DB2.
115

Installing Backup Exec using the command line (silent mode)
Command Line Switches for Silent Mode Installation of Backup Exec (continued)
Switch Additional Switches Description
Related Topics:
“Push-installing the Remote Agent and the AOFO using the command line” on page 103
Installing the Remote Administrator using the command line
You can also use Silent Mode Installation to install the Remote Administrator. Options
for the Remote Administrator are specified with the use of additional command
switches.
To install the Remote Administrator using the command line
1. Open a Windows command prompt.
/MAC: Installs the Remote Agent for Macintosh
Servers.
/CLONE: Installs the Clone CD option to the
default location, which is \clonecd.
/CLONE: Installs the Clone CD option to the
location that you specify.
/COPYCONFIG: Installs the Copy Server Configuration
option.
2. Change to the drive containing the Backup Exec CD.
3. Change directories to \WINNT\INSTALL\BE
4. Type setup /RA: and the appropriate switches. For example:
setup /RA: -s
The command line switches used for silent mode installation of the Remote
Administrator are described in the following table. Remember the following general
rules for using these switches:
■ Substitute values appropriate for your environment for values in italics; for
example, substitute your password for password.
116 Administrator’s Guide

Chapter 2, Installing Backup Exec
Installing Backup Exec using the command line (silent mode)
■ Enclose the value in quotation marks if it contains spaces, such as “Program
Files\Symantec\Backup Exec”.
Command Line Switches for Remote Administrator Silent Mode Installation
Switch Additional Switches Description
/RA: Installs Remote Administrator using the
options specified with the additional
switches.
Uninstalling Backup Exec using the command line
If Backup Exec is already installed, you can use the setup.exe program to uninstall
Backup Exec program files and Backup Exec data.
To uninstall Backup Exec using the command line
1. Open a Windows command prompt.
/DEST:"path" Specifies the path where Remote
Administrator will be installed.
Otherwise, the default path Program
Files\Symantec\Backup Exec is
used.
/DOCS: Installs online documentation.
/NOINSTALL: Allows you to select all install options
without actually installing the Backup
Exec software. This option can be used
with the /CPF: or /XML: switches.
/CPF:"file name" Creates a file containing all of the
installation parameters provided. This
file is encrypted.
/XML:"file name" Creates an XML file containing all of the
installation parameters provided.
Note The XML file is not encrypted,
which exposes parameters such as
the password.
2. Change to the drive containing the Backup Exec CD.
3. Change directories to \WINNT\INSTALL\BE.
117

Installing Backup Exec using the command line (silent mode)
4. To remove the Backup Exec program files but keep all of the Backup Exec data, type:
SETUP /UNINSTALL:
To remove the Backup Exec program files and the Backup Exec data, type:
SETUP /REMOVEALL:
Creating and using installation parameter files
If you use the command line switches without the -S switch, the Backup Exec
installation program launches with the command line parameters as defaults for the
installation options. For example, suppose you type:
SETUP /TS: /USER:user /DOM:domain /PASS:password /SNO:license
key
The Backup Exec installation program is launched. The screens that allow you to enter
the logon credentials and the license key will appear with the information you provided
on the command line.
You can also use the /CPF: and /XML: commands to create a parameter file that contains
all of the command line options you provided. This parameter file can then be used to
provide the options for installing either Backup Exec or the Remote Administrator.
To create installation parameter files
1. Open a Windows command prompt.
2. Change to the drive containing the Backup Exec CD.
3. Change directories to \WINNT\INSTALL\BE.
4. Type setup /TS: and the appropriate switches, including /CPF: and the full path
name of the parameter file. For example, type:
setup /TS: /USER:user /DOM:domain /PASS:password /SNO:license
key /CPF:"A:\file name" -S
Backup Exec will be installed on your server and a parameter file containing the user
name, domain, password, and license key will be saved to a floppy diskette. You can
use this parameter file to install to another computer.
To use installation parameter files
1. Open a Windows command prompt.
2. Change to the drive containing the Backup Exec CD.
118 Administrator’s Guide

3. Change directories to \WINNT\INSTALL\BE.
4. Type:
SETUP /PARAMS:"A:\file name" -S
Chapter 2, Installing Backup Exec
Using a clone CD image
5. If you want to overwrite a parameter, specify the new parameter. For example, to
change the password, type:
SETUP /PARAMS:"A:\file name" /PASS:new password -S
To create an XML file containing all parameters, use the /XML: switch. The XML file
is not encrypted, which exposes parameters such as the password.
Related Topics:
“Installing Backup Exec using the command line (silent mode)” on page 111
“Command line switches for Backup Exec silent mode installation” on page 112
Using a clone CD image
A clone CD image captures the Backup Exec installation program and your installation
settings, such as account information, additional options, and destination directory.
After the CD image has been created, it can be copied to a CD. You can then use that CD
to install Backup Exec on additional servers using the same settings.
The clone CD image is not removed from your system when Backup Exec is uninstalled.
Related Topics:
“Creating a clone CD image” on page 120
“Installing locally using a clone CD image” on page 120
“Installing to a remote system using a clone CD image” on page 121
119

Using a clone CD image
Creating a clone CD image
To create a clone CD image
1. Begin installing Backup Exec following the procedures described in “Installing
Backup Exec to a local computer” on page 81. You must use the Backup Exec
installation CD or a copy of the CD when creating the clone CD image for the first
time. A downloaded version of Backup Exec does not have the same directory layout
as the installation CD, and, therefore, cannot be used to create a clone CD image.
2. When the list of features being installed appears, select Create Clone CD.
3. Click Next and continue with the installation procedures.
4. When the Create Clone CD Image dialog box appears, ensure the directory listed is
the directory where you want the clone CD image file copied. If the location is not
correct, click Change and browse to select the correct location. The directory to
which the clone CD image file will be copied should be an empty directory.
5. Click Next and continue with the installation procedures.
If the Backup Exec installation CD is not in your CD drive, Backup Exec will prompt
you to specify the path where the CD image is located. If you have not yet created a
clone CD image, you must insert the Backup Exec installation CD or be able to access
this installation CD from the network.
Installing locally using a clone CD image
After a clone CD image has been created, it can be used to install the identical Backup
Exec installation parameters to another system.
To install locally using a clone CD image
❖ Insert the CD containing your clone CD image into the CD drive.
If autorun is not enabled on your system, run SETUP.CMD, which is in the root of
the installation CD directory.
Because the installation parameters, or options, have already been captured in the clone
CD image, you will not be prompted for these options.
120 Administrator’s Guide

Installing to a remote system using a clone CD image
To install to a remote system using a clone CD image
Chapter 2, Installing Backup Exec
Using a clone CD image
1. Begin the Backup Exec installation procedures as described in “Installing Backup
Exec to remote computers” on page 87.
2. Add the remote systems to which you are installing.
3. When the Remote Installation Types dialog box appears, select from one of the
following options:
Remote install with
licensed options
Remote install using the
same install settings as
the local computer
Remote install from
clone file settings
4. Follow the on-screen prompts.
Select this option if you want to enter license keys for the remote
systems. During the install, a dialog asking for the license keys for
the remote system appears.
Select this option if you want to install remotely using all of the
installation options installed on the local system. When this option
is used, you cannot change any settings on the remote system. For
example, if you have installed the Intelligent Disaster Recovery
option locally, this option will also be installed remotely.
Select this option if you want to install remotely using the clone
file settings that may be contained on a clone CD image or could
also be contained in a previously created parameter file (see
“Creating and using installation parameter files” on page 118).
When this option is selected, you will be able to browse to a
parameter file.
121

About the installation log
About the installation log
Backup Exec creates an installation log file, named Bkupinst.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. In addition, the text in the log file uses the following colors so you can identify
warnings and errors:
Installation log colors
This color Indicates
Black Normal operations
Orange Warning messages
Red Error messages
Bkupinst.htm is saved in:
\\Documents and Settings\All Users\Application
Data\Symantec\Backup Exec\Logs.
The Application Data folder is a hidden folder. If you do not see the Application Data
folder, refer to the Microsoft Windows documentation for instructions on how to display
hidden folders. Note that in some versions of Microsoft Windows, the All Users folder
has a different name. For example, All Users is named All Users.winnt in Microsoft
Windows 2000 Server.
Repairing Backup Exec
If you have missing or corrupted Backup Exec files or registry keys on the local media
server, run the Repair option. The program stops all Backup Exec services, reinstalls
corrupted files and registry keys, reinstalls tape devices (stand-alone drives and
libraries), and restarts the services. The database is not reinstalled.
Any changes made to Backup Exec program files and registry keys will be reset to the
original settings.
To repair Backup Exec
1. Close the Backup Exec application.
2. From the Windows Control Panel, double-click Add or Remove Programs.
122 Administrator’s Guide

Chapter 2, Installing Backup Exec
Starting and stopping Backup Exec services
3. At the Add or Remove Programs dialog box, select Symantec Backup Exec for
Windows Servers, and then click Change.
4. On the Welcome panel, click Next.
5. Select Local Install and Repair, and then click Next.
Make sure the option Remote Install is not selected.
6. Select Install.
7. Click Finish.
Starting and stopping Backup Exec services
To start or stop Backup Exec services
1. On the Tools menu, click Backup Exec Services.
2. Select the appropriate options as follows:
Server Type the name of a server you want to add to the list, and then click
Add. To import a list of servers, click Import List and select the file
containing the server list.
Start all services Click this to start all Backup Exec services for the selected server.
Stop all services Click this to stop all Backup Exec services for the selected server.
Restart all services Click this to stop all Backup Exec services and then restart the
services for the selected server.
Services credentials Click this to change service account information or to change
startup options.
Refresh Click this to refresh this dialog box.
Remove Servers Click this to remove a selected server or servers from the server
list.
123

Uninstalling Backup Exec
Uninstalling Backup Exec
Use Microsoft’s Add or Remove Programs option to remove Backup Exec from a
computer. For additional information on Add or Remove Programs, refer to your
Microsoft documentation.
Note When using the Shared Storage Option, you must uninstall Backup Exec from the
secondary servers before uninstalling from the primary server.
To uninstall Backup Exec
1. Close Backup Exec.
2. From the Windows Control Panel, double-click Add or Remove Programs.
3. At the Add or Remove Programs dialog box, select Symantec Backup Exec for
Windows Servers, and then click Remove.
4. When prompted to confirm the deletion of Backup Exec from your computer, click
Yes.
5. When prompted to remove all of the files associated with Backup Exec, click Yes;
click No to retain user-created data such as catalogs and job information.
If the uninstall program fails, click the View Installation Log File button for
additional information.
6. If prompted, reboot the computer after uninstalling Backup Exec.
Uninstalling Backup Exec also removes Symantec tape class drivers. If you reinstall
Backup Exec and want to use Symantec tape class drivers, you must reinstall them.
Related Topics:
“Push-installing the Remote Agent and the AOFO using the command line” on page 103
124 Administrator’s Guide

Chapter 2, Installing Backup Exec
Uninstalling Backup Exec options from the local media server
Uninstalling Backup Exec options from the local media server
The install wizard is used to uninstall Backup Exec options from the local media server.
To uninstall Backup Exec options from the local media server
1. From the Tools menu, click License Keys and Installation.
2. At the Welcome screen, click Next.
3. On the Backup Exec license keys dialog box, select the license key of the option that
you want to uninstall, and then click Remove.
4. On the Backup Exec Local Features dialog box, click the icon next to the option, and
select This feature will not be available, and then click Next.
An "X" will be displayed in the feature icon.
5. On the Installation Review dialog box, click Next, and then click Install to start the
process.
6. When the install wizard has completed, click Finish.
Corresponding files, registry keys, and configuration will be uninstalled.
About updating Backup Exec with LiveUpdate
Symantec LiveUpdate, which provides updates, upgrades, and new versions of Backup
Exec, is installed automatically with Backup Exec. If you enable the automatic update
option, you can configure LiveUpdate to poll the main Symantec Web server on a
scheduled interval.
In addition to scheduling LiveUpdate, you can also run it manually at any time. You can
access LiveUpdate from several locations in Backup Exec. However, you cannot access it
from the Windows Start menu.
Backup Exec installs version 3.0 of LiveUpdate. If a previous version of LiveUpdate is
detected on the computer, Backup Exec upgrades it to version 3.0.
Note To quickly view any hot fixes or service packs that are installed on the media
server, see “Viewing installed updates” on page 128.
LiveUpdate installs updates on the Backup Exec media server. You can then push-install
or manually copy those updates to Backup Exec Remote Agents.
125

About updating Backup Exec with LiveUpdate
If LiveUpdate installs any files, the Bkupinst.htm installation log file is updated with
information about those files.
You can use the LiveUpdate Administrator Utility with LiveUpdate. The LiveUpdate
Administrator Utility allows an administrator to modify LiveUpdate so 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. For more information,
see:
ftp://ftp.symantec.com/public/english_us_canada/liveupdate/luadmin
.pdf
Related Topics:
“Scheduling automatic updates using LiveUpdate” on page 126
“Running LiveUpdate manually” on page 128
Scheduling automatic updates using LiveUpdate
You can schedule LiveUpdate to check for updates:
■ Once on a specific date at a specific time
■ Every day at a specific time
■ Every week on a specific day of the week and at a specific time
■ Every month on a specific day of the month and at a specific time
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.
Backup Exec sends the following LiveUpdate alerts:
LiveUpdate alerts
Backup Exec sends this alert When
LiveUpdate Informational
Alert
An update is installed successfully.
126 Administrator’s Guide

LiveUpdate alerts
Backup Exec sends this alert When
To schedule automatic updates using LiveUpdate
1. On the Tools menu, click Options.
2. On the properties pane, under Settings, click LiveUpdate.
3. Complete the options as follows:
Chapter 2, Installing Backup Exec
About updating Backup Exec with LiveUpdate
LiveUpdate Warning Alert An update is installed successfully. However, you must restart the
computer.
LiveUpdate Error Alert An update fails to install.
Enable scheduled
automatic updates
Automatically download
and install all available
updates
Only notify me of
available updates
Check Enable scheduled automatic updates to schedule
automatic updates, and then choose the frequency of the updates.
Select this option if you want Backup Exec to download and install
all updates that are available without prompting you first.
Select this option if you want Backup Exec to alert you when
updates are available. Updates are not downloaded or installed.
This is the default option.
If you select this option, you need to run LiveUpdate manually to
download and install the available updates.
Once Select this option to enable Backup Exec to check for new updates
only on the date and time that you specify in the On and At fields.
Daily Select this option to enable Backup Exec to check for new updates
every day. In the At field, enter the time to check for new updates.
Weekly Select this option to enable Backup Exec to check for new updates
once a week. In the Every field, select the day of the week on
which to check for updates. In the At field, enter the time to check
for new updates.
Monthly Select this option to enable Backup Exec to check for new updates
once a month. In the Every field, select the day of the month on
which to check for updates. In the At field, enter the time to check
for new updates.
127

About updating Backup Exec with LiveUpdate
4. Click OK.
Running LiveUpdate manually
You can either set a schedule for LiveUpdate or run LiveUpdate manually at any time to
check for updates. You can configure LiveUpdate to run in either Interactive mode or
Express mode. Interactive mode gives you the flexibility to choose which Symantec
product updates you want to install. Express mode automatically installs all of the
updates for your Symantec products. For information about how to change the
LiveUpdate mode, see the LiveUpdate documentation.
To run LiveUpdate manually
1. On the Tools menu, click LiveUpdate.
2. Do one of the following:
If LiveUpdate is set for
Express mode
If LiveUpdate is set for
Interactive mode
Viewing installed updates
You can view hot fixes and service packs that are installed on a media server. You must
be logged on with administrator privileges.
If a hot fix is installed prior to a service pack, that hot fix no longer displays as installed
since the service pack contains the hot fix.
A hot fix that is offered after the service pack is released is displayed with the prior
service pack.
Service packs and hot fixes cannot be uninstalled.
To view installed updates
1. On the Help menu, click About Symantec Backup Exec for Windows Servers.
2. Click Installed Updates.
Click Start.
Click Next.
3. To install hot fixes and service packs, select Click here to run LiveUpdate.
128 Administrator’s Guide

Viewing license information
To view license information
Chapter 2, Installing Backup Exec
Viewing license information
1. On the Help menu, click About Symantec Backup Exec for Windows Servers.
2. Click License Information.
The License Information dialog box provides the following information:
Option Name of the available Backup Exec options.
Licensed Displays Yes if the option is licensed on the media server. Displays
No if the option is not licensed.
Installed Displays Yes if the option is installed on the media server. Displays
No if the option is not installed.
If the option is installed, it may still require some additional
configuration.
Upgrading from previous versions of Backup Exec
This version of Backup Exec for Windows Servers replaces any previous versions. No
separate migration or upgrade utility is necessary. Most settings and all catalogs and
data directories from previous versions of Backup Exec are kept (for example, when the
TSM option adds registry settings). At the end of the installation, the upgrade process is
summarized. Only Backup Exec version 9.x and later can be migrated to this release.
The new version of Backup Exec for Windows Servers (including the Evaluation version)
replaces any current installation. Separate installations of different versions cannot
exist on the same computer.
For information on how to migrate templates from Backup Exec version 9.0 and 9.1, see
“Migrating templates from previous versions of Backup Exec” on page 421.
Before you upgrade Backup Exec, do the following:
■ Delete job histories and catalogs that you no longer need to shorten the upgrade
window.
■ Run a database maintenance job.
129

Upgrading from previous versions of Backup Exec
To upgrade from previous versions of Backup Exec
1. Perform steps 1 through 5 in the topic “Installing Backup Exec to a local computer”
on page 81.
2. Enter license keys for Backup Exec, and for each Backup Exec option that you want to
install, and then click Next.
Read the Installation Review. To add additional license keys, click Back until the
Symantec Backup Exec license keys page appears. Enter the license keys, and then
click Next to continue.
The default location is C:\Program Files\Symantec\Backup Exec.
3. On the Back Up Existing Catalog and Data page, enter or browse to a directory to
which you want to back up all existing catalogs and data. The default location is:
C:\Program Files\Symantec\Backup Exec\Data
If you do not want to keep previous catalogs and data, click Do not back up previous
data and catalogs.
4. Click Next to continue.
An upgrade summary is displayed.
Upgrading Backup Exec options on remote computers
In order to upgrade options installed on remote computers, you must reinstall them. The
following options are push-installed, and will not be upgraded until they are reinstalled:
■ Backup Exec Remote Agent for Windows Systems. For more information, see
“Installing the Remote Agent for Windows Systems” on page 97.
■ Backup Exec NetWare Agent. For more information, see “About installing the Remote
Agent for NetWare Systems on a NetWare server” on page 924 and “Installing
Backup Exec options to remote computers” on page 92.
■ Backup Exec Advanced Open File Option. For more information, see “Installing the
Advanced Open File Option” on page 848.
To reinstall these options, repeat the installation steps for each option.
130 Administrator’s Guide

Getting Started
In Getting Started, you’ll find:
Chapter
■ A checklist to help you prepare your Backup Exec environment. Details on the
Getting Started page, Backup Exec Assistant, and other parts of the Backup Exec
Administration Console.
■ Details of default options set when Backup Exec is installed.
■ Descriptions of Backup Exec menus.
Before starting Backup Exec
For best results before starting Backup Exec, do the following:
❏ Make sure your storage devices are connected and configured properly.
❏ Decide if your backup will be to a tape device or a disk device. You can configure
both devices when you prepare your Backup Exec environment.
3
■ If you’re backing up to a tape device, verify that the device is supported. You can
install drivers for the devices when you configure your Backup Exec
environment.
■ If you’re backing up to a disk device using the Backup-to-Disk feature, decide
where you can create a backup folder. You should create it on a disk that won’t
be included in the backup jobs and that has enough free space to contain the
backup job. For more information, see “About backup-to-disk folders and files”
on page 218.
❏ Understand how Backup Exec provides overwrite protection for your media. For
more information, see “Media overwrite protection” on page 260.
131

Starting Backup Exec
❏ Understand the default media set and its infinite overwrite protection period. For
more information, see “About media in Backup Exec” on page 257.
❏ Learn about creating new media sets with weekly, monthly, or quarterly retention
periods. For more information, see “Default media set” on page 263.
❏ Decide the Windows credential you want your Backup Exec logon account to use
when browsing and making backup selections. You can use an existing account, or
create a new one. For more information, see “Creating a Backup Exec logon account”
on page 149.
❏ Decide the format that you want to display all reports, either HTML or Adobe
Portable Document Format (PDF). The default setting is HTML. For more
information, see “Setting default options for reports” on page 601.
Starting Backup Exec
❖ To start the Backup Exec Administration Console, click Start > All Programs >
Symantec Backup Exec for Windows Servers.
If you selected the option to add an icon to your desktop when you installed Backup
Exec, you can also double-click the icon to start Backup Exec.
Related Topics:
“Using the Administration Console” on page 133
“Using Backup Exec dialog boxes” on page 136
Using the Getting Started with Backup Exec page
The first time you run Backup Exec, the Getting Started with Backup Exec page appears.
The Getting Started with Backup Exec page provides a series of steps that you can follow
to configure environment settings in Backup Exec, including logon accounts, devices,
and media sets. If you have purchased and installed the Symantec Intelligent Disaster
Recovery Option you can configure it. Also, you can access the Backup Exec Assistant,
which has links to additional wizards, documentation, and technical support assistance
or you can create a backup job by using the Backup Wizard.
If you do not use the Getting Started with Backup Exec page, you can use the default
logon account and media set. The Backup Exec defaults are created during the
installation of Backup Exec. The default logon account credentials match the credentials
provided during the installation of Backup Exec. The default media set is Keep Data
Infinitely - Do Not Allow Overwrite and has an append and overwrite protection periods
set to Infinite. However, you cannot create a backup job until you configure a device.
132 Administrator’s Guide

To access the Getting Started with Backup Exec page
Chapter 3, Getting Started
❖ Click Help > Getting Started.
Using the Administration Console
Using the Administration Console
After you close the Getting Started with Backup Exec page, the Administration Console
appears. From the Administration Console, you can access all Backup Exec features.
Administration Console
Menu bar
Navigation bar
Task pane
Status bar
Columns
Selection pane Preview pane Results pane
133

Using the Administration Console
The main Administration Console screen includes the following components:
Getting Started page options
Item Description
Menu bar Backup Exec’s menu bar appears across the top of your screen. To
display a menu, click the menu name or use the keyboard shortcut.
You can launch Backup Exec operations by clicking options from a
menu. Some options may be unavailable until you select an item from
the console screen. For example, you cannot select Rename from the
Edit menu unless you have first selected an item to rename from either
the Devices view or the Media view.
Navigation bar The navigation bar appears under the menu bar and enables you to
navigate to Backup Exec’s views. Views that can be accessed through
the navigation bar include:
◆ Backup. Use this view to create a backup job.
◆ Restore. Use this view to create a restore job.
◆ Media Server. This view displays only if you have installed the
Central Admin Server Option (CASO). Use this view to monitor and
manage media servers in a CASO-enabled Backup Exec
environment.
◆ Job Setup. Use this view to perform tasks for new backup, restore,
and media rotation jobs, as well as to launch some utility jobs.
◆ Job Monitor. Use this view to monitor jobs and job history.
Through this view, you can also access the Outlook-like job
calendar and the System Summary.
◆ Alerts. Use this to view and respond to alerts, view alert history,
apply alert filters, and set up notification recipients to receive
e-mail or pager communications when alerts occur.
◆ Reports. Use this to view, print, save, and schedule reports about
your media server, its operations, and its device and media usage.
Also, you can use this to create a custom report. You can view a
report in Backup Exec in a PDF or HTML format. You can also save
and print reports in PDF, XML, HTML, Microsoft Excel (XLS), and
Comma Separated Value (CSV) formats.
◆ Devices. Use this view to create drive pools, cascaded drive pools,
and backup-to-disk folders, and to perform device operations and
access device properties pages.
◆ Media. Use this view to manage your media, create media sets, and
create media locations.
134 Administrator’s Guide

Chapter 3, Getting Started
Getting Started page options (continued)
Item Description
Using the Administration Console
Task pane The task pane displays on the left side of the Administration Console
by default, but can be hidden by selecting View, and then selecting
Task Pane. Through the task pane, you can initiate actions such as
creating a new backup job or responding to an alert. The contents of
the task pane are dynamic, changing according to the view selected
from the navigation bar. Some options may be unavailable until an
item is selected from the console screen or a prerequisite task is
performed. For example, you cannot select Rename from the Devices
task pane unless you have first selected an item that can be renamed,
such as a user-created drive pool.
Selection pane The Selection pane is where you select items to work with, such as
files to back up or restore.
Results pane The Results pane is the large pane on the right side of the screen that
usually contains a list or tree view of items that correspond to items
that are selected in the Selection pane. For example, if you select a
Backup-to-Disk folder in the Selection pane, the Backup-to-Disk files
that are contained in the folder display in the Results pane. This pane
can be divided to display a preview pane.
Preview pane The preview pane displays on the bottom right of the Administration
Console. It displays information about the item selected in the list or
tree view. This pane can be hidden by selecting View, and then
selecting Preview Pane.
Status bar The status bar appears on the bottom of the Administration Console
and provides information about the media server, jobs running or
scheduled to run on the server, alerts, and services running.
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 would like to make visible, configure column settings, or sort the
columns. You can also change the order of the entries in a column by
clicking the column heading. For example, names of reports display in
alphabetical order by default. To display report names in reverse
alphabetical order, click the Name column heading on the Reports
view.
135

Frequently asked questions
Using Backup Exec dialog boxes
Most of Backup Exec’s dialog boxes contain a Properties pane on the left side. Options
that correspond to the selected subnode display on the right side of the dialog box.
Frequently asked questions
How do I run a backup job?
There are several ways to run a backup, depending on your backup needs and level of
experience with Backup Exec. Use one of the following to run a backup job:
Ways to run a backup job
If you are a Do this
New user Use the Backup Wizard, which guides you through the setup of a
backup job.
Experienced user Do one of the following:
◆ On the navigation bar, click the arrow next to Backup, and then
click New Backup Job to configure the options for a backup job.
For more information about the various ways to create a backup job, see “Backing up
data” on page 345.
Where can I find the wizards?
You can find wizards in the following locations:
Location of wizards
To access wizards Do this
On the Backup Exec
Assistant
◆ On the navigation bar, click Job Setup to create a policy to use for
multiple backup jobs.
◆ Use Windows Explorer to create a backup job.
On the Help menu, click Backup Exec Assistant.
On the Tools menu On the Tools menu, click Wizards.
136 Administrator’s Guide

Where can I find the Readme file?
You can find the readme in the following locations:
Location of readme
Where can I find the online documentation for Backup Exec?
You can find the online documentation in the following locations:
How do I get in touch with Technical Support?
You can contact Technical Support the following ways:
Chapter 3, Getting Started
To access the readme Do this
In the Backup Exec
directory
Frequently asked questions
In the directory where Backup Exec was installed. The default
directory is C:\Program Files\Symantec\Backup Exec.
On the Help menu On the Help menu, click ReadMe File.
Location of documentation
To access the
documentation
On the Backup Exec
Assistant
Do this
◆ On the Help menu, click Backup Exec Assistant.
◆ Under Documentation, click View Symantec Backup Exec
Administrator’s Guide.
On the Help menu On the Help menu, click Administrator’s Guide.
Ways to contact Technical Support
To contact technical
support
On the Backup Exec
Assistant
Do this
◆ On the Help menu, click Backup Exec Assistant.
◆ Under Technical Support, click Backup Exec Technical Support.
On the Help menu On the Help menu, click Symantec on the Web > Online Support.
137

Backup Exec defaults
Backup Exec defaults
When you start Backup Exec for the first time, defaults are already configured. You can
adjust the defaults to meet the needs of your environment. Default settings are available
for various types of jobs, such as backup, restore, and test run. You also can set defaults
for catalogs, media management, bar code rules, and database maintenance.
The defaults that will probably affect you the most are the backup job defaults. You can
change many of these defaults after devising a media rotation strategy and creating
additional media sets and drive pools. In the short term though, you can run Backup
Exec and backup and restore jobs safely by using only the defaults set during
installation.
See the following sections for more information about default options:
Backup Exec default options
Item Description
Jobs “Setting default backup options” on page 389
“Setting defaults for restore jobs” on page 520
“Setting test run default options” on page 387
“Setting catalog defaults” on page 485
“Creating separate selection lists for each computer or resource” on
page 335
“Setting priority and availability windows for selection lists” on
page 334
Customizing Backup
Exec
“Setting default pre/post commands” on page 396
“Setting default backup network and security options” on page 400
Configuring Backup Exec “Configuring database maintenance” on page 162
Reports “Setting default options for reports” on page 601
Administrating Backup
Exec
“Configuring default schedule options” on page 377
“Using checkpoint restart on Microsoft Cluster Server failover” on
page 709
“Setting thresholds to recover jobs” on page 480
“Scheduling automatic updates using LiveUpdate” on page 126
Device and Media “Changing default preferences” on page 139
“Media locations and vaults” on page 286
“Bar code rules in mixed media libraries” on page 281
138 Administrator’s Guide

Changing default preferences
Chapter 3, Getting Started
Backup Exec default options (continued)
Item Description
Backup Exec defaults
Options “Setting offhost backup options for backup jobs” on page 892
“Setting defaults for the Advanced Open File Option for backup jobs”
on page 850
“Setting default backup and restore options for SQL” on page 1383
“Preparing for disaster recovery of Exchange Server” on page 1280
“Configuring default Lotus Domino options” on page 1318
“Setting default options for the Remote Agent for NetWare Systems”
on page 933
“Setting default options for SharePoint Portal Server 2003” on
page 1311
You can set defaults for the way you prefer Backup Exec to display various screens,
indicators, and alerts.
To set default preferences
1. On the Tools menu, click Options.
2. On the Properties pane, under Settings, click Preferences.
3. Select the appropriate options as follows:.
Show splash screen at
startup
Include robotic libraries
in inventory job when
Backup Exec services
start up
Select this option to display the splash screen when you start
Backup Exec. If this option is cleared, the Backup Exec
Administration Console is the first thing to display on
startup.
Select this option to have Backup Exec inventory all of the
slots in a robotic library when Backup Exec’s services are
starting. Depending on the number of storage devices
attached to your system, this process may take a few minutes.
139

Backup Exec defaults
Enable backup from
Windows Explorer
Display the job summary
before creating a job
Create jobs after a new
policy is created
Display progress
indicators for backup
jobs (requires additional
time to pre-scan devices)
Enable percentage bars
when available
Alerts
Automatically display
new alerts
Play sound after
receiving alert
ScreenTips
Select this option to create and submit backup jobs from
Windows Explorer. For more information, see “Using Backup
Exec’s Windows Explorer interface to back up data” on
page 377. If this option is cleared, you will not be able to
submit backups using the Backup Exec Windows Explorer
interface.
Select this option to have Backup Exec display a summary of
the job options you selected before submitting the job to the
job queue.
Select this option to have Backup Exec automatically display
the Create or Delete Policy Jobs dialog box after you create a
policy. You can use the Create or Delete Policy Jobs dialog box
to create jobs by associating selection lists with policies.
Select this option to display the percentage complete number
while a backup job is processing. These indicators appear in
the Job Activity tab, and they allow you to monitor the
progress of the job. Backups might take a little longer to
complete when this option is selected because the target
resources must be scanned to determine the amount of data
to be backed up.
Note Due to the time required to scan the target resources,
selecting this option when backing up remote
resources is not recommended.
Select this option to display a shaded percentage complete
bar in the Percent Complete column for active jobs. The
percentage complete bar displays in addition to the
percentage complete number.
Note If the color depth on your computer is set to 256 or
less, this option may appear as unavailable.
Select this option to have alerts automatically appear on the
desktop when they are sent. If you do not choose this option,
you are required to view and respond to alerts through the
Alerts view.
Select this option to have Backup Exec send an audible tone
when an alert is generated. Information about alerts can be
found in the Alerts view.
140 Administrator’s Guide

Chapter 3, Getting Started
Enable backup from
Windows Explorer
Display the job summary
before creating a job
Create jobs after a new
policy is created
Display progress
indicators for backup
jobs (requires additional
time to pre-scan devices)
Enable percentage bars
when available
Alerts
Automatically display
new alerts
Play sound after
receiving alert
ScreenTips
Backup Exec defaults
Select this option to create and submit backup jobs from
Windows Explorer. For more information, see “Using Backup
Exec’s Windows Explorer interface to back up data” on
page 377. If this option is cleared, you will not be able to
submit backups using the Backup Exec Windows Explorer
interface.
Select this option to have Backup Exec display a summary of
the job options you selected before submitting the job to the
job queue.
Select this option to have Backup Exec automatically display
the Create or Delete Policy Jobs dialog box after you create a
policy. You can use the Create or Delete Policy Jobs dialog box
to create jobs by associating selection lists with policies.
Select this option to display the percentage complete number
while a backup job is processing. These indicators appear in
the Job Activity tab, and they allow you to monitor the
progress of the job. Backups might take a little longer to
complete when this option is selected because the target
resources must be scanned to determine the amount of data
to be backed up.
Note Due to the time required to scan the target resources,
selecting this option when backing up remote
resources is not recommended.
Select this option to display a shaded percentage complete
bar in the Percent Complete column for active jobs. The
percentage complete bar displays in addition to the
percentage complete number.
Note If the color depth on your computer is set to 256 or
less, this option may appear as unavailable.
Select this option to have alerts automatically appear on the
desktop when they are sent. If you do not choose this option,
you are required to view and respond to alerts through the
Alerts view.
Select this option to have Backup Exec send an audible tone
when an alert is generated. Information about alerts can be
found in the Alerts view.
141

Backup Exec defaults
Enable backup from
Windows Explorer
Display the job summary
before creating a job
Create jobs after a new
policy is created
Display progress
indicators for backup
jobs (requires additional
time to pre-scan devices)
Enable percentage bars
when available
Alerts
Automatically display
new alerts
Play sound after
receiving alert
ScreenTips
Select this option to create and submit backup jobs from
Windows Explorer. For more information, see “Using Backup
Exec’s Windows Explorer interface to back up data” on
page 377. If this option is cleared, you will not be able to
submit backups using the Backup Exec Windows Explorer
interface.
Select this option to have Backup Exec display a summary of
the job options you selected before submitting the job to the
job queue.
Select this option to have Backup Exec automatically display
the Create or Delete Policy Jobs dialog box after you create a
policy. You can use the Create or Delete Policy Jobs dialog box
to create jobs by associating selection lists with policies.
Select this option to display the percentage complete number
while a backup job is processing. These indicators appear in
the Job Activity tab, and they allow you to monitor the
progress of the job. Backups might take a little longer to
complete when this option is selected because the target
resources must be scanned to determine the amount of data
to be backed up.
Note Due to the time required to scan the target resources,
selecting this option when backing up remote
resources is not recommended.
Select this option to display a shaded percentage complete
bar in the Percent Complete column for active jobs. The
percentage complete bar displays in addition to the
percentage complete number.
Note If the color depth on your computer is set to 256 or
less, this option may appear as unavailable.
Select this option to have alerts automatically appear on the
desktop when they are sent. If you do not choose this option,
you are required to view and respond to alerts through the
Alerts view.
Select this option to have Backup Exec send an audible tone
when an alert is generated. Information about alerts can be
found in the Alerts view.
142 Administrator’s Guide

Chapter 3, Getting Started
Backup Exec defaults
Enable ScreenTips Select this option to enable or disable ScreenTips, which
provide brief explanations of selected items on the
Administration Console. When ScreenTips are enabled, you
can view them by holding the mouse pointer on an item. Only
selected items have ScreenTips.
Seconds to delay display
of ScreenTips
Shade rows
Shade alternate rows in
Backup Exec views
If you selected the Enable ScreenTips option, type the
number of seconds you want Backup Exec to wait before
displaying ScreenTips. For example, if you type 10, the
mouse must be held over the item for 10 seconds before
Backup Exec displays the ScreenTip for the item.
Select this option to enable or disable highlighting on every
other row in various lists, such as the current jobs and job
history lists on the Job Monitor. Highlighting facilitates
viewing of long lists. This option is selected by default.
Note If the color depth on your computer is set to 256 or
less, this option may appear as unavailable.
Set contrast of shading If you selected the Shade alternate rows in Backup Exec
views option, use the slider to set the darkness of the shading
in the rows.
143

Backup Exec defaults
Changing device and media job defaults
You can set the default device and media set to use for each job that you create.
To change device and media job defaults
1. On the Tools menu, click Options.
2. On the Options - Set Application Defaults dialog box, under Job Defaults, click
Device and Media.
3. Select the appropriate options as follows:
Device Select the device that you want to use as the default device for jobs.
You can change this default for each job individually.
Media set Select the media set that you want to be used as the default media
set for jobs. You can change this default for each job individually.
144 Administrator’s Guide

Chapter
Configuring Backup Exec
settings and options
4
During installation and prior to first use, you configure several Backup Exec features,
such as a default logon account, database information, and audit log settings.
Configuring Backup Exec lets you standardize Backup Exec before jobs are created and
run. You can perform the following initial operations:
■ Configure logon accounts
■ Set the default Backup Exec logon account
■ Create new Backup Exec system logon accounts
■ Copy configuration settings and logon information to another media server
■ Configure audit logs
■ Configure database maintenance
■ Configuring and organizing columns in Backup Exec
Related Topics:
“Default backup exec logon account” on page 147
“Backup Exec System Logon Account” on page 148
“Copying configuration settings” on page 156
“Audit logs” on page 160
“Configuring database maintenance” on page 162
“Configuring columns” on page 164
“Sorting columns” on page 166
145

Configuring logon accounts
Configuring logon accounts
A Backup Exec logon account stores the credentials of a Windows user account. Backup
Exec logon accounts enable Backup Exec to manage user names and passwords and can
be used to browse resources or process jobs. Using Backup Exec logon accounts enables
you to apply Windows credential changes to the jobs that use them.
Backup Exec logon accounts are used to browse local and remote resources. Backup Exec
logon accounts can also be associated with selection list entries at the device level such
as shares, databases, etc. If you need to edit the credentials, you can edit the Backup Exec
logon account and the changes will be applied to the selected resources that use the
Backup Exec logon account.
Backup Exec logon accounts are not Windows 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 Windows 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 Windows user account.
You can view, create, delete, edit, and replace Backup Exec logon accounts using the
Logon Account Management dialog box.
The dialog box displays property information for each Backup Exec logon account you
create. It also displays your default Backup Exec logon account and the Windows user
name that is currently logged on to the media server. To view this information, select the
Network menu, and then click Logon Accounts.
The are three types of logon accounts in Backup Exec. They include:
Default Backup Exec
logon account
Backup Exec system
logon account
Backup Exec logon
account
Used to browse local and remote resources, make backup job
selections, and restore data.
Used to access most or all of your resources. It contains the
Backup Exec Services credentials.
Used to manage Backup Exec user names and passwords,
browse local and remote resources, process jobs, and apply
Microsoft Windows credential changes to the jobs that use
them.
Related Topics:
“Creating a Backup Exec logon account” on page 149
146 Administrator’s Guide

Default backup exec logon account
Chapter 4, Configuring Backup Exec settings and options
Configuring logon accounts
The default Backup Exec logon account enables you to browse, make selections, or
restore data. The first time you start Backup Exec, you must specify a default Backup
Exec logon account using the Logon Account Wizard. You can select an existing Backup
Exec logon account or create a new one.
You can create multiple Backup Exec logon accounts; however, each Backup Exec user can
only have one default Backup Exec logon account. Your default Backup Exec logon
account enables you to perform the following:
■ Browse resources. Your default Backup Exec logon account enables you to browse
local and remote resources when you create backup jobs. To browse resources, each
user must have a default Backup Exec logon account that is associated with their
Windows user account. The Backup Exec logon account does not have to be the same
user name as the Windows user that is used to log on to Backup Exec.
For example, you are logged on to a media server named MEDIASERVER as the local
Windows administrator. When you start Backup Exec, you are prompted to create a
default Backup Exec logon account for the local administrator because one does not
exist. You can create a Backup Exec logon account for the local administrator that
has the credentials for a domain administrator. The Backup Exec logon account will
have the following properties:
User name: DOMAIN\Administrator
Description: MEDIASERVER\Administrator Default Account
Owner: MEDIASERVER\Administrator
When you change your default Backup Exec logon account, you can use your new
default Backup Exec logon account to browse resources immediately; you do not have
to restart your system in order for the changes take effect.
■ Make backup selections. You can select a different Backup Exec logon account when
you make selections for backup. If your default does not have rights, the Logon
Account Selection dialog box appears and enables you to create or select a different
Backup Exec logon account. You can also change the Backup Exec logon account
when making backup selections using the Connect As command in the context
menu.
Note For more information on using Backup Exec logon accounts with Exchange
mailbox and SQL backups, see “Using Backup Exec logon accounts for SQL
resources” on page 1337 and “Exchange mailbox access requirements” on
page 1224.
147

Configuring logon accounts
■ Restore. You can assign Backup Exec logon accounts to resources when you create
restore jobs. The default Backup Exec logon account is used unless you choose a
different Backup Exec logon account when you create the restore job, in Resource
Credentials in the Restore Job Properties.
Related Topics:
“Changing your default Backup Exec logon account” on page 154
Backup Exec System Logon Account
The Backup Exec System Logon Account (SLA) is created when you install Backup Exec.
When the SLA is created, the username and password match the credentials provided
during install for the Backup Exec Services credentials. The owner of the SLA is the
Windows user that installed Backup Exec and is a common account by default. Common
accounts are shared accounts that can be accessed by all users.
The Backup Exec System Logon Account may have access to most or all of your
resources since it contains the Backup Exec Services credentials. If you want to make
Backup Exec more secure, you can change the SLA to be a restricted account. You can
also delete it after making another logon account the default. However, if you delete the
SLA, the jobs in which it is used may fail. If the SLA is deleted, you can re-create it using
the Logon Account Management dialog box.
The SLA is used for the following tasks and jobs:
■ Jobs migrated from a previous version of Backup Exec
■ Windows Explorer interface jobs
■ Duplicate backup data jobs
■ Command Line Applet (bemcmd.exe)
■ Backup Exec Agent for SAP Applications
Related Topics:
“Creating a new Backup Exec System Logon Account” on page 154
“Creating a Backup Exec logon account” on page 149
“Editing a Backup Exec logon account” on page 150
“Replacing a Backup Exec logon account” on page 152
“Deleting a Backup Exec logon account” on page 153
“Changing your default Backup Exec logon account” on page 154
“Copying configuration settings” on page 156
148 Administrator’s Guide

Creating a Backup Exec logon account
Chapter 4, Configuring Backup Exec settings and options
Configuring logon accounts
You can create Backup Exec logon accounts using the Logon Account Wizard, which
guides you through the creation of a Backup Exec logon account, or by using the Logon
Account Management dialog. You can enter Backup Exec logon account property
information when you create the Backup Exec logon account; however, Backup Exec
assigns the Backup Exec logon account owner to the Windows user name you used to log
on to Backup Exec. The owner of the Backup Exec logon account cannot be modified.
To create a new Backup Exec logon account using the Logon Account Wizard
❖ On the Tools menu, click Wizards > Logon Account Wizard.
The wizard guides you through the process of creating a Backup Exec logon account.
To create a new Backup Exec logon account manually
1. On the Network menu, click Logon Accounts.
2. Click New.
3. Enter the appropriate optionss:
User name Type the fully qualified user name for the Backup Exec logon
account. For example, DOMAIN\Administrator. The user name is
provided when you attempt to connect to a resource. The user
name you enter is not case-sensitive for the resources that are
accessed.
Password Type the password for the account. The password you enter is
encrypted for security. You can leave this field blank if this Backup
Exec logon account does not need a password.
Confirm password Re-type the password for confirmation. The password must match
the password you typed in the Password field.
Account name Type the unique name for the Backup Exec logon account. The user
name is automatically added if you do not enter information into
the field.
Notes Type any comments to describe how the Backup Exec logon
account will be used.
149

Configuring logon accounts
This is a restricted
logon account
This is my default logon
account
4. Click OK to create the Backup Exec logon account.
Related Topics:
“Creating a new Backup Exec System Logon Account” on page 154
“Editing a Backup Exec logon account” on page 150
“Replacing a Backup Exec logon account” on page 152
“Deleting a Backup Exec logon account” on page 153
“Changing your default Backup Exec logon account” on page 154
“Copying configuration settings” on page 156
“Copying logon account information” on page 159
Editing a Backup Exec logon account
When you edit a Backup Exec logon account, the changes are automatically applied to all
the resources that use the Backup Exec logon account. Changes made to a Backup Exec
logon account are applied immediately. You do not have to restart your system for the
changes to take effect. You can edit the following properties for a Backup Exec logon
account:
■ Type (restricted or common)
■ Account name
■ Password
■ User name
■ Notes
Select this check box to enable the Backup Exec logon account to be
used only by the owner of the logon account and those who know
the password. If this is not selected, the Backup Exec logon account
will be a common account. Common accounts are shared accounts
that can be accessed by all users.
Select this check box to make this your default Backup Exec logon
account used to browse, make selections, or restore data on your
local and remote resources.
150 Administrator’s Guide

To edit a Backup Exec logon account
1. On the Network menu, click Logon Accounts.
Chapter 4, Configuring Backup Exec settings and options
Configuring logon accounts
2. Select the Backup Exec logon account you want to change, and then click Edit.
If you are not logged on to Backup Exec with the same user name as the Backup Exec
logon account owner, you must provide the password before you can edit the account.
3. Modify the Backup Exec logon account properties as needed.
4. On the Edit Logon Credentials dialog box, click OK.
Related Topics:
“Changing a Backup Exec logon account password” on page 151
“Creating a Backup Exec logon account” on page 149
“Replacing a Backup Exec logon account” on page 152
“Deleting a Backup Exec logon account” on page 153
“Creating a new Backup Exec System Logon Account” on page 154
“Changing your default Backup Exec logon account” on page 154
“Copying configuration settings” on page 156
“Copying logon account information” on page 159
Changing a Backup Exec logon account password
You can change a Backup Exec logon account password using the following steps.
Changes made to a Backup Exec logon account password are applied immediately.
To change a Backup Exec logon account password
1. On the Network menu, click Logon Accounts.
2. Select the Backup Exec logon account to change, and then click Edit.
If you are not logged on to Backup Exec with the same user name as the Backup Exec
logon account owner, you must provide the password before you can edit the
account.
3. Click Change password.
4. In the Password field, type a new password.
151

Configuring logon accounts
5. In the Confirm field, re-type the password, and then click OK.
6. On the Edit Logon Credentials dialog box, click OK.
7. On the Logon Account Management dialog box, click OK.
Related Topics:
“Creating a Backup Exec logon account” on page 149
“Replacing a Backup Exec logon account” on page 152
“Deleting a Backup Exec logon account” on page 153
“Creating a new Backup Exec System Logon Account” on page 154
“Changing your default Backup Exec logon account” on page 154
“Copying configuration settings” on page 156
“Copying logon account information” on page 159
Replacing a Backup Exec logon account
You can replace a Backup Exec logon account within all existing jobs and selections lists.
The resources and selections lists in existing jobs that use the Backup Exec logon
account will be updated to use the new Backup Exec logon account. If the new Backup
Exec logon account is restricted, you must provide the password.
To replace a Backup Exec logon account
1. On the Network menu, click Logon Accounts.
2. Select the Backup Exec logon account you want to replace, and then click Replace.
3. Select the Backup Exec logon account with which you want to replace the selected
Backup Exec logon account.
If the Backup Exec logon account is restricted and you are not logged on to Backup
Exec with the same user name as the Backup Exec logon account owner, you must
provide the password before you can edit the account.
4. Click OK.
Related Topics:
“Creating a new Backup Exec System Logon Account” on page 154
“Creating a Backup Exec logon account” on page 149
152 Administrator’s Guide

“Editing a Backup Exec logon account” on page 150
“Deleting a Backup Exec logon account” on page 153
“Creating a new Backup Exec System Logon Account” on page 154
“Changing your default Backup Exec logon account” on page 154
“Copying configuration settings” on page 156
Deleting a Backup Exec logon account
You cannot delete a Backup Exec logon account when it is:
■ Being referenced by a job.
■ Owned by a user who is logged on to the media server.
Chapter 4, Configuring Backup Exec settings and options
Configuring logon accounts
■ Set as the default Backup Exec logon account of a user who is logged on to the media
server.
You can delete a Backup Exec logon account when the owner is logged off and all users
who have it set as their default logon account are logged off.
To delete a Backup Exec logon account
1. On the Network menu, click Logon Accounts.
2. Select the Backup Exec logon account you want to delete, and then click Delete.
3. Click Yes to confirm the deletion.
Related Topics:
“Creating a Backup Exec logon account” on page 149
“Editing a Backup Exec logon account” on page 150
“Creating a new Backup Exec System Logon Account” on page 154
“Changing your default Backup Exec logon account” on page 154
“Creating a new Backup Exec System Logon Account” on page 154
“Copying configuration settings” on page 156
“Copying logon account information” on page 159
153

Configuring logon accounts
Changing your default Backup Exec logon account
You can change your default Backup Exec logon account that enables you to browse,
make selections, or restore data.
To change your default Backup Exec logon account
1. On the Network menu, click Logon Accounts.
2. Select the Backup Exec logon account you want to use as your default Backup Exec
logon account, and then do one of the following:
■ Click Set as Default.
■ Click Edit, select the check box This is my default logon account, and then click
OK.
Related Topics:
“Creating a Backup Exec logon account” on page 149
“Editing a Backup Exec logon account” on page 150
“Creating a new Backup Exec System Logon Account” on page 154
“Changing your default Backup Exec logon account” on page 154
“Creating a new Backup Exec System Logon Account” on page 154
“Copying configuration settings” on page 156
“Copying logon account information” on page 159
Creating a new Backup Exec System Logon Account
The Backup Exec System Logon Account enables you to perform several operations,
such as copy jobs and Windows Explorer interface jobs. It is also used with Backup Exec
Agent for SAP Applications and Command Line Applet. If you delete the Backup Exec
System Logon Account, you should create a new one that enables you to perform the
specified operations and use the agent and applet.
To create a new Backup Exec System Logon Account
1. On the Network menu, click Logon Accounts.
2. Click System Account.
154 Administrator’s Guide

Chapter 4, Configuring Backup Exec settings and options
Configuring logon accounts
3. Select the appropriate options as follows, and then click OK to create the system
logon account:
User name Type the fully qualified user name for the Backup Exec logon
account. For example, DOMAIN\Administrator. The user name is
provided when you attempt to connect to a resource. The user
name you enter is not case-sensitive for the resources that are
accessed.
Change password Enables you to type and confirm a new password for the account.
The password you enter is encrypted for security. You can leave
this field blank if this Backup Exec logon account does not need a
password.
Notes Type any comments to describe how the Backup Exec logon
account will be used.
This is a restricted
logon account
This is my default logon
account
Select this check box to enable the Backup Exec logon account to be
used only by the owner of the Backup Exec logon account and those
who know the password. If this is not selected, the Backup Exec
logon account will be a common account. Common accounts are
shared accounts that can be accessed by all users.
Select this check box to make this your default account used to
browse, make selections, or restore data on your local and remote
resources.
Related Topics:
“Creating a Backup Exec logon account” on page 149
“Editing a Backup Exec logon account” on page 150
“Deleting a Backup Exec logon account” on page 153
“Changing your default Backup Exec logon account” on page 154
“Creating a new Backup Exec System Logon Account” on page 154
“Copying configuration settings” on page 156
“Copying logon account information” on page 159
155

Copying configuration settings
Copying configuration settings
You can copy configuration settings and logon information from one media server to
another. This copy ability allows you to quickly set up a group of media servers with the
same configuration or logon settings.
Note To copy configuration settings and logon information to other media servers, the
Copy Server Configurations feature must be installed. For more information, see
step 7 in “Installing Backup Exec options to remote computers” on page 92.
To copy configuration settings
1. From the Tools menu, click Copy Settings to Media Servers.
2. Select the appropriate settings to copy.
Default job options Select this option to copy the default job options from this media
server to selected servers. For information about default job
options, see “Backup Exec defaults” on page 138.
Default schedule Select this option to copy the default schedule from this media
server to selected servers. For more information about default
schedule option, see “Configuring default schedule options” on
page 377.
Error-handling rules Select this option to copy error-handling rules from this media
server to selected servers. For more information about
error-handling rules, see “Error-handling rules” on page 474.
Alert configuration Select this option to copy alert configurations to selected servers.
For more information about alert configuration, see “Configuring
alert category properties” on page 540.
3. If the destination media servers appear on the list, select all of the media servers
that you want to copy to.
4. Click OK.
To add a destination media server in a non-CASO environment
1. If a destination media server name does not appear, click Add.
2. Enter the name of the media server.
156 Administrator’s Guide

Chapter 4, Configuring Backup Exec settings and options
Copying configuration settings
3. If necessary, click Change Logon Account and select or enter the correct logon
account information (see “Configuring logon accounts” on page 146).
Note Changing a logon account does not permanently change the logon account for
each selected media server.
4. Click OK.
5. Repeat the previous steps, if necessary, to add another media server that you want
to copy the configurations to.
6. After all media servers have been selected, click OK.
To add a destination media server in a CASO environment
1. If a destination media server name does not appear, click Add.
2. Select one of the following:
Add an individual media
server
Add the managed media
servers in a media
server pool
Add all managed media
servers
This option lets you add an individual media server. Select this
option and then enter a media server in the Media server name box.
You can also click the ellipsis button and then browse to the media
server you want to add.
This option lets you add all the managed media servers in a media
server pool. Select this option, and then select a media server pool
in the Media server pool name box to which you want to copy
configuration settings and logon information. For more
information, see “Creating a media server pool” on page 820
This option appears only if CASO is installed. Select this option to
copy configuration settings and logon information to all of the
managed media servers in the CASO environment.
3. If necessary, click Change Logon Account and select or enter the correct logon
account information to be used to complete the copy operation (see “Configuring
logon accounts” on page 146). Changing a logon account credentials for a copy
operation does not permanently change the logon account.
4. If you want to import a list of media servers, click Import List, browse to select the
list, and then click Open.
5. After all media servers have been selected, click OK.
157

Copying configuration settings
To edit existing media server information
1. On the Copy Settings dialog box, in the Destination media servers box, select a
media server.
2. Click Edit.
3. Make the appropriate changes and then click OK.
To remove an existing media server from the Destination media servers box
1. On the Copy Settings dialog box, in the Destination media servers box, select a
media server.
2. Click Remove.
3. Click OK.
To import a list of media servers
1. On the Copy Settings dialog box, click Import List.
2. Browse to select the list, and then click Open.
3. Click OK.
Related Topics:
“Creating a Backup Exec logon account” on page 149
“Editing a Backup Exec logon account” on page 150
“Deleting a Backup Exec logon account” on page 153
“Changing your default Backup Exec logon account” on page 154
“Creating a new Backup Exec System Logon Account” on page 154
“Copying logon account information” on page 159
158 Administrator’s Guide

Copying logon account information
To copy logon accounts information
1. From the Network menu, click Logon Accounts.
Chapter 4, Configuring Backup Exec settings and options
Copying logon account information
2. Select the logon account information you want to copy, and then click Copy to
Servers.
3. On the Copy Logon Account dialog box, select the appropriate options as follows:
Server Name Enter the name of the media server you want to copy the logon
account information to, and then click Add.
Add Click this button after entering the name of a media server that you
want to copy the logon account to.
Remove Select a media server in the list, and then click this button if you
want to remove a media server from the list.
Import List Click this button if you want to import a list of media servers to be
added to the media servers in the list. The list should include only
the media server name, with one per line.
Logon Account Click this to select the logon account to use when connecting to the
media servers in the list.
If an account with this
description already
exists on the destination
server, overwrite it
4. Click OK.
Select this option if you want to overwrite logon accounts for an
existing job having the same name. This option only appears if you
are copying a job to another media server.
Related Topics:
“Configuring logon accounts” on page 146
“Configuring database maintenance” on page 162
“Configuring Backup Exec settings and options” on page 145
“Copying configuration settings” on page 156
159

Audit logs
Audit logs
Use audit logs to examine and review information about operations that have been
performed in Backup Exec. The audit log displays the date and time of the activity, who
performed it, what the activity was, and a description of the activity.
You can view information about activities that occur for all or any of the following:
■ Alerts
■ Audit logs
■ Devices and media
■ Encryption keys
■ Error-handling rules
■ Jobs
■ Logon accounts
■ Policies and job templates
■ Selection lists
■ Server configuration
You can delete the audit logs as part of the Backup Exec database maintenance, and you
can save the audit log to a file. Changes made to the audit log, such as when database
maintenance occurs, can also be displayed in the audit log.
Related Topics:
“Configuring the audit log” on page 160
“Viewing the audit log” on page 161
Configuring the audit log
Configure the audit log to display information about specific operations that are
performed on items in Backup Exec.
To configure the audit log
1. On the Tools menu, click Audit Log.
2. Click Configure Logging.
3. On the Audit Log Configuration dialog box, select the check box of the category that
you want to display in the audit log.
160 Administrator’s Guide

Chapter 4, Configuring Backup Exec settings and options
Audit logs
Expand the category by clicking the plus sign to the left of the category. Select the
operations that you want to display for the category.
Clear the check box of any item or operation that you do not want to display.
4. Click OK.
Related Topics:
“Audit logs” on page 160
“Viewing the audit log” on page 161
Viewing the audit log
To view the audit log
1. On the Tools menu, click Audit Log.
The Audit Log dialog box provides the following information:
Select category to view Click the drop-down arrow to view all of the items for which you
can view and configure audit logging. Select All to display changes
for all Backup Exec items, or select another category for which to
display changes.
Date/Time The date and time that this change was made in Backup Exec. Click
the column head to sort the information by date.
User Name The domain and user name of the user that made the change. Click
the column head to sort the information alphabetically.
Category The item or items that you have selected for audit logging. Click
the column head to sort the information alphabetically.
Message The action that was recorded by Backup Exec for the operation that
was performed. Click the column head to sort the information
alphabetically.
2. Use the scroll bar at the bottom of the Audit log window to view the whole entry, or
double-click the entry to display the same information in an easy-to-read Audit Log
Record.
3. Do any of the following:
■ Click Refresh to update the audit log with new entries.
161

Configuring database maintenance
■ Click Clear Category Log to remove all entries from an audit log category.
If you select specific categories to view, only the logs generated for the selected
categories are cleared when you click Clear Category Log.
■ Click Save Log to File to specify a file name and location to save the audit log
entries.
■ Click Properties to display information about the entry.
■ Click Configure Logging to select the types of items and the types of changes
made to the items that you want to display in the audit log. See “Configuring the
audit log” on page 160.
Related Topics:
“Configuring database maintenance” on page 162.
“Configuring the audit log” on page 160
Configuring database maintenance
The Database Maintenance option enables you to manage the Backup Exec database and
the Desktop and Laptop Option (DLO) database. Each database maintenance operation is
performed independently on each database. The Backup Exec database maintains a
record of files and data you have configured such as templates and catalogs. Database
maintenance enables you to perform the following:
■ Optimize database size
■ Delete expired data
■ Save the contents of the database files
■ Perform a database consistency check
You do not have to select all the options; however, each one performs a different process
that enables you to protect and maintain your database. Selecting all the options enables
you to recover the database quickly and maintain optimal performance.
Informational alerts are generated at the beginning and the end of the database
maintenance process each time database maintenance is performed. The alerts provide
details about the type of maintenance that was performed on each database and the
amount of time the maintenance took to complete. If the database maintenance process
fails, the alert indicates where the failure occurred and the reason for the failure.
162 Administrator’s Guide

To configure database maintenance
1. On the Tools menu, click Options.
2. Under Settings, click Database Maintenance.
3. Select the appropriate options as follows, and then click OK:
Enable Backup Exec
database maintenance
Last time maintenance
was performed
Perform database
maintenance at
Chapter 4, Configuring Backup Exec settings and options
Configuring database maintenance
Select this check box to activate the database maintenance process.
The date and time the last database maintenance was performed.
Enter the time you want to perform database maintenance. All the
maintenance will occur once a day at the time you specify.
Delete aged data Select this check box to activate the deletion of expired job history,
job logs, alert history, and reports from the Backup Exec database
after the specified number of days have passed.
Note For the Desktop and Laptop Option (DLO) database, only the
Alert History setting applies. DLO does not have job history,
job logs, or reports.
Keep job history for data
on media that have
current overwrite
protection periods
Keep job history for
specified number of
days
Select this option to keep all job history data for any media that
currently has an overwrite protection policy assigned to it. After a
media’s overwrite protection policy expires, the media’s job history
data can be deleted.
Enter the number of days to keep job history data in the database
before it is deleted. Job history data includes summary statistics for
a job and details about media, devices and backup sets used to
process the job.
Job logs Enter the number of days to keep job logs in the database before
they are deleted. Job logs includes detailed information about the
job.
Alert history Enter the number of days to keep alert history data in the database
before it is deleted. Alert history data includes property and
response information for the alert.
Reports Enter the number of days to keep report data in the database before
it is deleted. Report data includes property information about
report jobs that were generated. The report itself is not deleted.
163

Configuring columns
Audit logs Enter the number of days to keep audit log data in the database
before it is deleted. Audit logs include information that you have
selected about operations that are performed in Backup Exec. See
“Audit logs” on page 160.
Perform database
consistency check
Save contents of
database to the Backup
Exec data directory
Related Topics:
“Configuring the audit log” on page 160
Configuring columns
Backup Exec uses panes to present information to you in a structured and organized
manner. Within each pane are columns that specify the type of information that is
displayed. You can remove columns that may not interest you. You can also rearrange
the order in which the columns appear.
The position of the column names in the Column Settings dialog box dictates the
column’s positioning within the pane. For example, column names appearing at the top
of the list are positioned on the left side of the pane.
Related Topics:
“Hiding a column” on page 165
“Displaying a column” on page 165
“Rearranging columns” on page 165
“Sorting columns” on page 166
Select this check box to check the logical and physical consistency
of the data in the database.
Note The option is not checked by default, but it is recommended
that you run a consistency check periodically at a time when
there is minimal activity from Backup Exec.
Select this check box to dump the data contained in the database
into the Backup Exec data directory so that the database backup
file (BEDB.bak) can be backed up. The dump file will be maintained
in the data directory until the next database maintenance process
is performed and then this file will be overwritten. Selecting this
option enables you to recover the database in the event of failure.
Optimize database size Select this check box to reorganize fragmented pages and decrease
the size of the physical database to 10 percent above what is
actually used.
164 Administrator’s Guide

Hiding a column
To hide a column
Chapter 4, Configuring Backup Exec settings and options
Configuring columns
1. Right-click any column title on title bar in the pane where you want column
information hidden.
2. Click the column title you want to hide.
Related Topics:
“Displaying a column” on page 165
“Rearranging columns” on page 165
“Sorting columns” on page 166
Displaying a column
To display a column
1. Right-click any column title on title bar in the pane where you a column to appear.
2. Select a column that you want to appear.
Related Topics:
“Hiding a column” on page 165
“Rearranging columns” on page 165
“Sorting columns” on page 166
Rearranging columns
To rearrange columns
1. Right-click any column title.
2. Click Configure Columns.
3. Select a column title, and then click Move Up or Move down.
Each click of the Move Up button moves the column name one column to the left in
the pane, while each click of the Move Down button moves the selected column
name one column to the right.
165

Configuring columns
4. If you want to change the width of a column:
■ Select the column.
■ In the Width of selected column (in pixels) field, enter the column width.
5. Click OK.
Related Topics:
“Hiding a column” on page 165
“Displaying a column” on page 165
“Sorting columns” on page 166
Sorting columns
You can sort information by the column titles that appear in a pane. When you sort on
column titles, Backup Exec arranges all of the data that matches the sort criteria
together and displays it in the pane below the column titles. Ascending order lists
numbers from smallest to largest and lists letters in alphabetical order. Descending
order lists numbers from largest to smallest and lists letters in reverse alphabetical
order.
To sort column information
1. Right-click any column title on the pane where you want to sort job information.
2. Click Multi-Column Sort.
3. In the Sort by list, select the column titles on which you want to sort information.
4. Click Ascending to sort the information in ascending order or click Descending to
sort the information in descending order.
5. Repeat step 3 and step 4 in the Then by lists.
6. Click OK.
Related Topics:
“Hiding a column” on page 165
“Displaying a column” on page 165
“Rearranging columns” on page 165
166 Administrator’s Guide

Managing devices
Chapter
Device management in Backup Exec simplifies how you organize and allocate the
storage devices recognized by Backup Exec, including:
■ Tape drives or robotic libraries physically attached to a media server.
■ Virtual devices, called backup-to-disk folders, that you create.
■ Shared devices used in a SAN or CASO environment.
■ Removable storage devices shared by applications through the use of Microsoft’s
Removable Storage Feature.
For a list of supported devices, see:
http://support.veritas.com/menu_ddProduct_BEWNT_view_CL.htm
With Backup Exec, you can maximize your hardware investment by organizing your
devices in one or both of the following methods:
5
■ Device pools. Devices are grouped so that jobs assigned to the device pool are run on
the first available device. Setting up device pools offers the following benefits:
■ Automatic job rescheduling. If a device fails while a job is running on it, that job
is rescheduled and placed on hold. Other scheduled jobs are rerouted to working
devices in the device pool.
■ Concurrent processing. Devices in the device pool run different jobs at the same
time, allowing maximum hardware efficiency.
■ Dynamic load balancing. Jobs are more evenly distributed between all of the
devices included in the device pool when running simultaneous jobs.
■ Cascaded drive pools. Drives of the same type are linked together so that large
backup jobs that exceed the capacity of the media in one drive automatically
continue on the media in the next drive that is defined in the pool. The cascaded
drives appear logically as one device.
167

Viewing storage devices
Or, you can use the storage devices as they are configured by Backup Exec at
installation, without making any changes. The default device pool, All Devices
(Computer Name) is the default destination device when you create a backup job. By
default, the All Devices device pool contains all locally attached devices. If you have
installed the SAN Shared Storage Option, both locally attached and shared storage
devices appear in All Devices (Computer Name). If you have installed the Backup Exec
NDMP Option, you can add an NDMP server as a storage device.
In addition to device pools and cascaded drive pools, Backup Exec provides other device
management capabilities. You can:
■ Identify and monitor the current status of all storage devices.
■ Change physical tape devices without rebooting the Backup Exec server.
■ Monitor device usage statistics and track hardware errors. Backup Exec keeps track
of the device’s age, hours of use, mounts, number of bytes processed (written and
read), errors, when the device was last cleaned, and so on.
■ Manage the physical devices attached to the media server and perform operations
on these devices and the media contained in them.
Note Most of the benefits derived from Backup Exec’s device management functionality
are realized when using more than one storage device. However, users with only
one device can still take full advantage of Backup Exec’s device monitoring to help
make sure their devices are working properly.
Related Topics:
“Symantec Backup Exec SAN Shared Storage Option” on page 1547
“Symantec Backup Exec NDMP Option” on page 1571
“Creating utility jobs to help manage devices and media” on page 237
Viewing storage devices
When Backup Exec is installed, all storage devices connected to the media server are
automatically recognized as either robotic libraries or stand-alone drives. A stand-alone
drive is a single, locally attached tape drive.
Note Support for a single robotic library device is included with Backup Exec for
Windows Servers. Licenses for additional robotic library devices are available for
purchase.
168 Administrator’s Guide

Chapter 5, Managing devices
Viewing storage devices
If you group one or more robotic library slots into partitions, the partition drive pools
appear in the Devices view under the Device Pools icon. For information about
partitioning robotic library slots, see “Creating robotic library partitions” on page 214.
Click Devices on the navigation bar to see how devices are organized logically in device
pools, and how devices are arranged physically on servers. All devices that are displayed
under Storage Devices are available, including device pools, stand-alone drives, robotic
libraries, backup-to-disk folders, removable backup-to-disk folders, and cascaded drive
pools. If the SAN Shared Storage Option is installed, you can also view available
secondary storage devices on the storage area network. Media in the devices are also
displayed in the Devices view. You can run operations on the media such as running a
catalog job, restoring data, and more.
All logical groupings of the physical devices are displayed under Device Pools and
Cascaded Drive Pools. Cascaded drive pools are displayed under servers because they
only consist of drives from that server; they effectively act as a single device under that
server.
The default device pool All Devices (Computer Name) contains the media server’s locally
attached devices as well as any backup-to-disk folders created. Backup-to-disk folders
are destination devices for backups that are directed to your hard disk. The data from
these backups is saved on disk as backup-to-disk files.
If you are using the SAN Shared Storage Option, each server on the SAN will have an All
Devices (Computer Name) node that contains both local and shared devices available to
the server. At installation, all storage devices are automatically assigned to All Devices
(Computer Name).
If you have installed the NDMP Option, you can add an NDMP Server as a storage device.
Adding an NDMP Server as a storage device will also add it to the backup selection list.
Separate wizards are available for creating backup-to-disk folders and installing tape
device drivers. If you are new to Backup Exec, it may be easier to use the Device
Configuration Wizard to create and configure backup-to-disk folders, to install
Symantec device drivers, and to correct the display of robotic library drives that are
inadvertently displayed as an unknown device in the Devices view.
Related Topics:
“Configuring storage devices by using the Device Configuration Wizard” on page 171
“Viewing media in storage devices” on page 170
“Viewing device pool properties” on page 182
“Viewing properties of a cascaded drive pool” on page 187
“Viewing storage device properties” on page 195
“About devices in the shared storage environment” on page 1551
169

Viewing media in storage devices
Viewing media in storage devices
If you select a device or select Slots in the Devices view, information for the media
contained in the device or slot appears in the results pane. This information is also
displayed when you click Media on the navigation bar, and then click All Media.
You can run operations on the media by selecting a media, and then selecting a task in
the task pane, such as Catalog Media or Restore Data.
Media information in the Devices view
Item Description
Slot Number Number of the slot. This field only appears if Slots has been selected.
Bar Code Label obtained from a bar code reader. This field only appears if Slots
has been selected. Bar code information only appears if the robotic
library has a bar code reader and a bar code label is on the media.
Media Label Media label that was assigned automatically by Backup Exec, or that
was assigned or changed by the administrator, or that was a
pre-assigned bar code label.
You can edit the media label, which is limited to 32 characters. Editing
the label changes the name of the media in the display, but does not
write the new label to the media until an overwrite operation occurs.
When you edit a media label, try to make it a concise identifier that
will remain constant even when the media is reused. You should write
this media label on a label fixed to the outside of the physical media.
Duplicate labels can be automatically generated. For example,
reinstalling Backup Exec or bringing media from another Backup Exec
installation could cause duplication in labels. Duplicate labels are
allowed, but not recommended.
Note If a bar code is available, and a bar code-equipped device is used,
then the media label automatically defaults to that bar code.
Media Description By default, displays the original media label if the media is imported
media. If the media description has been edited, the new description
appears. Otherwise, this field is blank.
Allocated Date Date and time when the media was added to a media set as a result of
an overwrite operation.
Media Set Name of the media set this media belongs to.
Media Location Name of the device or vault where this media is located.
170 Administrator’s Guide

Media information in the Devices view
Item Description
Overwrite Protected
Until
Chapter 5, Managing devices
Configuring storage devices by using the Device Configuration Wizard
Date and time after which the media can be overwritten.
Appendable Until Date and time after which the media can no longer be appended to.
Used Capacity The amount of raw capacity on the media that has been used. Used
Capacity is calculated by subtracting Available Capacity from Total
Capacity.
Used Capacity may or may not equal Bytes Written.
Compression Ratio The ratio of Bytes Written to Used Capacity. Compression ratio will
show the overall effect that data compression and media flaws are
having on the amount of data that is being stored on the media.
Related Topics:
“Symantec Backup Exec Library Expansion Option” on page 1539
“About devices in the shared storage environment” on page 1551
Configuring storage devices by using the Device Configuration
Wizard
You can use the Device Configuration Wizard to configure all of your storage devices,
including creating backup-to-disk folders, installing Symantec tape device drivers, and
correcting the display of robotic library drives.
Separate wizards are available for creating backup-to-disk folders and installing tape
device drivers, but when you first install Backup Exec, it may be easier to use the Device
Configuration Wizard to configure these storage devices.
171

Configuring storage devices by using the Device Configuration Wizard
Use the Device Configuration Wizard for the following tasks:
Device Configuration Wizard tasks
You can More information
Create a backup-to-disk folder If you are new to Backup Exec, review the following topics for
information about backup-to-disk folders. While the wizard
prompts you to select some options, most of the
backup-to-disk folder settings are based on default settings.
For more information, see:
“About backup-to-disk folders and files” on page 218
“Creating a backup-to-disk folder by using the Backup-to-disk
Wizard” on page 221
“Requirements for creating a removable backup-to-disk
folder” on page 220
“Configuring advanced options for a backup-to-disk folder”
on page 225
“Setting defaults for new backup-to-disk folders” on page 226
Install Symantec device drivers Install Symantec tape device drivers by using the Symantec
Device Driver Installation Wizard.
For more information, see:
“Installing Symantec device drivers by using the Symantec
Device Driver Installation Wizard” on page 174
Configure robotic library drives Use this option to correct the display of robotic library drives.
For example, after installing Backup Exec, a stand-alone drive
may be inadvertently displayed as an unknown device in the
Devices view. If this happens, you can click the stand-alone
drive and drag it to the correct location.
If the storage devices are not displayed in the correct order,
ensure that the drive element addresses for robotic libraries
are in the right order, and that the right device drivers have
been installed.
For more information, see:
“About robotic libraries in Backup Exec” on page 206
“Enabling robotic library support” on page 208
“Configuring a robotic library” on page 208
172 Administrator’s Guide

To start the Device Configuration Wizard
1. On the navigation bar, click Devices.
Chapter 5, Managing devices
Adding devices by using the Hot-swappable Device Wizard
2. In the task pane, under Device Wizards, click Device configuration wizard.
3. Follow the on-screen prompts.
Related Topics:
“Viewing storage devices” on page 168
“Adding devices by using the Hot-swappable Device Wizard” on page 173
Adding devices by using the Hot-swappable Device Wizard
Use the Hot-swappable Device Wizard to replace or add a hot-swappable storage device
on a Backup Exec media server without having to reboot 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, including iSCSI-attached disks, tape devices, or libraries, in
the iSCSI control panel applet, add the device to the Persistent Targets list in the applet,
and then run the Hot-swappable Device Wizard. Listing the device as a Persistent Target
lets Backup Exec rediscover the device whenever the media server is restarted.
Start the Hot-swappable Wizard before you add or replace storage devices. 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 media server and stops the
Backup Exec services. You can then add or replace any storage devices. The wizard
detects the new 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 device is displayed in the Devices view, and usage statistics for the
device begin accumulating. You can add the new device to a device pool or to a cascaded
drive pool.
Any replaced storage device is displayed in the Devices view with a status of Offline.
To remove a storage device from Backup Exec, disable it and then delete it from the
Devices view.
173

Installing Symantec device drivers by using the Symantec Device Driver Installation Wizard
To start the Hot-swappable Device Wizard
1. On the navigation bar, click Devices.
2. In the task pane, under Device Wizards, click Hot-swappable device wizard.
3. Follow the on-screen prompts.
Installing Symantec device drivers by using the Symantec
Device Driver Installation Wizard
Use the Symantec Device Driver Installation Wizard to install Symantec device drivers.
The Symantec Device Driver Installation Wizard can be run from the Backup Exec
Device Configuration Wizard, or from tapeinst.exe, which is located in the Backup Exec
for Windows Servers installation directory. Tapeinst.exe is updated by the Device Driver
Installer package that is available as a download from the Symantec support Web site at:
http://support.veritas.com/menu_ddProduct_BEWNT_view_DOWNLOAD.htm
To run the Symantec Device Driver Installation Wizard from tapeinst.exe
1. From the Backup Exec for Windows Servers installation directory, double-click
tapeinst.exe.
The default location is C:\Program Files\Symantec\Backup Exec.
2. Follow the on-screen prompts.
On the Choosing tape drivers screen, click More Information to read current details
about each choice.
On the Scanning hardware screen, click Details to view changes that will be made
based on your selections on the Choosing tape drivers screen.
Related Topics:
“Configuring storage devices by using the Device Configuration Wizard” on page 171
174 Administrator’s Guide

Pausing and resuming devices
Chapter 5, Managing devices
Pausing and resuming devices
You can pause and resume the media server and all of its storage devices, including
robotic library drives, stand-alone drives, and backup-to-disk folders.
You can pause a media server to prevent scheduled and new jobs from running on that
server while maintenance activities, such as replacing a tape device, are being
performed. Active jobs will not be affected if they started before the server was paused.
To pause or resume the media server
1. On the navigation bar, click Devices.
2. Click the server icon.
3. Under Device Tasks in the task pane, select Paused.
A check mark appears next to the Paused option if the media server is currently
paused.
If the media server was not already paused, it is now paused. If the media server was
already paused, it is now resumed.
To pause or resume a robotic library or device
1. On the navigation bar, click Devices.
2. Click the robotic library device or stand-alone drive.
3. Under Device Tasks in the task pane, select Paused.
A check mark appears next to the Paused option if the device is currently paused.
If the device was not already paused, it is now paused. If the device was already
paused, it is now resumed.
Related Topics:
“Pausing and resuming a backup-to-disk folder” on page 232
175

Renaming a robotic library or device
Renaming a robotic library or device
You can rename the media server’s storage devices as well as any attached robotic
libraries.
To rename a robotic library or device
1. On the navigation bar, click Devices.
2. Click the robotic library or device that you want to rename.
3. Under General Tasks in the task pane, click Rename.
4. On the Rename dialog box, type the new name, and then click OK.
Related Topics:
“Renaming a backup-to-disk folder” on page 229
“Renaming a device pool” on page 182
“Renaming a cascaded drive pool” on page 187
About device pools
A device pool is a group of devices that enables load-balancing of Backup Exec jobs sent
to the same device pool for processing. The jobs are spread among the devices in a pool
so that the workload is shared among the devices.
When you submit a backup job to a device pool, the job is automatically sent to the first
available device in that device pool. As other jobs are created and started, they can run
concurrently on other devices in the device pool. By dynamically allocating devices as
jobs are submitted, Backup Exec processes jobs quickly and efficiently.
Devices can belong to more than one device pool, unless a device is in a cascaded drive
pool. Device pools can contain different types of devices, including specific devices in
multi-device robotic libraries.
You can assign priorities to devices in a device pool so that a specific device is used
before other devices in the device pool. The priority assigned to a device in one device
pool is unrelated to that device’s priority in any other device pool. For example, if Device
1 is placed in both Device Pool A and Device Pool B, you can assign different priorities to
it in each device pool. Device 1 can have a high priority in Device Pool A and a low
priority in Device Pool B.
176 Administrator’s Guide

Chapter 5, Managing devices
About device pools
You can send backup jobs to specific devices in a device pool. However, if that device is
busy, the job must wait until the device becomes available. When a specific device is
assigned, the job cannot be automatically routed to the next available device.
Device pools also provide automatic job rescheduling. For example, if a device pool
contains four stand-alone drives and the first device fails because of a hardware error,
the job that was running on the failed device is resubmitted and placed on hold, and the
other jobs are automatically routed to the working devices in the device pool.
In a device pool, Backup Exec selects the oldest recyclable media in all of the devices in
the device pool to use first. If more than one media that meets the requirements is
found, Backup Exec then searches the devices in a device pool according to device
priority and uses the oldest recyclable media in the device that has the highest priority.
All Devices (Server Name) is the default device pool, created when Backup Exec is
installed. All devices recognized by Backup Exec at startup are automatically assigned to
All Devices (Server Name). You can create other device pools to meet your particular
requirements, and assign and reassign devices to these pools. For example, you may
want to separate high-performance devices from lower performance devices in a
separate device pool in order to send high-priority jobs to the fast device pool for
quicker completion.
Related Topics:
“About cascaded drive pools” on page 183
Creating device pools
Device pools can consist of stand-alone drives, drives in single or multiple drive robotic
libraries, backup-to-disk folders, and removable backup-to-disk folders.
Tape drives that are in a cascaded drive pool are not available to be placed in another
device pool unless they are deleted from the cascaded drive pool first.
To create a device pool
1. On the navigation bar, click Devices.
2. Click Device Pools.
3. Under Device Pool Tasks in the task pane, select New device pool.
4. Select the appropriate options as follows, and then click OK:
Device pool name Type the name of the new device pool that you want to create.
177

Adding devices to a device pool
Description Type a description of the new device pool.
Device type Select a device type from the drop-down list to filter the list of
devices available for the new device pool. Only devices of this type
are displayed for selection.
Device sub-type: If device sub-types are available, you can select a subtype to
increase the filter on the list of devices available for the new device
pool. Only devices of this type and sub-type are displayed for
selection.
Select the devices to be
included in this device
pool
Related Topics:
“About cascaded drive pools” on page 183
“Creating a cascaded drive pool” on page 183
Adding devices to a device pool
You can add a device to an existing device pool, unless it is a tape drive in a cascaded
drive pool. Tape drives that are in a cascaded drive pool will be automatically deleted
from the cascaded drive pool if they are placed in another device pool.
To add a device to a device pool
1. On the navigation bar, click Devices.
2. Select the device pool.
Select the devices that you want to include in the new device pool.
3. Under Device Pool Tasks in the task pane, select Add device.
4. Select the appropriate options as follows, and then click OK:
Device pool name Name of the device pool to which you want to add devices.
Description Description of the device pool.
178 Administrator’s Guide

Chapter 5, Managing devices
Adding devices to a device pool
Device type Select a device type from the drop-down list to filter the list of
devices available for the device pool. Only devices of this type are
displayed for selection.
Device sub-type: If device sub-types are available, you can select a subtype to
increase the filter on the list of devices available for the device
pool. Only devices of this type and sub-type are displayed for
selection.
Select the devices to be
included in this device
pool
Setting priorities for devices in a device pool
You can set a priority that determines the order in which the devices in a device pool are
used. The default priority is 10 so all devices have the same priority initially. The device
to which you assign the lowest number is the first device to be used in the device pool;
for example, a device with a priority of 1 is used before a device with a priority of 5. You
can set a priority of 1 to 99.
Note Overwrite and append periods for media take precedence over device priority.
The Priority option is only displayed when you are viewing device properties under a
device pool icon. Drives that are displayed under the Stand-alone Drives icon or the
Robotic Libraries icon do not display a Priority option because the drive may belong to
multiple device pools and have a different priority in each device pool.
To set device priority in a device pool
1. On the navigation bar, click Devices.
2. Under Device Pools, select the device pool containing the device for which you want
to set a priority.
3. Select the device.
4. Under General Tasks in the task pane, select Properties.
5. Click General.
Select the devices you want to include in the device pool.
179

Adding devices to a device pool
6. In Priority, type a number from 1 to 99, with 1 designating this device as the first
device to be used in the device pool, and then click OK.
Related Topics:
“Viewing a device’s configuration properties” on page 198
Deleting devices from a device pool
You can delete a device from a device pool. The device will still be in the Backup Exec
device database and will still be available for use in other device pools. It is not necessary
to delete devices from a device pool before you delete that pool; the devices are
automatically removed when the pool is deleted.
To delete a device from a device pool
1. On the navigation bar, click Devices.
2. Under Device Pools, select the device pool from which you want to delete a device.
3. Select the device that you want to remove from the device pool. You can select
multiple devices to remove.
Make sure you select a device under Device Pools and not under the server icon; if
you delete a device under the server icon, the device is deleted from the database,
not just from the device pool.
4. Under Device Pool Tasks in the task pane, select Remove device.
5. When prompted to remove the displayed device from the device pool, click Yes.
Deleting device pools
It is not necessary to delete devices from a device pool before you delete that pool; the
devices are automatically removed when the pool is deleted.
You cannot delete the All Devices device pool, but you can delete all of the devices in it.
If scheduled jobs are assigned to the deleted device pool, you are prompted to redirect
them to another device pool.
180 Administrator’s Guide

To delete a device pool
1. On the navigation bar, click Devices.
Chapter 5, Managing devices
Adding devices to a device pool
2. Under Device Pools, select the device pool or pools that you want to delete.
3. Under General Tasks on the task pane, select Delete.
4. When prompted, click Yes or Yes to All to delete the device pool or pools that are
displayed.
5. If scheduled jobs are assigned to the deleted device pool, you are prompted to
redirect the jobs to another device pool or stand-alone drive.
Related Topics:
“Deleting devices from a device pool” on page 180
“Retargeting a scheduled job from a deleted device pool or media set” on page 181
Retargeting a scheduled job from a deleted device pool or media
set
If a device pool or media set is deleted, and scheduled jobs are assigned to that device
pool or media set, you are prompted to redirect the jobs to another device pool or
stand-alone drive, or to another media set.
To retarget a scheduled job from a deleted device pool or media set
1. When prompted to retarget the jobs, click Yes.
The job to be retargeted is displayed in the Retarget Job dialog box. If there are
scheduled jobs assigned to the deleted device pool or media set, you are prompted to
redirect the jobs to another device or device pool, or media set.
2. In the Destination field, click the to see available choices, and then
select the new device pool, stand-alone drive, or media set to which you want to
retarget the scheduled jobs.
3. Click Yes or Yes to All to retarget the job or jobs that are displayed to the new
destination.
Note If you choose not to retarget a job, the job will fail. To target the job to another
destination later, you must manually edit the job.
181

Adding devices to a device pool
Renaming a device pool
The default All Devices device pool cannot be renamed, but you can rename any
user-created device pool using either the Rename option or the device pool’s Properties
dialog box.
To rename a device pool
1. On the navigation bar, click Devices.
2. Under Device Pools, select the device pool you want to rename.
3. Under General Tasks, select Rename.
4. On the Rename dialog box, type the new name of this device pool, and then click OK.
The device pool is listed with the new name.
Related Topics:
“Viewing device pool properties” on page 182
Viewing device pool properties
Use Properties to view properties for a device pool, or to rename the device pool.
To view properties for a device pool
1. On the navigation bar, click Devices.
2. Under Device Pools in the tree view, select the device pool.
3. Under General Tasks in the task pane, select Properties.
The Device Pool Properties dialog box provides the following information:
Name Name of the device pool. Rename the device pool by typing a new
name in this field.
Description Description of the device pool. You can enter a description or
modify the description.
Creation date Date and time that this device pool was created.
182 Administrator’s Guide

About cascaded drive pools
Chapter 5, Managing devices
About cascaded drive pools
You can cascade (link) multiple stand-alone tape drives together to create one logical
drive. By cascading the tape drives, backup jobs can automatically “roll” to the media in
the next tape drive when the media is filled. Although multiple tape drives are linked to
form the cascaded drive pool, only the name of the cascaded drive pool is listed as the
destination device when a backup job is created.
Tape drives in a cascaded drive pool are not available for concurrent operations. Only
one tape drive is used at a time. The next tape drive in the cascaded drive pool is used
only when a backup job fills the current media, or when the next job requires a different
media (such as an overwrite job).
Use cascaded drive pools to run unattended backup jobs, or to make sure a large backup
job will complete without operator intervention. You may also want to use cascaded
drive pools if you want data from a job or group of jobs to reside on the same tape family.
Related Topics:
“About device pools” on page 176
Requirements for using cascaded drive pools
In order to cascade tape drives, the tape drives must be the same drive type, such as DLT
32K. To determine the drive type, look in the tape drive’s property page. For more
information, see “Viewing storage device properties” on page 195.
Caution If a tape drive that does not support hardware compression is added to a
cascaded drive pool, the hardware compression option on all other tape drives
in that pool is automatically disabled. You can enable the hardware
compression option on the other tape drives again, but the pool will then have
mixed compression, which could make restore operations difficult.
Backup-to-disk folders cannot be placed in cascaded drive pools.
Creating a cascaded drive pool
When you select drives for a cascaded drive pool, only drives of the same drive type are
displayed for selection. Any drives that you move to a cascaded drive pool are removed
from device pools that they are currently in.
Note Overwrite and append periods for media take precedence over tape drive priority.
183

About cascaded drive pools
To create a cascaded drive pool
1. On the navigation bar, click Devices.
2. Select Cascaded Drive Pools.
3. Under Device Pool Tasks in the task pane, select New device pool.
4. Select the appropriate options as follows, and then click OK:
Drive pool name Type the name of the new cascaded drive pool that you want to
create.
Description Description of the cascaded drive pool.
Device type Select a device type from the drop-down list to filter the list of
drives available for the cascaded drive pool. Only drives of this type
are displayed for selection.
Device sub-type: If device sub-types are available, you can select a subtype to
increase the filter on the list of drives available for the cascaded
drive pool. Only drives of this type and sub-type are displayed for
selection.
Select the drives to be
included in this device
pool.
Related Topics:
“Deleting drives from a cascaded drive pool” on page 185
“Deleting a cascaded drive pool” on page 186
Adding drives to a cascaded drive pool
Select the drives that you want to include in the new cascaded
drive pool. Any drives moved to a cascaded drive pool will be
removed from any device pools they are currently in.
You can add a drive to an existing cascaded drive pool provided the drive is of the same
type as the drives already in the pool and provided that the drive is not in another
cascaded drive pool. Drives that are part of a non-cascaded drive pool will be removed
from the other pool when added to a cascaded drive pool.
184 Administrator’s Guide

To add a drive to a cascaded drive pool
1. On the navigation bar, click Devices.
2. Select the cascaded drive pool to which you want to add a drive.
3. Under Device Pool Tasks in the task pane, select Add device.
4. Select the appropriate options as follows, and then click OK:
Deleting drives from a cascaded drive pool
Chapter 5, Managing devices
About cascaded drive pools
Device pool name Name of the cascaded drive pool to which you want to add drives.
Description Description of the cascaded drive pool.
Device type Only stand-alone drives are displayed for selection for a cascaded
drive pool.
Device sub-type: Select a sub-type, or media type, to increase the filter on the list of
drives available for the cascaded drive pool. Only drives that use
this media type are displayed for selection.
Select the devices to be
included in this device
pool
Use Delete to remove a drive from a cascaded drive pool, or drag the drive you want to
delete from the cascaded drive pool to the Stand-alone Drives icon. If the move is
allowed, the mouse arrow icon displays a plus sign (+) in a box. The drive will still be in
the Backup Exec device database and will still be available for use in other device pools.
It is not necessary to delete drives from a cascaded drive pool before you delete that
pool; the drives are automatically removed when the cascaded drive pool is deleted.
The following instructions describe the menu-driven method.
To delete a drive from a cascaded drive pool
1. On the navigation bar, click Devices.
Select the drives you want to include in the drive pool.
2. Select the cascaded drive pool from which you want to delete a drive.
3. Select the drive you want to delete from the cascaded drive pool.
185

About cascaded drive pools
4. Under Device Pool Tasks in the task pane, select Remove device.
5. When prompted, click Yes to delete the drive that is displayed.
Related Topics:
“Deleting a cascaded drive pool” on page 186
“Erasing media” on page 240
Deleting a cascaded drive pool
It is not necessary to delete drives from a cascaded drive pool before you delete that
pool; the drives are automatically removed from the pool when the pool is deleted.
If scheduled jobs are assigned to the deleted cascaded drive pool, you are prompted to
redirect them to another device or drive pool.
To delete a cascaded drive pool
1. On the navigation bar, click Devices.
2. Under Cascaded Drive Pools, select the drive pool or pools that you want to delete.
3. Under General Tasks, click Delete.
4. When prompted, click Yes or Yes to All to delete the cascaded drive pool or pools
that are displayed.
5. If scheduled jobs are assigned to the deleted cascaded drive pool, you are prompted
to redirect the jobs to another device pool or stand-alone drive.
6. If scheduled jobs are assigned to the deleted cascaded drive pool, you are prompted
to redirect the jobs to another destination.
Related Topics:
“Retargeting a scheduled job from a deleted device pool or media set” on page 181
186 Administrator’s Guide

Renaming a cascaded drive pool
Chapter 5, Managing devices
About cascaded drive pools
You can rename a cascaded drive pool using either the Rename option or by typing a
new name on the cascaded drive pool’s Properties dialog box.
To rename a cascaded drive pool
1. On the navigation bar, click Devices.
2. Under Cascaded Drive Pools, select the drive pool you want to rename.
3. Under General Tasks in the task pane, select Rename.
4. On the Rename dialog box, type the new name for the cascaded drive pool, and then
click OK.
Viewing properties of a cascaded drive pool
Use Properties to view properties for a cascaded drive pool, or to rename the cascaded
drive pool.
To view properties of a cascaded drive pool
1. On the navigation bar, click Devices.
2. Under Cascaded Drive Pools, select the cascaded drive pool for which you want to
view properties.
3. Under General Tasks in the task pane, select Properties.
The Cascaded Drive Pool Properties dialog box provides the following information:
Name Name of the cascaded drive pool. Rename the drive pool by
typing a new name in this field.
Description Description of the cascaded drive pool. You can enter a
description or modify the current description.
Creation date Date and time that this cascaded drive pool was created.
187

Running diagnostics on a media server
Running diagnostics on a media server
You can run a Backup Exec diagnostic utility on the media server. This utility creates a
file (bediag_(machine_name).txt) that includes useful configuration information for the
server. For more information, see “Generating a diagnostic file for troubleshooting” on
page 679. Technical support can use the results of the diagnostics to troubleshoot
problems.
You can also run diagnostics for a remote server (see “Running Bediag on a remote
computer” on page 681).
To run server diagnostics
1. On the navigation bar, click Devices.
2. Select the media server from the tree view.
3. Under General Tasks in the task pane, select Properties, and then click the General
tab.
4. Click Run Diagnostics.
5. On the Backup Exec Diagnostics dialog box, make sure the correct server name is
entered, and then click Run Diagnostics.
A file (bediag(machine_name).txt) is created that includes useful configuration
information for the server such as:
■ Account groups, account privileges, and environment settings.
■ Backup Exec Software version and registry information, Backup Exec Agent
listing, Windows version information, SCSI hardware configuration, SQL Server
information, Driver services information, and Windows Services information.
■ File Server information, supported shared directories, and Windows sockets
information.
6. After viewing the file, click Close.
Viewing media server properties
View media server properties for information about your media server, including
Backup Exec version information, operating system information, installed licenses
information, etc. Most of the details presented in the properties tabbed pages are for
information only. However, from the General tab, you can run Diagnostics, a Backup
Exec diagnostic utility, and from the Statistics tab, you can view jobs and alerts.
188 Administrator’s Guide

Chapter 5, Managing devices
Viewing media server properties
If the Central Admin Server Option is installed, two additional tabs can be viewed. For
information on the Settings tab, see “Setting defaults for managed media servers” on
page 805. For information on the Advanced tab, see “Changing the catalog location” on
page 816.
To view media server properties
1. On the navigation bar, click Devices.
2. Select the media server from the tree view.
3. Under General Tasks in the task pane, select Properties, and then click a tab.
Related Topics:
“Viewing a media server’s general properties” on page 189
“Viewing a media server’s system properties” on page 191
“Viewing a media server’s active job and alert statistics” on page 192
“Viewing a media server’s installed licenses” on page 193
“Viewing the location of Backup Exec databases” on page 193
Viewing a media server’s general properties
On the media server’s general properties, you can view information about what type of
media server this is, the server status, the version of Backup Exec that is running, and
time and date information.
To view a media server’s general properties
1. On the navigation bar, click Devices.
2. Select the media server from the tree view.
3. Under General Tasks in the task pane, select Properties, and then click the General
tab.
The Media Server Properties General tab provides the following information:
Name The name of the media server.
189

Viewing media server properties
Communication status If the Central Admin Server Option is installed, displays the status
of communications between the managed media server and the
central administration server.
See “Administering managed media servers” on page 832.
Media server status The status of the media server:
◆ Online - All services are running.
◆ Pause - The server has been paused. You can pause a media
server to prevent scheduled and new jobs from running on that
server while maintenance activities, such as replacing a tape
device, are being performed. Active jobs will not be affected if
they started before the server was paused.
◆ Unavailable - The Backup Exec services are not responding.
Depending on the thresholds that were set, active jobs will
become stalled, then failed, and then will be recovered.
See “Setting thresholds to recover jobs” on page 480.
◆ Offline - The media server is not online. Services have been
stopped.
Note If the Central Admin Server Option is installed, additional
statuses are displayed.
See “Administering managed media servers” on page 832
Media server type If this is a single installation of Backup Exec, the media server type
displayed is a stand-alone media server.
If the Central Admin Server Option is installed, the media server
type displayed is either a managed media server or a central
administration server.
See “Administering managed media servers” on page 832.
Description Enter a description of the server.
Version Backup Exec version and revision information.
License key The license key under which Backup Exec is installed. “Evaluation
Edition” is displayed if a license key was not provided during
Backup Exec’s installation.
Time zone Displays the time zone set for this media server.
Start date and time Date and time Backup Exec was initially installed and launched on
this media server.
Current date and time Current date and time.
190 Administrator’s Guide

Viewing a media server’s system properties
Chapter 5, Managing devices
Viewing media server properties
Run Diagnostics Click to run the Diagnostics utility to a file.
See “Running diagnostics on a media server” on page 188.
On the media server’s system properties, you can view information about the operating
system, the processor, and memory statistics.
To view a media server’s system properties
1. On the navigation bar, click Devices.
2. Select the media server from the tree view.
3. Under General Tasks in the task pane, select Properties, and then click the System
tab.
The Media Server Properties System tab provides the following information:
Type Operating system currently running on this media server.
Version Version of the operating system.
Build Build number of the operating system.
Type Processor installed in this media server.
Total processors Number of processors on this media server.
Physical Amount of hardware RAM installed in the media server.
Virtual remaining Amount of virtual memory remaining on the media server.
Page size Size of a single virtual memory page.
Page file Size of the virtual memory paging file.
191

Viewing media server properties
Viewing a media server’s active job and alert statistics
On the media server’s statistics properties, you can view the number of devices, jobs,
and alerts for this media server. You can also click links to immediately view active jobs
and alerts.
To view a media server’s active job and alert statistics
1. On the navigation bar, click Devices.
2. Select the media server from the tree view.
3. Under General Tasks in the task pane, select Properties, and then click the
Statistics tab.
The Media Server Properties Statistics tab provides the following information:
Number of devices Number of storage devices connected to this media server. In
systems with multi-drive robotic libraries attached, each drive in
the robotic library represents a separate device.
Number of active jobs Number of jobs currently in progress on this media server.
View jobs... Click this to view all current jobs and job histories for this media
server. The Job Monitor view on the navigation bar is displayed,
and the filters for current jobs and job histories are reset to display
jobs for this media server.
Number of error alerts Number of active error alerts for this media server.
Number of warning
alerts
Number of
informational alerts
Number of active warning alerts for this media server.
Number of active information alerts for this media server.
View alerts... Click this to view all active alerts for this media server. The Alerts
view on the navigation bar is displayed, and the filter is reset to
display active alerts for this media server.
192 Administrator’s Guide

Viewing a media server’s installed licenses
Chapter 5, Managing devices
Viewing media server properties
On the media server’s license information properties, you can view information about
additional options that are licensed and installed on the media server.
To view a media server’s installed licenses
1. On the navigation bar, click Devices.
2. Select the media server from the tree view.
3. Under General Tasks in the task pane, select Properties, and then click the License
Information tab.
The Media Server Properties License Information tab provides the following
information:
Option Name of the Backup Exec options.
Licensed Displays Yes if the option is licensed on the media server, and No if
the option is not licensed.
Installed Displays Yes if the option is installed on the media server, and No if
the option is not installed.
If the option is installed, it may still require some additional
configuration. Refer to the Symantec Backup Exec for Windows
Servers Administrator’s Guide, or click Help.
Viewing the location of Backup Exec databases
On the media server’s advanced properties, you can view information about the location
of the databases for Backup Exec, which include the Backup Exec database, the device
and media database (ADAMM), and the catalog database.
During Backup Exec installation, if you chose the default option to create a local Backup
Exec SQL Express instance on which to store the Backup Exec database, the databases
are all located on the local media server. If you chose another instance on the network
on which to store the Backup Exec database, then the databases are all located on the
Microsoft SQL Server that contains that instance.
In a SAN SSO configuration, on the secondary servers, the database locations are the
same as the database locations displayed on the primary server.
193

Viewing media server properties
In a Central Admin Server Option configuration, if the device and media database
location is on the central administration server, that information is displayed (see
“Setting defaults for managed media servers” on page 805).
Note Advanced properties are displayed only for the media server that the Backup Exec
Administration Console is connected to.
To view the location of Backup Exec databases
1. On the navigation bar, click Devices.
2. Select the media server from the tree view.
3. Under General Tasks in the task pane, select Properties, and then click the
Advanced tab.
The Media Server Properties Advanced tab provides the following information:
Server Name of the Microsoft SQL Server that contains the Backup Exec
database.
Instance Name of the instance that the Backup Exec database is installed on.
Name MS SQL database name of the Backup Exec database.
Path The path of the Backup Exec database.
Server Name of the Microsoft SQL Server that contains the Advanced
Device and Media Management (ADAMM) database.
Instance Name of the instance that the Advanced Device and Media
Management (ADAMM) database is installed on.
Name MS SQL database name for the Advanced Device and Media
Management (ADAMM) database.
Path The path of the Advanced Device and Media Management
(ADAMM) database.
Server Name of the Microsoft SQL Server that contains the Backup Exec
catalog database.
194 Administrator’s Guide

Chapter 5, Managing devices
Viewing storage device properties
Instance Database instance that contains the catalog database.
Name MS SQL database name for the Backup Exec catalog database.
Path The path of the Backup Exec catalog database.
Viewing storage device properties
Backup Exec provides details on each storage device connected to a media server and the
first robotic library drive.
Note Support for a single robotic library drive for use with Backup Exec is provided
when you purchase Backup Exec. To enable support for additional robotic library
drives, you must purchase the Library Expansion Option.
Most of the details presented in the device properties tabbed pages are for information
only.
To view a storage device’s properties
1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a
robotic library, click Robotic Libraries.
3. Select the device for which you want to view properties.
4. Under General Tasks in the task pane, select Properties.
5. Click any of the tabs, and review the information.
■ “Viewing a device’s general properties” on page 196
■ “Viewing a device’s configuration properties” on page 198
■ “Viewing a device’s SCSI information” on page 201
■ “Viewing a device’s statistics” on page 202
■ “Viewing a device’s cleaning properties” on page 203
■ “Viewing and specifying types of media for a device” on page 205
195

Viewing storage device properties
Viewing a device’s general properties
The Device Properties General tab provides information about a device. Most of this
information is for viewing only; however, you can rename your device from this tabbed
page by typing the new name in the Name field.
To view a device’s general properties
1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a
robotic library, click Robotic Libraries.
3. Select the device for which you want to view properties.
4. Under General Tasks in the task pane, select Properties, and then on the Drive
Properties dialog box, click General.
The General tab for device properties provides the following information:
Name Name of the device. You can also rename the device by typing a
new name in this field.
196 Administrator’s Guide

Chapter 5, Managing devices
Viewing storage device properties
Status ◆ Pause. Select this check box to pause the device, and then
click OK.
◆ Enable. Select this check box in order for Backup Exec to use
this device. Clear this check box to disable the device, and
allow it to be available for other applications. If the box is
clear, the device is disabled, and cannot be used by Backup
Exec. After changing the option, click OK.
◆ Online. If the device is online, the check box appears
dimmed, with a check mark. If the device is offline, the check
box is available, with no check mark. To bring the device
online, check Online. No operations are allowed on the
device until it is online again.
The device is displayed as offline if:
◆ The device was turned off after Backup Exec was started.
◆ The device was being used by another application (such as a
Windows backup utility) when Backup Exec was started.
◆ The device is removed from the computer.
◆ A tape drive failure occurred.
◆ A tape is stuck in the drive.
◆ The firmware of the device was updated; Backup Exec will
behave as if the device with its old name or identity no longer
exists.
To bring the device online, try the following:
◆ Check to make sure the device has power and that cables are
properly attached. Turn the device on and reboot the server,
or stop and restart the Backup Exec services.
◆ Stop the utility that is using the device, and then reboot the
server, or stop and restart the Backup Exec services.
To restart the Backup Exec services:
For Windows 2000, Windows XP, and Windows Server 2003,
go to Computer Management> System
Tools>Services>Applications.
◆ If the device firmware has changed, delete the device and
restart Backup Exec services. After the device appears with
its new firmware identity, retarget all jobs that were using
the old device name to the new device name.
Vendor Name of the vendor of the drive.
Product ID Product ID from the SCSI Inquiry string.
Firmware Version of the firmware used in the device.
197

Viewing storage device properties
Drive type Media and memory specifications of the device.
Media type If the device is a stand-alone drive, the media type used in this
drive type is displayed.
Date in service Date this device was first detected by this installation of Backup
Exec.
Serial number Serial number of the drive.
Related Topics:
“Viewing storage device properties” on page 195
“Renaming a backup-to-disk file” on page 232
Viewing a device’s configuration properties
The Drive Properties Configuration tab lets you:
■ Enable or disable hardware compression (if compression is supported by the drive).
■ Change the preferred block size, buffer size, buffer count, and high water count.
Caution Preferred Configuration settings are used to tune the performance of backup
and restore operations.
Changing Preferred Configuration settings is not generally recommended and
may have a negative effect on your backup and system performance. Any
changes should be thoroughly tested to make sure system performance does
not deteriorate before being put into general use.
To view a device’s configuration properties
1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a
robotic library, click Robotic Libraries.
3. Select the device for which you want to view properties.
4. Under General Tasks in the task pane, select Properties, and then on the Drive
Properties dialog box, click Configuration.
198 Administrator’s Guide

Chapter 5, Managing devices
Viewing storage device properties
The Configuration tab for drive properties provides the following information:
Enable compression If this option is available, this device is capable of supporting
hardware compression.
Select this check box to enable hardware compression.
If a job is configured to use hardware compression, but is run on
a device on which hardware compression is disabled (even
though it is supported), hardware compression is considered
unavailable and is not used.
If a device that does not support hardware compression is added
to a cascaded drive pool, the hardware compression option on all
other drives in that pool is automatically disabled. You can
enable the hardware compression option on the other drives
again, but the pool will then have mixed compression, and could
make restore operations difficult.
Block size (per device) The default is the preferred size of the blocks of data written to
new media in this device.
You can change the block size by selecting another size from the
scroll list, and then clicking OK.
Some devices (for example, DLT devices) provide better
performance when larger block sizes are used. The preferred
block size can range from 512 bytes to 64 kilobytes.
Backup Exec does not ensure that the requested block size is in
fact supported by that device. You should check the device
specifications to make sure that the block size is supported. If
the device does not support a block size, it will default to its
standard block size.
If the device does not support block size configuration, this
option is unavailable.
Buffer size (per device) The default is the preferred amount of data sent to the device on
each read or write request. The buffer size must be an even
multiple of the block size.
You can change the buffer size by selecting another size from
the scroll list, and then clicking OK. Depending on the amount
of memory in your system, increasing this value may improve
device performance. Each type of device requires a different
buffer size to achieve maximum throughput.
199

Viewing storage device properties
Buffer count The default is the preferred number of buffers allocated for this
device.
You can change the buffer count by selecting another count
from the scroll list, and then clicking OK.
Depending on the amount of memory in your system, increasing
this value may improve device performance. Each type of device
requires a different number of buffers to achieve maximum
throughput.
If you change the buffer count, you may need to adjust the high
water count accordingly.
High water count The default is the preferred number of buffers to be filled before
data is first sent to the device, and any time after that if the
device underruns.
You can change the high water count by selecting another count
from the scroll list, and then clicking OK.
The high water count cannot exceed the buffer count. A value of
0 disables the use of high water logic; that is, each buffer is sent
to the device as it is filled.
The default setting provides satisfactory performance in most
instances; in some configurations, throughput performance may
be increased when other values are specified in this field. If you
increase or decrease the buffer count, the high water count
should be adjusted accordingly. If a device has a high water
count default of 0, it should be left at 0.
Default Settings Click this button to return all the Preferred Configuration
settings to their defaults, and then click OK.
Read single block mode Select this check box to have this device read only one block of
data at a time. If this check box is selected, the device will read a
single block of data at a time, regardless of the size of the buffer
block.
Symantec recommends selecting this option if the device is a
shared storage device.
Write single block mode Select this check box to have this device write only one block of
data at a time. Selecting this check box provides greater control
over the handling of data write errors.
Symantec recommends selecting this option if the device is a
shared storage device.
200 Administrator’s Guide

Related Topics:
“Viewing storage device properties” on page 195
Viewing a device’s SCSI information
Chapter 5, Managing devices
Read SCSI pass-through
mode
Write SCSI pass-through
mode
Viewing storage device properties
The SCSI Information tab provides information about the Small Computer System
Interface (SCSI).
To view a device’s SCSI information
1. On the navigation bar, click Devices.
Select this check box to have this device read data without going
through a Microsoft tape device API. Selecting this check box
allows the data to pass directly through the device and allows
more detailed information if device errors occur.
Symantec recommends selecting this option if the device is a
shared storage device.
Select this check box to have this device write data without
going through the Microsoft tape device API. Selecting this
check box allows data to pass directly through the device driver
and allows more detailed information if device errors occur.
Symantec recommends selecting this option if the device is a
shared storage device.
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a
robotic library, click Robotic Libraries.
3. Select the device for which you want to view properties.
4. Under General Tasks in the task pane, select Properties, and then on the Drive
Properties dialog box, click SCSI Information.
The Device Properties SCSI Information tab provides the following information:
Inquiry Device information read from the device firmware.
Port Identifying number of the port on the server to which the device
is attached.
Bus Identifying number of the bus to which the device is attached.
201

Viewing storage device properties
Target ID Unique SCSI ID number (physical unit number).
LUN Logical Unit Number of the device.
Related Topics:
“Viewing storage device properties” on page 195
Viewing a device’s statistics
The Device Properties Statistics tab provides the date the device was last mounted,
device totals such as the total number of bytes written and read, and device errors. Error
rates are affected by media, head cleaning, and head wear.
The documentation included with your device should list the acceptable limits for hard
and soft errors; if not, check with the hardware manufacturer.
To view a device’s statistics properties
1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a
robotic library, click Robotic Libraries.
3. Select the device for which you want to view properties.
4. Under General Tasks in the task pane, select Properties, and then on the Drive
Properties dialog box, click Statistics.
The Statistics tab provides the following information:
Last mount date Last date that media was mounted by this device.
Total bytes written Number of bytes that have been written by this device.
Total bytes read Number of bytes that have been read by this device.
Total mounts Number of times media has been mounted by this device.
Total seeks Total number of seek operations (performed when a specific
piece of information is being located) that have been performed
by this device.
202 Administrator’s Guide

Related Topics:
“Viewing storage device properties” on page 195
Viewing a device’s cleaning properties
Chapter 5, Managing devices
Viewing storage device properties
Total hours in use Total number of hours that this device has been in use
(performing read, write, mount, and seek operations).
Seek errors Number of errors encountered while trying to locate data.
Soft read errors Number of recoverable read errors encountered. If you receive
soft errors, it may indicate the beginning of a problem. If you
receive excessive errors for your environment, check the device
and perform maintenance on it, and check the media for
damage.
Hard read errors Number of unrecoverable read errors encountered. If you
receive hard errors, check the device and perform maintenance
on it, and check the media for damage.
Soft write errors Number of recoverable write errors encountered. If you receive
soft errors, it may indicate the beginning of a problem. If you
receive excessive errors for your environment, check the device
and perform maintenance on it, and check the media for
damage.
Hard write errors Number of unrecoverable write errors encountered. If you
receive hard errors, check the device and perform maintenance
on it, and check the media for damage.
The Cleaning tab on the device properties provides statistics on totals and errors since
the last cleaning. The documentation included with your device should list the
acceptable limits for hard and soft errors; if not, check with the hardware manufacturer.
For robotic library drives, the statistics on the Cleaning tab are automatically updated
when a cleaning job successfully completes. (Cleaning jobs can only be created for a
robotic library drive.) If you want to maintain accurate cleaning statistics for your
stand-alone drives, click Reset Cleaning Statistics after the drive has been manually
cleaned.
203

Viewing storage device properties
To view a device’s cleaning properties
1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a
robotic library, click Robotic Libraries.
3. Select the device for which you want to view properties.
4. Under General Tasks in the task pane, select Properties, and then on the Drive
Properties dialog box, click Cleaning.
The Cleaning tab provides the following information:
Last cleaning date Last date a cleaning operation was performed on the device.
Hours since last cleaning Number of hours that the device has been in use since the last
cleaning.
Reset Cleaning Statistics Click this to reset all cleaning statistics to zero (stand-alone
drives only).
Bytes written Number of bytes that have been written by this device since the
last cleaning.
Bytes read Number of bytes that have been read by this device since the last
cleaning.
Total mounts Number of times media has been mounted by this device since
the last cleaning.
Total seeks Total number of seek operations (performed when a specific
piece of information is being located) that have been performed
by this device since the last cleaning.
Hours in use Total number of hours that this device has been in use
(performing read, write, mount, and seek operations) since the
last cleaning.
Seek errors Number of errors encountered since the last cleaning while
trying to locate data.
204 Administrator’s Guide

Related Topics:
“Viewing storage device properties” on page 195
Viewing and specifying types of media for a device
Chapter 5, Managing devices
Viewing storage device properties
Soft read errors Number of recoverable read errors encountered since the last
cleaning. Soft errors may indicate the beginning of a problem. If
excessive errors are reported for your environment, check the
device and perform maintenance on it, and check the media for
damage.
Hard read errors Number of unrecoverable read errors encountered since the last
cleaning. If you receive hard errors, check the device and
perform maintenance on it, and check the media for damage.
Soft write errors Number of recoverable write errors encountered since the last
cleaning. Soft errors may indicate the beginning of a problem. If
excessive errors are reported for your environment, check the
device and perform maintenance on it, and check the media for
damage.
Hard write errors Number of unrecoverable write errors encountered since the last
cleaning. If you receive hard errors, check the device and
perform maintenance on it, and check the media for damage.
The Media Types tab on the device properties displays types of media that can be placed
in the device, and lets you specify whether these media types can be used for read or
write operations.
Backup Exec’s device and media database maintains a list of media types, such as 4MM,
and then further defines the subcategories of a media type. For example, a 4MM media
type can include 4MM DDS-1 with a length of 60m and the storage capacity of 1.3 GB.
Another 4MM tape might also be a 4MM DDS-1 but have a length of 90m and a storage
capacity of 2.0 GB.
By default on the Media Types tab, all media type categories are listed, and are allowed
for use by both read and write operations. If a number appears in brackets beside the
media type, that media entry is available for use when creating a bar code rule.
You can specify that the device be limited to performing read and write operations on
specific media types. For example, if your device’s documentation states that the device
cannot perform write operations to a 4MM DDS-4 tape, you can select that media type
on this dialog box, clear the Write check box, and then click OK. This information is
205

About robotic libraries in Backup Exec
then incorporated into the device and media database, allowing Backup Exec to exclude
this media type when searching for media to be used for a job that requires writing to
the media.
To view a device’s media type properties
1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a
robotic library, click Robotic Libraries.
3. Select the device for which you want to view properties.
4. Under General Tasks in the task pane, select Properties, and then on the Drive
Properties dialog box, click Media Type.
The Media Types tab provides the following information:
Media type Type of media, such as 4mm, and any defined category of this
media type, such as CLN for cleaning tape. Media types that have
numbers appearing in brackets (for example, 4mm [6]) can be used
to define specific bar code rules.
Read Displays Yes if this media type can be read by the device;
otherwise, displays No.
Write Displays Yes if this media type can be written to by the device;
otherwise, displays No.
Related Topics:
“Viewing storage device properties” on page 195
“Bar code rules in mixed media libraries” on page 281
About robotic libraries in Backup Exec
Backup Exec’s Advanced Device and Media Management (ADAMM) feature provides
powerful functionality for robotic libraries. With typical robotic library modules, you
divide slots in the robotic library into defined groups, and then target backups to those
groups. This arrangement works as long as there is enough media in the group to
process the jobs targeted there. Problems occur when the data exceeds the available
media in the group, because operations cannot continue until overwritable media is
206 Administrator’s Guide

Chapter 5, Managing devices
About robotic libraries in Backup Exec
physically added, and you create an import media job to insert media into your robotic
library. This situation can take place even though slots in the robotic library assigned to
other groups contain usable media.
Backup Exec’s Device and Media Management feature solves the problems associated
with typical robotic library modules. Rather than targeting a backup job to a specific
group of slots with a finite number of media, Backup Exec accesses all of the media in
the robotic library and uses media that belongs to the job’s targeted media set. If the
backup job exceeds the capacity of one piece of media, Backup Exec searches all media
contained in the robotic library, finds a suitable media, and uses it for the job.
For example:
An operator has a robotic library with six slots. The operator inserts six blank tapes
and targets backup jobs to various media sets within the robotic library. Depending
on whether the backups are overwrite or append jobs, Backup Exec automatically
allocates available tapes in the robotic library. If a job exceeds the capacity of one
tape and another overwritable tape is available in the robotic library, the job will
automatically continue on that tape. When Backup Exec runs out of tapes, it
prompts the operator to add overwritable media.
In a robotic library, Backup Exec selects the oldest recyclable media in the library to use
first. If more than one media meeting the requirements is found, Backup Exec then
selects the media in the lowest-numbered slot; for example, media in slot 2 would be
selected before equivalent media in slot 4.
If a job requiring overwritable media is targeted to a robotic library and no overwritable
media is available, the job is skipped and the next job targeted to the robotic library is
queued. When overwritable media becomes available either by the addition of media to
the robotic library or by the overwrite protection period expiring for a media currently
in the robotic library, the skipped job will run.
Related Topics:
“Enabling robotic library support” on page 208
“Importing media to a robotic library” on page 249
“Configuring a robotic library” on page 208
“Symantec Backup Exec Library Expansion Option” on page 1539
207

Enabling robotic library support
Enabling robotic library support
Support for a single robotic library drive for use with Backup Exec is provided when you
purchase Backup Exec. To enable support for additional robotic library drives, you must
purchase the Library Expansion Option.
To enable robotic library support
1. On the Tools menu, click License Keys and Installation.
2. On the Welcome screen, click Next.
3. On the Program Maintenance screen, check Local Install, and then click Next.
4. In the list of install components, select Enable Robotic Library Support.
Enable Robotic Library Support provides support for a single-drive robotic library
or for the first drive in a multi-drive robotic library.
For support for each additional single-drive robotic library, or for each additional
drive in a multi-drive robotic library, you must purchase and install the Library
Expansion Option.
5. Click Next.
6. Review the installation review, and then click Install.
7. When the installation is complete, click Finish.
Configuring a robotic library
Before installing Backup Exec, make sure the SCSI addresses of the robotic library and
the storage device are configured properly.
After completing the configuration of your robotic library, you should perform an
Inventory operation to update Backup Exec’s media database.
During startup, if there is media in the storage devices in the robotic library, Backup
Exec attempts to return the media to its original magazine slot. If the media cannot be
returned to the slot, an error message appears requesting that the media be ejected from
the storage device.
208 Administrator’s Guide

To configure a robotic library
Chapter 5, Managing devices
Configuring a robotic library
1. Start the Device Configuration Wizard by clicking Tools>Wizards>Device
Configuration Wizard.
2. On the Welcome screen, click Next.
3. Review the device summary, and then click Next.
4. On the Create and Configure Backup Devices screen, click Configure robotic library
drives, and then click Next.
5. On the Configure Library Drives screen, make sure that each device in the robotic
library is properly associated with the robotic library.
If the devices are not correctly associated, try the following:
■ If a robotic library appears in the backup devices list as a stand-alone drive,
correct the association by clicking and dragging the drive over the robotic
library entry.
■ If the robotic arm is not shown, follow the procedure in “Enabling robotic library
support” on page 208.
■ If your robotic library uses a zero-based slot configuration, be sure the Slot Base
field on the Configuration tab of the robot’s Properties dialog box displays 0.
6. After completing the configuration of your robotic library, click Next, and then click
Finish to exit the wizard.
7. Run an Inventory operation to update Backup Exec’s media database. See
“Inventorying media” on page 238.
Related Topics:
“Setting up robotic library hardware” on page 1540
“Installing Backup Exec” on page 71
“Setting up cleaning jobs” on page 248
209

Configuring a robotic library
Viewing robotic library properties
Through the robotic library’s Properties dialog box, you can rename a robotic library,
enable or disable the device for Backup Exec, specify the slot base numbering, and view
information about the library.
To view robotic library properties
1. On the navigation bar, click Devices.
2. Expand the server icon in the tree view, and then click Robotic Libraries.
3. Select the robotic library.
4. Under General Tasks in the task pane, select Properties.
5. Click a tab to view information about any of the following:
■ “Viewing robotic library general properties” on page 210
■ “Viewing robotic library configuration properties” on page 212
■ “Viewing SCSI information for a robotic library” on page 213
■ “Viewing statistics for a robotic library” on page 214
6. Click OK.
Viewing robotic library general properties
While most of the information appearing on the General tab for a robotic library’s
properties dialog box is for viewing only, you can use this dialog to rename your robotic
library, and to change its status.
To view general properties of a robotic library
1. On the navigation bar, click Devices.
2. Expand the server icon in the tree view, and then click Robotic Libraries.
3. Select the robotic library.
4. Under General Tasks in the task pane, select Properties, and then on the Library
Properties dialog box, click General.
210 Administrator’s Guide

Chapter 5, Managing devices
The General tab provides the following information:
Configuring a robotic library
Name Name of the robotic library. You can rename the device by typing a
new name in this field.
Status ◆ Pause. Select this check box to pause the device, and then click
OK.
◆ Enable. Select this check box in order for Backup Exec to use
this device. Clear this check box to disable the device, and allow
it to be available for other applications. If the box is clear, the
device is disabled, and cannot be used by Backup Exec. After
changing the option, click OK.
◆ Online. If the device is online, the check box appears dimmed,
with a check mark. If the device is offline, the check box is
available, with no check mark. To bring the device online,
check Online. No operations are allowed on the device until it is
online again.
The device is displayed as offline if:
◆ The device was turned off after Backup Exec was started.
◆ The device was being used by another application (such as a
Windows backup utility) when Backup Exec was started.
◆ The device is removed from the computer.
◆ A tape drive failure occurred.
◆ A tape is stuck in the drive.
◆ The firmware of the device was updated; Backup Exec will
behave as if the device with its old name or identity no longer
exists.
To put the device online, try the following:
◆ Check to make sure the device has power and that cables are
properly attached. Turn the device on and reboot the server, or
stop and restart the Backup Exec services.
◆ Stop the utility that is using the device, and then reboot the
server, or stop and restart the Backup Exec services.
To restart the Backup Exec services:
For Windows 2000, Windows XP, and Windows Server 2003, go
to Computer Management, select System Tools, select
Services, and then select Applications.
◆ If the device firmware has changed, delete the device and
restart Backup Exec services. After the device appears with its
new firmware identity, retarget all jobs that were using the old
device name to the new device name.
Vendor Name of the vendor of the robotic library.
211

Configuring a robotic library
Product ID Product ID from the SCSI Inquiry string.
Firmware Version of the firmware used in the device.
Library type Manufacturer and model number of the robotic library.
Date in service Date this device was first detected by Backup Exec.
Serial number Serial number of the robotic library.
Related Topics:
“Viewing robotic library properties” on page 210
Viewing robotic library configuration properties
Through the Configuration tab of a robotic library’s properties dialog box, you can
enable start-up initialization for the robotic library, enable bar code rules, enable
Removable Storage, and specify slot base numbering.
To view configuration properties of a robotic library
1. On the navigation bar, click Devices.
2. Expand the server icon in the tree view, and then click Robotic Libraries.
3. Select the robotic library.
4. Under General Tasks in the task pane, select Properties, and then on the Library
Properties dialog box, click Configuration.
The Configuration tab provides the following information:
Enable startup
initialization
Select this option to have Backup Exec initialize the robotic library
when Backup Exec is started. Depending upon the robotic library,
initialization can include reading all bar code labels on media.
Enable bar code rules Select this check box to enable bar code rules.
See “Bar code rules in mixed media libraries” on page 281.
212 Administrator’s Guide

Enable Removable
Storage (RSM)
Related Topics:
“Viewing robotic library properties” on page 210
Viewing SCSI information for a robotic library
To view SCSI information properties of a robotic library
1. On the navigation bar, click Devices.
Chapter 5, Managing devices
Configuring a robotic library
2. Expand the server icon in the tree view, and then click Robotic Libraries.
3. Select the robotic library.
Select this option to allow Removable Storage to share the devices
in robotic libraries between two or more applications. If the device
is enabled in Removable Storage, Backup Exec uses Removable
Storage for device and media operations; if the device is disabled in
Removable Storage, Backup Exec controls the device directly.
See “Using Microsoft’s Removable Storage feature with Backup
Exec” on page 234.
Slot base Depicts the starting slot. Some robotic libraries have slots starting
at "0"; others start at "1". If your robotic library uses a zero-based
slot configuration you can reassign how the slots are displayed by
typing the appropriate number in the Slot Base field.
4. Under General Tasks in the task pane, select Properties, and then on the Library
Properties dialog box, click SCSI Information.
The SCSI Information tab of a robotic library’s properties dialog box displays the
following information:
Inquiry Device information that is read from the device firmware.
Port Identifying number of the port on the server to which the device is
attached.
Bus Identifying number of the bus to which the device is attached.
Target ID Unique SCSI ID number (physical unit number).
LUN Logical Unit Number of the device.
213

Configuring a robotic library
Related Topics:
“Viewing robotic library properties” on page 210
Viewing statistics for a robotic library
To view statistics properties of a robotic library
1. On the navigation bar, click Devices.
2. Expand the server icon in the tree view, and then click Robotic Libraries.
3. Select the robotic library.
4. Under General Tasks in the task pane, select Properties, and then on the Library
Properties dialog box, click Statistics.
The Statistics tab of a robotic library’s properties dialog box provides the following
information:
Slot count Number of slots in the robotic library.
Drive element count Number of drive elements contained in the robotic library.
Total mounts Number of times media has been mounted by this device.
Mount errors Number of errors encountered while mounting media in a drive.
Related Topics:
“Viewing robotic library properties” on page 210
Creating robotic library partitions
You can group one or more robotic library slots into partitions. Partitioning robotic
library slots provides more control over which media is used for backup jobs. When you
set up robotic library partitions, Backup Exec creates a device pool for each partition.
Jobs targeted to a partition device pool run on the media located in the partition’s slots.
For example, if you set up a partition that contains slots 1 and 2 and you want to run a
weekly backup only on the media in these slots, you would submit the job to the partition
device pool containing slots 1 and 2.
214 Administrator’s Guide

Chapter 5, Managing devices
Configuring a robotic library
The partition device pools appear in the Devices view under the Device Pools icon. If
the robotic library is partitioned, Backup Exec searches for the oldest recyclable media
in the targeted partition only. If more than one media meeting the requirements is
found, Backup Exec then selects the media in the lowest-numbered slot; for example,
media in slot 2 would be selected before equivalent media in slot 4.
In order to fully benefit from Backup Exec’s partition management feature, Symantec
recommends that you create a partitioning scheme that best matches the manner in
which you want to control your backups. For example, some administrators may feel
that network backups are best managed by allowing access to partitions based on users
and groups, while others may want to base their partitions on operation types (Backup,
Tape Rotation, Archive, etc.).
To create partitions
1. On the navigation bar, click Devices.
2. Expand the server icon, and then click Robotic Libraries.
3. Select the robotic library containing the slots that you want to partition.
4. Under Robotic Library Tasks in the task pane, select Configure partitions.
5. Select the robotic library slots to include in each partition by clicking the slots on
which each new partition should begin.
A partition divider that lists the range of slots included in the partition is inserted
wherever you click.
For example, if you want to create two 5-slot partitions on a robotic library with 10
slots, click Slot 1 and Slot 6. In this example, Slots 1-5 will be included in the first
partition and Slots 6-10 will be included in the second.
Partitions can include any number of robotic library slots; however, the first
partition cannot be moved or deleted when other partitions exist.
Note Depending upon the robotic library configuration, the first slot could be numbered
1 or 0. If the robotic library uses a zero-based slot configuration and you assign
the first partition to begin with slot 1, the Partition Utility will actually use slot 0
as the first slot for partition 1 and adjust the starting slot accordingly for all other
partitions.
215

Configuring a robotic library
Configure Partitions dialog box
Partition
Divider
6. While defining the partitions, use the following buttons to help make selections:
Remove Partition Remove the selected partition. The slots contained in the
partition you are removing are added to the partition preceding
it.
Move Up Move the selected partition divider up to increase the number of
slots in the partition. (The number of slots in the preceding
partition is decreased.)
Move Down Move the selected partition divider down to decrease the
number of slots in the partition. (The number of slots in the
preceding partition is increased.)
Remove All Remove all partition settings.
7. Click OK after configuring the partitions.
8. Click Yes to accept the partitions.
The partition drive pools appear under Robotic Libraries for the robotic library on
which they were created. All partition drive pools for a robotic library have the same
name and display the slot ranges for the partition in parentheses within the name.
9. After defining the partitions, you can submit jobs to those partitions’ drive pools.
The partition drive pools appear in the list of devices along with other devices
available to the media server.
216 Administrator’s Guide

Chapter 5, Managing devices
Configuring a robotic library
10. Click the target partition drive pool and run the job as you would any other Backup
Exec job.
Redefining robotic library partitions
You can reassign slots to different partitions or even create or delete partitions from a
partition drive pool by repeating the steps for creating partitions and providing different
beginning slot parameters. For example, if your current set-up is a 6-slot robotic library
with two partitions (partition 1 = slots 1-3 and partition 2 = slots 4-6), but you want to
have three partitions with slots 1-2 in partition 1, slots 3-5 in partition 2, and slot 6 in
partition 3, you would select slots 1, 3, and 6.
Because the first two partition drive pools maintain the same identity, even though the
slots have been reassigned, jobs submitted to those partition drive pools will not have to
be retargeted.
However, if you change from three partitions to two partitions, any jobs submitted to the
third partition must be retargeted since that third partition no longer exists. Also, if you
create a new partition that completely contains two or more of the old partitions, jobs
submitted to the old partition must be retargeted.
For example, if a robotic library that had been partitioned with:
Partition 1 Slots 1 - 2
Partition 2 Slots 3 - 4
Partition 3 Slots 5 - 10
is repartitioned so that:
Partition 1 Slots 1 - 4
Partition 2 Slots 5 - 6
Partition 3 Slots 7 - 10
Then any jobs targeted to the old partition 2 (slots 3-4) must be retargeted.
Note If a job is targeted to a particular robotic library drive (or a device pool that is not a
partition drive pool), the job defaults to the first partition in the robotic library.
217

About backup-to-disk folders and files
Related Topics:
“Creating robotic library partitions” on page 214
“Retargeting a scheduled job from a deleted device pool or media set” on page 181
About backup-to-disk folders and files
The backup-to-disk feature enables you to back up data to a folder on a hard disk. You can
also use it as part of a backup process where you back up data to disk first and then
transfer the data to a tape when more time is available. A backup-to-disk folder is a
virtual device that Backup Exec treats the same as any real device.
On devices that have non-removable media, create a backup-to-disk folder. On devices
that have removable media, such as a zip drive, create a removable backup-to-disk folder.
Backup-to-disk folders that are created on devices that have non-removable media
support concurrent operations from one or more media servers.
When you create a new backup-to-disk folder, Backup Exec automatically assigns the
name Backup-to-Disk Folder x, where x is a number that is incremented by one each time
a new backup-to-disk folder is created. You can rename the backup-to-disk folder at any
time. You can also set defaults for backup-to-disk folders that will apply to every new
backup-to-disk folder that is created. If you have the Central Admin Server Option
(CASO) or the SAN Shared Storage Option installed, you can share backup-to-disk folders
between computers.
When you back up to disk, Backup Exec places the data in a backup-to-disk file in the
backup-to-disk folder you specify. Backup-to-disk files are virtual media where backed up
data is stored. Backup-to-disk files are like any other type of media, so you can inventory,
catalog, erase, and restore them.
Since Backup Exec recognizes the backup-to-disk folders as devices, you can view them
by selecting Devices on the navigation bar. You can view the backup-to-disk files from
both the Devices view and the Media view.
In Windows Explorer, the backup-to-disk folders display in the path you specified when
you added the folders. The backup-to-disk files display with a .bkf file extension. Each
backup-to-disk folder also contains a file named changer.cfg and a file named folder.cfg,
which store information about the backup-to-disk files.
Note Do not delete or edit the changer.cfg or folder.cfg files.
218 Administrator’s Guide

Chapter 5, Managing devices
About backup-to-disk folders and files
A subfolder with a prefix of IMG in the name may display under a backup-to-disk folder.
Backup Exec creates this subfolder when the following conditions are met in a backup
job:
■ The option to enable the restore of individual items is selected.
■ A backup-to-disk folder is selected as the backup device.
Backup Exec handles these subfolders in the same manner as .bkf files.
Disaster recovery from virtual devices, such as backup-to-disk folders, must be done via
remote Intelligent Disaster Recovery using a media server with access to the virtual
device.
Related Topics:
“Creating a backup-to-disk folder by using the Backup-to-disk Wizard” on page 221
“Requirements for creating a backup-to-disk folder” on page 219
“Requirements for creating a removable backup-to-disk folder” on page 220
“Creating a backup-to-disk folder” on page 222
“Sharing an existing backup-to-disk folder” on page 228
“Duplicating backed up data” on page 381
“Renaming a backup-to-disk folder” on page 229
“Setting defaults for new backup-to-disk folders” on page 226
Requirements for creating a backup-to-disk folder
You can create a backup-to-disk folder in any location to which you can write a file:
■ NTFS partitions (local or remote)
The backup-to-disk folder must exist on an NTFS partition for backup jobs in which
the option to enable the restore of individual items is selected. This option is
available for Microsoft Exchange databases and storage groups, Microsoft Active
Directory, and Microsoft SharePoint content database and Team database.
■ DFS shares
■ FAT/FAT32 partitions (local or remote)
■ Veritas Volume Manager partitions
■ RAID drives with any configuration
■ NFS volumes
■ Network Attached Storage (NAS) devices
219

About backup-to-disk folders and files
If a NAS device is emulating a Windows operating system, contact the NAS
manufacturer for assistance before creating backup-to-disk folders on the NAS
device. Symantec does not certify NAS devices. If the operating system is a
proprietary operating system and not a true Windows operating system, Symantec
cannot properly troubleshoot the device.
You should create a backup-to-disk folder on a different physical disk than the disk you
want to back up. For example, if the Backup Exec Advanced Open File Option (AOFO) is
used to snap volumes during a backup, and if the destination device is a backup-to-disk
folder, the backup-to-disk folder should be on a separate volume that is not being
snapped.
Similarly, when making selections for backups that you are targeting to a
backup-to-disk folder, avoid including that folder in the selections for the job. For
example, if you create a new backup-to-disk folder in C:\Backup Folders and then select
the entire C:\ volume for backup, make sure that you exclude C:\Backup Folders from the
selection list.
Related Topics:
“Creating a backup-to-disk folder by using the Backup-to-disk Wizard” on page 221
“Creating a backup-to-disk folder” on page 222
“Configuring advanced options for a backup-to-disk folder” on page 225
“Setting defaults for new backup-to-disk folders” on page 226
Requirements for creating a removable backup-to-disk folder
A removable backup-to-disk folder:
■ Supports spanning of backup sets from one piece of media to another.
■ Does not support concurrent operations.
You should not share removable backup-to-disk folders between media servers.
You can create removable backup-to-disk folders on any device that has removable
media, provided the device appears as a drive letter and is formatted with a file system.
Devices with removable media can include:
■ CDR-RW
■ DVD-RW
■ ZIP
■ REV
■ Removable hard disk
220 Administrator’s Guide

Chapter 5, Managing devices
Creating a backup-to-disk folder by using the Backup-to-disk Wizard
Note For CDR-RW and DVD-RW, third-party software must be used to format the media
before it can be used with Backup Exec.
Related Topics:
“Creating a backup-to-disk folder by using the Backup-to-disk Wizard” on page 221
“Creating a backup-to-disk folder” on page 222
“Configuring advanced options for a backup-to-disk folder” on page 225
“Setting defaults for new backup-to-disk folders” on page 226
Creating a backup-to-disk folder by using the Backup-to-disk
Wizard
If you are new to Backup Exec or are uncertain about how to set up a backup-to-disk
folder, you can use the Backup-to-disk Wizard. The wizard will guide you through the
process of creating a backup-to-disk folder or editing an existing one. While the wizard
will prompt you to select some options, most of the settings are based on the default
settings.
To create a backup-to-disk folder by using the Backup-to-disk Wizard
1. On the navigation bar, click Devices.
2. In the task pane, under Device Wizards, click Backup-to-disk Wizard.
3. Follow the on-screen prompts.
Related Topics:
“About backup-to-disk folders and files” on page 218
“Requirements for creating a backup-to-disk folder” on page 219
“Requirements for creating a removable backup-to-disk folder” on page 220
“Creating a backup-to-disk folder” on page 222
“Configuring advanced options for a backup-to-disk folder” on page 225
“Setting defaults for new backup-to-disk folders” on page 226
221

Creating a backup-to-disk folder
Creating a backup-to-disk folder
Before you can start using the backup-to-disk feature, you must create at least one
backup-to-disk folder. To review the requirements for creating backup-to-disk folders,
see “Requirements for creating a backup-to-disk folder” on page 219 or “Requirements
for creating a removable backup-to-disk folder” on page 220.
To create a backup-to-disk folder
1. On the navigation bar, click Devices.
2. Under Backup-to-Disk Tasks in the task pane, click New folder or New removable
folder.
3. Enter or change information as appropriate:
Name Name of the backup-to-disk folder. You can type a new folder name
here.
Backup-to-disk folder names must not exceed 128 characters.
Path Enter the path where the folder is to reside. If this is a removable
backup-to-disk folder, enter a drive.
The backup-to-disk path name, which includes the backup-to-disk
folder name, must not exceed 512 characters.
Note If you do not know the exact path, click the button next to
the Path field to browse to the correct path.
Pause Check Pause to pause the device, and then click OK.
Enable Check Enable in order for Backup Exec to use this device. Clear this
check box to disable the device, and allow it to be available for
other applications. If the box is clear, the device is disabled, and
cannot be used by Backup Exec. After changing the option, click
OK.
Online If the device is online, the check box appears dimmed, with a check
mark. If the device is offline, the check box is available, with no
check mark. To bring the device online, check Online. No
operations are allowed on the device until it is online again.
222 Administrator’s Guide

Chapter 5, Managing devices
Creating a backup-to-disk folder
Priority The Priority field is only available when the backup-to-disk folder
belongs to a device pool and is selected for viewing under the
device pool icon. Backup-to-disk folder properties displayed under
the Backup-to-Disk Folders and Removable Backup-to-Disk icons
do not display the Priority field. For more information, see “Setting
priorities for devices in a device pool” on page 179.
Set a priority for a backup-to-disk folder that determines the order
in which the devices in a device pool are used. In the Priority box,
type a number from 1 to 99, with 1 designating this device as the
first device to be used in the device pool, or click the arrows to
select a value.
The default priority is 10, so all devices have the same priority
initially. The device to which you assign the lowest number is the
first device to be used in the device pool; for example, a device with
a priority of 1 is used before a device with a priority of 5.
Note Overwrite and append periods for media take precedence
over device priority.
Maximum number of
backup sets per
backup-to-disk file
Maximum size for
backup-to-disk files
Type the maximum number of backup sets to be written to each
backup-to-disk file in this folder. The maximum number can range
from 1 to 8192. The default is 100.
Fewer backup sets in a backup-to-disk file may allow the overwrite
protection period to expire sooner, and disk space to be reclaimed
faster.
Type the maximum size for each backup-to-disk file contained in
this folder, and then select either MB or GB as the unit of size. The
file size can be from 1 MB to 4096 GB. The default is 1 GB.
If you create smaller but more numerous backup-to-disk files,
performance may be slower. If large backup-to-disk files are
created, file system limitations could cause memory allocation
problems or network issues, especially if the backup-to-disk files
are stored across a network.
223

Creating a backup-to-disk folder
Allocate the maximum
size for backup-to-disk
files
Allow x concurrent jobs
for this backup-to-disk
folder
This option is not available for a removable backup-to-disk folder.
Check Allocate the maximum size for backup-to-disk files to
create the backup-to-disk file at the maximum size to reduce disk
fragmentation.
You should consider increasing the append period and the
maximum number of backup sets per backup-to-disk file. These
increased settings allow the file to be overwritable longer and
prevent leaving unused space in the file.
However, increased append periods can cause an increase in the
overall overwrite protection period since the overwrite protection
period starts at the end of the last append job. This could result in
fewer backup jobs being targeted to this backup-to-disk folder. To
avoid this, set the maximum size for backup-to-disk files to an
appropriate size.
When the backup-to-disk file is initially created at the maximum
size, the backup job may be delayed while Backup Exec creates the
file. The backup job remains in a running state until the
backup-to-disk file is created and data can be written to it.
This option is not available for a removable backup-to-disk folder.
Type the number of concurrent operations that you want to allow
to this folder. This number can range from 1 to 16.
4. Click the Advanced tab to configure settings for the amount of disk space to reserve
for the backup-to-disk folder, and to configure device settings; otherwise, click OK.
The folder appears in the Devices view under the Backup-to-Disk Folders or
Removable Backup-to-Disk Folders icon, depending on which type you created. It
also appears in Windows Explorer as a folder. You can back up data to this folder
now.
Related Topics:
“About backup-to-disk folders and files” on page 218
“Configuring advanced options for a backup-to-disk folder” on page 225
“Setting defaults for new backup-to-disk folders” on page 226
“Changing the path of a backup-to-disk folder” on page 229
224 Administrator’s Guide

Chapter 5, Managing devices
Configuring advanced options for a backup-to-disk folder
Configuring advanced options for a backup-to-disk folder
You can set a disk space reserve for a backup-to-disk folder so that job submission and
job processing to the folder are suspended when that threshold is reached. The reserved
disk space prevents disk-full errors and provides early warning when the media reaches
a specific capacity threshold. Setting this reserve prevents jobs from being submitted to
a backup-to-disk folder that does not have enough disk space to allow the job to
complete. Backup Exec can instead submit the jobs to backup-to-disk folders that do
have enough disk space.
Set options for a disk space reserve for backup-to-disk folders, preferred settings for this
device, and set a priority for this folder that determines the order in which the devices in
a device pool are used.
To configure advanced options for a backup-to-disk folder
1. On the navigation bar, click Devices.
2. Expand the icon for the computer where the backup-to-disk folder is located.
3. Select the folder that you want to view.
4. Under General Tasks in the task pane, click Properties, and then click the
Advanced tab.
5. Enter or change information as appropriate:
Disk space reserve Check Disk space reserve to prevent a job from being written to
the backup-to-disk folder when the threshold that you specify is
reached.
Enter an amount of disk space to reserve on the disk. When this
threshold is reached, Backup Exec cannot submit jobs for
processing that are targeted to this backup-to-disk folder, but jobs
that are running will finish. The backup-to-disk status displays
Low Disk Space.
You must free some disk space to allow job submission to resume.
Auto detect settings Check Auto detect settings to let Backup Exec automatically detect
the preferred settings for this device.
Uncheck Auto detect settings if this is a device for which you want
to set buffered reads or writes.
225

Configuring advanced options for a backup-to-disk folder
Buffered reads Check Buffered reads if:
Related Topics:
“About backup-to-disk folders and files” on page 218
“Setting defaults for new backup-to-disk folders” on page 226
Setting defaults for new backup-to-disk folders
You can set defaults to apply to any new backup-to-disk folders that are created.
To set defaults for a backup-to-disk folder
1. On the Tools menu, click Options.
2. On the Properties pane, under Settings, click Backup-to-Disk.
3. Set the following defaults as appropriate:
◆ You do not want Backup Exec to automatically detect settings
for this device
◆ You want this device to allow buffered reads, which is the
reading of large blocks of data.
Enabling buffered reads may provide increased performance.
Buffered writes Check Buffered writes if:
Maximum number of
backup sets per
backup-to-disk file
◆ You do not want Backup Exec to automatically detect settings
for this device
◆ You want this device to allow buffered writes, which is the
writing of large blocks of data.
Type the maximum number of backup sets to be written to each
backup-to-disk file in this folder. The maximum number can range
from 1 to 8192. The default is 100.
Fewer backup sets in a backup-to-disk file may allow the overwrite
protection period to expire sooner, and disk space to be reclaimed
faster.
226 Administrator’s Guide

Maximum size for
backup-to-disk files
Chapter 5, Managing devices
Allocate the maximum
size for backup-to-disk
files
Allow x concurrent jobs
for this backup-to-disk
folder
Configuring advanced options for a backup-to-disk folder
Type the maximum size for each backup-to-disk file contained in
this folder, and then select either MB or GB as the unit of size. The
file size can be from 1 MB to 4096 GB. The default is 1 GB.
If you create smaller but more numerous backup-to-disk files,
performance may be slower. If large backup-to-disk files are
created, file system limitations could cause memory allocation
problems or network issues, especially if the backup-to-disk files
are stored across a network.
This default will not apply to removable backup-to-disk folders.
Check Allocate the maximum size for backup-to-disk files to
create the backup-to-disk file at the maximum size to reduce disk
fragmentation.
You should consider increasing the append period and the
maximum number of backup sets per backup-to-disk file. These
increased settings allow the file to be overwritable longer and
prevent leaving unused space in the file.
However, increased append periods can cause an increase in the
overall overwrite protection period since the overwrite protection
period starts at the end of the last append job. This could result in
fewer backup jobs being targeted to this backup-to-disk folder. To
avoid this, set the maximum size for backup-to-disk files to an
appropriate size.
When the backup-to-disk file is initially created at the maximum
size, the backup job may be delayed while Backup Exec creates the
file. The backup job remains in a running state until the
backup-to-disk file is created and data can be written to it.
This default will not apply to removable backup-to-disk folders.
Type the number of concurrent operations that you want to allow
to this folder. This number can range from 1 to 16.
Disk space reserve Check Disk space reserve to prevent a job from being written to
the backup-to-disk folder when the threshold that you specify is
reached.
Enter an amount of disk space to reserve on the disk. When this
threshold is reached, Backup Exec cannot submit jobs for
processing that are targeted to this backup-to-disk folder, but jobs
that are running will finish. The backup-to-disk status displays
Low Disk Space.
You must free some disk space to allow job submission to resume.
Backup-to-disk default
folder location
Type the default path for new backup-to-disk folders.
227

Configuring advanced options for a backup-to-disk folder
4. Click OK.
Related Topics:
“About backup-to-disk folders and files” on page 218
“Requirements for creating a backup-to-disk folder” on page 219
“Configuring advanced options for a backup-to-disk folder” on page 225
Sharing an existing backup-to-disk folder
If you have the Central Admin Server Option (CASO) or the SAN Shared Storage Option
installed, you can share backup-to-disk folders between computers. A removable
backup-to-disk folder cannot be shared.
In the Devices view, shared backup-to-disk folders are listed under each computer that
has access to that backup-to-disk folder. All of the logical groupings of the
backup-to-disk folders are displayed in the Devices view, under Device Pools.
To stop sharing a backup-to-disk folder, delete it from the computer that you don’t want
to share it with.
A backup-to-disk folder that was created by a previous installation of Backup Exec
cannot be shared, and is considered unknown by Backup Exec. If Backup Exec finds an
unknown backup-to-disk folder at the specified path, you are prompted to create a new
backup-to-disk folder at that path.
To share an existing backup-to-disk folder
1. On the computer on which you want to add the folder for sharing, on the navigation
bar, click Devices.
2. In the task pane, under Backup-to-Disk Tasks, click Add Shared Folder.
3. Type or browse to the path of the shared backup-to-disk folder that you want to add
to this computer.
4. Click OK.
The shared backup-to-disk folder is displayed in the Devices view under the
Backup-to-Disk Folders node.
228 Administrator’s Guide

Renaming a backup-to-disk folder
Chapter 5, Managing devices
Renaming a backup-to-disk folder
When you use the Backup Exec Rename option to rename a backup-to-disk folder, the
name changes in Backup Exec, but not on the disk.
If you also want to change the name of the Windows folder in Windows Explorer, follow
the instructions in “Changing the path of a backup-to-disk folder” on page 229.
Backup-to-disk folder names must not exceed 128 characters. The backup-to-disk path
name, which includes the backup-to-disk folder name, must not exceed 512 characters.
To change the name of a backup-to-disk folder
1. On the navigation bar, click Devices.
2. Expand the icon for the computer where the backup-to-disk folder is located.
3. Select the backup-to-disk folder you want to rename.
4. Under General Tasks in the task pane, select Rename.
5. On the Rename dialog box, type the new backup-to-disk folder name, and then click
OK.
6. If you want to rename the Windows folder in Windows Explorer, use the Windows
Rename option.
Changing the path of a backup-to-disk folder
To change the path of a backup-to-disk folder, you must first create a new
backup-to-disk folder, and then move the backup-to-disk files from the original
backup-to-disk folder to the new backup-to-disk folder.
To change the path of a backup-to-disk folder
1. Add a new backup-to-disk folder with a name and path that is different than the
original backup-to-disk folder.
2. In Windows Explorer, copy and paste the backup-to-disk files from the original
backup-to-disk folder to the new folder.
3. On the Backup Exec navigation bar, click Devices.
229

Deleting a backup-to-disk folder
4. Right-click the new backup-to-disk folder, and then click Scan on the shortcut
menu, or select the new folder and press .
5. Click the new backup-to-disk folder and verify that the backup-to-disk files appear
in the results pane.
6. To rename the new backup-to-disk folder to match the name of the original folder,
delete the original backup-to-disk folder and then rename the new folder.
Related Topics:
“Requirements for creating a backup-to-disk folder” on page 219
“Renaming a backup-to-disk folder” on page 229
“Deleting a backup-to-disk file” on page 233
Deleting a backup-to-disk folder
When you use the Backup Exec Delete option to delete a backup-to-disk folder, the
folder is removed from Backup Exec, but the backup-to-disk folder and the files in it
remain on the disk so you can recreate them later. If you also want to delete the folder
from the disk, use the Windows Delete option. However, you cannot recreate the
backup-to-disk folder or files after you delete them from the disk.
To delete a backup-to-disk folder
1. On the navigation bar, click Devices.
2. Expand the icon for the computer where the backup-to-disk folder is located.
3. Select the backup-to-disk folder that you want to remove.
4. Under General Tasks in the task pane, select Delete.
5. Click Yes.
The backup-to-disk folder is removed from Backup Exec, but the files and the folder
still exist on the disk. You can still recreate the backup-to-disk folder at a later date
if necessary. If you do not want to delete the folder from the disk, you have
completed this procedure.
6. If you want to delete the folder from the disk, use Windows Explorer to navigate to
the folder.
230 Administrator’s Guide

Chapter 5, Managing devices
Deleting a backup-to-disk folder
Caution If you delete the folder from the disk you cannot recreate it later. You lose all
the files from the folder.
7. Right-click the folder that you want to delete, and then on the shortcut menu, click
Delete.
8. When prompted to delete the folder, click Yes.
The folder is removed from the disk. You cannot recreate the folder or the files.
Recreating a backup-to-disk folder and its contents
If you have deleted a backup-to-disk folder from Backup Exec, but have not deleted it
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 in order to recreate it. If
you deleted a backup-to-disk folder from the disk, you cannot recreate it.
To recreate a backup-to-disk folder and the files in it
1. Add a new folder to Backup Exec using the same name and path as the deleted
folder.
2. On the navigation bar, click Devices.
3. Expand the icon for the computer where the backup-to-disk folder is located.
4. Select the new folder.
5. Under Media Tasks in the task pane, select Inventory and create and run an
inventory job.
When the inventory is complete, the files display on the results pane.
Related Topics:
“Requirements for creating a backup-to-disk folder” on page 219
“Inventorying media” on page 238
231

Pausing and resuming a backup-to-disk folder
Pausing and resuming a backup-to-disk folder
When you pause a backup-to-disk folder, backup jobs do not run on it. If a backup job is
already running on a backup-to-disk folder when you pause it, the job will complete, but
any subsequent backup jobs will not run until the folder is resumed.
If a backup job fails and the backup-to-disk folder goes offline, after you correct the
problem, you can select the folder and then under Devices task in the task pane, select
Online.
To pause or resume a backup-to-disk folder
1. On the navigation bar, click Devices.
2. Expand the icon for the computer where the backup-to-disk folder is located.
3. Select the backup-to-disk folder you want to pause or resume.
If the backup-to-disk folder is currently paused, this status is displayed next to the
backup-to-disk folder name in the Devices tree view.
4. Under Device Tasks in the task pane, select Pause.
If the folder was not already paused, it is now paused. If the folder was already
paused, it is now resumed.
Renaming a backup-to-disk file
When you rename a backup-to-disk file, the name changes in Backup Exec, on the disk,
and on the media label.
To rename a backup-to-disk file
1. On the navigation bar, click Devices.
2. Expand the icon for the computer where the backup-to-disk folder is located.
3. Select the folder that contains the file you want to rename.
4. On the results pane, select the file you want to rename.
5. Under General Tasks in the task pane, select Rename.
6. Type a new name for the file, and then click OK.
232 Administrator’s Guide

Deleting a backup-to-disk file
Chapter 5, Managing devices
Pausing and resuming a backup-to-disk folder
You must move backup-to-disk files to the Retired Media set before you can delete
them. When you delete a backup-to-disk file from the Media tab in Backup Exec, it is
deleted from Backup Exec but the Windows folder and files still exist in Windows
Explorer. You can recreate the deleted backup-to-disk files if you have not used
Windows Explorer to delete them from the disk.
To delete a backup-to-disk file
1. On the navigation bar, click Media.
2. Click the media set that contains the backup-to-disk file.
3. Use the Windows drag-and-drop feature to move the backup-to-disk file into the
Retired Media set.
4. On the results pane, select the backup-to-disk file you want to delete.
5. Under General Tasks in the task pane, select Delete.
6. When prompted to delete the backup-to-disk file, click Yes, or if you selected
multiple backup-to-disk files, click Yes to All.
The backup-to-disk file is deleted from Backup Exec, but not from the disk. To delete
the backup-to-disk file from the disk, continue to step 7. If you do not want to delete
the backup-to-disk file from the disk, you have completed this procedure.
Caution If you perform step 7 to delete the backup-to-disk file from the disk, you can
no longer restore the deleted file.
7. Using Windows Explorer, navigate to the location where the backup-to-disk file is
stored.
8. Right-click the backup-to-disk file.
9. Click Delete, and then click Yes.
233

Recreating a deleted backup-to-disk file
Recreating a deleted backup-to-disk file
If you deleted a backup-to-disk file from Backup Exec, but did not use Windows Explorer
to delete the file from the disk, you can recreate it by running Inventory.
To recreate a backup-to-disk file
1. On the navigation bar, click Devices.
2. Expand the icon for the computer where the backup-to-disk folder is located.
3. Select the folder where the backup-to-disk file was located before you deleted it.
4. Under Media Tasks in the task pane, select Inventory and create and run an
inventory job.
The backup-to-disk file appears on the results pane when the inventory job
completes.
Related Topics:
“Inventorying media” on page 238
Using Microsoft’s Removable Storage feature with Backup Exec
Removable Storage is a feature of Windows 2000, Windows XP, and Windows Server
2003 computers that allows applications to share removable storage devices. Removable
Storage performs requests for device access from different applications on a first in,
first out basis. It also tracks media usage for online media (media currently mounted in a
robotic library) and for offline media that has been installed previously in a robotic
library. Removable Storage does not manage single-slot tape drives.
On the media server, you can allow Removable Storage to share the devices in robotic
libraries between two or more applications, or you can allow some or all devices in
robotic libraries to be controlled and used exclusively by Backup Exec’s Advanced Device
and Media Management (ADAMM). If the device is enabled for Removable Storage
through the robotic library’s Properties (see “Viewing robotic library configuration
properties” on page 212), Backup Exec uses Removable Storage for device and media
operations; if the Enable Removable Storage option is cleared, Backup Exec controls the
device directly.
In some situations, Removable Storage does not support a robotic library, but may still
support some drives in the robotic library. When this happens, Removable Storage
disables the robotic libraries but enables the supported drives in the robotic libraries.
234 Administrator’s Guide

Chapter 5, Managing devices
Recreating a deleted backup-to-disk file
You should use the Removable Storage snap-in in an MMC (Microsoft Management
Console) to disable all of the drives in the robotic library. This allows Backup Exec to
control the robotic library and all of the drives.
If you do not need to share the devices, exclusive use by Backup Exec will allow faster
tape backups and restores. If you allow exclusive use by Backup Exec, you can still
enable or disable devices in Removable Storage while Backup Exec is running; Backup
Exec will respond by switching to other devices in the robotic libraries as appropriate.
You should not enable Removable Storage for devices used with the SAN Shared Storage
Option (SAN SSO). RSM does not appropriately manage devices and media used by
multiple servers.
The Removable Storage database is automatically backed up by Backup Exec, and can be
restored if necessary. For more information, see “Advanced options for restore” on
page 494.
The Backup Exec services account must have Administrator rights to protect the
Removable Storage database. If the account does not have Administrator rights, the
following error message is recorded in the job log: "An error occurred while exporting
the RSM Database files. The RSM Database could not be backed up."
Only Microsoft tape class drivers can be used if you plan to use Backup Exec and the
Removable Storage feature. If you want to use a third party tape class driver or a
Symantec tape class driver, you must disable the device through Removable Storage
before installing the driver.
Using media in drives managed by Removable Storage
Use the Removable Storage snap-in to manually control the movement of media into
and out of the robotic libraries managed by Removable Storage, to allocate media to one
application process or another, and to prepare new, imported, or unrecognized media
for use within the Removable Storage domain. You must use appropriate processes to
move media between applications. Media that is assigned by Removable Storage to an
application other than Backup Exec cannot be accessed by ADAMM.
Media in the Removable Storage Import and Free media pools are available for use in
Backup Exec, and can be assigned to Backup Exec using one of the following methods:
■ In Computer Management on the local computer, under the Storage node, open
Removable Storage, and then open Media Pools. Move media from the Import or
Free media pools into a Backup Exec media pool (see your Microsoft Windows 2000
documentation or online help for details). The next time that Removable Storage is
scanned, any media that is in the Backup Exec pool is allocated to Backup Exec and
marked as "in use" by Backup Exec.
235

Recreating a deleted backup-to-disk file
■ Acquire available media through normal Backup Exec operations. This media is then
placed in the Removable Storage Import pool and can be accessed by Backup Exec
using the policies you established for Imported media.
Media that is in the Removable Storage Free media pool or that is unrecognizable by
Removable Storage is marked as unknown media within Backup Exec. You must run an
Inventory job to mount and read the media header. The media is imported into Backup
Exec and marked as in use by Backup Exec. If you do not want that media used by Backup
Exec, delete it from the ADAMM database. For more information, see “Deleting media”
on page 296.
Backup Exec cannot append to media prepared initially by Removable Storage. To be
able to use this media, you must run an overwrite operation. If media is introduced for
the first time into Removable Storage, but it was previously possessed by Backup Exec or
written to by Backup Exec during a mount operation, even on another server, then that
media is allocated to Backup Exec for exclusive use.
Using Backup Exec exclusively with some devices
If you want to use Backup Exec exclusively on some devices, ensure the Enable Remote
Storage (RSM) option is cleared on the robotic library’s Configuration tab; to allow
other applications on the server to access Removable Storage to share other devices,
select the Enable Remote Storage (RSM) option (see “Viewing robotic library
configuration properties” on page 212).
Symantec recommends enabling or disabling devices using Removable Storage only
when the device is not in use and the internal drives are empty.
Monitoring Backup Exec and Removable Storage
To view the Removable Storage work queue
1. Click Start, and then point to Programs.
2. Point to Administrative Tools, and then click Computer Management.
3. Expand the tree view of Storage.
4. Expand Removable Storage, and then click Work Queue.
You can also track the location and status of media by viewing the media and drive
objects associated with the robotic library being shared with Backup Exec. The status of
the media is updated as the media is moved.
236 Administrator’s Guide

Chapter 5, Managing devices
Creating utility jobs to help manage devices and media
Removing the Backup Exec pool from Removable Storage
If you must uninstall Backup Exec at some time, you may want to delete the Removable
Storage Backup Exec pool. Refer to your Microsoft documentation for details on how to
use the Removable Storage snap-in to delete an application media pool.
Creating utility jobs to help manage devices and media
Backup Exec includes utility jobs that aid in managing devices and media. You can
specify a job priority and a recipient for notification when these jobs run. Utility jobs,
which are similar to backup and restore jobs, generate job history records and an XML
job log when they run.
Jobs that can be scheduled as recurring jobs are listed in the following table:
Utility jobs that can be scheduled
Utility job that can be scheduled For more information, see
Catalog media “Cataloging media while reviewing devices or media” on
page 284
Restore data “Creating a restore job while reviewing media or devices” on
page 286
Inventory robotic library or
device
Erase media in a robotic library
or device
“Inventorying media” on page 238
“Erasing media” on page 240
Import media “Importing media to a robotic library” on page 249
Export media “Exporting media from a robotic library” on page 251
Export expired media (robotic
libraries only)
“Exporting expired media from a robotic library” on page 255
Lock robotic library “Locking the robotic library’s front panel” on page 252
Unlock robotic library “Unlocking the robotic library’s front panel” on page 254
Clean drive “Setting up cleaning jobs” on page 248
237

Creating utility jobs to help manage devices and media
Utility jobs that can be created only as run-once jobs, which are jobs that are scheduled
to run now or to run once at a specified date and time, are listed in the following table:
Utility jobs that can run once
Utility jobs that can run once: For more information, see:
Label media “Labeling media” on page 246
Format media, including WORM
media
If you have a robotic library, you can perform utility operations on the robotic library,
the robotic library drive, all slots, and individual slots.
You can perform operations on devices in Backup Exec by doing one of the following:
■ Right-click an object to display options on the shortcut menu.
■ Select an object, and then click an available task on the task pane.
Inventorying media
“Formatting media in a drive” on page 244
Retension media “Retensioning a tape” on page 243
Eject media “Ejecting media from a drive” on page 247
Initialize robotic library “Initializing the robotic library” on page 253
Run Inventory to mount the media in the device and read the media label, which is then
displayed in the Devices view. If this is the first time that Backup Exec has encountered
this media, the media label is also added to the Media view.
If you change the media in the robotic library or device, run Inventory so that the
current media in the device is displayed in the views; otherwise, the previous media is
still displayed as being in the device.
You should run an inventory operation when Backup Exec is started for the first time
following a new installation or a product upgrade. When Backup Exec is exited and
restarted, it saves information pertaining to the location and contents of all of the media
from the last Backup Exec session (provided the media in the devices hasn’t changed).
With this information, Backup Exec can immediately begin processing operations when
it is restarted.
When media is changed in a robotic library, you can inventory all of the slots in the
robotic library or select the slots to be inventoried. You are not required to re-inventory
slots when adding media requested by Backup Exec. For example:
238 Administrator’s Guide

Chapter 5, Managing devices
Creating utility jobs to help manage devices and media
If you are performing a restore operation, and the data is contained on media that is
not currently in the robotic library, you are prompted to insert the media for the
restore operation. In this case, you are not required to re-inventory the slot where
the restore source media is placed.
When media that is not requested by Backup Exec is added or removed from the
magazine, you should perform an inventory operation on the changed slots. This
updates the media database so Backup Exec doesn’t load and unload each media in the
magazine searching for the correct media on which to process jobs. You can select
specific slots to inventory. If you swap media often you may want Backup Exec to
perform an inventory on the robotic library magazine each time Backup Exec services
are started.
To inventory media in a device
1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the device resides in a robotic
library, click Robotic Libraries.
3. If you want to inventory a drive or slot, select the drive or slot containing the media
you want to inventory, or select Slots.
4. If you want to inventory a backup-to-disk file:
■ Double-click the icon for the computer where the backup-to-disk folder is
located.
■ Click the backup-to-disk folder that contains the file you want to inventory.
■ On the Results pane, select the file you want to inventory.
5. Under Media Tasks in the task pane, select Inventory.
6. Select the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
239

Creating utility jobs to help manage devices and media
7. If you want a person or group to be notified when the job completes, on the
Properties pane, under Settings, click Notification and select the options you want
(see “Assigning notification recipients for completed jobs” on page 565).
8. If you want to run the job now, click Run Now. Otherwise, on the Properties pane,
under Frequency, click Schedule to set the scheduling options you want to use (see
“Scheduling jobs” on page 368).
There may be a delay (up to several minutes for some drives) as the media is mounted
and inventoried.
The inventory operation can be monitored or canceled through the Job Monitor.
Related Topics:
“Media labeling” on page 278
“Include robotic libraries in inventory job when Backup Exec services start up” on
page 139
Inventorying all drives when Backup Exec services start
You can set a default so that all drives are inventoried whenever Backup Exec services
are started. An inventory of all drives on start-up is recommended if media is often
moved between robotic libraries, but Backup Exec may take longer to start.
To inventory all drives when Backup Exec services starts
1. On the Tools menu, click Options.
2. In the Properties pane, under Settings, click Preferences.
3. Click Inventory all drives on Backup Exec services startup.
4. Click OK.
Erasing media
You can erase media using either Quick erase or Long erase. Not all devices support a
long erase; those that do not can only perform a quick erase.
Quick erase writes an indicator at the beginning of the media that makes the data
contained on the media inaccessible. For most uses, a Quick erase is sufficient.
240 Administrator’s Guide

Chapter 5, Managing devices
Creating utility jobs to help manage devices and media
Long erase instructs the drive to physically erase the entire media. If you have sensitive
information on the media and you want to dispose of it, use Long erase. Running Long
erase on media can take several minutes to several hours to complete (depending on the
drive and the media capacity).
Quick and Long erase do not change the media label. To change a media label, use Label
Media or Rename prior to the Erase operation.
To erase media
1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the device resides in a robotic
library, click Robotic Libraries.
3. Select the drive or slot containing the media you want to erase.
4. Under Media Tasks in the task pane, select either Erase media, quick or Erase
media, long.
Note If the drive does not support a long erase, Erase media, long will not be available.
The following warning is displayed:
"This operation will be performed on the current media in the drive or slot. If the
media has been changed since the last inventory operation was performed, the
media label in the next dialog may not match the media in the drive or slot selected."
5. Click OK to continue.
The media displayed was read during the last inventory operation; the display does
not change until another inventory operation occurs. Therefore, if you change
media in the slot or drive but did not run Inventory, the media label displayed may
not match the actual media in the slot or drive.
6. When prompted, click Yes to erase the media.
7. Select the appropriate options as follows:
Job name Type a name for the job or accept the default name.
241

Creating utility jobs to help manage devices and media
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
8. If you want a person or group to be notified when the job completes, on the
Properties pane, under Settings, click Notification and select the options you want
(see “Setting up notification for alerts” on page 543).
9. If you want to run the job now, click Run Now. Otherwise, on the Properties pane,
under Frequency, click Schedule to set the scheduling options you want to use (see
“Scheduling jobs” on page 368).
You can monitor the Erase operation through the Job Monitor.
You cannot cancel an Erase operation after it has started; however, you can use Cancel
to stop a queued erase operation.
Erasing backup-to-disk files
Erasing backup-to-disk files removes the data from both the backup-to-disk folder and
the disk, and removes the file references from the catalog. However, the backup-to-disk
file remains for use with future backup jobs. You cannot restore the data after you erase
it. If you want to remove data from Backup Exec and restore it later, delete the file from
the Media view (For more information, see “Deleting a backup-to-disk file” on page 233.)
Unlike other types of devices, when you erase a file from a backup-to-disk folder you
cannot choose whether to perform a quick erase or a long erase. Backup Exec performs
only a quick erase on backup-to-disk files in backup-to-disk folders.
Caution You cannot restore the data that you erase. Before you erase files, be sure that
you no longer need them.
To erase a backup-to-disk file
1. On the navigation bar, click Devices.
2. Expand the icon for the computer where the backup-to-disk folder is located.
3. Under Backup-to-Disk Folders, click the backup-to-disk folder that contains the file
you want to erase.
242 Administrator’s Guide

4. On the Results pane, select the file you want to erase.
Chapter 5, Managing devices
Creating utility jobs to help manage devices and media
5. Under Media Tasks in the task pane, select Erase media, quick.
6. Click OK to continue.
7. Click Yes, or if more than one file was selected, click Yes to All.
8. Select the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
9. If you want a person or group to be notified when the job completes, on the
Properties pane, under Settings, click Notification and select the options you want
(see “Setting up notification for alerts” on page 543).
10. If you want to run the job now, click Run Now. Otherwise, on the Properties pane,
under Frequency, click Schedule to set the scheduling options you want to use (see
“Scheduling jobs” on page 368).
Retensioning a tape
Use Retension media to run the tape in the tape drive from beginning to end at a fast
speed so that the tape winds evenly and runs more smoothly past the tape drive heads.
Refer to the documentation that came with your tape drive to see how often this utility
should be performed.
Retensioning is primarily for Mini Cartridge and quarter-inch cartridges and is not
supported on most other types of tape drives.
243

Creating utility jobs to help manage devices and media
To retension a tape
1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a
robotic library, click Robotic Libraries.
3. Select the drive or slot containing the media you want to retension.
4. Under Media Tasks in the task pane, select Retension media.
5. Select the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
6. If you want a person or group to be notified when the job completes, on the
Properties pane, under Settings, click Notification, and select the options you want
(see “Assigning notification recipients for completed jobs” on page 565).
7. Click Run now.
The job will be submitted as a Run now job, unless you submitted the job on hold. You
can monitor the Retension operation from the Job Monitor.
You cannot cancel a Retension operation after it has started; however, you can use
Cancel to stop a queued retension operation.
Formatting media in a drive
Use Format media to format the media currently in the drive. Most devices do not
support formatting. If formatting is not supported, the option is not available.
If you use Format on a DC2000 tape, the formatting may take two or more hours to
complete.
Caution Formatting erases the media. All data on the media is lost.
244 Administrator’s Guide

To format media in a drive
1. On the navigation bar, click Devices.
Chapter 5, Managing devices
Creating utility jobs to help manage devices and media
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a
robotic library, click Robotic Libraries.
3. Select the drive or slot containing the media you want to format.
4. Under Media Tasks in the task pane, select Format media.
The media label that is displayed was read during the last inventory operation. The
media label displayed does not change until another inventory operation occurs.
Therefore, if you changed media in the slot or drive but did not run Inventory, the
media label displayed may not match the actual media in the slot or drive.
5. To format the media that is displayed, click Yes.
6. Select the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
7. If you want a person or group to be notified when the job completes, on the
Properties pane, under Settings, click Notification, and select the options you want
(see “Assigning notification recipients for completed jobs” on page 565).
8. Click Run now.
The job will be submitted as a Run now job, unless you submitted the job on hold. You
can monitor the Format operation from the Job Monitor.
You cannot cancel a Format operation after it has started; however, you can use Cancel
to stop a queued Format operation.
245

Creating utility jobs to help manage devices and media
Labeling media
Use Label media to immediately write a new media label on the media in the selected
drive. This operation destroys any data on the media. To change the media label without
destroying the data on the media (until an overwrite operation occurs), use Rename.
To label media
1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a
robotic library, click Robotic Libraries.
3. Select the drive or slot containing the media you want to label.
4. Under Media Tasks on the task pane, select Label media.
The following warning is displayed:
"This operation will be performed on the current media in the drive or slot. If the
media has been changed since the last inventory operation was performed, the
media label in the next dialog may not match the media in the drive or slot selected."
5. Click OK.
6. Type the name you want to use as the recorded media label for this media.
7. Click OK to erase all data on the media and re-label the media.
8. Select the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
9. If you want a person or group to be notified when the job completes, on the
Properties pane, under Settings, click Notification and select the options you want
(see “Assigning notification recipients for completed jobs” on page 565).
246 Administrator’s Guide

Chapter 5, Managing devices
Creating utility jobs to help manage devices and media
10. Click Run now.
The job will be submitted as a Run now job, unless you submitted the job on hold.
You can monitor the Label media operation from the Job Monitor.
You cannot cancel a Label media operation after it has started; however, you can use
Cancel to stop a queued Label media operation.
11. Write this same media label on an external label fixed to the outside of the physical
media.
Related Topics:
“Renaming media” on page 282
Ejecting media from a drive
Use Eject media to eject the media currently in the drive. If the media is a tape, Eject
rewinds the tape before ejecting it.
Some drives do not support a software-driven media eject. If the media is a tape, the tape
is rewound and you may be instructed to manually remove it.
To eject media from a drive
1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, and then select the drive.
3. Under Media Tasks in the task pane, select Eject media.
4. Select the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
247

Creating utility jobs to help manage devices and media
5. If you want a person or group to be notified when the job completes, on the
Properties pane, under Settings, click Notification, and select the options you want
(see “Assigning notification recipients for completed jobs” on page 565).
6. Click Run Now.
The job will be submitted as a Run now job, unless you submitted the job on hold.
Setting up cleaning jobs
You can submit once-only cleaning jobs, or set up scheduled cleaning jobs.
Before submitting a cleaning job, you must define a cleaning slot that contains the
cleaning tape.
To define a cleaning slot
1. On the navigation bar, click Devices.
2. Click Robotic Libraries, and then click the drive or robotic library for which you are
setting up the cleaning.
3. Click Slots to display the library’s slots in the results pane.
4. Select the slot that contains the cleaning tape.
5. Under General Tasks in the task bar, select Properties.
6. Check Cleaning slot and click OK.
Make sure that the cleaning tape is located in the slot that you defined as the
cleaning slot. After defining the cleaning slot, you can set up a cleaning job for the
robotic library drive.
To run a cleaning job
1. On the navigation bar, click Devices.
2. Click Robotic Libraries, and then click the drive or robotic library containing the
drive, and then select the drive.
3. Under Drive Tasks in the task pane, select Clean.
248 Administrator’s Guide

4. Select the appropriate options as follows:
Chapter 5, Managing devices
Creating utility jobs to help manage devices and media
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
5. If you want a person or group to be notified when the job completes, on the
Properties pane, under Settings, click Notification and select the options you want
(see “Assigning notification recipients for completed jobs” on page 565).
6. If you want to run the job now, click Run Now. Otherwise, on the Properties pane,
under Frequency, click Schedule to set the scheduling options you want to use (see
“Scheduling jobs” on page 368).
You can monitor the cleaning job through the Job Monitor. You can view cleaning
statistics for the drive by right-clicking the drive and selecting Properties. For more
information, see “Viewing storage device properties” on page 195.
Importing media to a robotic library
You must create an import media job to insert media into your robotic library so that the
Backup Exec database is updated. Before you create an import media job, note the
following:
■ If the media does not have a bar code, when you create the import job, you must
select the option Auto-inventory after import is completed.
■ If your robotic library uses a media magazine, make sure no jobs are currently
running and that all media are ejected from the drive and are back in the magazine
slots before swapping the magazine.
You can select any number of slots to import.
The Backup Exec import media job fully supports robotic libraries with portals. When
this job is run, the slots you selected are checked for media. If media is found, it is
exported to the portals. After all the media has been exported, you are prompted to
insert new media into the portal so it can be imported. This process continues until all of
the requested media has been imported into the robotic library.
You can monitor this job on the Job Monitor.
249

Creating utility jobs to help manage devices and media
To import media to a robotic library
1. On the navigation bar, click Devices.
2. Select the robotic library.
3. Click Slots.
4. On the Results pane, select the slots you want to import media to.
5. Under Media Tasks in the task pane, select Import media.
6. Complete the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
7. If the media does not have a bar code, or if you want Backup Exec to automatically
create an inventory job to run after the import job completes, under Settings, click
Options, and then select Auto-inventory after import is completed.
8. If you want Backup Exec to notify someone when the job completes, on the
Properties pane, under Settings, click Notification.
See “Setting up notification for alerts” on page 543.
9. Do one of the following:
■ To run the job now, click Run Now.
■ To set scheduling options, on the Properties pane, under Frequency, click
Schedule.
See “Scheduling jobs” on page 368.
Related Topics:
“About robotic libraries in Backup Exec” on page 206
250 Administrator’s Guide

Exporting media from a robotic library
Chapter 5, Managing devices
Creating utility jobs to help manage devices and media
You must create a job to export media so that the Backup Exec database is updated.
The Backup Exec export media job fully supports robotic libraries with portals. When
this job is run on one or more robotic library slots, the exported media is placed in the
portals. If you select more media than there are portals, the robotic library will fill as
many slots as possible, and then you are prompted to remove the media from the portal.
This process continues until all of the selected media has been removed from the robotic
library.
You can also select a media vault that you want the exported media moved to after the
export job has successfully completed.
You can monitor this job on the Job Monitor.
To export media from a robotic library
1. On the navigation bar, click Devices.
2. Select the robotic library.
3. Click Slots.
4. On the Results pane, select the slots you want to export media from.
5. Under Media Tasks in the task pane, select Export media.
6. Complete the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
7. If you want to move the media to a media vault after the export job is complete, on
the Properties pane, under Settings, click Options, and select a media vault.
8. If you want Backup Exec to notify someone when the job completes, on the
Properties pane, under Settings, click Notification.
251

Creating utility jobs to help manage devices and media
See “Assigning notification recipients for completed jobs” on page 565.
9. Do one of the following:
■ To run the job now, click Run Now.
■ To set scheduling options, on the Properties pane, under Frequency, click
Schedule.
See “Scheduling jobs” on page 368.
Locking the robotic library’s front panel
You must create a job to lock the robotic library’s front panel. You can monitor this job
on the Job Monitor.
To lock the robotic library’s front panel
1. On the navigation bar, click Devices.
2. Select the robotic library.
3. Under Robotic Library Tasks in the task pane, select Lock.
4. Complete the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
5. If you want Backup Exec to notify someone when the job completes, on the
Properties pane, under Settings, click Notification.
See “Assigning notification recipients for completed jobs” on page 565.
252 Administrator’s Guide

6. Do one of the following:
Chapter 5, Managing devices
■ To run the job now, click Run Now.
Creating utility jobs to help manage devices and media
■ To set scheduling options, on the Properties pane, under Frequency, click
Schedule.
See “Scheduling jobs” on page 368.
Initializing the robotic library
You must create a job to initialize the robotic library. You can monitor this job on the Job
Monitor.
To initialize the robotic library
1. On the navigation bar, click Devices.
2. Select the robotic library.
3. Under Robotic Library Tasks in the task pane, select Initialize.
4. Complete the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
5. If you want Backup Exec to notify someone when the job completes, on the
Properties pane, under Settings, click Notification.
See “Assigning notification recipients for completed jobs” on page 565.
6. Do one of the following:
■ To run the job now, click Run Now.
■ To set scheduling options, on the Properties pane, under Frequency, click
Schedule.
253

Creating utility jobs to help manage devices and media
See “Scheduling jobs” on page 368.
Unlocking the robotic library’s front panel
You must create a job to unlock the robotic library’s front panel. You can monitor this
job on the Job Monitor.
To unlock the robotic library’s front panel
1. On the navigation bar, click Devices.
2. Select the robotic library.
3. Under Robotic Library Tasks in the task pane, click Unlock.
4. Complete the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
5. If you want Backup Exec to notify someone when the job completes, on the
Properties pane, under Settings, click Notification.
See “Assigning notification recipients for completed jobs” on page 565.
6. Do one of the following:
■ To run the job now, click Run Now.
■ To set scheduling options, on the Properties pane, under Frequency, click
Schedule.
See “Scheduling jobs” on page 368.
254 Administrator’s Guide

Exporting expired media from a robotic library
Chapter 5, Managing devices
Creating utility jobs to help manage devices and media
The export expired media job allows you to automate media handling in robotic libraries
by removing media that cannot be written to so that scratch media can easily be added
to the library in preparation for the next backup window. Expired media is any media
that cannot be written to.
When you export expired media from the robotic library, the media status is displayed
as offline. If the media is in a media set that has a vault media rule, then the media is
moved to the vault location.
Cleaning media can be exported with the export expired media job. You can include all
cleaning media, or all cleaning media that has been used more than a specified number
of times.
You can choose to be prompted as a reminder to import new media after an export
expired media job completes successfully. You can monitor the export expired media job
through the Job Monitor.
To export expired media from a robotic library
1. On the navigation bar, click Devices.
2. Select the robotic library.
3. Under Robotic Library Tasks in the task pane, click Export expired media.
4. On the Export Job Properties pane, under Settings, click General.
5. Complete the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority for the job. Available options are:
◆ Lowest
◆ Low
◆ Medium
◆ High
◆ Highest
6. To set options for the export expired media job, on the Properties pane, under
Settings, click Options.
255

Creating utility jobs to help manage devices and media
7. Complete the appropriate options as follows:
Include cleaning media
in export
Export cleaning media
used more than x times
After export,
automatically prompt
for new media to be
imported
Upon successful export,
move the media to
media vault
8. If you want Backup Exec to notify someone when the job completes, on the
Properties pane, under Settings, click Notification.
See “Assigning notification recipients for completed jobs” on page 565.
9. Do one of the following:
■ To run the job now, click Run Now.
Select this check box to include cleaning media in the export of
expired media.
Select the number of times that the cleaning media can be used
before it is exported by this job.
Select this check box to be prompted to import new media to the
slot after the export expired media operation has completed.
Select a vault to logically move the media to after the export job
successfully completes.
To create a media vault, see “Creating media vaults” on page 287.
■ To set scheduling options, on the Properties pane, under Frequency, click
Schedule.
See “Scheduling jobs” on page 368.
256 Administrator’s Guide

Managing media
With Backup Exec’s media management tools you can:
■ Protect data from being overwritten.
■ Set up media rotation strategies.
■ Track the location of media.
■ Label media automatically.
■ Read and track media labels with bar codes.
■ Collect and report media statistics.
About media in Backup Exec
Chapter
6
With Backup Exec, you are not required to select media for jobs; it is done for you by the
Advanced Device and Media Management (ADAMM) component. Backup Exec tracks all
media that is loaded into attached storage devices, media that is offline, and media that
has been placed in media vaults.
On the navigation bar, click Media to view all the media used in Backup Exec:
■ All Media. All media that has been introduced into Backup Exec. Any media that is
available for overwriting in backup operations, such as scratch or recyclable media,
displays in blue. When you click the All Media icon, the Results pane displays
properties for the media in Backup Exec. For more information, see “Viewing media
in storage devices” on page 170.
■ Media Sets. A media set is a set of rules that manage media. These rules include the
append and the overwrite protection periods, and vault rules, which allow you to set
dates for when media should be moved to or returned from a media vault.
257

About media in Backup Exec
The overwrite protection period is the length of time that data is retained on a
specific media before becoming available for overwriting. The append period is the
length of time that data can be added to a media. You can create different media
sets, each with different data overwrite protection and append periods. When a
backup job is created, you associate it with a specific media set that defines the data
overwrite protection and append periods that you want applied to the backup job.
You can use media sets to set up media rotation strategies.
Media that are already associated with a media set are allocated media. Allocated
media have current append and overwrite protection periods. Media that are
associated with a media set, but have expired overwrite protection periods are
recyclable media.
You can move recyclable media to Scratch Media, or you can let it remain associated
with the media set. Backup Exec automatically finds and overwrites media that have
expired overwrite protection periods. When a backup job runs, by default Backup
Exec uses scratch media first, and then if no scratch media are available, selects
recyclable media that is in the targeted media set for overwriting. To change this
default, on the Tools menu, click Options, and then under Settings, click Media
Management. Recyclable media, along with scratch media, display in blue in the
Media and Devices views.
Media Sets include:
■ Cleaning Media - All cleaning media.
■ Imported Media - Media created by a product other than this installation of
Backup Exec. By default, Imported media have an overwrite protection period of
Infinite, but can still be overwritten if the media overwrite protection level is set
to Partial or None. You can overwrite imported media using several methods.
Data can be restored from imported media until that media is overwritten.
Other media pools that are contained in Imported Media are:
■ Backup Exec and Windows NT Backup Media - Media from another
installation of Backup Exec.
■ Backup Exec Archive Media - Media that was used for archive jobs.
■ Foreign Media - Media from a product other than Backup Exec.
■ Retired Media - A system media set that protects it from being used
(overwritten). It is used for media that you have taken out of service, usually
because of an excessive number of errors. After a media has been associated
with the retired media set, it is not selected for backup jobs by Backup Exec. It is
still available for restore operations, if it has not been damaged.
258 Administrator’s Guide

Chapter 6, Managing media
About media in Backup Exec
You can delete media that is in Retired Media to remove it from Backup Exec.
You may want to delete media, for example, when you have a lot of offsite media
that you do not want to recycle or if you throw away the media. If you decide to
use deleted media in Backup Exec, it is recognized as Imported Media and must
be cataloged before you can restore from it.
■ Scratch Media - A system media set that allows media to be overwritten. New,
blank, and erased media are automatically associated with the scratch media
set.
■ Keep Data Infinitely - Do Not Allow Overwrite - A default media set that is
created when Backup Exec is first installed. Until you create another media set,
the default rules in the media set Keep Data Infinitely - Do Not Allow Overwrite
apply to all backup jobs that you create. By using these default rules for
overwrite protection, you can keep your backup data safe from overwriting,
unless you erase, label, or format the media, or associate it with Scratch Media.
You can rename this media set at any time after installation, so it may not
continue to be displayed as Keep Data Infinitely - Do Not Allow Overwrite. For
more information about this default media set, see “Default media set” on
page 263.
Note If you are upgrading from a version of Backup Exec prior to 11d, the
default media set name remains Media Set 1.
■ Media Location - Backup Exec helps you track the location of your media. There are
three categories available for tracking media:
■ Online media - Media that reside in a storage device, robotic library slot, or
backup-to-disk folder.
■ Offline media - Media that are onsite but are not in devices or slots, or media
vaults.
■ User-defined media vault - A logical representation of the actual physical
location of media, such as a special media room, a scratch bin, or an offsite
location.
Related Topics:
“Creating media sets” on page 264
“Running the Media Set Wizard” on page 266
“Media locations and vaults” on page 286
“Associating media with a media set” on page 297
259

Media overwrite protection
Media overwrite protection
Each media is associated with a media set, which is a set of rules that manage media.
These rules include:
Rules specified in the media set
Rule Description
Append period The amount of time that data can be appended (added) to
media. It is measured from the time the media was first
allocated. It can be specified in hours, days, weeks, or years.
Overwrite protection period The amount of time that media is protected from being
overwritten. It 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.
Your media rotation strategy must balance between your need to save useful data as long
as possible, and the fact that media are not in infinite supply. The compromise between
the longevity of stored backup data and the cost of more media is controlled in Backup
Exec by the rules specified in the media set, which allows Backup Exec to identify which
media can be written to and which media is overwrite-protected.
260 Administrator’s Guide

Append periods and overwrite protection periods
TIME TIME
TIME
A P P E N D P E R I O D
Chapter 6, Managing media
O V E R W R I T E P R O T E C T I O N P E R I O D
The append period begins when the media is allocated to a
media set.
The overwrite protection period is
measured from the time of the last
write to the media.
During the append period, data can
be added to the media. Any data
already on the media is protected
against loss.
The append period ends.
After the append
period expires, and
while the overwrite
protection period is
still active, data
cannot be added to the
media. Any data
already on the media
is protected against
loss.
The overwrite protection period
expires.
New
data
Old
data
After the overwrite protection
period expires, the media becomes
recyclable. This means that new
data can be written to the
beginning of the media by a new
backup job (causing loss of the
original data).
Media overwrite protection
The media
cannot be
overwritten
by another
job during
this interval.
(However,
you could
erase the
media or
associate it
with scratch
media.)
The append and overwrite protection periods that you specify apply to all the data on
the media. Therefore, each time data is written to a media, the time remaining in the
overwrite protection period is reset and the countdown restarted.
261

Media overwrite protection
How overwrite protection periods are reset
Time in
days
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Append period = 5 days
Normal Bkup
Protection
period
14 Days
The media can be overwritten at
this time
First Day
Time in
days
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Append period = 5 days
Normal Bkup
Normal Bkup
Protection
period
14 Days
1
1 2
1 2 3
1 2 34
Because the overwrite protection period does not begin until the job completes, the
amount of time that the job takes to complete affects the amount of time until the media
can be overwritten.
For example, suppose that you create a media set named Weekly with an overwrite
protection period of seven days, and an append period of 0 days, and you schedule a full
backup job to run each Friday at 20:00. When it is time for the full backup to run at 20:00
the following Friday, the job cannot run because the first backup job that ran the
previous Friday did not complete until 21:10 p.m. The overwrite protection period for
the Weekly media set still has 70 minutes remaining.
Typically, to prevent this situation, you would shorten the overwrite protection period
to account for the amount of time a job may run. For this example, the scheduled job
recurring at 20:00 can run if the overwrite protection period is set to 6 days instead of 7
days.
262 Administrator’s Guide
1
The media can be overwritten at
this time
Second Day
Time in
days
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Append period = 5 days
Normal Bkup
Normal Bkup
Normal Bkup
Normal Bkup
Normal Bkup
Protection
period
14 Days
Fifth Day
The media can be overwritten at
this time

Default media set
Chapter 6, Managing media
Media overwrite protection
When Backup Exec is installed, important defaults are set to protect media from being
overwritten:
■ A media set named Keep Data Infinitely - Do Not Allow Overwrite is created.
■ The append and overwrite protection periods are set to Infinite for the media set
Keep Data Infinitely - Do Not Allow Overwrite.
■ All backup jobs you create are associated with the media set Keep Data Infinitely -
Do Not Allow Overwrite.
Note If you are upgrading from a version of Backup Exec prior to 11d, the default
media set name remains Media Set 1.
By using these defaults, you can keep all of your backup data safe from overwriting
(unless you erase, label, or format the media, or associate it with scratch media). You will
eventually run out of overwritable media unless you continually introduce scratch
media into Backup Exec.
To ensure that Backup Exec has media available, you can:
■ Create new media sets with append and overwrite protection periods set to intervals
of time that accommodate your needs (such as weekly, monthly, etc.) and then
specify these media sets when you create a backup job. When the overwrite
protection period expires, the media are still displayed as being associated with that
media set, but with a status of recyclable. Whenever more media are needed for
other jobs, Backup Exec automatically finds and overwrites recyclable media.
■ Change the append and overwrite protection periods of the media set Keep Data
Infinitely - Do Not Allow Overwrite to finite periods. The risk with changing the
overwrite protection period in the media set Keep Data Infinitely - Do Not Allow
Overwrite is that if you continue to use this media set as the default media set for all
backup jobs, your data may not be protected as long as you need it to be.
Related Topics:
“Creating media sets” on page 264
“Deleting a media set” on page 267
“Renaming a media set” on page 268
“Associating media with a media set” on page 297
“Changing general media set properties” on page 268
263

Media overwrite protection
Creating media sets
A media set consists of rules that specify append periods, overwrite protection periods,
and vaulting periods.
When you create a new media set, you specify an append period and an overwrite
protection period for the set. When media is associated with the media set, the append
and overwrite protection periods apply to that media.
You can also specify vault rules, which allow you to set dates for when media should be
reported as ready to be moved to or returned from a media vault. The Vault Wizard
logically moves the media, and then exports the media, but you must physically move
the media to and from the vault. You can use the Vault Wizard to print or view reports
that contain details on which media are ready to be moved, and to update the media
location. See “Using the Vault Wizard to move media” on page 293.
If your environment includes remote sites, you should create separate media sets for
each remote site, so that if vault rules are enabled, the reports contain details on which
media are ready to be moved for just that site.
Note Even if the overwrite protection period is current, media can still be overwritten if
the overwrite protection level is set to None.
See “Media overwrite protection levels” on page 270.
To create a media set
1. On the navigation bar, click Media.
2. Under Media Set Tasks in the task pane, click New Media Set.
3. On the General tab, select the appropriate options as follows, and then click OK:
Name Type a name for the new media set.
Creation date Date and time when the media set was created. Backup Exec sets
the date and time automatically. You cannot change them.
264 Administrator’s Guide

Overwrite protection
period
Chapter 6, Managing media
Media overwrite protection
Enter the length of time in hours, days, weeks, or years to retain
the data on the media before the media can be overwritten
(unless the media is erased, formatted, labeled, associated with
Scratch Media, or if the Media Overwrite Protection Level is set
to None).
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 the job takes to complete
affects the amount of time until 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, setting the overwrite protection period for seven
days and the append period for four days ensures that data will
not be overwritten for at least seven days, and that data can be
appended to the media for the next four days. The last data
appended to this media is retained for at least seven days.
Because of the method Backup Exec uses to compute time, the
unit of time that you enter may be converted. For example, if you
enter 14 days, the next time you view this property, it may be
displayed as two weeks.
The default is Infinite - Don’t Allow Overwrite, which protects
the media from being overwritten for 1,000 years, unless the
media is erased, formatted, labeled, moved to Scratch Media, or
if the media overwrite protection level is set to None.
Append period Enter the length of time in hours, days, or weeks, that data can
be added to media. Because of the method Backup Exec uses to
compute time, the unit of time that you enter may be converted.
For example, if you enter 14 days, the next time you view this
property, it may be displayed as two weeks.
The append period starts when the first backup job is written to
this media.
The default is Infinite - Allow Append, which allows data to be
appended until the media capacity is reached.
Note Symantec Backup Exec for Windows Servers 11d does not
support appending to tapes or backup-to-disk folders that
contain backup sets created by a previous version Backup
Exec.
4. To specify vault rules to set dates for when media should be moved to or returned
from a media vault, click the Vault Rules tab.
265

Media overwrite protection
5. Select the appropriate options as follows, and then click OK.
Select the media vault to use with
this media set:
Move media to this vault x after it
is allocated (first written to or
overwritten)
Return media from this vault x
after it is last written to
Related Topics:
“Media overwrite protection” on page 260
“Deleting a media set” on page 267
“Renaming a media set” on page 268
“Changing general media set properties” on page 268
“Configuring vault rules for media sets” on page 288
“Using the Vault Wizard to move media” on page 293
Running the Media Set Wizard
Click the drop-down arrow to select a media vault. This
media vault will be used to store the media associated
with this media set that meet the move and return time
periods.
Before the media location can be updated, even if the
move and return dates are overdue, you must run the
task Update vault using wizard (see “Using the Vault
Wizard to move media” on page 293). This wizard can
print reports that detail which media are ready to move to
and return from the vault, and can update the location of
the media if you choose to move them. However, you must
physically collect the media, and move the media to and
from the vault.
Specify a time period after which this media will be
reported as ready to be moved to this vault.
Specify a time period after which this media will be
reported as ready to be returned from this vault.
The Media Set Wizard guides you through the process of creating a new media set, and
may be helpful if you are new to Backup Exec or are unfamiliar with the concepts and
terminology of media sets. Before you run this wizard, you should understand media
overwrite protection and append periods. For an overview of these terms, see “Media
overwrite protection” on page 260. If you do not need a wizard to set up a new media set,
see “Creating media sets” on page 264.
266 Administrator’s Guide

To run the Media Set Wizard
1. On the Tools menu, point to Wizards.
Chapter 6, Managing media
Media overwrite protection
2. Click Media Set Wizard, and then follow the instructions.
If you set the media overwrite protection level to Full, you must have blank media
ready and online before the first backup job runs. If you plan to use imported media,
you must inventory it first.
Deleting a media set
Use Delete to remove a media set from the Media Sets category. If you delete a media set
to which scheduled jobs are targeted, you are prompted to retarget the jobs to another
media set.
You cannot delete a media set that has associated media. You must associate the media
with another media set first.
Caution Make sure that the media set to which you associate the media has the
appropriate overwrite protection and append periods.
To delete a media set
1. On the navigation bar, click Media.
2. In the Media selection pane, under Media Sets, select the media set that you want to
delete.
3. Under General Tasks on the task pane, click Delete.
4. Click Yes to delete the media set, or if you selected multiple media sets to delete,
click Yes to All to delete all the selected media sets without further prompting.
5. If there are scheduled jobs allocated to the deleted media set, you are prompted to
redirect the jobs to another media set.
6. In the Media Set selection box, click the Down arrow to see more options, and then
select the new media set to which you want to redirect the scheduled jobs.
7. Click Yes to redirect the displayed job to the selected media set, or if there are
multiple scheduled jobs, click Yes to All to redirect all scheduled jobs to this media
set without further prompting.
The scheduled jobs are redirected.
267

Media overwrite protection
Renaming a media set
When you rename a media set, any jobs that use that media set will display the new
media set name.
To rename a media set
1. On the navigation bar, click Media.
2. In the Media selection pane, under Media Sets, select the media set you want to
rename.
3. Under General Tasks on the task pane, click Rename.
4. In the Name field, type the new name you want to assign to this media set, and then
click OK.
Changing general media set properties
On general media set properties, you can change the:
■ Name of a media set
■ Overwrite protection and append periods for a media set
■ Media vault and the vaulting periods associated with a media set.
To change general media set properties
1. On the navigation bar, click Media.
2. In the Media selection pane, under Media Sets, select a media set.
3. Under General Tasks on the task pane, click Properties.
4. To change the media set name or overwrite or append periods, click the General tab.
5. Select the appropriate options as follows, and then click OK:
Name View or change the media set name.
When you rename a media set, any jobs that use that media
set will display the new media set name.
See “Renaming a media set” on page 268.
268 Administrator’s Guide

Chapter 6, Managing media
Creation date Date when the media set was created.
Overwrite protection
period
Media overwrite protection
Enter the length of time, in hours, days, weeks, or years to
retain the data on the media before the media can be
overwritten (unless the media is erased, formatted, labeled,
associated with Scratch Media, or if the media overwrite
protection level is set to None).
The overwrite protection 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.
For example, setting the overwrite protection period for
seven days and the append period for four days ensures that
data will not be overwritten for at least seven days, and that
data can be appended to the media for the next four days. The
last data appended to this media is retained for seven days.
Because of the method Backup Exec uses to compute time, the
unit of time that you enter may be converted. For example, if
you enter 14 days, the next time you view this property, it
may be displayed as two weeks.
The default is Infinite - Don’t Allow Overwrite, which
protects the media from being overwritten for 1,000 years,
unless the media is erased, formatted, labeled, associated
with Scratch Media, or if the media overwrite protection level
is set to None.
Append period Enter the length of time, in hours, days, or weeks, that data
may be added to the media. Because of the method Backup
Exec uses to compute time, the unit of time that you enter
may be converted. For example, if you enter 14 days, the next
time you view this property, it may be displayed as two
weeks.
The append period starts when the first backup job is written
to this media.
The default is Infinite - Allow Append which allows data to
be appended until the media capacity is reached.
Note Symantec Backup Exec for Windows Servers 11d does
not support appending to tapes or backup-to-disk
folders that contain backup sets created by a previous
version Backup Exec.
269

Media overwrite protection
Media overwrite protection levels
The media overwrite protection level is a global setting that supersedes the media set’s
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 media’s overwrite protection period.
Use the media overwrite protection level to specify the type of media, such as scratch or
imported media, that you want to be available for overwrite backup jobs.
The options for the media overwrite protection level are:
■ Full - Overwrites scratch media, which are media that contain data you are willing to
discard, and recyclable media, which are media that are associated with media sets
and have expired overwrite protection periods.
■ Partial - Overwrites imported media, which are media that was created by another
installation of Backup Exec or some other backup product, and overwrite scratch
media.
■ None - Overwrites all media, including those that have current overwrite protection
periods (allocated media).
Caution The None option is not recommended. It does not protect data from being
overwritten.
Section 1 in the figure “Media overwrite protection” on page 273 illustrates the media
overwrite protection level.
Related Topics:
“Media locations and vaults” on page 286
Media overwrite protection on page 260
Setting the search order for overwritable media
Media overwrite options set the order in which Backup Exec searches for overwritable
media. When Backup Exec searches for overwritable media for a backup job, it searches
for either scratch media or media that has an expired overwrite protection period. You
are prompted to select the type of media that you want Backup Exec to use first:
■ Overwrite scratch media before overwriting recyclable media contained in the
targeted media set.
270 Administrator’s Guide

Chapter 6, Managing media
Media overwrite protection
If you choose to overwrite scratch media before recyclable media, more media may be
required for the same number of jobs, but the recyclable media may be preserved
longer for possible recovery.
■ Overwrite recyclable media contained in the targeted media set before overwriting
scratch media.
If you choose to overwrite recyclable media before scratch media, you will re-use the
same media more frequently than if you choose to overwrite scratch media before
recyclable media.
In a device pool, Backup Exec selects the oldest recyclable media in all of the devices in
the device pool to use first.
In a robotic library, Backup Exec selects the oldest recyclable media in the library to use
first. If the robotic library is partitioned, Backup Exec searches for the oldest recyclable
media in the targeted partition only.
Caution It is recommended that you physically write-protect media containing critical
data by using the write-protect tab on the media cartridge to protect against
unintentional move or erase operations, or expired overwrite protection
periods.
The following table describes the order in which Backup Exec searches for media to use
for an overwrite job, depending on the combination of the overwrite protection level and
the media overwrite option you select.
How Backup Exec searches for overwritable media
Overwrite protection level and overwrite
option:
Full + Overwrite scratch media first
Note This combination provides the most
protection against overwriting media.
Media is overwritten in this order:
1. Scratch media
2. Recyclable media in the targeted media set
3. Recyclable media in any media set
Full + Overwrite recyclable media first 1. Recyclable media in the targeted media set
2. Scratch media
3. Recyclable media in any media set
Partial + Overwrite scratch media first 1. Scratch media
2. Recyclable media in the targeted media set
3. Recyclable media in any media set
4. Imported media
271

Media overwrite protection
How Backup Exec searches for overwritable media (continued)
Overwrite protection level and overwrite
option:
Partial + Overwrite recyclable media first 1. Recyclable media in the targeted media set
2. Scratch media
3. Recyclable media in any media set
4. Imported media
None - No overwrite protection + overwrite
scratch media first
Caution This option is not recommended
because it does not protect data from being
overwritten.
None - No overwrite protection + overwrite
recyclable media first
Caution This option is not recommended
because it does not protect data from being
overwritten.
Media is overwritten in this order:
1. Scratch media
2. Recyclable media in the targeted media set
3. Recyclable media in any media set
4. Imported media
5. Allocated media in any media set
1. Recyclable media in the targeted media set
2. Scratch media
3. Recyclable media in any media set
4. Imported media
5. Allocated media in any media set
272 Administrator’s Guide

Media overwrite protection
Recyclable Media
(current user media sets)
Scratch Media
Recyclable Media
(other media sets))
Imported Media
Allocated Media
Chapter 6, Managing media
Media Overwrite Options
Media Overwrite Option can
reverse these, causing the
Scratch media set to be examined
second rather than first.
Media overwrite protection
The most obvious candidates for backup jobs requiring overwritable media are scratch
media and recyclable media (media with expired overwrite protection periods). These are
the first types of media for which Backup Exec searches when a backup requires media to
overwrite. The search pattern is different according to whether you have chosen Full,
Partial, or None. The media indicate that a type of media set is examined for availability.
In addition to setting overwrite protection levels, you must set overwrite options, which
set the order in which Backup Exec searches for overwritable media.
Related Topics:
“Media locations and vaults” on page 286
2
With the Media Overwrite Options,
you can make Backup Exec favor
scratch media over the expired
(recyclable) media in the Media Set of
the current job (on the right side of
this page), or favor the latter over the
former (on the left of this page).
1
1
2
Scratch Media
Recyclable Media
(current user media
Recyclable Media
(other media sets)
Imported Media
Allocated Media
Media Overwrite
Protection Level
Media Overwrite Protection
None Partial Full
When Backup Exec is unable to locate usable media,
it prompts you to provide one.
1
273

Setting defaults for media management
About overwriting allocated or imported media
Backup Exec protects allocated and imported media from being overwritten when full or
partial overwrite protection is used. However, if necessary, you can allow allocated and
imported media to be overwritten by Backup Exec before the data overwrite protection
period expires, and without setting the media overwrite protection level to None. Several
methods are available:
■ Move the media to Scratch Media. The media is overwritten when it is selected for an
overwrite job.
■ Erase the media. Erased media is automatically recognized as scratch media and will
be overwritten immediately.
■ Label the media. The Label Media operation immediately writes a new media label on
the media, which destroys any data contained on the media.
■ Format the media. Formatting destroys any data contained on the media.
■ Change the overwrite protection period for the media set so that it is expired. Select
the media set, and then under General Tasks, click Properties.
Related Topics:
“Deleting media” on page 296
“Changing general media set properties” on page 268
“Setting the search order for overwritable media” on page 270
Setting defaults for media management
Use this procedure to set defaults for the media overwrite protection level, the media
overwrite options, and media labeling.
To set defaults for media management
1. On the Tools menu, click Options.
2. On the Properties pane, under Settings, click Media Management.
274 Administrator’s Guide

3. Select the appropriate options as follows:
Chapter 6, Managing media
Full - protect allocated and
imported media
Partial - protect only
allocated media
Prompt before overwriting
imported media
None
Caution This option is
not recommended
because it does not
protect data from
being overwritten.
Prompt before overwriting
allocated or imported
media
Setting defaults for media management
Select this option to protect media in media sets and imported
media from being overwritten. See “Media overwrite protection
levels” on page 270.
This is the safest option to choose because the media being
protected cannot be overwritten until:
◆ The overwrite protection period for the media expires.
◆ You move media that belongs to an active media set to
Scratch Media.
◆ You erase, format, or label the media.
◆ You move media from Imported Media to Scratch Media.
Select this option to allow imported and scratch media to be
overwritten. Media in a media set that has an overwrite
protection period that has not expired (allocated media), cannot
be overwritten.
This option is recommended if you have media from an earlier
version of Backup Exec or another product (imported media)
that you want to reuse.
Select this option to be prompted before Backup Exec overwrites
imported media when Partial has been selected.
Note The job will not run until you respond to this prompt.
Select this option to disable the media overwrite protection
feature. With this option, you are responsible for making sure
that the media in your storage devices are not accidentally
overwritten.
For example, when an overwrite job is submitted to a device, and
the media overwrite protection level is set to None, the media in
that device is overwritten.
If you selected None (no overwrite protection), it is highly
recommended that you select this option to be prompted before
overwriting allocated or imported media.
Note The job will not run until you respond to this prompt.
275

Setting defaults for media management
Overwrite scratch media
before overwriting
recyclable media
contained in the targeted
media set
Overwrite recyclable
media contained in the
targeted media set before
overwriting scratch media
Select this option to have Backup Exec overwrite scratch media
first when an overwrite job occurs. See “Setting the search order
for overwritable media” on page 270.
If no scratch media are found in any of the storage devices,
Backup Exec overwrites recyclable media in the targeted media
set.
If no recyclable media are found, Backup Exec automatically
searches for other media to overwrite. The media that is
overwritten depends on the level of overwrite protection that
you set (Full, Partial, or None). If you select this option, more
media may be required for the same number of jobs than if you
choose to overwrite recyclable media first.
Because this option affects the order in which Backup Exec
overwrites media, choosing to overwrite scratch media first may
allow the recyclable media to be preserved longer for possible
recovery.
Select this option to have Backup Exec overwrite recyclable
media in the targeted media set when an overwrite job occurs.
If no recyclable media are found in any of the storage devices,
Backup Exec overwrites scratch media.
If no recyclable or scratch media are found, Backup Exec
automatically searches for media to overwrite. The media that is
overwritten depends on the level of overwrite protection that
you set (Full, Partial, or None). See “How Backup Exec searches
for overwritable media” on page 271.
If you choose to overwrite recyclable media in the targeted
media set first, you will re-use the same media more frequently
than if you choose to overwrite scratch media first.
Media type Select the type of media for which you want to create default
labels. See “Imported media labeling” on page 280.
For example, if you select 4mm, then all 4mm-type media that
are entered for the first time into this installation of Backup
Exec are assigned a label according to what you specify in the
following fields.
Prefix Displays the current default prefix for the selected cartridge
type. To specify a new prefix on the label, type from one to eight
alphanumeric characters.
276 Administrator’s Guide

Related Topics:
“Setting the search order for overwritable media” on page 270
“Media labeling” on page 278
Chapter 6, Managing media
Setting defaults for media management
Next value Displays the next number that will be included in the label of the
next media that matches the selected cartridge type when that
media is entered for the first time into this installation of
Backup Exec. This number is incremented by one each time a
media that matches the selected cartridge type is entered into
this installation of Backup Exec.
For example, if Cartridge type is set to 4mm, and Next value is
set to 1, the first time a 4mm media is entered into this
installation of Backup Exec, its label will include the number 1.
The label on the next 4mm media entered will include the
number 2.
To enter a new value, type from one to eight numeric characters.
This number must not exceed the number specified in the Digits
field.
Digits Displays the length of Next value, including placeholder zeroes.
This field defines the minimum size of the numeric portion of
the label.
For example, if Next value is set to 1, and Digits is set to 6, then
the Next value for the media label is 000001, 000002, 000003,
and so on.
If the Next value exceeds the entry in the Digits field, the extra
digit is added. Using the previous example, if label numbering
continued until 999,999, the next label would be 1,000,000 even
though the value specified in Digits is 6.
Rolling over the label numbering to 1,000,000 and 1,000,001
rather than 000,000 and 000,001 prevents the duplication of
labels.
The number entered in the Digits field must be in the range of
three to eight.
Default media vault Select the default vault that you want media moved to when a
job is run to move media to a vault or to export media. The
default media vault that you select here is displayed on the job
properties dialog box, in Options.
See “Scheduling a job to move media” on page 292 or “Exporting
expired media from a robotic library” on page 255.
277

Auditing media operations
Auditing media operations
Whenever media is overwritten, appended, erased, formatted, or labeled, the operation is
recorded in the Backup Exec database. You can review these entries in the audit log,
under the category Devices and Media. You can also run the Audit Log report to see what
operations were performed on media.
In the audit log, all operations for the Devices and Media category are enabled for logging
by default.
To view the audit log entries for media operations
1. On the Tools menu, click Audit Log.
2. In the Select category to view field, click Devices and Media .
3. View the entries in the Audit Log window.
To configure specific media operations for logging
1. On the Tools menu, click Audit Log.
2. On the Audit Logs dialog box, click Configure Logging.
3. Expand the Devices and Media category.
4. Select the operations that you want to log, or clear the check box of any item or
operation that you do not want to log.
5. Click OK.
Media labeling
Related Topics:
“Audit logs” on page 160
Media used in Backup Exec is identified by its media label. When new, blank, or
unlabeled 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 would be
4M, followed by 000001. The next media label generated for an unlabeled 4mm tape
would be 4M000002, and so on.
278 Administrator’s Guide

Chapter 6, Managing media
Media labeling
You can allow the media label to be assigned automatically by Backup Exec, or you can
specify a label prefix and number to be assigned for a type of media. For example, you
can specify that all 4mm media that are entered for the first time into this installation of
Backup Exec are labeled with a prefix of ACCT, and with numbering starting from 1000.
You can specify another media type to be labeled with a prefix of FIN, and with
numbering starting at 10,000. Customizing labels in this manner can help you recognize
and organize media.
Another type of media label used by Backup Exec is the media ID, which is a unique label
assigned by Backup Exec to individual media used in Backup Exec. The media ID is used
internally by Backup Exec in order to keep statistics on each media. Because the media
label or bar code label for media can be changed, Backup Exec must use the media ID,
which cannot be changed or erased, to preserve continuity in record keeping for each
individual media. 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 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 media’s
property page.
Write the media label on an external label fixed to the outside of the physical media.
Whenever you change the media label, you should also change the external label to
match.
Three methods are available in Backup Exec to change a media label:
■ Label Media operation. Writes a new media label on the media. This write operation
destroys any data on the media. This option is available on the Devices view.
■ Rename operation. 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.
■ Edit the label in the media’s property page. Editing the label 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.
Related Topics:
“Media locations and vaults” on page 286
“Labeling media” on page 246
“Bar code labeling” on page 280
“Renaming media” on page 282
“Viewing general media properties” on page 298
279

Media labeling
Imported media labeling
Backup Exec does not automatically relabel imported media. The imported media’s
existing label is read and displayed in the Media view, in one of the Imported Media sets.
Additionally, the imported media’s original media label is displayed under the heading
Media Description in the Results pane of the Media view. You can edit the media
description in the media’s property page to make it a more descriptive label.
If the media overwrite protection level is set to Partial or None, the imported media may
be selected for a job and be overwritten. The imported media is automatically labeled
when it is overwritten during a job.
If you want to label a specific imported media while maintaining full media overwrite
protection for other imported media, erase the specific media and then label it.
Related Topics:
“Viewing general media properties” on page 298
Bar code labeling
If there is a bar code label on the physical cartridge, and the cartridge is in a robotic
library that has a bar code reader, the bar code label automatically becomes the media
label.
You can change the media label in Backup Exec, but as long as the media has a bar code
label that can be read, the bar code label takes precedence over the media label. To use
the media label you entered using Backup Exec, you must remove the physical bar code
label from the media cartridge, or use the media in a device without a bar code reader.
Example
Robotic Library 1 has bar code support. During a backup operation, Backup Exec
requests a new or overwritable media for the operation. A new media with the bar
code label 'ABCD' is inserted in the robotic library magazine and the bar code reader
scans the bar code ID on the media label. Backup Exec selects this media for the
operation and detects that a bar code label has been assigned to the media. Backup
Exec automatically uses the bar code label and continues the operation.
When you change magazines or insert new media in a magazine, bar code readers allow
you to quickly update slot information by right-clicking the slot (or slots) and selecting
Scan.
Related Topics:
“Media labeling” on page 278
280 Administrator’s Guide

Bar code rules in mixed media libraries
Chapter 6, Managing media
Media labeling
If you have bar code support for a robotic library that uses different types of drives, you
can create a bar code rule so that Backup Exec can identify which media type to use in a
drive. When Backup Exec reads the bar code rule, it locates the type of media that
corresponds to the prefix or suffix and then mounts the media into a drive that accepts
that type of media.
After setting up bar code rules, you must set up two more items in order for the bar code
rules to work:
■ Enable the bar code rules for the robotic library by selecting the bar code rules
option on the Configuration tab in the robotic library’s properties.
■ For each drive in the mixed media library, indicate what type of media can be used
and whether that media can be used for read or write operations. To set this up, see
“Viewing and specifying types of media for a device” on page 205.
To create bar code rules in a mixed media library
1. On the Tools menu, click Options.
2. In the Properties pane, under Settings, click Bar Code Rules.
3. Click New.
4. Select the appropriate options as follows:
Select a media type Select the media for which you want to add a bar code rule.
Vendor (Optional) Type the name of this library’s manufacturer. You can find
the name of the library manufacturer on the library’s property page.
This field is not case-sensitive.
By typing a vendor name here, you restrict the bar code rule to that
vendor’s libraries. If you are creating a general bar code rule that
applies to libraries from different vendors, leave this field blank.
Bar code prefix Type a code to be placed before the bar code that represents a media
type. The code can be up to 16 characters, and any combination of
letters and numbers. This field is not case-sensitive.
Bar code suffix Type a code to be placed after the bar code that represents a media type.
The code can be up to 16 characters, and any combination of letters and
numbers. This field is not case-sensitive.
5. Click OK to save the bar code rule for the media.
281

Media labeling
6. Verify that bar code rules are enabled for the robotic library. The bar code rules do
not go into effect until you enable them for the robotic library. For more information,
see “Viewing robotic library configuration properties” on page 212.
To change a bar code rule
1. On the Tools menu, click Options.
2. In the Properties pane, under Settings, click Bar Code Rules.
3. Click Edit, and then change the options as needed.
4. Click OK to save the changes, and then click OK to exit.
To delete a bar code rule
1. On the Tools menu, click Options.
2. In the Properties Pane, under Settings, click Bar Code Rules.
3. Select a bar code rule to delete, and then click Delete.
4. Click Yes to verify that you want to delete the rule, and then click OK.
Renaming media
Use Rename to assign a new label to media. The new label is not actually written to the
media until an overwrite operation occurs. All data on the media is preserved until the
next overwrite job. However, the new media label is stored in the database and is
displayed for that media. To write a new media label to the media immediately, use Label
Media on the device’s property page. The media’s contents will be erased.
If you rename a media, and then use it in another installation of Backup Exec, that media
is treated as imported media, and the media’s original media label is displayed; the
renamed label is not transferred to other installations of Backup Exec.
To rename media
1. Do one of the following:
■ If the media is in a device, then from the navigation bar, click Devices, and then
click that device to display the media.
■ If you don’t know where the media is, from the navigation bar, click Media, and
then click All Media to display all media.
282 Administrator’s Guide

2. Select the media you want to rename.
3. Under General Tasks in the task pane, click Rename.
4. In Name, type a new media label, and then click OK.
Chapter 6, Managing media
About WORM media
5. Write this media label on an external label fixed to the outside of the physical media.
Related Topics:
“Viewing general media properties” on page 298
About WORM media
Write once, read many (WORM) data storage is used for archiving data that requires a
long retention period. Data can be written to WORM media one time only. After that, the
media can be appended to, but it cannot be overwritten, erased, or reformatted.
When WORM media is used in a media set, the overwrite protection period is not applied
to it, but the append period is applied.
New WORM media is WORM media that has not been written to. When new WORM
media is introduced into Backup Exec, it is placed in the Scratch Media set.
After the WORM media has been written to one time, you cannot move it to the Scratch
media set. You can move WORM media to the Retired Media set to delete it from Backup
Exec, but you cannot erase it or reformat it.
You can use WORM media for ad hoc backup jobs and for backup jobs created from
policies. When you select the option Use Write once, read many (WORM) media, Backup
Exec confirms that the destination device is or contains a WORM-compatible drive, and
that the WORM media is available in the drive. If WORM media or a WORM-compatible
drive is not found, an alert is sent.
Related Topics:
“Device and media options for backup jobs and templates” on page 354
283

Cataloging media while reviewing devices or media
Cataloging media while reviewing devices or media
Catalog media in order to:
■ Log the contents of a media created by a product other than this installation of
Backup Exec (imported media)
■ Create a new catalog on the local hard drive if the catalog for the media no longer
exists.
Before you can restore data from media or verify it, the media, including backup-to-disk
files, must have a catalog. If the media is being used by this computer for the first time,
you may need to inventory the media first (see “Inventorying media” on page 238).
To catalog media while reviewing devices or media
1. On the navigation bar, click Media or Devices.
2. Select the media set or location that is associated with the media to be cataloged, or
select the device containing the media to be cataloged, and then select the media
that you want to catalog.
3. On the task pane, under Media Tasks, click Catalog media.
4. Select the appropriate options as follows:
Device Select the device on which this job will run.
Password If this media is password protected and is being cataloged
by this system for the first time, enter the password.
Confirm Password If this media is password protected and being cataloged by
this system for the first time, type the password again.
5. On the Properties pane, under Settings, click General.
6. Select the appropriate options as follows:
Job name Type a name for the job or accept the default name.
284 Administrator’s Guide

Chapter 6, Managing media
Cataloging media while reviewing devices or media
Job priority Select the priority level for this job. If another job is scheduled to
run at the same time as this job, the priority you set determines
which job runs first. Your choices are:
◆ Highest
◆ High
◆ Medium
◆ Low
◆ Lowest
7. If you want a person or group to be notified when the job completes, on the
Properties pane, under Settings, click Notification, and then select the options you
want (see “Assigning notification recipients for completed jobs” on page 565).
8. Do one of the following:
To run the job now Click Run Now.
To set the scheduling
options you want to use
You can monitor or cancel the catalog job on the Job Monitor.
9. If the job requires that media be inserted into a robotic library, you are prompted to
create an Import Library job (see “Importing media to a robotic library” on page 249).
When you create the Import Library job, under Import Job Properties, click Options,
and then select Auto-inventory after import is completed.
Related Topics:
“Restore jobs and the catalog” on page 484
“Setting catalog defaults” on page 485
“Selecting data to restore” on page 508
“Canceling a restore job” on page 524
On the Properties pane, under Frequency, click Schedule.
(see “Scheduling jobs” on page 368).
285

Creating a restore job while reviewing media or devices
Creating a restore job while reviewing media or devices
You can create a restore job while reviewing media or devices in Backup Exec. You must
catalog the media before you can select the files that you want to restore.
The catalog for media that was backed up at other Backup Exec installations does not
exist on the media server. You must catalog media that was backed up at other Backup
Exec installations on the local media server before you can view data in the Restore Job
Properties dialog box.
Creating a restore job while reviewing media or devices
1. On the navigation bar, click Media or Devices.
2. Double-click the media set or location that is associated with the data to be restored.
3. Select the media that you want to restore.
4. On the task pane, under Media Tasks, click Restore data.
5. Go to “Restoring data by setting job properties” on page 488 for details on selecting
restore job properties.
6. If the job requires that media be inserted into a robotic library, you are prompted to
create an Import Library job (see “Importing media to a robotic library” on page 249).
When you create the Import Library job, under Import Job Properties, click Options,
and then select Auto-inventory after import is completed.
Related Topics:
“Cataloging media while reviewing devices or media” on page 284
Media locations and vaults
Media in Backup Exec can be located in any of the following:
■ Online media. This location lists media that reside in a storage device, robotic library
slot, or backup-to-disk folder. Online media is defined by Backup Exec, so you cannot
delete or rename it, and you cannot add or move media to it.
Note If you move media from the online media location, its overwrite protection period
and append period remain in effect.
286 Administrator’s Guide

Chapter 6, Managing media
Media locations and vaults
■ Offline media. This location displays all media that are onsite but are not in devices
or slots, or media vaults. Media are automatically moved to this location if you use
Backup Exec to remove media from a device or slot. You can add media to the offline
location from another media location. To move offline media back to online, run an
inventory of the devices or slot, or catalog the media. You cannot delete or rename
the offline location.
■ User-defined media vault. A media vault is a logical representation of the actual
physical location of media. You can create media vaults to keep track of where media
is physically stored, such as a special media room, a scratch bin, or an offsite
location. For example, you could create a media vault where media to be sent offsite
are moved. Then, print the Media Vault Contents report, which lists the media
contained in that vault, to accompany the physical media to their offsite storage. You
can also create vault rules to help you track when media should be moved to or
returned from a vault.
Related Topics:
“Finding media in a location or vault” on page 289
“Configuring vault rules for media sets” on page 288
“Using the Vault Wizard to move media” on page 293
“Renaming a media vault” on page 289
“Moving media to a vault or to the offline media location” on page 290
“Deleting a media vault” on page 290
“Media Vault Contents Report” on page 632
Creating media vaults
Create a media vault so that you can track media that are stored in specific sites.
To create a media vault
1. On the navigation bar, click Media.
2. Under Media Location Tasks on the task pane, click New media vault.
3. Type the name and a description of the new vault.
4. Click OK.
The new vault is displayed under Media Location in the Media view.
287

Media locations and vaults
Configuring vault rules for media sets
On the vault rule properties for media sets, you can add or change:
■ The media vault to which you want to send media that are associated with this
media set.
■ The amount of time to wait between when the media is allocated and when it is sent
to the vault.
■ The amount of time to wait between returning the media from the vault and when it
was last written to.
Backup Exec does not update the vault automatically. You must use the Update vault
using wizard task to print or view reports that contain details on which media are ready
to be moved to and from the vault, and to update the media location. You can also
schedule a job called Move Media to a Vault to export media from a device, and update
the media location for any media that are moved to a vault.
To configure vault rules for media sets
1. On the navigation bar, click Media.
2. In the Media selection pane, under Media Sets, select a media set.
3. Under General Tasks on the task pane, click Properties.
4. Click the Vault Rules tab.
5. Select the appropriate options as follows, and then click OK:
Select the media vault to use with
this media set:
Select a media vault. This media vault will be used to
store the media that are associated with this media set
and that meet the move and return time periods.
Before Backup Exec can update the media location, even
if the dates to move to or return from the vault are
overdue, you must run the task Update vault using
wizard.
See “Using the Vault Wizard to move media” on page 293.
This wizard can print reports that detail which media are
ready to move to and return from the vault, and can
update the location of the media if you choose to move
them. However, you must physically collect the media,
and move the media to and from the vault.
288 Administrator’s Guide

Related Topics:
“Using the Vault Wizard to move media” on page 293
“Moving media to a vault or to the offline media location” on page 290
“Creating media sets” on page 264
Chapter 6, Managing media
Move media to this vault x after it
is allocated (first written to or
overwritten).
Return media from this vault x
after it is last written to.
Finding media in a location or vault
Media locations and vaults
You can find where media is located by searching for the name on the media label.
To find media in a location or vault
1. On the navigation bar, click Media.
2. On the Media selections pane, click Media Location.
3. Under Media Location Tasks on the task pane, click Find media.
4. Type the name from the media label of the media you want to find, and then click
OK.
The location of the media is highlighted and its properties are displayed in the
preview pane.
Renaming a media vault
You can rename a media vault. You cannot rename the Backup Exec Media Location
defaults Online Media and Offline Media.
To rename a media vault
1. On the navigation bar, click Media.
Specify a time period after this media is first written to or
used in an overwrite job when it will be reported as ready
to be moved to this vault.
Specify a time period after this media is last written to
when it will be reported as ready to be returned from this
vault.
2. On the Media selections pane, click the media vault that you want to rename.
289

Moving media to a vault or to the offline media location
3. Under General Tasks in the task pane, click Rename.
4. Type the new name, and then click OK.
Deleting a media vault
You can delete an empty media vault. If there is any media in the vault, you must move it
before you can delete the vault. You cannot delete the online or offline locations.
To delete a media vault
1. On the navigation bar, click Media.
2. Select the media vault that you want to delete.
3. Under General Tasks in the task pane, click Delete.
4. Click Yes to delete, or if you are deleting multiple vaults, click Yes to All to delete
without prompting for each vault.
Moving media to a vault or to the offline media location
Several operations are available for you to logically move media to a vault or to the
offline media location. Some move operations also prompt you to export the media as
part of the operation. While these operations logically move the media, you must
physically move the media to an actual location that is represented by the vault name.
Move media to a vault or to the offline media location using any of the following
methods:
Moving media
How to move media to a vault or
the offline media location
Scan the bar code label or type
the media label to logically move
media to a vault or to the offline
media location.
For more information
“Scanning bar code labels to move media” on page 291
290 Administrator’s Guide

Moving media
How to move media to a vault or
the offline media location
Schedule a job to logically move
media to a vault after it is
successfully exported from a
device.
In a policy, create a job template
to export media.
Run the Vault Wizard to export
media from a device and to
logically move media to a vault.
Drag and drop media to a vault or
to the offline media location, and
then export the media from the
device.
Click the Move to vault task to
logically move media to a vault or
to the offline media location.
Scanning bar code labels to move media
Chapter 6, Managing media
Moving media to a vault or to the offline media location
If you have a bar code scanner, this is an efficient method for moving media to a vault or
to the offline media location. You can also type a media label into the dialog box.
To scan bar code labels to move media
1. On the navigation bar, click Media.
2. In the Media selections pane, select the media location or vault to which you want to
move media.
3. In the task pane, under Media Location Tasks in the task pane, click Add media to
selected vault.
4. Scan the bar code label, or type the media label, for the media you want to move to
this vault.
5. Click OK.
For more information
“Scheduling a job to move media” on page 292
“Adding an export media template to a policy” on page 424
“Using the Vault Wizard to move media” on page 293
“Using the drag and drop method to move media” on page 294
“Using the Move to vault task to move media” on page 295
291

Moving media to a vault or to the offline media location
6. Repeat steps 4 and 5 for all the media you want to add.
7. Click OK.
Related Topics:
Moving media to a vault or to the offline media location on page 290
Scheduling a job to move media
If you set up vault rules for a media set, you can schedule a job called Move Media to
Vault. This job exports the media from the device, and then logically moves the media to
the specified vault.
You can specify a vault for a media set in the media set vault rules, or you can specify a
default vault.
There must be an existing user-defined media vault under the Media Location node in
the Media view. To create a media vault, see “Creating media vaults” on page 287.
To schedule a job to move media
1. On the navigation bar, click Job Setup.
2. On the task pane, under Backup Strategy Tasks, click New job to move media to a
vault.
3. Select the appropriate options as follows:
Job name Type a name for the job or accept the default name.
Job priority Select the priority level for this job. If another job is scheduled to
run at the same time as this job, the priority you set determines
which job runs first. Your choices are:
◆ Highest
◆ High
◆ Medium
◆ Low
◆ Lowest
4. To move the media to a media vault after a successful export, on the Properties pane,
under Settings, click Options, and select a media vault.
292 Administrator’s Guide

Chapter 6, Managing media
Moving media to a vault or to the offline media location
5. If you want a person or group to be notified when the job completes, on the
Properties pane, under Settings, click Notification, and then select the options you
want (see “Assigning recipients to alert categories for notification” on page 564).
6. If you want to run the job now, click Run Now. Otherwise, on the Properties pane,
under Frequency, click Schedule to set the scheduling options you want to use (see
“Scheduling jobs” on page 368).
You can monitor or cancel the job on the Job Monitor.
Related Topics:
Moving media to a vault or to the offline media location on page 290
Using the Vault Wizard to move media
Use the Vault Wizard to print or view reports that contain details on which media are
ready to be moved to and from a vault, and to update vaults.
After a vault is updated, if Backup Exec detects a robotic library, you are prompted to
export media. If you choose to export the media, an Export Media job runs (see
“Exporting expired media from a robotic library” on page 255).
Note If your environment includes remote sites, you should create separate media sets
for each remote site, so that if vault rules are enabled, the reports contain details
on which media are ready to be moved for just that site.
To specify vault media rules when creating a new media set, see “Creating media sets” on
page 264. To change vault media rules for an existing media set, see “Configuring vault
rules for media sets” on page 288.
To use the Vault Wizard to move media to a vault
1. On the navigation bar, click Media.
2. Select the vault that you want to update.
3. Under Media Location Tasks on the task pane, click task Update vault using wizard.
The Vault Wizard appears.
4. Follow the instructions on the wizard.
Related Topics:
“Creating media sets” on page 264
293

Moving media to a vault or to the offline media location
“Configuring vault rules for media sets” on page 288
Moving media to a vault or to the offline media location on page 290
Using the drag and drop method to move media
To move media to a vault or to the offline media location, drag and drop it from one
location to another location. The drag and drop method also prompts you to export the
media from a device.
The following table lists the drag-and-drop rules for media:
Note If you move media from an online location, its overwrite protection period and append
period remain in effect.
Media Drag-and-Drop Rules
From/To Online
Location
Online
location
Offline
location
User-defined
vault
Media
Pools/Sets
Offline
Location
No Yes, with a
warning that
the media is
not
physically
moved from
the online
location.
Media Vaults Media
Pools/Sets
Yes, with a
warning that
the media is
not
physically
moved from
the online
location.
No No
No No Yes No No
No Yes Yes No No
No Yes, with a
warning
All Media No Yes, with a
warning that
the media is
not
physically
moved from
the online
location.
Yes, with a
warning
Yes, with a
warning that
the media is
not
physically
moved from
the online
location.
Yes No
Yes No
All Media
294 Administrator’s Guide

To use the drag and drop method to move media
1. On the navigation bar, click Media.
Chapter 6, Managing media
Moving media to a vault or to the offline media location
2. On the Media selections pane, click the vault containing the media.
3. Select the media from the Results pane, and drag it to the new location.
4. When you are prompted to export the media, click Yes or Yes to All.
An Export Media job runs, and then you are prompted to remove the media from the
device.
Related Topics:
Moving media to a vault or to the offline media location on page 290
Using the Move to vault task to move media
You can select media in the Media view, and then open a dialog box and choose a vault or
the offline media location to move the media to. The media location is updated, but the
media is not ejected or exported.
To use the Move to vault task to move media
1. On the navigation bar, click Media.
2. Expand All Media to display a list of media, and then select the media that you want
to move to a media vault.
3. Under Media Tasks on the task pane, click Move to vault.
4. Select a media vault to which you want to move this media, and then click Yes or Yes
to All.
The media location is updated.
Related Topics:
“Exporting expired media from a robotic library” on page 255
Moving media to a vault or to the offline media location on page 290
295

Removing damaged media
Removing damaged media
Media that meets or exceeds the discard thresholds determined by the media
manufacturer should be associated with the Retired Media media set. Based on a
measurement of soft errors generated by the storage device firmware, media that
exceeds acceptable levels of these errors are reported to Backup Exec as potential
candidates to be discarded.
To decide which media to retire, run a Media Sets report to see the total number of errors
for media, or view the properties for a specific media.
Associate any media with an unacceptable level of errors to Retired Media so that you are
protected against using defective media before critical backup operations begin. After
you mark media as retired, it will not be used by Backup Exec for future backup jobs. The
media is still available to be restored from if it is not damaged.
Related Topics:
“Deleting media” on page 296
“Viewing media statistics” on page 299
“Failed Backup Jobs Report” on page 625
Deleting media
Media can only be deleted from Backup Exec when it is part of the Retired Media set.
You may want to delete media when:
■ You have a lot of offsite media that you do not want to recycle.
■ You throw away damaged or old media.
Media can only be deleted from Backup Exec after it has been associated with the
Retired Media set.
When deleted media is reused in Backup Exec, it is recognized as imported media. Before
you can restore from the media, you must catalog it.
Note Deleting media from Backup Exec is not the same operation as erasing media.
To delete media
1. On the navigation bar, click Media.
2. Associate the media that you want to delete with the Retired Media set by doing one
of the following:
296 Administrator’s Guide

Chapter 6, Managing media
■ Drag the media to the Retired Media icon.
Associating media with a media set
■ Under Media Tasks on the task pane, click Associate with media set, select the
Retired Media set to associate the media with, and then click Yes or Yes to all.
3. Double-click the Retired Media icon, and then select the media that you want to
delete.
4. Under General Tasks in the task pane, click Delete.
If Delete is unavailable, the media is not associated with the Retired Media set. You
must associate the media with Retired Media before Delete is available.
5. Click Yes or Yes to All to delete the media that are displayed.
Related Topics:
“Viewing media statistics” on page 299
“Failed Backup Jobs Report” on page 625
Associating media with a media set
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.
To associate media with a media set
1. On the navigation bar, click Media.
2. Expand All Media to display a list of media.
3. Select the media that you want to associate with a media set.
4. Do one of the following:
■ Drag the media to the media set.
■ Under Media Tasks on the task pane, click Associate with media set, select a
media set to associate the media with, and then click Yes or Yes to all.
The media is associated with the selected media set.
297

Viewing general media properties
Viewing general media properties
To view media properties
1. On the navigation bar, click Media.
2. Expand the All Media icon, and then select the media that you want to view.
3. Under General Tasks on the task pane, click Properties.
The General Media Properties tab provides the following information:
Media label Media label that was assigned automatically by Backup Exec, or
that was assigned or changed by the administrator, or that was a
pre-assigned bar code label.
You can edit the media label, which is limited to 32 characters.
Editing the label changes the name of the media in the display,
but does not write the new label to the media until an overwrite
operation occurs. When you edit a media label, try to make it a
concise identifier that will remain constant even when the
media is reused. You should write this media label on a label
fixed to the outside of the physical media.
Duplicate labels can be automatically generated. For example,
reinstalling Backup Exec or bringing media from another
Backup Exec installation could cause duplication in labels.
Duplicate labels are allowed, but not recommended.
Note If a bar code is available, and a bar code-equipped device is
used, then the media label automatically defaults to that
bar code.
Description By default, displays the original media label if the media is
imported media.
You can edit the media description, which is limited to 128
characters, to make it a more descriptive label.
Media type Media type and subtype (if available). Click the button next to
the field to change the media type or subtype.
Export pending When a template runs that has an associated export template to
export this media, Yes is displayed; otherwise, No is displayed.
See “Adding an export media template to a policy” on page 424.
Media set Name of the media set this media belongs to.
298 Administrator’s Guide

Related Topics:
“Media labeling” on page 278
“Creating a test run job” on page 385
“Viewing media in storage devices” on page 170
“Viewing media statistics” on page 299
Viewing media statistics
To view media statistics
1. On the navigation bar, click Media.
Chapter 6, Managing media
Viewing general media properties
Media location Name of the device or vault where this media is located.
Creation date Date and time when the media was first entered into Backup
Exec.
Allocated date Date and time when the media was added to a media set as a
result of an overwrite operation.
Modified date Date and time when data was last written to the media.
Overwrite protection until Date and time after which the media can be overwritten.
Appendable until Date and time after which the media can no longer be appended
to.
2. Expand the All Media icon, and then select the media that you want to view.
3. Under General Tasks in the task pane, click Properties.
4. Select the Statistics tab.
The Statistics tab provides the following information:
Hours in use The total number of hours that this media has been in use.
Used capacity The amount of raw capacity on the media that has been used. Used
Capacity is calculated by subtracting Available Capacity from
Total Capacity.
Used Capacity may or may not equal Bytes Written.
299

Viewing general media properties
Available capacity The amount of expected raw capacity on the media that remains
unused. Some tape devices support the ability to read the amount
of remaining capacity of the media that is currently loaded in the
device. If a tape device supports reading of the remaining capacity
amount, then Available Capacity is derived from the remaining
capacity amount. Otherwise, Available Capacity is calculated by
subtracting Bytes Written from Total Capacity.
Because Free Space is reported in terms of unused raw capacity,
review Bytes Written and Compression Ratio to better estimate if
there is enough free space to accommodate a specific job.
Total capacity The amount of expected total raw capacity of the media. Some tape
devices support the ability to read the amount of total capacity of
the media that is currently loaded in the device. If a tape device
supports reading of the total capacity amount, then Total Capacity
is derived from the total capacity amount. Otherwise, Total
Capacity is estimated based on past usage of the media.
Compression ratio The ratio of Bytes Written to Used Capacity. Compression ratio
will show the overall effect that data compression and media flaws
are having on the amount of data that is being stored on the media.
Bytes written The amount of data that has been written into blocks on the media.
Bytes Written may differ from Used Capacity due to the effects of
data compression and media flaws. Data compression will tend to
increase Bytes Written when compared to Used Capacity. Media
flaws will decrease Bytes Written when compared to Used
Capacity.
Bytes read Number of bytes that have been read from this media.
Mounts Number of times this media has been mounted.
Seeks The total number of seek operations (performed when a specific
piece of information is being located) that have been performed on
this media.
Seek errors The number of errors encountered while trying to locate data.
Soft write errors The number of recoverable write errors encountered. If you receive
soft errors, it may indicate the beginning of a problem. If you
receive excessive errors for your environment, check the media for
damage.
Hard write errors The number of unrecoverable write errors encountered. If you
receive hard errors, check the media for damage.
300 Administrator’s Guide

Related Topics:
“Changing general media set properties” on page 268
“Creating media sets” on page 264
Media rotation strategies
Chapter 6, Managing media
Media rotation strategies
Soft read errors The number of recoverable read errors encountered. If you receive
soft errors, it may indicate the beginning of a problem. If you
receive excessive errors for your environment, check the media for
damage.
Hard read errors The number of unrecoverable read errors encountered. If you
receive hard errors, check the media for damage.
There are many media rotation strategies you can use to protect your data. They differ
mostly by the number of media required and by the amount of time the media is kept
before it is rotated back into the schedule. Three of the most commonly used media
rotation strategies are:
■ Son. Uses the same media each day to run a full backup. See “Son media rotation
strategy” on page 302.
■ Father/Son. Uses multiple media, includes a combination of weekly full and daily
differential or incremental backups for a two-week schedule, and provides backups
for offsite storage. See “Father/son media rotation strategy” on page 302.
■ Grandfather. Uses multiple media, includes a combination of weekly and monthly
full and daily differential or incremental backups, and provides backups for offsite
storage. See “Grandfather media rotation strategy” on page 303.
For information on how to create these strategies, see “Creating a new policy” on
page 416.
301

Media rotation strategies
Son media rotation strategy
Number of media required: 1 (minimum)
Overwrite protection period: last backup
The Son strategy involves performing a full backup every day. Although the Son strategy
is simple to administer, backing up with a single media is not an effective method of
backup. This is because magnetic media eventually wears out after many uses and the
data you can restore only spans back to your last backup.
Son Backup Strategy
Week 1
Father/son media rotation strategy
Mon Tue Wed Thu Fri
Media 1 Media 1 Media 1 Media 1 Media 1
Full Backup
Number of media required: 6 (minimum)
Overwrite protection period: Two weeks
The Father/Son media rotation strategy uses a combination of full and differential or
incremental backups for a two-week schedule.
In the Father/Son scenario, four media are used Monday through Thursday for
differential or incremental backups. The other two media containing full backups are
rotated out and stored offsite every Friday.
302 Administrator’s Guide

Father/Son Backup Strategy
Week 1
Week 2
Chapter 6, Managing media
Mon Tue Wed Thu Fri
Media 1
Media 1
Full Backup
Media 2
Media 2
Media 3
Media 3
Media rotation strategies
Note When this backup strategy is first implemented, you must start with a full backup.
The Father/Son strategy is easy to administer and allows you to keep data longer than
the Son strategy, but it is not suitable for the stringent data protection needs of most
network environments.
Grandfather media rotation strategy
Media 4
Media 4
Media 5
Media 6
Incremental or Differential
Backup
Number of media required: 19 (minimum)
Overwrite protection period: One year
The Grandfather method is one of the most common media rotation strategies. It is
simple to administer and comprehensive enough to allow easy location of files when they
need to be restored.
In the Grandfather scenario, four media are used Monday through Thursday for
incremental or differential backups; another three media are used every Friday for full
backups. The remaining 12 media are used for monthly full backups and are kept offsite.
303

Media rotation strategies
Grandfather Backup Strategy
Mon Tue Wed Thu Fri
Mon 1
Week 1
Tue 2 Wed 3 Thu 4 Fri 5
Week 2
Week 3
Week 4
Mon 1
Mon 1
Mon 1
Tue 2
Full Backup
Tue 2 Wed 3 Thu 4 Fri 6
Wed 3
Thu 4
The Grandfather strategy is recommended because it offers a good media number to
storage life ratio (19 media/1 year). It is also easy to modify if you want to incorporate
more media. For example, you could perform a full backup on the last Saturday of the
month to archive permanently.
304 Administrator’s Guide
Fri 7
Tue 2 Wed 3 Thu 4 Monthly
Incremental or
Differential
Backup

Preparing for backup
Chapter
Before you back up your data, you should become familiar with how to:
■ Use backup strategies
■ Select data to back up
■ Create user-defined selection lists
■ Protect specific types of data, such as Windows Server 2003 systems, utility
partitions, and EFI system partitions
About backup strategies
7
A backup strategy is the collection of procedures you implement for backing up your
network, including what methods of backups are performed, when backups are
performed, and how media is rotated back into use for your regular backups. A good
backup strategy allows minimal time to get a system up and running in the event of a
disaster.
Backup Exec offers flexible solutions for protecting the data on your network. Use the
media rotation feature and let Backup Exec do all the administrative work for you, or
design and manage your own media rotation strategy, the procedures for reusing media,
that meets your exact specifications.
You can create backup job templates that define your backup strategy, and then reuse the
templates to implement your strategy for all resources being protected by your media
server.
Related Topics:
“Media rotation strategies” on page 301
305

About backup strategies
Choosing a backup strategy
In order to develop a secure and effective plan for managing your data, you should
consider the following:
■ The importance of the data you are backing up.
■ How often your system needs to be backed up.
■ How much storage media you will use.
■ When you will use certain storage media.
■ How you will keep track of your backup information.
Before choosing a strategy to use with the Backup Exec system, you should answer the
following questions:
How often should I back up?
While there is no requirement on how often to back up your data, there is one
consideration that can help you decide: The cost of re-creating data that was added or
modified since the last backup.
Calculate the manpower, lost time and/or sales, and other costs that would be incurred if
the file server or workstation crashed right before the next backup was scheduled to take
place (always assume the worst scenario). If the cost is excessive, the strategy should be
adjusted accordingly.
For example, the cost to re-create an extensive database system that is continually
updated by several database operators would be quite substantial. On the other hand, the
cost to re-create the data for a user creating one or two inter-office memos would be
considerably less. In this scenario, the network administrator would probably opt to back
up the database several times daily, and set up daily jobs for the user’s workstation.
In an ideal environment, one full backup should be performed on workstations every day
and servers should be fully backed up more often. Important data files and directories
that constantly change may need to be backed up several times a day. Because of time
and media constraints, this is not feasible for many environments, so a schedule
including incremental or differential backups must be implemented. For safety reasons,
a full backup should always be performed before adding new applications or changing
the server configuration.
How much data must be backed up?
The amount of data to be backed up is a key determinant of the media rotation strategy
you choose. If you are backing up large amounts of data that needs to be retained on
media for long periods of time, you will need to select a strategy that is suitable for these
requirements.
306 Administrator’s Guide

Chapter 7, Preparing for backup
About backup strategies
How long does the data need to be stored?
The amount of time the data needs to be stored is directly related to the media rotation
scheme you use. For example, if you use one media and back up every day, your backups
will never be more than a day old.
Since storage media is relatively inexpensive when compared to the value of your data, it
is a good idea to periodically back up your system on media not used in the media
rotation scheme and store it permanently. Some administrators may choose to do this
every week, while others may choose to store only one permanent backup per month.
The threat of viruses is an issue also. Some viruses take effect immediately, while others
may take days or weeks to cause noticeable damage. Because of this, you should have at
least the following backups available to restore at any time:
■ 3 daily backups (for example, Monday, Tuesday, Wednesday).
■ A one-week-old full backup.
■ A one-month-old full backup.
Having these backups available should allow you to restore your system prior to when it
became infected.
Which devices am I backing up?
Since Backup Exec can back up servers, workstations, and agents, you should consider
which resources you want to protect. You will need to coordinate times that are suitable
to back up different resources. For example, you may want to back up file servers during
the evening and back up workstations at lunchtime.
Should I include more than one system in each job?
When you are setting up jobs for the network, you must decide if you want to create one
job that includes many resources or a job for each resource. Here are some of the
advantages and disadvantages of each method.
Advantages and disadvantages of including more than one system in a job
Method Advantages Disadvantages
One job per device ◆ If a job fails, you know
immediately which resource was
not backed up.
◆ If a resource is turned off or
moved, backups of other resources
are not affected.
◆ When resources are added to the
network you can simply set up
new jobs for each resource.
◆ You have more jobs
to keep track of (for
example, reviewing
job histories, and so
forth).
307

About backup strategies
Advantages and disadvantages of including more than one system in a job
Method (continued) Advantages Disadvantages
Multiple resources
per job
Understanding backup methods and their advantages
Before you can develop your media rotation strategy, you will need to decide whether you
want to perform only full backups or use a strategy that includes Full backups and one of
the modified backup methods (differential, incremental or working set backups).
The backup methods used by Backup Exec are:
■ Full. Includes all of the data that was selected for backup and uses the full backup
method. Backup Exec detects the device as having been backed up. You can use either
archive bit or modified time to determine if a file has been backed up.
Note You will need to perform a full backup of your server to establish a baseline for
disaster recovery.
Full backups also include Copy backups, which include all selected data and do not
affect any media rotation scheme because the archive bit is not reset. Copy backups
are useful when you need to:
■ Back up data for a special purpose (for example, to send to another site).
■ Back up specific data.
◆ There are fewer jobs to keep track
of and create.
◆ You know the order in which the
data is backed up.
◆ You could make it an overwrite job
and thus be able to use the same
name for the media and the job.
■ Perform an additional backup to take off-site.
◆ If any of the
resources in the job
are not available
during the backup,
the job results in an
abnormal
completion status.
■ Back up data that belongs to a media rotation job without affecting the rotation
cycle.
Another Full backup option is the archive backup option, which automatically
deletes files from the volume after they have been successfully backed up. This
backup method is designed for migrating data from disk to storage media and should
not be incorporated in a regular backup schedule.
308 Administrator’s Guide

Chapter 7, Preparing for backup
About backup strategies
Using the archive backup method allows you to free valuable disk space and reduce
clutter on your server volume by migrating stagnant directories and files from the
server to media. An archive backup job backs up the selected data, verifies the
media, and then deletes the data from the volume.
Note For data to be deleted, rights to delete a file must be granted; otherwise data will
be backed up but not deleted.
Backup Exec will not delete data from Backup Exec Agent workstations when
using the archive feature.
■ Differential. Includes all files that have changed since the last full or incremental
backup. The difference between differential and incremental backups is that
incremental backups include only the files that have changed since the last full or
incremental backup.
Backup Exec provides two differential backup methods, one that uses archive bit and
one that uses modified time to determine if the file was backed up. If you select to use
the Full - Back up files - Using archive bit (reset archive bit) and want to run
differential backups, you must use the Differential - Back up changed files since last
full - Using archive bit (does not reset archive bit) method. If you select to use the
Full - Back up files - Using modified time, you must use the Differential - Back up
changed files since last full - Using modified time method.
In most schemes, differential backups are recommended over incremental backups.
Differential backups allow much easier restoration of an entire device than
incremental backups since only two backups are required. Fewer required media also
decreases the risk of not being able to restore important data because of media
errors.
You should not mix differential and incremental backups together.
■ Incremental. Incremental backups include only the files that have changed since the
last full or incremental backup.
Backup Exec provides two incremental backup methods, one that uses archive bit
and one that uses modified time to determine if the file was backed up. If you select
to use the Full - Back up files - Using archive bit (reset archive bit) and want to run
incremental backups, you must use the Incremental - Back up changed files since
last full or incremental- Using archive bit (reset archive bit) method. If you select to
use the Full - Back up files - Using modified time, you must use the Incremental -
Back up changed files since last full or incremental - Using modified time method.
The advantages and disadvantages described in this section pertain to either type of
differential backup.
■ Working set. The working set backup option includes two options; Changed today
and Last accessed in x days. The Changed today option was called Daily backup in
previous versions of Backup Exec. You can perform backups using the Changed today
309

About backup strategies
method in addition to the media rotation scheme selected. The Changed today
method backs up all files with today’s date (created or changed today). The Changed
today method does not affect the files’ backup status because the archive bit is not
reset.
If you select the Last accessed in x days method, you can then indicate in the Files
accessed in x days field that you want to include data that has been accessed in a
specific number of days.
This option is similar to a differential backup, in which files that have been created
or changed since the last full backup are included; however, the difference lies in that
you can also specify to include all files accessed within the last x number of days.
This option can speed the recovery of a crashed server because you only need to
restore the working set backup to get up and running again, and then restore the
latest full backup at a later time (if necessary).
To effectively include the data needed to make your system operational after
restoring a working set backup, specifying at least 30 days in the Files accessed in x
days field is recommended. With a full/working set backup scheme, the non-full
backups will require more media space than full/differential or full/incremental
schemes. However, in environments where active data is migrated frequently
between machines, or when restore times are especially critical, working set backups
can make up the cost of extra media in time savings for restoring data.
There are advantages and disadvantages to each backup method.
Backup Method Advantages and Disadvantages
Method Advantages Disadvantages
Full ◆ Files are easy to find - Since full
backups include all data
contained on a device, you don’t
have to search through several
media to find a file that you need
to restore.
◆ There is always a current backup
of your entire system on one
media or
media set - If you should need to
restore your entire system, all of
the most current information is
located on the last full backup.
◆ Redundant backups - since most of
the files on your file server rarely
change, each full backup following
the first is merely a copy of what has
already been backed up. This
requires more media.
◆ Full backups take longer to perform -
Full backups can be time consuming,
especially when you have other
devices on the network that need to
be backed up (e.g., agent
workstations, remote servers).
310 Administrator’s Guide

Backup Method Advantages and Disadvantages
Method Advantages Disadvantages
Differential ◆ Files are easy to find - Restoring a
system backed up with a
differential strategy requires a
maximum of two backups - the
latest full backup and the latest
differential backup. This is less
time consuming than backup
strategies that require the latest
full backup and all incremental
backups created since the full
backup.
◆ Less time required for backup and
restore - Differential backups take
less time to restore than full
backups. Faster recovery is
possible in disaster situations
because you only need the latest
full and differential backup media
to fully restore a device.
Incremental ◆ Better use of media - Only files
that have changed since the last
backup are included, so there is
much less data storage space
required.
◆ Less time required for backup -
Incremental backups take much
less time than full and differential
backups to complete.
Chapter 7, Preparing for backup
About backup strategies
◆ Redundant backups - All of the files
created or modified since the last
incremental backup are included;
thus creating redundant backups.
◆ Backups are spread across multiple
media - Since multiple media is
required in a disaster situation, this
can cause recovery of a device to take
longer. In addition, the media must
be restored in the correct order to
effectively bring the system up to
date.
311

About backup strategies
Backup Method Advantages and Disadvantages
Method Advantages Disadvantages
Working Set ◆ Restoring a system backed up
with a working set strategy
requires only the media
containing the latest working set
backup media and the media
containing the most recent full
backup.
◆ You can perform a working set
backup, restore the data to a new
system, and be up and running
faster than if you had to restore a
full backup followed by all of the
incremental or differential
backups.
◆ Working set backups take less
time to run than full backups.
Understanding the archive bit and backup methods
◆ The Last accessed in (x) days method
is available only on platforms that
support the last accessed date
(Windows, NetWare, and UNIX).
Working set backups will work as
differential backups when selected
for other platforms.
Whenever a file is created or changed, the operating system activates the Archive Bit or
modified bit. Unless you select to use backup methods that depend on a date and time
stamp, Backup Exec uses the archive bit to determine whether a file has been backed up,
which is an important element of your backup strategy.
Selecting the following backup methods can affect the archive bit:
■ Full - Back up files - Using archive bit (reset archive bit)
■ Differential - Back up changed files since last full - Using archive bit (does not reset
archive bit)
■ Incremental - Back up changed files since last full or incremental - Using archive bit
(reset archive bit)
Whenever a file has been backed up using either the Full - Back up files - Using archive
bit (reset archive bit) or Incremental - Changed Files - Reset Archive Bit backup
method, Backup Exec turns the archive bit off, indicating to the system that the file has
been backed up. If the file is changed again prior to the next full or incremental backup,
the bit is turned on again, and Backup Exec will back up the file in the next full or
incremental backup. Backups using the Differential - Changed Files backup method
include only files that were created or modified since the last full backup. When this type
of differential backup is performed, the archive bit is left intact.
Consider the following backup strategy scenario:
312 Administrator’s Guide

Chapter 7, Preparing for backup
About backup strategies
Fred wants to implement a backup strategy for the office fileserver. Fred knows that
all backup strategies begin with a full backup (backup of an entire device using the
full backup method), so he creates a Selection List (see “Creating selection lists” on
page 328) for his server and submits the job to run at the end of the day on Friday.
Since most files on the server, such as operating system files and application files,
seldom change, Fred decides that he can save time and media by incorporating
incremental or differential backups in his media rotation scheme. Fred opts to use
incremental backups, so he schedules the script to run at the end of the day, Monday
through Thursday, with the incremental backup method.
Here’s what happens: Fred’s Friday tape contains all of the data on the fileserver and
Backup Exec changes all of the files’ statuses to backed up. At the end of the day on
Monday, the incremental job runs and only the files that were created or changed
(had the archive bit re-set by the operating system) are backed up. When the
incremental job completes, Backup Exec will turn the archive bit off, showing that
the files have been backed up. On Tuesday through Thursday, the same events
happen.
If Fred’s fileserver crashed on Thursday morning, after he got it running, he would
restore each backup in the order in which it was created (for example, Friday,
Monday, Tuesday, and so forth).
If Fred had decided to perform differential backups on Monday through Thursday, he
would have only needed Friday’s and Wednesday’s tapes: Friday’s tape because it
included all of the data, and Wednesday’s tape because it included every file that had
been created or changed since Friday’s backup.
Understanding modified time and backup methods
If you select to use Full - Back Up Files - Using modified time, Differential - Using
modified time, or Incremental - Using modified time, Backup Exec uses a file’s modified
time rather than the archive bit to determine if it needs to be backed up.
When Backup Exec runs a full or incremental backup, the time the backup launches is
recorded in the Backup Exec database. The next time an incremental or differential
backup launches, Backup Exec compares the file system time to the backup time recorded
in the Backup Exec database. If the file system time is later than the database time, the
file is backed up.
Note The Full - Using modified time backup method adds the time of the backup to the
Backup Exec database only if the full backup job completes successfully. If the full
backup job does not complete successfully, any subsequent backup jobs that use
the differential or incremental modified time backup methods back up all of the
data instead of just the data that changed since the last full backup.
313

About backup strategies
When an incremental backup is run, a new time is recorded in the Backup Exec database.
The database time is not updated with differential backups.
Using the modified time allows Backup Exec to run differential backups on file system,
such as Unix, which do not have an archive bit.
If you want Backup Exec to use modified time to determine if a file has been backed up,
the full and incremental (or full and differential) backups must use the same backup
selection list.
Related Topics:
“About selection lists” on page 327
Using the Windows NTFS Change Journal to determine changed files
For Windows 2000 or later systems, you can enhance incremental and differential
backup performance by selecting to have Backup Exec use the information recorded in
the NTFS Change Journal. NTFS logs all file system changes in the Change Journal. If you
select to use the Change Journal and select Differential - Using modified time or
Incremental - Using modified time as the backup method, Backup Exec will scan the
journal to get a list of changed files rather than scan all files, reducing the amount of
time required to perform the incremental or differential backup.
314 Administrator’s Guide

Selecting data to back up
Chapter 7, Preparing for backup
Selecting data to back up
When you are setting up a backup job, the first thing you do is select the data you want
to back up. You make your selections from the backup selections pane on the Backup Job
Properties dialog box.
Backup Data Selection
Server name
Local drives
System State
Backup Exec database
There are several ways you can select data to back up. You can select an entire drive, a
folder, files, System State, network share, Backup Exec Agent volume, or user-defined
selection. You also can use the Advanced File Selection feature to include or exclude
specific files or specific types of files. Or you can set up a selection list that you can reuse
for several backups.
Note If the account to which you are logged on does not have sufficient rights, you are
required to supply another logon account that can be used to view files for backup.
To expand the view for an item, click the plus sign (+) next to it or double-click the item
name. To collapse the view, click the minus sign (-) next to an item or double-click the
item name.
To view the contents of an item, double-click the item’s icon. The item’s contents appear
in the right frame of the backup selections view. For all items (except System State), you
can traverse file levels from either side of the window by clicking folders and subfolders
as they appear.
When you are browsing remote selections, Backup Exec requires a valid logon account to
expand the resources and devices. If the default logon account does not enable access to
a remote selection, Backup Exec prompts you to select another existing logon account or
create a new logon account that can access the selection.
315

About using fully qualified computer names in backup selections
To select data, select the check box next to the drive or directory you want to back up.
.Data selection
A slash in a shaded check box means some items below
the check box are selected, but the item itself cannot be
selected.
A slash in a check box means some items below the
directory or drive level are selected.
A check mark in a check box means all items at or below
the directory or drive level are selected.
A clear check box means the item can be
selected.
About using fully qualified computer names in backup
selections
You can enter fully qualified computer names in Backup Exec anywhere that you can
enter a computer name. In addition, Backup Exec can show fully qualified computer
names where computer names are listed.
For fully qualified computer names, the following rules apply:
■ The maximum number of characters for each label (the text between the dots) is 63
■ The maximum total number of characters in the fully qualified name is 254,
including the dots, but excluding the \\
■ The name cannot include the following characters: * | < > ?
To find a fully qualified computer name, from the Control Panel, select System >
Computer Name. The fully qualified name appears in the Full computer name field.
If you upgraded from Backup Exec version 10d or earlier, the backup selection list may
include some selections that use fully qualified computer names and some selections
that do not use fully qualified computer names. Symantec does not recommend using
both fully qualified computer names and non-qualified computer names in selection
lists. Symantec recommends using fully qualified computer names.
For example, if you have a computer named Test_Computer, you can have two selections
for it. One selection is called Test_Computer. The fully qualified selection is called
Test_Computer.domain.company.com. In this case, Backup Exec treats each selection as
a separate computer, even though both selections are for the same computer. For
316 Administrator’s Guide

Chapter 7, Preparing for backup
About the Computer Name node
backup jobs that use the short computer name, the catalog contains the short computer
name. For backup jobs that use the fully qualified name, the catalog contains the fully
qualified name.
About the Computer Name node
The first node under All Resources shows the name of the computer on which Backup
Exec is installed. It includes the following sub-nodes:
Sub-nodes of the Computer Name node
Sub-node name Description
Local Drives Includes hard drives as well as CD-ROM drives that physically reside on the
media server.
Shadow Copy
Components
(Windows Server
2003)
Uses Microsoft’s Volume Shadow Copy Service to protect critical operating
system and application service data, and third party application and user
data on Windows Server 2003 resources.
System State Lists a collection of system-specific data that is backed up whenever the
computer name node is selected. Symantec recommends that you back up
System State. However, you can clear the check box next to System State if
you do not want to back it up with the resources on the server. You cannot
select or expand the System State resources individually. They are backed
up only as a collection, never individually.
You can only perform a full backup on System State. However, if you select
other items at the same time, you can perform other backup methods on
those items. You can back up System State remotely on other computers if
Backup Exec Remote Agent is installed on the remote computer. For more
information about System State, refer to your Microsoft Windows 2000 or
Windows Server 2003 documentation.
Active Directory
Application Mode
Backup Exec
database
Appears only when Active Directory Application Mode (ADAM) resources
are available for backup. Even though ADAM is a Shadow Copy component,
the ADAM node is not selected automatically when you select the Shadow
Copy Components node. You must select the ADAM node if you want to
back up the ADAM resources.
Includes job, schedule, job history, notification, alerts, device, media, and
catalog indexes data for Backup Exec
317

About the Favorite Resources node
Sub-nodes of the Computer Name node
Sub-node name Description
Utility Partition Includes the utility partitions that are installed on the system and available
for backup. Individual utility partition objects are named Utility Partition
on Disk disk_number (for example, Utility Partition on Disk 0), and cannot
be expanded. Backing up utility partitions is recommended when a full
system backup is done, such as for disaster recovery preparation. Utility
partitions can be backed up individually. If there are not utility partitions
on the system, this resource is not available. Administrative rights are
required to browse and back up utility partitions.
EFI System Partition Appears if an Extensible Firmware Interface (EFI) system partition is on
the computer. In most cases, each computer will have only one EFI system
partition. However, if more than one exists on a computer, Backup Exec
displays only the active partition.
EFI is required to boot Windows on all Intel Itanium 64-bit computers. You
can back up and restore EFI system partition data using Backup Exec on
Intel Itanium 64-bit computers. EFI system partition data can be backed up
only on remote computers using the Backup Exec Remote Agent for
Windows Systems.
The Advanced Open File Option is not available for use with EFI system
partition backups. In addition, the Use the Microsoft Change Journal if
available option on the General backup options dialog box is not available
for EFI system partition backups.
EFI system partitions can be recovered after a disaster using the Backup
Exec Intelligent Disaster Recovery option.
Related Topics:
“About the Active Directory Recovery Agent” on page 903
About the Favorite Resources node
The Favorite Resources node lists the remote computers that are set up to publish
information to the media server. Several nodes may appear under the Favorite
Resources node, depending on the type of remote computers that you use. The nodes
that may appear include:
■ Linux/Unix Servers
■ Macintosh Servers
■ NetWare Agents
■ Windows Systems
318 Administrator’s Guide

Chapter 7, Preparing for backup
About the Favorite Resources node
From the Windows Systems node, you can add or delete remote Windows computers.
When you add or delete a remote computer, it may take a few minutes for the computer
name to appear or to be removed from the Windows Systems node.
Backup Exec automatically deletes a remote computer from the Windows Systems node
in the following situations:
■ The remote computer becomes disconnected from the network.
■ The Remote Agent is uninstalled from the remote computer.
If the media server receives published information from the remote computer again,
Backup Exec adds the computer name to the Windows Systems node again.
If the media server does not receive published information within a 24-hour period, a
user attention icon appears next to the remote computer’s name. This icon is displayed
for 13 days. Some of the reasons why the media server may not receive published
information include:
■ The publishing option is disabled on the Remote Agent.
■ A media server is removed from the list to publish to.
For more information about publishing, see “Publishing the remote Windows computer
to media servers” on page 919.
Adding a Windows system to the Favorite Resources node
To add a Windows system to the Favorite Resources node
1. On the navigation bar, click the arrow next to Backup.
2. Click New backup job.
3. On the backup selection tree, expand the Favorite Resources node.
4. Right-click Windows Systems.
5. Click Add Windows Systems.
6. In the System Name box, type the name or IP address of the remote computer that
you want to add.
319

About the Favorite Resources node
7. Select one of the following:
Install the Remote Agent,
and then add to Favorite
Resources
Add a system that already
has the Remote Agent
installed
8. In the Logon Account box, select the logon account to use for the remote computer.
This box is not available if you selected Install the Remote Agent, and then add to
Favorite Resources in step 7.
9. Click OK.
If you selected Install the Remote Agent, and then add to Favorite Resources in
step 7, the installation wizard appears. For instructions on how to install the Remote
Agent by using the wizard, see step 4 on page 95.
It may be several minutes before the computer name appears under the node.
Deleting a Windows system from the Favorite Resources node
To delete a Windows system from the Favorite Resources node
1. On the navigation bar, click the arrow next to Backup.
2. Click New backup job.
Click this option if the Remote Agent for Windows Systems is not
installed on the remote computer. Backup Exec installs the
Remote Agent on the remote computer, and then adds the remote
computer to the Favorite Resources node.
Click this option if the Remote Agent for Windows Systems is
already installed on the remote computer. Backup Exec adds the
remote computer to the Favorite Resources node.
3. On the backup selection tree, expand the Favorite Resources node, and then expand
the Windows Systems node.
4. Right-click the Windows system that you want to delete.
5. Click Delete from Favorite Resources.
It may be several minutes before the computer name is removed from the node.
320 Administrator’s Guide

About the Domains node
Chapter 7, Preparing for backup
About the Domains node
The Domains node contains two sub-nodes: Active Directory Domains and Microsoft
Windows Network. The Microsoft Windows Network node enables you to browse to
resources in a Microsoft Windows network.
The Active Directory Domains node enables you to browse Active Directory domains.
Backup Exec automatically discovers the Active Directory domain to which the media
server belongs and displays it in the backup selection list. Also, you can manually add
Active Directory domains to the backup selections list.
You cannot select the Active Directory Domains node itself for backup. You must expand
the node to browse Active Directory domains.
When you add an Active Directory domain, you must use a fully qualified domain name.
An example of a fully qualified domain name is domain.companyname.com. For fully
qualified domain names, the following rules apply:
■ The maximum number of characters for each label (the text between the dots) is 63
■ The maximum total number of characters in the fully qualified domain name is 254,
including the dots, but excluding the \\
■ The name cannot include the following characters: * | < > ?
Adding an Active Directory domain to the Active Directory
Domains node
To add an Active Directory domain
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the backup selections tree, expand the Domains node.
4. Right-click Active Directory Domains.
5. Click Manage Active Directory Domains.
6. In the Name box, type the fully qualified domain name.
7. Click Add.
8. Click Close.
321

About the Oracle Real Application Clusters node
About the Oracle Real Application Clusters node
The Oracle Real Application Clusters node appears only if you install a licensed version
of the Oracle Agent. You cannot select this node for backup. However, you can expand
the node to view and select Real Application Cluster nodes.
For more information about protecting Oracle Real Application Clusters, see “About
backing up Oracle RAC resources” on page 1414.
About the NDMP Devices node
The NDMP Devices node appears only if you install a licensed version of the NDMP
Agent. You cannot select this node for backup. However, you can expand the node to
view and select NDMP devices for backup. For more information about protecting NDMP
devices, see “Backing up NDMP resources” on page 1574.
About the Microsoft SharePoint Server Farms node
The Microsoft SharePoint Server Farms node appears only if you install a licensed
version of the SharePoint Agent. It shows a logical view of the topology of each
SharePoint server farm on your network. Backup Exec automatically discovers
SharePoint farms when you browse to a SharePoint front-end Web server and adds the
farms to this node. Additionally, you can add farms manually by using the Add Server
Farm menu option. For more information, see “Selecting SharePoint resources for
backup” on page 1299.
About the User-defined Selections node
You can create shortcuts to shares and save them as user-defined selections. Use this
feature to quickly access shares that have a very long path or that are unavailable when
you set up a backup job. A share may be unavailable because the network resources that
are used to locate the computer are offline, even though the computer may still be
running and available. In some cases this happens because the computer is on the
Internet and accessible from within the company’s private network, but cannot be
located by using just its name or normal browsing methods.
322 Administrator’s Guide

Chapter 7, Preparing for backup
About the User-defined Selections node
Adding a user-defined selection to the User-defined Selections
node
You can set up direct access to a share by entering its Universal Naming Convention
(UNC) path name or computer name, or a fully qualified computer name.
User-defined selection formats
Format type Example
UNC name \\mycomputer\shared\temp
Fully qualified
computer name
For more information about fully qualified computer names, see
“About using fully qualified computer names in backup selections” on page 316
To add a user-defined selection to the User-defined Selections node
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. Right-click User-defined Selections, and then click Manage User-defined
Selections.
4. In the Name box, type the server name and volume name, the computer name, or
fully qualified computer name.
You can provide TCP/IP addresses for user-defined selections, but Symantec does
not recommended it. Backup Exec does not support user-defined selections for IP
addresses in a Dynamic Host Configuration Protocol (DHCP) environment.
5. Click Add.
6. When you are finished adding selections, click Close.
The selections that you specify can be selected for backup operations from the
User-defined Selections node.
Related Topics:
“About selection lists” on page 327
“Creating selection lists” on page 328
\\mycomputer.domain.companyname.com\temp
323

About the Workstation Agents node
“Deleting selection lists” on page 331
“Editing selection lists” on page 332
About the Workstation Agents node
The Workstation Agents node appears only if you have agents and options from Backup
Exec version 10d or earlier that are set up to publish to the media server.
For more information about Workstation Agents, see “Symantec Backup Exec
Workstation Agents” on page 685.
Selecting Distributed File System (Dfs) links for backup
Only the Dfs links themselves are backed up; the data that the links lead to is not
included.
To back up the data in the Dfs links, back up the data on the server where the data
resides.
If you are backing up any volumes along with the Dfs root, it is recommended that you
exclude any Dfs links that reside on those volumes from the backup.
To back up Microsoft’s Distributed File System (Dfs)
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, select Network and Security.
3. Check Enable selection of user shares, and then click OK.
4. On the navigation bar, click the arrow next to Backup.
5. Click New Backup Job.
6. Create a user-defined selection for the computer that hosts the Dfs root (even if the
computer that hosts the Dfs root is the local selection).
Backup Exec does not support the use of Dfs domain root paths (\\domain\dfsroot).
Add only the computer that hosts the Dfs root to protect the Dfs links.
7. In the backup selection tree, expand User-defined Selections, and then expand the
node for the computer you added.
8. Select the Dfs root.
324 Administrator’s Guide

9. Run the backup job.
Chapter 7, Preparing for backup
Including or excluding files for backup
Related Topics:
“Adding a user-defined selection to the User-defined Selections node” on page 323
“Restoring Distributed File System (Dfs) links” on page 505
Including or excluding files for backup
Advanced file selection allows you to quickly select or de-select files for backup and
archive operations by specifying file attributes. With this feature you can:
■ Include or exclude files by filename attributes. For example, you can select only files
with .txt extensions, or exclude files with .exe extensions from a backup.
■ Select only files that fall within a specified date range. For example, you can select
files that were created or modified during the month of December.
■ Specify files that have not been accessed in a specified number of days. For example,
you can select files that have not been accessed in 30 days from your “My
Documents” folder for an archive operation.
To include or exclude files for backup
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. Select the resource that contains the files you want to include or exclude from the
backup.
4. Click Include/Exclude.
5. Select the appropriate options as follows:
Drives If you want to include or exclude files from a backup of a
different drive than the one you selected previously on the
Backup Job Properties dialog box, select the new drive that
contains the files you want to include or exclude.
325

Including or excluding files for backup
File Selection
Path If you want to include or exclude a specific file, type the name of
the folder and/or subfolder on the selected drive that contains
the file.
You can use wildcard characters. Use a question mark (?) to
represent any single character. Use two asterisks (**) to represent
any number of characters.
For example, on your C: drive you have a My Documents folder
that contains a subfolder called Work Files. There are three Work
Files subfolders called 1999, 2000, and 2001. Each one of those
subfolders has a subfolder called Personnel. If you type the path
as \My Documents\**\Personnel, the backup will include or
exclude:
◆ C:\My Documents\Work Files\2001\Personnel
◆ C:\My Documents\Work Files\2000\Personnel
◆ C:\My Documents\Work Files\1999\Personnel
In addition, every subfolder below the ** wildcard is included or
excluded. However, the only files from the subfolders that are
included or excluded are those that match the file name you type
in the File field. So in the example above, every subfolder of
C:\My Documents is included in or excluded from the backup,
and only the files that match the file name you type in the File
field are included or excluded.
After you type the path, type the file name in the File field.
File Type the name of the file you want to include in or exclude from
the backup.
You can use wildcard characters. Use a question mark (?) to
represent any single character. Use two asterisks (**) to represent
any number of characters.
For example, to include all files with the .exe extension, type
**.exe.
After you type the file name, indicate whether you want to
include or exclude it.
Include (Default) Select this option to include the files in the job.
Exclude Select this option to exclude the files from the job.
Include subdirectories Select this option if you want to select the contents of all the
subfolders when a directory is selected.
326 Administrator’s Guide

Chapter 7, Preparing for backup
About selection lists
Only modified Files Select this to include or exclude modified files in the path you
specify.
Only read-only Files Select this to include or exclude files that cannot be modified.
Files dated Select this to include or exclude the files created or modified
during a specific time period. Then select the beginning and
ending dates.
Files not accessed in x days Select this to include or exclude files that have not been accessed
in a specified number of days. This is useful when you need to
migrate older files from your system.
If the data does not match all of the criteria specified in the Advanced Backup File
Selection dialog box, Backup Exec does not include or exclude it in the backup.
6. After completing your selections, click OK.
7. Submit the operation using the same procedures as required for other backups. For
more information, see “Creating a backup job by setting job properties” on page 349.
About selection lists
Selection lists provide a quick and easy way of selecting files that you back up often.
After you choose devices, directories and files, you can save the selections as a selection
list that you can use in regularly scheduled operations or once-only operations.
Selection lists, which define what is to be backed up, are also automatically created
when you create a backup. You can combine a selection list with a policy and quickly
create a backup job.
Backup Exec detects and notifies you about items in a selection list that are no longer on
the resource. Notification occurs as a selection list is loaded for local selections, and as
any remote server is expanded in the tree.
You can also choose to notify recipients when a job completes that contains a particular
selection list. This feature allows you to notify users who may be interested that a
particular set of selections was backed up. The completion status of the job is included in
the notification.
To view the job history of the jobs that are associated with a selection list, from Job
Setup, right-click the selection list, and then from the shortcut menu, click View
History.
327

About selection lists
Related Topics:
“Creating selection lists” on page 328
“Deleting selection lists” on page 331
“Editing selection lists” on page 332
“Editing selection lists” on page 332
Creating selection lists
A backup selection list is a list of the resources you want to back up. After you create a
selection list you can use it with any backup job or policy. Depending on how you set the
Backup Exec default options for selection lists, Backup Exec will do one of the following
when you create a new selection list:
■ Create a separate selection list for each computer you choose.
■ Create a separate selection list for each resource you choose.
■ Create one selection list, regardless of the number of computers or resources you
choose.
To create a selection list
1. On the navigation bar, click Job Setup.
2. In the task pane, under Selection Lists Tasks, select New backup selection list.
3. Select the resources that you want to back up from the backup selections pane. For
more information about selecting data, see “Selecting data to back up” on page 315.
4. Select the appropriate options as follows:
Selection list name Enter the name of this selection list.
Selection list
description
Load Selections from
existing list
Enter a description for this selection list.
Click this button if you want to load an existing selection list or
merge multiple selection lists (see “Merging and replacing selection
lists” on page 330).
Include/Exclude Click this button if you want to use the Advanced File Selection for
selecting files for backing up (see “Including or excluding files for
backup” on page 325).
328 Administrator’s Guide

Chapter 7, Preparing for backup
About selection lists
Include subdirectories Select this option if you want to select the contents of all the
subfolders when a directory is selected.
Show file details Select this option to display details about the files available for
selecting.
5. (Optional) To change the order in which the resources in the selection list are backed
up, on the Properties pane, under Source, click Resource Order.
6. (Optional) To change or test a logon account for the resources, on the Properties
pane, under Source, click Resource Credentials. For more information, see “About
selection lists” on page 327.
7. (Optional) To set the priority for processing the jobs associated with the selection
list, or to can set a time range when the resources in the list will be available for
backup, on the Properties pane, under Source, click Priority and Availability. For
more information, see “Setting priority and availability windows for selection lists”
on page 334.
8. (Optional) To notify users that a job containing this selection list was completed, on
the Properties pane, under Source, click Selection List Notification. For details on
adding notification recipients, see “Assigning notification recipients for completed
jobs” on page 565.
9. If you are creating a selection list for a CASO environment, do the following in the
order listed:
■ On the Properties pane, under Destination, click Device.
■ Check Restrict backup of the selection list to devices on the following media
server or media servers in a pool.
■ Select the media server from the drop-down list.
10. Click OK.
Related Topics:
“About selection lists” on page 327
“Deleting selection lists” on page 331
“Editing selection lists” on page 332
“To edit the Excludes selection list” on page 333
“Creating separate selection lists for each computer or resource” on page 335
329

About selection lists
Holding jobs that back up a selection list
You can place all jobs that back up a selection list on hold to prevent the jobs from
running. The jobs do not run until you change the job’s hold status.
To hold jobs that back up a selection list
1. On the navigation bar, click Job Setup.
2. On the Backup Selection Lists pane, right-click the selection list whose jobs you
want to place on hold, and then click Hold Jobs.
The jobs that back up this selection list are placed on hold. To remove the hold and
run the jobs according to the schedule, click Remove Hold.
You can select multiple selection lists by selecting a selection list, and then pressing
the or keys while you click other selection lists.
Merging and replacing selection lists
You can create a new selection list by merging two or more existing lists with new
selections. You can also replace selections in the tree with other selection lists.
To merge and replace selection lists
1. On the navigation bar, click Job Setup.
2. Under Selection Lists Tasks in the task pane, select New backup selection list.
3. On the New Backup Selection List dialog box, select resources to include in the
selection list.
4. Click Load selections from existing list.
5. On the Use Selections dialog box, select the selection lists that you want to merge
with or replace the previously selected backup selections.
6. Do one of the following:
To merge the selection
lists
To replace the existing
selection list
Click Merge.
Click Replace.
330 Administrator’s Guide

Chapter 7, Preparing for backup
About selection lists
7. Complete the other options on the New Backup Selection List dialog box as described
in “Creating selection lists” on page 328.
8. Click OK.
Deleting selection lists
You can delete a selection list. However, if a selection list is associated with a policy, you
must remove the selection list’s association from the policy before you can delete the
selection list.
You cannot delete the Excludes selection list.
To delete selection lists
1. On the Edit menu, click Manage Selection Lists.
2. Click the selection list that you want to delete.
3. Click Delete.
4. Click Yes to delete the Selection List or click No to cancel the delete operation.
If the selection list is being used by a job, you will not be able to delete it.
5. Click Close.
Related Topics:
“About selection lists” on page 327
“Creating selection lists” on page 328
“Editing selection lists” on page 332
“To edit the Excludes selection list” on page 333
“Deleting a job created from a policy” on page 434
331

About selection lists
Editing selection lists
Editing a selection list affects all jobs that use the selection list. However, if you edit a
selection list that is being used by an active job, the changes do not affect that job. If you
want to only edit selections for a specific job, edit the job rather than the selection list.
To edit one selection list
1. On the Edit menu, click Manage Selection Lists.
2. Select the selection list that you want to edit.
3. Click Edit.
4. Edit the selection list properties.
5. Click OK.
To edit multiple selection lists
1. On the navigation bar, click Job Setup.
2. On the Backup Selection Lists pane, select the selection list you want to edit.
Select multiple selection lists to edit by holding down the CTRL key while clicking
the selection lists.
3. Under General Tasks in the task pane, click Properties.
4. If you selected multiple selection lists to edit, do one of the following:
To change all of the
properties for each
selection list, one at a
time
To change the priority
and availability,
notification, and device
(for a CAS only)
properties for all of the
selected selection lists
Click Edit each selection list.
Click Apply settings to all of the selected selection lists.
If the selection list is being used by jobs, any change you make to this selection list
will affect all jobs associated with it.
332 Administrator’s Guide

5. Click Yes to continue.
6. Edit the selection list properties.
7. Click OK.
8. Click Close.
Editing the Excludes selection list
To edit the Excludes selection list
1. On the Edit menu, click Manage Selection Lists.
2. On the Manage Selection Lists dialog box, select Excludes.
3. Click Edit.
4. Do one of the following:
If the Excludes list was
edited previously
If this is the first time the
Excludes list is being
edited
5. Edit the selection list properties.
6. If you want to delete one of the selection rules:
Chapter 7, Preparing for backup
■ Select the selection rule that you want to delete.
■ Click Delete.
7. Click OK.
8. Click Close.
◆ Select the selection rule that you want to edit.
◆ Click Edit.
Click Insert.
Related Topics:
“Including or excluding files for backup” on page 325
“About selection lists” on page 327
About selection lists
333

About selection lists
“Creating selection lists” on page 328
“Assigning notification recipients for completed jobs” on page 565
“Deleting selection lists” on page 331
Setting priority and availability windows for selection lists
When you create a backup selection list, you can specify the priority for processing the
jobs associated with the selection list. In addition, you can set a time range when the
resources in the list will be available for backup. The time range is called the availability
window. You can set a default availability window for selection lists. When you create a
new selection list, the default availability window displays, but you must select the Limit
availability of this selection list for backup to the following daily time window option
in order for the selection list to use the default window.
You can set one availability window per selection list, and the window is the same for
each day of the week. If you merge two or more selection lists or replace a selection list,
Backup Exec uses the availability window of the original list.
If you schedule a job to run outside of the availability window, the job does not run and
Backup Exec displays an Invalid Schedule status for the job on the Job Monitor. For
example, you set the availability window to allow resources to be available for backup
between the hours of 11:00 p.m. and 6:00 a.m. If you schedule a backup job to run at 7:00
a.m, the job will not run because the resources are not available at that time. When
scheduling a job, be sure that the schedule overlaps the availability window for the
resources.
To set a default availability window for selection lists
1. On the Tools menu, select Options.
2. On the Properties pane, under Job Defaults, click Priority and Availability.
3. Proceed to step 5 of “To set priority and availability for selection lists” on page 334.
To set priority and availability for selection lists
1. On the navigation bar, click Job Setup.
2. In the task pane, under Selection Lists Tasks, select New backup selection list.
3. Select the data you want to back up.
4. On the Properties pane, under Source, click Priority and Availability.
334 Administrator’s Guide

5. Complete the appropriate options as follows:
Chapter 7, Preparing for backup
About selection lists
Job priority Select the default priority you want to assign to the all jobs
associated with this selection list. The choices are Highest, High,
Medium, Low, and Lowest.
Limit availability of this
selection list for backup
to the following daily
time window
This option displays as Limit availability to this daily time
window when you are setting default options. Select this check
box to enable the availability window, which specifies when the
selection list will be available for backup each day. Then specify
the window settings or use the default settings.
If you do not select this option, the resources in the selection list
are always available for backup.
First available date Select the first date when the selection list should be available to
be backed up. The list will be available every day from this date
onward.
Begin time Select the earliest time when this selection list will be available for
backup.
End time Select the latest time when this selection list will be available for
backup.
Enable automatic
cancellation for this
selection list
Cancel backup job if not
completed within x
Select this option if you want Backup Exec to cancel the job
associated with this selection list if the job does not complete
within the selected number of hours or minutes. Backup Exec
starts timing the length of time the job takes to run when the job is
queued, not when the job begins.
Type the number of hours or minutes you want to allow jobs to
complete before they are automatically canceled. The default
amount of time is three hours.
Creating separate selection lists for each computer or resource
Backup Exec includes default settings that enable separate selection lists to be created
for each resource or computer you select when you create a new backup selection list
outside of a backup job. This feature does not apply when you create a selection list
while creating a backup job.
If you set up Backup Exec to create a separate selection list for each resource or
computer, the selection list name will contain either the default name or a user-defined
name followed by the name of the computer or resource that you selected for backup.
335

About selection lists
To create separate selection lists for each computer or resource
1. On the Tools menu, select Options.
2. On the Properties pane, under Settings, select Selection List.
3. Select one of the following options:
Separate backup
selection list for each
computer
Separate backup
selection list for each
resource
Single backup selection
list for all selections
Creating a custom filter for Backup Selection Lists
To create a custom filter for Backup Selection Lists
1. On the navigation bar, click Job Setup.
2. On the Backup Selection Lists pane, in the Filter list, click .
3. Type a unique name and a description for this filter.
4. Do any of the following:
To filter by selection list
name
To filter by selection list
description
To filter by computers
backed up by the
selection list
Select this option to have Backup Exec create a different backup
selection list for each computer that you select when you create a
selection list outside of a backup job.
Select this option to have Backup Exec create a different backup
selection list for each resource that you select when you create a
selection list outside of a backup job.
Select this option to have Backup Exec create one selection list,
regardless of the number of resources or computers selected for
backup. This is the default option.
◆ Under Criteria, click Selection List Name.
◆ Type the name of the selection list on which you want to filter.
◆ Under Criteria, click Description.
◆ Type all or part of the description of the selection list on which
you want to filter.
◆ Under Criteria, click Protected Server.
◆ Type the name of the server on which you want to filter.
336 Administrator’s Guide

To filter by resource type
5. Click OK.
Filtering backup selection lists
To filter backup selection lists
1. On the navigation bar, click Job Setup.
Chapter 7, Preparing for backup
About selection lists
2. On the Backup Selection Lists pane, in the Filter list, click the filter that you want to
use.
Searching selection lists
Backup Exec includes a search feature for selection lists, which enables you to search for
selection lists that back up a particular computer. This feature is helpful when you have
a large number of selection lists.
To search a selection list
1. On the navigation bar, click Job Setup.
2. On the task pane, under Selection List Tasks, click Search backup selection lists.
3. Type the name of the computer for which you want to locate selection lists. You can
type the complete name or part of the name.
4. Click Find Now.
◆ Under Criteria, click Resource Type.
◆ Check Enable this filter.
◆ Select the check boxes for the types of resources on which you
want to filter. Clear the check boxes for the types of resources
on which you do not want to filter.
To filter by policy ◆ Under Criteria, click Policy.
To filter by selection lists
that are not protected
◆ Check Enable this filter.
◆ Select the policy on which you want to filter.
◆ Under Criteria, click Not Protected.
◆ Check Filter for backup selection lists that are not protected.
337

About selection lists
The Search Selection Lists dialog box expands to display the results of the search.
You can right-click a selection list to create a new job using policies, copy or delete
the selection list, or view the selection list properties.
Viewing the history for backup selection lists
You can view the history of the jobs that use a specific backup selection list. Backup Exec
shows the following history information:
■ Job name
■ Device name
■ Job type
■ Job status
■ Start time
■ End time
■ Elapsed time
■ Byte count
■ Job rate
To view the history for backup selection lists
1. On the navigation bar, click Job Setup.
2. Right-click the backup selection list for which you want to view history.
3. Click View History.
4. Click OK.
Viewing a summary for a selection list
To view a summary for backup selection lists
1. On the navigation bar, click Job Setup.
2. Right-click the backup selection list for which you want to view a summary.
3. Click View Summary.
338 Administrator’s Guide

4. Click OK.
Chapter 7, Preparing for backup
Using resource discovery to search for new resources
Using resource discovery to search for new resources
Backup Exec’s Resource Discovery feature allows detection of new backup resources
within a Windows or Active Directory domain. Using this feature, you can create and
schedule a job that searches for new server volumes or databases. You can specify which
types of resources to include in the search, and can have Backup Exec send a notification
when a new resource is discovered.
Using the discovered resources identified in the job log, you can then create a backup job
to ensure that the new resource is protected.
When you set up a resource discovery job, Backup Exec lists all of the Windows domains
it has discovered. If you have Active Directory domains, you must add them to the list
manually. When the list of domains is in place, you select which domains you want to
search for new resources.
The Remote Agent is required to discover resources on remote computers. However,
installing a MAPI client on the media server enables Exchange resources to be
discovered on remote resources on which the Remote Agent is not installed.
On Windows Server 2003 resources, Backup Exec’s Resource Discovery feature will
detect the Shadow Copy Components; it will not detect System State.
To use resource discovery to search for new resources
1. On the navigation bar, click Job Setup.
2. Under Backup Strategy Tasks in the task pane, select New job to automatically
discover resources.
3. To add an Active Directory domain to the list of domains to search for new
resources, do the following in the order listed:
■ Click Add Active Directory Domain.
■ In the Name field, type the fully qualified name for the domain.
■ Click Add.
■ Click Close
4. Select the domain you want Backup Exec to search for new resources.
5. If you need to change the logon account for the domain, click Change Logon
Account and enter or select the logon credentials to access this domain.
339

Using resource discovery to search for new resources
6. If you want to exclude computers from the search, do one of the following:
To browse for the
computer name
To type the computer
name
◆ In the Domain field, select the domain that contains the
computers you want to exclude.
◆ From the list of computers, select the computer that you want
to exclude.
◆ Click Exclude.
◆ In the Servers excluded field, type the name of the computer.
◆ Click Add.
7. On the Properties pane, under Settings, click General and then complete the
appropriate options as follows: :
Job name Enter the name for this job.
Job priority Select the priority level for this job. If another job is scheduled to
run at the same time as this job, the priority you set determines
which job runs first. Your choices are:
◆ Highest
◆ High
◆ Medium
◆ Low
◆ Lowest
8. On the Properties pane, under Settings, click Resources and then complete the
appropriate options as follows:
Network administrative
shares
Select this option if you want Backup Exec to search for new
administrative network shares or volumes.
Network user shares Select this option if you want Backup Exec to search for new
user-defined shares.
Microsoft SQL databases Select this option if you want Backup Exec to search for new
Microsoft SQL databases.
Microsoft Exchange
servers
Select this option if you want Backup Exec to search for new
Microsoft Exchange servers. Backup Exec searches for Information
Store, Exchange Directory, or Storage Groups; it does not discover
individual databases under storage groups.
340 Administrator’s Guide

Chapter 7, Preparing for backup
About the Backup Exec Shadow Copy Components file system
Lotus Domino databases Select this option if you want Backup Exec to search for new Lotus
Domino databases.
System State and/or
Shadow Copy
Components
Select this option if you want Backup Exec to search for new System
State resources or shadow copy components.
Oracle databases Select this option if you want to search for new Oracle databases.
DB2 databases Select this option if you want to search for new DB2 databases.
Send separate
notification for each
new resource found
Send one notification
for all new resources
found
Include previously
discovered resources
when sending
notification
Select this option if you want Backup Exec to send separate
notifications when each new resource is found.
Select this option if you want Backup Exec to send out a single
notification for all new resources found.
Select this option if you want Backup Exec to send a notification
that includes all resources previously found during resource
discovery jobs.
9. If you want Backup Exec to notify someone when this job completes, on the
Properties pane, under Settings, click Notification (see “Assigning notification
recipients for completed jobs” on page 565).
10. If you want to run the job now, click Run Now. Otherwise, on the Properties pane,
under Frequency, click Schedule to set the scheduling options you want to use (see
“Scheduling jobs” on page 368).
About the Backup Exec Shadow Copy Components file system
The Backup Exec Shadow Copy Components file system uses Microsoft’s Volume
Shadow Copy Service to protect critical operating system and application service data,
and third party application and user data on Windows Server 2003 resources.
Volume Shadow Copy Service allows a computer to be backed up while applications and
services are running by providing a copy of a volume when a backup is initiated.
Applications do not need to be shut down to ensure a successful volume backup. Volume
Shadow Copy Service enables third party vendors to create snapshot plug-ins, or
Writers, for use with this shadow copy technology.
341

About the Backup Exec Shadow Copy Components file system
A Writer is specific code within an application that participates in the Volume Shadow
Copy Service framework to provide point-in-time, recovery-consistent operating system
and application data. Writers appear as Shadow Copy Components, which are listed as
resources in backup and restore selections. When expanded, the Backup Exec Shadow
Copy Components file system includes the following types of Writers:
■ Service State - Critical operating system and application service data, such as Event
Logs, Windows Management Instrumentation (WMI), Removable Storage Manager
(RSM), and others.
■ User Data - Third party application and user data, and others.
Even though ADAM and System State are Shadow Copy component, the ADAM node and
the System State node are not selected automatically when you select the Shadow Copy
Components node. You must select those node if you want to back up those resources.
Only Writers that have been tested for use with Backup Exec are available for selection
in the backup selection list. Other Writers may be displayed in the selection list, but
cannot be selected for backup.
Automatic exclusion of files during volume-level backups
If you select a volume that contains Shadow Copy data for backup, Backup Exec
determines which Shadow Copy files should not be included in a volume level backup.
These files will be automatically excluded for backup by a feature called Active File
Exclusion. If this exclusion did not happen during a non-snapshot backup, these files
would appear as in use - skipped. If this exclusion did not happen during a snapshot
backup, the files would be backed up in a possible inconsistent state, which could create
restore issues.
Windows SharePoint Services support
The Windows SharePoint Services feature pack utilizes a SQL (MSDE) instance called
SHAREPOINT as a repository for shared information and collaboration data. On
Windows Server 2003, in the absence of a Symantec SQL Agent installation, the SQL
SHAREPOINT instance can be protected by the Shadow Copy Components file system. If
the SQL Agent is installed, then the SQL SHAREPOINT instance can be protected by the
SQL Agent.
Note If Windows SharePoint Services is installed using an instance name other than the
default SHAREPOINT instance name, then it cannot be protected by the Shadow
Copy Components file system. In that case, the Symantec SQL Agent must be used
to protect the SQL SHAREPOINT instance.
342 Administrator’s Guide

Small Business Server 2003 support
Chapter 7, Preparing for backup
About the Backup Exec Shadow Copy Components file system
Windows Small Business Server 2003 Standard and Premium contain a SQL (MSDE)
instance called SBSMONITORING as a repository for server-related activity data. In the
absence of a Symantec SQL Agent installation, the SQL SBSMONITORING instance can
be protected by the Shadow Copy Components file system. If the SQL Agent is installed,
then the SQL SBSMONITORING instance can be protected by the SQL Agent.
How the Shadow Copy Components file system is affected by
upgrades
When you upgrade from Backup Exec 10d to 11d, Backup Exec automatically updates the
backup selection lists that include Shadow Copy Components. The following table shows
what is updated:
Automatic selection list updates for Backup Exec 11d
If this was selected in 10d Backup Exec does this automatically in 11d
Shadow Copy Components Adds System State to the selection list.
System State (under the Shadow Copy
Components node)
Active Directory Application Mode (under the
Shadow Copy Components, User Data nodes
Any specific Active Directory Application
Mode instance
Changes the selection to System state only.
Changes the selection to Active Directory
Application Mode only.
Changes the selection to Active Directory
Application Mode only, with the specific instance
selected.
343

About the Backup Exec Shadow Copy Components file system
344 Administrator’s Guide

Backing up data
Chapter
Backups are crucial for data protection, and Backup Exec offers you many choices for
creating backup jobs to protect your data, including:
8
■ Using the Backup Wizard. Use this wizard to submit a backup job if you are a new or
inexperienced Backup Exec user. The wizard guides you through the process of
creating a backup job using most of the default options. After you become more
experienced with Backup Exec, you will probably create backups by configuring
backup job properties.
■ Configuring backup job properties. Experienced Backup Exec users can create
customized backup jobs by selecting resources to protect and setting backup options.
Using the backup job properties pages allows you to set some options, such as job
priority and database options, that cannot be set per job using the Backup Wizard.
■ Creating a selection list. Select the data you want to back up and save the selections
as a selection list. You can then choose the selection list when creating a backup job.
You can use selection lists for multiple jobs. You can also choose a selection list and
combine it with a policy to create a job.
■ Using Backup Exec’s Windows Explorer interface. Select and back up files and folders
from Windows Explorer without having to launch the Backup Exec Administration
Console.
Backup Exec allows you to set default options for backup jobs, but also gives you the
flexibility to override these options for specific jobs. You can direct all backup jobs to a
specified network segment, isolating the backup data so that other connected networks
are not affected when backup operations are performed, or you can specify a LAN for a
single job.
Backup Exec also provides the option of setting up backup jobs that take place on a
routine basis (scheduled jobs), or set up one-time backup jobs.
In addition to creating backup jobs to protect data, you can create:
345

■ A test run of a scheduled backup job to determine whether or not it is likely to
complete successfully.
■ A job that duplicates backup sets either from previously backed up data or data
scheduled to be backed up. If the backup sets are to be duplicated from a scheduled
job, the duplicate backup data job runs automatically after the backup job completes.
■ Verify jobs to test the integrity of the media.
■ Archive jobs to preserve storage space.
■ Resource discovery jobs to find new resources that may need to be backed up on a
regular basis.
Before you begin backing up data, you should develop a backup strategy that includes the
method, frequency, and media rotation methods that are appropriate for your
organization. You may have different strategies for different areas of the organization.
You may also want to configure device and media management before creating backup
jobs. You can set up Backup Exec to use physical devices, such as stand-alone drives, or
virtual devices, such as backup-to-disk folders. Or, you can have Backup Exec use logical
groupings of devices, such as drive pools. Specifically, you might want to perform the
following tasks to help you manage storage hardware and media most effectively:
■ Set up drive pools for systems with more than one storage device. For more
information, see “Creating device pools” on page 177.
■ Create media sets. For more information, see “Creating media sets” on page 264.
Caution To protect remote resources, you must install the Backup Exec Remote Agent
for Windows Servers on the remote computer. The Remote Agent is a system
service that runs on Windows servers and workstations and provides efficient
backup processing by locally performing tasks that, in typical backup
technologies, require extensive network interaction.
Related Topics:
“Creating a backup job by using the Backup Wizard” on page 347
“About backup strategies” on page 305
“Symantec Backup Exec Remote Agent for Windows Systems” on page 913
346 Administrator’s Guide

Chapter 8, Backing up data
Creating a backup job by using the Backup Wizard
Creating a backup job by using the Backup Wizard
If you are new to Backup Exec or are uncertain about how to set up a backup job, you can
use the Backup Wizard. You can use the wizard in the following ways:
How to use the Backup Wizard
Option Description
Back up the media
server now using
default settings
Create a backup job
with custom settings
This method backs up the local media server by using the default settings.
You cannot select data or set options for the backup. The backup job is
submitted immediately using your default logon account and the default
backup selections and settings.
Backup Exec can back up the following types of data with this method:
◆ Local drives that do not use removable media
◆ Lotus Domino resources
◆ Microsoft SQL Server databases
◆ Microsoft Sharepoint Portal Server
◆ Microsoft Exchange 2000 Information Store
◆ Microsoft Exchange 2000 Key Management Service (KMS) and Site
Replication Service (SRS)
You cannot back up the following types of data with this method:
◆ Microsoft SQL Server filegroup resources
◆ Microsoft Sharepoint Portal Server workspaces
◆ Microsoft Exchange individual mailboxes and public folders
◆ Microsoft Exchange 2000 installable filesystem (IFS) drive (usually M:)
In addition, you cannot run this type of backup job in a cluster
environment or in a Central Admin Server Option environment.
If you want to perform this type of backup job on a system where
backup-to-disk folders are located, Symantec recommends that you add
the backup-to-disk folders to the Excludes Selection List. If you do not
exclude backup-to-disk folders, data is continuously added to the folders
during the backup job, which uses all the free drive space.
This method guides you through the process of creating a backup job.The
wizard prompts you to select options. However, many of the backup job
settings are based on the default settings.
To back up the media server now by using default settings
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job using Wizard.
347

Creating a backup job by using the Backup Wizard
3. Click Back up this media server now using default settings.
4. Click Next.
5. Click Finish.
To create a backup job that uses custom setting
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job using Wizard.
3. Click Create a backup job with custom settings.
4. Click Next.
5. Follow the on-screen prompts.
Related Topics:
“Creating a backup job by setting job properties” on page 349
“Monitoring jobs” on page 442
Preventing the Backup Wizard from launching from the Backup
button
By default, the Backup Wizard displays when you select Backup on the navigation bar. If
you prefer to set up backup jobs manually, you can prevent the Backup Wizard from
displaying. If you disable the Backup Wizard, you can re-enable it at any time.
To prevent the Backup Wizard from launching from the Backup button
1. On the navigation bar, click Backup.
2. Uncheck Always launch the Backup Wizard from the Backup button.
3. Click Next.
To set the Backup Wizard to launch from the Backup button
1. On the Tools menu, click Wizards>Backup Wizard.
2. Check Always launch the Backup Wizard from the Backup button.
348 Administrator’s Guide

3. Click Next.
Creating a backup job by setting job properties
To create a backup job by setting job properties
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
Chapter 8, Backing up data
Creating a backup job by setting job properties
3. From the backup selections pane, select the data you want to back up.
See “Selecting data to back up” on page 315.
4. On the Properties pane, under Destination, click Device and Media, and complete
the options as described in “Device and media options for backup jobs and
templates” on page 354.
5. On the Properties pane, under Settings, click General and complete the options as
described in “General options for backup jobs and templates” on page 357.
You can select additional configuration options for your backup job if, before
selecting to run or submit the job, you select additional options on the Backup Job
Properties dialog box’s Properties pane:
■ If you want to set advanced options for the backup job, on the Properties pane,
under Settings, click Advanced. Then, complete the options as described in
“Advanced options for backup jobs” on page 362.
■ If you want to change the backup network for this job, on the Properties pane,
under Settings, click Network and Security, and then set up the backup network
for this job (see “Changing the backup network for a job” on page 403).
■ If you want to set commands to run before or after a job, on the Properties pane,
under Settings, click Pre/Post Commands and complete the options as described
in “Pre/post commands for backup or restore jobs” on page 365.
■ If you are using the Advanced Open File Option, on the Properties pane, under
Settings, select Advanced Open File and complete the options as described in
“Setting defaults for the Advanced Open File Option for backup jobs” on
page 850.
■ If you are backing up other platform types or database agents, such as NetWare,
Exchange, or SQL, select the platform type or database agent from the
Properties pane. Refer to the chapter or appendix for that item for instructions
on completing the options.
349

Creating a backup job by setting job properties
■ If you want Backup Exec to notify someone when the backup job completes, on
the Properties pane, under Settings, click Notification (see “Assigning
notification recipients for completed jobs” on page 565).
■ If you want Backup Exec to notify someone when a backup job containing a
specific selection list completes, on the Properties pane, under Source, click
Selection List Notification (see “Assigning notification recipients for completed
jobs” on page 565).
6. If you want to run the job now, click Run Now. Otherwise, on the Properties pane,
under Frequency, click Schedule to set the scheduling options you want to use (see
“Scheduling jobs” on page 368), and then click Submit.
7. If the backup job summary appears, review it, and then click OK to run the job. If you
want to turn off the job summary for future backup jobs, from the Tools menu, click
Options, and then clear Display the job summary before creating a job (see “Backup
Exec defaults” on page 138).
Note If a drive loses power during a backup operation, you should restart the backup job
using a different tape. You can restore the data written to the tape up to the point
of the power loss, but you should not reuse the tape for subsequent backup
operations.
Related Topics:
“Creating a backup job by using the Backup Wizard” on page 347
“Selecting data to back up” on page 315
Selections options for backup jobs
When the Backup Job Properties dialog box appears, Selections is chosen by default on
the Properties pane. Through the Selections options, you choose the data you want to
include in the backup job. Options on this dialog box include:
Selections options for backup job
Item Description
Selection list name If you are creating a job using an existing selection list, select the
selection list you want to use (see “About selection lists” on page 327).
Otherwise, use the default Selection list name, which creates a new
selection list using this name.
Selection list description Enter a description for the selection list.
350 Administrator’s Guide

Selections options for backup job (continued)
Item Description
Load Selections from
Existing List
Chapter 8, Backing up data
Creating a backup job by setting job properties
Click this button if you want to use a previously created selection list
or merge existing selection lists (see “About selection lists” on
page 327).
Text Select this option to view selections as a list of files and directories.
Include/Exclude Click this button if you want to use the Advanced File Selection for
selecting files for backing up (see “Including or excluding files for
backup” on page 325).
Include subdirectories Select this option if you want to select the contents of all the
subfolders when a directory is selected.
Show file details Select this option to display details about the files available for
selecting.
Related Topics:
“Selecting data to back up” on page 315
“About selection lists” on page 327
“Including or excluding files for backup” on page 325
“Creating selection lists” on page 328
“Adding a user-defined selection to the User-defined Selections node” on page 323
Changing the order for processing backup selections
After you make selections for a backup job, you can set up Backup Exec to process those
selections in a certain order. Please note the following about the order in which
selections can be backed up:
■ You can order resources within a server, but you cannot alternate selections across
servers. For example, you can select C: and D: from Server A followed by selections
from Server B. However, you cannot order selections as C: from Server A and then C:
from Server B and then D: from both servers.
■ For any given server, system state must be ordered last.
351

Creating a backup job by setting job properties
To change the order for processing backup selections
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. Select the data you want to back up.
4. On the Properties pane, under Source, click Resource Order.
5. Select an item you want to move.
6. Click Move Up or Move Down until the item is in the correct order.
Click Make First to move an item to the top of the list or click Make Last to move an
item to the bottom of the list.
7. Process the backup job (see “Creating a backup job by setting job properties” on
page 349).
Changing and testing logon accounts for resources
A logon account enables Backup Exec to access resources for backup. You can verify that
the logon accounts you select can access the resources you want to back up.
To change and test a logon account for a resource
Note For remote selections, do not change the logon account information. They rely on
the logon account used to connect to the server they reside on, and will ignore the
additional logon account you can specify. This applies to drives, Lotus, System
State, and Exchange selections (except mailboxes, which can and do use logon
accounts).
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. Select the data you want to back up.
4. On the Properties pane, under Source, click Resource Credentials.
5. Select the resource whose logon account you want to edit.
6. Click Change.
352 Administrator’s Guide

Chapter 8, Backing up data
Creating a backup job by setting job properties
7. Select the Backup Exec logon account you want to use for this backup selection, or
click New and create a new Backup Exec logon account (see “Creating a Backup Exec
logon account” on page 149).
8. To verify that the logon account you are using can access the resources selected for
backup, click Test All.
While Backup Exec attempts to connect to the resources, "Testing" displays in the
Test Results column. After a test has completed, the Test Results column will display
one of the following results: Successful, Not tested, or an error message. The Not
Tested result indicates that either the logon accounts have not been tested or that
the tests have been performed but the server that contains the selection could not be
accessed.
Some tests may take a long time to complete. To cancel a logon account test, click
Cancel Test.
9. Click OK.
353

Creating a backup job by setting job properties
Device and media options for backup jobs and templates
You select the storage device and media set on which the backup job will run by clicking
Device and Media on the Backup Job Properties box and completing the options you
want.
Options on this dialog box include:
Device and Media options for backup job
Item Description
Device Select a drive pool, stand-alone drive, robotic library drive, or
backup folder to be used for processing the backup.
If you select a backup folder, be sure it is not on the disk you are
backing up. For example, if you are backing up your local C:\ drive,
select a backup folder that is not on your local C:\ drive. Backup
jobs submitted to a backup folder cannot span disks unless the
folder is a removable backup-to-disk folder (see “About
backup-to-disk folders and files” on page 218). If the size of a
backup job exceeds the amount of free space on the disk where the
backup folder is located, the job fails. Before you back up data to a
disk, verify that there is sufficient free space on the destination
disk. To maximize the amount of data that you can store on a disk,
use the software compression option.
If a backup job fails due to insufficient disk space, the backup folder
goes offline. To complete the backup job, you must create more free
space on the disk, and then pause and resume the folder. You can
create more disk space by:
◆ Moving the backup files to another disk or backing up the files
to a tape.
◆ Changing the location of the backup folder.
◆ Erasing the backup files.
◆ Overwriting the existing backup files.
If you are unable to create more free space and cannot continue the
backup job, you can restore the data that was backed up prior to the
failure.
Backup files are subject to the same overwrite and append options
as other media.
Make sure that appropriate media (overwritable or appendable) is
in the stand-alone drive or drive pool you select.
If the media in the drive is not overwritable or appendable, a
message is displayed requesting that you insert overwritable
media.
354 Administrator’s Guide

Device and Media options for backup job (continued)
Item Description
Restrict backup of the
selection list to devices on
the following media server
or media servers in a pool
Chapter 8, Backing up data
Creating a backup job by setting job properties
This check box displays only if you have the Central Admin Server
Option installed. You can specify if you want a job to run on devices
on a specific managed media server or on devices that are on a
group of managed media servers. This is an additional filter that
lets you control where certain jobs are delegated. For example, to
always run backups of Exchange databases only on the devices that
are attached to managed media servers in a pool named Exchange
Backups, select this option, and then select the Exchange Backups
media server pool.
Media set Select the media set for the backup (see “Changing general media
set properties” on page 268). If you select Overwrite, the media in
the drive is overwritten if the media is scratch, or if its overwrite
protection period has expired. If allocated or imported media are in
the drive, they may also be overwritten depending on the Media
Overwrite Protection Level that is set.
If you selected one of the append options, the backup will be added
to an appendable media (if one exists).
Overwrite media Select this option to place this backup on an overwritable media.
Make sure that appropriate media is in the stand-alone drive or
drive pool you select in the Device field in this dialog box.
The media in the drive is overwritten if the media is scratch or
recyclable (its overwrite protection period has expired). If allocated
or imported media are in the drive, they may also be overwritten
depending on the Media Overwrite Protection Level that is set.
Depending on your configuration, overwritable media is selected
from scratch media or recyclable media. For more information, see
“Setting the search order for overwritable media” on page 270.
If the media in the drive is not overwritable, an alert appears
requesting that you insert overwritable media.
Append to media, overwrite
if no appendable media is
available
Select this option to append this backup to the media set listed in
the Media Set field in this dialog box. The backup set is appended if
an appendable media is available in the selected media set; if not,
an overwritable media is used and added to the media set.
Note If an append job fills a media, the job continues on another
piece of overwritable media.
If the media in the drive is not overwritable, an alert appears
requesting that you insert overwritable media.
355

Creating a backup job by setting job properties
Device and Media options for backup job (continued)
Item Description
Append to media, terminate
job if no appendable media
is available
Eject media after job
completes
Retension media before
backup
Use Write once, read many
(WORM) media
Maximum number of
devices to use for resources
that support multiple data
streams
Minimum number of
devices, terminate job if
fewer devices are available
Select this option to append this backup to the media set listed in
the Media Set field in this dialog box. The backup set is appended if
an appendable media is available in the selected media set; if not,
the job is terminated.
Select this option to have Backup Exec automatically eject the
media in the drive when the operation completes.
Select this option to have Backup Exec run the tape in the drive
from beginning to end at a fast speed, which helps the tape wind
evenly and run more smoothly past the tape drive heads.
Retensioning is primarily for Mini Cartridge and quarter-inch
cartridges and is not supported on most other types of tape drives.
Check Use Write once, read many (WORM) media to use WORM
media for this backup job. Backup Exec confirms that the
destination device is or contains a WORM-compatible drive, and
that the WORM media is available in the drive. If WORM media or a
WORM-compatible drive is not found, an alert is sent.
For more information, see “About WORM media” on page 283.
Select the number of devices that this backup job can use. Only one
device per stream can be used.
Select the minimum number of devices that can be used for this
backup job. If the minimum number of devices is not available, the
job ends without completing.
356 Administrator’s Guide

General options for backup jobs and templates
Chapter 8, Backing up data
Creating a backup job by setting job properties
General options for backup jobs, including the name of the job and the backup method to
be used, can be set through the Backup Job Properties dialog box. To set these options, on
the Properties pane, under Settings, click General.
Options on this dialog box include:
General settings options
Item Description
Job name/Template name Enter the name for this backup job or template, or accept the
default name that appears. The name must be unique.
Backup set description Type a description of the information you are backing up.
357

Creating a backup job by setting job properties
General settings options (continued)
Item Description
Backup method for files Select a backup method. Your choices are:
◆ Full - Back up files
- Using archive bit (reset archive bit). Includes all of the files
selected for backup and resets the archive bit to indicate that
the files have been backed up.
- Using modified time. Includes all of the files selected for
backup and allows the use of incrementals and differentials
using the modified date and time stamp.
- Copy the files. Includes all selected data, and does not affect
any media rotation scheme because the archive bit is not reset.
- Archive the files (delete files after successful copy). Backs up
the selected data, verifies the media, and then deletes the data
from the volume. For data to be deleted, rights to delete a file
must be granted; otherwise data will be backed up, but not
deleted.
Note Backup Exec does not delete data from Backup Exec Agent
workstations when using the archive feature.
◆ Differential - Back up changed files since last full
- Using archive bit (does not reset archive bit). Includes all files
that have changed (based on the archive bit) since the last full
backup, and does not affect any media rotation scheme because
the archive bit is not reset.
- Using modified time. Includes all files changed since the last
full backup, using the files’ last modified date and time stamp.
Make sure that the same script or selection list is used for the
differential backup that was used for the full backup.
◆ Incremental - Back up changed files since last full or
incremental
- Using archive bit (reset archive bit). Includes only the files
that have changed (based on the archive bit) since the last full or
incremental backup and resets the archive bit to indicate that
the files have been backed up.
- Using modified time. Includes all files that have changed since
the last full or incremental backup, using the files’ last modified
date and time stamp. Make sure that the same script or selection
list is used for the incremental backup that was used for the full
backup.
◆ Working Set - Back up files
- Changed today. Backs up all files that were created or modified
today.
358 Administrator’s Guide

General settings options (continued)
Item Description
Backup method for files
(continued)
Chapter 8, Backing up data
Creating a backup job by setting job properties
- Last accessed in (x) days. If you select this backup method, you
can then indicate in the Files accessed in x days field that you
want to include data that has been accessed in a specific number
of days.
For more information, see “Understanding backup methods and
their advantages” on page 308.
Files accessed in x days If you selected Last accessed in (x) days in the Backup method for
files field, use this field to specify the number of days for which to
include accessed files.
Note Symantec recommends that you specify at least 30 days in
order to include the data needed to make your system
operational if you have to restore a working set backup.
Use the Microsoft Change
Journal if available
Select this option if you want to use the Microsoft Change Journal to
determine which files have been modified since the last full backup.
This option can only be used with NTFS volumes. This option is
available when you select one of the following backup methods:
◆ Full - Back Up Files - Using modified time. This method is not
available when performing offhost backup.
◆ Differential - Back up changed files since last full - Using
modified time
◆ Incremental - Back up changed files since last full or
incremental - Using modified time.
In addition, this option becomes available if you select the Collect
additional information for synthetic backup and for true image
restore check box.
Note If you use the Change Journal with the option to collect
additional information for synthetic backup and for true
image restores, the archive bit is not reset, even if you
selected a backup method that has “reset archive bit” in the
name.
If you are backing up volumes with junction points that were
created by linkd.exe, you should not use the Microsoft Change
Journal. Junction points are not followed properly in this situation.
Preserve tree on archive Select this option to retain the directory structure on the hard drive
of the files backed up in an archive job. This option is only available
when Archive is selected as the backup method.
359

Creating a backup job by setting job properties
General settings options (continued)
Item Description
Collect additional
information for synthetic
backup and for true image
restore
Verify after backup
completes
This option displays only for templates. It is used with synthetic
backup jobs and true image restore jobs. It specifies that Backup
Exec collects the information required to detect files and directories
that have been moved, renamed, or newly installed since the last
backup, and then includes those files and directories in the backup
jobs. If this option is not selected, Backup Exec skips these files and
directories if their archive bits are unchanged. With this option
selected, Backup Exec compares path names, file names, modified
times, and other attributes with those from the previous full and
incremental backups. If any of these attributes are new or changed,
then the file or directory is backed up.
Backups that have this option selected require more disk space, and
take more time to run, than backups that do not.
You must select this option for the baseline and incremental backup
template in a synthetic backup policy. For more information about
synthetic backups, see “Symantec Backup Exec Advanced
Disk-based Backup Option” on page 865.
Select this option to have Backup Exec automatically perform a
verify operation to make sure the media can be read once the
backup has been completed. Verifying all backups is recommended.
360 Administrator’s Guide

General settings options (continued)
Item Description
Related Topics:
“Creating a backup job by setting job properties” on page 349
Chapter 8, Backing up data
Compression type Select one of the following:
Creating a backup job by setting job properties
◆ None. Select this option to copy the data to the media in its
original form (uncompressed). Using some form of data
compression can help expedite backups and preserve storage
media space.
Hardware data compression should not be used in environments
where devices that support hardware compression are used
interchangeably with devices that do not have that
functionality.
For example, if a drive that does not support hardware
compression is added to a cascaded drive pool that includes
drives supporting the feature, hardware compression is
automatically disabled. You can manually re-enable hardware
compression on the drives that support it, but this results in
media inconsistency. If the drive that supports hardware
compression fails, the compressed media cannot be restored
with the non-compression drive.
◆ Software. Select this option to use STAC software data
compression, which compresses the data before it is sent to the
storage device.
◆ Hardware [if available, otherwise none]. Select this option to
use hardware data compression (if the storage device supports
it). If the drive does not feature data compression the data is
backed up uncompressed.
◆ Hardware [if available, otherwise software]. Select this option
to use hardware data compression (if the storage device
supports it). If the drive does not feature hardware data
compression, STAC software compression is used.
361

Creating a backup job by setting job properties
Advanced options for backup jobs
To set Advanced options, such as open file options, for backup jobs or backup job
templates, on the Properties pane, under Settings, click Advanced.
Advanced options for backup jobs include:
Advanced options for backup job
Item Description
Enable single instance
backup for NTFS volumes
Back up files and directories
by following junction points
This option is only available if single instance store is being used.
This option ensures that only one instance of a file for NTFS
volumes will be backed up regardless of the number of single
instance store (SIS) links that point to it.
Caution If the backup job does not run to completion, the file data
may not be included in the backup set. Rerun the backup
until it is successfully completed.
If the incremental backup method was used, running the
job again will not back up the same files. You must run a
full or copy backup to ensure that all files are backed up
completely. If the 'incremental - using modified time'
backup method was used, running the same backup job to
completion will back up the files correctly.
Select this check box to back up the information for the junction
points and the files and directories to which they are linked. If this
check box is not selected, then only the information for the junction
points is backed up; the files and directories to which they are
linked are not backed up.
Note Since Mounted Drives that do not have a drive letter assigned
to them cannot be selected, the files and directories to which
they are linked are backed up regardless of whether this
option is selected.
If this option is selected and the actual files and directories to
which the junction points are linked are also included in the
backup selections, then the files and directories are backed up
twice; once during the full file and directory backup, and
again via the junction point.
WARNING: If a junction point is linked to a location that
encompasses it, then recursion (a situation where data is backed up
repeatedly) will occur, resulting in an error and job failure. For
example, if c:\ junctionpoint is linked to c:\, recursion will occur
when attempting to back up c:\ junctionpoint, and the backup job
will fail.
362 Administrator’s Guide

Advanced options for backup job (continued)
Item Description
Back up data in Remote
Storage
Chapter 8, Backing up data
Creating a backup job by setting job properties
Select this check box to back up data that has been migrated from
primary storage to secondary storage. The data is not recalled to its
original location; it is backed up directly to the backup media.
If this option is selected, you should not run a backup of your entire
system because Backup Exec has to load the data that has been
migrated to secondary storage and additional time is required for
any set that includes migrated data.
If this check box is cleared, only the placeholder that stores the
location of the data on secondary storage will be backed up, not the
data itself.
Note This option should not be selected if the device used for
secondary storage and backups contains only one drive
because Remote Storage and Backup Exec will compete for
use of the drive.
Set Remote Agent priority This option allows you to select the number of CPU cycles the media
server will use to maintain optimal server performance while
Remote Agent backups are running. The higher the priority, the
more the protected server’s CPU processing power is used during
backup operations.
Note Allocating fewer CPU cycles to a backup job may result in
slower backup performance.
This field contains the following options:
◆ Normal Priority. Select this option to allocate the default
number of CPU cycles the protected server will use during a
Remote Agent backup.
◆ Below Normal Priority. Select this option to allocate fewer
server CPU cycles to the backup job.
◆ Lowest Priority. Select this option to allocate the fewest number
of CPU cycles to the backup job.
Never Select this option to have Backup Exec skip open files if they are
encountered during the backup operation. A listing of skipped files
appears in the job log for the backup.
363

Creating a backup job by setting job properties
Advanced options for backup job (continued)
Item Description
If closed within x seconds Select this option to have Backup Exec wait the specified time
interval for files to close before skipping the open file and
continuing the backup operation.
If the file does not close during the specified interval, it is skipped.
A listing of skipped files appears in the job log for the backup.
Note If multiple files are open, Backup Exec waits the specified
time interval for each file; depending on the number of open
files, this may significantly increase the backup time.
With a lock Select this option to have Backup Exec attempt to open files that are
in use. If Backup Exec is able to open a file, the file is locked while it
is being backed up to prevent other processes from writing to it.
Backing up open files is not as effective as closing applications and
allowing the files to be backed up in a consistent state.
Without a lock Select this option to have Backup Exec attempt to open files that are
in use. If Backup Exec is able to open the file, the file is NOT locked
while it is being backed up. This allows other applications to write
data to the file during the backup operation.
WARNING: This option allows files that contain inconsistent data
and possibly corrupt data to be backed up.
Allow managed media
server to use any network
interface to access remote
agents
This option displays only if you have the Central Admin Server
Option installed. Select this option to enable a job that is delegated
or copied to a managed media server to use any network interface to
access remote agents. Be default, jobs that are delegated or copied
to a managed media server from the central administration server
use the network and security settings that are set on the managed
media server. If the network specified on the managed media server
is unavailable, selecting this check box enables the managed media
server to use an alternate network to run important jobs.
Note To back up the Removable Storage database in the \Ntmsdata subdirectory, the
WMI repository in the wbem\Repository subdirectory, and the Terminal Services
database in the default \LServer subdirectory, select the \System32
directory. Files that you place in the Systemroot\System32\Ntmsdata
subdirectory, the \wbem\Repository subdirectory, or the default \LServer
subdirectory may not be backed up; only system files are included in the backup. It
is recommended that you do not place user files in the Systemroot\System32
directory or subdirectories.
364 Administrator’s Guide

Chapter 8, Backing up data
Creating a backup job by setting job properties
Related Topics:
“Creating a backup job by setting job properties” on page 349
“Setting defaults for the Advanced Open File Option for backup jobs” on page 850
Pre/post commands for backup or restore jobs
To set commands to run before or after a job, on the Properties pane of the Backup Job
Properties dialog box, the Restore Job Properties dialog box, or the New Backup Job
Template dialog box, under Settings, click Pre/Post Commands.
You can run commands before or after a backup or restore job, and set conditions for
these commands:
■ Run the backup or restore job only if the pre-command is successful
■ Run the post-command only if the pre-command is successful
■ Run the post-command even if the backup or restore job fails
■ Allow Backup Exec to check the return codes (or exit codes) of the pre- and
post-commands to determine if the commands completed successfully. An exit code
of zero returned to the operating system by the pre- or post-command is interpreted
by Backup Exec to mean the command completed successfully. A non-zero exit code
is interpreted by Backup Exec to mean the command ended with an error.
If it is critical that the job does not run if the pre-command fails, then configure Backup
Exec to check the return codes of the pre- and post-commands to determine if the
pre-command failed or completed successfully.
For example, if a pre-command that shuts down a database before a backup is run fails,
the database could be corrupted when the backup is run. In this situation, it is critical
that the backup job does not run if the pre-command fails.
Additionally, if Backup Exec is configured to check the return codes of the pre- and
post-commands, and the post-command returns a non-zero code, the job log reports that
the post-command failed. If you also selected to run the job only if the pre-command is
successful, and both the pre-command and the job ran successfully, Backup Exec will
mark the job as failed if the post-command fails.
For example, if the pre-command runs successfully and shuts down the database and the
backup job also runs successfully, but the post-command cannot restart the database,
Backup Exec marks the job and the post-command as failed.
If you select the option On each server backed up, the pre- and post-commands are run
and completed for each server before processing begins on the next selected server.
365

Creating a backup job by setting job properties
Options for this dialog box include:
Pre- and post-command options
Item Description
Pre-command Specify a command to be run on the specified server before the
backup or restore job is run. Use local paths, and make sure the
paths exist on each server and are correct.
Note Commands that require user interaction, such as prompts,
are not supported.
Post-command Specify a command to be run on the specified server after the
backup or restore job has run. Use local paths, and make sure the
paths exist on each server and are correct.
Note Commands that require user interaction, such as prompts,
are not supported.
Allow pre- and
post-commands to be
successful only if completed
with a return code of zero
Run job only if
pre-command is successful
Select this option to allow Backup Exec to check the return codes of
the pre- and post-commands to determine if they completed
successfully.
An exit code of zero returned to the operating system by the pre- or
post-command is interpreted by Backup Exec to mean that the
command completed successfully. A non-zero exit code is
interpreted by Backup Exec to mean the command ended with an
error.
After checking the return codes, Backup Exec continues processing
according to selections you made for running the pre- and
post-commands.
If this option is not selected, the success of the pre- and
post-commands is not determined based on the return code.
Select this option to run the backup or restore job only if the
pre-command is successful. If the pre-command fails, the job does
not run, and is marked as failed.
If it is critical that the job does not run if the pre-command fails,
then select Allow pre- and post-commands to be successful only if
completed with a return code of zero. If a non-zero code is
returned, it is interpreted by Backup Exec to mean that the
pre-command did not run successfully. The job is not run and the
job status is marked as Failed.
366 Administrator’s Guide

Pre- and post-command options (continued)
Item Description
Run post-command only if
pre-command is successful
Run post-command even if
job fails
Run post-command after
job verification completes
Cancel command if not
completed within x minutes
Related Topics:
“Creating a backup job by setting job properties” on page 349
“Setting default backup options” on page 389
Chapter 8, Backing up data
Creating a backup job by setting job properties
Select this option to run the post-command only if the
pre-command is successful.
If it is critical that the post-command does not run if the
pre-command fails, then select Allow pre- and post-commands to
be successful only if completed with a return code of zero. If a
non-zero code is returned for the pre-command, it is interpreted by
Backup Exec to mean that the pre-command did not run
successfully. The post-command does not run.
If you also select Run job only if pre-command is successful, and
both the pre-command and the job are successful, but the
post-command returns a non-zero code, the job log reports both the
job and the post-command as failed.
Select this option if it is critical to run the post-command regardless
of whether the job is successful or not.
If you also select Allow pre- and post-commands to be successful
only if completed with a return code of zero and the post-command
returns a non-zero code, the job log reports the post-command as
failed.
If you selected the Verify after backup completes option on the
General backup properties dialog box, select this option to run the
post-command after the verification completes.
Select the number of minutes Backup Exec should wait before
canceling a pre- or post-command that did not complete. The
default time-out is 30 minutes.
On this media server Select this option to run the pre- and post-commands on this media
server only.
On each server backed up Select this option to run the pre- and post-commands one time on
each server backed up.
The pre- and post-command selections apply to each server
independently. If you select this option, the pre- and
post-commands are run and completed for each server before
processing begins on the next selected server.
367

Scheduling jobs
“Setting default pre/post commands” on page 396
Scheduling jobs
The schedule option enables you to configure the time and the frequency that you want
to run jobs. You can configure a schedule for jobs such as backup, restore, inventory, and
new catalog. During the job setup, you can choose to run jobs immediately, run once on a
specific day and time, or run according to a schedule.
To configure a schedule for a template in a policy, see “Setting the schedule for a
template” on page 423.
Note When you create a backup selection list, you can set a time range when the
resources in the list will be available for backup. The time range is called the
availability window. If you schedule a job to run outside of the availability window,
the job does not run and Backup Exec displays an Invalid Schedule status for the
job on the Job Monitor. When scheduling a job, be sure that the schedule is within
the availability window for the resources. For more information, see “Setting
priority and availability windows for selection lists” on page 334.
To schedule a job
1. Determine the type of job you want to schedule, and then on the navigation bar, click
the appropriate button. For example, to schedule a backup job, click the arrow next to
Backup.
2. On the Properties pane, under Frequency, click Schedule.
3. Select the appropriate options as follows:.
Current date and time Displays the current date and time set on this computer.
Run now Select Run now to run the job immediately.
Run on Date at Time Select Run on Date at Time to schedule the job to run one time on
the selected date at the selected time, and then type the date and
time.
Run according to
schedule
Select Run according to schedule to configure a schedule for a
recurring job, and then click Edit Schedule Details to configure the
schedule.
368 Administrator’s Guide

4. Click Run Now.
Related Topics:
“Backing up data” on page 345
“Configuring default schedule options” on page 377
“Excluding dates from a schedule” on page 376
Chapter 8, Backing up data
Scheduling jobs
Effective date If Run according to schedule is selected, the effective date displays
the day that the schedule begins.
Time window If Run according to schedule is selected, the time window displays
the specified period of time during which a job can begin on any
scheduled day.
When setting up the time during which a task runs, you can enter a
time window that extends past midnight and into the next day. Bear
in mind, however, that this may change the days on which the task
runs. For example, if you schedule a task to run every Friday
between 8:00 PM and 4:00 AM, it’s possible for the task to run on
Saturday morning sometime before or at 4:00 AM. If you don’t want
the task to run on Saturday, you must alter the time window, for
example, by changing the ending value from 04:00:00 AM to
11:59:59 PM. Then, the task is confined to one day.
Note When a time window crosses midnight, the start time is later
in the day than the end time.
Submit job on hold Select Submit job on hold if you want to submit the job with an
on-hold status.
You should select this option if you want to submit the job, but do
not want the job to run until you change the job’s hold status.
Delete the job if the job
successfully completes
Delete the job after the
job completes
Select this to delete jobs that complete successfully, have been
created to run once, either now or at a scheduled time, and have not
been created from a template. This option is selected by default.
Select this to delete jobs that complete, but with exceptions, have
been created to run once, either now or at a scheduled time, and
have not been created from a template. This option is selected by
default.
Do not delete the job Select this to keep the jobs that were created to run once, and were
not created from a template, in the Job Setup view.
369

Scheduling jobs
About the scheduling calendar
Both the Calendar Schedule tab and the Exclude Dates tab display a three-month
calendar. The calendar provides a way to select days on which you want jobs to run and a
way to view a summary of your schedule.
When you select a day to run a job, a green check mark displays on the calendar. In
addition, when you are viewing a calendar for one type of schedule option, gray check
marks indicate that other types of schedule options are set for those days.
Scheduling a job to run on specific days
To schedule a job to run on specific days
1. Determine the type of job that you want to schedule, and then on the navigation bar,
click the appropriate button.
For example, to schedule a backup job, click the arrow next to Backup.
2. On the Properties pane, under Frequency, click Schedule.
3. Click Run according to schedule.
4. Click Edit Schedule Details.
5. On the Calendar Schedule tab, under Edit Calendar schedule by, click Specific Dates.
6. Do one of the following:
To select a single date ◆ Click New.
7. Click OK.
◆ Enter the date.
◆ Click OK.
To select multiple dates Click the dates on the calendar.
370 Administrator’s Guide

Scheduling a job to run on recurring week days
Chapter 8, Backing up data
Scheduling jobs
Use the recurring week days option to run jobs on the following types of schedules:
Recurring schedule examples
Recurring job option Example
The same day of the
week, every week of
the month
Every day of the
same week of every
month
On selected days
during selected
weeks of the month
To schedule a job to run on recurring week days
1. Determine the type of job that you want to schedule, and then on the navigation bar,
click the appropriate button.
For example, to schedule a backup job, click the arrow next to Backup.
2. On the Properties pane, under Frequency, click Schedule.
3. Click Run according to schedule.
4. Click Edit Schedule Details.
5. On the Calendar Schedule tab, under Edit Calendar schedule by, click Recurring
Week Days.
6. Do one of the following:
To run a job on a single
day
To run a job on the same
day every week
For example, every Wednesday.
For example, every day during the second week of the month.
For example, the last Friday of every month.
Check the check box for that specific day.
Select the name of the day in the matrix. For example, to run a job
every Monday, click Mon
371

Scheduling jobs
To run a job every day of
an entire week
To run a job the last week
of the month, regardless
of the number of weeks in
a month
To run a job on all days of
the month
To clear all existing
selections
7. Click OK.
Scheduling a job to run on recurring days of the month
To schedule a job to run on recurring days of the month
1. Determine the type of job that you want to schedule, and then on the navigation bar,
click the appropriate button.
For example, to schedule a backup job, click the arrow next to Backup.
2. On the Properties pane, under Frequency, click Schedule.
3. Click Run according to schedule.
4. Click Edit Schedule Details.
5. On the Calendar Schedule tab, under Edit Calendar schedule by, click Recurring
Days of the Month.
6. Do one of the following:
To run jobs on specific
days of the month
To run jobs on the last
day of the month,
regardless of the actual
date
Select the row number for that week. For example, to select the
first week of each month, click 1st.
Click Last.
Click Select All.
Click Deselect All.
Click the button for each day.
Check Last Day.
372 Administrator’s Guide

7. Click OK.
Scheduling a job to run on a day interval
Chapter 8, Backing up data
To run a job on all days of
the month
To clear all existing
selections
Scheduling jobs
You can schedule a job to run every certain number of days calculated from a particular
date. For example, you can set up a job to run every three days, starting on January 1,
2006. By default, the date from which the interval is calculated is the current date.
However, you can set a date on which you want the schedule to go into effect. If the
selection list that you are backing up has an availability window, Backup Exec uses the
availability window instead of the date that you select here to calculate the starting date.
For example, you schedule a backup job to run every 7 days beginning on the 11th day of
June. The associated selection list has an availability window that begins on the 12th day
of June. The job is scheduled to run for the first time on June 12th. However, the calendar
indicates that the starting date is June 11th.
Note Recurring tasks run during the specified time window.
To schedule a job to run on a day interval
1. Determine the type of job that you want to schedule, and then on the navigation bar,
click the appropriate button.
For example, to schedule a backup job, click the arrow next to Backup.
2. On the Properties pane, under Frequency, click Schedule.
3. Click Run according to schedule.
4. Click Edit Schedule Details.
5. On the Calendar Schedule tab, under Edit Calendar schedule by, click Day Interval
6. Check Every.
Click Select All.
Click Deselect All.
7. Enter the number of days on which you want the job to recur.
373

Scheduling jobs
8. In the days calculated from box, select the date on which you want the schedule to go
into effect.
The date you enter here does not override the effective date that you set up using the
Effective Date option on the Calendar Schedule tab.
9. Click OK.
Setting the effective date for a job schedule
The effective date determines when your schedule goes into effect. A job cannot run
prior to its effective date. By default, the effective date is the current date.
To set the effective date for a job schedule
1. Determine the type of job that you want to schedule, and then on the navigation bar,
click the appropriate button.
For example, to schedule a backup job, click the arrow next to Backup.
2. On the Properties pane, under Frequency, click Schedule.
3. Click Run according to schedule.
4. Click Edit Schedule Details.
5. On the Calendar Schedule tab, under Edit Calendar schedule by, click Effective Date.
6. Verify that the Make the schedule go into effect check box is checked.
7. Select the date on which you want the schedule to go into effect.
8. Click OK.
Setting the time window for a scheduled job
The time window is the period of time during which a job can begin. The time window
uses a 24-hour clock. The time window does not extend beyond 23 hours, 59 minutes,
and 59 seconds. For example, you cannot set a time window to start at 03:00 and end at
05:00 the next day.
The default time window is from midnight to 23:59:59. If you use the default setting, a
job that is scheduled to run on Monday can begin at or anytime after midnight on
Monday. It cannot start after 23:59:59 on Monday night.
374 Administrator’s Guide

Chapter 8, Backing up data
Scheduling jobs
You can set a time window that extends past midnight and into the next day, which may
change the day on which the job runs. For example, if you schedule a job to run every
Friday between 22:00 and 04:00, the job may run on Saturday morning before or at 04:00.
If you do not want the job to run on Saturday, you must alter the time window to start the
job no later than 23:59:59.
To set the time window for a scheduled job
1. Determine the type of job that you want to schedule, and then on the navigation bar,
click the appropriate button.
For example, to schedule a backup job, click the arrow next to Backup.
2. On the Properties pane, under Frequency, click Schedule.
3. Click Run according to schedule.
4. Click Edit Schedule Details.
5. On the Calendar Schedule tab, under Edit Calendar schedule by, click Time Window.
6. In the Start no earlier than box, select the time after which the job can start.
7. In the and no later than box, select the time by which the job must start.
8. Click OK.
Restarting a job during a time interval
You can set up a job to run multiple times on the scheduled run day during the specified
time interval. You specify the interval at which the job repeats during the time window.
For example, if there is a 12-hour time window for a job, you can set the job to run every
two hours during that time window. The job runs at the interval you specify, respective to
the start time of your time window. The interval must be greater than zero, and less than
23:59:59. In addition, the restart interval must be less than the amount of time set for
the time window. For example, if you have a two-hour time window, you cannot specify a
restart interval greater than 01:59:59.
To restart a job during a time interval
1. Determine the type of job that you want to schedule, and then on the navigation bar,
click the appropriate button.
For example, to schedule a backup job, click the arrow next to Backup.
375

Scheduling jobs
2. On the Properties pane, under Frequency, click Schedule.
3. Click Run according to schedule.
4. Click Edit Schedule Details.
5. On the Calendar Schedule tab, under Edit Calendar schedule by, click Restart Time
Interval.
6. Check Restart task every.
7. Select the time interval in hours, minutes, and seconds.
8. Click OK.
Excluding dates from a schedule
You can exclude specific dates, such as holidays, from a schedule. When you select a date,
the symbol on that date on the calendar changes to a red circle with a line through it.
To exclude dates from a schedule
1. Determine the type of job that you want to schedule, and then on the navigation bar,
click the appropriate button.
For example, to schedule a backup job, click the arrow next to Backup.
2. On the Properties pane, under Frequency, click Schedule.
3. Click Run according to schedule.
4. Click Edit Schedule Details.
5. Click the Exclude Dates tab.
6. Do one of the following:
To exclude a single date ◆ Click New.
◆ Enter the date.
◆ Click OK.
To exclude multiple dates Click the dates on the calendar.
376 Administrator’s Guide

7. Click OK.
Configuring default schedule options
Chapter 8, Backing up data
To add an excluded date
back into the schedule
Using Backup Exec’s Windows Explorer interface to back up data
You can configure default scheduling parameters for all new jobs that you create. If you
want to keep a static schedule for all new jobs that you run according to a schedule, you
can set a default schedule for all jobs, and then use the Run according to schedule
option during job setup to make changes, if necessary.
To configure default schedule options:
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Schedule.
3. Click Edit Schedule Details and then select the appropriate options.
4. Click OK.
Related Topics:
“Backup Exec defaults” on page 138
◆ In the Exclude Dates box, click the date.
◆ Click Delete.
Using Backup Exec’s Windows Explorer interface to back up
data
Backup Exec’s Windows Explorer interface allows you to select and back up files from
Windows Explorer. Backup Exec’s administration console does not have to be running to
create and submit backup jobs from Windows Explorer; however, Backup Exec services
must be running on the server.
The Windows Explorer interface can be used on the Backup Exec server and any
computer running the Backup Exec Remote Administrator (see “To run the Remote
Administrator” on page 109). From the Remote Administrator, you can back up user
shares, but not administrative shares on remote resources.
Backup Exec’s Windows Explorer interface cannot be used to back up databases, such as
Microsoft SQL or Exchange server. To back up a database, use the appropriate Backup
Exec agent. For more information, see “Backup Exec agents and options” on page 62.
377

Using Backup Exec’s Windows Explorer interface to back up data
Note NetBIOS must be enabled to submit a backup job from Windows Explorer.
Setting up Backup Exec to create backups from Windows
Explorer
Note NetBIOS must be enabled to submit a backup job from Windows Explorer.
To set up Backup Exec to create backups from Windows Explorer
1. On the Tools menu, click Options.
2. On the Properties pane, under Settings, click Preferences.
3. Select Enable backup from Windows Explorer.
4. Click OK.
The Back up with Backup Exec option now appears on the Windows Explorer
shortcut menu.
Related Topics:
“Backup Exec defaults” on page 138
“Submitting a backup job from Windows Explorer” on page 378
“Archiving data” on page 380
Submitting a backup job from Windows Explorer
After you have set up Backup Exec to create backups from Windows Explorer, you can
submit a backup job. The first time you submit a backup job using the Backup Exec
Windows Explorer interface, you can specify logon information for a remote media
server and enter a backup device name. The Backup Settings dialog box allows you to
save the settings, which are used for subsequent backup jobs submitted from Windows
Explorer. If you do not save the settings, you need to enter the logon information and the
backup device name each time you submit a backup job from Windows Explorer.
The first time you run a backup on a resource, you must use the Backup Exec graphical
user interface. If the first backup on a resource is from the Windows Explorer interface,
the job will fail and will continue to fail until you run a job from Backup Exec.
Note NetBIOS must be enabled to submit a backup job from Windows Explorer.
378 Administrator’s Guide

To submit a backup job from Windows Explorer
Chapter 8, Backing up data
Using Backup Exec’s Windows Explorer interface to back up data
1. From Windows Explorer, select the files or folders you want to back up.
2. Right-click the selected files or folders and select Back up with Backup Exec from
the shortcut menu.
3. On the Backup Settings dialog box, select the appropriate options as follows:
Server Name Type the name of the media server on which Backup Exec is
installed.
User Name View or change the user name. The default is the name of the
user currently logged on to the machine. You can enter a
different user or administrator.
Note If you are logged on as part of a workgroup, the user
domain is your local machine name.
Password Type the password for the user.
Job Name View or change the job name. Backup Exec generates a unique
name for the backup job in the format: Backup . If the job name exceeds 25 characters, the
utility truncates the local machine name. For example:
For a backup run on a machine named ADMN-30PAYROLL,
Backup Exec could generate the job name Backup ADMN-30P
960576233.
If you change the default job name, you must ensure it is a
unique job name.
Device Name Type the name of the backup device.
Include subdirectories in
backup
Select this option to include all subfolders within the selected
folders in the backup job.
Save Settings Select this option to save the backup settings as defaults for
subsequent backup jobs.
Note You must submit a backup job to save the settings in the
Registry.
Clear this option if you want to change the settings for a single
backup job but keep the defaults saved in the Registry.
Job Status View the status of a job, confirmation and error messages, and
the job ID.
379

Archiving data
The backup job defaults to the options set in the Backup tab. For more information,
see “Setting default backup options” on page 389.
4. Click Submit Job.
Archiving data
5. Click Close Dialog after the backup job has been submitted and confirmed. You must
close the Backup Settings dialog box to submit another backup job from Windows
Explorer.
Related Topics:
“Archiving data” on page 380
With Backup Exec’s archive feature, you can free valuable disk space and reduce clutter
on your server volume by migrating stagnant directories and files from the server to
media.
If you select archive as your backup method when creating a job, Backup Exec backs up
the selected data, verifies the media, and then deletes the data from the volume.
Note For data to be deleted, rights to delete a file must be granted; otherwise data will be
backed up, but not deleted.
Backup Exec does not delete data from Backup Exec Agent workstations when
using the archive feature.
During an archive job, Backup Exec automatically performs a verify operation after the
data is backed up. If the verify operation fails, the archive job stops and you are notified.
If you get a verification failure, investigate the problem by viewing the job log, try to
correct the problem, and then retry the archive operation. After the data is backed up
and verified, Backup Exec automatically deletes the data included in the archive job. The
job log contains a list of the data that was deleted.
Note If the checkpoint restart setting is enabled for an archive backup job that is
resumed when a cluster failover occurs, the files selected for archive are not
automatically deleted from the source volume after the backup completes.
The archive operation can be used to perform disk grooming, which uses Windows’ last
access date to move obsolete files from the server to media.
Note The NTFS file system supports the last access date capability.
380 Administrator’s Guide

To archive data
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. Select the data that you want to archive.
4. Click General.
Chapter 8, Backing up data
Duplicating backed up data
5. In the Backup method for files field, select Working Set - Back up files - Last
accessed in (x) days.
6. In the Files accessed in x days field, enter the number of days to use as the criteria
for selecting the files.
7. Complete the backup job options following the procedures described in “Creating a
backup job by setting job properties” on page 349.
Related Topics:
“Including or excluding files for backup” on page 325
“Archiving data” on page 380
Duplicating backed up data
You can create a job to duplicate backup data, selecting either to duplicate existing
backup sets or to duplicate backup sets immediately following a scheduled job.
If you select to duplicate existing backup sets, the backup sets you select from catalogs
are read from the source media and written to the selected destination, such as a drive,
drive pool, or backup folder. You can schedule when this type of job runs.
If you duplicate Oracle or DB2 backup sets that were created with multiple data streams,
note the following
■ Backup Exec converts the multiple data streams to a sequential data stream during
the duplication job.
■ A restore job from the duplicated copy may be slower than a restore job from the
original media.
If you select to duplicate backup sets following a job, you select a scheduled backup job as
the source. That backup job runs first, and then the backup sets it created are copied to
the destination you selected for the duplicate job. To duplicate backup sets following a
381

Duplicating backed up data
job, the backup job must be scheduled to run and must not be associated with any other
duplicate jobs. You cannot schedule this job; instead, the duplicate job runs only after the
related, or linked, backup job completes.
To duplicate backup data
1. From the navigation bar, click Job Setup.
2. Under Backup Tasks, select New job to duplicate backup sets.
3. If you want to copy existing backup sets to another destination:
■ Select Duplicate existing backup sets, and then click OK.
■ Select the backup sets you want to copy. For Oracle or DB2 jobs that were created
with multiple data streams, under the instance name, select the date on which
the backup set was created.
4. If you want to duplicate backup sets created when a scheduled backup job runs:
■ Select Duplicate backup sets following a job, and then click OK.
■ Select the scheduled backup job to be used as the source.
5. On the Properties pane, under Destination, select Device and Media, and complete
the options as described in “Device and media options for backup jobs and
templates” on page 354.
6. On the Properties pane, under Settings, click General, and complete the appropriate
options as follows:
Job name Type the name for this backup job.
Job priority Select the priority level for this job. If another job is scheduled to
run at the same time as this job, the priority you set determines
which job runs first. Your choices are:
◆ Highest
◆ High
◆ Medium
◆ Low
◆ Lowest
Backup set description Type a description of the information you are backing up.
382 Administrator’s Guide

Chapter 8, Backing up data
Duplicating backed up data
Preferred source device Select the device used as the destination device for the original
backup job.
7. On the Properties pane, under Settings, click Advanced, and complete the
appropriate options as follows:
Verify after backup
completes
Select this option to have Backup Exec automatically perform a
verify operation to make sure the media can be read after the
backup has been completed. Verifying all backups is
recommended.
Compression type Select one of the following:
◆ None. Select this option to copy the data to the media in its
original form (uncompressed). Using some form of data
compression can help expedite backups and preserve storage
media space.
Hardware data compression should not be used in
environments where devices that support hardware
compression are used interchangeably with devices that do
not have that functionality.
For example, if a drive that does not support hardware
compression is added to a cascaded drive pool that includes
drives supporting the feature, hardware compression is
automatically disabled. You can manually re-enable hardware
compression on the drives that support it, but this results in
media inconsistency. If the drive that supports hardware
compression fails, the compressed media cannot be restored
with the non-compression drive.
◆ Hardware [if available, otherwise none]. Select this option to
use hardware data compression (if the storage device supports
it). If the drive does not feature data compression the data is
backed up uncompressed.
8. To encrypt the duplicated data, do the following in the order listed:
■ On the Properties pane, under Settings, click Network and Security.
■ Select an encryption key from the list or click Manage keys to create a new key.
9. If you want Backup Exec to notify someone when the backup job completes, on the
Properties pane, under Settings, click Notification (see “Assigning notification
recipients for completed jobs” on page 565).
10. If you are duplicating data from a scheduled backup job, click Run Now.
383

Verifying a backup
The duplicate job will launch immediately following the completion of the scheduled
backup job.
11. If you are duplicating data from an existing backup set, either click Run Now or
under Frequency, click Schedule to set the scheduling options you want to use (see
“Scheduling jobs” on page 368).
Verifying a backup
In addition to the verification of files that is done when a backup or archive job runs, you
can submit verify jobs to test the integrity of the media.
If you perform a verify operation and files fail to verify, the media may be bad. Details
about files that failed to verify are provided in the job log, which can be viewed from the
Job Monitor.
To verify a backup
1. On the navigation bar, click Job Setup.
2. In the task pane, under Backup Tasks, click New job to verify backup data.
3. Select the media you want to verify.
4. On the Properties pane, under Destination, click Device.
5. Select the device that contains the media you want to verify.
6. On the Properties pane, under Settings, click General.
7. Select the appropriate options as follows:
Job name Type a name that describes the data you are verifying.
Job priority Select the priority level for this job. If another job is scheduled to
run at the same time as this job, the priority you set determines
which job runs first. Your choices are:
◆ Highest
◆ High
◆ Medium
◆ Low
◆ Lowest
384 Administrator’s Guide

Chapter 8, Backing up data
Creating a test run job
8. If you want Backup Exec to notify someone when the backup job completes, on the
Properties pane, under Settings, click Notification (see “Assigning notification
recipients for completed jobs” on page 565).
9. If you want to run the job now, click Run Now. Otherwise, on the Properties pane,
under Frequency, click Schedule to set the scheduling options you want to use (see
“Scheduling jobs” on page 368).
After verification has completed, you can check the results in the job log.
Related Topics:
“Setting default backup options” on page 389
“Verify after backup completes” on page 383
Creating a test run job
The Backup Exec test run option determines if a scheduled backup will complete
successfully. When you run a test job, you can monitor the job just as you would a normal
backup job, but no data is backed up. During the test run, the tape capacity, credentials,
and media are checked. If there is an error, the job will continue to run and the error will
appear in the job log. Notification can also be sent to a designated recipient.
During a test run job, the following may cause a job to fail:
■ The logon credentials are incorrect.
■ Insufficient media is available.
■ Media is not in the drive.
■ There is no overwritable media for an overwrite job.
■ There is no appendable media for an append job.
Test run jobs that are targeted to All Drives will fail the test if any of the devices in the
All Drives drive pool cannot handle the job. For example, if one of the devices does not
have any media.
A test run job checks media capacity available for the selected job. However, you can
check if there is enough available media for multiple test run jobs in the Test Run Results
report.
Note Before you create a test run job, Symantec recommends that you run backup jobs
to your devices first. Backup Exec does not recognize the capacity of a backup
device until an actual backup job is targeted to the device. If you create a test run
385

Creating a test run job
job before any other jobs, Backup Exec cannot check that the device has sufficient
capacity to perform the backup job. After at least one backup job has been targeted
to a device, Backup Exec can determine the capacity.
To create a test run job
1. On the navigation bar, click Job Setup.
2. In the Jobs pane, select the job for which you want to create a test run.
3. Under General Tasks, click Test Run.
4. Select the appropriate General options as follows:
Job name Type a name for the test run job.
Credentials check Select this check box to verify that the Backup Exec logon account
is correct for the resources being backed up.
Media capacity check to
complete individual job
Select this check box to test if there is enough available capacity
on the media to complete the job.
Note During the test run job, the number of scheduled jobs in the
queue is not checked; therefore, jobs that are scheduled
before the test run job may use the media that was available
when the test run job was performed.
Media check Select this check box to test whether the media is online and
overwritable.
Use previous job history,
if available
Select this option to use past job histories to determine whether
there is enough media available to run the scheduled backup job.
Checking the previous job history is faster than performing a
pre-scan.
Perform Pre-scan Select this option to enable Backup Exec to scan the scheduled
backup job to determine whether there is enough media available
to run the job. This is the most accurate method of determining
media capacity and should be selected if there is not an existing
job history.
Upon any failure, place
the scheduled job on hold
Select this option to have the scheduled job placed on hold if any
failures are detected during the test run.
386 Administrator’s Guide

Chapter 8, Backing up data
Creating a test run job
Run at priority Select the priority level for the test job. If another job is scheduled
to run at the same time as this job, the priority you set determines
which job runs first. Your choices are:
◆ Highest
◆ High
◆ Medium
◆ Low
◆ Lowest
5. If you want Backup Exec to notify a recipient when the backup job completes, on the
Properties pane, under Settings, click Notification (see “Assigning notification
recipients for completed jobs” on page 565).
6. If you want to run the job now, click Run Now. Otherwise, on the Properties pane,
under Frequency, click Schedule to set the scheduling options you want to use (see
“Scheduling jobs” on page 368).
Related Topics:
“Viewing general media properties” on page 298
“Creating a backup job by setting job properties” on page 349
“Test Run Results Report” on page 652
Setting test run default options
To set test run default options
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Test Run.
3. Select the appropriate options as follows:
Check credentials Select this check box to verify that the Backup Exec logon account
is correct for the resources being backed up.
387

Creating a test run job
Check media capacity to
complete job
4. Click OK.
Select this check box to test if there is enough available capacity on
the media to complete the job.
Note During the test run job, the number of scheduled jobs in the
queue is not checked; therefore, jobs that are scheduled
before the test run job may use the media that was available
when the test run job was performed.
Check media availability Select this check box to test whether the media is online and
overwritable.
Use previous job history,
if available
Select this option to use past job histories to determine whether
there is enough media available to run the scheduled backup job.
Checking the previous job history is faster than performing a
pre-scan.
Perform Pre-scan Select this option to enable Backup Exec to scan the scheduled
backup job to determine whether there is enough media available to
run the job. This is the most accurate method of determining media
capacity and should be selected if there is not an existing job
history.
Place the scheduled job
on hold if any failure
occurs during the Test
Run job
Select this option to have the scheduled job placed on hold if any
failures are detected during the test run.
388 Administrator’s Guide

Customizing backup
options
Customizing backup options consist of the following:
■ Setting default backup options
■ Setting default pre/post commands
■ Specifying a backup network
■ Setting up encryption keys
Setting default backup options
Chapter
9
You can set up Backup Exec with the settings that you want to use for most backup
operations, such as the backup method and compression type. If the default options are
not appropriate for a particular backup job, you can override the default options when
you set up a backup job.
To set default backup options
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Backup.
3. Select the appropriate options as follows:
Backup method for files Select the default Backup method. Full - Back up files - Using
archive bit (reset archive bit) is the typical selection for this
field. For more information about backup methods, see
“Understanding backup methods and their advantages” on
page 308.
389

Setting default backup options
Files accessed in x days When the Working Set backup method is selected, use this field
to specify the number of days for which to include accessed files.
Use the Microsoft Change
Journal if available
Collect additional
information for synthetic
backup and for true image
restore
Select this option if you want to use Windows’ NTFS Change
Journal to determine which files have been modified since the
last full backup. This option can only be used with NTFS volumes
and only when the backup method selected is Full - Back up files
- Using modified time, Differential - Using modified time or
Incremental - Using modified time.
This option displays only for templates. It is used with synthetic
backup jobs and true image restore jobs. Select this option is you
want Backup Exec to:
◆ Collect the information that is required to detect files and
directories that have been moved, renamed, or newly
installed since the last backup
◆ Include those files and directories in the backup jobs.
If you do not select this option, Backup Exec skips the files and
directories that have unchanged archive bits. When you select
this option, Backup Exec compares path names, file names,
modified times, and other attributes with those from the
previous full and incremental backups. If any of these attributes
are new or changed, then the file or directory is backed up.
Backup jobs that have this option selected require more disk
space, and take more time to run, than backups that do not.
You must select this option for the baseline and incremental
backup template in a synthetic backup policy. For more
information about synthetic backups, see “Symantec Backup
Exec Advanced Disk-based Backup Option” on page 865.
390 Administrator’s Guide

Chapter 9, Customizing backup options
Setting default backup options
Media overwrite protection Select one of the following media overwrite options:
◆ Overwrite media. Select this option to place this backup on
an overwritable media. Make sure that appropriate media is
in the stand-alone drive or drive pool you select in the Device
field in this dialog box.
The media in the drive is overwritten if the media is scratch
or recyclable (its overwrite protection period has expired). If
allocated or imported media are in the drive, they may also be
overwritten depending on the Media Overwrite Protection
Level that is set. For more information, see “Media overwrite
protection levels” on page 270.
If the media in the drive is not overwritable, a message is
displayed requesting that you insert overwritable media.
◆ Append to media, overwrite if no appendable media is
available. Select this option to add this backup to the media
set listed in the Media Set field in the General applications
dialog box (see “Changing default preferences” on page 139).
The backup set is appended if an appendable media is
available in the selected media set; if not, an overwritable
media is used and added to the media set.
If an append job fills a media, the job continues on another
piece of overwritable media.
Depending on your configuration, overwritable media is
selected from Scratch media or Recyclable media. For more
information, see “Media overwrite protection” on page 260.
If the media in the drive is not overwritable, a message is
displayed requesting that you insert overwritable media.
◆ Append to media, terminate job if no appendable media is
available. Select this option to add this backup to the media
set listed in the Media Set field in the General applications
dialog box (see “Changing default preferences” on page 139).
The backup set is appended if an appendable media is
available in the selected media set; if not, the job is
terminated.
391

Setting default backup options
Compression type Select one of the following compression types:
◆ None. Select this option to copy the data to the media in its
original form (uncompressed).
Note Using some form of data compression can help expedite
backups and preserve storage media space.
◆ Software. Select this option to use STAC software data
compression, which compresses the data before it is sent to
the storage device.
◆ Hardware [if available, otherwise none]. Select this option
to use hardware data compression (if the storage device
supports it). If the drive does not feature data compression,
the data is backed up uncompressed.
◆ Hardware [if available, otherwise software]. Select this
option to use hardware data compression (if the storage
device supports it). If the drive does not feature hardware
data compression, STAC software compression is used.
Verify after backup Select this option if you want backups to be verified after they
are completed. Verify operations make sure the media can be
read once the backup has been completed. Verifying all backups
is recommended.
392 Administrator’s Guide

Back up files and
directories by following
junction points
Back up data in Remote
Storage
Chapter 9, Customizing backup options
Setting default backup options
Select this check box to back up the information for the junction
points and the files and directories to which they are linked. If
this check box is not selected, then only the information for the
junction points is backed up; the files and directories to which
they are linked are not backed up.
If you use junction points created by linkd.exe (or a similar tool)
to span volumes, then Advanced Open File Option (AOFO)
backups and Change Journal incremental backups will not follow
the junction points properly. To perform AOFO and Change
Journal incremental backups of volumes with junction points,
clear this option. Junction points created by Disk Manager or
mountvol.exe are supported.
Note Since Mounted Drives that do not have a drive letter
assigned to them cannot be selected, the files and
directories to which they are linked are backed up
regardless of whether this option is selected.
If this option is selected and the actual files and directories
to which the junction points are linked are also included in
the backup selections, then the files and directories are
backed up twice; once during the full file and directory
backup, and again via the junction point.
WARNING: If a junction point is linked to a location that
encompasses it, then recursion (a situation where data is backed
up repeatedly) will occur, resulting in an error and job failure. For
example, if c:\ junctionpoint is linked to c:\, recursion will occur
when attempting to back up c:\ junctionpoint, and the backup job
will fail.
Select this check box to back up data that has been migrated
from primary storage to secondary storage. The data will not be
recalled to its original location; it will be backed up directly to the
backup media.
If this option is selected, you should not run a backup of your
entire system because Backup Exec will have to load the data that
has been migrated to secondary storage and additional time will
be required for any set that includes migrated data.
If this check box is cleared, only the placeholder that stores the
location of the data on secondary storage will be backed up, not
the data itself.
Note This option should not be selected if the device used for
secondary storage and backups contains only one drive
because Remote Storage and Backup Exec will compete for
use of the drive.
393

Setting default backup options
Enable single instance
backup for NTFS
Select this option if you want Backup Exec to protect Single
Instance Store (SIS) volumes. SIS, which is used by Remote
Installation Services to save disk space, maintains a single
physical copy of all identical files on a specified volume. If SIS
finds an identical file on the volume, a copy of the original file is
placed in the SIS and a link is made to the actual physical
location. By selecting this option, Backup Exec will back up the
physical file one time, no matter how many links have been
created.
Caution If the backup job does not run to completion, the file
data may not be included in the backup set. Rerun the
backup until it is successfully completed.
If the incremental backup method was used, running
the job again will not back up the same files. You must
run a full or copy backup to ensure that all files are
backed up completely. If the incremental - using
modified time backup method was used, running the
same backup job to completion will back up the files
correctly.
Never Select this option to have Backup Exec skip open files if they are
encountered during the backup operation. A listing of skipped
files appears in the job log for the backup.
If closed within x seconds Select this option to have Backup Exec wait the specified time
interval for files to close before skipping the open file and
continuing the backup operation.
If the file does not close during the specified interval, it is
skipped. A listing of skipped files appears in the job log for the
backup.
Note If multiple files are open, Backup Exec waits the specified
time interval for each file; depending on the number of
open files, this may significantly increase the backup time.
With a lock Select this option to have Backup Exec attempt to open files that
are in use. If Backup Exec is able to open a file, the file is locked
while it is being backed up to prevent other processes from
writing to it. Backing up open files is not as effective as closing
applications and allowing the files to be backed up in a
consistent state.
394 Administrator’s Guide

Chapter 9, Customizing backup options
Setting default backup options
Without a lock Select this option to have Backup Exec attempt to open files that
are in use. If Backup Exec is able to open the file, the file is NOT
locked while it is being backed up. This allows other applications
to write data to the file during the backup operation.
WARNING: This option allows files to be backed up that contain
inconsistent data and possibly corrupt data.
For information about the Advanced Open File Option, see
“Symantec Backup Exec Advanced Open File Option” on
page 843.
395

Setting default pre/post commands
Setting default pre/post commands
You can set defaults for the commands you want to run before or after all backup and
restore jobs. If the default options are not appropriate for a particular job, you can
override the default options when you create the job.
Conditions that you can set for these commands include:
■ Run the backup or restore job only if the pre-command is successful
■ Run the post-command only if the pre-command is successful
■ Run the post-command even if the backup or restore job fails
■ Allow Backup Exec to check the return codes (or exit codes) of the pre- and
post-commands to determine if the commands completed successfully. An exit code
of zero returned to the operating system by the pre- or post-command is interpreted
by Backup Exec to mean the job completed successfully. A non-zero exit code is
interpreted by Backup Exec to mean the job ended with an error.
If it is critical that the job not run if the pre-command fails, then configure Backup Exec
to check the return codes of the pre- and post-commands to determine if the
pre-command failed or completed successfully.
For example, if a pre-command that shuts down a database before a backup is run fails,
the database could be corrupted when the backup is run. In this situation, it is critical
that the backup job not run if the pre-command fails.
Additionally, if Backup Exec is configured to check the return codes of the pre- and
post-commands, and the post-command returns a non-zero code, the job log reports that
the post-command failed. If you also selected to run the job only if the pre-command is
successful, and both the pre-command and the job ran successfully, Backup Exec will
mark the job as failed if the post-command fails.
For example, if the pre-command runs successfully and shuts down the database and the
backup job also runs successfully, but the post-command cannot restart the database,
Backup Exec marks the job and the post-command as failed.
If you select the option On each server backed up, the pre- and post-commands are run
and completed for each server before processing begins on the next selected server.
To set default pre/post commands
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Pre/Post Commands.
396 Administrator’s Guide

3. Select the appropriate options as follows:
Allow pre- and
post-commands to be
successful only if
completed with a return
code of zero
Run job only if
pre-command is successful
Run post-command only if
pre-command is successful
Run post-command even if
job fails
Chapter 9, Customizing backup options
Setting default pre/post commands
Select this option to allow Backup Exec to check the return codes
of the pre- and post-commands to determine if they completed
successfully.
An exit code of zero returned to the operating system by the preor
post-command is interpreted by Backup Exec to mean the job
completed successfully. A non-zero exit code is interpreted by
Backup Exec to mean the job ended with an error.
After checking the return codes, Backup Exec continues
processing according to selections you made for running the preand
post-commands.
If this option is not selected, the success of the pre- and
post-commands is not determined based on the return code.
Select this option to run the backup or restore job only if the
pre-command is successful. If the pre-command fails, the job
does not run, and is marked as failed.
If it is critical that the job not run if the pre-command fails, then
select Allow pre- and post-commands to be successful only if
completed with a return code of zero. If a non-zero code is
returned, it is interpreted by Backup Exec to mean that the
pre-command did not run successfully. The job is not run and the
job status is marked as Failed.
Select this option to run the post-command only if the
pre-command is successful.
If it is critical that the post-command fail if the pre-command
fails, then select Allow pre- and post job commands to be
successful only if completed with a return code of zero. If a
non-zero code is returned for the pre-command, it is interpreted
by Backup Exec to mean that the pre-command did not run
successfully. The post-command is not run.
If you also select Run job only if pre-command is successful,
and both the pre-command and the job are successful, but the
post-command returns a non-zero code, the job log reports both
the job and the post-command as failed.
Select this option if it is critical to run the post-command
regardless if the job is successful or not.
If you also select Allow pre- and post job commands to be
successful only if completed with a return code of zero and the
post-command returns a non-zero code, the job log reports the
post-command as failed.
397

Specifying backup networks
Run post-command after
job verification completes
Cancel command if not
completed within x
minutes
4. Click OK.
Related Topics:
“Pre/post commands for backup or restore jobs” on page 365
Specifying backup networks
If you selected the Verify after backup completes option on the
General backup properties dialog box, select this option to run
the post-command after the verification completes.
Select the number of minutes Backup Exec should wait before
canceling a pre-job or post-command that did not complete. The
default time-out is 30 minutes.
On this media server Select this option to run the pre- and post-commands on this
media server only.
On each server backed up
or restored to
Select this option to run the pre- and post-commands one time
on each server backed up or restored to.
The pre- and post-command selections apply to each server
independently. If you select this option, the pre- and
post-commands are run and completed for each server before
processing begins on the next selected server.
The Backup Network feature allows you to direct primary backup traffic generated by
Backup Exec to a specific local network. Directing backup jobs to a specified local
network isolates the backup data so that other connected networks are not affected
when backup operations are performed. You also can use a backup network when
restoring data. The feature is enabled on the media server and allows you to protect all
the remote computers that reside on the specified local network.
When the feature is enabled and a backup job is submitted, Backup Exec verifies that the
remote computer is on the same subnet as the selected interface on the media server. If
the remote computer is on the selected subnet, then the backup operation is performed.
If the remote computer is not on the selected subnet, then the job fails. However, you
can set up Backup Exec to use any available network to back up remote computers. The
following diagram shows an example of a basic backup network configuration.
398 Administrator’s Guide

Example of backup network
Backup Exec media server
Chapter 9, Customizing backup options
IP address:
128.10.0.1
IP address:
10.67.0.1
IP address:
128.10.0.2
IP address:
10.67.0.2
database server running Remote Agent
corporate network
network ID: 128.20.0.0
subnet mask: 255.255.0.0
Specifying backup networks
backup network
network ID: 128.10.0.0
subnet mask: 255.255.0.0
IP address:
128.10.0.3
IP address:
10.67.0.3
router A
router B
mail server running Remote Agent
database user mail user
database and mail user
In the example, the database server and mail server are connected to both the backup
network and the corporate network.
When backup operations are performed by the Backup Exec media server, the backup
data will use either the backup network or the corporate network to back up the database
server. If the backup data goes through the corporate network, the amount of time it
takes to back up the database server will increase because the network route between the
two computers is longer. This may cause users to experience network latencies when
accessing the mail server since there is an increase in network traffic.
In contrast, if the Specified Backup Network feature is enabled and you back up the
database server, the backup data traffic is isolated to the backup network and users
accessing the mail server are not affected. The backup network will be used to perform
all backup operations, unless the remote computer is not connected to the backup
network.
If you want to back up remote computers that are not connected to the backup network,
such as the database user’s computer, then choose to use any available network route.
This allows you to back up the remote computer even though it does not reside on the
backup network.
399

Specifying backup networks
Related Topics:
“Using Backup Exec with firewalls” on page 405
“Browsing systems through a firewall” on page 406
About using IPv4 and IPv6 in Backup Exec
Backup Exec supports versions 4 and 6 of the Internet Protocol (IP), which are commonly
referred to as IPv4 and IPv6. You can use IPv4 and IPv6 in backup and restore networks.
Support for IPv6 is dependent upon operating system support for the protocol, as well as
proper network configuration.
You can use Backup Exec in a mixed IPv4/IPv6 environment or an IPv4-only
environment.
Enter an IPv4 or IPv6 address for a computer anywhere that you can enter a computer
name in Backup Exec, except in the following locations:
■ User-defined selections.
■ Clusters. Microsoft Windows does not support an IPv6 address as a clustered
resource.
■ The Connect to Media Server dialog box
A Remote Agent that supports IPv6 can be backed up or restored using IPv6 only from a
media server that is IPv6-compliant.
Setting default backup network and security options
You can specify a network to be used as the default for every Backup Exec job. Before
configuring the feature, test for network connectivity between the media server and the
remote computers.
Note The remote computers that you want to back up must have the most current
version of Backup Exec Remote Agent installed.
To set the default backup network and security options
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Network and Security.
400 Administrator’s Guide

3. Select the appropriate options as follows:
Enable selection of user
shares
Chapter 9, Customizing backup options
Specifying backup networks
Select this option to enable selection of Windows user shares.
401

Specifying backup networks
Enable remote agent TCP
dynamic port range
Select this option if you want to allow remote agents to use a
range of ports for communications, and then enter the port
range. If the first port that Backup Exec attempts to use is not
available, communications will be attempted through one of the
other ports in the range. If none of the ports in the range are
available, Backup Exec will use any available dynamic port.
Default port ranges are 1025 to 65535. Symantec recommends
using a range of 25 allocated ports for the remote systems if
using Backup Exec with a firewall (see “Using Backup Exec with
firewalls” on page 405).
Interface Select the name of the network interface card that connects the
media server to the network you want to use for the backup
network. The list includes all available network interface cards
on the media server.
Interface details Displays the Media Access Control (MAC) address, Adapter type,
Description, IP addresses, and subnet prefixes of the network
interface you selected for the backup network.
Protocol Select the protocol you want to use. The options are:
◆ Use any available protocol
◆ Use IPv4
◆ Use IPv6
Subnet Displays the 32-bit number that determines the subnet to which
the network interface card belongs.
Allow use of any available
network interface, subnet,
or protocol for remote
agents not bound to the
above network interface,
subnet, or protocol
If a remote system that you selected for backup or restore is not
part of the specified backup network, select this check box to
ensure that the data from the remote system is backed up or
restored over any available network.
If you do not select this check box and you selected data from a
remote system that is not part of the specified backup network,
the job fails because Backup Exec cannot back up or restore the
data from the remote system
402 Administrator’s Guide

Use a custom port to
receive operation requests
from the remote system
Related Topics:
“Changing the backup network for a job” on page 403
“Specifying the restore network” on page 523
Changing the backup network for a job
Chapter 9, Customizing backup options
Specifying backup networks
When you set up a default network, Backup Exec uses it automatically for every backup
and restore job. However, when you are setting up a new backup job, you can change the
backup network for that job. When you change the backup network for a job, you also can
set that backup network as the new default backup network for all future backup jobs.
To change the backup network for a job
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
Check Use a custom port to receive operation requests from the
remote system to change the port used for communications
between this computer and the remote computer for both DBAand
media server-initiated operations. By default, port 5633 is
used.
If you change the port number on the remote Windows or Linux
computer, you must also change it on the media server, and then
restart the Backup Exec Job Engine service on the media server.
For information on how to change the port number on the
remote Linux computer, see “What to do when Oracle instance
information changes” on page 1413.
Encryption key Select the default encryption key you want to use.
Manage keys Click Manage keys to create a new encryption key, delete an
encryption key, or set an encryption key as the default.
3. Set up the backup job as usual by selecting data and setting General and Advanced
options (see “Creating a backup job by setting job properties” on page 349).
4. On the Properties pane, under Settings, click Network and Security.
403

Specifying backup networks
5. Select the appropriate options as follows:
Network Interface Select the name of the network interface card that connects the
media server to the network you want to use for the backup
network for this backup job. The list includes all available network
interfaces on the media server.
If you are using the Central Admin Server Option (CASO), select the
Use the default network interface for the managed media server
option if you want CASO delegated backup jobs to be processed
using the network interface card configured as the default in the
managed media server.
Subnet Displays the 32-bit number that determines the subnet to which
the network interface card belongs.
Protocol Select the protocol you want to use. The options are:
◆ Use any available protocol
◆ Use IPv4
◆ Use IPv6
Allow use of any
available network
interface, subnet, or
protocol for remote
agents not bound to the
above network interface,
subnet, or protocol
6. Complete the backup job as normal.
If a remote system that you selected for backup is not part of the
specified backup network, select this check box to ensure that the
data from the remote system is backed up over any available
network.
If you do not select this check box and you selected data from a
remote system that is not part of the specified backup network, the
job fails because Backup Exec cannot back up the data from the
remote system.
Interface details Displays the Media Access Control (MAC) address, Adapter type,
Description, IP addresses, and subnet prefixes of the network
interface you selected for the backup network.
Encryption key Select the encryption key you want to use.
Manage keys Click Manage keys to create a new encryption key, delete an
encryption key, or set an encryption key as the default.
Related Topics:
“Specifying backup networks” on page 398
“Setting default backup network and security options” on page 400
404 Administrator’s Guide

“Creating a backup job by setting job properties” on page 349
Using Backup Exec with firewalls
Chapter 9, Customizing backup options
Using Backup Exec with firewalls
In firewall environments, Backup Exec provides the following advantages:
■ The number of ports used for backup network connections is kept to a minimum.
■ Ports opened on the Backup Exec Server and systems using the Remote Agent for
Windows Servers are dynamic and offer high levels of flexibility during browsing,
backup, and restore operations.
■ You can set specific firewall port ranges and specify backup and restore networks
within these ranges to isolate data traffic and provide high levels of reliability.
Note The Remote Agent for Windows Servers is required to perform remote backups and
restores.
Because firewalls affect system communications between a media server and remote
systems that reside outside the firewall environment, special port requirements must be
considered when configuring Backup Exec for use with firewalls.
Symantec recommends having port 10000 open and available on the Backup Exec media
server as well as on the remote systems. In addition, you must open the dynamic port
ranges specified for communications between the media server and remote agents.
When a media server makes a connection with a remote system, the initial connection
will be initiated to the well known port 10000. The Remote Agent will be listening for
connections on this predefined port. The media server side of this connection will be
bound to an available port. Additional connections from the media server to the Remote
Agent will be initiated on any available port.
Communication between the media server and the Remote Agent will usually require up
to 2 ports on the remote agent side per backup operation. If you plan on supporting
multiple backups and restores occurring simultaneously, you must configure your
firewall to allow a range of ports large enough to support the maximum number of
simultaneous operations desired.
Should a conflict arise, the default port of 10000 can be changed to another port number
by modifying the %systemroot%\System32\drivers\etc\services file, and changing the
NDMP port to an alternate port number. For example, if you installed Windows 2000 to
its default location, from your Windows Explorer, select
C:\WINNT\System32\drivers\etc\services. Using a text editor, such as Notepad, modify
your NDMP entry, or if necessary, add an NDMP entry with the new port number. This
entry should be formatted as follows:
ndmp 10000/tcp #Network Data Management Protocol
405

Using Backup Exec with firewalls
Note If the default port is changed, it must be changed on the media server and all
remote systems being backed up through the firewall on this port.
When setting up TCP dynamic port ranges, Symantec recommends using a range of 25
allocated ports for the remote computers. The number of dynamic ports used by remote
systems can change based on the number of devices being protected and the number of
tape devices in use. You may need to increase these port ranges to maintain the highest
level of performance. Backup Exec and the firewall need to have the ranges defined (and
port 10000).
Unless you specify a range, Backup Exec uses the full range of dynamic ports available.
When performing remote backups through a firewall, you should select a specific range
on the Network and Firewall defaults dialog box.
Browsing systems through a firewall
Because most firewalls do not allow a remote system to be displayed in the Microsoft
Windows Network tree, you may need to take additional steps to select these remote
systems in the Backup Exec administration console.
To browse systems through a firewall
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Network and Security.
3. Verify that a dynamic range of ports has been set for the media server and remote
agent and that the firewall is configured to pass these port ranges and the 10,000
port (which is used for the initial connection from the media server to the Remote
Agent).
Port 6101 must be open to browse Windows systems in the backup selections tree.
4. Click OK.
406 Administrator’s Guide

Encryption keys
Chapter 9, Customizing backup options
Encryption keys
Backup Exec provides you with the ability to encrypt data with encryption keys. When
you encrypt the data on a tape, you protect it from unauthorized access. Backup Exec can
encrypt data at a computer that uses the Remote Agent, and then transfer the encrypted
data to the media server. Backup Exec then writes the encrypted data on a set-by-set
basis to tape or to a backup-to-disk folder. When you install Backup Exec, the installation
program installs the necessary encryption software on the media server and on remote
computers that use the Remote Agent.
Backup Exec encrypts the following types of data:
■ User data, such as files and Microsoft Exchange databases.
■ Metadata, such as file names, attributes, and operating system information.
■ On-tape catalog file and directory information,
Backup Exec does not encrypt Backup Exec metadata or on-disk catalog file and directory
information.
You can set a default encryption key to use for all backup jobs, templates, and duplicate
backup set jobs. However, you can override the default key for a specific job. You can also
use encryption in policies when you create Backup templates or Duplicate Backup Set
templates. When you create a Duplicate Backup Set template or a duplicate backup sets
job, backup sets that are already encrypted are not re-encrypted. However, you can
encrypt any unencrypted backup sets.
If you use encryption in a synthetic backup policy, all the templates in the policy must
use the same encryption key. You should not change the key after you create the policy.
For the synthetic backup template, Backup Exec automatically uses the encryption key
that you select for the other templates in the policy.
When you select encrypted data for restore, Backup Exec verifies that encryption keys
for the data are available in the database. If any of the keys are not available, Backup
Exec prompts you to recreate the missing keys. If you delete the key after you schedule
the job to run, the job fails.
If Backup Exec cannot locate an encryption key while a catalog job is processing, Backup
Exec sends an alert. You can then recreate the missing encryption key if you know the
pass phrase.
If you use encryption keys with the Intelligent Disaster Recovery option, special
considerations apply.
See “About encrypted backup sets and the Disaster Recovery Wizard” on page 1525.
407

Encryption keys
Encryption types
Backup Exec supports two types of encryption: 128-bit Advanced Encryption Standard
(AES) and 256-bit AES. The 256-bit AES encryption provides a stronger level of security
because the key is longer for 256-bit AES than for 128-bit AES. However, 128-bit AES
encryption enables backup jobs to process more quickly.
Restricted keys and common keys
Backup Exec has two types of encryption keys:
Types of encryption keys
Key type Description
Common Anyone can use the key to encrypt data during a backup job and to restore
encrypted data.
Restricted Anyone can use the key to encrypt data during a backup job. If a user other
than the key owner tries to restore data that was encrypted with a
restricted key, Backup Exec prompts the user for the key’s pass phrase. If
the user cannot supply the correct pass phrase for the key, the user cannot
restore the data.
Pass phrases
Encryption keys require a pass phrase, which is similar to a password. Pass phrases are
usually longer than passwords and are comprised of several words or groups of text. A
good pass phrase is between eight and 128 characters. The minimum number of
characters for 128-bit AES encryption is eight. The minimum number of characters for
256-bit AES encryption is 16. Symantec recommends that you use more than the
minimum number of characters.
Also, a good pass phrase contains a combination of upper and lower case numbers,
letters, and special characters. You should avoid using literary quotations in pass
phrases.
A pass phrase can include only printable ASCII characters, which are characters 32
through 126. ASCII character 32 is the space character, which is entered using the space
bar on the keyboard. ASCII characters 33 through 126 include the following:
!"#$%&'()*+,-./0123456789:;?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcde
fghijklmnopqrstuvwxyz{|}~
408 Administrator’s Guide

Related Topics:
“Creating an encryption key” on page 410
“Selecting an encryption key for a backup job” on page 411
“Setting a default encryption key” on page 411
“Removing the default status from an encryption key” on page 412
“Deleting an encryption key” on page 413
About using encryption with compression
Chapter 9, Customizing backup options
Encryption keys
You can use software compression with encryption for a backup job. First, Backup Exec
compresses the files, and then encrypts them. However, backup jobs take longer to
complete when you use both encryption and software compression.
Symantec recommends that you avoid using hardware compression with encryption.
Hardware compression is performed after encryption. Data becomes randomized during
the encryption process. Compression does not work properly on data that is randomized.
About encryption key management
When a user creates an encryption key, Backup Exec marks that key with an identifier
based on the logged-on user’s security identifier. The person who creates the key
becomes the owner of the key.
Backup Exec stores the keys in the Backup Exec database. However, Backup Exec does not
store the pass phrases for the keys. The owner of each key is responsible for
remembering the pass phrase for the key. To protect your keys, Symantec recommends
the following:
■ Maintain a written log of the pass phrases. Keep the log in a safe place in a separate
physical location from the encrypted backup sets.
■ Back up the Backup Exec database. The database keeps a record of the keys.
Caution If you do not have a backup of the Backup Exec database and do not remember
your pass phrases, you cannot restore data from the encrypted media. In
addition, Symantec cannot restore encrypted data in this situation.
A key that is created on a media server is specific to that media server. You cannot move
keys between media servers. However, you can create new keys on a different media
server by using existing pass phrases. A pass phrase always generates the same key. In
addition, if you delete a key accidentally, you can recreate it by using the pass phrase.
409

Encryption keys
If a Backup Exec database becomes corrupted on a media server and is replaced by a new
database, you must manually recreate all of the encryption keys that were stored on the
original database. If you move a database from one media server to another media server,
the encryption keys remain intact as long as the new media server:
■ Has the same user accounts as the original media server.
■ Is in the same domain as the original media server.
Creating an encryption key
To create an encryption key
1. On the Tools menu, click Encryption Keys.
2. Click New.
3. Complete the appropriate options as follows:
Key name Type a unique name for this key. The name can include up to 256
characters.
Encryption type Select the encryption type to use for this key. Your choices are
128-bit AES or 256-bit AES. The default type is 256-bit AES.
The 256-bit AES encryption provides a stronger level of security
than 128-bit AES encryption. However, backup jobs may process
more slowly with 256-bit AES encryption than with 128-bit AES
encryption.
Pass phrase Type a pass phrase for this key. For 128-bit AES encryption, the
pass phrase must be at least eight characters. For 256-bit AES
encryption, the pass phrase must be at least 16 characters.
Symantec recommends that you use more than the minimum
number of characters.
You can use only printable ASCII characters. For more
information, see “Pass phrases” on page 408.
Confirm pass phrase Retype the pass phrase.
Common Select this option to make this a common key. If a key is common,
anyone can use the key to back up and restore data.
410 Administrator’s Guide

4. Click OK.
Selecting an encryption key for a backup job
To select an encryption key for a backup job
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. Select the data that you want to back up.
4. On the Properties pane, under Settings, click Network and Security.
5. In the Encryption key field, do one of the following:
6. Process the backup job as normal.
Related Topics:
“Duplicating backed up data” on page 381
“Adding a duplicate backup template to a policy” on page 436
“Creating a synthetic backup by adding templates to a policy” on page 874
Chapter 9, Customizing backup options
Encryption keys
Restricted Select this option to make this a restricted key. If a key is
restricted, anyone can use the key to back up data, but only the
key owner or a user who knows the pass phrase can use the key to
restore the encrypted data.
To use an existing key Select the key from the list.
To create a new key Click the arrow, and then click .
Setting a default encryption key
You can set a default encryption key to use for backup jobs, templates, and duplicate
backup set jobs. You can override the default key for an individual job.
411

Encryption keys
To set a default encryption key
1. On the Tools menu, click Encryption Keys.
2. Select a key from the list.
3. Click Set As Default.
4. Click OK.
Removing the default status from an encryption key
When you remove the default status from an encryption key, you must manually select
an encryption key for new backup jobs, templates, and duplicate backup set jobs.
However, default encryption keys remain in place for existing jobs that you configured to
use encryption.
To remove the default status from an encryption key
1. On the Tools menu, click Encryption Keys.
2. Select the default key from the list.
3. Click Clear Default.
4. Click OK.
Replacing an encryption key
You can replace one encryption key with another for all backup jobs, templates, and
duplicate backup set jobs.
To replace an encryption key
1. On the Tools menu, click Encryption Keys.
2. Select the key that you want to replace.
3. Click Replace.
412 Administrator’s Guide

Chapter 9, Customizing backup options
Encryption keys
4. In the Select an encryption key to replace “key name” box, do one of the following:
To use an existing key Select the key from the list.
To create a new key Click the arrow, and then click .
5. Click OK.
Deleting an encryption key
You should be cautious when you delete encryption keys. When you delete an encryption
key, you cannot restore the backup sets that you encrypted with that key unless you
create a new key that uses the same encryption key and pass phrase as the original key.
You can delete encryption keys if:
■ The encrypted data on the tape has expired or if the tape is retired.
■ The encryption key is not the default key.
■ The encryption key is not being used in a job or a template. If the key is being used,
you must select a new key for the job or template.
■ The encryption key is not being used in a selection list for restore jobs and for verify
duplicate backup set jobs. If you delete a key that is being used in one of the listed job
types, the selection list can no longer be used.
If you delete an encryption key that is being used in a scheduled restore job, you cannot
replace the key. Therefore, any scheduled restore job in which you delete an encryption
key fails.
To delete an encryption key
1. On the Tools menu, click Encryption Keys.
2. Select the key that you want to delete.
3. Click Delete.
4. Click Yes.
5. If the key is used in a job or template, do the following:
■ In the Select an encryption key to replace “key name” box, select the new key for
the jobs or templates listed.
■ Click OK.
413

Encryption keys
Related Topics:
“Replacing an encryption key” on page 412
About restoring encrypted data
Encrypted backup sets are identified in the restore selection list by an icon with a lock on
it. When you select encrypted data to restore, Backup Exec automatically validates the
encryption key for the data. If the encryption key that was used to back up the data is
still in the Backup Exec database, then Backup Exec selects that encryption key
automatically. However, if the encryption key cannot be located, Backup Exec prompts
you to provide the pass phrase for the encryption key that was used to back up the data.
If you enter the correct pass phrase, Backup Exec recreates the key.
When restricted encryption keys are used to back up data, any users other than the key
owner must enter the pass phrase to restore the data and to edit a restore job.
About cataloging media that contains encrypted backup sets
When you catalog media that contains encrypted backup sets, Backup Exec attempts to
find valid encryption keys for the sets in the Backup Exec database. If Backup Exec does
not find a valid key, it issues an alert that instructs you to create one. After you create a
valid key, you can respond to the alert to retry cataloging the encrypted set.
Alternatively, you can skip the encrypted set and continue to catalog the rest of the
media, or cancel the catalog job.
414 Administrator’s Guide

Policies and templates
Chapter
10
Policies provide a method for managing backup jobs and strategies. Policies contain job
templates, which are job attributes that define how and when Backup Exec processes a
job. Templates specify the devices, settings, and schedule for a job, but do not include
the selections to be backed up. To create jobs, combine a policy with a selection list.
Policies are useful in a number of situations. For example, you can set up policies for:
■ Rotating media. If you use the policy wizard to create a policy, you can use the
Monthly full backup with weekly and daily backups option to create a
Grandfather, Father, Son media rotation scheme.
■ Setting relationships between jobs. When a policy contains more than one template,
you can use template rules to establish relationships between the templates. For
example, you can set a template rule so that when one backup job completes, Backup
Exec automatically starts another backup job.
■ Creating duplicate copies of backup sets. Set up a policy that contains a backup
template and a duplicate backup set template. The duplicate backup set template
initiates a job that copies the backup set created by the backup job.
■ Exporting media. Set up a policy that contains an export media template and at least
one backup template. Then, set up a template rule that schedules a media export job
after the backup completes. You can also select a vault to move the media to after it
is exported from the robotic library slots.
■ Creating a synthetic backup. If you have purchased and installed the Advanced
Disk-based Backup Option (ADBO), then you can set up a policy that contains the
necessary job templates for creating a synthetic backup.
■ Enabling true image restore of backup sets. If you have purchased and installed the
Advanced Disk-based Backup Option (ADBO), then you can set up a policy that
contains the necessary job templates for enabling true image restore of backup sets.
415

Creating a new policy
After you combine a selection list with a policy, Backup Exec automatically creates a job
for each template in the policy. For example, if a policy contains three templates, Backup
Exec will create one job for each template, for a total of three jobs. Polices are reusable,
so you can create a single policy and combine it with several different selection lists.
Related Topics:
“Policy Jobs Summary Report” on page 639
“Backup Set Details by Resource Report” on page 615
“Policy Protected Resources” on page 641
“About the synthetic backup feature” on page 866
“About true image restore” on page 880
“Resource Backup Policy Performance Report” on page 644
Creating a new policy
Creating a new policy involves choosing a name and description for the policy, adding
templates to the policy, and setting up relationships between templates (if necessary).
After you set up all of the templates for a policy, you should combine the policy with a
selection list to create jobs.
You can set up the policy manually or use the policy wizard. The policy wizard guides
you through the creation of a policy using one of the following backup strategies:
■ Daily full backups
■ Weekly full backup with daily backups
■ Monthly full backup with weekly and daily backups (this creates the Grandfather,
Father, Son media rotation scheme)
If you have installed the Advanced Disk-based Option, the wizard can also help you
create synthetic backups and enable true image restore of backups by collecting
additional catalog information. For more information, see “Symantec Backup Exec
Advanced Disk-based Backup Option” on page 865.
To create a new policy manually
1. On the navigation bar, click Job Setup.
2. In the task pane, under Policy Tasks, click New policy.
416 Administrator’s Guide

3. In the New Policy dialog box, enter the following information:
4. Do one of the following:
5. Click OK to start editing the template that you selected.
To create a policy using the Policy Wizard
1. On the navigation bar, click Job Setup.
2. In the task pane, under Policy Tasks, click New policy using wizard.
3. Follow the instructions in the wizard to create a policy.
Related Topics:
“Adding a backup template to a policy” on page 421.
“Adding an export media template to a policy” on page 424.
“Adding a duplicate backup template to a policy” on page 436.
“Importing a template into a policy” on page 426
“About the synthetic backup feature” on page 866
“About true image restore” on page 880
Chapter 10, Policies and templates
Creating a new policy
Policy name Type a unique name for this policy. You can use a name that
describes the type of backup or the resources that this policy will
protect, such as "Monthly full backup policy" or "My documents
daily backup". The policy name that you enter here displays in the
Policies list on the Job Setup view.
Policy description Type a description of this policy.
To create a new template:
To import an existing
template:
◆ Click New Template.
◆ Select the type of template that you want to add.
◆ Click Import Template.
◆ Select the templates that you want to import.
417

Creating a new policy
Editing a policy
To edit a policy
❖ Do one of the following:
To edit a policy that is
not associated with a job:
To edit a policy that is
associated with a
scheduled job:
Related Topics:
“Editing a template in a policy” on page 427
Deleting a policy
If you no longer need a policy, you can delete it. Before you delete a policy, be certain
that you no longer need the jobs that are associated with the policy. Before you can
delete a policy, you must remove the association between the selection lists and the
policy. When you remove the association between selection lists and policies, any active
jobs that were associated with the policy will complete and then will be deleted.
To delete a policy
1. On the navigation bar, click Job Setup.
2. Select the policy that you want to delete.
3. Do one of the following:
If selection lists are
associated with the
policy:
◆ On the navigation bar, click Job Setup.
◆ Double-click the policy.
◆ On the navigation bar, click Job Setup or Job Monitor.
◆ Right-click the job.
◆ Click Edit Policy.
◆ In the task pane, under Policy Tasks, click Delete jobs created
by policy.
◆ Check the check boxes next to the selection list names to
delete all of the jobs created by this policy. Click Yes when
prompted to continue.
◆ Select the policy again that you want to delete, and then in the
task pane, under General Tasks, click Delete.
◆ When prompted to continue, click Yes.
418 Administrator’s Guide

If no selection lists are
associated with the
policy:
4. Click Yes to confirm that you want to delete this policy.
Using an example policy
Chapter 10, Policies and templates
Creating a new policy
Backup Exec provides example policies that contain standard settings for the following
policy types: media rotation, duplicate backup, and synthetic backup. You can copy the
example policies and then customize them to meet your needs.
To use an example policy
1. On the navigation bar, click Job Setup.
2. In the Policies pane, right-click the example policy you want to use, and then click
Copy.
Note The Synthetic Backup example policy displays only if you have purchased and
installed the Advanced Disk-based Backup Option. For more information about
the Synthetic Backup example policy, see “Creating a synthetic backup by copying
the example policy” on page 873.
3. Do one of the following:
To copy the example
policy to this media
server:
To copy the example
policy to other media
servers:
Under General Tasks on the task pane, click Delete.
Click Copy to this media server.
◆ Click Copy to other media servers.
◆ Select the media server you want to copy to.
◆ If the media server doesn’t appear on the list, click Add, and
then enter the media server name.
4. To overwrite an existing policy with the same name, check the Overwrite policies
with identical names that already exist on the destination media server check box.
See “Copying jobs, selection lists, and policies” on page 440.
Backup Exec creates a new policy named "Copy of " and places it in
the list of policies on the Job Setup view of the media servers that you copied it to.
419

Using templates in policies
5. Customize the policy and templates as necessary.
For example, you may want to give the policy a new name and description, and
change when the templates are scheduled to run. For details on setting options in
templates, see “Adding a backup template to a policy” on page 421.
6. When finished, click OK.
7. Create jobs using this policy and a selection list. For more information, see “Creating
jobs using policies” on page 432.
Re-creating example policies
You can re-create example policies. If an example policy with the default example policy
name already exists when you select the Re-create Example Policies option, Backup
Exec creates another example policy and adds an incremented number to the example
policy name. For example, if the Example: Media Rotation 0002 policy exists, Backup
Exec creates another example policy called Example: Media Rotation 0003.
To re-create example policies
❖ On the Tools menu, select Re-create Example Policies.
Using templates in policies
Templates are the building blocks of policies. They contain all the settings for a job,
except the resources to be backed up. Each policy must contain at least one template.
Backup Exec includes four types of templates:
■ Backup. Use this template to create backup jobs, such as full, incremental, and
differential. For more information, see “Adding a backup template to a policy” on
page 421.
■ Duplicate backup set. With this type of template, you can use a staging strategy to
create duplicate copies of backup sets. It allows multiple levels of data duplication,
either within the backup window or outside of the backup window. For more
information, see “About duplicate backup set templates” on page 435.
■ Export media. Use this template to set up an export media utility job that runs
automatically after a backup or duplicate backup set job completes. The export
media job either moves media from robotic library slots into a portal or displays an
alert reminding you to remove the media from a slot. You can also select a vault to
move the media to after it is exported from the robotic library slots. For more
information, see “Adding an export media template to a policy” on page 424.
420 Administrator’s Guide

Chapter 10, Policies and templates
Using templates in policies
■ Synthetic backup. This template is available only with the Backup Exec Advanced
Disk-based Backup Option. For more information, see “Symantec Backup Exec
Advanced Disk-based Backup Option” on page 865.
Note For information about creating a policy for true image restore, see “Creating a
policy for true image restore” on page 883.
You can copy backup templates from one policy to another using the Import Template
option. You can save time by importing templates that contain all or most of the settings
you want to use. After you import templates, you can give the template a unique name
and change any of the settings.
Related Topics:
“Exporting expired media from a robotic library” on page 255
“Importing a template into a policy” on page 426
Migrating templates from previous versions of Backup Exec
If you set up templates in previous Backup Exec versions, you are already familiar with
the concept of templates. When you upgrade to Backup Exec 11d, each template that
existed in your previous version of Backup Exec is automatically migrated into a
separate policy that contains a single template. For example, if you had 10 templates in
Backup Exec 9.1, you will have 10 policies in Backup Exec 11d. Each policy will have one
template.
Adding a backup template to a policy
Each policy you create must include at least one template. The templates include the
information that Backup Exec needs to run jobs. Creating a backup template is similar to
creating a backup job. You select the device and media that you want to use, the settings
for the job, and the schedule for the job. However, in templates you do not select
resources to back up. After a policy is complete, create a job by combining the policy
with the selection list that includes the resources you want to back up.
To add a backup template to a policy
1. Set up a new policy using the steps in “Creating a new policy” on page 416.
2. On the New Policy dialog box, click New Template.
3. On the Template Selection dialog box, select Backup Template, and then click OK.
421

Using templates in policies
4. On the Properties pane, under Destination, click Device and Media. Complete the
Device and Media options. For more information about completing device and media
options, see “Device and media options for backup jobs and templates” on page 354.
5. On the Properties pane, under Settings, click General. Complete the General
options for this template. For more information about General options, see “General
options for backup jobs and templates” on page 357.
If the Advanced Disk-based Backup Option (ADBO) is installed, and you want to
create a policy for synthetic backup or true image restore, you must select the
option Collect additional information for synthetic backup and for true image
restore. See “Creating a synthetic backup by adding templates to a policy” on
page 874 or “Creating a policy for true image restore” on page 883.
6. On the Properties pane, under Settings, click Advanced. Complete the Advanced
options for this template. For more information about Advanced options, see
“Advanced options for backup jobs” on page 362.
7. On the Properties pane, under Settings, click Pre/Post Commands. Complete the
Pre/Post Command options. For more information about pre/post commands, see
“Pre/post commands for backup or restore jobs” on page 365.
8. On the Properties pane, under Settings, click Network and Security. For more
information about setting and managing encryption keys, see “Encryption keys” on
page 407.
If the Central Admin Server Option (CASO) is installed, an option displays to allow
managed media servers to use any network interface to access remote agents. For
more information, see “Enabling managed media servers to use any available
network interface card” on page 814.
9. On the Properties pane, under Settings, select additional options for this job as
needed:
■ If you are using the Advanced Open File Option, select Advanced Open File and
complete the options as described in “Setting defaults for the Advanced Open
File Option for backup jobs” on page 850.
■ If you want to use offhost backup, select Advanced Disk-based Backup and
complete the options as described in “About offhost backup” on page 887.
■ If you are backing up other platform types or database agents, such as NetWare,
Exchange, SQL, or SharePoint, select the platform type or database agent. Refer
to the chapter for that item for instructions on completing the options.
■ If you want Backup Exec to notify someone when the backup job completes,
select Notification. For more information, see “Assigning notification recipients
for completed jobs” on page 565.
422 Administrator’s Guide

Chapter 10, Policies and templates
Using templates in policies
■ If you want to prevent certain files or file types from being included in the
backup, select Exclusions. For more information about file exclusion, see
“Including or excluding files for backup” on page 325.
10. Set the schedule for the template. See “Setting the schedule for a template” on
page 423.
11. Click OK.
The template is complete. You can add another template or combine the policy with
a selection list. For more information, see “Creating jobs using policies” on page 432.
Setting the schedule for a template
Types of schedules for a template include:
■ Run now and run according to rules for this template. If you select this option, the
job will run as soon as a selection list is combined with the policy in which the
template is contained. If the template is also linked to another template via a
template rule, the job will also run according to the rule selected for the template.
■ Run according to schedule and run according to rules for this template. If you
select this option, you can set a date when the template will go into effect, a time
window, and the days on which the job will run. If the template is also linked to
another template via a template rule, the job will also run according to the rule
selected for the template. This is the default setting for templates.
■ Run only according to rules for this template. If you select this option, the template
must be part of a template rule. The job created from the template will run based on
the rule set for the template.
You can set an availability window and a priority on selection lists. If you set a schedule
for a template that is not within the availability window for the selection list, Backup
Exec displays the job status as Invalid Time Window.
423

Using templates in policies
To set the schedule for a template
1. On the Properties pane, under Frequency, select Schedule.
2. Select one of the following options:
Run now and run
according to rules for this
template
Run according to
schedule and run
according to rules for this
template
Run only according to
rules for this template
Select this option to run the job immediately after a selection list
is combined with the policy in which this template is contained. If
the template is part of a template rule, the job will also run
according to the template rule.
Note If you select this option to change the schedule for an
existing template in a policy, the existing associated jobs
are not run immediately. This prevents you from
inadvertently performing a run now operation on all jobs
that were created when the policy was combined with
selection lists. The jobs run only according to the rules for
the template.
Select this option to configure a schedule for a recurring job, and
then click Edit Schedule Details to set the schedule. For more
information, see “Scheduling jobs” on page 368.
If the template is part of a template rule, the job will also run
according to the template rule.
Select this option to set the job to run based on a template rule.
For example, with the After completes, start
template rule, will run whenever
completes.
Submit job on hold Select this option to submit the jobs that are created using this
template with an on-hold status. You should select this option if
you want to submit the job, but do not want it to run until you
change the job’s hold status.
Adding an export media template to a policy
You can use the export media template to set up an export media utility job that runs
automatically after a backup or duplicate backup set job completes. If the targeted
device is a library with a portal, the export media job moves the media from its slot in
the portal and generates an alert reminding you to remove the media from the portal.
You can select a vault to move the media to after it is exported from the robotic library
slots. If the device is a library that does not have a portal, the export media job will
generate an alert reminding you to remove the media from the indicated slot.
424 Administrator’s Guide

Chapter 10, Policies and templates
Using templates in policies
The export media template must be part of a multi-template policy. There must be a
source template that produces media and initiates the export job. For example, if you
want to export media after your monthly full backup completes, set up a policy with a
backup template for the monthly full backup job and set up an export template to run
after the monthly full job completes. If a job requires multiple pieces of media, the
export media job starts after the source backup job completes, not after each piece of
media is filled.
When you create an export media template, Backup Exec automatically adds the After
completes, start to export media template rule to the
policy. Backup Exec replaces with the name of the template that you
select as the source for the export media template, such as a backup template. Backup
Exec replaces with the export media template.
To add an export media template to a policy
1. Set up a new policy using the steps in “Creating a new policy” on page 416.
2. Set up a backup template, which will be the media-producing template that is the
source for the export job.
3. On the New Policy dialog box, click New Template.
4. On the Template Selection dialog box, select Export Media Template, and then click
OK.
Note The Export Media template displays only if the policy contains a backup template.
5. Select the media-producing template to use as the source for the export job.
For example, if you want to export media after the monthly full backup completes,
select the template for monthly full backups as the source media set template.
6. On the Properties pane, under Settings, click General. Type a name for this export
media template.
7. To move the media to a media vault after a successful export, on the Properties
pane, under Settings, click Options, and select a media vault. For more information,
see “Scanning bar code labels to move media” on page 291.
8. If you want to set up notification for this job, on the Properties pane, under
Settings, click Notification. For more information, see “Assigning notification
recipients for completed jobs” on page 565.
425

Using templates in policies
Note The export media job must run according to the template rule, so you do not need
to set any schedule options for this job.
9. Click OK.
Backup Exec adds the template rule called After completes, start
to export media.
The template is complete. You can add another template or combine the policy with
a selection list. For more information, see “Creating jobs using policies” on page 432.
Importing a template into a policy
Importing templates makes template creation easier. If an existing template contains
many of the settings that you want to use again, you can import the existing template
into a policy instead of manually creating a new template and duplicating the settings.
Backup Exec does not import any template rules that are associated with the imported
template.
After you import a template into a policy, you can change the template settings as
needed.
To import a template into a policy
1. On the navigation bar, click Job Setup.
2. If you want to import a policy into an existing policy, in the Policies section,
double-click the policy.
If you want to create a new policy and then import an existing template into it, in the
task pane, under Policy Tasks, click New policy. Enter a policy name and
description.
3. Click Import Template.
4. Select the templates you want to import.
5. Click OK.
Backup Exec copies the templates into the policy and provides the default name of
, where indicates that this is the second copy
of this template, or the third copy, etc. To change the template name or other
properties, select it from the list and click Edit Template.
426 Administrator’s Guide

Editing a template in a policy
To edit a template in a policy
1. On the navigation bar, click Job Setup.
Chapter 10, Policies and templates
Using templates in policies
2. In the Policies section, double-click the policy that contains the template you want
to edit.
3. Select the template from the list that displays in the Job Templates area.
4. Click Edit Template.
5. Change the template properties as needed.
Deleting a template from a policy
When you delete a template from a policy, it is permanently removed from Backup Exec.
In addition, Backup Exec deletes any scheduled jobs that were created from the policy
that contained the deleted template. Any active jobs that were created from the policy
will complete and then will be deleted.
Do not delete a template from a policy unless you are certain that you no longer need the
jobs associated with the template. If a policy contains only one template, delete the
policy instead of the template.
To delete a template from a policy
1. On the navigation bar, click Job Setup.
2. In the Policies section, double-click the policy.
3. Select the template from the list that displays in the Job templates area.
4. Click Delete Template.
5. Click Yes to confirm that you want to delete this template. If you selected multiple
templates, click Yes to All.
The template is removed from the policy.
Related Topics:
“Deleting a policy” on page 418
427

Setting template rules
Setting template rules
Template rules enable you to set up relationships between templates in a policy. For
example, you can use template rules to determine which job should be processed first if
a start time conflict exists, or to determine which job should start when another job
starts, ends, or fails.
When you set a template rule, you must select the rule you want to use and the
templates to which the rule will be applied. Backup Exec displays different rules
depending on the types of templates that exist in the policy. For example, if a policy
contains a duplicate backup template, Backup Exec displays rules for duplicating backup
sets. If Backup Exec automatically adds a template rule to a template, you should not
delete that rule.
The following template rules are available:
Template Rules
Rule Description
Rules to handle conflicting job start times
If start times conflict,
supersedes .
If start times conflict,
will start
and upon completion,
starts .
Rules to link jobs together
After
starts, also start
.
If two templates in the same policy have the same start time,
will run first, and will run according to
the schedule set for it, after the job completes. For
example, you set a weekly backup to run every Saturday at 5:00 p.m.
and a daily backup to run every day at 5:00 p.m. On Saturday, both the
weekly backup and the daily backup are scheduled to run at 5:00 p.m.
If you set the weekly backup as and the daily backup as
, the weekly backup will run at 5:00 p.m. on Saturday.
The daily backup will not run on Saturday, but it will run on Sunday at
5:00 p.m., according to its schedule.
If two templates in the same policy have the same start time,
will start first. After completes,
will start automatically.
With this rule, you can run two jobs simultaneously.
428 Administrator’s Guide

Template Rules
Rule Description
After
completes, start
.
If
successfully completes,
start .
If fails,
start .
Rules to limit when jobs run
must
complete at least once
before any other
templates will be
allowed to start.
Run only
once.
Rules to duplicate backup sets
Duplicate all backup sets
that were created by
using
as
scheduled.
Chapter 10, Policies and templates
Setting template rules
Use this rule if you want Backup Exec to start a job automatically after
a selected job completes. The second job will start regardless of
whether the first job completes successfully. For example, if the first
job fails, the second job will run.
Use this rule if you want Backup Exec to automatically start a job after
a selected job successfully completes. The second job will not start if
the first job fails.
Use this rule if you want Backup Exec to automatically start a new job
if a selected job fails.
This rule is used when baseline backups are needed, such as with
synthetic backup templates. If you set up a baseline backup job, it
must complete before any other synthetic backups can begin. If you
set the baseline backup template as the in this rule, you
can ensure that no other synthetic backup jobs will run until the
baseline backup completes.
This rule applies to synthetic backups. If you set up a baseline backup,
it needs to run only once.
This rule applies to a duplicate backup template. It displays only if the
policy contains a duplicate backup template and the template has a
schedule associated with it. Backup Exec automatically adds this rule
to the policy if you set the schedule for the template to Run now and
run according to rules for this template or Run according to
schedule and run according to rules for this template. With this rule,
you can set up the data duplication job to run outside of the backup
window.
429

Setting template rules
Template Rules
Rule Description
After
completes, start
to
duplicate the backup set.
Rules to export media
After
completes, start
to export
media.
To set a template rule
1. On the navigation bar, click Job Setup.
2. If you want to set template rules for existing templates in an existing policy, in the
Policies section, double-click the policy.
If you want to create a new policy, in the task pane, under Policy Tasks, click New
policy. Enter a policy name and description. Then create a new template.
3. On the Policy Properties screen, click New Rule.
4. Complete the fields that display as follows:
This rule applies to a duplicate backup template and displays only if
the policy contains a duplicate backup template. After you create a
duplicate backup template, Backup Exec automatically adds this rule
to the policy if you set the schedule for the template to Run only
according to rules for this template. Backup Exec replaces with the template that you selected as the source for the duplicate
backup template, and replaces with the duplicate
template you created. With this rule, it is likely that the duplication
job will run during the backup window. If you do not want to run the
duplication during the backup window, use the Duplicate all backup
sets that were created by using as
scheduled rule.
This rule applies to export media templates and displays only if the
policy contains an export media template. After you create an export
media template, Backup Exec automatically adds this rule to the
policy. Backup Exec replaces with the template that you
selected as the source for the export media template, and replaces
with the export media template you created.
Template rule Select the template rule that you want to apply.
430 Administrator’s Guide

Chapter 10, Policies and templates
Setting template rules
Template A Select the template that you want to insert into the
slot in the template rule you selected. Template A is usually the
trigger for template B. For example, in the template rule After
completes, start , template A must
complete before Backup Exec will start template B.
Template B Select the template that you want to insert into the
slot in the template rule you selected. Some rules do not require
more than one template. If another template is not required for a
template rule, you cannot select a template from this option.
5. Click OK.
Changing template rules
To change a template rule
1. On the navigation bar, click Job Setup.
2. In the Policies section, double-click the policy.
3. On the Policy Properties screen, select the rule you want to change and click Edit
Rule.
4. Change the template rule as needed.
5. Click OK.
Deleting template rules
You can delete template rules that you added to templates. You should not delete
template rules that Backup Exec added to a template automatically. For multi-stage
backup templates, at least one template rule must exist. You should not delete template
rules for export media templates.
To delete a template rule
1. On the navigation bar, click Job Setup.
2. In the Policies section, double-click the policy.
431

Creating jobs using policies
3. On the Policy Properties screen, select the rule you want to delete and then click
Delete Rule.
The rule is removed from the policy.
Creating jobs using policies
After you create a policy and set up templates in it, you should combine the policy with a
selection list to create jobs. When a policy is combined with a selection list, Backup Exec
creates jobs based on the settings in the templates. You can combine a policy with
several selection lists, and combine a selection list with several policies. You can create
new jobs by selecting a policy and then selecting the selection lists to combine with it, or
by selecting a selection list and then selecting the policies to combine with it. Backup
Exec creates a job for each template and each selection list. For example, if you combine
a policy that contains three templates with two selection lists, Backup Exec creates six
jobs; three jobs for one selection list and three jobs for the other selection list.
When you create a backup selection list, you can set a time range when the resources in
the list will be available for backup. The time range is called the availability window.
When you combine a selection list with a policy, Backup Exec compares the schedule of
each template in the policy with the availability window for the selection list. If the
template schedules do not fall within the availability window, Backup Exec will not
create jobs for the policy. When setting the schedule for templates, be sure that the
schedule overlaps the availability window for the resources you want to back up with the
templates.
To create new jobs for a policy
1. On the navigation bar, click Job Setup.
2. Select the policy for which you want to create jobs.
3. Under Policy Tasks in the task pane, click New jobs using policy.
4. Select the selection lists for which you want to create jobs, and then click OK.
Backup Exec creates a job for each template in the policy.
To create new jobs for a selection list
1. On the navigation bar, click Job Setup.
2. Select the selection list for which you want to create jobs.
3. Under Selection List Tasks, click New jobs using policy.
432 Administrator’s Guide

4. Select the policies for which you want to create jobs, and then click OK.
Backup Exec creates a job for each template in the policy.
Viewing the policies that protect selection lists
Chapter 10, Policies and templates
Creating jobs using policies
You can view a list of the selection lists that are designated for backup by a selected
policy, or view a list of policies that are designated to back up a selected selection list.
To view a list of selection lists that are designated for backup by a selected policy
1. On the navigation bar, click Job Setup.
2. Under Policies, right-click the policy for which you want to view selection lists
designated for backup.
3. Click View Selection Lists Backed Up By Policy.
To view a list of policies that are designated to back up a selected selection list
1. On the navigation bar, click Job Setup.
2. Under Backup Selection Lists, right-click the selection list for which you want to
view policies.
3. Click View Policies That Back Up Selection List.
Editing the next occurrence of a policy-based job
You can edit the next occurrence of a scheduled policy-based job. Only the next
occurrence of a scheduled job can be edited. After the next occurrence of the job
completes, the job will resume its original settings as created in the policy. Edits made to
the associated policy will overwrite any edits made to the job’s next occurrence.
To edit the next occurrence of a scheduled policy-based job
1. On the navigation bar, click Job Monitor.
2. Click the Job List tab.
3. Right-click the job you want to edit, and then click Edit Next Run.
433

Creating jobs using policies
Deleting a job created from a policy
In order to delete a job that was created from a policy, you must remove the association
between the selection list and the policy. Backup Exec deletes any scheduled jobs that
were created from the policy. Any active jobs that were created from the policy will
complete and then will be deleted
To delete a job created from a policy
1. On the navigation bar, click Job Setup.
2. Select the policy or the selection list from which the job was created.
3. If you selected the policy, under Policy Tasks, click Delete jobs created by policy.
If you selected the selection list, under Selection List Tasks, click Delete jobs
created by policy.
4. Check the check box next to the selection list name, and then click OK.
5. When prompted to continue with the deletion, click Yes.
Backup Exec deletes the jobs that were created from the policy.
Renaming a job created from a policy
When you create a job from a policy, Backup Exec automatically names the job. The job
name is a combination of the selection list name, policy name, and template name. For
example, a job created from a policy might be named Backup Selection List 0001-Policy
001-Backup Template 0001. You can rename jobs that were created from policies to
make them more meaningful to you.
To rename a job that was created from a policy
1. On the navigation bar, click Job Setup.
2. Under Jobs, right-click the policy-created job that you want to rename.
3. Click Rename.
4. Type the new name in the Name field, and then click OK.
434 Administrator’s Guide

About duplicate backup set templates
Chapter 10, Policies and templates
About duplicate backup set templates
The Duplicate Backup Set template enables you to use a multi-stage backup strategy for
backing up data to disk and then copying it to tape. The duplicate backup template does
not replace the existing Duplicate Backup Sets option. Instead, it provides an automated,
alternate method of duplicating backup sets. It allows for multiple levels of data
duplication either within the backup window or outside of the backup window.
Duplicate backups are useful in the following situations:
■ You want to stage your data. For example, you may want to back up data to disk with
a 28 day retention (stage 1), then copy the data to another disk for three months for
longer term storage (stage 2), and then move the data to tape for offsite storage
(stage 3). A policy for this example staging would include a backup template to back
up the data to disk for the 28 days, a duplicate backup set template to copy the data
from the original disk to the second disk, and another duplicate backup set template
to copy the data from the second disk to the tape. Each of these stages may have a
different media set to define the data retention period differently for each stage.
■ You want to reduce your backup window. For example, create a policy that contains
a backup job template that uses the Backup-to-Disk option to back up data to disk
during the backup window. Then create a duplicate template to copy the backed up
data from disk to tape and schedule the duplication job to occur outside the backup
window.
■ You want to create a duplicate set of backup tapes to store offsite. For example,
create a backup template to back up data to either disk or tape. Then create a
duplicate template and either set the duplication job to run immediately after the
first backup job completes or schedule it to run at a specific time.
If you need to restore data from duplicate backups, you can restore from the source
backup or from any of the duplicate backups.
There are two methods to configure duplicate backups:
■ The direct link method. This method requires a policy with one backup template and
one duplicate backup template. The direct link is established by the After
completes, start to duplicate the backup set template
rule, where is the backup template and is the duplicate
template. The template rule provides a direct link between the backup job and the
duplication job. To set up duplicate backups using this method, you must set up a
policy and then:
■ Add a backup template with a recurring schedule.
■ Add a duplicate template and set the Run only according to rules for this
template schedule option.
Backup Exec automatically adds the After completes, start
to duplicate the backup set template rule to the policy.
435

About duplicate backup set templates
■ The incremental duplication method. This method requires at least one backup
template and at least one duplicate template. If a policy contains several templates,
you can use this method to associate one duplicate backup template to several
backup and/or duplicate backup templates. With this method, use the Duplicate all
backup sets that were created by using as scheduled
template rule. To set up duplicate backups using this method, you must set up a
policy and then:
■ Add a backup template with a recurring schedule.
■ Add a duplicate backup template with a recurring schedule.
■ Set up a template rule using the Duplicate all backup sets that were created by
using as scheduled template rule.
Adding a duplicate backup template to a policy
To add a duplicate backup template
1. Set up a new policy using the steps in “Creating a new policy” on page 416.
2. Set up a backup template.
3. On the New Policy dialog box, click New Template.
4. On the Template Selection dialog box, select Duplicate Backup Sets Template, and
then click OK.
5. Select the source template, which is the template that will provide the backup data
to be copied.
6. In the Properties pane, under Destination, select Device and Media. For more
information about the device and media options, see “Device and media options for
backup jobs and templates” on page 354.
Note A duplicate backup set template must use a destination device that can be
accessed by the same media server as the device specified for the original backup
set.
436 Administrator’s Guide

Chapter 10, Policies and templates
About duplicate backup set templates
7. In the Properties pane, under Settings, select General. Complete the appropriate
options as follows:
Template name Type the name for this template.
Backup set description Type a description of the information you are backing up.
Preferred source device Select the device that was used as the destination device for the
original backup job.
8. In the Properties pane, under Settings, select Advanced. Complete the appropriate
options as follows:
Verify after job
completes
This option enables Backup Exec to automatically verify that the
media can be read after the backup completes. This option is
selected by default. Symantec recommends that you verify all
backups.
Compression type Select one of the following:
◆ None. Select this option to copy the data to the media in its
original form. If the data was backed up using software
compression, then it is copied in its software compression
form. Using some form of data compression can help expedite
backups and preserve storage media space.
Hardware data compression should not be used in
environments where devices that support hardware
compression are used interchangeably with devices that do
not have that functionality.
For example, if a drive that does not support hardware
compression is added to a cascaded drive pool that includes
drives supporting the feature, hardware compression is
automatically disabled. You can manually re-enable hardware
compression on the drives that support it, but this results in
media inconsistency. If the drive that supports hardware
compression fails, the compressed media cannot be restored
with the non-compression drive
◆ Hardware [if available, otherwise none]. Select this option to
use hardware data compression (if the storage device supports
it). If the drive does not feature data compression the data is
backed up uncompressed.
9. On the Properties pane, under Settings, click Network and Security.
437

About duplicate backup set templates
For more information about setting and managing encryption keys, see “Encryption
keys” on page 407.
10. If you want to set up notification for this job, on the Properties pane, under Settings,
click Notification. For more information about notifications, see “Assigning
notification recipients for completed jobs” on page 565.
11. Set the schedule for the backup job. See “Setting the schedule for a template” on
page 423.
Note You must set a schedule for the template if you want to use the Use scheduled
to duplicate all backup sets that were created by
template rule.
12. Click OK.
You can add another template to the policy or combine the policy with a selection
list to create jobs.
438 Administrator’s Guide

Administrating Backup
Exec
Chapter
11
Backup Exec includes features that enable you to manage Backup Exec and jobs created
in Backup Exec. You can perform the following operations:
■ Copy jobs, selection lists, and policies to local or remote servers (“Copying jobs,
selection lists, and policies” on page 440)
■ Monitor jobs (“Monitoring jobs” on page 442)
■ Filter jobs (“Filtering jobs” on page 465)
■ View the Backup Exec System Summary (“Viewing the Backup Exec System
Summary” on page 465)
■ Configure error-handling rules (“Error-handling rules” on page 474)
■ Configure thresholds to recover jobs (“Setting thresholds to recover jobs” on
page 480)
439

Copying jobs, selection lists, and policies
Copying jobs, selection lists, and policies
Backup Exec enables you to copy all jobs (including backup, report, utility, and archive
jobs), selection lists, and policies that were created on your media server to the same
media server, or to another media server.
Note To copy jobs, selection lists, or polices to other media servers, the Copy Server
Configurations feature must be installed. For more information, see “About Backup
Exec’s standard features” on page 78.
To copy jobs, selection lists, or policies
1. On the media server’s navigation bar, click Job Setup.
2. Select the job, backup selection list, or policy you want to copy.
3. Under General Tasks in the task list, select Copy.
4. Select the appropriate options as follows:
Copy to this media
server
Copy to other media
servers
Destination media
servers
Overwrite jobs with
identical names that
already exist on the
destination media
server
Overwrite logon
accounts used by this
job that already exist on
the destination server
Select this option if you want to copy to this media server.
Select this option if you want to copy to other media servers.
If you are copying to other servers, select the media server you
want to copy to. If the media server doesn’t appear on the list, click
Add, and then enter the media server name.
Select this option if you want to overwrite an existing job, selection
list, or policy having the same name.
Select this option if you want to overwrite logon accounts for an
existing job having the same name. This option only appears if you
are copying a job to another media server.
Add Click this button if you want to add a media server to the
Destination media servers list.
440 Administrator’s Guide

Chapter 11, Administrating Backup Exec
Copying jobs, selection lists, and policies
Edit Select a media server, and then click this button if you want to edit
information stored for a media server, such as logon account
information.
Remove Select a media server, and then click this button if you want to
remove a media server from the Destination media servers list.
Import List Click this button if you want to import a list of media servers to the
Destination media servers list. The list should include only the
media server name, with one per line.
5. Click OK.
The operation is queued. The default time-out is five minutes; if the transfer cannot be
completed within five minutes, the transfer is terminated and an alert is issued. The
queue checks for copy jobs every 60 seconds, and then sends all the copy jobs that are
queued.
Backup Exec sends an alert with the job success or failure status along with a log file that
allows you to view results. The job log for Copy to Media Server jobs does not display
with the other job logs in the Job History.
To view the job log for a copy to media server job
1. On the navigation bar, click Alerts.
2. Click the Active Alerts or Alert History tab.
3. Click the Source column heading.
4. Locate an alert with “Job” as a Source and “Copy to Media Server job” as a Job Name.
5. Right-click the alert, and then select View Job Log.
6. If a Copy to Media Server alert does not exist, do one of the following:
To enable the alert from
the task pane
To enable the alert from
the Tools menu
◆ In the task pane, under Alert Tasks, click Configure alert
categories.
◆ Enable the Job Failed and Job Success alert categories.
◆ On the Tools menu, click Options.
◆ On the Properties pane, under Settings, click Preferences.
◆ Check Automatically display new alerts.
441

Monitoring jobs
Monitoring jobs
Backup Exec’s Job Monitor enables you to monitor and perform tasks on active,
scheduled, or completed jobs that have been submitted for processing. The Job Monitor
has three views: Job List, Calendar, and System Summary.
The Job List view displays active and scheduled jobs in the Current Jobs pane and
successful, completed with exceptions, failed, and canceled jobs in the Job History pane.
The Calendar view displays scheduled, active, and completed jobs in either a daily,
weekly, or monthly view. The System Summary view provides details of job, alert,
device, and media activity.
Related Topics:
“About managing custom filters” on page 466
“Viewing and changing active jobs” on page 442
“Viewing and changing scheduled jobs” on page 448
“Viewing and changing completed jobs” on page 455
Viewing and changing active jobs
You can view properties and change the status of active and scheduled jobs that are
submitted for processing in the Job List or Calendar view in the Job Monitor. If you select
the Calendar view and the job is not displayed, click the arrow that appears above the
listed jobs to display all the jobs for the selected day.
To view active job properties
1. On the navigation bar, click Job Monitor.
2. Click the Job List or Calendar tab.
3. Select the active job you want to view from the Current Jobs pane or the Job
Calendar, and then under General Tasks in the task pane, click Properties.
Note To view the history of an active job from Job Monitor or Job Setup, right-click the
active job, and then from the shortcut menu, click View History.
The Job Activity dialog box appears. The Job Activity dialog contains two tabs: Job
Activity and Job History. The Job Activity tab only appears for active jobs and
provides detailed information about the job’s current status. The Job History tab
provides a summary of the job as it is being processed. For more information on the
job history, see “Viewing and changing completed jobs” on page 455.
442 Administrator’s Guide

The Job Activity tab provides the following information:
Job name The job name entered during job configuration.
Job type The type of job submitted for processing.
Chapter 11, Administrating Backup Exec
Monitoring jobs
Job log The filename of the job log. The job log cannot be viewed until the
job has completed. The job log is located in Program
Files\Symantec\Backup Exec\Data.
Status The status of the operation. For details, see “Active job statuses” on
page 447.
Current Operation The type of operation currently in progress (Backup, Catalog,
Restore, Verify, etc.).
Created On The type of server on which the job was created, either a central
administration server or a managed media server.
The media server on which this job is running.
This only displays if you have a central administration server or
managed media server.
Server name The media server processing the job.
Device name The name of the storage device processing the job.
Note Only data from the first stream displays for multi-stream
jobs.
Source The media or share being processed. The icon field to the left of the
field name displays either:
◆ A disk drive icon when a backup or archive operation is
running, or
◆ A tape drive icon when a restore or verify operation is running.
Note Only data from the first stream displays for multi-stream
jobs.
Destination Where the data is being written. The icon field to the left of the
field name displays either:
◆ A tape device icon when a backup operation is running, or
◆ A disk drive icon when a restore operation is running.
Note Only data from the first stream displays for multi-stream
jobs.
443

Monitoring jobs
Current directory Name of the current directory being processed. The icon field to
the left of the field displays either:
◆ A folder if the active job is a backup or restore operation, or
◆ No icon, if the active job is not a backup or restore operation,
but a job such as an Erase or Format operation.
Note Only data from the first stream displays for multi-stream
jobs.
Current file Name of the current file being processed. The icon field to the left
of the field name displays either:
◆ A page, if the active job is a backup or restore operation, or
◆ No icon, if the active job is not a backup or restore operation,
but a job such as an Erase or Format operation.
Note Only data from the first stream displays for multi-stream
jobs.
Media server The media server on which this job is running.
If the Central Admin Server Option is installed, this is the managed
media server that the central administration server has delegated
this job to. For more information, see “Managing jobs in CASO” on
page 834.
Delegation status If the Central Admin Server Option is installed, indicates the
current status of a job that is being delegated from the central
administration server to the managed media server. These statuses
include the following, where is replaced with the name of the
managed media server:
◆ Preparing to delegate job to
Statistics
◆ Delegating job to
◆ Job has been delegated to
◆ Job has been received by
◆ Job is actively running on
◆ Job has completed on
◆ Error in delegating job ... re-submitting job to
For more information, see “Managing jobs in CASO” on page 834.
Directories Number of directories processed.
Files Number of files processed.
Skipped files Number of files skipped during the operation.
444 Administrator’s Guide

Corrupt files Number of corrupt files encountered during the operation.
Files in use Number of files in use encountered during the operation.
Job rate Number of megabytes processed per minute.
Bytes Number of bytes processed.
Start time Time the operation started.
Elapsed time Length of time that has elapsed since the operation started.
Chapter 11, Administrating Backup Exec
Monitoring jobs
Percent complete Select percentage of the job that has completed. To display this
option, on the Tools menu, select Options, and then in
Preferences, select Display progress indicators for backup jobs.
Estimated total bytes The total number of bytes for the backup job estimated during a
prescan. To display this option, on the Tools menu, select Options,
and then in Preferences, select Display progress indicators for
backup jobs.
Estimated time
remaining
The estimated time it will take for the job to complete. To display
this option, on the Tools menu, select Options, and then in
Preferences, select Display progress indicators for backup jobs.
Note Indicates that the option to show job estimates is not selected. To
show this option, do the following:
◆ On the Tools menu, click Options.
◆ On the Properties pane, under Settings, click Preferences.
◆ Check Display progress indicators for backup jobs.
4. Click Cancel Job to cancel the processing of the job. If the job is scheduled, it will run
again at the next scheduled time. Canceling a job may take a considerable amount of
time depending on the tape drive selected for the job.
5. Click Print to print the job activity information. You must have a printer attached to
the computer and configured in order to print the report.
6. Click Find to search for a word in the Job Activity log.
445

Monitoring jobs
Cancelling an active job
To cancel an active job
1. On the navigation bar, click Job Monitor.
2. Click the Job List or Calendar tab.
3. Select the active job from the Current Jobs pane or the Job Calendar, and then
under Active Job Tasks in the task pane, click Cancel.
Confirm the cancellation of the job. If the job is scheduled, it will run again at the
next scheduled time.
You can select multiple jobs in the Job List view in the Job Monitor by selecting a
job, and then pressing the or keys while you click other jobs that you
want to select. This allows you to perform tasks such as Cancel on more than one job
at a time, as long as the jobs are of similar type.
If 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 status column.
Placing an active job on hold
To place all scheduled occurrences of an active job on hold
1. On the navigation bar, click Job Monitor.
2. Click the Job List or Calendar tab.
3. Select the active job from the Current Jobs pane or the Job Calendar, and then
under General Tasks in the task pane, click Hold Schedule.
The active job continues and all scheduled occurrences of the job are placed on hold.
To remove the hold on future jobs, click Hold Schedule again.
You can select multiple jobs in the Job List view in the Job Monitor by selecting a
job, and then pressing the or keys while you click other jobs that you
want to select. This allows you to perform Hold Schedule on more than one job at a
time, as long as the state of the jobs are the same.
Related Topics:
“Viewing and changing completed jobs” on page 455
“Scheduled job statuses” on page 449
446 Administrator’s Guide

Active job statuses
Possible statuses for an active job include:
Active job statuses
Item Description
Running The operation is underway.
Chapter 11, Administrating Backup Exec
Monitoring jobs
Queued The job has been initiated, but Backup Exec is actively looking for a
suitable drive or media.
Cancel Pending Backup Exec cannot process the Cancel request immediately. This
status is displayed until the job is actually canceled. The job is then
displayed in Job History with a status of Canceled.
Loading Media The media is being loaded and positioned on the target device.
Pre-processing This status can indicate any or all of the following:
◆ Backup Exec is calculating the amount of data that will be backed
up, if the Display progress indicators for backup jobs option is
enabled. To view this option, from the Tools menu, click Options,
and then under Settings in the task pane, click Preferences.
◆ Backup Exec is waiting for a pre- or post-command to complete.
◆ Backup Exec is retrieving the set maps and is positioning the tape
to the append point location for an append job.
Snapshot processing Backup Exec is processing a snapshot operation.
Device Paused The device that the job was sent to is paused. For more information,
see “Pausing and resuming devices” on page 175.
Server Paused The media server is paused. For more information, see “Pausing and
resuming devices” on page 175.
Stalled The Backup Exec services have become unresponsive. For more
information, see “Setting thresholds to recover jobs” on page 480.
Media Request You must insert media for the job to continue.
Communication Stalled Communications between the managed media server and the central
administration server have not occurred within the configured time
threshold.
For more information, see “Setting communication thresholds and
active job status updates” on page 808.
447

Monitoring jobs
Active job statuses
Item Description
No Communication No communication about jobs is being received at the central
administration server from the managed media server. The
configured time threshold has been reached.
For more information, see “Setting communication thresholds and
active job status updates” on page 808.
Consistency Check Backup Exec is running a consistency check of the databases before
backup.
Updating Catalogs Backup Exec is updating the catalog information.
Schedule, CPS backup job
running
Related Topics:
“Scheduled job statuses” on page 449
“Completed job statuses” on page 461
Viewing and changing scheduled jobs
The Exchange logs are being continuously protected with Continuous
Protection Server (CPS). The status appears if you check the option
Continuously back up transaction logs with Backup Exec Continuous
Protection Server on the backup job properties for Exchange
backups. For more information, see “Continuous protection for
Exchange data” on page 1235.
You can view and modify scheduled jobs submitted for processing using the Job List or
Calendar view in the Job Monitor. The Calendar view also enables you to schedule a new
job.
To view the history of a scheduled job from Job Monitor or Job Setup, right-click the
scheduled job, and then from the shortcut menu, click View History.
The Jobs List view displays a single occurrence of a scheduled job in the Current Jobs
pane. The Calendar view can display a single occurrence or all occurrences of a
scheduled job depending on the View Filters selected. If you select the Calendar view and
the job is not displayed, click the arrow that appears above the listed jobs to display all
the jobs for the selected day.
You can select multiple jobs in the Job List view in the Job Monitor by selecting a job, and
then pressing the or keys while you click other jobs that you want to
select. This allows you to perform tasks such as Test Run or Delete on more than one job
at a time, as long as the jobs are of similar type.
448 Administrator’s Guide

Related Topics:
“Running a scheduled job immediately” on page 451
“Placing a scheduled job or the job queue on hold” on page 452
“Changing the priority for a scheduled job” on page 453
“Running a test job for a scheduled job” on page 454
“Deleting scheduled jobs” on page 454
Scheduled job statuses
Possible statuses for scheduled jobs are listed in the following table:
Scheduled job statuses
Scheduled Job Status Description
Chapter 11, Administrating Backup Exec
Monitoring jobs
Blocked by template rule The scheduled job cannot run because it was created by a policy that
contains a job template with the template rule < Template A> must
complete at least once before any other templates will be allowed to
start. The job designated as in the policy must run
before this scheduled job can run. For more information, see “Setting
template rules” on page 428.
Invalid Schedule The scheduled job will not run because:
◆ An associated record in the database is missing, or
◆ The availability window and the schedule for the selection list
being backed up by this job do not have a time in common. For
more information, see “Setting priority and availability windows
for selection lists” on page 334.
Not in Time Window The job was ready to be sent for processing, but the time window for
the job closed. This probably occurred because appropriate
destination devices were not available during the common time
between the job’s time window and the selection list’s availability
window.
For more information, see “Setting priority and availability windows
for selection lists” on page 334.
On Hold The job has been placed on hold.
Queued A temporary state that displays when Backup Exec is applying an
error-handling rule that is enabled to retry the job. For more
information, see “Custom error-handling rule for recovered jobs” on
page 478.
449

Monitoring jobs
Scheduled job statuses (continued)
Scheduled Job Status Description
Ready The job is ready to run, but cannot for the reason displayed:
◆ Internal error. No devices are available, but the cause is unknown.
◆ Invalid job. The job type in unknown; there may be an internal
error or the database is corrupted.
◆ Invalid target. This is a device type that no longer exists.
◆ Media server not available.
◆ No license for option name. A license must be purchased and
installed on the targeted media server.
◆ No media servers are available.
◆ No media servers available in media server pool.
◆ Specified destination cascaded drive pool is empty.
◆ Specified destination device pool is empty.
◆ Specified destination device is not in media server pool.
◆ Specified destination device not on local media server.
◆ Specified destination device pool on local media server is empty.
◆ The destination device cannot be a cascaded drive pool.
◆ The destination device cannot be a device pool.
◆ The destination device cannot be a media server.
◆ There is another job running in the system that is blocking.
execution of this job. This job will run after the other job
completes.
◆ Invalid input.
◆ Incompatible Resumes.
◆ No server license available.
◆ No multi-server license available.
◆ No Windows 2000 License.
◆ No Windows NT 4.0 server.
◆ No Windows 2000 server.
◆ No NetWare server.
◆ Need local media server.
◆ Local server is not a media server.
◆ No idle devices are available.
◆ No eligible devices within the device pool are available.
◆ Blocked by an active, linked Duplicate Backup Sets job.
◆ No devices within the cascaded drive pool are available.
450 Administrator’s Guide

Scheduled job statuses (continued)
Scheduled Job Status Description
Related Topics:
“Active job statuses” on page 447
“Completed job statuses” on page 461
Running a scheduled job immediately
Chapter 11, Administrating Backup Exec
Monitoring jobs
Scheduled The job is scheduled to run in the future. Scheduled jobs that are
linked to another job, such as a job to duplicate backup sets, will not
display a scheduled job status.
Server Paused The job is ready, but the Backup Exec media server has been paused.
No jobs are dispatched while the media server is paused. See “Pausing
and resuming devices” on page 175.
Superseded by job x The scheduled job cannot run because it was created by a policy that
contains a job template with the template rule If start times conflict,
supersedes . The job will
run according to the schedule set for it, after the job
completes. For more information, see “Setting template rules” on
page 428.
To Be Scheduled A state the scheduled job transitions through as it is being sent for
processing.
You can run a scheduled job immediately and the job will also run on the next scheduled
occurrence.
To run a scheduled job immediately
1. On the navigation bar, click Job Monitor.
2. Click the Job List or Calendar tab.
3. Select the scheduled job from the Current Jobs pane or the Job Calendar, and then
under Scheduled Job Tasks in the task pane, click Run now.
The scheduled job is submitted to the job queue for processing.
Related Topics:
“Changing the priority for a scheduled job” on page 453
451

Monitoring jobs
“Running a test job for a scheduled job” on page 454
“Deleting scheduled jobs” on page 454
Placing a scheduled job or the job queue on hold
You can place a scheduled job on hold to prevent the job from running. You can also
place the entire job queue on hold to make changes to your environment. Jobs do not
run until you change the hold status.
To place a scheduled job on hold
1. On the navigation bar, click Job Monitor.
2. Click the Job List or Calendar tab.
3. From the Current Jobs pane or the Job Calendar, select the scheduled job.
4. In the task pane, under General Tasks, check Hold Schedule.
The scheduled job is placed on hold. To remove the hold and run the job according to
the schedule, uncheck Hold Schedule.
To select multiple jobs, select a job, and then press the Ctrl or Shift keys while you
click other jobs that you want to select. This allows you to apply Hold Schedule to
more than one job at a time, as long as the state of the jobs are the same.
To place the job queue on hold
1. On the navigation bar, click Job Monitor.
2. Click Job List.
3. In the task pane under General Tasks in the task pane, check Hold job queue.
4. Click Yes.
All the jobs in the queue are placed on hold. To remove the hold and run the jobs
according to the schedule, uncheck Hold job queue.
Related Topics:
“Running a scheduled job immediately” on page 451
“Running a test job for a scheduled job” on page 454
“Deleting scheduled jobs” on page 454
452 Administrator’s Guide

Changing the priority for a scheduled job
Chapter 11, Administrating Backup Exec
Monitoring jobs
The priority determines the order that jobs run. If another job is scheduled to run at the
same time as this job, the priority you set determines which job runs first. The priority is
changed for all occurrences of the scheduled job.
If there are multiple backup jobs using the same selection list, then updating the priority
of one backup job will cause the priority for the other backup jobs to be changed as well.
If this occurs, you are prompted before the priority is changed for all backup jobs that
use the same selection list.
You can select multiple jobs by selecting a job, and then pressing the or
keys while you click other jobs that you want to select. This allows you to perform tasks
such as setting priorities on more than one job at a time, as long as the jobs are of similar
type.
To change the priority for a scheduled job from the Job Monitor view
1. On the navigation bar, click Job Monitor.
2. Click the Job List or Calendar tab.
The priority of the job is displayed in the Priority column and include the following
settings:
■ Highest
■ High
■ Medium
■ Low
■ Lowest
3. Select the scheduled job from the Current Jobs pane or the Job Calendar, and then
under Scheduled Job Tasks in the task pane, click Increase priority or Decrease
priority.
The priority is increased or decreased.
To change the priority for a scheduled job from the Job Setup view
1. On the navigation bar, click Job Setup.
2. Select the job from the Jobs pane, and then under General Tasks in the task pane,
click Increase Priority or Decrease Priority.
The priority is increased or decreased.
453

Monitoring jobs
Running a test job for a scheduled job
The test run option determines if a scheduled backup will complete successfully. During
the test run, the tape capacity, credentials, and media are checked. If the test job
determines there is a problem, the job will continue to run and the problem will appear
in the job log.
To run a test job for a scheduled job
1. On the navigation bar, click Job Monitor.
2. Click the Job List or Calendar tab.
3. Select the active job from the Current Jobs pane or the Job Calendar, and then under
Scheduled Job Tasks in the task pane, click Test run.
You can select multiple jobs in the Job List view in the Job Monitor by selecting a job,
and then pressing the or keys while you click other jobs that you
want to select. This allows you to perform tasks such as Test Run on more than one
job at a time, as long as the jobs are of similar type.
4. Enter test run properties for the job. For more information, see “Setting test run
default options” on page 387.
5. On the Properties pane, under Settings, click Notification and enter notification
information for the items. For more information, see “Assigning notification
recipients for completed jobs” on page 565.
6. On the Properties pane, under Frequency, click Schedule and then click Submit job
on hold if you want to submit the job with an on-hold status.
Select this option if you want to submit the job, but do not want the job to run until
you change the job’s hold status.
7. Click Run Now to submit the test run job.
Deleting scheduled jobs
Deleting a scheduled job from the Job Monitor removes a single job occurrence or all
occurrences of the scheduled job.
If the job was created by a policy, you must first click Delete jobs created by policy in
the Job Setup task pane, and remove the association between the policy and the selection
list. Then, you are prompted to delete the jobs that were created when the policy and
selection list were combined.
454 Administrator’s Guide

To delete a scheduled job
1. On the navigation bar, click Job Monitor.
2. Click the Job List or Calendar tab.
Chapter 11, Administrating Backup Exec
Monitoring jobs
3. Right-click the scheduled job in the Current Jobs pane or the Job Calendar, and then
click Delete.
4. Confirm the deletion of the scheduled job. Deleting this job deletes this occurrence
and all other occurrences of this job.
To delete only the occurrences for a specific date, click Cancel on the warning
message. On the navigation bar, click Job Setup and then right-click the job. Click
Properties, and then under Frequency on the Properties pane, click Schedule. Click
Run according to schedule, click Edit Schedule Details, and then exclude that date.
5. After clicking Delete, you are prompted to delete backup selection lists that are no
longer in use by any other jobs. Click Yes to delete all of the unused backup selection
lists, or click No to leave the backup selection lists intact.
To delete selection lists later, on the Edit menu, click Delete Selection Lists.
Related Topics:
“Renaming a job created from a policy” on page 434
Viewing and changing completed jobs
You can view detailed job-related properties for each job that has been processed. For
some jobs, you can right-click the job and choose to retry the job, or choose to configure
a custom error-handling rule for the error that the job failed with.
Errors that are reported in the job log contain hyperlinks that you can click to go to the
Symantec Software Support Services web site and access technical notes and
trouble-shooting steps that are related to a specific error.
The Job History dialog box contains two tabs: Job History and Job Log. The Job History
tab provides summary information for the job. The Job Log tab provides job and file
statistics. Most job logs display in HTML format. However, some logs may display in
text.
455

Monitoring jobs
To view completed job properties
1. On the navigation bar, click Job Monitor.
2. Click the Job list or Calendar tab.
3. Select the completed job you want to view from the Job History pane or the Job
Calendar, and then under General Tasks in the task pane, click Properties.
The Job History dialog box appears. Click Expand All to view all the information
contained in the topics. Click Collapse All to hide the information in the topics.
The Job History tab provides the following job summary and set detail information:
Previous Click this to display the job history of the previous job that was run
as part of this recurring job.
Next Click this to display the job history of the next job that was run as
part of this recurring job.
Job name Job name entered during job configuration.
Job type Type of operation that was performed (Archive, Backup, Catalog,
Restore, Verify).
Job status Status of the operation.
Job log File name and location of the job log.
Server name Media server that processed the job.
Selection list name Selection list processed in the job.
Device Name Name of the device that processed the job.
Target name Name of the device selected during job configuration.
Media set name Name of the media set that processed the job.
All Media Used Lists all the media that was used to process the job.
Job Summary Information
Byte count Number of bytes processed.
Job rate Amount of data backed up per minute for the entire job.
456 Administrator’s Guide

Files Total number of files processed.
Directories Total number of directories processed.
Skipped files Number of files skipped during the operation.
Corrupt files Number of corrupt files encountered during the operation.
Files in use Number of open files encountered during the operation.
Original start time Time the job was submitted for processing.
Job started Time the operation started.
Job ended The time the operation ended.
Elapsed time Length of time the operation took.
Set Detail Information
Chapter 11, Administrating Backup Exec
Monitoring jobs
Set type Type of operation that was performed on the media set (Archive,
Backup, Catalog, Restore, Verify).
Set status Status of the operation.
Set description Job name entered during job configuration.
Resource name Name of the resource for the job.
Logon account Name of the logon account that was used for the job.
Encryption key Indicates if an encryption key was used for the job.
457

Monitoring jobs
Error If an error occurred, the error code is displayed.
Click the Job Log. To locate where the error occurred in the Backup
Set Detail Information, click the error text. Then, if additional
information on an error is available, click the Unique Message
Identifier in the blue hyperlink to go to the Symantec Software
Support Services web site. See “Viewing Unique Message Identifier
error codes in job logs” on page 459 for more information.
After you click OK and exit the log, right-click the job in the Job
History pane, and then click Error-Handling. The Error-Handling
Rule Settings dialog box is displayed. Using this dialog box, you can
enable retry options and final job disposition for jobs when this
error occurs. See “Error-handling rules” on page 474 for more
information.
Agent used Indicates if the Backup Exec agent was used during the operation.
Advanced Open File
Option used
Indicates if the Advanced Open File Option was used during the
operation.
Image used Indicates if the Backup Exec ServerFree Option was used during
the operation.
Start time Time the operation started.
End time Length of time the operation took.
4. Click Job Log to view detailed information about the job.
The job log is in an HTML format. Click Expand All to view all the information in the
topics or Collapse All to hide the information in the topics.
The Job Log tab provides the following information, depending on the type of
operation:
Job Information Displays the job server, job name, the date and time the job started,
the type of job, and the job log name.
Device and Media
Information
Displays the drive name, media label, the overwrite protection and
append periods, and the media set that this job was targeted to.
Utility Job Information Displays information about the slot, bar code, media label, status,
and device that the utility job was processed on. For more
information, see “Creating utility jobs to help manage devices and
media” on page 237.
458 Administrator’s Guide

5. Click Save As to save the job history or job log under a different name or in a
different location.
Chapter 11, Administrating Backup Exec
Monitoring jobs
Job Completion Status Displays the job end time, completion status, error codes, error
description, and error category. The job completion section is
green, orange, or red, depending on the job status (for more detail,
see “Completed job statuses” on page 461).
Errors Displays a detailed description of the errors encountered during
job processing. The errors are grouped by set and labeled. The label
includes the operation and destination resource name for that set.
The error section is red in the job log.
To locate where the error occurred in the Backup Set Detail
Information, click the error text. Then, if additional information on
an error is available, click the underlined error code number to go
to the Symantec Software Support Services web site.
Exceptions Displays a detailed description of the minor errors encountered
during job processing. The exceptions section is orange in the job
log.
6. Click Print if you want to print the job history or job log; however, you must have a
printer attached to your system and configured in order to print the report.
7. Click Find to search for a word in the job history.
8. Click Close to close the log.
Related Topics:
“Completed job statuses” on page 461
“Configuring default job log options” on page 462
Viewing Unique Message Identifier error codes in job logs
Errors that are reported in the job log each have a unique code, called a Unique Message
Identifier (UMI). These codes contain hyperlinks that you can click to go to the
Symantec Software Support Services web site and access technical notes and
trouble-shooting steps that are related to a specific error. Unique Message Identifier
(UMI) error code establishes unique error and message codes across all Symantec
products.
459

Monitoring jobs
To link from an error code in the job log to the Symantec Software Support Services web site
1. On the navigation bar, click Job Monitor.
2. Click the Job List or Calendar tab.
3. Select the completed job you want to view from the Job History pane or the Job
Calendar, and then under General Tasks in the task pane, click Properties.
The Job History dialog box appears.
Click Expand All to view all the information contained in the topics. Click Collapse
All to hide the information in the topics.
4. Scroll to the Job Completion Status section.
5. Click the Unique Message Identifier, displayed as a blue hyperlink, to launch a new
browser window, and go to the Symantec Software Support Services web site.
You can create or enable an error-handling rule for this error, which allows you to set
retry options and final job disposition for jobs when this error occurs.
Related Topics:
“Error-handling rules” on page 474
Deleting completed jobs
You can delete a job from the Job Monitor, or have Backup Exec automatically delete the
job history using database maintenance, or you can set a default when you schedule jobs
to automatically delete jobs that are set to run once, and that are not created from
templates.
If you delete a job, it is removed from the computer and cannot be recovered.
To delete a completed job
1. On the navigation bar, click Job Monitor.
2. Click the Job List or Calendar tab.
3. Select the job you want to delete from the Job History pane or the Job Calendar, and
then under General Tasks in the task pane, click Delete.
460 Administrator’s Guide

Chapter 11, Administrating Backup Exec
Monitoring jobs
You can select multiple jobs in the Job list view in the Job Monitor by selecting a job,
and then pressing the or keys while you click other jobs that you
want to select. This allows you to perform tasks such as Delete on more than one job
at a time, as long as the jobs are of similar type.
After clicking Delete, you are prompted to make sure that you want to delete the job
history and its associated job log.
You can delete up to 2500 jobs from the Job History. If you attempt to delete more
than 2500 jobs, you are prompted to continue with the deletion.
4. Confirm the deletion of the job history and associated job log.
Related Topics:
“Configuring database maintenance” on page 162
“Scheduling jobs” on page 368
Completed job statuses
Possible job completion statuses for jobs that were processed include the following:
Job completion status
Status Description
Successful The job completed without errors.
Completed with
exceptions
The job completed, but a file in use, skipped, or corrupted was
encountered during the operation.
Failed over The job ran in a cluster environment and was active on one computer,
and then the cluster performed a failover and the job was restarted on
another computer in the cluster. There are two separate sets of job
history when a job is failed over. The first job history will have the
Failed over status and the second job history will have the status that
is appropriate for the completed job.
Resumed The status is the same as the failed over status, however the Apply
CheckPoint Restart option was selected.
Canceled The administrator terminated the operation as it was running.
Canceled, timed out The Enable automatic cancellation feature in the Frequency -
Schedule property was enabled and the job was not completed within
the specified timeframe. See “Scheduling jobs” on page 368.
461

Monitoring jobs
Job completion status
Status Description
Failed The operation took place, but one or more significant errors occurred.
The job log should indicate what caused the errors so that you can
decide if you want to run the job again. For example, if a job failure
occurred due to a lost connection during job processing, you could
choose to resubmit the job when the connection is restored.
If a drive loses power during a backup operation, you should restart
the backup job using a different tape. You can restore the data written
to the tape up to the point of the power loss, but you should not reuse
the tape for subsequent backup operations.
A failed job will have an error message in the Errors section of the job
log with a navigable link to the Symantec Software Support Services
web site. See “Viewing Unique Message Identifier error codes in job
logs” on page 459.
Some reasons a job may fail are:
◆ Devices specified by the job were not available when the job was
run.
◆ The logon account information used in the backup job is incorrect.
Verify the logon account information is valid for the resource
being backed up.
◆ There was a problem with the storage device when the job was run.
◆ The computer being backed up was shut down before or during the
backup job.
Recovered The job was active when the status of the managed media server
changed from Communication Stalled to No Communication. The
custom error-handling rule for Recovered Jobs was applied to the job.
For more information, see “Setting communication thresholds and
active job status updates” on page 808.
Missed The job did not run during the scheduled time window. The job is
rescheduled to run based on the time window that you configured. For
more information, see “Setting the time window for a scheduled job”
on page 374.
Configuring default job log options
You can configure default options for job logs that specify the amount of detail you want
to include in the completed job log. For jobs that produce large job logs, for example, a
backup of a considerable number of separate files, you may want to reduce the amount
of detail in the job log. The size of the job log increases proportionally to the level of
detail configured for the job log.
462 Administrator’s Guide

To configure default job log options
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Job Logs.
3. Select the appropriate options as follows:
Information to include in log
Summary information
only
Summary information
and directories
processed
Summary information,
directories, and files
processed
Summary information,
directories, files and file
details
Prefix for the job log file
name
Chapter 11, Administrating Backup Exec
Select this option to include the:
◆ Job name
◆ Job type
◆ Job log name
◆ Media server name
◆ Storage device
◆ Starting date and time
◆ Errors encountered
◆ Ending date and time
Monitoring jobs
◆ Completion statistics
This option also includes the name of files that were skipped, the
media set name, the backup type and results of the verify operation
if one was performed.
Select this option to include summary information and a list of all
processed subdirectories.
Select this option to include Summary information, processed
subdirectories, and a list of all the filenames that were processed.
Select this option to include Summary information, processed
subdirectories, a list of all the filenames and their attributes.
Selecting this option increases the job log sizes significantly.
Enter a prefix to prepend to the job logs that are processed. The
default prefix is BEX.
The job log file name consists of Prefix_ServerName_Count, where
Prefix is the label that you enter in this field, ServerName is the
name of the media server that ran the job, and Count is the number
of job logs that this job has produced.
463

Monitoring jobs
E-mail job log attachments
Attach job logs as html Click this to attach the job logs in an html format when an email
notification is sent.
Attach job logs as text Click this to attach the job logs in a text format when an email
notification is sent.
Job log path You can view the current location of the job log. To change the path
you can use BE Utility.
Related Topics:
“Backup Exec defaults” on page 138
“Viewing and changing completed jobs” on page 455
Using job logs with vertical applications
The Backup Exec Administration Console provides a view of the job logs in HTML
format. If necessary, you can convert the job logs to a text format for use with vertical
applications.
To convert a job log file to a text format, type the following at a command prompt from
the default directory C:\Program Files\Symantec\Backup Exec\Data, or wherever
Backup Exec was installed to:
bemcmd -o31 -f""
For example, to display the job log C:\program files\Symantec\Backup
Exec\Data\bex00001.xml in text format to the command prompt, you would type:
bemcmd -o31 -f"C:\program files\Symantec\Backup
Exec\Data\bex00001.xml"
To redirect the job log to a file, you would type one of the following:
bemcmd -o31 -f"C:\program files\Symantec\Backup
Exec\Data\bex00001.xml" > bex00001.txt
or
bemcmd -o31 -l"bex00001.txt" -f"C:\program
files\Symantec\Backup Exec\Data\bex00001.xml"
464 Administrator’s Guide

Viewing the Backup Exec System Summary
Chapter 11, Administrating Backup Exec
Viewing the Backup Exec System Summary
The Backup Exec System Summary provides detailed summary information about your
media server, jobs, alerts, devices, and media.
To view the Backup Exec System Summary
Filtering jobs
1. On the navigation bar, click Job Monitor.
2. Click the System Summary tab.
You can select predefined filters to limit the jobs that appear in the Jobs pane in the Job
Setup view and the Jobs List pane and the Calendar pane in the Job Monitor view.
To filter jobs
1. Do one of the following:
To filter jobs on the Job
Setup View
To filter jobs on the Job
Monitor view
Click Job Setup.
Click Job Monitor.
2. In the Filter list, click the filter that you want to use.
Related Topics:
“About managing custom filters” on page 466
“Viewing and changing active jobs” on page 442
“Viewing and changing scheduled jobs” on page 448
“Viewing and changing completed jobs” on page 455
465

About managing custom filters
About managing custom filters
You can create and edit custom filters for jobs in the Job Setup view and on the Job List
and Calendar tabs on the Job Monitor view. Backup Exec has an XML file for each pane in
which you can create custom filters. Backup Exec stores the custom filters that you create
in the following location:
\Program Files\Symantec\Backup Exec\Data
The logon account name that you use to log on to the computer is appended to each
custom filters file. Each Backup Exec user has custom filter files. You can only view the
custom filters that you create.
For example, you log on to the computer by using an account named Admin and create
custom filters in Backup Exec for the Current Jobs pane. When you close Backup Exec,
the custom filters are saved in:
\Program Files\Symantec\Backup
Exec\Data\CurrentJobsFilters_Admin.xml
Related Topics:
“Creating a custom filter for jobs” on page 466
“Creating a custom filter for current jobs” on page 468
“Creating a custom filter for jobs in the job history” on page 470
“Creating a custom filter for the calendar” on page 472
“Deleting Custom Filters” on page 473
“Editing Custom Filters” on page 474
Creating a custom filter for jobs
To create a custom filter for Jobs
1. On the navigation bar, click Job Setup.
2. On the Jobs pane, in the Filter list, click .
3. Type a unique name and a description for this filter.
466 Administrator’s Guide

4. Do any of the following:
To filter by job type ◆ Under Criteria, click Job Type.
To filter by backup
method
Chapter 11, Administrating Backup Exec
◆ Check Enable this filter.
About managing custom filters
◆ Check the check boxes for the types of jobs on which you want
to filter. Uncheck the check boxes for the types of jobs on
which you do not want to filter.
◆ Under Criteria, click Backup Method.
◆ Check Enable this filter.
◆ Check the check boxes for the types of backup methods on
which you want to filter. Uncheck the check boxes for the
types of backup methods on which you do not want to filter.
To filter by recurrence ◆ Under Criteria, click Recurrence.
◆ Check Enable this filter.
◆ Check the check boxes for the types of jobs on which you want
to filter. Uncheck the check boxes for the types of jobs on
which you do not want to filter.
To filter by priority ◆ Under Criteria, click Priority.
◆ Check Enable this filter.
◆ Check the check boxes for the types of priority on which you
want to filter. Uncheck the check boxes for the types of
priority on which you do not want to filter.
To filter by policy ◆ Under Criteria, click Policy.
◆ Check Enable this filter.
◆ Check the check boxes for the types of policy on which you
want to filter. Uncheck the check boxes for the types of policy
on which you do not want to filter.
To filter by selection list ◆ Under Criteria, click Selection List.
◆ Check Enable this filter.
◆ Check the check boxes for the types of selection lists on which
you want to filter. Uncheck the check boxes for the selection
lists on which you do not want to filter.
To filter by device name ◆ Under Criteria, click Device Name.
◆ Check Enable this filter.
◆ Check the check boxes for the types of devices on which you
want to filter. Uncheck the check boxes for the types of device
on which you do not want to filter.
467

About managing custom filters
To filter by the server a
job was created on
5. Click OK.
Creating a custom filter for current jobs
To create a custom filter for Current Jobs
1. On the navigation bar, click Job Monitor.
2. On the Current Jobs pane, in the Filter list, click .
3. Type a unique name and a description for this filter.
4. Do any of the following:
◆ Under Criteria, click Created On.
◆ Check Enable this filter.
◆ Check the check boxes for the types of servers on which you
want to filter. Uncheck the check boxes for the types of
servers on which you do not want to filter.
This option appears only if you have the Central Admin Server
Option installed.
To filter by state ◆ Under Criteria, click State.
◆ Check Enable this filter.
◆ Check the check boxes for the types of state on which you
want to filter. Uncheck the check boxes for the types of state
on which you do not want to filter.
To filter by the job type ◆ Under Criteria, click Job Type.
To filter by the server a
job was created on
◆ Check Enable this filter.
◆ Check the check boxes for the types of job on which you want
to filter. Uncheck the check boxes for the types of job on
which you do not want to filter.
◆ Under Criteria, click Created On.
◆ Check Enable this filter.
◆ Check the check boxes for the types of server on which you
want to filter. Uncheck the check boxes for the types of server
on which you do not want to filter.
This option displays only if you have the Central Admin Server
Option installed.
468 Administrator’s Guide

To filter by date range ◆ Under Criteria, click Date Range.
To filter by active job
status
5. Click OK.
Chapter 11, Administrating Backup Exec
About managing custom filters
◆ Do one of the following:
Click Do not use a date range.
Click Show next and then enter the amount of hours or days
on which you want to filter.
◆ Under Active Job Criteria, click Job Status.
◆ Check Enable this filter.
◆ Check the check boxes for the types of job status on which you
want to filter. Uncheck the check boxes for the types of job
status on which you do not want to filter.
To filter by media server ◆ Under Active Job Criteria, click Media Server.
To filter by media server
pool
To filter by scheduled job
status
To filter by backup
method
◆ Check Enable this filter.
◆ Check the check boxes for the media servers on which you
want to filter. Uncheck the check boxes for the media servers
on which you do not want to filter.
This option displays only if you have the Central Admin Server
Option installed.
◆ Under Active Job Criteria, click Media Server Pool.
◆ Check Enable this filter.
◆ Check the check boxes for the media server pools on which
you want to filter. Uncheck the check boxes for the media
server pools on which you do not want to filter.
This option displays only if you have the Central Admin Server
Option installed.
◆ Under Scheduled Job Criteria, click Backup Method.
◆ Check Enable this filter.
◆ Check the check boxes for the types of job status on which you
want to filter. Uncheck the check boxes for the types of job
status on which you do not want to filter.
◆ Under Scheduled Job Criteria, click Backup Method.
◆ Check Enable this filter.
◆ Check the check boxes for the types of backup methods on
which you want to filter. Uncheck the check boxes for the
types of backup methods you do not want to filter.
469

About managing custom filters
Creating a custom filter for jobs in the job history
To create a custom filter for jobs in the Job History
1. On the navigation bar, click Job Monitor.
2. On the Job History pane, in the Filter list, click .
3. Type a unique name and a description for this filter.
4. Do any of the following:
To filter by job type ◆ Under Criteria, click Job Type.
To filter by the job status
To filter by the server a
job was created on
◆ Check Enable this filter.
◆ Check the check boxes for the types of job on which you want
to filter. Uncheck the check boxes for the types of job on
which you do not want to filter.
◆ Under Criteria, click Job Status.
◆ Check Enable this filter.
◆ Check the check boxes for the types of job status on which you
want to filter. Uncheck the check boxes for the types of job
status on which you do not want to filter.
◆ Under Criteria, click Created On.
◆ Check Enable this filter.
◆ Check the check boxes for the types of server on which you
want to filter. Uncheck the check boxes for the types of server
on which you do not want to filter.
This option displays only if you have the Central Admin Server
Option installed.
To filter by media server ◆ Under Active Job Criteria, click Media Server.
◆ Check Enable this filter.
◆ Check the check boxes for the media servers on which you
want to filter. Uncheck the check boxes for the media servers
on which you do not want to filter.
This option displays only if you have the Central Admin Server
Option installed.
470 Administrator’s Guide

To filter by media server
pool
To filter by protected
server
5. Click OK.
Chapter 11, Administrating Backup Exec
About managing custom filters
◆ Under Active Job Criteria, click Media Server Pool.
◆ Check Enable this filter.
◆ Check the check boxes for the media server pools on which
you want to filter. Uncheck the check boxes for the media
server pools on which you do not want to filter.
This option displays only if you have the Central Admin Server
Option installed.
◆ Under Criteria, click Protected Server.
◆ Type the name of the server on which you want to filter.
To filter by job name ◆ Under Criteria, click Job Name.
◆ Type the name of the job on which you want to filter.
To filter by date range ◆ Under Criteria, click Date Range.
◆ Do one of the following:
Click Do not use a date range if you do not want to filter by
specified dates.
Click Show last, and then enter the amount of hours or days
on which you want to filter.
Click Show using the following date range. Check From, and
then enter the date and time on which you want to begin to
filter jobs. Check To, and then enter the date and time on
which you want to end the filter.
◆ Click Show only the last occurrence of a job.
To filter by byte count ◆ Under Criteria, click Byte Count.
◆ Check Enable this filter.
◆ Do one of the following:
Check Greater than, and then enter the amount of the byte
count and the type of bytes on which you want to filter.
Check Less than, and then enter the amount of the byte count
and the type of bytes on which you want to filter.
To filter by elapsed time ◆ Under Criteria, click Byte Count.
◆ Check Enable this filter.
◆ Do one of the following:
Check Greater than, and then enter the amount of time on
which you want to filter.
Check Less than, and then enter the amount of time on which
you want to filter.
471

About managing custom filters
Creating a custom filter for the calendar
To create a custom filter for the Calendar
1. On the navigation bar, click Job Monitor.
2. On the Job Calendar pane, in the Filter list, click .
3. Type a unique name and a description for this filter.
4. Do any of the following:
To filter by state ◆ Under Criteria, click Job State.
◆ Check Enable this filter.
◆ Check the check boxes for the types of state on which you
want to filter. Uncheck the check boxes for the types of state
on which you do not want to filter.
To filter by the job type ◆ Under Criteria, click Job Type.
To filter by job status (job
history)
To filter by the server a
job was created on
◆ Check Enable this filter.
◆ Check the check boxes for the types of job on which you want
to filter. Uncheck the check boxes for the types of job on
which you do not want to filter.
◆ Under Criteria, click Job Status ( Job History).
◆ Check Enable this filter.
◆ Check the check boxes for the types of job status on which you
want to filter. Uncheck the check boxes for the types of job
status on which you do not want to filter.
◆ Under Criteria, click Created On.
◆ Check Enable this filter.
◆ Check the check boxes for the types of server on which you
want to filter. Uncheck the check boxes for the types of server
on which you do not want to filter.
This option displays only if you have the Central Admin Server
Option installed.
472 Administrator’s Guide

To filter by media server ◆ Under Active Job Criteria, click Media Server.
To filter by media server
pool
5. Click OK.
Deleting Custom Filters
To delete a custom filter:
1. Do one of the following:
To delete a custom filter
from the Job Setup view
To delete a custom filter
from the Job Monitor
view
2. In the Filter list, highlight the filter that you want to delete.
3. Click Delete.
Chapter 11, Administrating Backup Exec
◆ Check Enable this filter.
About managing custom filters
◆ Check the check boxes for the media servers on which you
want to filter. Uncheck the check boxes for the media servers
on which you do not want to filter.
This option displays only if you have the Central Admin Server
Option installed.
◆ Under Active Job Criteria, click Media Server Pool.
◆ Check Enable this filter.
◆ Check the check boxes for the media server pools on which
you want to filter. Uncheck the check boxes for the media
server pools on which you do not want to filter.
This option displays only if you have the Central Admin Server
Option installed.
Click Job Setup.
Click Job Monitor.
473

Error-handling rules
Editing Custom Filters
To edit a custom filter:
1. Do one of the following:
To edit a custom filter
from the Job Setup view
To edit a custom filter
from the Job Monitor
view
2. In the Filter list, highlight the filter that you want to edit.
3. Click Edit.
4. Edit the custom filter options.
5. Click OK.
Error-handling rules
Click Job Setup.
Click Job Monitor.
You can enable default rules or create custom rules to set retry options and final job
disposition for failed or canceled jobs. Retry options let you specify how often to retry a
job if it fails and the time to wait between retry attempts. The final job disposition lets
you either place the job on hold until you can fix the error, or reschedule the job for its
next scheduled service.
To apply an error-handling rule for a group of similar errors, or error categories, you
can enable a default error-handling rule. Each default error-handling rule applies to one
category of errors, such as Network Errors or Security Errors. Default error-handling
rules are disabled by default, so you must edit a rule and enable it before the retry
options and job disposition settings will apply to jobs that fail with errors in the selected
category. You cannot delete default error-handling rules, or add specific error codes to a
category, or add new error categories. Before the error-handling rules will apply, the
final error code must be in an error category that is associated with a rule, and the rule
must be enabled.
To apply an error-handling rule for a specific error code that is in an error category, you
can create a custom error-handling rule. You can select up to 28 error codes in an error
category that a custom error-handling rule can apply to. You can also add an error code
to an existing custom rule.
474 Administrator’s Guide

Chapter 11, Administrating Backup Exec
Error-handling rules
One custom error-handling rule, named Recovered Jobs, is created when Backup Exec is
installed and is enabled by default. This rule applies retry options and a final job
disposition to jobs that fail and that are not scheduled to run again. See “Custom
error-handling rule for recovered jobs” on page 478.
If both a custom error-handling rule and a default error-handling rule apply to a failed
job, the settings in the custom rule are applied to the job.
Note If the server on which Backup Exec is installed is in a cluster environment, the
Cluster Failover error-handling rule is displayed on the list of error-handling
rules. This rule is enabled by default. See “Cluster failover error-handling rule” on
page 479.
Creating a custom error-handling rule
To create a custom error-handling rule or to edit error-handling rules
1. Do one of the following:
■ On the Tools menu, click Error-Handling Rules.
■ Right-click a failed or canceled job in the Job History pane in the Job Monitor
view. Click Properties, and then click Error-Handling. Go to step 4 on page 476.
The Error-Handling Rules dialog box appears.
2. Select the appropriate options as described in the following:
Name The name of the error-handling rule.
Type ◆ Default: Predefined default error-handling rules for a category
of errors. You cannot delete default rules and you cannot
modify default rules to include specific error codes in a
category.
◆ Custom: Error-handling rules that you can create for a specific
error code or codes in an error category.
If both a custom error-handling rule and a default error-handling
rule apply to a failed job, the settings in the custom rule are applied
to the job.
Job Status The status of the job that will activate this rule. Statuses are:
◆ Error
◆ Canceled
◆ Failed
475

Error-handling rules
Error Category The category of error codes that this rule applies to.
Enabled ◆ Yes: This rule is enabled. Retry options and final job disposition
will be applied to jobs that failed with the error codes selected
for this rule.
◆ No: This rule is disabled.
3. Do one of the following:
■ To create a new, custom error-handling rule for a specific job error, click New.
Continue with step 4.
■ To delete a custom error-handling rule, select the rule, and then click Delete.
■ To update a default or custom error-handling rule, select a rule, and then click
Edit. Continue with step 4.
4. Complete the items in the Error-Handling Rule Settings dialog box as follows, and
then click OK:
Name Enter a new name or change the name for the error-handling rule.
To add or update a custom error-handling rule, you must enter a
rule name.
Final Job Status The status for the job that will activate the rule. The job status can
be viewed, but not modified. Statuses are:
◆ Error
◆ Canceled
◆ Failed
476 Administrator’s Guide

Chapter 11, Administrating Backup Exec
Error-handling rules
Error Category The category of error for which the rule will be applied.
If you are editing a default or custom error-handling rule, the error
category can be viewed, but not modified.
If you are creating a custom error-handling rule, you must select
an error category that contains the errors to apply this rule to.
Available error categories include:
◆ Other
◆ Network
◆ Server
◆ Resource
◆ Security
◆ Backup Device
◆ Backup Media
◆ Job
◆ System
◆ Dispatch
Enabled Select this check box to enable the error-handling rule, or clear the
check box to disable the rule. This check box must be selected
before you can set the retry options and the final job disposition
options.
Available errors Error codes that are not associated with a custom error-handling
rule. This field will not be displayed if you are editing a default
error-handling rule.
If you are creating or editing a custom error-handling rule, you
must select the check box of the error code that you want this rule
to apply to. You can select up to 28 error codes.
To change the list of available errors, select a different error
category.
Retry Options
Retry job Select this check box to allow Backup Exec to retry the job.
Maximum retries Enter the number of times you want the job retried. The maximum
number of times the job can be retried is 99.
Retry interval Enter the number of minutes to wait before the job is retried. The
maximum number of minutes is 1440.
Final job disposition
477

Error-handling rules
Place job on hold until
error condition has been
manually cleared
Reschedule for its next
scheduled service
Select this option to place the job on hold until you can manually
clear the error. After you clear the error, you must remove the hold
for the job.
Select this option to run the job at the next scheduled occurrence.
Notes Enter any miscellaneous information for the error-handling rule.
Related Topics:
“Error-handling rules” on page 474
“Custom error-handling rule for recovered jobs” on page 478
“Cluster failover error-handling rule” on page 479
Custom error-handling rule for recovered jobs
Recovered Jobs is a custom error-handling rule that is used by Backup Exec to recover
jobs that were failed with specific errors. This rule is created when Backup Exec is
installed, and is enabled by default.
The retry options for this rule are to retry the job twice, with an interval of five minutes
between the retry attempts. The final job disposition is to place the job on hold until you
have manually cleared the error condition.
The following table describes the error codes that are selected by default for the
Recovered Jobs custom error-handling rule.
Error codes for recovered jobs custom error-handling rule
Error code Description
0xE00081D9
E_JOB_ENGINE_DEAD
0xE0008820
E_JOB_LOCAL
RECOVERNORMAL
0xE000881F
E_JOB_REMOTE
RECOVERNORMAL
The displayed error message is:
The Backup Exec job engine system service is not
responding.
See “Setting thresholds to recover jobs” on page 480.
The displayed error message is:
The local job has been recovered. No user action
is required.
The displayed error message is:
The remote job has been recovered. No user action
is required.
478 Administrator’s Guide

Error codes for recovered jobs custom error-handling rule (continued)
Error code Description
0xE0008821
E_JOB_STARTUP
RECOVERY
Chapter 11, Administrating Backup Exec
The displayed error message is:
Error-handling rules
Note If the Central Admin Server Option is installed, additional error codes are
selected.
Related Topics:
“Error-handling rules” on page 474
“Cluster failover error-handling rule” on page 479
Cluster failover error-handling rule
Job was recovered as a result of Backup Exec RPC
service starting. No user action is required.
If the server on which Backup Exec is installed is in a cluster environment, the Cluster
Failover error-handling rule is displayed on the list of error-handling rules. This rule is
enabled by default.
You cannot configure any options for this rule. You can only enable or disable the
Cluster Failover error-handling rule.
The cluster failover error-handling rule and the Apply CheckPoint Restart option in
Cluster Backup Job Properties work together to enable you to resume jobs from the point
of failover. The Apply CheckPoint Restart option is dependent on the cluster failover
error-handling rule; if you disable the rule, the option will automatically be disabled to
match the rule’s setting.
Related Topics:
“Enabling or disabling checkpoint restart” on page 711
479

Setting thresholds to recover jobs
Setting thresholds to recover jobs
If the Backup Exec services become unresponsive, that is, when there are problems with
jobs being sent to the Backup Exec engine or if it seems that jobs are not running, you
can set the threshold at which Backup Exec changes the status of active jobs to stalled.
You can also set the threshold at which Backup Exec fails the jobs that were stalled, and
then recovers them.
By setting a fewer number of seconds before Backup Exec reaches the threshold for
changing a job’s status to stalled, you can receive an earlier notification that jobs have
stalled. A shorter time between the stalled and recovered thresholds also allows Backup
Exec to fail and then recover the stalled jobs earlier. However, setting the thresholds too
low may force a job to be recovered when it is not necessary.
Backup Exec recovers the jobs by using the custom error-handling rule named
Recovered Jobs. This custom error-handling rule is created and enabled when Backup
Exec is installed, and specifies that stalled/failed/recovered jobs are retried two times,
with an interval of five minutes between the retries. For more information, see “Custom
error-handling rule for recovered jobs” on page 478.
Jobs that are stalled and then failed and recovered by Backup Exec because of
unresponsive Backup Exec services are displayed differently in Backup Exec than jobs
that fail because of errors in normal daily activities. The stalled/failed/recovered jobs
are not indicated in red text in the job history as other failed jobs are. Instead, these jobs
are displayed in gray text with a job status of Recovered.
In the job history, the error category is listed as Job Errors. The job history indicates the
type of internal communication error that occurred and that the job was recovered.
Based on the type of error that occurred, there may or may not be a log file associated
with the recovered job.
To set thresholds to recover jobs
1. On the Tools menu, click Options.
2. On the Properties pane, under Settings, click Job Status and Recovery.
3. Change the appropriate fields described in the following table, and then click OK:
Stalled When the Backup Exec job engine service is not responding, enter
the number of seconds before the statuses for active jobs are
changed to Stalled.
480 Administrator’s Guide

Related Topics:
“Error-handling rules” on page 474
“Creating a backup job by using the Backup Wizard” on page 347
“Creating a backup job by setting job properties” on page 349
“About selection lists” on page 327
“Duplicating backed up data” on page 381
“Restoring data by setting job properties” on page 488
“Using resource discovery to search for new resources” on page 339
Chapter 11, Administrating Backup Exec
Setting thresholds to recover jobs
Recovered Enter the number of seconds before jobs are failed and then
recovered by Backup Exec. A custom error-handling rule named
Recovered Jobs is applied to recovered jobs. If this rule is disabled,
then any other error-handling rules that have been enabled will
apply to the recovered jobs. If there are no error-handling rules
that apply to the job, then the job fails.
481

Setting thresholds to recover jobs
482 Administrator’s Guide

Restoring data
Chapter
12
With Backup Exec, you can retrieve information from storage media, including media
created with backup software other than Backup Exec, and restore it to any server or
remote workstation.
In most cases, you will need to restore only one file, but there may be times when
directories, groups of files, or an entire system will need to be restored. Backup Exec
offers several methods for finding the files you need to restore:
Methods for finding files to restore
Method Description
Resource view Lists backed up data by the resource from which it was backed up. This
feature is useful for finding files that were located on a certain server or
workstation.
Media view Lists the data that is contained on a piece of media. This feature is useful
for viewing the contents of a tape that was backed up from another media
server.
Include/Exclude files
feature
Enables you to specify file and date attributes for the data you want to
restore.
Search catalogs Enables you to find files or other items that you want to restore, or to make
sure that you have backups of certain files. This feature also enables you to
see all cataloged, backed up versions of a file, so you can restore earlier
versions if needed.
You can select options that you want to use for most restore jobs. Backup Exec will use
the default options unless you override them when setting up a specific restore job.
483

Restore jobs and the catalog
When creating your restore jobs, you can:
■ Restore data to the system from which it was originally backed up or redirect the
restore to another system.
■ Specify if the restore job should begin processing immediately or schedule it to run
at a future time.
■ Specify which local network is to be used for restoring data, ensuring that other
connected critical networks are not affected by this Backup Exec job.
Related Topics:
“The View by Media tab displays nodes that represent the media that contain backup
sets. Each node displays the media label for the media on which the backup set is
contained.” on page 508
“Selecting data to restore” on page 508
“Including or excluding files for restore” on page 511
Restore jobs and the catalog
While backing up data from a resource, Backup Exec creates a set of catalog files that
reside on the media server and on the media. These catalog files contain information
about the contents of all media and are used when selections are made for restore jobs.
Media backed up at other Backup Exec installations must be cataloged by the local media
server before data can be viewed in the Restore Job Properties dialog box because the
catalog for the media does not exist on the media server. The media must have a Catalog
job performed on it before files can be selected to restore.
Related Topics:
“Cataloging media while reviewing devices or media” on page 284
“Cataloging media while reviewing devices or media” on page 284
“Setting catalog defaults” on page 485
“Catalog levels” on page 486
484 Administrator’s Guide

Setting catalog defaults
To set catalog defaults
Chapter 12, Restoring data
1. On the Tools menu, click Options.
2. On the Properties pane, under Settings, click Catalog.
3. Select the appropriate options as follows:
Request all media in the
sequence for catalog
operations
Use storage media-based
catalogs
Restore jobs and the catalog
Select this option to catalog media starting with the lowest
known tape number in the tape family. For example, if you don’t
have tape one, the catalog job will begin with tape two. If you
uncheck this option, the catalog job begins on the tape that you
specify.
If you uncheck Request all media in the sequence for catalog
operations, then you cannot select the Use storage media-based
catalogs check box.
Select this option to allow Backup Exec to read the catalog
information from the media.
Media-based catalogs allow quick cataloging of media that are
not included in the disk-based catalog (for example, media that
was written by another installation of Backup Exec). This feature
enables media to be cataloged in minutes, rather than the hours
required with traditional file-by-file cataloging methods.
If you want to create a new catalog by having Backup Exec read
each file block, clear this option. Clearing this option is only
recommended if normal catalog methods are unsuccessful.
If you uncheck Request all media in the sequence for catalog
operations, then the Use storage media-based catalogs check box
cannot be selected.
Truncate catalogs after Select this option to retain only the header information and to
remove all file and directory details after the specified amount of
time. This option reduces the size of the catalogs considerably.
After the catalogs have been truncated, the files and directories
cannot be restored unless the media is recataloged.
The last access date is not reset when catalogs are truncated.
You can perform a full restore of backup sets from truncated
catalogs.
This option does not apply to synthetic backup jobs or true
image restore jobs.
485

Restore jobs and the catalog
Current path Type the path where you want catalogs to be located. This path
defaults to \Backup Exec\NT\Catalogs.
Catalog drive Select a volume where you want the catalog files to be located.
This is useful if you have limited disk space on your media
server.
Catalog path Specify a path on the volume for the catalog files. If the path you
provide does not exist, you will be prompted to create the path.
4. Click OK.
Related Topics:
“Restore jobs and the catalog” on page 484
“Catalog levels” on page 486
Catalog levels
The amount of information that can be viewed through the catalog for media is
determined by the media’s catalog level. Backup Exec fully catalogs each backup;
however, there may be instances where media does not appear as fully cataloged in the
Restore Job Properties dialog box. The following are possible catalog levels:
Media catalog levels
Item Description
Fully cataloged media With fully-cataloged media, you can:
◆ View information on all the directories and files contained in
each backup set.
◆ Search for files to restore.
◆ Use the file versioning feature.
Truncated cataloged media Truncated cataloged media lists only backup set information. No
files or file attributes can be viewed. This version of Backup Exec
writes only full catalogs. However, truncated cataloged media that
was migrated from earlier versions of Backup Exec, but not
cataloged by this version, will appear as truncated cataloged media.
Truncated cataloged media will not allow you to make restore
selections. You must catalog the media to view and select files to
restore.
486 Administrator’s Guide

Related Topics:
“Setting catalog defaults” on page 485
“Restore jobs and the catalog” on page 484
Chapter 12, Restoring data
Media catalog levels (continued)
Item Description
Restoring data by using the Restore Wizard
Restoring data by using the Restore Wizard
Uncataloged media There is no catalog information for the media. You must catalog the
media to view and select files to restore.
The Restore Wizard guides you through the creation of a restore job. The Restore Wizard
is helpful for users who are new to Backup Exec.
To restore data using the Restore Wizard
1. From the navigation bar, click the arrow next to Restore.
2. Click New Restore Job using Wizard.
3. Follow the on-screen prompts.
Preventing the Restore Wizard from launching from the Restore
button
By default, the Restore Wizard displays when you select Restore on the navigation bar. If
you prefer to set up restore jobs manually, you can prevent the Restore Wizard from
displaying. If you disable the Restore Wizard, you can re-enable it at any time.
To prevent the Restore Wizard from launching from the Restore button
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job using Wizard.
3. Uncheck Always launch the Restore Wizard from the Restore button.
4. Click Next.
487

Restoring data by setting job properties
To set the Restore Wizard to launch from the Restore button
1. On the Tools menu, click Wizards > Restore Wizard.
2. Check Always launch the Restore Wizard from the Restore button.
3. Click Next.
Restoring data by setting job properties
To restore data by setting job properties
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Select the data that you want to restore.
To protect remote resources, you must install the Backup Exec Remote Agent for
Windows Systems on the remote computer.
4. To change or test the logon credentials for the selected resources, on the Properties
pane, under Source, click Resource Credentials. Complete the options as described
in “Changing and testing resource credentials for restore jobs” on page 516.
5. On the Properties pane, under Source, click Device, and then select the options as
described in “Device options for restore jobs” on page 492.
6. On the Properties pane, under Settings, click General, and then select the options as
described in “General options for restore jobs” on page 492.
You can select additional configuration options for the restore job before selecting to
run or schedule the job. Select additional options on the Restore Job Properties
dialog box Properties pane:
■ If you want to redirect this job to another system other than the one from which
the data was backed up, on the Properties pane, under Destination, click one of
the following (see “Redirecting a restore job” on page 517):
■ File Redirection. Select this option to redirect file sets.
■ Microsoft SQL Redirection. Select this option to redirect SQL Server sets to
another SQL server.
■ Microsoft Exchange Redirection. Select this option to redirect Exchange
sets to another Exchange server.
488 Administrator’s Guide

Chapter 12, Restoring data
Restoring data by setting job properties
■ Microsoft Sharepoint Redirection. Select this option to redirect Sharepoint
Portal Server sets to another Sharepoint server.
■ Oracle Redirection. Select this option to redirect an Oracle instance to
another Oracle server or to an alternate path on an alternate server or the
original server.
■ DB2 Redirection. Select this option to redirect DB2 instances or containers.
■ If you want to set advanced options for the restore job, on the Properties pane,
under Settings, click Advanced. Complete the options as described in “Advanced
options for restore jobs” on page 494.
■ If you want to set commands to run before or after the job, on the Properties
pane, under Settings, click Pre/Post Commands and complete the options as
described in “Running pre and post commands for restore jobs” on page 498.
■ If you are restoring other platform types or database agents, such as SQL,
Exchange, or NetWare, select the platform type from the Properties pane, under
Settings, and then refer to the chapter or appendix for that item for instructions
on completing the options.
■ If you want to specify a local network to be used for this restore job, on the
Properties pane, click Network and Security, and then enter the network
information (see “Specifying the restore network” on page 523).
■ If you want Backup Exec to notify recipients when this job completes, on the
Properties pane, under Settings, click Notification, and then select each
recipient to be notified when the job completes (see “Assigning notification
recipients for completed jobs” on page 565).
Depending on how the default settings for your software are configured, some of the
options may or may not already be selected. You can override the default options by
selecting or clearing items in these dialog boxes.
7. If you want to run the job now, click Run Now. Otherwise, on the Properties pane,
under Frequency, click Schedule to set the scheduling options you want to use (see
“Scheduling jobs” on page 368).
To monitor the job while it is processing, click Job Monitor, and ensure Show active jobs
is selected under Current Job View Filters. You can review results of the restore job in the
job’s log.
Caution When restoring System State, you must reboot your system before performing
subsequent restore jobs.
489

Restoring data by setting job properties
Note Depending on your file system environment, byte counts for restored data may not
match the byte count recorded when the data was backed up. This is normal and
does not mean that files were excluded in the restore job. For more information,
see “Restore questions” on page 675.
Related Topics:
“Selecting data to restore” on page 508
“Symantec Backup Exec Remote Agent for Windows Systems” on page 913
“Redirecting a restore job” on page 517
“Redirecting restores for SQL” on page 1376
“Requirements for restoring Exchange 2000, 2003, and 2007” on page 1259
“Requirements for restoring Exchange 2000, 2003, and 2007” on page 1259
“Restoring NetWare servers” on page 932
“Selecting restore options for Lotus Domino databases” on page 1326
“Filtering jobs” on page 465
“About restoring file permissions” on page 500
Selections options for restore jobs
When the Restore Job Properties dialog box appears, Selections is chosen by default on
the Properties pane. Through the Selections options, you choose the data you want to
include in the restore job. You can also choose how the data will appear in this dialog box.
Options on this dialog box include:
Selections options for restore jobs
Item Description
Selection list If you are creating a job using an existing selection list, select the
selection list or lists you want to use. Otherwise, use the default
Selection list, which creates a new selection list using this name.
Load Selections from
Existing List
Click this button if you want to use a previously created selection list
or merge existing selection lists.
Search Catalogs Click this button to search for files or other items that you want to
restore.
490 Administrator’s Guide

Chapter 12, Restoring data
Selections options for restore jobs (continued)
Item Description
Restoring data by setting job properties
Include/Exclude Click this button if you want to select files to include in or exclude
from the restore job. (see “Including or excluding files for restore” on
page 511).
Include subdirectories Select this option if you want to select the contents of all the
subfolders when a directory is selected.
Show file details Select this option to display details, such as the media label, the last
backup date, and the backup set count, about the files available for
selection.
Preview pane Select this check box to display the preview pane at the bottom of the
dialog box, or clear this check box to remove the preview pane.
Beginning backup date Appears only when the View by Media and View by Resource tabs are
selected. To enable date ranges, check the check box next to the date.
To display only the catalogs for data that was backed up during a
specific date range, enter the beginning date in this field and enter the
ending date in the Ending backup date field.
Ending backup date Appears only when the View by Media and View by Resource tabs are
selected. To enable date ranges, check the check box next to the date.
To display only the catalogs for data that was backed up during a
specific date range, enter the ending date in this field and enter the
beginning date in the Beginning backup date field.
View by Resource Select this tab to display backed up data by the resource from which it
was backed up. This feature is useful for finding files that were located
on a certain server or workstation.
View by Media Select this tab to display the data that is contained on a piece of media.
This feature is useful for viewing the contents of a tape that was
backed up from another media server.
View Selection Details Select this tab to display details about the media selected on either the
View by Resource tab or the View by Media tab. The details that
display include the date and time when the media was created, the
media label, and the backup set to which the media belongs.
491

Restoring data by setting job properties
Device options for restore jobs
To set device options for restore jobs, on the Properties pane, under Source, click Device.
Device options for restore jobs
Item Description
Device Enter the name of the device that contains the media for the data you want
to restore.
Maximum number
of devices to use for
resources that
support multiple
data streams
General options for restore jobs
Select the maximum number of devices that this restore job can use. Only
one device per stream can be used. This option is applicable only for
restores of Oracle and DB2 data.
General options for restore jobs, including the name of the job, can be set through the
Restore Job Properties dialog box. To set these options, on the Properties pane, under
Settings, click General. Options for this dialog box include:
General settings options for restore job
Item Description
Job name Enter a name that describes the data that you are restoring. This is
the name that is used to identify this job in the job schedule.
Job priority Select the priority level for this job. If another job is scheduled to
run at the same time as this job, the priority you set determines
which job runs first. Your choices are:
◆ Highest
◆ High
◆ Medium
◆ Low
◆ Lowest
Restore over existing files Select this option to have Backup Exec overwrite files on the target
resource that have the same name as files that are being restored.
Use this option only when you are sure that you want to restore an
older version of a file.
492 Administrator’s Guide

Chapter 12, Restoring data
General settings options for restore job (continued)
Item Description
Restoring data by setting job properties
Skip if file exists Select this option to prevent Backup Exec from overwriting files on
the target disk with files that have the same names that are
included in the restore job.
Overwrite the file on disk
only if it is older
Restore all information for
files and directories
Restore only security
information for files and
directories
Restore all information
except security for files and
directories
Select this option to prevent Backup Exec from restoring over files
that exist on the disk if they are more recent than the files included
in the restore job.
This option is useful if you are rebuilding a system. For example,
after installing the operating system on a crashed computer, you
could restore a previous full backup of the system without worrying
about overwriting later versions of operating system files.
Select this option to restore all information, including security
information, for files and directories.
Select this option to restore only security information for files and
directories. No other information is restored. This option is valid
only for NTFS volumes. If you select this option along with the Skip
if file exists option, no information will be restored. You can use this
option with the Restore over existing files option and the Skip if
existing file is more recent option.
Select this option to restore all information except security
information for files and directories. This option is valid only for
NTFS volumes.
Restore corrupt files Select this option only if you do not want to have Backup Exec
automatically exclude corrupt files from the restore process.
This option is only recommended if a job has failed because a
catalog query could not determine the corrupt files on the tape.
Normally, when a restore job is run, Backup Exec queries the catalog
to determine if any corrupt files are on the tape and excludes them
from the restore job. If, during the query process, Backup Exec
cannot determine if a file is corrupt, the Restore job will not
continue and will be marked as Failed. If a corrupt file cannot be
excluded automatically, you can manually exclude corrupt files in
the Restore selections window and run the job with the Restore
Corrupt File option enabled.
493

Restoring data by setting job properties
General settings options for restore job (continued)
Item Description
Preserve tree Select this check box to restore the data with its original directory
structure intact. This option is enabled by default. If you clear this
option, all data (including the data in subdirectories) is restored to
the path you specify in the Redirection dialog box.
Clearing the Preserve Tree option is useful when restoring several
subdirectories or individual files from media, but it should not be
cleared when restoring an entire drive.
Related Topics:
“Restoring data by setting job properties” on page 488
Advanced options for restore jobs
To set Advanced options for restore jobs, on the Properties pane, under Settings, click
Advanced. Options for this dialog box include:
Advanced options for restore
Item Description
Restore Removable Storage
data
Select this check box to restore the Removable Storage data. The
Removable Storage database is stored in the
Systemroot\System32\Ntsmsdata directory and is automatically
backed up when the system directory is selected for backup.
Removable Storage is a service used to manage removable media
and storage devices; it enables applications to access and share the
same media resources.
Restore disk quota data Select this check box to restore disk quota data. Disk quota data is
automatically backed up when the root directory of a volume is
selected for backup.
Disk quotas track and control disk usage on a per user, per volume
basis; the values can be restored to the limits that were set before
the backup.
494 Administrator’s Guide

Restore Terminal Services
database
Restore Windows
Management
Instrumentation repository
Chapter 12, Restoring data
Advanced options for restore (continued)
Item Description
Restoring data by setting job properties
Select this check box to restore the Terminal Services database. The
default location for the Terminal Services database, which contains
licensing data for client licenses, is the
Systemroot\System32\LServer directory and is automatically
backed up when the system directory is selected for backup.
Terminal Services allow client applications to be run on a server so
that client computers can function as terminals rather than
independent systems.
Select this check box to restore the Windows Management
Instrumentation (WMI) repository. The WMI repository is stored in
the Systemroot\System32\wbem\Repository directory and is
automatically backed up when the system directory is selected for
backup.
The Windows Management Instrumentation repository provides
support for monitoring and controlling system resources and
provides a consistent view of your managed environment.
Restore Cluster Quorum Select this check box to restore the cluster configuration. For more
information about restoring clusters, see “About Restoring data to a
Microsoft cluster” on page 729.
Force the recovery of the
cluster quorum even if
other nodes are online
and/or disk signatures do
not match.
Select this check box to restore the cluster configuration if you are
not able to take the other nodes in the cluster offline or if the disk
that the cluster quorum previously resided on has been changed.
This option is only available if Restore Cluster Quorum is also
selected.
If this option is selected, the cluster service for any nodes that are
online is stopped. This option also enables the drive letter of the
disk that the cluster quorum was on to remain the same, even if the
configuration has changed and the disk signatures contained in the
restore media do not match the disk signatures contained in the
cluster quorum.
Any changes made to the cluster quorum after the last backup will
be lost.
495

Restoring data by setting job properties
Advanced options for restore (continued)
Item Description
Mark this server as the
primary arbitrator for
replication when restoring
folders managed by the File
Replication Service, or
when restoring SYSVOL in
System State.
Restore Windows NT 4.0
registry
Merge the existing
hardware configuration and
registry services with the
data to be restored
Overwrite the existing
hardware configuration and
registry services with the
data to be restored
Restore junction points,
directories, and files from
backup media
Select this check box to designate this server as the primary
replicator for all members in the set when restoring FRS-managed
folders or SYSVOL as part of System State.
If all members of a replication set are to be restored, then stop
replication, restore all the member servers, and then when
restoring the last member server, select this option to designate the
server as the primary replicator. If this option is not selected,
replication may not function.
Note In this version of Backup Exec, all restores of SYSVOL and
FRS-managed folders are non-authoritative. An authoritative
restore can only be performed by redirecting the restore and
then copying the files to the server. Refer to your Microsoft
documentation for details on performing an authoritative
restore.
Select this check box to restore registry information if it exists in
the data you selected.
Select this option if you want to merge the existing hardware and
registry services with the data you selected to be restored. This
option should only be used for restoring System State.
Select this option if you want to overwrite hardware configuration
and registry services with the data you selected to be restored. This
option should only be used for restoring System State and there
have been no hardware changes.
Select this option to restore the information for the junction points
and the files and directories to which they are linked. Selecting this
option overwrites existing junction points on your system.
Note If a junction point was originally backed up without the Back
up files and directories by following junction points check
box selected (see “Back up files and directories by following
junction points” on page 362), then the files and directories
to which the junction point is linked will not be restored,
unless the junction point was linked to a mounted drive that
did not have an assigned drive letter.
496 Administrator’s Guide

Preserve existing junction
points and restore files and
directories from backup
media
Related Topics:
“Restoring data by setting job properties” on page 488
Chapter 12, Restoring data
Advanced options for restore (continued)
Item Description
Allow managed media
server to use any network
interface to access remote
agents
Path on media server for
staging temporary restore
data when restoring
individual items from tape
Restoring data by setting job properties
Select this option to restore files and directories backed up from
junction point links while retaining the system's current junction
points. This option keeps current junction points from being
overwritten with the junction point information restored from the
backup media.
When this option is selected and identical junction points or
directory names exist on both the target system and the media, the
files and directories are restored to the target system's junction
point or directory.
If a junction point or directory does not already exist in the same
location and with the same name as the junction point to be
restored, then the information for the junction point and the files
and directories to which they point will be restored.
Note If a junction point was originally backed up without the Back
up files and directories by following junction points check
box selected (see “Back up files and directories by following
junction points” on page 362), then the files and directories
to which the junction point is linked will not be restored,
unless the junction point was linked to a mounted drive that
did not have an assigned drive letter.
This option is applicable only for the Central Admin Server Option.
Select this option to enable a job that is delegated or copied to a
managed media server to use any network interface to access
remote agents. Be default, jobs that are delegated or copied to a
managed media server from the central administration server use
the network and security settings that are set on the managed
media server. If the network specified on the managed media server
is unavailable, selecting this check box enables the managed media
server to use an alternate network to run important jobs.
This option is applicable only when you restore individual items
from tape-based backups of Microsoft Exchange, SharePoint, and
Active Directory. Type the path to a location on this media server
where restore data and metadata can be stored temporarily before
the individual items are restored. The staged data is automatically
deleted when the restore is complete.
Symantec recommends that you avoid using system volumes for
temporary staging locations.
497

Restoring data by setting job properties
Running pre and post commands for restore jobs
You can run commands before or after a restore job, and set the following conditions for
these commands:
■ Run the job only if the pre-job command is successful
■ Run the post-job command only if the pre-job command is successful
■ Run the post-job command even if the job fails
■ Allow Backup Exec to check the return codes (or exit codes) of the pre- and post-job
commands to determine if the commands completed successfully. An exit code of
zero returned to the operating system by the pre- or post-job command is interpreted
by Backup Exec to mean the command completed successfully. A non-zero exit code
is interpreted by Backup Exec to mean the command ended with an error.
If it is critical that the job not run if the pre-job command fails, then configure Backup
Exec to check the return codes of the pre- and post-job commands to determine if the
pre-job command failed or completed successfully.
For example, if a pre-job command that shuts down a database before a restore is run
fails, the database could be corrupted when the restore is run. In this situation, it is
critical that the restore job fail if the pre-job command fails.
Additionally, if Backup Exec is configured to check the return codes of the pre- and
post-job commands, and the post-job command returns a non-zero code, the job log
reports that the post-job command failed. If you also selected to run the job only if the
pre-job command is successful, and both the pre-job command and the job ran
successfully, Backup Exec will mark the job as failed if the post-job command fails.
For example, if the pre-job command runs successfully and shuts down the database and
the restore job also runs successfully, but the post-job command cannot restart the
database, Backup Exec marks the job and the post-job command as failed.
If you select the option On each server restored to, the pre- and post-commands are run
and completed for each server before processing begins on the next selected server.
498 Administrator’s Guide

To set up commands to run before or after a restore job
Chapter 12, Restoring data
Restoring data by setting job properties
1. On the Properties pane, under Settings, click Pre/Post Commands.
2. Select the following options as needed:
Pre-command Specify a command to be run on the specified server before the
restore job is run. Use local paths, and make sure the paths exist
on each server and are correct.
Note Commands that require user interaction, such as
prompts, are not supported.
Post-command Specify a command to be run on the specified server after the
restore job has run. Use local paths, and make sure the paths
exist on each server and are correct.
Note Commands that require user interaction, such as
prompts, are not supported.
Allow pre- and post-
commands to be successful
only if completed with a
return code of zero
Run job only if
pre-command is successful
Select this option to allow Backup Exec to check the return
codes of the pre- and post-commands to determine if they
completed successfully.
An exit code of zero returned to the operating system by the
pre- or post-command is interpreted by Backup Exec to mean
the command completed successfully. A non-zero exit code is
interpreted by Backup Exec as the command ended with an
error.
After checking the return codes, Backup Exec continues
processing according to selections you made for running the
pre- and post- commands.
If this option is not selected, the success of the pre- and postcommands
is not determined based on the return code.
Select this option to run the restore job only if the
pre-command is successful. If the pre-command fails, the job
does not run, and is marked as failed.
If it is critical that the job not run if the pre-command fails,
then select Allow pre- and post-job commands to be successful
only if completed with a return code of zero. If a non-zero exit
code is returned, it is interpreted by Backup Exec to mean that
the pre-command did not run successfully. The job is not run
and the job status is marked as Failed.
499

Restoring data by setting job properties
Run post-command only if
pre-command is successful
Run post-command even if
job fails
Cancel command if not
completed within x minutes
Related Topics:
“Restoring data by setting job properties” on page 488
“Setting default pre/post commands” on page 396
About restoring file permissions
Select this option to run the post-command only if the
pre-command is successful.
If it is critical that the post-command fail if the pre-command
fails, then select Allow pre- and post-commands to be
successful only if completed with a return code of zero. If a
non-zero exit code is returned for the pre-command, it is
interpreted by Backup Exec to mean that the pre-command did
not run successfully. The post-command is not run.
If you also select Run job only if pre-job command is
successful, and both the pre-command and the job are
successful, but the post-command returns a non-zero code, the
job log reports both the job and the post-command as failed.
Select this option if it is critical to run the post-command
regardless if the job is successful or not.
If you also select Allow pre- and post-commands to be
successful only if completed with a return code of zero and the
post-command returns a non-zero code, the job log reports the
post-command as failed.
Select the number of minutes Backup Exec should wait before
canceling a pre- or post-command that did not complete. The
default time-out is 30 minutes.
On this media server Select this option to run the pre- and post-commands on this
media server only.
On each server restored to Select this option to run the pre- and post-commands one time
on each server to which data is restored during this job.
The pre- and post-command selections apply to each server
independently. If you select this option, the pre- and
post-commands are run and completed for each server before
processing begins on the next selected server.
This section contains details on restoring data using the Restore Security option, which
affects file security. This security feature applies only to NTFS partitions. To enable the
Restore Security option, on the Properties pane, under Settings, you select General.
500 Administrator’s Guide

Chapter 12, Restoring data
Restoring data by setting job properties
When restoring data with the Restore Security option, Backup Exec overwrites all
directory security information presently on the disk with the security levels associated
with the data being restored. This overwrite begins at the root of the restored directory
structure and updates each directory in the tree until it reaches the data contained in the
last directory.
For example:
With the following data on the storage media (a backup made prior to making
security changes on disk):
\(root)Security applied: Users - Full
\UsersSecurity applied: Users - Full
\User1Security applied: User1 - Full
DATA.TXT Security applied: User1 - Full
With the following data on the disk (recently changed directory and file security):
\(root)Security applied: Users - Read
\UsersSecurity applied: Users - Change
\User1Security applied: User1 - Full
DATA.TXT Security applied: User1 - Full
After a restore with the Restore Security option selected, the security level of
the data on the disk looks like this:
\(root)Security applied: Users - Full
\UsersSecurity applied: Users - Full
\User1Security applied: User1 - Full
DATA.TXT Security applied: User1 - Full
If the data is restored without the Restore Security option selected, data.txt
would inherit the permissions of the directory in which it was restored. In this
case, it would inherit User1 directory’s security level of Full.
Related Topics:
“General settings options for restore job” on page 492
Restoring System State
The system-specific data that comprises System State includes the registry, the COM+
Class Registration database, and boot and system files. The Certificate Services database
will also be included if the server is operating as a certificate server. If the server is a
domain controller, the data also includes Active Directory services database and SYSVOL
directory. The System State data is backed up only as a collection. However, you can use
the Active Directory Recovery Agent to restore individual objects.
501

Restoring data by setting job properties
If you are restoring Active Directory to a computer that is a domain controller, you must
start the computer in safe mode and use the Directory Services Restore Mode to perform
the restore. System State cannot be restored unless the target computer is in Directory
Services Restore Mode. To restore System State data to a server that is not a domain
controller, you can perform a basic restore.
Note A System State backup is always a full backup. Therefore, when restoring, only the
most recent backup of the System State must be restored.
You should not cancel a System State restore job. Canceling this job could leave the
system unusable.
To start the Backup Exec services and perform a local restore of System State data on a
domain controller
1. Start the target server, press when prompted for Startup Options, and then
select the Directory Services Restore Mode option.
2. To open Services, right-click My Computer, and then click Manage.
3. Expand Services and Applications.
4. Click Services.
5. For each Backup Exec service listed:
■ Click Properties on the shortcut menu.
■ Click the Log On tab, click This account, enter a user account with local
administrator’s rights, and then click OK.
■ Right-click the service, and then click Start.
6. After the Backup Exec services have started, run Backup Exec and perform a restore
of the System State. Set the following option on the Advanced screen: Mark this
server as the primary arbitrator for replication when restoring folders managed
by the File Replication Service, or when restoring SYSVOL in System State. For
more information, see “Advanced options for restore jobs” on page 494.
Caution When restoring System State, you must reboot your system before performing
subsequent restore jobs.
If you have more than one domain controller in the network and you want Active
Directory replicated to the other domain controllers, you must perform an authoritative
restore of the Active Directory.
502 Administrator’s Guide

Chapter 12, Restoring data
Restoring data by setting job properties
To perform an authoritative restore of the Active Directory, you must run Microsoft’s
Ntdsutil utility after the Backup Exec restore job completes and you have restored the
System State data, but before you restart the server. An authoritative restore ensures
that the restored data is replicated to all of the servers. For more information about
authoritative restore and the Ntdsutil utility, see your Microsoft documentation.
Related Topics:
“Restoring data by setting job properties” on page 488
“Advanced options for restore” on page 494
“About restoring individual Active Directory and ADAM objects” on page 905
About restoring Shadow Copy Components
The Backup Exec Shadow Copy Components file system uses Microsoft’s Volume Shadow
Copy Service to protect critical operating system and application service data, and third
party application and user data on Windows Server 2003 resources.
A Writer is specific code within an application that participates in the Volume Shadow
Copy Service framework to provide point-in-time, recovery-consistent operating system
and application data. Writers appear as Shadow Copy Components, which are listed as
resources in backup and restore selections. When expanded, the Backup Exec Shadow
Copy Components file system includes System State Writers, Service State Writers, and
User Data Writers.
■ System State Writers. To restore System State Writers, see “Restoring System State”
on page 501.
■ Service State Writers. To restore Service State Writers, follow normal restore
procedures. See “Restoring data by setting job properties” on page 488.
The User Data Writer in Backup Exec is the Active Directory Application Mode Writer
(ADAM Writer). When restoring data with the ADAM Writer, Backup Exec stops the
service for the ADAM instance you want to restore before the restore job starts. However,
Backup Exec does not restart the ADAM service when the restore job completes because
post-processing jobs, such as authoritative restores using Adamutil.exe, may be needed.
You must restart the ADAM service. If Backup Exec cannot stop the ADAM service or if
Backup Exec cannot restore all of the ADAM files, the ADAM restore will fail.
Related Topics:
“About restoring individual Active Directory and ADAM objects” on page 905
“Using redirected restore for Active Directory, Active Directory Application Mode” on
page 518
503

Restoring data by setting job properties
About restoring utility partitions
Utility partitions, which are usually small partitions installed on the disk by OEM
vendors like Dell, Compaq, Hewlett-Packard, and IBM, can be selected for restore. These
utility partitions contain system diagnostic and configuration utilities and are usually
restored during disaster recovery. However, utility partitions can be selected during a
normal restore job provided the following requirements are met:
■ Utility partitions, but not the data belonging to the partitions, must be present on
the system.
■ You must have Administrator rights to restore utility partitions.
■ The system on which the utility partition data is being restored should be the same
system from which the data was originally backed up, unless you are required to do a
redirected restore (see “Performing redirected restores of utility partitions” on
page 504).
■ Utility partitions being restored must belong to the same vendor. For example, Dell
utility partitions cannot be restored to a Compaq system.
■ The size of the utility partition on which the data is being restored must be equal or
greater in size than the utility partition that was backed up.
Related Topics:
“Restoring data by using the Restore Wizard” on page 487
“Selecting data to restore” on page 508
Performing redirected restores of utility partitions
You may need to perform a redirected restore of a utility partition if, during a disaster
recovery, the system being recovered has been renamed. A redirected restore could also
be required if a new system is replacing a crashed system. In the latter case, the system
being restored must be the same model as the system originally backed up.
When doing a redirected restore of utility partitions, the following conditions must be
met:
■ Utility partitions, but not the data belonging to the partitions, must be present on
the system.
■ You must have Administrator rights to restore utility partitions.
■ Utility partitions being restored must belong to the same vendor. For example, Dell
utility partitions cannot be restored to a Compaq system.
■ The size of the utility partition on which the data is being restored must be equal or
greater in size than the utility partition that was backed up.
504 Administrator’s Guide

Chapter 12, Restoring data
Restoring data by setting job properties
■ The system on which the redirected restore is targeted must be the same make and
model and have the same size utility partitions as the system from which the utility
partition was backed up.
Related Topics:
“Redirecting a restore job” on page 517
“Manual disaster recovery of Windows computers” on page 658
About restoring EFI system partition data
The Extensible Firmware Interface (EFI) is required to boot Windows on all Intel Itanium
64-bit computers. You can restore EFI system partition data using Backup Exec on Intel
Itanium 64-bit computers. EFI system partition data can be restored only on remote
computers using the Backup Exec Remote Agent. You can redirect EFI partition data to
any NTFS or FAT drive. However, you cannot redirect a restore job to an EFI partition.
If the 64-bit Intel Itanium computer cannot be started because the EFI system partition
data is corrupted, you must use the Backup Exec Intelligent Disaster Recovery (IDR)
option to restore the EFI data.
Related Topics:
“About the Backup Exec Shadow Copy Components file system” on page 341
“Redirecting a restore job” on page 517
“Symantec Backup Exec Intelligent Disaster Recovery Option” on page 1501
Restoring Distributed File System (Dfs) links
To restore Distributed file system (Dfs) links
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. In the selection list, navigate to the computer that hosts the Dfs root.
4. Expand the Dfs root selection and then select the backup set to restore.
If you backed up any Dfs links, de-select them before you restore the volume.
The links within the Dfs root are not cataloged, therefore Backup Exec displays "No
selections exist". All Dfs link data is associated with the Dfs root name, so the links
will be restored with the Dfs root.
505

Restoring data by setting job properties
5. Run the restore job.
Related Topics:
“Selecting Distributed File System (Dfs) links for backup” on page 324
About restoring media created with other backup software
Media backed up with the following software products can be read with this version of
Backup Exec and restored to the system from which it was backed up or redirected to a
compatible system or resource. In addition, Backup Exec can read media backed up with
products that record media in the following tape formats:
■ Microsoft Tape Format (MTF)
■ SIDF
■ BrightStor® ARCserve® Backup Formats
■ Stac Image Option
Backup Exec also supports restoring NetWare SMS volume backups to non-SMS volumes.
For example, data backed up with Backup Exec for NetWare Servers or Novell’s SBackup
can be restored to the Windows media server or another network share. Media from the
following products can be restored with Backup Exec:
■ Backup Exec for Windows NT 7.3 and later (MTF)
■ Backup Exec for NetWare Servers 7.x, 8.x, and 9.x (MTF)
■ Software-compressed media created with previous versions of Backup Exec, such as
Backup Exec for Windows NT (5.x, 6.x and 7.x)
■ Seagate Backup Director (SIDF)
■ Seagate Storage Exec (SIDF)
■ BrightStor® ARCserve® Backup 9, 10, 11, and 11.5 for Windows
■ Novell SBackup (SIDF)
■ Palindrome Backup Director for Windows NT and NetWare (SIDF)
■ Palindrome Storage Manager for Windows NT and NetWare (SIDF)
Note Software-compressed data backed up with products other than Backup Exec for
Windows Servers cannot be restored.
For more information about supported software, go to
http://support.veritas.com/menu_ddProduct_BEWNT_view_CL.htm
506 Administrator’s Guide

Chapter 12, Restoring data
Restoring data from ARCserve media
Restoring data by setting job properties
Backup Exec enables you to restore data from tapes backed up with ARCserve for
Windows 9 or later.
The following types of data cannot be restored from ARCserve tapes:
■ System State (from tapes created by ARCserve 6.x for NetWare and ARCserve 6.x for
Microsoft Windows
■ Databases, such as Microsoft SQL and Exchange Server and NetWare Directory
Services
■ Windows registry
■ Interleaved files
■ Compressed files
■ Encrypted files
■ Long filenames and Extended Attributes for OS/2 files
■ Long filenames and resource forks for Macintosh files
Media containing ARCserve backups can be overwritten; however, backup append jobs
are not supported. All Backup Exec media utility functions can be performed on
ARCserve media.
Note If the ARCserve backup spans multiple tapes, you must have all the tapes that were
included in the ARCserve backup available. Make sure you start both the catalog
and restore jobs with the first tape used in the ARCserve backup.
To restore data from ARCserve media
1. Inventory all the tapes included in the ARCserve backup.
2. Catalog all the tapes included in the ARCserve backup.
During cataloging, Backup Exec reports file formats that it can read. Files that
cannot be read do not appear in the catalogs. The media description that appears in
the Backup Exec catalog comes from the session description used by ARCserve.
Media-based catalogs are not supported on tapes created by other vendors’ backup
products. Because of this, cataloging ARCserve tapes takes considerably longer than
cataloging a tape made with Backup Exec.
3. Restore selected data to a server or workstation.
507

Selecting data to restore
Due to the naming conventions ARCserve uses for some systems, it may be necessary
to select a different location for the data using Backup Exec’s File Redirection. For
more information, see “Redirecting a restore job” on page 517.
Related Topics:
“Inventorying media” on page 238
“Cataloging media while reviewing devices or media” on page 284
“Restoring data by setting job properties” on page 488
“Redirecting a restore job” on page 517
“About restoring media created with other backup software” on page 506
Selecting data to restore
When you are setting up a restore job, the first thing you do is select the data you want to
restore. You can select data from the View by Resource tab or the View by Media tab.
On the View by Resource tab, restore selections are listed by the resource from which
they were backed up.
View by Resource
The View by Media tab displays nodes that represent the media that contain backup sets.
Each node displays the media label for the media on which the backup set is contained.
If a backup set spans multiple pieces of media, the node for that backup set displays the
media labels for all of those pieces of media. Beneath that node, the backup sets displays.
Note True image restore selections do not appear on the View by Media tab. You can
view true image restore selections on the View by Resource tab.
508 Administrator’s Guide

View by Media
Media label
Backup sets
Chapter 12, Restoring data
Selecting data to restore
To expand the view for a resource or piece of media, click the adjacent box that contains
the plus sign (+). To collapse the view, click the minus sign (-).
When the view is expanded, backup sets contained on the resource or media are
displayed. You can expand the backup set to view the data included in the backup. The
data that has been backed up from the resource appears in the right pane of the Restore
Job Properties - Selections dialog box. Remember that only media cataloged or backed up
at this server are displayed in the views. If you want to restore data backed up at another
installation of Backup Exec, you must catalog the media first.
You can traverse file levels from either side of the window by clicking folders and
subfolders as they appear.
To select data, select the check box next to the drives, directory, or file you want to
restore. If the Include Subdirectories option is selected on the Restore Job Properties
dialog box, all files and directories at or below the selected directory level are included in
the restore job. The check box and check mark displayed vary depending on the item’s
status.
Data Selections
A slash in a shaded check box means that some
items below the check box are selected, but the
item itself cannot be selected.
A check mark in a check box means all items at
or below the directory or drive level are
selected.
A slash in a check box means some items below
the directory or drive level are selected.
A clear check box means the item can be
selected.
Related Topics:
“Restore jobs and the catalog” on page 484
“Cataloging media while reviewing devices or media” on page 284
“Restoring data by setting job properties” on page 488
509

Creating a restore selection list
Creating a restore selection list
To create a restore selection list
1. On the navigation bar, click Job Setup.
2. On the Task pane, under Selection List Tasks, click New restore selection list.
3. Select the resources that you want to include in the selection list.
4. Select the appropriate options as follows:
Selection list Type the name of this selection list or use the name that Backup
Exec provides.
Load Selections from
Existing List
Click Load Selections from Existing List if you want to load an
existing selection list or merge multiple selection lists (see
“Merging and replacing selection lists” on page 330).
Search Catalogs Click Search Catalogs to search the catalog to find files or other
items that you want to restore, or to make sure that you have
backups of certain files. This feature also enables you to see all
cataloged, backed up versions of a file, so you can restore earlier
versions if you need to. You can also use this feature to make sure
that you have multiple copies of a file before removing it with an
archive job.
Include/Exclude Click Include/Exclude to select files that you want to include in or
exclude from this selection list.
Include subdirectories Select this option if you want to select the contents of all the
subfolders when a directory is selected.
Show file details Select this option to display details about the files available for
selecting.
Preview pane Select this check box to display the preview pane at the bottom of
the dialog box, or clear this check box to remove the preview pane.
Beginning backup date Displays only when the View by Media and View by Resource tabs
are selected. To enable date ranges, check the check box next to the
date. To display only the catalogs for data that was backed up
during a specific date range, enter the beginning date in this field
and enter the ending date in the Ending backup date field.
510 Administrator’s Guide

Chapter 12, Restoring data
Including or excluding files for restore
Ending backup date Displays only when the View by Media and View by Resource tabs
are selected. To enable date ranges, check the check box next to the
date. To display only the catalogs for data that was backed up
during a specific date range, enter the ending date in this field and
enter the beginning date in the Beginning backup date field.
View by Resource Select this tab to display backed up data by the resource from which
it was backed up. This feature is useful for finding files that were
located on a certain server or workstation.
View by Media Select this tab to display the data that is contained on a piece of
media. This feature is useful for viewing the contents of a tape that
was backed up from another media server.
View Selection Details Select this tab to display details about the media selected on either
the View by Resource tab or the View by Media tab. The details that
display include the date and time when the media was created, the
media label, and the backup set to which the media belongs.
5. (Optional) To change or test a logon account for the resources, on the Properties
pane, under Source, click Resource Credentials. For more information, see “To
change and test resource credentials for restore jobs” on page 516.
6. Click OK.
Including or excluding files for restore
Use the Include/Exclude feature to include files in or exclude files from a restore job. This
feature is useful when you want to restore only a specific file, a specific type of file, or
files that were created or modified on a certain date. With this feature you can:
■ Include or exclude files by filename extensions. For example, you can include only
files with *.txt extensions, or exclude files with *.exe extensions.
■ Select only files that fall within a specified date range. For example, you can select
files that were created or modified during the month of December.
To include or exclude files for restore
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
511

Including or excluding files for restore
4. Click Include/Exclude.
Select the appropriate options as follows:
Media Select the media that contains the files you want to restore.
Backup Set Select the backup set for which you want to specify attributes.
Path Enter any available directory or subdirectory. Enter the full
path to the subdirectory.
File Specify a filename to be included or excluded. The default for
this field is *.*, which means every file name with every
extension is selected. Wildcard characters are permitted. The
asterisk (*) in a file name or extension is a wildcard character
that represents all characters occupying any remaining
position in the file name or extension. For example, to specify
all files with the .exe extension, type *.exe
The question mark symbol (?) wildcard for a single character is
also supported, as well as a double asterisk (**) to represent any
number of characters, irrespective of any backslashes.
Include Subdirectories When this option is selected, all subdirectories and their
contents in the path you have entered are included in (or
excluded from) the job. If you want to process only the directory
listed in the Path field, leave this option cleared.
Include Select this option to include the files in the operation. This is
the default option.
Exclude Select this option to exclude files from the job.
Files Dated Select this check box to include or exclude files created or
modified during the specified time period.
5. Submit the job using the same procedures required for other restore jobs.
Related Topics:
“Restoring data by using the Restore Wizard” on page 487
“Redirecting a restore job” on page 517
512 Administrator’s Guide

Searching for files to restore
Chapter 12, Restoring data
Searching for files to restore
You can search the catalog to easily find files that you want to restore, or to make sure
that you have backups of certain files. This feature also enables you to see all cataloged,
backed up versions of a file, so you can restore earlier versions if you need to. You can
also use this feature to make sure that you have multiple copies of a file before removing
it with an archive job.
To search for files to restore
1. On the Edit menu, click Search Catalogs.
2. Select which method you want to use for searching catalogs:
■ To search for a file by name and resource, select the Name and Resource tab and
complete the options described in“Name and resource options for catalog
search” on page 514.
■ To search for files by date modified, select the Date Modified tab and complete
the options described in “Date modified options for catalog search” on page 515.
3. Click Find Now.
Click Stop to halt the search, or New Search to search for another file.
The Catalog Search results window appears. All of the backed up versions of the file
appear in the Catalog Search window. Double-click the file to view the file’s
properties.
To sort the listings by filename, size, type or date modified, click the appropriate
column heading.
4. Check the version of the file you want to restore and click Apply.
5. Submit the job using the same procedures required for other restore jobs.
Backup Exec will prompt you to insert the correct media if it is not already located in a
drive.
Related Topics:
“Restoring data by using the Restore Wizard” on page 487
513

Searching for files to restore
Name and resource options for catalog search
To display the Name & Resource dialog box, on the Edit menu, click Search Catalogs.
Options on this dialog box include:
Name and resource options
Item Description
File/item name The name of the file or item that you want to find. If you do not
want to limit the search to a particular file, leave this field blank to
search all files.
You can use wildcard characters. Use a question mark (?) to
represent any single character. Use an asterisk (*) to represent any
number of characters.
For example, to include all files with the .exe extension, type *.exe.
Path The directory in which to search. If you do not want to limit the
search to a particular directory, leave this field blank to search all
directories.
To search NetWare catalogs, use a forward slash (/).
Resource The server and share in which to search. If you do not want to limit
the search to a particular resource, leave this field blank to search
all resources.
Media The cataloged media to search. You can select All Cataloged Storage
Media to search the entire catalog, or you can select individual
media to narrow the search.
Find directories Select this option to search for directories listed in the Path or File
name fields.
Include subdirectories Select this option to search all subdirectories below the directory
listed under the Location field.
514 Administrator’s Guide

Date modified options for catalog search
Chapter 12, Restoring data
Searching for files to restore
To search for files by date modified, on the Search Catalogs dialog box, select the Date
Modified tab.
Options on this dialog box include:
Date Modified options
Item Description
All Files This option enables you to search for all files.
Find all files created or
modified
Restore jobs and media libraries
Select this option to search only for files that have been created or
modified in a specified time period.
Between x/x/x and x/x/x Click this option and enter specific dates by month, day, and year.
During the previous x
month(s)
Click this option if you want to restrict the search to the previous
month or months, and then specify the number of months.
During the previous x day(s) Click this option if you want to restrict the search to the previous
day or days, and then specify the number of days.
For restore jobs, Backup Exec accesses the source media (if it is contained in the
magazine) regardless of its sequential placement in the magazine. For example, if the
data specified for a restore job resides on two media in the magazine, the media do not
have to be placed in adjacent slots for Backup Exec to restore the data. Backup Exec’s
ability to randomly access media in this manner minimizes the amount of administrator
attention required at the media server.
If Backup Exec does not find the media required for the restore job in the robotic library
or other accessible storage devices, an alert is issued requesting the media necessary to
complete the job.
515

Changing and testing resource credentials for restore jobs
Changing and testing resource credentials for restore jobs
If the logon account needed to restore data is different from the default logon account,
you can change the account through the Resource Credentials dialog box. You can also
use this dialog box to overwrite logon accounts for redirected restores. You can also
verify that a logon account can access a resource.
To change and test resource credentials for restore jobs
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Select the data you want to restore.
4. On the Properties pane, under Source, click Resource Credentials.
5. Select the resource whose logon account you want to edit.
6. Click Change.
7. Select the logon account you want to use for this selection, or click New and create a
new logon account (see “Creating a Backup Exec logon account” on page 149).
8. To verify that the logon account you are using can access the resources selected for
restore, click Test All.
While Backup Exec attempts to connect to the resources, "Testing" displays in the
Test Results column. After a test has completed, the Test Results column will display
one of the following results: Successful, Not tested, or an error message. The Not
Tested result indicates that either the logon accounts have not been tested or that
the tests have been performed but the server that contains the selection could not be
accessed
Some tests may take a long time to complete. To cancel a logon account test, click
Cancel Test.
9. Click OK.
Related Topics:
“Restoring data by setting job properties” on page 488
“Redirecting a restore job” on page 517
516 Administrator’s Guide

Redirecting a restore job
Chapter 12, Restoring data
Redirecting a restore job
Backup Exec defaults to restoring data to the resource from which the data originated. By
using the Restore Job Properties - Redirection dialog boxes, you can restore data to any
protected server, share, or Backup Exec agent workstation.
To redirect database files that are protected by licensed Backup Exec agents such as SQL
or Exchange, on the Task pane, under Destination, select the redirection option for the
agent.
To redirect a restore job
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Select the data to be restored.
4. On the Properties pane, under Destination, click File Redirection.
5. Select the appropriate options as follows:
Redirect file sets Click this option to specify target paths or resources other than
where the data was originally backed up.
Restore to drive Select the destination for the restored data. Click the Browse
button (...) to view local and network drives.
Server logon account The current logon account being used by the server appears. If
you need to use another logon account, click Change, and then
select or create another account (see “Creating a new Backup
Exec System Logon Account” on page 154). Click Clear to clear
this field.
Restore to path Specify the target path on the device listed in the Restore to
Drive field. If you want to retain the original directory structure,
make sure that the Preserve Tree option is selected in the
Restore Job Properties - Settings - General dialog box. If the
Preserve tree option is not selected, all of the data will be
restored to the path designated in this field.
Path logon account Enter the logon account required for the target path. If you need
to use another logon account, click Change, and then select or
create another account. Click Clear to clear this field.
517

Redirecting a restore job
Entering a name of an agent drive (Win98, Mac, UNIX) that does not appear in the
Restore to drive list box causes the agent restore job to fail. To resolve this, click
Browse, and open the Remote Selections window. After Backup Exec detects the
agent, the agent shares will appear in the Restore to drive list and the restore job can
be attempted again.
6. If you want to run the job now, click Run Now. Otherwise, in the Properties pane,
under Frequency, click Schedule to set the scheduling options you want to use.
Related Topics:
“Preserve tree” on page 494
“Using redirected restore for Active Directory, Active Directory Application Mode” on
page 518
“Redirecting restores for SQL” on page 1376
“Redirecting SharePoint Portal Server restore jobs” on page 1294
“Scheduling jobs” on page 368
Using redirected restore for Active Directory, Active Directory
Application Mode
When you want to install a new Windows Server 2003 Server Domain Controller into an
existing domain, the Active Directory and SYSVOL data are replicated from the existing
Domain Controller that is in the domain to the new Domain Controller. If there is a large
amount of data to be replicated or if the connection between the Domain Controllers is
slow or intermittent, the replication time can be lengthy. The Active Directory
Application Mode replication time is also affected by the amount of data to be replicated
and the connection speed. To decrease the replication time for Active Directory and
Active Directory Application Mode, you can use the Install from Media feature.
For Active Directory, you can use the Install from Media feature to perform a System
State backup of an existing Domain Controller in the domain in which you want to add a
new Domain Controller. Then, you can perform a redirected restore of the data from the
System State backup to the target Domain Controller.
For Active Directory Application Mode, you can back up data using the ADAM Writer.
Then, you can perform a redirected restore of the data from the ADAM backup to the
target system.
518 Administrator’s Guide

To install Active Directory using the Install from Media feature
Chapter 12, Restoring data
Redirecting a restore job
1. Perform a standard System State backup of an active Windows Server 2003 Server
Domain Controller that is in the target domain.
2. Transport the tape to the location of the system that will be installed into the target
Domain.
Caution The tape is not encrypted or protected. Symantec recommends that you
encrypt the tape. Use caution when transporting it to the location of the target
domain.
3. Inventory the drive where the tape is loaded.
4. Catalog the tape.
5. Perform a redirected restore of the System State backup to a temporary location on a
volume or directory on the target system. On the Properties pane, under
Destination, click File Redirection. And then select redirection options.
When you redirect restored data, Backup Exec creates a sub-directory for each type
of System State data being restored. Backup Exec creates the following
sub-directories: Active Directory, SYSVOL, Registry, Boot Files, COM+ Class
Registration Database, Certificate Server (if installed), and Cluster Quorum (if
installed).
6. To begin the Domain Controller installation, click Start on the target system, and
then click Run.
7. Type dcpromo /adv
8. Click OK.
9. Click Next when the Active Directory Installation Wizard appears.
10. Select Additional domain controller for an existing domain.
11. Click Next.
12. Select From these restored backup files, and then enter the temporary location to
which you redirected the System State data in step 5.
13. Click Next.
519

Setting defaults for restore jobs
14. Complete the Active Directory Installation Wizard by following the prompts on the
screen.
15. Complete the Domain Controller installation.
16. Reboot the system that has the new Domain Controller.
17. Delete any remaining temporary redirected System State files.
For more information, refer to your Microsoft documentation.
Related Topics:
“Creating a backup job by setting job properties” on page 349
“Inventorying media” on page 238
“Cataloging media while reviewing devices or media” on page 284
“Redirecting a restore job” on page 517
Setting defaults for restore jobs
The default options for all restore jobs are set through the Options - Set Application
Defaults dialog box. Configure these items to match the settings that you want to use for
most restore jobs. You can override these defaults while setting up a restore job, if
necessary.
To set defaults for restore jobs
1. On the Tools menu, select Options.
2. On the Properties pane, under Job Defaults, click Restore.
3. Select the appropriate options as follows:
Restore over existing files Select this option to have Backup Exec overwrite files on the
target resource that have the same name as files that are being
restored. Use this option only when you are sure that you want to
restore an older version of a file.
Skip if file exists Select this option to prevent Backup Exec from overwriting files
on the target disk with files that have the same names that are
included in the restore job.
520 Administrator’s Guide

Chapter 12, Restoring data
Overwrite the file on disk
only if it is older
Setting defaults for restore jobs
Select this option to prevent Backup Exec from restoring over
files that exist on the disk if they are more recent than the files
included in the restore job.
This option is useful if you are rebuilding a system. For example,
after installing the operating system on a crashed computer, you
could restore a previous full backup of the system without
worrying about overwriting later versions of operating system
files.
Restore corrupt files Backup Exec will automatically exclude corrupt files from the
restore process unless you select this option.
Caution Corrupt files, which appear in the restore selections
window with a red X, could be incomplete files.
Restoring corrupt files could result in corrupt data.
Symantec recommends performing redirected restore
of corrupt files rather than restoring to the original
location.
Restore junction points,
files and directories from
backup media
When this option is selected, the information for the junction
points and the files and directories to which they are linked is
restored. Selecting this option overwrites existing junction
points on your system.
If a junction point was originally backed up without the Back up
files and directories by following junction points check box
selected (see “Back up files and directories by following junction
points” on page 362), then the files and directories to which the
junction point is linked will not be restored, unless the junction
point was linked to a mounted drive that did not have an
assigned drive letter.
521

Setting defaults for restore jobs
Preserve existing junction
points and restore files and
directories from backup
media
Path on media server for
staging temporary restore
data when restoring
individual items from tape
Related Topics:
“Restoring data by setting job properties” on page 488
Select this option to restore files and directories backed up from
junction point links while retaining the system's current
junction points. This option keeps current junction points from
being overwritten with the junction point information restored
from the backup media.
When this option is selected and identical junction points or
directory names exist on both the target system and the media,
the files and directories are restored to the target system's
junction point or directory.
Note If a junction point or directory does not already exist in the
same location and with the same name as the junction
point to be restored, then the information for the junction
point and the files and directories to which they point will
be restored.
If a junction point was originally backed up without the
Back up files and directories by following junction points
check box selected (see “Back up files and directories by
following junction points” on page 362), then the files and
directories to which the junction point is linked will not be
restored, unless the junction point was linked to a
mounted drive that did not have an assigned drive letter.
This option is applicable only when you are restoring individual
items from tape-based backups of Microsoft Exchange,
SharePoint, and Active Directory. Type the path to a location on
this media server where restore data and metadata can be stored
temporarily before the individual items are restored.
Symantec recommends that you avoid using system volumes for
temporary staging locations.
522 Administrator’s Guide

Specifying the restore network
Chapter 12, Restoring data
Specifying the restore network
Backup Exec restores data using the default network information (see “Setting default
backup network and security options” on page 400). However, you can override the
default settings for a restore job. Isolating the restore job to a specific network ensures
other connected critical networks are not affected when the restore job is being
processed.
To specify the restore network
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Select the data to be restored.
4. On the Properties pane, under Settings, click Network and Security.
5. Select the appropriate options as follows:
Network Interface Select the name of the network interface card that connects the
media server to the network you want to use for the restore
network. The list includes all available network interface cards on
the media server.
If you are using the Central Admin Server Option (CASO), select the
Use the default network interface for the managed media server
option if you want CASO delegated restore jobs to be processed
using the network interface card configured as the default in the
managed media server.
Subnet Displays the 32-bit number that determines the subnet to which
the network interface card belongs.
Protocol The options are:
◆ Use any available protocol
◆ Use IPv4
◆ Use IPv6
523

Canceling a restore job
Allow use of any
available network
interface, subnet, or
protocol for remote
agents not bound to the
above network interface,
subnet, or protocol
6. Continue selecting options for the restore job.
7. If you want to run the job now, click Run Now. Otherwise, on the Properties pane,
under Frequency, click Schedule to set the scheduling options you want to use.
Related Topics:
“Restoring data by using the Restore Wizard” on page 487
“Specifying backup networks” on page 398
“Scheduling jobs” on page 368
Canceling a restore job
Canceling a restore job while it is in progress will result in unusable data, and may leave
the drive in an unusable state. You may want to redirect the restore to a noncritical
target, and 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 could leave the
system unusable.
To cancel a restore job
1. On the navigation bar, click Job Monitor.
2. Click the Job List tab.
3. In the Current Jobs Filter box, click Active jobs.
4. Select the restore job you want to cancel.
If a remote system that you selected for backup or restore is not
part of the specified restore network, select this check box to
ensure that the data from the remote system is backed up or
restored over any available network.
If you do not select this check box and you selected data from a
remote system that is not part of the specified restore network, the
job fails because Backup Exec cannot back up or restore the data
from the remote system.
Interface details Displays the Media Access Control (MAC) address, Adapter type,
Description, IP addresses, and subnet prefixes of the network
interface you selected for the restore network.
524 Administrator’s Guide

Chapter 12, Restoring data
5. In the task pane, under Active Job Tasks, click Cancel.
6. Click Yes.
Related Topics:
“Deleting scheduled jobs” on page 454
Canceling a restore job
525

Canceling a restore job
526 Administrator’s Guide

Alerts and notifications
Chapter
13
An alert is any event in Backup Exec that is important enough to display a message or
require a response from you.
Alert categories are conditions that cause alerts. Alert categories encompass many
circumstances or problems that affect the system, jobs, media, or device sources. Each
alert category can include one or more events that generate an alert. For example, a Job
Failed error can be caused for many reasons.
Each alert category has an alert type, which helps you distinguish the severity of the
alert or whether Backup Exec needs a response from you.
Alert Types
Attention required Indicates issues that require a response before the job
or operation can continue.
Error Indicates issues that affect job processing or the
integrity of your backup.
Warning Indicates conditions that may or may not cause jobs to
fail. You should monitor the conditions and take
actions to resolve them.
Information Provides status messages for the conditions that you
might want to know about.
Most alerts are enabled. However, you choose which alerts to display by editing alert
category properties.
See “Configuring alert category properties” on page 540.
527

Viewing alerts
Alerts remain in the Active Alerts pane until they receive a response. You can respond to
an alert manually or you can configure Backup Exec to respond to them automatically
after a specified length of time. Depending on the alert type, a response might not be
required, such as with informational alerts. After you respond to an alert, Backup Exec
moves it to alert history, where it remains for the length of time you specify or until you
delete it.
See “Responding to active alerts” on page 535.
You can configure Notifications to inform recipients when alerts occur. For example, you
can notify a backup administrator via email or cell phone text message when a critical
alert occurs.
See Setting up notification for alerts on page 543.
To assist with hardware troubleshooting, Backup Exec displays alerts for SCSI event ids 9
(device timeout), 11 (controller error), and 15 (device not ready).
Viewing alerts
Backup Exec has two views for alerts: Active Alerts and Alert History.
Active alerts display the alerts that are active in the system. Alert history displays alerts
that have been responded to, or the alerts that have been automatically cleared from the
system.
By default, Backup Exec displays all enabled alerts. However, when you select an alert
view, you can choose filters to limit the type of alerts that appear in the pane (see
“Filtering alerts” on page 529). You can double-click alerts in either view to see more
detailed information (see “Viewing alert properties” on page 532).
It may be necessary to view the job log to troubleshoot an alert. You can view the job log
from an active or previous alert. See Viewing the job log from an alert on page 534.
The status bar at the bottom of the screen displays an alert icon. The icon that displays in
the status bar is for the most severe type of active alert, which may not be the most
recent alert.
To view alerts
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab or the Alert History tab.
Related Topics:
“Responding to active alerts” on page 535
528 Administrator’s Guide

Filtering alerts
Chapter 13, Alerts and notifications
Viewing alerts
You can filter the alerts that appear in the Active Alerts or Alert History views. This is
useful when you have many alerts and you want to only view specific alert types. You can
also filter the Alert History by alert types to expedite finding alerts that were generated
in the past.
To filter alerts
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab or the Alert History tab.
3. In the Active Alerts or Alert History Filter box, click the option for the alerts that you
want to view.
Attention required
alerts
Lists alerts that require a response.
Error alerts Lists system, job, media, and device error alerts.
Warning alerts Lists system, job, media, and device warning alerts.
Information alerts Lists system, job, media, and device information alerts.
System alerts Lists the alerts that originated from the system.
Media alerts Lists the alerts that originated from media.
Device alerts Lists the alerts that originated from devices.
Job alerts Lists the alerts that originated from a job.
Media server alerts Displays only if you have the Central Admin Server Option
installed. After you select this option, select the media server for
which you want to view alerts. Select All media servers to view
alerts for all media servers.
Custom Filter Lists custom alerts filters.
Related Topics:
“Responding to active alerts” on page 535
“Creating custom filters for alerts” on page 530
529

Viewing alerts
Creating custom filters for alerts
You can view various types of alerts and the sources that cause them by creating custom
filters. For example, you can create a custom filter that displays only Attention Required
and Error Alerts that are generated from Devices and Media sources.
To create custom filters for alerts
1. On the navigation bar, click Alerts.
2. On the Active Alerts tab or the Alert History tab, in the Filter list, click .
3. Type a unique name and a description for the filter.
4. On the Properties pane, under Criteria, click Alert Type.
5. Check Enable this filter.
6. Uncheck the checkboxes for the alert types that you do not want to display.
7. On the Properties pane, under Criteria, click Source.
8. Check Enable this filter.
9. Uncheck the checkboxes for the sources that you do not want to filter on.
10. Click OK.
Related Topics:
“Editing custom filters for alerts” on page 531
“Deleting custom filters for alerts” on page 531
“Filtering alerts” on page 529
530 Administrator’s Guide

Editing custom filters for alerts
To edit a custom filter for alerts
1. On the navigation bar, click Alerts.
Chapter 13, Alerts and notifications
Viewing alerts
2. On the Active Alerts tab or the Alert History tab, in the Filter list, highlight the
custom filter that you want to edit or delete.
Edit and Delete buttons appear at the far right of the highlighted selection.
3. Click the Edit button and configure properties in the Edit Alert Custom Filter dialog
box.
4. Click OK.
Related Topics:
“Creating custom filters for alerts” on page 530
“Filtering alerts” on page 529
Deleting custom filters for alerts
To delete a custom filter for alerts
1. On the navigation bar, click Alerts.
2. On the Active Alerts tab or the Alert History tab, in the Filter list, highlight the
custom filter that you want to edit or delete.
Edit and Delete buttons appear at the far right of the highlighted selection.
3. Click the Delete button.
4. Click Yes when you are prompted to confirm that you want to delete the filter.
Related Topics:
“Creating custom filters for alerts” on page 530
531

Viewing alerts
Viewing alert properties
Alert properties provide detailed information about each alert. In addition to the alert
properties information, you can view category properties. If the alert is in the alert
history, you can view response information.
To view alert properties
1. On the navigation bar, click Alerts.
2. Click the Active Alerts or Alert History tab.
3. Select the alert from either the Active Alerts or Alert History pane.
4. Under General Tasks in the task pane, click Properties.
The Alert Properties dialog box provides the following items:
Alert Properties
Category The title of the alert.
Type The severity of the alert. The type helps you determine how quickly
you want to respond. Following are the alert types:
◆ Errors
◆ Warnings
◆ Information
◆ Attention Required
Server The name of the media server on which the alert occurred.
Device The name of the device on which the alert occurred.
Job Name The name of the job associated with the alert.
Time alert received The date and time the alert occurred.
Source The cause of the alert. Alerts can originate from one of the
following sources:
◆ System
◆ Job
◆ Media
◆ Device
532 Administrator’s Guide

SNMP trap
Identification
Properties of Category
5. After you view the alert properties, click OK.
Chapter 13, Alerts and notifications
Viewing alerts
The SNMP message from Backup Exec regarding status and error
conditions. SNMP must be installed to view this message.
Enabled The alert is activated or disabled.
Send notifications Notifications are enabled or cleared for the alert. Recipients must
be configured in order to use this option.
Send SNMP
notifications
SNMP notifications are enabled or cleared for the alert. SNMP must
be installed to use this option.
Record in event log The alert is entered into the Windows Event Viewer. The Windows
Event log displays all the property information for the alert.
If a link appears in the Windows Event log you can search the
Symantec Technical Support web site for information about the
Event ID.
Event ID The alert’s ID in the Windows Event Viewer.
Automatically clear
after x
days/hours/minutes
The length of time the alert remains active before it is moved to the
Alert history.
For attention required alerts, you can set a default response. For
more information, see the documentation for Backup Exec Utility.
Respond with This option is available only for the Media Overwrite, Media
Remove, Media Insert, Library Insert alert categories. The response
Backup Exec automatically sends.
Include job log Sends the job log to the recipient configured for notification. This
option can only be used for recipients that are configured for email
or printer notification.
Response (Alert History Properties)
User who responded The user ID that responded to the alert.
Response machine The name of the computer from which the user responded.
Time user responded The date and time the user responded to the alert.
User response The response the user entered for the alert.
533

Viewing alerts
Related Topics:
“Configuring alert category properties” on page 540
“Configuring recipients” on page 547
“About SNMP notification” on page 567
Viewing the job log from an alert
The job log provides detailed job information, device and media information, job options,
file statistics, and job completion status for completed jobs. You can view the job log for
jobs that have generated alerts from either Active alerts or Alert history, depending on
where the alert is located.
To view the job log
1. On the navigation bar, click Alerts.
2. Click the Active Alerts or Alert History tab.
3. Select the alert for which you want to view the job log from either the Active Alerts
or Alert History pane.
4. Perform one of the following:
■ If the alert is in Active alerts, under Alert Tasks in the task pane, click View job
log.
■ If the alert is in the Alert history, under Alert History Tasks, click View job log.
5. To search for a specific word or phrase, click Find. Type the text you want to find,
and then click Find Next.
Be sure to expand all sections of the job log. The Find feature searches only the
expanded sections of the job log.
6. To print the job log, click Print. You must have a printer attached to your system and
configured in order to print the log.
To save the job log as an .html or .txt file, click Save As and then select the file name,
file location, and file type.
7. After you have finished viewing the job log, click OK.
Related Topics:
“Viewing and changing completed jobs” on page 455
534 Administrator’s Guide

Responding to active alerts
Chapter 13, Alerts and notifications
Responding to active alerts
You can respond to active alerts and depending on the alert condition, continue or cancel
the operation. By default, Backup Exec displays all enabled alerts. If you have set View
Filters (see “Viewing alerts” on page 528), only those alerts that are selected appear.
You can configure automatic responses for alert categories. For more information, see
“Configuring automatic responses for alert categories” on page 536.
To respond to an active alert
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Select the alert to which you want to respond, and then under Alert Tasks in the task
pane, click Respond.
Note If you have more than one alert selected, click Respond OK to all to clear the
selected alerts to the alert history. The alerts must have an OK response available
to be automatically cleared.
The alert dialog box appears.
If you click Close, you will close the dialog box, but the alert remains active. To clear
the alert and move it to the alert history, you must select a response such as OK, Yes,
No, or Cancel from the alert dialog box.
The alert dialog box provides the following information:
Category Name The title of the alert.
Message Describes the event that caused the alert and provides
suggestions for responding to the alert.
Server name The name of the computer on which the alert occurred.
Device name The name of the device on which the alert occurred.
Job name The job associated with the alert.
Time The date and time the alert occurred.
535

Responding to active alerts
Automatically display new
alerts
Automatically respond to
and clear all alerts in the
category
4. Click a response for the alert.
After the alert condition is resolved, the alert is moved to the Alert history.
Related Topics:
“Clearing informational alerts from the Active Alerts pane” on page 539
“Enabling or disabling alerts from the Active Alerts pane” on page 542
Configuring automatic responses for alert categories
Using the Alert Autoresponse Wizard, you can:
■ Configure the length of time to keep alerts active
Select this check box to have alerts automatically appear in the
Backup Exec console when they are sent. If you do not select this
option, you must respond to alerts through the Active Alerts
pane. For more information, see “Changing default preferences”
on page 139.
■ Specify the response that you want to send for alerts
You can use the Alert Autoresponse Wizard for the following alert categories:
Alert categories for the Alerts Autoresponse Wizard
Alert category Description
To provide automatic responses for this alert select the amount
of time to wait before a response is provided and select the
response. For more information, see “Configuring automatic
responses for alert categories” on page 536.
Library Insert The Library Insert alert is a request to insert overwritable media into the
robotic library by using the import command.
Media Insert The Media Insert alert is a request to insert overwritable media into a tape
drive. Most tape drives provide status to Backup Exec when media is
inserted, which clears the alert. Other tape drives do not generate this
status and the alert must be cleared with a response.
Media Overwrite The Media Overwrite alert is displayed when Media Overwrite Protection is
configured to prompt before overwriting media.
536 Administrator’s Guide

Alert categories for the Alerts Autoresponse Wizard
Alert category Description
Chapter 13, Alerts and notifications
Responding to active alerts
Media Remove The Media remove alert is a request to acknowledge that media has been
removed from a tape drive. Most tape drives provide status to Backup Exec
when media is removed, which clears the alert. Other tape drives do not
generate this status and the alert must be cleared with a response.
Automatic responses are useful if you routinely get these alerts and your responses to
the alerts are always the same.
To configure automatic responses for alert categories
1. On the Tools menu, click Wizards>Alert Autoresponse Wizard.
2. On the Welcome to the Alert Autoresponse Wizard panel, click Next.
3. On the Configure Library Insert Category panel, select the appropriate options as
follows:
Automatically clear after Select the amount of time to display the alert before Backup Exec
clears it and moves it to the alert history. When this job queues
again, the alert reappears on the Active Alerts tab and clears
automatically after the time interval elapses.
Respond with This option is not available for the Library Insert alert category.
Do not autorespond Select this to keep this alert on the Active Alerts tab until media is
added to the library.
4. Click Next.
5. On the Configure Media Insert Category panel, select the appropriate options as
follows:
Automatically clear after Select the amount of time to display the alert before Backup
Exec clears it.
537

Responding to active alerts
Respond with Do one of the following:
6. Click Next.
7. On the Configure Media Overwrite Category panel, select the appropriate options as
follows:
8. Click Next.
9. On the Configure Media Remove Category panel, select the appropriate options as
follows:
10. Click Next.
◆ Select Yes to acknowledge that the media was inserted.
◆ Select No to retry the media insert operation on another tape
drive (if multiple tape drives were selected for the job).
◆ Select Cancel to cancel this occurrence of the job.
Do not autorespond Select this to keep this alert on the Active Alerts tab until media is
added to the tape drive.
Automatically clear after Select the amount of time to display the alert.
Respond with Do one of the following:
◆ Select Yes to overwrite the media automatically.
◆ Select No to try other media.
◆ Select Cancel to cancel the occurrence of this job.
Do not autorespond Select this to keep this alert on the Active Alerts tab until you
acknowledge the alert by clicking OK.
Automatically clear after Select the amount of time to display the alert on the Active Alerts
tab before Backup Exec clears it and moves it to Alert History.
Respond with This option is not available for the Media Remove alert category.
Do not autorespond Select this to keep this alert on the Active Alerts tab until you
acknowledge the alert by clicking OK.
11. Read the Alert Autoresponse Summary panel, and then click Next.
538 Administrator’s Guide

Chapter 13, Alerts and notifications
Responding to active alerts
12. On the Completing the Alert Autoresponse Wizard panel, click Finish.
Settings that you configure by using this wizard are overridden if the alert category
properties are reconfigured. See “Configuring alert category properties” on page 540.
Clearing informational alerts from the Active Alerts pane
Informational alerts can originate from the system, jobs, media, or devices. The alerts
are set by default to move to the alert history after 24 hours; however, some
informational alerts appear frequently and fill the Active alerts pane. You may want to
clear these informational alerts to the Alert history pane before they are automatically
moved by the system.
To clear informational alerts from the active alerts pane
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Alert Tasks in the task pane, click Clear all informational alerts.
All the informational alerts in the Active alerts pane are cleared to the Alert
history.
539

Configuring alert category properties
Configuring alert category properties
You can set up alert categories to enable or disable alerts and determine actions such as
notification and responses that will take place when an alert occurs.
For a quick way of enabling and disabling alerts without configuring other options, see
Enabling or disabling alerts from the Active Alerts pane on page 542
Most alerts are enabled by default, however the following alert categories are initially
disabled:
■ Backup job contains no data
■ Job Start
■ Job Success
Each time you change the alert configuration, it is recorded in the audit log. You can view
the audit log at any time to view the changes made to the alert category.
To view or change alert category properties
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Alert Tasks in the task pane, click Configure alert categories.
4. Under Alert Categories, click the alert for which you want to view or change
properties.
Tip You can change the options for more than one alert category simultaneously. To
select consecutive alert categories, click the first alert, press and hold down
, and then click the last item. To select alert categories that are not
consecutive, press and hold down , and then click each item.
5. Under Category Properties, select the appropriate options as follows:
Category name The title of the alert. This property can be viewed, but not edited.
Enable alerts for this
category
Select this check box to activate or disable the alert. You cannot
disable alert types such as error and attention required.
You can also enable an alert category from the task pane. For
more information, see “Enabling or disabling alerts from the
Active Alerts pane” on page 542.
540 Administrator’s Guide

Send notifications to
selected recipients
Include job log with a
notification to an email or
printer recipient
Chapter 13, Alerts and notifications
Configuring alert category properties
Select this check box to send notifications when an alert occurs.
You must have recipients configured to use this option.
To configure recipients to receive the notification, click
Recipients. For more information, see “Configuring recipients”
on page 547.
Select this check box to send the job log to the recipient
configured for notification. The recipient must be configured to
receive email or printer notifications.
Send SNMP Notifications Select this check box to enable SNMP notifications. SNMP must
be installed to use this option. For more information, see “About
SNMP notification” on page 567.
Record event in the
Windows Event Log
Automatically clear after x
days/hours/minutes
Select this check box to enter the alert into the Windows Event
Viewer. The Windows Event log displays all the property
information for the alert.
If a link appears in the Windows Event log you can search the
Symantec Technical Support web site for information about the
Event ID.
Select this check box to enter the number of minutes, hours, or
days you want the alert to remain active before it is moved to the
Alert history.
For attention required alerts, you can set up automatic
responses. For more information, see “Configuring automatic
responses for alert categories” on page 536.
Respond with This option is available only for the Media Overwrite, Media
Remove, Media Insert, Library Insert alert categories. Select the
response that you want Backup Exec to send automatically. The
choices are Cancel, No, Yes or OK.
6. Click Apply to apply the properties to the alert and continue configuring additional
alerts.
7. Click OK to exit the Configure Alert Categories dialog box.
Related Topics:
“Assigning recipients to alert categories for notification” on page 564
541

Deleting alerts from the alert history
Enabling or disabling alerts from the Active Alerts pane
You can quickly enable or disable alerts from the task pane instead of configuring them
in the Configure Alert Categories dialog box (see “Configuring alert category properties”
on page 540).
To enable or disable an alert from the active alerts pane
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. On the Active Alerts pane, select the alert that you want to enable or disable.
4. Under Alert Tasks in the task pane, click Alert category enabled.
The alert will be enabled or disabled, depending on the current setting. The error and
attention required alert types cannot be disabled.
Deleting alerts from the alert history
Alerts that have been responded to or automatically cleared from the system are kept in
the Alert history. All alerts are displayed, except for entries that have been filtered and
selected for exclusion. The alerts remain in the Alert history for the length of time you
set in the database maintenance option or until you delete the alert.
To delete an alert from the alert history
1. On the navigation bar, click Alerts.
2. Click the Alert History tab.
3. Select the alert you want to delete, and then under Alert History Tasks in the task
pane, click Delete.
4. Click Yes to confirm that you want to delete the alert.
The alert is removed from the Backup Exec database.
542 Administrator’s Guide

Setting up notification for alerts
Chapter 13, Alerts and notifications
Setting up notification for alerts
You can configure Backup Exec to notify recipients when alerts occur. The following
notification methods are available:
SMTP email or phone
text messaging
MAPI email
VIM email
Pager
You can use printer and Net Send notification methods, but they do not require
configuration before creating and assigning recipients. You can use one or more methods
for each recipient.
To set up notification
1. Configure the method you want to use to notify the recipient.
2. Configure recipients. Recipients are individuals, computer consoles, printers, or
groups.
3. Assign the recipients to alerts or jobs for notification.
Configuring SMTP for email or mobile phone text message
notification
You must have an SMTP-compliant email system such as a POP3 mail server to receive
alert notification messages using the SMTP notification method.
To configure the SMTP email or mobile phone notification method
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
See “Configuring SMTP for email or mobile phone text message
notification” on page 543.
See “Configuring MAPI email for notification” on page 545.
See “Configuring VIM email for notification” on page 546.
See “Configuring a pager for alert notification” on page 546.
3. Under Notification Tasks in the task pane, click Configure email and pagers.
543

Setting up notification for alerts
4. Click the SMTP Configuration tab and select the appropriate options as follows:
Enable Select this check box to activate the notification method.
SMTP mail server Type the name of an SMTP mail server on which you have a valid
user account. Backup Exec will not check the server name or the
email address for validity.
SMTP port Defaults to a standard SMTP port. In most cases, the default
should not have to be changed.
Sender name The sender’s name. Spaces and special characters are allowed
here.
Sender email address Type the email address of the user from whom the notification
message will be sent. The email address should contain a name
that identifies the user to the mail server, followed by an at sign
(@) and the host name and domain name of the mail server. For
example, john.smith@company.com.
For a mobile phone: type the number of the mobile phone in
email address format. For example:
1231231234@mymobile.com. Check with the mobile service
provider for the correct email address for text messages.
Enable SMTP
Authentication
5. Click OK.
Related Topics:
“Configuring recipients” on page 547
Select this check box to enable SMTP authentication, which logs
the sender in to the mail server prior to sending the SMTP
notification.
For SMTP authentication to work properly, anonymous access
and TLS encryption must be disabled on the Exchange server.
SMTP server login The login name of the sender on the SMTP mail server.
Sender password The sender’s password on the SMTP mail server. Make sure you
provide a confirmation password. Backup Exec will not check the
server name or the email address for validity.
544 Administrator’s Guide

Configuring MAPI email for notification
Chapter 13, Alerts and notifications
Setting up notification for alerts
You must have a MAPI-compliant email system such as Microsoft Exchange to receive
alert notification messages using the MAPI notification method.
Note If you install Outlook after installing Backup Exec, you must stop and restart the
Backup Exec services for MAPI email notification to work and in order to save the
MAPI configuration settings.
To configure MAPI alert notification
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Configure email and pagers.
4. Click the MAPI Configuration tab and select the appropriate options as follows:
Enable Select this check box to activate the notification method.
Mail server name Type the name of the Exchange server. You must use an
Exchange server to which the Backup Exec service account has
access. For more information, see “Changing Windows security”
on page 75.
Mailbox name to send
email from
5. Click OK.
Related Topics:
“Configuring recipients” on page 547
Type the mailbox from whom the notification message will be
sent, for example, John Smith. The name appears in the From
field in the message and does not require a full address.
Note The Backup Exec services must be running under a
domain account that has rights to the Exchange mailbox
used for MAPI notification in order to save the MAPI
configuration settings.
545

Setting up notification for alerts
Configuring VIM email for notification
You must have a VIM (Lotus Notes) compliant email system to receive alert notification
messages using the VIM notification method.
To configure VIM alert notification
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Configure email and pagers.
4. Click the VIM Configuration tab and select the appropriate options as follows:
Enable Select this check box to activate the notification method.
Notes client directory Type the path of the directory in which the Notes client is
located.
Mail password Type the password that enables you to connect to the Notes
client.
Confirm mail password Re-type the password that enables you to connect to the Notes
client.
5. Click OK.
Related Topics:
“Configuring recipients” on page 547
Configuring a pager for alert notification
You can configure Backup Exec to page you with alert notification messages. A modem is
required for pager notification. Make sure that the modem can communicate properly
with your paging service. Before setting up pager notification, contact your paging
service for information about modems compatible with the service.
To configure a pager for alert notification
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
546 Administrator’s Guide

Chapter 13, Alerts and notifications
Configuring recipients
3. Under Notification Tasks in the task pane, click Configure email and pagers.
The Notification Configuration Properties dialog box appears.
4. Click the Pager Configuration tab and select Enable to activate this alert notification
method.
5. Select a modem from the Select a modem for sending pages option.
Only modems recognized in Windows appear in the list box.
6. Click OK.
Related Topics:
“Configuring recipients” on page 547
Configuring recipients
Recipients are individuals with a predefined notification method, computer consoles,
printers, or groups. Recipient configuration consists of selecting a notification method
and defining notification limits. After you create entries for the recipients, you can
assign them to alerts, jobs, or selection lists. The following types of recipients can be
configured for notifications:
Person
Net Send
Printer
Group
An individual that has a predefined method of notification such as SMTP,
MAPI, or VIM email, or a pager. You must configure the notification
method before you can enable it for the recipient.
A computer that serves as a notification recipient.
A specific printer to which notifications can be sent.
A group of one or more recipients, including person recipients, Net Send
recipients, and other groups.
Related Topics:
“Configuring SMTP for email or mobile phone text message notification” on page 543
“Assigning recipients to alert categories for notification” on page 564
“Assigning notification recipients for completed jobs” on page 565
“About selection lists” on page 327
547

Configuring recipients
Configuring SMTP email or mobile phone text messaging for a
person recipient
You can configure a person recipient to receive SMTP email or mobile phone text
message notification messages if you have configured the SMTP notification method.
To configure SMTP email or mobile phone text messaging for a person recipient
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Configure recipients.
The Configure Recipients dialog box appears.
4. Click New, click Person in the Recipient Type dialog box, and then click OK.
5. In the Name field, type the name of the recipient that you want to configure.
6. Click the SMTP Mail tab and select the appropriate options as follows:
Enable Select this check box to activate this notification method for the
recipient.
Address For email: type the email address of the recipient to whom the
notification message will be sent. For example,
john.smith@company.com.
For a mobile phone: type the number of the mobile phone in
email address format. For example:
1231231234@mymobile.com. Check with the mobile service
provider for the correct email address for text messages.
Test Enables you to test the notification configuration for the
recipient.
Limit the number of notifications sent
Enable Select this check box to activate the option.
548 Administrator’s Guide

Notify me a maximum of x
times within x minutes
Reset the notification
limits after x minutes
Limit when notifications can be sent
7. Click OK.
Related Topics:
“Editing recipient notification methods” on page 562
“Editing recipient notification properties” on page 562
“Assigning recipients to alert categories for notification” on page 564
Chapter 13, Alerts and notifications
Configuring recipients
Type the total number of notifications you want sent to the
recipient for all alerts generated within the specified number of
minutes. After the specified number of notifications have been
sent, additional notifications are not sent until the specified
minutes have been reached. The maximum number of minutes
that can be set is 1440, which is the number of minutes in a day.
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications sent is reset
to zero.
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
notification for recipients” on page 561.
549

Configuring recipients
Configuring MAPI mail for a person recipient
You can configure a person recipient to receive MAPI email notification messages if you
have configured the MAPI notification method.
To configure MAPI mail for a person recipient
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Configure recipients.
The Configure Recipients dialog box appears.
4. Click New, click Person in the Recipient Type dialog box, and then click OK.
5. In the Name field, type the name of the recipient that you want to configure.
6. Click the MAPI Mail tab and select the appropriate options as follows:
Enable Select this check box to activate this notification method for the
recipient.
Mailbox Type the email address or mailbox name of the recipient to
whom the notification message will be sent. For example,
john.smith@company.com or John Smith.
Test Enables you to test the notification configuration for the
recipient.
Limit the number of notifications sent
Enable Select this check box to activate the option.
Notify me a maximum of x
times within x minutes
Type the total number of notifications you want sent to the
recipient for all alerts generated within the specified number of
minutes. After the specified number of notifications have been
sent, additional notifications are not sent until the specified
minutes have been reached. The maximum number of minutes
that can be set is 1440, which is the number of minutes in a day.
550 Administrator’s Guide

Reset the notification
limits after x minutes
Limit when notifications can be sent
7. Click OK.
Related Topics:
“Editing recipient notification methods” on page 562
“Editing recipient notification properties” on page 562
“Assigning recipients to alert categories for notification” on page 564
Chapter 13, Alerts and notifications
Configuring recipients
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications sent is reset
to zero.
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
notification for recipients” on page 561.
551

Configuring recipients
Configuring VIM mail for a person recipient
You can configure a person recipient to receive VIM email notification messages if you
have configured the VIM notification method.
To configure VIM mail for a person recipient
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Configure recipients.
The Configure Recipients dialog box appears.
4. Click New, click Person in the Recipient Type dialog box, and then click OK.
5. In the Name field, type the name of the recipient that you want to configure.
6. Click the VIM Mail tab and select the appropriate options as follows:
Enable Select this check box to activate this notification method for the
recipient.
Address Type the email address of the recipient to whom the notification
message will be sent. For example, JohnSmith@company.com.
Test Enables you to test the notification configuration for the
recipient.
Limit the number of notifications sent
Enable Select this check box to activate the option.
Notify me a maximum of x
times within x minutes
Reset the notification
limits after x minutes
Type the total number of notifications you want sent to the
recipient for all alerts generated within the specified number of
minutes. After the specified number of notifications have been
sent, additional notifications are not sent until the specified
minutes have been reached. The maximum number of minutes
that can be set is 1440, which is the number of minutes in a day.
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications sent is reset
to zero.
552 Administrator’s Guide

Limit when notifications can be sent
Related Topics:
“Editing recipient notification methods” on page 562
“Editing recipient notification properties” on page 562
“Assigning recipients to alert categories for notification” on page 564
Configuring a pager for a person recipient
Chapter 13, Alerts and notifications
Configuring recipients
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
notification for recipients” on page 561.
You can configure a person recipient to receive notification messages by pager if you
have configured the pager notification method.
To configure a pager for a person recipient
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Configure recipients.
The Configure Recipients dialog box appears.
4. Click New, click Person in the Recipient Type dialog box, and then click OK.
5. In the Name field, type the name of the recipient that you want to configure.
6. Click the Pager tab and select the appropriate options as follows:
Enable Select this check box to activate this notification method for the
recipient.
Carrier Phone Type the area code and phone number to access the paging
service provider’s modem. The paging service number may be
different from the number you enter to manually enter a page.
553

Configuring recipients
Country/region name and
code
Enter the country or region name and country code in which the
pager is located.
Pager Pin Type the pager identification number provided by the paging
service provider. You will have a pin if you use TAP services and
in most cases, the number is the last seven digits of the pager’s
phone number.
Advanced Pager setup options
Advanced Enables you to configure additional settings for the pager. For
more information about the options, see “Click Advanced to
configure advanced pager setup options in the Advanced Pager
Information dialog box:” on page 555.
Test Enables you to test the notification configuration for the
recipient.
Limit the number of notifications sent
Enable Select this check box to activate the option.
Notify me a maximum of x
times within x minutes
Reset the notification
limits after x minutes
Limit when notifications can be sent
Type the total number of notifications you want sent to the
recipient for all alerts generated within the specified number of
minutes. After the specified number of notifications have been
sent, additional notifications are not sent until the specified
minutes have been reached. The maximum number of minutes
that can be set is 1440, which is the number of minutes in a day.
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications sent is reset
to zero.
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
notification for recipients” on page 561.
554 Administrator’s Guide

Chapter 13, Alerts and notifications
Configuring recipients
7. Click Advanced to configure advanced pager setup options in the Advanced Pager
Information dialog box:
Pager Configuration
Password Type the password for the pager, if one is required.
Message Length Type the maximum number of characters you want to use for
messages. The number is determined by the paging service
provider.
Retrys Type the number of times you want the paging service provider to
retry the page. The number is determined by the paging service
provider.
Pager type
Numeric Select this option if you are configuring a pager that accepts only
numbers.
Alpha-numeric Select this option if you are configuring a pager that accepts letters
and numbers.
Modem Configuration
Modem Baud Rate Select the speed of the modem. The speeds that appear are limits
set by the paging service; select the appropriate speed regardless of
the modem speed rating.
Data bits, Parity, Stop
bit
Select the communication protocol. In most cases, you should use
the Windows default.
8. Click OK to save the settings in the Advanced Pager Information dialog box, and then
click OK to save the pager configuration settings.
Related Topics:
“Editing recipient notification methods” on page 562
“Editing recipient notification properties” on page 562
“Assigning recipients to alert categories for notification” on page 564
555

Configuring recipients
Configuring a net send recipient
You can configure Net Send to send notification messages to a target computer or user.
Note If the target computer has Internet pop-up advertisement blocking software
installed, the Net Send notification message will not display.
To configure a net send recipient
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Configure recipients.
The Configure Recipients dialog box appears.
4. Click New, click Net Send in the Recipient Type dialog box, and then click OK.
5. Select the appropriate options from the Net Send Recipient Properties dialog box:
Name Type the recipient for whom you are configuring the notification.
Target Computer or User
Name
Type the name of the computer or user to whom you are sending
the notification. You should enter a computer rather than a user
because the Net Send message will fail if the user is logged off
the network.
Note If the target computer has Internet pop-up advertisement
blocking software installed, the Net Send notification
message will not display.
All Computers Select the check box to send the notification to all the computers
in the network.
Test Enables you to test the notification configuration for the
recipient.
556 Administrator’s Guide

Limit the number of notifications sent
Enable Select this check box to activate the option.
Notify me a maximum of x
times within x minutes
Reset the notification
limits after x minutes
Limit when notifications can be sent
6. Click OK.
Related Topics:
“Editing recipient notification methods” on page 562
“Editing recipient notification properties” on page 562
“Assigning recipients to alert categories for notification” on page 564
Chapter 13, Alerts and notifications
Configuring recipients
Type the total number of notifications you want sent to the
recipient for all alerts generated within the specified number of
minutes. After the specified number of notifications have been
sent, additional notifications are not sent until the specified
minutes have been reached. The maximum number of minutes
that can be set is 1440, which is the number of minutes in a day.
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications sent is reset
to zero.
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
notification for recipients” on page 561.
557

Configuring recipients
Configuring a printer recipient
You can select installed printers as a notification method for recipients; however, fax
printer devices are not supported by Backup Exec. Only printers that were configured
using the same username and password as the Backup Exec service account can be
selected.
To configure a printer recipient
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Configure recipients.
The Configure Recipients dialog box appears.
4. Click New, click Printer in the Recipient Type dialog box, and then click OK.
5. Click Printer, and then click OK.
6. Select the appropriate options in the Printer Recipient Properties dialog box:
Name Type the recipient for whom you are configuring the notification.
You cannot use a fax printer device to receive the notification.
Target Printer Select the name of the printer to which the notification message
will be sent.
Test Enables you to test the notification configuration for the
recipient.
Limit the number of notifications sent
Enable Select this check box to activate the option.
Notify me a maximum of x
times within x minutes
Type the total number of notifications you want sent to the
recipient for all alerts generated within the specified number of
minutes. After the specified number of notifications have been
sent, additional notifications are not sent until the specified
minutes have been reached. The maximum number of minutes
that can be set is 1440, which is the number of minutes in a day.
558 Administrator’s Guide

Reset the notification
limits after x minutes
Limit when notifications can be sent
Related Topics:
“Editing recipient notification methods” on page 562
“Editing recipient notification properties” on page 562
“Assigning recipients to alert categories for notification” on page 564
Chapter 13, Alerts and notifications
Configuring recipients
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications sent is reset
to zero.
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
notification for recipients” on page 561.
559

Configuring recipients
Configuring a group recipient
Groups are configured by adding recipients as group members. A group contains one or
more recipients and each recipient receives the notification message. Members of the
group can be a combination of individual persons, computers, printers, or other groups.
To configure a group recipient
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Configure recipients.
The Configure Recipients dialog box appears.
4. Click New, click Group in the Recipient Type dialog box, and then click OK.
5. In the Group Name field, type the group for whom you are configuring the
notification.
6. To add members to the group, select recipients from the All Recipients list, and then
click Add to move them to the Group Members list.
7. To remove members from the group, select recipients from the Group Members list,
and then click Remove to move them to the All Recipients list.
8. When you have completed the group, click OK.
The new group can be added to other groups.
Related Topics:
“Editing recipient notification methods” on page 562
“Editing recipient notification properties” on page 562
“Assigning recipients to alert categories for notification” on page 564
560 Administrator’s Guide

Scheduling notification for recipients
Chapter 13, Alerts and notifications
Configuring recipients
During the recipient configuration process, you can enable the Limit when notifications
can be sent option to select the times of the day and the days of the week the recipient is
available to receive the notification messages. You can modify the schedule after the
recipient is configured by editing recipient notification properties.
To configure the notification schedule for recipients during recipient configuration
1. On the Recipient Properties dialog box, under the Limit when notifications can be
sent group box, click Enable to activate the option.
Note To access the Recipient Properties dialog box, on the navigation bar, click Alerts.
On the task pane, under Notification Tasks, click Configure recipients. Click New
to create a new recipient or select an existing recipient and then click Properties.
2. Click Schedule.
3. Clear the Include work days check box to exclude Monday through Friday from 8
A.M. to 6 P.M.
4. Clear the Include weeknights check box to exclude Monday through Friday from 6
P.M. to 8 A.M.
5. Clear the Include weekends check box to exclude Saturday and Sunday, 24 hours a
day.
6. You can select any combination of Include work days, Include weeknights, or
Include weekends, or click any single hour of the chart to select or clear that hour.
7. After selecting the days and times you want, click OK.
561

Configuring recipients
Editing recipient notification properties
You can edit the recipient notification properties at any time and change the recipient
information, such as an email address, telephone number or schedule.
To edit the recipient notification properties
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Configure recipients.
The Configure Recipients dialog box appears.
4. Select the recipient you want to edit, and then click Properties.
The Recipient Properties dialog box for the type of recipient you selected appears.
5. Edit the properties for the selected recipient.
You can edit any of the properties except for the recipient name in the Name field. To
modify the recipient name, you must create a new recipient, and then delete the old
one.
6. Click OK.
Editing recipient notification methods
You can configure new notification methods or edit existing notification methods after
you configure recipients.
To edit notification methods
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Assign recipients to alert
categories.
The Alert Notification Setup dialog box appears.
4. Under Recipients, click Settings.
The Notification Configuration Properties dialog box appears.
562 Administrator’s Guide

Chapter 13, Alerts and notifications
Configuring recipients
5. Edit notification properties for the following types of notification methods:
■ SMTP Configuration. See “Configuring SMTP for email or mobile phone text
message notification” on page 543.
■ MAPI Configuration. See “Configuring MAPI email for notification” on page 545.
■ VIM Configuration. See “Configuring VIM email for notification” on page 546.
■ Pager Configuration. Click Enable to activate or clear the notification method,
and then select a modem from the Configured Modems list.
6. Click OK.
Removing recipients
You can delete recipients that do not want to receive notification messages; however, the
recipient is permanently removed upon deletion. If you want to keep the recipient, but do
not want the recipient to receive notifications, clear the Enable check box in the
recipient properties.
To remove a recipient
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Configure recipients.
4. Select the recipient you want to delete, and then click Remove.
563

Assigning recipients to alert categories for notification
Assigning recipients to alert categories for notification
You can assign recipients to alert categories to receive notification messages. When an
alert occurs, all the recipients assigned to the alert category receive the notification
message. You can also clear a recipient from an alert category and edit properties for the
alert categories during the alert notification setup.
To assign a recipient to an alert category
1. On the navigation bar, click Alerts.
2. Click the Active Alerts tab.
3. Under Notification Tasks in the task pane, click Assign recipients to alert
categories.
4. Under Alert Categories, select the alert category to which you want to assign
recipients.
5. Under Recipients, select the recipients you want to receive notification messages for
the alert category, or click Check All to select all the recipients in the list.
6. Click OK.
To clear a recipient assigned to an alert category
❖ Under Alert Categories, select the alert category from which you want to clear the
recipient and then under Recipients, click the check box for the recipient you want
to clear.
Related Topics:
“Configuring alert category properties” on page 540
“Configuring SMTP for email or mobile phone text message notification” on page 543
“Configuring recipients” on page 547
564 Administrator’s Guide

Chapter 13, Alerts and notifications
Assigning notification recipients for completed jobs
Assigning notification recipients for completed jobs
You can assign recipients to be notified when a job completes or when a job containing a
specific selection list completes.
You can configure new recipients or edit existing recipients and add a job log to the
notification message; however, the job log can only be added for recipients configured for
email or printer notification.
To assign notification recipients for completed jobs
1. Do one of the following:
■ To select recipients to be notified when a job completes, edit the job’s properties.
In the job properties dialog box, on the Properties pane, under Settings, click
Notification.
■ To select recipients to be notified when a job containing a specific selection list
completes, on the navigation bar, click Job Setup. Then, on the Backup Selection
Lists pane, select the selection list that you want to add notification to.
Under General Tasks in the task pane, click Properties, and then under Source,
click Selection List Notification.
2. Select the recipients you want to assign to the job or selection list.
3. If the recipient is using an email or printer notification method, click Include job log
with a notification to an email or printer recipient.
4. You can continue selecting other options from the Properties pane.
To configure new recipients or edit recipient properties
1. Repeat step 1 on page 565.
2. Perform one of the following:
■ To configure a new recipient, click New, select the recipient type you want to
configure, and then click OK.
■ To edit recipient properties, select the recipient for which you want to edit
properties, and then click Properties.
3. Enter or edit recipient properties for the following types of recipients:
■ Person
■ SMTP Mail. See “Configuring SMTP email or mobile phone text messaging
for a person recipient” on page 548
565

Assigning notification recipients for completed jobs
■ MAPI Mail. See “Configuring MAPI mail for a person recipient” on page 550
■ VIM Mail. See “Configuring VIM mail for a person recipient” on page 552
■ Pager. See “Configuring a pager for a person recipient” on page 553
■ Net Send. See “Select the appropriate options from the Net Send Recipient
Properties dialog box:” on page 556
■ Printer. See “Select the appropriate options in the Printer Recipient Properties
dialog box:” on page 558
■ Group. Perform the following:
4. Click OK.
■ In the Group Name field, type the group for whom you are configuring the
notification.
■ To add members to the group, select recipients from the All Recipients list,
and then click Add to move them to the Group Members list.
■ To remove members from the group, select recipients from the Group
Members list, and then click Remove to move them to the All Recipients
list.
5. You can edit recipient properties or select other options from the Properties pane.
Related Topics:
“Backing up data” on page 345
566 Administrator’s Guide

About SNMP notification
Chapter 13, Alerts and notifications
About SNMP notification
SNMP (Simple Network Management Protocol) is a method by which a network can be
monitored from a central location. SNMP-enabled network applications (like Backup
Exec) report to an SNMP Console (a management workstation). The console receives
messages (traps) from Backup Exec regarding status and error conditions. A MIB is
available in the WINNT\SNMP\language directory on the Backup Exec CD that you can
load into your SNMP console.
The Object Identifier prefix for Symantec is:
1.3.6.1.4.1.1302
Backup Exec SNMP Traps (messages) have unique object IDs and may include up to four
strings. The following SNMP Trap types are supported:
SNMP Traps
Trap Type Object ID String 1 String 2 String 3 String 4
Product Start 1302.3.1.1.9.1 Backup Exec:
Application
initializing
Product Stop 1302.3.1.1.9.2 Backup Exec:
Application
terminating
Job Canceled 1302.3.1.2.8.2 Backup Exec:
Job canceled
by Operator
Job Failed 1302.3.1.2.8.1 Backup Exec:
Job failed
Storage device
requires
human
intervention
Robotic library
requires
human
intervention
1302.3.2.5.3.3 Backup Exec:
Storage device
requires
attention
1302.3.2.4.3.3 Backup Exec:
robotic library
device requires
attention
machine name product,
version,
revision
machine name product,
version,
revision
machine name job name local or remote
Operator name
machine name job name detail message
machine name job name detail message
machine name job name detail message
567

About SNMP notification
SNMP Traps
Trap Type Object ID String 1 String 2 String 3 String 4
Intelligent
Disaster
Recovery
Message
Intelligent
Disaster
Recovery
Message
Backup Exec
system error
Backup Exec
general
information
1302.3.1.4.2.1.
1
1302.3.1.4.2.1.
2
Copy to
alternate path
failed
Backup
complete,
update DR
disks
1302.3.1.1.9.3 The
application
has
encountered
an error
1302.3.1.1.9.4 Information
on normal
events
Job Success 1302.3.1.2.8.3 The job
succeeded
Job Success
with
exceptions
1302.3.1.2.8.4 The job
succeeded, but
there was a
problem
Job Started 1302.3.1.2.8.5 The job has
started
Job Completed
with no data
1302.3.1.2.8.6 The job
succeeded, but
there was no
data
Job Warning 1302.3.1.2.8.7 The job has a
warning
PVL Device
Error
1302.3.1.5.1.1.
1
The device has
encountered
an error
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
568 Administrator’s Guide

SNMP Traps
PVL Device
Warning
Chapter 13, Alerts and notifications
1302.3.1.5.1.1.
2
The device has
encountered a
warning
About SNMP notification
Trap Type Object ID String 1 String 2 String 3 String 4
PVL Device
Information
PVL Device
Intervention
PVL Media
Error
PVL Media
Warning
PVL Media
Information
PVL Media
Intervention
1302.3.1.5.1.1.
3
1302.3.1.5.1.1.
4
1302.3.1.5.2.1.
1
1302.3.1.5.2.1.
2
1302.3.1.5.2.1.
3
1302.3.1.5.2.1.
4
Catalog Error 1302.3.1.5.3.1.
1
Tape Alert
Error
Tape Alert
Warning
Tape Alert
Information
1302.3.1.5.4.1.
1
1302.3.1.5.4.1.
2
1302.3.1.5.4.1.
3
Normal device
information
Device
requires
attention
There is an
error with the
media
There may be
a problem with
the media
Normal media
information
Media requires
attention
There is an
error with the
catalog
There is a
TapeAlert
error
There is a
TapeAlert
warning
Normal
TapeAlert
information
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
569

About SNMP notification
SNMP Traps
Trap Type Object ID String 1 String 2 String 3 String 4
Database
Maintenance
Error
Database
Maintenance
Information
Software
Update Error
Software
Update
Warning
Software
Update
Information
Install Update
Warning
Install Update
Information
1302.3.2.5.5.1.
1
1302.3.2.5.5.1.
2
1302.3.2.5.6.1.
1
1302.3.2.5.6.1.
2
1302.3.2.5.6.1.
3
1302.3.2.5.7.1.
1
1302.3.2.5.7.1.
2
There is a
database
maintenance
error
Normal
database
maintenance
information
There is a
software
update error
There is a
software
update
warning
Normal
software
update
information
There is an
install
warning
Normal Install
information
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
machine name job name detail message
Related Topics:
“Installing and configuring the SNMP system service” on page 571
570 Administrator’s Guide

Installing and configuring the SNMP system service
Chapter 13, Alerts and notifications
About SNMP notification
In order to receive Backup Exec traps at the SNMP console, you must configure the SNMP
system service with the SNMP console's IP address.
To install the SNMP system service and configure it to send traps to the SNMP console for
Windows 2000 and Windows server 2003
1. Click Start, point to Settings, point to Control Panel, and then double-click
Add/Remove Programs.
2. Click Add/Remove Windows Components.
3. In Add/Remove Windows Components, select Management and Monitoring Tools,
and then click Details.
When selecting the component, do not select or clear its check box.
4. Select Simple Network Management Protocol, and then click OK.
5. Click Next.
SNMP starts automatically after installation. You must be logged on as an
administrator or a member of the Administrators group in order to complete this
procedure. If your computer is connected to a network, network policy settings might
also prevent you from completing this procedure.
Related Topics:
“Configuring alert category properties” on page 540
571

Adding Windows Management Instrumentation capability
Adding Windows Management Instrumentation capability
Windows Management Instrumentation (WMI) is an infrastructure through which you
can monitor and control system resources. Backup Exec includes performance counter
and SNMP providers that can be manually installed and used with WMI.
To install the WMI performance counter provider
1. Insert the Backup Exec Installation CD.
2. At the command prompt, type the following:
mofcomp :\winnt\wmi\backupexecperfmon.mof
To install the WMI SNMP provider
Note Before you install the SNMP provider included with Backup Exec, you must have
the Microsoft SNMP provider installed on your system. For more information, refer
to your Microsoft documentation.
1. Insert the Backup Exec Installation CD.
2. At the command prompt, type the following:
mofcomp :\winnt\wmi\snmp\eng\bkupexecmib.mof
Note To use the WMI SNMP provider you must set up SNMP notification.
Uninstalling WMI providers
To uninstall the WMI performance counter provider
❖ At the command line, type:
mofcomp :\winnt\wmi\deletebackupexecperfmon.mof
To uninstall the WMI SNMP provider
❖ At the command line, type:
Smi2smir /d Backup_Exec_MIB
572 Administrator’s Guide

Reports in Backup Exec
Chapter
14
Backup Exec includes 45 standard reports that show detailed information about your
system. When generating most of the reports, you can specify settings that serve as filter
parameters or a time range for the data that you want to include in the report. You can
then run and view the report immediately, or you can create a new job that saves the
report data in the Job History. You can also view general properties for each report.
Backup Exec also provides:
■ The ability to schedule a report to run at a specified time or to specify a recurring
schedule for the report to run.
■ The ability to have Backup Exec distribute reports through notification.
To run reports across multiple media servers, you must install the Backup Exec SAN
Shared Storage Option, even if you are not operating in a shared storage environment.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
“Scheduling report jobs and setting notification recipients” on page 582
“Available reports” on page 604
573

Viewing reports
Viewing reports
Reports can be viewed and printed in the following formats:
■ PDF
■ HTML
■ XML
■ Microsoft Excel (XLS)
■ Comma Separated Value (CSV)
To properly format integrated Backup Exec reports, you must configure a default printer
using the Windows Control Panel Printers applet. This is required even if you do not have
a printer attached to your system.
To view the list of available reports
1. On the navigation bar, click Reports.
2. In the Reports pane, click All Reports.
3. To sort the list of available reports, click the column heading on which you want to
sort.
Related Topics:
“Running and viewing a new report job” on page 578
“Scheduling report jobs and setting notification recipients” on page 582
“Available reports” on page 604
Running a report
When you run a report, you can specify the criteria that is used to determine the items
that will be included in the report. The settings, or parameters, available for you to select
depend on the type of data that can be included in the report. After the report is
generated, only the items that match the criteria appear in the report.
To run a report
1. On the navigation bar, click Reports.
2. On the Reports pane, select the report you want to run.
574 Administrator’s Guide

3. In the task pane, under Report Tasks, click Run report now.
Chapter 14, Reports in Backup Exec
Running a report
4. If the Run Report Now Properties dialog box appears, then select the appropriate
settings, or filter parameters, for the data you want to include in the report.
Only filter parameters that are available for a report appear. Select the appropriate
options as follows:
Media set Filters the report based on media set names. Media sets include all
the media that is inserted into the storage device.
Media server Filters the report based on media server names. The media server is
the server on which Backup Exec is installed. This setting is only
available if the SAN Shared Storage Option is available.
Job status Filters the report based on job status.
Protected server Filters the report based on specific protected server names. The
protected server is the server that is being backed up.
Vault Filters the report based on specific vault names. A media vault is a
virtual representation of the actual physical location of media. For
more information on media vaults, see “Media locations and
vaults” on page 286.
575

Running a report
Ranges Filters the report based on the time range for the data that you
want to include in the report. If range parameters are not available
for a report, you will not be able to select the parameter. Range
parameters or options available include:
◆ Days. Select this check box to enable the date filter.
- Number of days before day report runs. Type the number of
days prior to the current day to begin the filter process on the
data to be included in the report. You can enter a minimum of 0
and a maximum of 32,000 days.
- Number of days after day report runs. Type the number of
days after the current day to begin the filter process on the data
to be included in the report. You can enter a minimum of 0 and a
maximum of 32,000 days.
◆ Hours. Select this check box to enable the hours filter.
- Number of hours within time report. Type the number of
hours either before or after the present hour to filter the data to
be included in the report. The time frame depends on the type
of report. You can enter a minimum of 0 and a maximum of
32,000 hours.
◆ Event count. Select this check box to enable the event count
filter.
- Maximum number of events to include. Enter the number of
events to include in the report. Events generate alerts and
originate from one of the following sources: system, job, media,
or device. You can enter a minimum of 0 and a maximum of
32,000 events.
Note Entering a value of zero for the range parameter does not
limit the amount of data included in the report; this can
result in an extensive report.
5. Click Run Now.
The report appears and displays data based on the criteria you set when you ran the
report.
6. To save the report, click Save As; for a report in PDF, click the Save a Copy icon.
When prompted, enter the file name and location where you want to save the report
and then click Save.
The report is saved in the location you specify. Backup Exec also creates a folder, with
the same name as the report, in the same location in which the report is saved. The
folder contains images and report pages that enable you to view the saved report.
7. To print the report, click Print; for a report in PDF, click the Print icon. You must
have a printer attached to the computer, and configured in order to print the report.
576 Administrator’s Guide

Chapter 14, Reports in Backup Exec
For reports in an HTML format, do the following:
Running a report
■ To ensure the reports print correctly, in the Layout tab of the Print dialog box,
under Orientation, select Landscape.
■ To print all the pages in a multiple page report, in the Options tab of the Print
dialog box, select Print all linked documents.
Note If all the data does not print in an HTML-formatted report, you may need to edit
the page setup for the report. To edit the page setup, open Microsoft Internet
Explorer, and then on the File menu, click Page Setup. Under Header and Footers,
delete the Header and Footer and then under Margins, set the Left and Right
margins to the minimum setting that your printer will accept.
8. After you have finished viewing the report, click OK.
The report will automatically be deleted.
Related Topics:
“Scheduling report jobs and setting notification recipients” on page 582
“Available reports” on page 604
577

Running and viewing a new report job
Running and viewing a new report job
You can create a report job that saves the report data in the Job History. You can specify
filters and ranges and select recipients for notification; however, the report is not
included in the notification. Report jobs run immediately and you cannot specify a
schedule. After the report is generated, you can view the completed report and job
history in the Job Monitor. The report data will also be saved in the Backup Exec
database.
The Admin Plus Pack Option enables you to perform advanced report tasks such as
scheduling a report job and including the report in a notification.
To run a new report job
1. On the navigation bar, click Reports.
2. On the Reports pane, select the report for which you want to run a job.
3. Under Report Tasks in the task pane, click New report job.
4. On the Properties pane, under Settings, click General and then type the name for
the job in Job name and select the Job priority.
If another job is scheduled to run at the same time as this job, the priority you set
determines which job runs first.
5. On the Properties pane, under Settings, select the appropriate filter parameters for
the data you want to include in the report.
If filter parameters or settings are not available for a report, you will not be able to
view the parameters. Select the appropriate options as follows.
Media set Filters the report based on media set names. Media sets include all
the media that is inserted into the storage device.
Media server Filters the report based on media server names. The media server is
the server on which Backup Exec is installed. This option is only
available if the SAN Shared Storage Option is installed.
Job status Filters the report based on job status.
Protected server Filters the report based on specific protected server names. The
protected server is the server that is being backed up.
578 Administrator’s Guide

Chapter 14, Reports in Backup Exec
Running and viewing a new report job
Vault Filters the report based on specific vault names. A media vault is a
virtual representation of the actual physical location of media. For
more information on media vaults, see “Media locations and
vaults” on page 286.
6. On the Properties pane, under Settings, click Ranges and select the appropriate
range parameters for the data you want to include in the report.
If range parameters are not available for a report, you will not be able to select the
parameter. Select the appropriate options as follows
Days Select this check box to enable the date filter.
Number of days before
day report runs
Number of days after
day report runs
Type the number of days prior to the current day to begin the filter
process on the data to be included in the report. You can enter a
minimum of 0 and a maximum of 32,000 days.
Type the number of days after the current day to begin the filter
process on the data to be included in the report. You can enter a
minimum of 0 and a maximum of 32,000 days.
Hours Select this check box to enable the hours filter.
Number of hours within
time report
Type the number of hours either before or after the present hour to
filter the data to be included in the report. The time frame depends
on the type of report. You can enter a minimum of 0 and a
maximum of 32,000 hours.
Event count Select this check box to enable the event count filter.
Maximum number of
events to include
Enter the number of events to include in the report. Events
generate alerts and originate from one of the following sources:
system, job, media, or device. You can enter a minimum of 0 and a
maximum of 32,000 events.
Entering a value of zero for the range parameter does not limit the amount of data
included in the report; this can result in an extensive report.
7. To notify recipients when the report job completes and to send the completed report
to the recipients, do the following in the order listed.
■ On the Properties pane, under Settings, click Notification.
■ Select the recipients who will receive notification when the report job completes.
579

Running and viewing a new report job
■ To include a copy of the completed report along with the notification, check
Include job log with a notification to an e-mail or printer recipient.
8. On the Properties pane, under Frequency, click Schedule and then click Submit job
on hold if you want to submit the job with an on-hold status.
Select this option if you want to submit the job, but do not want the job to run until
you change the job’s hold status.
9. Click Enable automatic cancellation, and then type the number of hours or minutes
in the Cancel job if not completed within option.
Select this option if you want to cancel the job if is not completed within the selected
number of hours or minutes. Backup Exec starts timing the length of time the job
takes to run when the job actually begins, not the scheduled time.
10. After you have completed all the items you want to set for the new report job, click
Run Now.
The report is submitted according to the options you selected.
To view the report in the Job History
1. On the navigation bar, click Job Monitor.
2. Click the Job List tab.
3. On the Job History pane, select the report you want to view.
4. Under General Tasks in the task pane, click Properties.
The report and job history appear and display data based on the criteria you selected
when you set up the job.
5. Click Job History to view detailed information about the job or Report to view the
contents of the report.
6. To print the report, click Print; for a report in PDF, click the Print icon. You must
have a printer attached to the computer, and configured in order to print the report.
For reports in an HTML format, do the following:
■ To ensure the reports print correctly, in the Layout tab of the Print dialog box,
under Orientation, select Landscape.
■ To print all the pages in a multiple page report, in the Options tab of the Print
dialog box, select Print all linked documents.
580 Administrator’s Guide

Chapter 14, Reports in Backup Exec
Running and viewing a new report job
If all the data does not print in an HTML-formatted report, you may need to edit the
page setup for the report. To edit the page setup, open Microsoft Internet Explorer,
and then on the File menu, click Page Setup. Under Header and Footers, delete the
Header and Footer and then under Margins, set the Left and Right margins to the
minimum setting that your printer will accept.
7. After you have finished viewing the report, click OK.
The report is saved for the length of time you set in the database maintenance
option.
To save the report to a new location
1. On the navigation bar, click Job Monitor.
2. Click the Job List tab.
3. On the Job History pane, right-click the report you want to save.
4. Click Properties.
5. Click Save As.
The Save As dialog box appears.
6. Enter the file name and location where you want to save the report and then click
Save.
The report is saved in the location you specify. Backup Exec also creates a folder, with
the same name as the report, in the same location in which the report is saved. The
folder contains images and report pages that enable you to view the saved report.
To delete the report from Job History
1. On the navigation bar, click Job Monitor.
2. Click the Job List tab.
3. On the Job History pane, select the report you want to delete.
4. Under General Tasks in the task pane, click Delete.
5. Confirm the job deletion.
The report and associated job history are deleted.
581

Running and viewing a new report job
Related Topics:
“Configuring database maintenance” on page 162
“Viewing and changing completed jobs” on page 455
“Available reports” on page 604
Scheduling report jobs and setting notification recipients
You can create a report job and schedule it to run at a specific time or specify a recurring
schedule for a report to run. For information about creating a report job, see “Running
and viewing a new report job” on page 578. For information about scheduling the job, see
“Scheduling jobs” on page 368.
You can also assign notification recipients to the report job just as you would for other
Backup Exec jobs, such as backups and restores. If you select Include job log with a
notification to an e-mail or printer recipient, the report is included with the
notification. If this option is not selected, the recipient only gets a message that the
report has run.
582 Administrator’s Guide

About custom reports in Backup Exec
Chapter 14, Reports in Backup Exec
About custom reports in Backup Exec
You can create reports that contain information to meet the specific requirements of
your organization. You choose the data to include in the report, and then determine how
the data is filtered, sorted, and grouped. In addition, you can set up pie graphs and bar
graphs to graphically represent the report data.
You can customize the look of the reports by:
■ Adding your company logo to the report
■ Changing the color of the banner
■ Adding text to the footer
Filter criteria and filter expressions
Filters let you customize reports to include only the information that meets specific
criteria. For example, you can use filters to find:
■ Jobs that contain a specific word
■ Alerts that occurred on a specific day
■ Media that are in a specific location
You use filter criteria to create filter expressions. You can use one or multiple filter
expressions. A filter expression consists of a field name, an operator, and a value. The
following filter expression finds all alerts for errors:
Filter expression for finding alerts for errors
Filter type Data
Field name Alert type
Operator = (Equal)
Value Error
583

Creating a custom report
If you want the report to include only alerts for errors that occurred on a specific day, add
another filter expression for the date:
Filter expression for finding alerts on a specific day
Filter type Data
Field name Date entered
Operator =(Equal)
Value 02/03/06
Related Topics:
Setting filters for custom reports on page 586
Grouping fields in custom reports on page 591
Sorting fields in custom reports on page 592
Setting graph options in custom reports on page 593
Creating a custom report
To create a custom report
1. On the navigation bar, click Reports.
2. On the task pane, click New custom report.
3. On the Custom Report dialog box, type a name and description for the report.
4. If you do not want this report to include the default header and footer settings,
uncheck Use header and footer settings specified in Tools/Options.
5. On the properties pane, under Report Definition, click Field Selection.
6. In the Category box, select one of the following groups for which you want to create a
report:
Alerts Includes fields for information such as the alert message
text, the alert title, when the alert was created, and the
name of the responder.
584 Administrator’s Guide

Chapter 14, Reports in Backup Exec
Creating a custom report
Device Includes fields for information such as the number of bytes
that were read or written, number of hours the device was
in use, and the number of errors on the device.
Job Includes fields for information such as the job priority, the
job name, the due date, and the policy name.
Job History Includes fields for information such as the backup rate, the
device used, errors, and media.
Media Includes fields for information such as the backup set date
and time, the backup type, the date allocated and modified,
and the media set name.
Policy Includes fields for information such as the job priority, the
policy name and description, the selection list name, and
the due date.
7. In the Available fields box, select the fields that you want to include on the report,
and then click the right-arrow button.
By default, Backup Exec displays only the basic fields for each category. The basic
fields are the fields that are most likely to be used in a report. To show all available
fields, check Show advanced fields.
To select consecutive fields, click the first item, press and hold SHIFT, and then click
the last item. To select fields that are not consecutive, press and hold CTRL, and then
click each item.
8. To adjust the order of the fields on the report, select a field, and then click Move Up
and Move Down until the field is in the correct order.
Fields are displayed on the report based on the order in which they display in the box
titled Fields selected for the report. The first field in the list displays on the left side
of the report.
9. To adjust the width of the column for a field:
■ Click the field name in the Fields selected for the report list.
■ In the Column width box, type the new width.
■ Click Set.
585

Creating a custom report
10. Do any of the following:
To set filter criteria for
the report
To group fields for the
report
To sort fields for the
report
To set graph options
for the report
To preview and test the
report
To finish and close the
report
Setting filters for custom reports
◆ On the properties pane, under Report Definition, click Filters.
◆ Proceed to step 6 in “Setting filters for custom reports” on
page 586.
◆ On the properties pane, under Report Definition, click
Grouping.
◆ Proceed to step 6 in “Grouping fields in custom reports” on
page 591.
◆ On the properties pane, under Report Definition, click Sorting.
◆ Proceed to step 6 in “Sorting fields in custom reports” on
page 592.
◆ On the properties pane, under Report Definition, click Graph
Options.
◆ Proceed to step 6 in “Setting graph options in custom reports”
on page 593.
◆ On the properties pane, under Preview, click Preview.
◆ To test the report, on the Preview dialog box, click Test Report
Click OK.
Filters let you customize reports to include only the information that meets specific
criteria. You can filter on any field that is available for the report category, including
fields that you do not want to include on the report. For example, if you want to create a
report that lists jobs that ran on the media server named Test Server, you can set up the
following filter:
Field name Media Server
Operator = (Equal)
Value Test Server
586 Administrator’s Guide

Chapter 14, Reports in Backup Exec
Creating a custom report
Since the report lists all jobs that ran on Test Server, the Media Server field does not
need to display on the report. However, you might consider adding the media server
name to the report name.
To set filters for custom reports
1. On the navigation bar, click Reports.
2. In the tree view, click Custom Reports.
3. In the reports list, click the report that you want to filter.
4. On the task pane, click Edit.
5. On the properties pane, under Report Definition, click Filters.
6. Complete the options as follows:
Show advanced fields Check Show advanced fields to see all of the fields that are
available for filtering. By default, only the most common fields
display.
Field name Select the field on which you want to filter.
587

Creating a custom report
Operator Select the appropriate operator for this filter. Operators determine
how the field name and the value are linked. The following
operators are available in Backup Exec, but the list that displays
varies depending on the type of field you selected in Field name:
◆ = (Equal). The field name must equal the value.
◆ (Not Equal). The field name must not equal the value.
7. Click Add.
◆ > (Greater Than). The field name must be larger than the
value.
◆ >= (Greater Than or Equal). The field name must be larger
than or equal to the value.
◆ < (Less Than). The field name must be smaller than the value.
◆

8. Repeat step 6 and step 7 to add more filters.
9. To combine sets of filter expressions, do any of the following:
To combine two filter
expressions so that
both expressions must
be true for the result to
be true
To combine two filter
expressions so that
one of the expressions
must be true for the
result to be true
To combine two filter
expressions into a
single expression
Chapter 14, Reports in Backup Exec
Click AND.
Creating a custom report
For example, to find all backup jobs that failed, add the following
expressions:
◆ Status = Failed
◆ Type = Backup
After you set up the expressions, do the following:
◆ Click AND to combine the two expressions.
The combined expression is:
Status = Failed AND Type = Backup
Click OR.
For example, to find jobs that either failed or were canceled, add
the following expressions:
◆ Status = Failed
◆ Status = Canceled
After you set up the expressions, do the following:
◆ Click OR to combine Status = Failed with Status = Canceled.
The combined expression is:
Status = Failed OR Status = Canceled
Click ( ) +
For example, to find backup jobs and restore jobs that failed, add
the following expressions:
◆ Status = Failed
◆ Type = Backup
◆ Type = Restore
After you set up the expressions, do the following:
◆ Use OR to combine Type = Backup with Type = Restore.
◆ Press and hold Ctrl while you click Type = Backup and Type =
Restore.
◆ Click ( ) + to combine Type = Backup with Type = Restore.
◆ Use AND to combine Status = Failed with (Type = Backup OR
Type = Restore).
The combined expression is:
Status = Failed AND (Type = Backup OR Type = Restore)
589

Creating a custom report
To separate two filter
expressions that were
combined into a single
expression
10. To change any of the expressions, do the following in the order listed:
■ In the Filter criteria box, select the expression that you want to change.
■ Click Edit.
■ In the Filter expression area, edit the expression’s values.
■ Click Update.
11. To remove an expression, select the expression, and then click Remove.
12. Do any of the following:
To group fields for the
report
To sort fields for the
report
To set graph options
for the report
To preview and test the
report
To finish and close the
report
Click ( ) -
For example, if you used ( ) + to combine Type = Backup with Type
= Restore, it is displayed on the Filters dialog box like this:
(Type = Backup OR Type = Restore)
To make the combined expression into two individual expressions,
do the following:
◆ Press and hold Ctrl while you click both Type = Backup and
Type = Restore.
◆ Click ( ) -
After you separate the exrpressions, they are displayed without
the parentheses.
◆ On the properties pane, under Report Definition, click
Grouping.
◆ Proceed to step 6 in “Grouping fields in custom reports” on
page 591.
◆ On the properties pane, under Report Definition, click Sorting.
◆ Proceed to step 6 in “Sorting fields in custom reports” on
page 592.
◆ On the properties pane, under Report Definition, click Graph
Options.
◆ Proceed to step 6 in “Setting graph options in custom reports”
on page 593.
◆ On the properties pane, under Preview, click Preview.
◆ To test the report, on the Preview dialog box, click Test Report.
Click OK.
590 Administrator’s Guide

Grouping fields in custom reports
Chapter 14, Reports in Backup Exec
Creating a custom report
You can group a custom report by up to three of the fields that you have chosen for the
report. Grouping fields creates sections on the report. For example, if you group by media
server, Backup Exec creates a section for each media server that matches the filter
criteria. Under each media server’s section, the report displays the data that corresponds
to the remaining fields that you selected for the report.
A report must have at least one field that is not grouped. For example, if you select three
fields in the report, you can group only two of the fields. If you group all of the fields, no
data appears on the report because all of the data is listed in the group section titles. In
addition, you must have at least four fields on the report to use all three grouping fields.
After you select a field on which to group the report, you can group the data for that field
in ascending or descending order. Ascending order lists numbers from smallest to largest
and lists letters in alphabetical order. Descending order lists numbers from largest to
smallest and lists letters in reverse alphabetical order. For example, if you group by a
date field in ascending order, the report data is grouped by date, starting with the earliest
date.
To group fields in custom reports
1. On the navigation bar, click Reports.
2. In the tree view, click Custom Reports.
3. In the reports list, click the report that contains the fields you want to group.
4. In the task pane, click Edit.
5. On the properties pane, under Report Definition, click Grouping.
6. In the Group by box, select the name of the field on which you want to group data.
7. Click Ascending to group the information in ascending order or click Descending to
group the information in descending order.
8. If you want to group on additional fields, in the Then group by box, repeat step 6 and
step 7.
9. Do any of the following:
To sort fields for the
report
◆ On the properties pane, under Report Definition, click Sorting.
◆ Proceed to step 6 in “Sorting fields in custom reports” on
page 592.
591

Creating a custom report
To set graph options
for the report
To preview and test the
report
To finish and close the
report
Sorting fields in custom reports
You can sort a custom report by up to three of the fields that you have chosen for the
report. When you sort on fields, Backup Exec arranges all of the data that matches the
sort criteria together in the report. For example, if you sort on the Media Server field in
ascending order, all data for Media Server A displays first, followed by all data for Media
Server B, and so on. Ascending order lists numbers from smallest to largest and lists
letters in alphabetical order. Descending order lists numbers from largest to smallest and
lists letters in reverse alphabetical order.
To sort fields in custom reports
1. On the navigation bar, click Reports.
2. In the tree view, click Custom Reports.
3. In the reports list, click the report that contains the fields you want to sort.
4. In the task pane, click Edit.
◆ On the properties pane, under Report Definition, click Graph
Options.
◆ Proceed to step 6 in “Setting graph options in custom reports”
on page 593.
◆ On the properties pane, under Preview, click Preview.
◆ To test the report, on the Preview dialog box, click Test Report.
Click OK.
5. On the properties pane, under Report Definition, click Sorting.
6. In the Sort on list, select the name of the field on which you want to sort
information.
7. Click Ascending to sort the information in ascending order or click Descending to
sort the information in descending order.
8. If you want to sort on additional fields, in the Then sort on box repeat step 6 and
step 7.
592 Administrator’s Guide

9. Do any of the following:
To set graph options
for the report
To preview and test the
report
To finish and close the
report
Setting graph options in custom reports
Chapter 14, Reports in Backup Exec
Creating a custom report
You can include a pie graph or a bar graph in custom reports.
You must select at least two fields on the Field Selection dialog box to create a pie graph,
and at least three fields to create a bar graph.
To set graph options in custom reports
1. On the navigation bar, click Reports.
2. In the tree view, click Custom Reports.
3. In the reports list, click the report for which you want to set graph options.
4. In the task pane, click Edit.
5. On the properties pane, under Report Definition, click Graph Options.
6. In the Graph type box, select the type of graph that you want to create, either Pie or
Bar.
7. In the Graph title box, type the title that you want to display above the graph in the
report.
8. Complete the following options for a pie graph:
Category field (pie section
per value)
◆ On the properties pane, under Report Definition, click Graph
Options.
◆ Proceed to step 6 in “Setting graph options in custom reports”
on page 593.
◆ On the properties pane, under Preview, click Preview.
◆ To test the report, on the Preview dialog box, click Test Report.
Click OK.
Select the field for which you want to display sections in the pie
chart.
593

Creating a custom report
Data field Select the field for which you want to calculate values.
Aggregation function Select the way that you want Backup Exec to calculate the values
generated for the Data field. Your choices are:
◆ Minimum. Calculates the lowest value. This is available for
numeric fields only.
◆ Maximum. Calculates the highest value. This is available for
numeric fields only.
◆ Average. Calculates the average value. This is available for
numeric fields only.
◆ Count. Calculates the number of values. This option is the only
available option for non-numeric fields, such as text fields or
date fields, but it is also available for numeric fields.
◆ Sum. Calculates the sum of the values. This is available for
numeric fields only.
9. Complete the following options for a bar graph:
Vertical axis title Type the title that you want to display to the left of the graph. The
title will display vertically in the report. There is a 50-character
limit.
Series field (bar per
value)
Category field (set of
series bars per value)
Select the field that contains the values that you want to display
on the horizontal bars of the graph. Backup Exec creates a legend
for the values.
Select the field that contains the information for which you want
to group information along the left side of the graph.
Data field Select the field for which you want to calculate values.
Horizontal axis title Type the title that you want to display below the graph.
Aggregation function Select one of the following functions to calculate the values
generated for the Data field. Your choices are:
◆ Minimum. Calculates the lowest value.
◆ Maximum. Calculates the highest value.
◆ Average. Calculates the average value.
◆ Count. Calculates the number of values. This option is
available only for non-numeric fields, such as text fields or
date fields.
◆ Sum. Calculates the sum of the values.
594 Administrator’s Guide

10. Do any of the following:
To preview and test the
report
To finish and close the
report
Example graphs
Chapter 14, Reports in Backup Exec
Creating a custom report
This section includes three examples of graphs that you can create in custom reports. In
addition, the fields that were used to create the graphs are included. Review the
examples to learn how the fields on the Graph Options dialog box correspond to
completed graphs.
Example pie graph
◆ On the properties pane, under Preview, click Preview.
◆ To test the report, on the Preview dialog box, click Test Report.
Click OK.
595

Creating a custom report
The example pie graph, titled Frequency of Alert Types, was created using the following:
Example pie graph options
Graph option name Fields selected
Graph Type Pie
Graph title Frequency of Alert Types
Category field Event name
Data field Event name
Aggregation
function
Example bar graph 1
Count
596 Administrator’s Guide

Chapter 14, Reports in Backup Exec
Creating a custom report
The example bar graph, titled Average Duration of Job per Device per Selection List, was
created using the following:
Example bar graph 1 options
Graph option name Fields selected
Graph Type Bar
Graph title Average duration of job per device per selection list
Vertical axis title Selection list
Series field Device name
Category field Selection list name
Data field Job duration
Aggregation
function
Average
Horizontal axis title Average duration of a job (seconds)
597

Creating a custom report
Example bar graph 2
The example bar graph, titled Total Storage Per Device, was created using the following:
Example bar graph 2 options
Graph option name Fields selected
Graph Type Bar
Graph title Total Storage Per Device
Vertical axis title Resource
Series field Device name
Category field Resource name
Data field Total data size
Aggregation
function
Sum
598 Administrator’s Guide

Example bar graph 2 options
Graph option name Fields selected
Horizontal axis title Total Data Stored (MB)
Previewing custom reports
To preview custom reports
1. On the navigation bar, click Reports.
2. In the tree view, click Custom Reports.
3. In the reports list, click the report that you want to preview and test.
4. In the task pane, click Edit.
5. On the properties pane, under Preview, click Preview.
6. Click OK.
Copying custom reports
To copy custom reports
1. On the navigation bar, click Reports.
2. In the tree view, click Custom Reports.
3. In the reports list, click the report that you want to copy.
4. In the task pane, click Copy.
5. In the Name of copy box, type a unique name for the copied report.
6. Click OK.
Chapter 14, Reports in Backup Exec
Copying custom reports
599

Editing custom reports
Editing custom reports
If the report that you want to edit has been run in a previous report job, the changes you
make now may affect the appearance of the reports in job history. Symantec
recommends that you copy the report and then edit the copy.
To edit custom reports
1. On the navigation bar, click Reports.
2. In the tree view, click Custom Reports.
3. In the reports list, click the report that you want to filter.
4. In the task pane, click Edit.
5. Change the report settings as needed.
6. Click OK.
Deleting custom reports
Before you can delete a custom report, you must delete all of the associated job history
records.
To delete job history records that are associated with custom reports
1. On the navigation bar, click Job Monitor.
2. In the Job History pane, select the job history for the custom report that you want to
delete.
The report name is listed in the Device Name column.
3. On the task pane, under General Tasks, click Delete.
To delete custom reports
1. On the navigation bar, click Reports.
2. In the tree view, click Custom Reports.
3. In the reports list, click the report that you want to filter.
600 Administrator’s Guide

4. In the task pane, click Delete.
5. Click Yes.
Setting default options for reports
Chapter 14, Reports in Backup Exec
Setting default options for reports
You can set Backup Exec to display all reports in either HTML or Adobe Portable
Document Format (PDF). The default setting is HTML. The format that you select does
not affect the format of the reports sent to users with the notification feature.
In addition, you can set default options for the header and footer for all custom reports.
You can:
■ Include a logo in the header.
■ Choose a color for the banner in the header.
■ Include text in the footer.
■ Include the time in the footer.
When you choose a color for the banner, you can type the numbers that correspond to
the colors (RGB values), or you can select the color from a chart.
To set default options for reports
1. On the Tools menu, click Options.
2. On the Properties pane, under Settings, click Reports.
3. Complete the following options:
HTML Select this option if you want all reports to display in HTML
format. This is the default setting.
PDF Select this option if you want all reports to display in Adobe
Portable Document Format (PDF).
Use company logo image
file
Check Use company logo image file if you want to use your
company’s logo in the header of all custom reports.
Image file path If you checked Use company logo image file, type the path to the
logo that you want to use in all custom reports.
Red Type the number that corresponds to the value for red.
601

Viewing report properties
Green Type the number that corresponds to the value for green.
Blue Type the number that corresponds to the value for blue.
Colors Click Colors to select a basic color or to create a custom color for
the banner on custom reports.
Text Type the text that you want to display in the footer of custom
reports.
Include time Check Include time if you want the footer of custom reports to
include the time when the report runs.
4. Click OK.
Viewing report properties
Report properties provide detailed information about each report. The properties can be
viewed, but not edited.
To view report properties
1. On the navigation bar, click Reports.
2. On the Reports pane, select the report for which you want to view properties.
3. In the task pane, under Report tasks, click Properties.
The Report dialog box provides the following information:
Title The name of the report.
Description Describes the type of data that is included in the report.
602 Administrator’s Guide

4. Click OK after you have finished viewing the properties.
Related Topics:
“Running a report” on page 574
Chapter 14, Reports in Backup Exec
Viewing report properties
Category Classification for the report. Available report categories include:
◆ Media
◆ Media Vault
◆ Jobs
◆ Devices
◆ Configuration
◆ Alerts
◆ Template
Author The creator of the report.
Subject The version of the product for which the report was created.
File name The location of the report.
File size The size of the report.
Creation Date The date the report was installed on the system.
603

Available reports
Available reports
This section provides detailed information about each report available in Backup Exec.
The file name of the report, a description, and the information included in the report are
listed for each report. The data included in each report will vary depending on the
criteria you selected to include in the report.
The following reports are included in Backup Exec:
Backup Exec Reports
Report Name Description
Active Alerts Lists all active alerts chronologically, displaying the most recent
alerts first (see “Active Alerts Report” on page 608).
Active Alerts by Media
Server
Lists all active alerts grouped and filtered by media server,
displaying the most recent alerts first (see “Active Alerts by Media
Server Report” on page 609).
Alert History Lists all alerts in the alert history chronologically, displaying the
most recent alerts first (see “Alert History Report” on page 610).
Alert History by Media
Server
Lists all alerts in the alert history grouped and filtered by media
server, displaying the most recent alerts first (see “Alert History by
Media Server Report” on page 611).
Audit Log Lists the contents of the audit logs for selected servers for the
specified time period (see “Audit Log Report” on page 612).
Backup Job Success Rate Lists the success rate for backup jobs run to protect selected servers
(see “Backup Job Success Rate Report” on page 613).
Backup Resource Success
Rate
Backup Set Details by
Resource
Lists the success rate for backup jobs for specified past number of
days for resources on selected servers (see “Backup Resource
Success Rate Report” on page 614).
Lists all backup sets that ran within the last 72 hours. The sets are
grouped by the server and resource (see “Backup Set Details by
Resource Report” on page 615).
Backup Sets by Media Set Lists all backup sets by media set (see “Backup Sets by Media Set
Report” on page 616).
604 Administrator’s Guide

Backup Exec Reports (continued)
Report Name Description
Chapter 14, Reports in Backup Exec
Available reports
Backup Size by Resource Lists the backup size for each resource job for up to seven previous
runs and then computes the trailing average for up to seven
previous runs for each job run (see “Backup Size By Resource
Report” on page 617).
Configuration Settings Lists the contents of the Backup Exec system configuration
parameters table (see “Configuration Settings Report” on page 618).
Current Job Status Details the job queue sorted by status (see “Current Job Status
Report” on page 619).
Daily Device Utilization Lists the percentage of the storage devices’ capacity that the media
server uses. (see “Daily Network Device Utilization Report” on
page 620).
Device Summary Lists device usage and error summary for each selected media
server (see “Device Summary Report” on page 620).
Device Usage by Policy Lists all the policies that are targeted to specific drive selections
(see “Device Usage by Policy” on page 622).
Error-Handling Rules Lists all the defined error-handling rules (see “Error-Handling
Rules Report” on page 622).
Event Logs Lists all Backup Exec and other system and application event logs
(see “Event Logs Report” on page 624).
Event Recipients Lists all events registered by each notification recipient (see “Event
Recipients Report” on page 625).
Failed Backup Jobs Lists all the failed backup jobs sorted by the resource server and
time frame (see “Failed Backup Jobs Report” on page 625).
Job Distribution by Device Lists all the jobs that have been run on each system device during
the specified period (see “Job Distribution by Device Report” on
page 626).
Jobs Summary Lists all the jobs that ran within the last 72 hours in chronological
order (see “Jobs Summary Report” on page 627).
Machines Backed Up Lists all the servers that have been protected by Backup Exec (see
“Machines Backed Up Report” on page 628).
605

Available reports
Backup Exec Reports (continued)
Report Name Description
Managed Media Servers Lists the status and configuration for all media servers managed by
Backup Exec (see “Managed Media Servers Report” on page 628).
Media Required for
Recovery
Lists the media that contain the backup sets for each system backed
up on selected servers for the specified time period. This report can
be inaccurate if media overwrite settings allow the media to be
overwritten (see “Media Required for Recovery Report” on
page 630).
Media Set Lists all the media sets and media used by Backup Exec servers. The
current location is given for each media (see “Media Set Report” on
page 631).
Media Vault Contents Lists the media located in each media vault (see “Media Vault
Contents Report” on page 632).
Missed Availability Window Lists all jobs that have missed scheduled availability windows
within the specified time range. The jobs are listed in chronological
order (see “Missed Availability Report” on page 633).
Move Media to Vault Lists all media that can be moved to a media vault. The media listed
are not currently in a media vault and the media’s append period
has expired (see “Move Media to Vault Report” on page 634).
Operations Overview Lists past and future operations data for user-set period (see
“Operations Overview Report” on page 635).
Overnight Summary Lists the results of backup jobs for each resource during the last 24
hours. This report includes backup jobs that were scheduled to run
but did not run. Jobs are given a grace period of 24 hours before
being marked as past due (see “Overnight Summary Report” on
page 637).
Policy Jobs by Resource Lists all backup sets that were created in the selected period. The
sets are grouped by target server and resource (see “Policy Jobs by
Resource Summary Report” on page 638).
Policy Jobs Summary Lists in chronological order all jobs derived from selected policies
that have run within the specified time range (see “Policy Jobs
Summary Report” on page 639).
Policy Properties Lists all policies and policy job templates that are defined for the
server (see “Policy Properties Report” on page 640).
606 Administrator’s Guide

Backup Exec Reports (continued)
Report Name Description
Chapter 14, Reports in Backup Exec
Available reports
Policy Protected Resources Lists job information for each job that is derived from a policy and
assigned to protect any part of the named resource (see “Policy
Protected Resources” on page 641).
Problem Files Lists all the problem files reported for jobs. The files are grouped by
day and resource (see “Problem Files Report” on page 642).
Recently Written Media Lists all media that have been modified in the last 24 hours (see
“Recently Written Media Report” on page 643).
Resource Backup Policy
Performance
Lists the success rate for policy derived backup jobs (see “Resource
Backup Policy Performance Report” on page 644).
Resource Risk Assessment Lists job information for resources on which the last backup job run
on the resource failed. The data is filtered by resource server (see
“Resource Risk Assessment Report” on page 645).
Resources Protected by
Policy
Restore Set Details by
Resource
Lists the policies, templates, and selection lists being used to
protect a resource (see “Resources Protected by Policy report” on
page 646).
Lists all restore sets that ran within the last 72 hours. The sets are
grouped by the server and resource (see “Restore Set Details by
Resource Report” on page 647).
Retrieve Media from Vault Lists all reusable media currently in the specified vault (see
“Retrieve Media from Vault Report” on page 648).
Robotic Library Inventory Lists the contents of slots in robotic libraries attached to media
servers. Usage statistics are provided for each piece of media (see
“Robotic Library Inventory Report” on page 649).
Scheduled Server Workload Lists the estimated scheduled workload for the next 24-hour period
by server (see “Scheduled Server Workload” on page 650).
Scratch Media Availability Lists the aging distribution of media. Shows how many media are
available for overwrite and when other media will become available
for overwrite (see “Scratch Media Availability Report” on page 651).
Test Run Results Lists the results for the test run jobs set for the selected time period
and media servers (see “Test Run Results Report” on page 652).
607

Available reports
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
Active Alerts Report
The Active Alerts report lists all active alerts chronologically, displaying the most recent
alerts first. You can limit the number of alerts that appear in the report by entering
range parameters for the Event count.
Information displayed in the Active Alerts report is described in the following table.
Active Alerts Report
Item Description
Time Date and time the alert occurred.
Media Server Name of the media server on which the alert occurred.
Job Name Name of the job associated with the alert.
Device Name Name of the device on which the job ran.
Category Title of the alert, such as Service Start or Job Failed.
Message Describes the event that caused the alert.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
608 Administrator’s Guide

Active Alerts by Media Server Report
Chapter 14, Reports in Backup Exec
Available reports
The Active Alerts by Media Server report lists all active alerts grouped and filtered by
media server, displaying the most recent alerts first. You can limit the amount of data
that appears in the report by selecting filter parameters for the Event count or for the
Media server option.
Information displayed in the Active Alerts by Media Server report is described in the
following table.
Active Alerts by Media Server Report
Item Description
Time Date and time the alert occurred.
Job Name Name of the job associated with the alert.
Device Name Name of the device on which the job ran.
Category Title of the alert, such as Service Start or Job Failed.
Message Describes the event that caused the alert.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
609

Available reports
Alert History Report
The Alert History report lists all the alerts in the Alert History chronologically,
displaying the most recent alerts first. You can limit the number of alerts that appear in
the report by entering range parameters for the Days or Event count options
Information displayed in the Active History report is described in the following table.
Alert History Report
Item Description
Received Date and time the alert occurred.
Responded Date and time the user responded to the alert.
Responding User User that responded to the alert.
Job Name The name of the job associated with the alert.
Media Server Name of the media server on which the alert occurred.
Category Title of the alert, such as Service Start or Job Failed.
Message Describes the event that caused the alert.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
610 Administrator’s Guide

Alert History by Media Server Report
Chapter 14, Reports in Backup Exec
Available reports
The Alert History by Media Server report lists all alerts in the alert history grouped and
filtered by media server, displaying the most recent alerts first. You can limit the amount
of data that appears in the report by selecting filter parameters for the Days, Event
Count or Media server options.
Information displayed in the Alert History by Media Server report is described in the
following table.
Alert History by Media Server Report
Item Description
Media Server Name of the media server on which the alert occurred.
Time Date and time the alert occurred.
Received Time the alert occurred.
Responded Time the user responded to the alert.
Responding User User that responded to the alert.
Job Name Name of the job associated with the alert.
Category Title of the alert, such as Service Start or Job Failed.
Message Describes the event that caused the alert.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
611

Available reports
Audit Log Report
The Audit Log report lists the contents of the audit logs for the selected servers for the
selected time period. You can limit the amount of data that appears in the report by
entering filter parameters for the Media server or Audit Category options and range
parameters for the Days and Event count options.
Information displayed in the Audit Log report is described in the following table.
Audit Log Report
Item Description
Media Server Name of the media server on which the audit logs are located.
Category Category in which the change occurred, such as Logon Account, Alerts,
or Job.
Date Entered Time and date the change occurred.
Message Description of the change made in Backup Exec.
User Name User that made the change.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
612 Administrator’s Guide

Backup Job Success Rate Report
Chapter 14, Reports in Backup Exec
Available reports
The Backup Job Success Rate report lists the success rate for backup jobs run to protect
selected servers. You can limit the amount of data that appears in the report by entering
filter parameters for the Protected server option and range parameters for the Days
option.
Information displayed in the Backup Success Rate report is described in the following
table.
Backup Success Rate Report
Item Description
Server Name of the server being protected.
Date Date the backup job was processed.
Total Jobs Total number of jobs processed by the media server.
Successful Total number of jobs successfully performed by the media server.
Success Rate Percentage of successful jobs processed by the media server.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
613

Available reports
Backup Resource Success Rate Report
The Backup Resource Success Rate report lists the success rate for backup jobs for a
specific number of days for resources on selected servers. You can limit the amount of
data that appears in the report by entering range parameters for the Days option.
Information displayed in the Backup Success Rate by Resource report is described in the
following table.
Backup Resource Success Rate Report
Item Description
Resource Name of the system being protected.
Date Date the backup job was processed.
Backup Sets Total number of backup sets processed by the media server.
Successful Total number of jobs successfully performed by the media server.
Success Rate Percentage of successful jobs processed by the media server.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
614 Administrator’s Guide

Backup Set Details by Resource Report
Chapter 14, Reports in Backup Exec
Available reports
The Backup Set Details by Resource report lists all jobs that ran within the specified time
range on a selected server. The jobs are grouped by the server and resource. You can limit
the amount of data that appears in the report by entering filter parameters for the
Protected server option and range parameters for the Hours option.
Information displayed in the Daily Jobs by Resource report is described in the following
table.
Backup Set Details by Resource Report
Item Description
Resource Name of the system being protected.
Start Time Date and time the operation started.
Duration Length of time the operation took to process.
Size (MB) Number of megabytes processed.
Files Number of files processed.
Directories Number of directories processed.
MB/Minute Number of megabytes processed per minute.
Skipped Number of files skipped during the operation.
Corrupt FIles Number of corrupt files encountered during the operation.
Files in Use Number of files in use during the operation.
Status Status of the operation, such as Completed.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
615

Available reports
Backup Sets by Media Set Report
The Backup Sets by Media Set report lists all the backup sets by media set. You can limit
the amount of data that appears in the report by selecting filter parameters for the
Media Set option.
Information displayed in the Backup Sets by Media Sets report is described in the
following table.
Backup Sets by Media Sets Report
Item Description
Media Set Name of the media set on which the job ran.
Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned bar code label.
Set Sequential number for backup sets on the media.
Method Specific type of backup. For more information on backup methods, see
“Choosing a backup strategy” on page 306.
Date / Time Date and time the data was backed up.
Backup Set Description /
Source
Describes the data that was backed up and the location of the data.
Directories Number of directories backed up.
Files Number of files backed up.
MB Amount of data backed up in megabytes.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
616 Administrator’s Guide

Backup Size By Resource Report
Chapter 14, Reports in Backup Exec
Available reports
The Backup Size By Resource report lists the backup size for each resource job for up to
seven previous policy-based jobs run. It also computes the trailing average, which is the
average of the amount of data backed up in the seven previous jobs.
This report only shows jobs created by applying a policy to a resource. For information
about creating policies, see “Creating a new policy” on page 416. For information on
creating jobs with policies, see “Creating jobs using policies” on page 432.
You can limit the amount of data that appears in the report by entering filter parameters
for the Protected server option.
Information displayed in the Backup Size by Resource report is described in the
following table.
Backup Size by Resource Job Report
Item Description
Server Name of the media server where the data for the backup job was
located.
Resource Name of the resource backed up.
Job Name of the backup job.
Job Date and Time Run Date and time the backup job was processed.
Backup Size, MB Amount of data backed up in megabytes.
Trailing Avg, MB Average amount of data backed up during the seven previous runs.
Difference % Amount by which the data backed up in the current job differs from
the previous backup jobs.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
617

Available reports
Configuration Settings Report
The Configuration Settings report lists the contents of the Backup Exec system
configuration parameters table.
Information displayed in the Configuration Settings report is described in the following
table.
Configuration Settings Report
Item Description
Parameter Name Name of the Backup Exec configuration parameter.
Class Parameters that are associated with the Backup Exec system.
Value Value of the configuration parameter.
Note The StoreMaintenanceLastrun and StoreMaintenanceRuntime
parameters display the date and time in Greenwich Mean Time
(GMT).
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
618 Administrator’s Guide

Current Job Status Report
Chapter 14, Reports in Backup Exec
Available reports
The Current Job Status report provides details about the job queue sorted by status. You
can limit the amount of data that appears in the report by selecting filter parameters for
the Job status.
Information displayed in the Job Queue Status report is described in the following table.
Job Queue Status Report
Item Description
Job Status Displays the job status.
Job Name of the job.
Next Due Date Next date and time the job is scheduled to run.
Original Due Date Original date and time the job was scheduled to run.
Priority Job priority that determines which job runs first. If another job is
scheduled to run at the same time as this job, the priority you set
determines which job runs first. Available priorities include:
◆ Highest
◆ High
◆ Medium
◆ Lowest
◆ Low
On Hold Displays an X if the job is on hold; otherwise, displays a dash (-).
Type Type of job that was run, such as Backup or Restore.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
619

Available reports
Daily Network Device Utilization Report
The Daily Network Device Utilization report lists the percentage of the storage devices’
capacity that the media server uses.
Information displayed in the Daily Network Device Utilization report is described in the
following table.
Daily Network Device Utilization Report
Item Description
Drive Name Name of the storage device and the media server where the device is
located.
Date Date the storage device was used.
Jobs Number of jobs processed by the media server’s storage device.
Size (MB) Number of megabytes processed by the media server’s storage device.
Utilization (%) Percentage of device utilization.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
Device Summary Report
The Device Summary report lists all the devices for each selected media server. You can
limit the amount of data that appears in the report by selecting filter parameters for the
Media server option.
Information displayed in the Device Summary report is described in the following table.
Device Summary Report
Item Description
Server Name of the server where the device is located.
Device Name Name of the device, such as the name of the robotic library. This field
is left blank for stand-alone drives.
620 Administrator’s Guide

Device Summary Report (continued)
Item Description
Drive Name Name of the drive in the robotic library.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
Chapter 14, Reports in Backup Exec
Available reports
Vendor/Product ID Name of the vendor of the drive, the product ID, and firmware from
the SCSI Inquiry string.
SCSI Target Address of the SCSI Card, SCSI Bus, Target Device ID, and LUN.
State Device state, such as online.
Created Date media was created.
Cleaned Date last cleaning job was run on the drive.
Hours Hours the device has been in use since the last cleaning job.
Errors Number of errors occurring since the last cleaning job.
MB Megabytes read and written since the last cleaning job.
Mounts Number of mounts occurring since the last cleaning job.
Hours Total number of hours the device has been in use.
Errors Total number of errors occurring on the device.
MB Total number of megabytes read and written to the device.
Mounts Total number of mounts occurring to the device.
621

Available reports
Device Usage by Policy
The Device Usage by Policy report lists all the policies that are targeted to specific drive
selections. You can limit the amount of data that appears in the report by selecting filter
parameters for the Policy Name.
Information displayed in the Device Usage by Policy report is described in the following
table.
Device Usage by Policy Report
Item Description
Drive Name Name of the storage device and the media server where the device is
located.
Method Specific type of backup. For more information on backup methods, see
“Understanding backup methods and their advantages” on page 308.
Policy Name Name of the policy.
Template Name Name of the job template.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
Error-Handling Rules Report
The Error-Handling Rules report lists all error-handling rules and provides details about
each rule. You can limit the amount of data that appears in the report by selecting filter
parameters for the Media Server.
Information displayed in the Error-Handling Rules report is described in the following
table.
Error Handling Rules Report
Item Description
Rule Name Name of the Error-Handling rule.
Notes Information entered in the Notes section when the error-handling rule
was created.
622 Administrator’s Guide

Error Handling Rules Report (continued)
Item Description
Job Status Final job status that activates the rule. Possible statuses are:
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
Chapter 14, Reports in Backup Exec
◆ Error
◆ Canceled
Available reports
Error Category Category of error for which the rule will be applied. Available error
categories include:
◆ Device
◆ Job
◆ Media
◆ Network
◆ Other
◆ Resource
◆ Security
◆ Server
◆ System
Enabled Displays if the rule is enabled or disabled.
Cancel Job Displays an X if this option is selected for the error-handling rule. The
option cancels all jobs after the maximum number of retries have been
attempted.
Pause Job Displays an X if this option is selected for the error-handling rule. The
option enables Backup Exec to pause the job until you can manually
clear the error.
Retry Job Displays an X if this option is selected for the error-handling rule. The
option enables Backup Exec to retry the job.
Maximum Retries Number of times the job is to be retried.
Retry Interval (minutes) Number of minutes the job is to wait before being retried.
623

Available reports
Event Logs Report
The Event Logs report lists all Backup Exec and other system and application event logs.
Information displayed in the Event Logs report is described in the following table.
Event Logs Report
Item Description
Server Name of the server on which the event occurred.
Number Number assigned to the event in the Windows Event log.
Event Type of event that occurred.
Date Date the event occurred.
Time Time the event occurred.
Source Source from which the event originated.
Description Message displayed for the event.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
624 Administrator’s Guide

Event Recipients Report
Chapter 14, Reports in Backup Exec
Available reports
The Event Recipient report lists events registered by each notification recipient.
Information displayed in the Event Recipient report is described in the following table.
Event Recipient Report
Item Description
Recipient Type Type of recipient, such as Person, Net Send, Printer, or Group.
Recipient Name Name of the recipient.
Event Type Alert category or ad hoc job.
Event Name Detail for the alert category or ad hoc job.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
Failed Backup Jobs Report
The Failed Backup Jobs report lists all the failed backup jobs associated with a policy. The
jobs are sorted by the server and specified time frame. You can limit the amount of data
that appears in the report by entering filter parameters for the Protected server option
and range parameters for the Days option.
Information displayed in the Failed Backup Jobs report is described in the following
table:
Failed Jobs Report
Item Description
Resource Name of the system being protected.
Start Time Date and time the backup job started.
Duration Length of time the operation took to process.
Job Name Name of job that failed.
625

Available reports
Failed Jobs Report (continued)
Item Description
Category Category for the failed job that may be generated by a system, job,
media, or device error.
Error Code Displays the error code that corresponds to the failure.
Description Describes the event that caused the error.
Status Status of the operation, such as Completed.
Device Name Name of the device on which the job ran.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
Job Distribution by Device Report
The Job Distribution by Device report lists the jobs that have been run on each system
device during the specified period. It helps determine the device’s job workload. You can
limit the amount of data that appears in the report by selecting range parameters for the
Days option.
Information displayed in the Job Distribution by Device report is described in the
following table.
Job Distribution by Device Report
Item Description
Device Name of the device on which the job ran.
Job Date and Time Run Date and time the job was processed.
Job Name of the job that ran on the device.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
626 Administrator’s Guide

Jobs Summary Report
Chapter 14, Reports in Backup Exec
Available reports
The Jobs Summary report lists all jobs that have run within the specified time range. The
jobs are listed in chronological order. You can limit the amount of data that appears in
the report by selecting range parameters for the Hours option.
Information displayed in the Jobs Summary report is described in the following table.
Jobs Summary Report
Item Description
Start Time Date and time the operation started.
Job Name Name of the completed job.
Duration Length of time the operation took to process.
Size (MB) Number of megabytes processed.
Files Number of files processed.
Directories Number of directories processed.
MB/Minute Number of megabytes processed per minute.
Skipped Number of files skipped during the operation.
Corrupt FIles Number of corrupt files encountered during the operation.
Files in Use Number of files in use during the operation.
Status Status of the operation, such as Completed.
Type Specific type of backup. For more information on backup methods, see
“Understanding backup methods and their advantages” on page 308.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
627

Available reports
Machines Backed Up Report
The Machines Backed Up report lists all the protected servers and the times they were
backed up. You can limit the amount of data that appears in the report by selecting range
parameters for the Days option.
Information displayed in the Machines Backed Up report is described in the following
table.
Machines Backed Up Report
Item Description
Server Name of the server that was backed up.
Total Backup Count Total number of backups performed.
Last Backup Date of the last backup job for this server.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
Managed Media Servers Report
The Managed Media Servers report lists status and configuration information for all
media servers managed by Backup Exec. You can limit the amount of data that appears in
the report by selecting filter parameters for the Media Server option.
Information displayed in the Managed Media Servers report is described in the following
table.
Managed Media Server Report
Item Description
Managed Media Server Name of the managed media server.
Status Status of the server. Possible status includes:
◆ Online - available for use.
◆ Stalled - not responding immediately to messages
◆ No Comm - communications to the server have been lost for some
period of time.
628 Administrator’s Guide

Managed Media Server Report (continued)
Item Description
Related Topics:
“Running a report” on page 574
Chapter 14, Reports in Backup Exec
Available reports
Stalled Time limit used for determining Stalled communications status.
No Comm Time limit used for determining No Comm communications status.
Catalog Location Location where server keeps catalog information. Possible locations
are:
◆ Local - the catalog information is kept on the media server itself.
◆ CASO - the catalog information is kept on the Central Admin
Server.
Logs When job logs are uploaded from the managed server to the CASO
database. Possible upload times are:
◆ timed basis in seconds
◆ schedule time
◆ completion of job
◆ never
History When job history is uploaded from the managed server to the CASO
database. Possible upload times are:
◆ timed basis in seconds
◆ schedule time
◆ completion of job
◆ never
Status When status is uploaded from the managed server to the CASO
database. Possible upload times are:
◆ timed basis in seconds
◆ schedule time
◆ completion of job
◆ never
Display Alert Displays Yes if you have configured an alert to be set if time between
server clocks exceed a preset value (maximum time difference
tolerance).
Sec Maximum time difference tolerance in seconds set for server.
629

Available reports
“Running and viewing a new report job” on page 578
Media Required for Recovery Report
The Media Required for Recovery report lists the media that contain the backup sets for
each system backed up on the selected media server for the specified time period.
However, this report may be inaccurate if media overwrite settings allow the media to be
overwritten. You can limit the amount of data that appears in the report by selecting
filter parameters for the Protected server option and range parameters for the Days
option.
Information displayed in the Media Required for Recovery report is described in the
following table.
Media Required for Recovery Report
Item Description
Resource Name of the system that was backed up.
Type Specific type of backup. For more information on backup methods, see
“Understanding backup methods and their advantages” on page 308.
Date Date and time the backup job set was created.
Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned bar code label.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
630 Administrator’s Guide

Media Set Report
Chapter 14, Reports in Backup Exec
Available reports
The Media Set report lists all media sets and media used by Backup Exec servers. Usage
statistics are given for each piece of media. You can limit the amount of data that appears
in the report by selecting filter parameters for the Media set option.
Information displayed in the Media Set report is described in the following table.
Media Set Report
Item Description
Media Set Name of the media set.
Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned bar code label.
Media Type Type of media cartridge, such as 4mm.
Allocated Date media was allocated to a media set as a result of an overwrite
operation.
Modified Date data was last written to the media.
Location Location of the media.
Hours Total number of hours that this media has been in use.
Mounts Total number of times this media has been mounted.
Soft Errors Number of recoverable read errors encountered.
Hard Errors Number of unrecoverable read errors encountered.
Write MB Number of bytes that have been written to this media.
Current MB Estimate of the number of megabytes currently on this media.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
631

Available reports
Media Vault Contents Report
The Media Vault Contents report lists all the media in a specified media vault. You can
limit the amount of data that appears in the report by selecting filter parameters for the
Vault option.
Information displayed in the Media Vault Contents report is described in the following
table.
Media Vault Contents Report
Item Description
Vault Name Location of the media.
Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned bar code label.
Overwrite Protection End
Date
Vault Media Rule Move
Date
Date that data on the media may be overwritten.
Date media can be moved to vault.
Media Set Name of media set to which the media belongs.
Vault Media Rule Name Name of vault media rule.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
632 Administrator’s Guide

Missed Availability Report
Chapter 14, Reports in Backup Exec
Available reports
The Missed Availability report lists all jobs that have missed scheduled availability
windows within the specified time range. The jobs are listed in chronological order. You
can limit the amount of data that appears in the report by selecting range parameters for
the Hours option.
Information displayed in the Missed Availability report is described in the following
table.
Missed Availability Report
Item Description
Date Date and time the job was created.
Attempted Start Time Time Backup Exec attempted to start the job.
Job Name Name of the job.
Selection List Name of the selection list for the job.
Begin Time Date and time for beginning of availability window.
End Time Date and time for end of availability window.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
633

Available reports
Move Media to Vault Report
Lists all media that you can move to a media vault. The media listed are not currently in
a media vault and meets one of the following criteria:
■ The media has met or exceeded the vault move date specified for the media
containing the media.
■ The append period has expired, but the overwrite protection period is still current
(allocated).
You can limit the amount of data that appears in the report by entering filter parameters
for Media Server and range parameters for the Days option.
Information displayed in the Move Media to Vault report is described in the following
table.
Move Media to Vault Report
Item Description
Media Server Name of the media server where the data for the backup job was
located.
Media Set Name of the media set.
Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned bar code label.
Location Location of the media.
Append Period End Date Last date that data may be added to the media.
Overwrite Protection End
Date
Vault Media Rule Move
Date
Date that data on the media may be overwritten.
Date media can be moved to vault.
Vault Name Name of vault to which media is to be moved.
Vault Media Rule Name Name of vault media rule.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
634 Administrator’s Guide

Operations Overview Report
Chapter 14, Reports in Backup Exec
Available reports
The Operations Overview report lists details for past and future Backup Exec operations.
You can limit the amount of data that appears in the report by entering range parameters
for the Days or Event Count options.
Information displayed in the Operations Overview report is described in the following
table.
Operations Overview
Item Description
Job summary for jobs
completed in the past x
Hours
Details Backup Exec job activity for the specified time period.
Completed (Canceled) Total number of canceled jobs.
Completed (Failed) Total number of jobs that failed.
Completed (Success) Total number of jobs that completed successfully.
Exceptions Total number of jobs that completed successfully, but may contain one
or more skipped files, corrupt files, virus infected files or files in use.
Media Total Total number of media used to back up the completed jobs.
Total Size (MB) Total amount of data backed up.
Errors Total number of system, job, media, and device error alerts.
Warnings Total number of job, media, and device warning alerts.
Information Total number of system, job, media, and device information alerts.
Attention Required Total number of alerts that require a response from the user.
Scratch Media Total number of scratch media available.
Recyclable Total number of recyclable media available.
Allocated Number of allocated media (media belonging to a user media set).
Imported Number of imported media (media created by a product other than
this installation of Backup Exec).
635

Available reports
Operations Overview (continued)
Item Description
Appendable Media Total number of appendable media available.
Overwrite Protection
Level
Displays level of overwrite protection (Full, Partial, None) assigned to
the media.
Active Jobs Total number of active jobs.
Scheduled Total number of scheduled jobs.
Scheduled (On hold) Total number of scheduled jobs on hold.
Job Status Displays the job status.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
636 Administrator’s Guide

Overnight Summary Report
Chapter 14, Reports in Backup Exec
Available reports
The Overnight Summary report lists the results of backup jobs for each resource during
the last 24 hours. This report includes backup jobs that were due to run but did not run.
Jobs are given a grace period of 24 hours before being marked as past due. You can limit
the amount of data that appears in the report by entering filter parameters for the
Protected server option.
Information displayed in the Overnight Summary report is described in the following
table.
Overnight Summary Report
Item Description
Resource System being protected.
Type Specific type of backup. For more information on backup methods, see
“Understanding backup methods and their advantages” on page 308.
Start time Date and time the operation started.
Status Status of the operation.
Error Category Category for the job that may be generated by a system, job, media, or
device error.
Media Server Name of the media server on which the job ran.
Device Name Name of the device on which the job ran.
Total Tasks Total number of jobs run within the last 24 hours.
Uncorrected Exceptions Number of jobs that failed and were not run again with successful
completion.
Service Level Percentage of jobs that ran successfully.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
637

Available reports
Policy Jobs by Resource Summary Report
The Policy Jobs by Resource Summary report lists all of the backup sets that were created
within a selected period. The jobs are grouped by target server and resource. You can
limit the amount of data that appears in the report by selecting filter parameters for the
Protected Server and range parameters for the Hours option.
Information displayed in the Policy Jobs by Resource Summary report is described in the
following table.
Policy Jobs by Resource Summary Report
Item Description
Policy Name of the policy.
Start Time Date and time the operation started.
Duration Length of time the operation took to process.
Size (MB) Number of megabytes processed.
Files Number of files processed.
Directories Number of directories processed.
MB/Minute Number of megabytes processed per minute.
Skipped Number of files skipped during the operation.
Corrupt FIles Number of corrupt files encountered during the operation.
Files in Use Number of files in use during the operation.
Status Status of the operation, such as Completed.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
638 Administrator’s Guide

Policy Jobs Summary Report
Chapter 14, Reports in Backup Exec
Available reports
The Policy Jobs Summary report lists all jobs created from selected policies that have run
within a specified time range. The jobs are listed in chronological order. You can limit the
amount of data that appears in the report by selecting filter parameters for the Policy
Name and range parameters for the Hours option.
Information displayed in the Policy Jobs Summary report is described in the following
table.
Policy Jobs Summary Report
Item Description
Policy Name of the policy.
Start Time Date and time the operation started.
Job Name Name of the completed job.
Duration Length of time the operation took to process.
Size (MB) Number of megabytes processed.
Files Number of files processed.
Directories Number of directories processed.
MB/Minute Number of megabytes processed per minute.
Skipped Number of files skipped during the operation.
Corrupt FIles Number of corrupt files encountered during the operation.
Files in Use Number of files in use during the operation.
Status Status of the operation, such as Completed.
Type Specific type of backup. For more information on backup methods, see
“Understanding backup methods and their advantages” on page 308.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
639

Available reports
Policy Properties Report
The Policy Properties report lists all policies and policy job templates that are defined for
the media server.
Information displayed in the Policy Definitions report is described in the following table.
Policy Definitions Report
Item Description
Template Name Name of the job template.
Set Description Describes the data that was backed up and the location of the data.
Method Specific type of backup. For more information on backup methods, see
“Understanding backup methods and their advantages” on page 308.
Type Type of job that will run, such as Backup.
Device Name of the device on which the job will run.
Media Set Name of the media set on which the job will run.
Overwrite/Append The media overwrite protection option configured for the backup job
template properties.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
640 Administrator’s Guide

Policy Protected Resources
Chapter 14, Reports in Backup Exec
Available reports
The Policy Protected Resources report lists job information for each job derived from a
policy and assigned to protect any part of a named resource. You can limit the amount of
data that appears in the report by selecting filter parameters for the Protected server
option.
Information displayed in the Policy Protected Resources report is described in the
following table.
Policy Protected Resources Report
Item Description
Resource System being protected.
Policy Name of policy.
Job Name Name of the job.
Next Due Date Next date and time the job is scheduled to run.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
641

Available reports
Problem Files Report
The Problem Files report lists all the problem files reported for jobs. The files are
grouped by day and resource. You can limit the amount of data that appears in the report
by selecting filter parameters for the Protected server option and range parameters for
the Days option.
Information displayed in the Problem Files report is described in the following table.
Problem Files Report
Item Description
Date Date the problem file was encountered.
Resource System on which the problem file is located.
Time Time the problem file was encountered.
Reason Error code listed in the job log summary.
File Name Name of the problem file.
Type Specific type of file that caused the problem.
Media Server Name of the server on which the file is located.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
642 Administrator’s Guide

Recently Written Media Report
Chapter 14, Reports in Backup Exec
Available reports
The Recently Written Media report lists all the media that has been modified within the
specified period. You can limit the amount of data that appears in the report by selecting
range parameters for the Hours option.
Information displayed in the Recently Written Media report is described in the following
table.
Recently Written Media
Item Description
Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned bar code label.
Location Location of the media, such as the storage vault name or drive name.
Set Name of backup set.
Date and Time Modified Date and time media was last modified.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
643

Available reports
Resource Backup Policy Performance Report
The Resource Backup Policy Performance report lists the success rate for policy backup
jobs. You can limit the amount of data that appears in the report by selecting filter
parameters for the Protected Server option and range parameters for the Days option.
Information displayed in the Resource Backup Policy Performance report is described in
the following table.
Resource Backup Policy Performance
Item Description
Policy Name of policy.
Resource Name of system being protected.
Date Date job completed.
Backup Sets Total number of backup sets processed by the media server.
Successful Total number of jobs successfully performed by the media server.
Success Rate Percentage of successful jobs processed by the media server.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
644 Administrator’s Guide

Resource Risk Assessment Report
Chapter 14, Reports in Backup Exec
Available reports
The Resource Risk Assessment report shows job information for resources on which the
last backup job that was run on the resource failed. You can limit the amount of data that
appears in the report by selecting filter parameters for the Protected server option.
Information displayed in the Resource Risk Assessment report is described in the
following table.
Resource Risk Assessment Report
Item Description
Resource System on which the job ran.
Error Text Describes the event that caused the job to fail.
Start Time Time the operation started.
Job Name of the job that failed.
Error Category The category for the failed job that may be generated by a system, job,
media, or device error.
Media Server Name of the media server on which the job ran.
Device Name Name of the device on which the job ran.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
645

Available reports
Resources Protected by Policy report
The Resources Protected by Policy report lists the policies, templates, and selection lists
being used to protect a resource.
Information displayed in the Resources Protected by Policy report is described in the
following table:
Resources Protected by Policy Report
Item Description
Policy Name of the policy.
Resource The resource that is being protected.
Template Name The name of the job template contained in the policy that is applied to the
resource being protected.
Selection List The list of resources selected for protection
Job Name of the job.
Next Due Date Next date and time that the job is scheduled to run.
646 Administrator’s Guide

Restore Set Details by Resource Report
Chapter 14, Reports in Backup Exec
Available reports
The Restore Set Details by Resource report lists all restore jobs that ran within the
specified time range on a selected server. The jobs are grouped by the server and
resource. You can limit the amount of data that appears in the report by entering filter
parameters for the Protected server option and range parameters for the Hours option.
Information displayed in the Daily Jobs by Resource report is described in the following
table.
Backup Set Details by Resource Report
Item Description
Resource Name of the system being protected.
Start Time Date and time the operation started.
Duration Length of time the operation took to process.
Size (MB) Number of megabytes processed.
Files Number of files processed.
Directories Number of directories processed.
MB/Minute Number of megabytes processed per minute.
Skipped Number of files skipped during the operation.
Corrupt FIles Number of corrupt files encountered during the operation.
Files in Use Number of files in use during the operation.
Status Status of the operation, such as Completed.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
647

Available reports
Retrieve Media from Vault Report
The Retrieve Media from Vault report lists all reusable media currently in a specified
media vault. You can limit the amount of data that appears in the report by selecting
filter parameters for the Vault option.
Information displayed in the Retrieve Media from Vault report is described in the
following table.
Retrieve Media from Vault Report
Item Description
Vault Name Name of the vault where the media is located.
Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned bar code label.
Overwrite Protection End
Date
Date that data on the media may be overwritten.
Move Date Date media can be moved to vault.
Media Set Name of the media set.
Vault Media Rule Name Name of vault media rule.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
648 Administrator’s Guide

Robotic Library Inventory Report
Chapter 14, Reports in Backup Exec
Available reports
The Robotic Library Inventory report lists the contents of slots in robotic libraries
attached to media servers. Usage statistics are provided for each piece of media. You can
limit the amount of data that appears in the report by selecting filter parameters for the
Media server option.
Information displayed in the Robotic Library Inventory report is described in the
following table.
Robotic Library Inventory Report
Item Description
Server Name of the server where the robotic library is located.
Device Name Name of the robotic library.
Slot Sequential number of the slot in the robotic library.
Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned bar code label.
State State of operation of the slot: paused, disabled, enabled, offline, or
online.
Modified Date the media in the slot was last accessed.
Write MB Number of bytes that have been written to this media.
Full Space available on a media; “1” indicates that media is full and “0”
indicates that there is space available on the media.
Hours Total number of hours this media has been in use.
Mounts Total number of times this media has been mounted.
Append The time remaining in the media’s append period.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
649

Available reports
Scheduled Server Workload
The Scheduled Server Workload report displays the estimated scheduled workload for a
server during the next 24-hour period or a user-defined time period. The report only
displays recurring jobs that have already run at least one time, not jobs scheduled to run
once. You can limit the amount of data that appears in the report by selecting filter
parameters for the Media server option and range parameters for the Hours option.
Information displayed in the Scheduled Server Workload report is described in the
following table.
Scheduled Server Workload Report
Item Description
Media Server Name of the media server that will process the scheduled jobs.
Job Name of the job scheduled to run.
Next Due Date Time and day the next job is scheduled to run.
Backup Size, MB Estimated amount of data in megabytes to be processed during the
next 24 hours.
Total Size (MB) Total amount of data to be processed on the server during the next 24
hours.
Total Size (MB) Total amount of data to be processed on all media servers.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
650 Administrator’s Guide

Scratch Media Availability Report
Chapter 14, Reports in Backup Exec
Available reports
The Scratch Media Availability report shows the aging distribution of media, how many
media are available for overwrite, and when other media will become available for
overwrite. You can limit the amount of data that appears in the report by selecting range
parameters for the Days option.
Information displayed in the Scratch Media Availability report is described in the
following table.
Scratch Media Availability Report
Item Description
Category The media set period configured in media set properties.
Media Label Media label assigned by Backup Exec, assigned by the administrator,
or contained on a pre-assigned bar code label.
Size (GB) Capacity of the scratch media available to which data can be written.
Available to Append (GB) Capacity of scratch media available for append.
Group Total Total number and capacity of scratch media available to the system.
Media Total Total number of scratch media available.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
651

Available reports
Test Run Results Report
The Test Run Results report displays the results for the test run jobs set for the selected
period and the selected media servers. You can limit the amount of data that appears in
the report by selecting filter parameters for the Media server option and range
parameters for the Hours option.
Information displayed in the Test Run Results report is described in the following table.
Test Run Results
Item Description
Media Server Name of the media server on which the job ran.
Job Date and Time Run Date and time the backup job was processed.
Job Name Name of the test run job.
Media Type Type of media used, such as 4mm.
Device Name Name of the device, such as the name of the robotic library.
Max Needed Amount of space needed on the media to run the job.
Online Capacity of media available in the device to which data can be
appended.
Media Total Total amount of appendable media available to the system.
Online Capacity of media available in the device to which data can be written.
Media Total Total amount of overwritable media available to the system.
Credential Check Indicates if the Backup Exec logon account was verified as correct for
the resources being backed up.
Backup Size, MB Size in megabytes of the backup.
Related Topics:
“Running a report” on page 574
“Running and viewing a new report job” on page 578
652 Administrator’s Guide

Chapter
Disaster preparation and
recovery
15
Disaster preparation planning is the implementation of strategies and procedures that
will minimize damage in the event a catastrophe destroys your data. While precautions
can be taken to minimize the effects of this type of occurrence (UPS devices, password
protection, and so forth), unfortunately there is nothing that can safeguard your data
100 percent.
The purpose of a Disaster Preparation Plan (DPP) is to return to an operational status as
quickly as possible. Backup Exec is a crucial component of the DPP and this section
discusses how to apply this powerful data management tool to your DPP.
There are two basic methods available for disaster recovery:
■ Manual recovery. This section provides procedures for manually recovering both
local and remote Windows 2003/XP/2000 computers.
■ Automated recovery. Backup Exec’s Intelligent Disaster Recovery (IDR) option
automates the disaster recovery process for Windows Server 2003/XP/2000
computers. IDR is an option you must purchase separately.
Related Topics:
“Symantec Backup Exec Intelligent Disaster Recovery Option” on page 1501
“Returning to the last known good configuration” on page 655
“Manual disaster recovery of Windows computers” on page 658
653

Key elements of a disaster preparation plan (DPP)
Key elements of a disaster preparation plan (DPP)
The DPP you put in place with your Backup Exec system should be tailored to your
network environment. While environments vary in different organizations, there are
five elements to consider when creating a comprehensive DPP.
Disaster preparation plan elements
Element Description
Hardware protection The hardware devices on your network (CPUs, drives, video) are susceptible
to damage from many disaster situations. Uninterruptible power supplies
(UPS), surge protectors, and security monitoring devices are the equipment
most often used today to protect hardware. If you do not already have these
items in place, you should consider installing them. The initial investment
could be justified many times over in the event of a disaster.
The ability to
maintain business
operations during a
disaster period
A sound backup
strategy.
Off-site storage of
backups.
Effective DPP
management
Make sure that proper precautions are taken by everyone to implement
plans for network interruptions. For example, the phones in the sales
department won’t stop ringing because the server is down, so orders may
have to be handwritten until the server is up again. Each department
should work out strategies for such occurrences. If the proper precautions
are taken, the server can be rebuilt quickly and operations can still
continue.
A well-designed backup strategy that includes a strong media rotation
scheme plays a key role in quickly restoring your file server.
It is imperative that backed up data be moved off-site regularly. This
ensures that if something happens to your facility, all of your backups will
not be destroyed. Depending on the importance of your data, you may
choose to use several off-site storage facilities. There are companies that
provide off-site storage services that pick up and deliver tapes when they
are to be rotated.
The last element - and possibly the most important - is proper
management of your DPP strategy. A person or group of people should be
charged with constantly supervising your organization’s disaster
preparation efforts. Someone should install and maintain hardware
protection devices, make sure all departments have a plan if the server goes
down temporarily, and make sure that backups are made and rotated
off-site regularly. Also, it is a good idea to document your Disaster
Preparation Plan for reference purposes.
654 Administrator’s Guide

Chapter 15, Disaster preparation and recovery
Returning to the last known good configuration
Backup Exec plays a major role in your DPP by offering an easy, reliable way of
backing up and restoring your files. The rest of this chapter describes how to take
some precautionary measures to make restoration as straightforward as possible in
the event of a disaster.
Related Topics:
“Selecting data to back up” on page 315
Returning to the last known good configuration
Changes to the system configuration may keep the system from booting. If you suspect
that boot problems are the result of a configuration change, you may be able to correct
the problem by returning to a previous configuration. This method is simple and fast,
and in some cases will correct boot problems in a Windows computer. There are slightly
different procedures for Windows 2000/XP/Windows Server 2003 computers. This
section includes procedures for each type of computers.
Any changes made to the system since the last time the configuration was saved are lost.
To return to a previous configuration
1. Restart the system.
2. Press during startup.
3. Select one of the following options:
Safe Mode This option allows you to diagnose and fix system startup
problems. For more information, see your Microsoft
documentation.
Last Known Good
Configuration
Related Topics:
“Creating a hardware profile copy” on page 656
“Creating an emergency repair disk” on page 657
This option allows you to return to a previous saved configuration.
655

Returning to the last known good configuration
Creating a hardware profile copy
Before making a major hardware change, copy the current hardware profile to a new
hardware profile and boot into the new profile before adding or changing the hardware.
This way, you can return to the previous configuration if something does not work
properly.
To create a copy of the current hardware profile and make that the preferred boot option
1. Right-click the My Computer icon.
2. Click Properties to display the System Properties dialog box.
3. Click Hardware.
4. Click Hardware Profiles.
5. Select the current hardware profile, and then click Copy.
6. Type the name for the new configuration in the To field, and then click OK.
7. To make the new profile the preferred boot option, select it, and then click the up
arrow next to the list box to move the new hardware profile to the top of the box.
8. Choose whether Windows is to use the new hardware profile automatically (after a
delay) during startup, or if the system should wait indefinitely until the hardware
profile is chosen by selecting the appropriate option.
9. Click OK.
The new configuration is saved, and the startup options are set.
Related Topics:
“Returning to the last known good configuration” on page 655
“Creating an emergency repair disk” on page 657
656 Administrator’s Guide

Creating an emergency repair disk
Chapter 15, Disaster preparation and recovery
Creating an emergency repair disk
When Windows 2000 Server is installed, the installation program prompts you to create
an Emergency Repair Disk (ERD). This disk contains system information that can help
get the system running in the event of a disaster. It is important to keep the ERD updated
whenever system changes are made. The ERD is only useful if it is kept current.
For Windows XP or Windows Server 2003, Emergency Repair Disk has been replaced
with Automated System Recovery (ASR).
Whenever a major change is made to the system, make a fresh copy of the ERD before
and after the change is made. Major changes include adding, removing, or otherwise
modifying hard drives or partitions, file systems, configurations, and so forth. As a
general rule, update the ERD before and after the hard drive configuration is changed.
The addition of a new component to the server, such as Microsoft Exchange Server or
Microsoft SQL Server, and changes from Control Panel, are also situations in which the
ERD should be refreshed both before and after the change.
Also remember to make a backup of the ERD; always keep an ERD from at least one
generation back. When creating a fresh ERD, use a floppy disk that can be reformatted,
because RDISK.EXE, the program that creates the ERD, always formats the floppy disk.
Note The Emergency Repair Disk is a useful and necessary tool; it is NOT a bootable
disk. There is not enough space on the disk for the boot files and the repair
information files.
To create the ERD for Windows 2000
You must not change or delete the systemroot\repair folder because the repair process
relies on information saved in this folder.
1. Click Start> Programs> Accessories> System Tools> Backup.
2. Click Tools> Create an Emergency Repair Disk.
3. Insert a disk into the A: drive and follow the instructions.
The Also back up the registry to the repair directory option saves your current
registry files in a folder within the systemroot/repair folder. This option is beneficial
in the event your hard disk fails and you need to recover your system.
Related Topics:
“Returning to the last known good configuration” on page 655
“Creating a hardware profile copy” on page 656
“Creating an emergency repair disk” on page 657
657

Manual disaster recovery of Windows computers
Using Windows’ Automated System Recovery and System
Restore to recover a Windows XP or Windows Server 2003
system
The ASR feature, which replaces the Emergency Repair Disk for Windows XP and
Windows Server 2003, allows you to restore the operating system to a previous state so
that you can start Windows XP Professional or Windows Server 2003 when other
recovery methods do not work.
Microsoft recommends using System Restore, which saves only incremental changes and
lets you start Windows XP Professional in normal or safe mode, before resorting to ASR.
For more information about ASR or System Restore, refer to your Microsoft
documentation.
Related Topics:
“Manual disaster recovery of Windows computers” on page 658
Manual disaster recovery of Windows computers
Note If your system is protected by Backup Exec for Windows Servers Intelligent
Disaster Recovery (IDR), see “Symantec Backup Exec Intelligent Disaster Recovery
Option” on page 1501 for information on automated disaster recovery. The
procedures described in the following sections allow you to manually recover a
computer not protected by IDR.
Different types of computers require different disaster recovery procedures. This section
includes separate procedures for recovering the following types of computers:
■ Local Windows computer (see “Manual disaster recovery of a local Windows
2000/XP/Server 2003 computer (includes non-authoritative and authoritative
restore of Active Directory for a domain controller)” on page 659).
■ Remote Windows computer (see “Disaster recovery of a remote Windows
2000/XP/Server 2003 computer (includes non-authoritative and authoritative
restore of Active Directory for a domain controller)” on page 663).
These procedures will restore your computer’s operating system to its pre-disaster state
and will restore your data files, except those protected by one of the Backup Exec agents.
Use these disaster recovery procedures in the following situations:
■ The Windows operating system has become corrupted and cannot be restored using
the Emergency Repair Disks.
658 Administrator’s Guide

Chapter 15, Disaster preparation and recovery
Manual disaster recovery of Windows computers
■ The hard drive containing the Windows operating system has encountered an
unrecoverable error that requires reformatting the disk.
■ The hard drive containing the Windows operating system needs to be replaced.
Related Topics:
“Disaster recovery of a remote Windows 2000/XP/Server 2003 computer (includes
non-authoritative and authoritative restore of Active Directory for a domain controller)”
on page 663
Manual disaster recovery of a local Windows 2000/XP/Server
2003 computer (includes non-authoritative and authoritative
restore of Active Directory for a domain controller)
This procedure will restore your computer’s operating system to a pre-disaster state and
will restore your data files, except those protected by one of the Backup Exec database
agents, such as the Exchange Agent or SQL Agent. If any of your data is protected by
Backup Exec agents, refer to the section on restoring the data protected by the agent
before beginning disaster recovery.
If your system is protected by Backup Exec for Windows Servers Intelligent Disaster
Recovery (IDR), see “Symantec Backup Exec Intelligent Disaster Recovery Option” on
page 1501 for information on automated disaster recovery. The procedure described in
the following section allows you to manually recover a computer not protected by IDR.
A media drive must be attached to the computer that is being recovered. You will also
need:
■ A current full backup of the computer to be recovered and any subsequent
incremental/differential backups.
■ The Windows 2000/XP/Server 2003 installation media.
■ The Backup Exec for Windows Servers installation media.
To manually recover a local Windows 2000/XP/Server 2003 computer
1. Install Windows 2000/XP/Server 2003.
This basic Windows installation is necessary to provide Backup Exec with a target to
which it can restore the system. The computer name, Windows directory, and the
file system (such as NTFS) must be the same as the previous Windows installation.
This installation will be overwritten by the backed up version, which will restore
your original system configuration, application settings, and security settings.
659

Manual disaster recovery of Windows computers
If you are recovering from an entire hard disk failure, use Windows setup to
partition and format the new disk during installation. Format the partitions with the
same file system as before the failure.
■ If the system was in a specific domain or workgroup, do not join the domain or
workgroup at this time.
■ If you are recovering a domain controller, do not perform the domain controller
installation process at this time.
2. Install Backup Exec for Windows Servers to a directory other than where it was
originally installed (this is a temporary installation).
Always log on to Windows using the Administrator account or its equivalent during
this procedure.
3. Using the Device Configuration Wizard, install the appropriate device driver for the
attached media drive. For more information, see “Using the Getting Started with
Backup Exec page” on page 132.
4. Start Backup Exec for Windows Servers.
5. From the navigation bar, click Devices.
6. Inventory the media containing the latest full backup of the computer to be
recovered (see “Inventorying media” on page 238).
7. Catalog the media containing the latest full backup of the computer to be recovered
(see “Cataloging media while reviewing devices or media” on page 284). If the
subsequent differential/incremental backups are on separate media, catalog those
also.
8. From the navigation bar, click Restore.
9. Select all sets from the full and incremental backups that contain logical drives on
the hard disk. If differential backup sets are to be restored, select only the last
differential set. Make sure you include System State or Shadow Copy components as
part of the restore selections.
10. On the Properties pane, under Settings, click General, and then select the following
options:
■ Restore over existing files
■ Restore security
■ Preserve tree
660 Administrator’s Guide

Chapter 15, Disaster preparation and recovery
Manual disaster recovery of Windows computers
11. On the Properties pane, under Settings, click Advanced, and then select the
appropriate options (see “Advanced options for restore” on page 494).
If you are restoring a computer that is the only domain controller in the domain or
the entire domain is being rebuilt and this is the first domain controller, select the
option Mark this server as the primary arbitrator for replication when restoring
folders managed by the File Replication Service, or when restoring SYSVOL in
System State.
12. Click Run Now.
13. If you are restoring a computer that is the only domain controller in the domain or
the entire domain is being rebuilt and this is the first domain controller, reboot the
computer after the restore job successfully completes.
Your computer’s operating system is now restored to a pre-disaster state. Your data files
have been restored, except those protected by Backup Exec database agents.
14. Continue with one of the following:
If you are performing an
authoritative restore
If you are not performing
an authoritative restore
15. Change the Backup Exec services to the local system account.
■ Right-click My Computer and then select Manage.
■ From the left pane of the Computer Management utility, double-click Services
and Applications.
■ Click Services.
■ In the right pane, double-click each Backup Exec service, and from the Log On
tab, change Log on as to use Local System account.
■ Close the Computer Management utility.
16. Restart the computer.
go to step 15.
the recovery is complete.
17. Press during startup.
A menu appears that allows you to diagnose and fix system startup problems.
18. Select Directory Services Restore Mode.
661

Manual disaster recovery of Windows computers
19. Launch Backup Exec.
20. From the navigation bar, click Restore.
21. Select System State (Windows 2000 or Windows XP) or Shadow Copy (Windows 2003)
components as the restore selections. Run the Restore job.
22. At this point, you can either choose to restore the entire Active Directory, or specific
objects from the Active Directory:
Restore the entire Active Directory by performing the following:
■ Open a command prompt.
■ Type NTDSUTIL and press Enter.
■ Type Authoritative Restore and press Enter.
■ Type Restore Database, press Enter, click OK and then click Yes.
Restore specific objects from the Active Directory by performing the following:
■ Open a command prompt.
■ Type NTDSUTIL and press Enter.
■ Type Authoritative Restore and press Enter.
■ Type Restore Subtree "ou=.dc=,dc= (without
the quotation marks), and then press Enter, where is the name of
the organizational unit you want to restore, is the domain name
the OU resides in, and is the top level domain name of the domain
controller, such as com, org, or net. You can do this as many times for as many
objects you need to restore.
23. Once you have finished restoring Active Directory information, exit NTDSUTIL.
24. Restart the computer.
Related Topics:
“Restoring data by setting job properties” on page 488
“Disaster recovery of a remote Windows 2000/XP/Server 2003 computer (includes
non-authoritative and authoritative restore of Active Directory for a domain controller)”
on page 663
“Manual disaster recovery of Windows computers” on page 658
662 Administrator’s Guide

Chapter 15, Disaster preparation and recovery
Manual disaster recovery of Windows computers
Disaster recovery of a remote Windows 2000/XP/Server 2003
computer (includes non-authoritative and authoritative restore
of Active Directory for a domain controller)
You can perform disaster recovery on a remote computer attached to the media server.
This procedure will restore your computer’s operating system to its pre-disaster state
and will restore your data files, except those protected by one of the Backup Exec agents.
If any of your data is protected by Backup Exec agents, see “Backup Exec agents and
options” on page 62 before beginning disaster recovery.
If your system is protected by Backup Exec for Windows Servers Intelligent Disaster
Recovery (IDR), see “Symantec Backup Exec Intelligent Disaster Recovery Option” on
page 1501 for information on automated disaster recovery. The procedure described in
the following section allows you to manually recover a computer not protected by IDR.
You will need:
■ A current full backup of the computer to be recovered and any subsequent
incremental/differential backups.
■ The Windows 2000/XP/Server 2003 installation media.
Always log on to Windows using the Administrator account or its equivalent during this
procedure.
To manually recover a remote Windows 2000/XP/Server 2003 computer
At the remote computer:
1. Install Windows 2000/XP/Server 2003.
This basic Windows installation is necessary to provide Backup Exec with a target to
which it can restore the system. The computer name, Windows directory and the file
system (such as NTFS) must be the same as the previous Windows installation. This
basic installation will later be overwritten by the backed up version, which will
restore your system configuration, application settings, and security settings.
If you are recovering from an entire hard disk failure, use Windows setup to
partition and format the new disk during installation. Format the partitions with the
same file system as before the failure.
■ If the system was in a specific domain or workgroup, do not join the domain or
workgroup at this time.
■ If you are recovering a domain controller, do not perform the domain controller
installation process at this time.
At the media server:
663

Manual disaster recovery of Windows computers
2. Install the Backup Exec Remote Agent to the remote computer. For more
information, see “Installing the Remote Agent for Windows Systems” on page 97.
3. Start Backup Exec for Windows Servers.
4. From the navigation bar, click Devices, and then inventory the media containing the
latest full backup of the computer to be recovered (see “Inventorying media” on
page 238).
5. Catalog the media containing the latest full backup of the computer to be recovered.
If the subsequent differential/incremental backups are on separate media, catalog
those also (see “Cataloging media while reviewing devices or media” on page 284).
6. From the navigation bar, click Restore, and then select all sets from the full and
incremental backups that contain logical drives on the hard disk. If differential
backup sets are to be restored, select only the last differential set. Make sure you
include System State or Shadow Copy components as part of the restore selections.
7. On the Properties pane, under Settings, click General, and then select the following
options:
■ Restore over existing files
■ Restore security
■ Preserve tree
8. On the Properties pane, under Settings, click Advanced, and then select the
appropriate options (see “Advanced options for restore” on page 494).
If you are restoring a computer that is the only domain controller in the domain or
the entire domain is being rebuilt and this is the first domain controller, select the
option Mark this server as the primary arbitrator for replication when restoring
folders managed by the File Replication Service, or when restoring SYSVOL in
System State.
9. Click Run Now.
10. After the job completes, restart the remote computer.
Your computer’s operating system is now restored to its pre-disaster state. Your data files
have been restored, except those protected by Backup Exec database agents.
664 Administrator’s Guide

11. Continue with one of the following:
If you are performing an
authoritative restore
If you are not performing
an authoritative restore
Chapter 15, Disaster preparation and recovery
Manual disaster recovery of Windows computers
12. At the remote server, press during startup.
A menu appears that allows you to diagnose and fix system startup problems.
13. Select Directory Services Restore Mode.
14. At the media server, start Backup Exec.
15. From the navigation bar, click Restore.
16. Select System State (Windows 2000 or Windows XP) or Shadow Copy (Windows 2003)
components as the restore selections.
17. From the Properties pane, under Source, select Resource Credentials.
18. Highlight the restore selection for the remote server and click New.
19. Create a new logon account for this restore job. The account should have
administrator privileges on the remote server.
20. Select the new logon account and click OK.
21. Run the Restore job.
At the remote server:
go to step 12.
the recovery is complete.
22. At this point, you can either choose to restore the entire Active Directory, or specific
objects from the Active Directory:
Restore the entire Active Directory by performing the following:
■ Open a command prompt.
■ Type NTDSUTIL and press Enter.
■ Type Authoritative Restore and press Enter.
■ Type Restore Database, press Enter, click OK and then click Yes.
Restore specific objects from the Active Directory by performing the following:
665

Manual disaster recovery of Windows computers
■ Open a command prompt.
■ Type NTDSUTIL and press Enter.
■ Type Authoritative Restore and press Enter.
■ Type Restore Subtree "ou=.dc=,dc= (without
the quotation marks), and then press Enter, where is the name of
the organizational unit you want to restore, is the domain name
the OU resides in, and is the top level domain name of the domain
controller, such as com, org, or net. You can do this as many times for as many
objects you need to restore.
23. Once you have finished restoring Active Directory information, exit NTDSUTIL.
24. Restart the computer.
Related Topics:
“Restoring data by setting job properties” on page 488
“Manual disaster recovery of Windows computers” on page 658
666 Administrator’s Guide

Troubleshooting
Chapter
This section provides information on troubleshooting Backup Exec.
Note For more information, the Symantec Technical Support web site
(support.veritas.com) provides information on error messages, how
to/troubleshooting information and software downloads.
16
Problems can be caused by a number of conditions, so when you experience a problem
you will need to narrow the possibilities to solve it quickly. Use the following table to help
isolate the problem:
For storage hardware
problems:
If you receive an error
message in Backup Exec:
See “Hardware-related questions” on page 668.
See “Error messages” on page 671
For performance issues: See “Improving Backup Exec performance” on page 675.
For issues relating to
backing up data:
For issues relating to
restoring data:
To contact Technical
Support:
See “Backup questions” on page 672.
See “Restore questions” on page 675.
See “Contacting Technical Support” on page 678.
667

Hardware-related questions
Hardware-related questions
My drive is not listed in Backup Exec’s Devices list. The drive is connected, powered on and
recognized in the Windows Device Manager. What should I do?
First, make sure that your devices are supported by Backup Exec for Windows Servers.
Refer to the Hardware Compatibility List available on the Symantec support web site, at
http://support.veritas.com/menu_ddProduct_BEWNT_view_CL.htm .
If your device is listed on the Hardware Compatibility List, try running Backup Exec’s
Device Configuration wizard and installing Symantec device drivers (see “Configuring
storage devices by using the Device Configuration Wizard” on page 171). The Symantec
Device Driver Installation wizard will find and install the most suitable driver for your
storage device.
Note The Hardware Compatibility List is frequently updated with newly-supported
devices.
My drive appears as offline. Why?
If the device is offline, this message is displayed. No operations are allowed on the device
until it is online again. When the device is online, no message is displayed.
Backup-to-Disk folders may go offline if:
■ The drive containing the Backup-to-disk folder is full.
■ The drive containing the backup-to-disk folder is offline.
■ The remote server containing the Backup-to-disk folder is offline.
Other storage devices may go offline if:
■ The device was turned off after Backup Exec was started.
■ The device was being used by another application (such as a Windows
2000/XP/Server 2003 backup utility) when Backup Exec was started.
■ The device is removed from the computer.
■ A tape drive failure occurred (check the Event Log to troubleshoot the problem).
■ A tape is stuck in the drive.
■ The firmware of the drive was updated; Backup Exec will behave as if the drive with
its old name or identity no longer exists.
To place the device online, try the following:
■ Check to make sure the device has power and that cables are properly attached. Turn
the device on and reboot the server, or stop and restart the Backup Exec services.
668 Administrator’s Guide

Chapter 16, Troubleshooting
Hardware-related questions
■ Stop the utility that is using the device, and then reboot the server, or stop and
restart the Backup Exec services.
To restart the Backup Exec services:
From the Tools menu, select Backup Exec Services and then click the Restart all
services button.
If the drive’s firmware is updated or changed:
If the drive’s firmware has changed, delete the drive and restart Backup Exec services.
After the drive appears with its new firmware identity, retarget all jobs that were using
the old drive name to the new drive name.
I set up bar code rules through the Tools menu by selecting Options, and then selecting Bar
Code Rules. However, my bar code rules don’t seem to be working. Why?
After setting up bar code rules, you must perform two more steps in order for the bar
code rules to work.
1. You must enable the bar code rules for the robotic library by selecting the bar code
rules option on the Configuration tab in the robotic library’s properties.
2. In addition to setting the bar code rules for each type of media you use, for each drive
in your mixed media library you should indicate what type of media can be used and
whether that media can be used for read or write operations.
For more information, see “Bar code rules in mixed media libraries” on page 281.
How do I get the latest device drivers for my hardware?
The latest device drivers for Backup Exec can be found at
http://support.veritas.com/rd/bews-drivers.htm.
Backup Exec doesn’t detect my robotic library. What could be wrong?
Be sure that Windows 2000/XP/Server 2003 properly recognizes the device. This can be
verified by checking the Windows Device Manager. For configuration and setup
instructions, see “Symantec Backup Exec Library Expansion Option” on page 1539. You
may also want to read “Using Microsoft’s Removable Storage feature with Backup Exec”
on page 234.
I’m getting an error "Storage device [device] reported an error on a request to read/write
data to/from media. Error reported: Data error (cyclic redundancy check)." What should I
do?
The cyclic redundancy check (CRC) error can be caused by many factors. The following
list contains the most common reasons for this error and potential ways to resolve the
problem:
669

Hardware-related questions
1. Contaminated read/write heads of the tape device. Check with the hardware
manufacturer for proper cleaning techniques.
2. Bad media. Replace the media. Try a new tape that is certified by the hardware
manufacturer.
3. Tape driver. Load the appropriate Backup Exec tape driver. The latest Backup Exec
tape drivers can be downloaded from the Symantec Technical Support web site at
http://support.veritas.com/rd/bews-drivers.htm.
4. SCSI controller wide negotiation not configured properly. If the device is a wide (68
pin) SCSI device, then wide negotiation may and should be used. If the device is a
narrow (50 pin) SCSI device, disable wide negotiation. Use the manufacturer's SCSI
setup program to disable wide negotiation on the SCSI controller card.
5. SCSI controller transfer rate is too fast. Use the manufacturer's SCSI setup program
to lower the SCSI transfer rate. Check with the controller and backup device
manufacturer for the proper configuration for the SCSI transfer rate.
6. SCSI controller synchronous negotiation enabled. Use the manufacturer's SCSI setup
program to disable synchronous negotiation on the SCSI controller card. Check with
the controller and backup device manufacturer for the proper configuration for SCSI
synchronous negotiation.
7. Incorrect termination or bad cables. Verify that the SCSI cable is good and that it is
configured to provide proper SCSI termination. Do not mix passive and active
termination.
8. Confirm that the tape drive is functioning properly. Check with the tape drive
manufacturer for diagnostic software to test the condition of the tape drive
hardware.
9. General SCSI problems. Isolate the tape drive on its own controller card.
Why does my DLT tape drive hang when cataloging some tapes?
The DLT tape drive maintains internal information about the tape on a tape directory
track. The directory track is updated before the tape is ejected from the drive. If the drive
is powered off without ejecting the tape first, this information is lost.
Re-generating the tape directory information takes several hours to complete, which
makes it seem like the drive is hung. Allow sufficient time for the operation to complete
and then eject the tape. Normal operation will resume after the directory track has been
updated.
670 Administrator’s Guide

Chapter 16, Troubleshooting
Error messages
A backup to my DLT tape drive is stuck at 99% complete. What should I do?
The backup most likely fails to complete because the Eject media after job completes
option is selected on tape drives that require you to manually remove the tape (such as
Digital Linear Tape (DLT), Linear Tape-Open (LTO), Travan, and Onstream drives).
To remedy this situation, either deselect the Eject media... option or using BEUTILITY,
you can configure Backup Exec to set automatic responses to the media alert.
Related Topics:
“Configuring storage devices by using the Device Configuration Wizard” on page 171
“Error messages” on page 671
“Improving Backup Exec performance” on page 675
Error messages
Backup Exec generates an error message when a condition occurs that is important
enough to warrant your attention, or requires that you submit a response. Most alerts
and error messages are self explanatory, but there may be times when you need to get
more information to resolve an error condition. There are two ways to get more
information on Backup Exec error messages.
■ Look in the job log and follow the link for the Unique Message Identifier (UMI) error
message “Viewing Unique Message Identifier error codes in job logs” on page 459.
■ Search the Symantec technical support knowledge base for the error. From the Help
menu, click Symantec on the Web, and then select Search Knowledge Base.
Related Topics:
“Error-handling rules” on page 474
“Hardware-related questions” on page 668.
671

Backup questions
Backup questions
I am unable to back up certain files on my system that are being used by other processes.
Why is that?
When Backup Exec encounters a file that is in use by another process, it either skips the
file or waits for the file to become available, depending on the Backup open files setting.
When Backup Exec is configured to back up open files, it attempts to open the files in a
different mode. It locks these files while they are being backed up to prevent other
processes from writing to them. This mode should be a last resort to obtaining a backup
of open files; in most circumstances, it is more desirable to close applications that leave
files open so their files may be backed up in a consistent state.
If you want to back up open files on Windows computers, Backup Exec’s Advanced Open
File Option (sold separately) provides uninterrupted data protection for network
environments.
Why do Backup Exec’s consoles continue to own a storage device even when it's not
running?
Backup Exec is a true client/server application that must always be available to process
jobs submitted from both local and remote administrative consoles.
Because of the Advanced Device and Media Management functionality, all storage
devices attached to the media server are claimed by Backup Exec whenever the server is
running. The Advanced Device and Media Management feature in Backup Exec requires
constant control of the storage devices in order to perform two important and useful
operations: collection of statistics on media and device usage, and media overwrite
protection.
When performing a local backup, the total number of bytes backed up by Backup Exec does
not match the number of bytes displayed by Windows. Why?
This problem may be caused by the type of partition for which the system is formatted.
If you have a Windows NTFS compressed partition, Backup Exec displays the
uncompressed byte count of the files being backed up while Windows Explorer displays
the compressed byte count of the files on the hard drive. For example, a NTFS partition
that contains 1 GB of data is compressed by Windows to 500 MB. Backup Exec reports
that 1 GB of data was backed up, even though Windows Explorer displays that only 500
MB of compressed data exists on the hard drive.
If you have a FAT partition, Backup Exec reports the actual number of bytes of the files
being backed up while File Manager reports an inflated amount of disk space. For
example, a 2 GB FAT partition has a 32 K cluster size and File Manager displays 1.9 GB of
used space. Backup Exec reports that 1.4 GB of data was backed up. Assuming that a 50
MB pagefile.sys is excluded from the backup, there is a 450 MB difference in the number
of bytes.
672 Administrator’s Guide

Chapter 16, Troubleshooting
Backup questions
Converting to NTFS will regain disk space since it is more efficient and the default
cluster size (automatically set by Windows) in NTFS is less than FAT. Windows allows
you to specify a cluster size other than the default; however system performance may
decrease. For more information, see the Windows documentation.
The following tables display the cluster sizes for NTFS partitions.
NTFS Partition Cluster Sizes
Partition Size (MB) Cluster Size

Backup questions
What TCP/UDP ports does Backup Exec use?
TCP/UDP ports used by Backup Exec
Service or Process TCP/UDP Port
Backup Exec Agent Browser
(process=benetns.exe)
Backup Exec Remote Agent for Windows
Servers (process=beremote.exe)
Backup Exec Server
(process=beserver.exe)
MSSQL$BKUPEXEC
(process=sqlservr.exe)
TCP 6101
TCP 10000
TCP 3527
TCP 6106
TCP 1125
UDP 1434 (ms-sql-m)
Backup Exec Remote Agent for NetWare TCP 10000 (Backup Exec 10.x)
TCP 6102 (Backup Exec 9.x)
Oracle Agent for Windows and Linux
Servers
DB2 Agent for Windows and Linux
Servers
Remote Agent for Linux or Unix Servers
(RALUS)
Windows 98 & ME Agent, Version 10d or
earlier of the Oracle Agent, Macintosh
Agent, and Unix Agent.
Random port unless
configured otherwise
Random port unless
configured otherwise
Related Topics:
“Backing up data” on page 345
“Hardware-related questions” on page 668.
“Improving Backup Exec performance” on page 675.
Default NDMP port, typically
TCP 10000
TCP 6101
674 Administrator’s Guide

Restore questions
Chapter 16, Troubleshooting
Restore questions
Sometimes the byte counts for data that I restore don’t match the byte counts indicated
when the data was initially backed up. Why?
When data backed up from an NTFS volume is restored to an NTFS volume, the byte
count will match between the backup and restore operations. However, when data backed
up from a NTFS or FAT volume is restored to a FAT volume, the byte count restored is
expected to be less than that backed up. The reason for the discrepancy is that the
Windows returns a default ACL (access control list) for FAT data; the stream of data is
backed up (and the bytes are counted) but is discarded during a restore (and the bytes are
not counted).
Related Topics:
“Restoring data” on page 483
“Hardware-related questions” on page 668.
Improving Backup Exec performance
Many variables can affect throughput performance. These include:
Hardware The speed of the disk controller and hardware errors caused by the
disk drive, the tape drive, the disk controller, the SCSI bus, or the
improper cabling/termination can slow performance.
Confirm that the controller is rated for the tape backup hardware and
that the SCSI Bios Settings are set properly. Newer models of SCSI
Controllers are set to communicate with SCSI Hard Drives by default.
Most tape drives can only handle a maximum sync transfer rate (bus
speed) of between 3 to 22 MB/sec when utilizing hardware
compression. Speed in excess of this will not only affect the ability for
data to write to the tape in a continuous stream, but can also
potentially damage the tape hardware.
In addition, you should also make sure that:
◆ Enable disconnect and enable Sync Negotiation is set to NO (in
most cases).
◆ Initiate Wide Negotiation is set to Yes when the tape device is
connected to a 68 pin wide SCSI Cable Connector.
◆ Tape drives are not connected to a SCSI Raid Controller.
675

Improving Backup Exec performance
System The capacity and speed of the media server performing the backup, or
the remote system being backed up significantly impacts performance.
System activity during backup also impacts performance.
Fragmented disks take a longer time to back up. Heavily fragmented
hard disks not only affect the rate at which data is written to tape, but
also affect the overall system performance. Fragmented files take
longer to back up because each segment of data is located at a different
location on the disk, which causes the disk to take longer to access the
data. Make sure you defragment disks on a regular basis.
Memory The amount of available memory will impact backup speed.
Insufficient memory, improper page file settings, and a lack of
available free hard disk space will cause excessive paging and slow
performance.
For more information, see “System requirements” on page 79.
File Types The average file can potentially compress at a 2:1 ratio when hardware
compression is used. Higher and lower compression occur depending
on the type of files being backed up. Average compression can double
the backup speed, while no compression runs the tape device at its
rated speed.
Image and picture files are fully compressed on disks. Therefore, no
hardware compression takes place during the backup causing the tape
drive to operate at its native (non-compression) rate of speed.
Hardware compression is performed by the tape device and not the
backup software.
Compression Successful compression can increase the tape drive's data transfer rate
up to twice the native rate. Some tape drives use the Lempel-Ziv (LZ1)
compression algorithm for its superior versatility and efficiency.
Compression can be highly variable depending on your input data.
Compression algorithms look for repeatable data patterns that can be
compacted.
Image files from a graphical program like Microsoft Paint, may
compress at 4.5:1 or more, while binary files may compress at just
1.5:1. Data that has already been compressed or random data (such as
encrypted data or MPEG files) may actually expand by about five
percent if you attempt to compress it further. This can reduce drive
throughput.
Files The total number of files on a disk and the relative size of each file
impacts backup performance. Fastest backups occur when the disk
contains fewer large size files. Slowest backups occur when the disk
contains thousands of small files. A large number of files located in the
same directory path back up more efficiently than backing them up
from multiple directory locations.
676 Administrator’s Guide

Related Topics:
“Backing up data” on page 345
Chapter 16, Troubleshooting
Improving Backup Exec performance
Block Size Larger block sizes improve the compression ratio, which helps the
drive to achieve better throughput and more tape capacity. Make sure
that the block and buffer size are set properly. The throughput will
increase in proportion to the compression achieved, until the drive's
maximum throughput is reached. Symantec does not recommend
increasing the Block Size above the default settings.
Network The backup speed for a remote disk is limited by the speed of the
physical connection. The rate at which a remote server's hard disks are
able to be backed up depends on:
◆ The make/model of network cards.
◆ The mode/frame type configuration for the adapter.
◆ The connectivity equipment (hubs, switches, routers, and so on).
◆ Windows Settings.
Local disk drives on the media server can usually be backed up at a
higher rate of speed than backing up remote servers across a network.
677

Contacting Technical Support
Contacting Technical Support
If you have tried everything you can to solve a problem, but still need a resolution, you
can contact Technical Support by phone (see “Before calling Technical Support” on
page 678) or via the internet with Symantec DirectAssist (see “Using Symantec
DirectAssist for troubleshooting” on page 683).
Before calling Technical Support
To expedite the Technical Support process:
■ Know your Backup Exec version and revision number (see “Finding version and
revision information for your Backup Exec installation” on page 678)
■ Use one of the diagnostic utilities (see “Backup Exec diagnostic utilities” on
page 678) included with Backup Exec to collect information that technical support
can use to diagnose your issue.
Finding version and revision information for your Backup Exec
installation
Locally, the version and build information can be located by selecting the About Backup
Exec option from the Help menu.
Backup Exec diagnostic utilities
Backup Exec includes two utilities for compiling and gathering diagnostic information
that can help you, and if necessary technical support, troubleshoot issues with your
Backup Exec installation.
■ Bediag.exe generates a comprehensive diagnostic file that contains specific
environmental information such as service information, registry settings, user
privileges, and file versions. This diagnostic file can be used in conjunction with
many Symantec Backup Exec knowledge base articles to resolve your issue more
quickly. “Generating a diagnostic file for troubleshooting” on page 679
■ The Symantec Gather Utility (VxGather.exe) captures the most common diagnostic
and historical files necessary for troubleshooting purposes. By default the Symantec
Gather Utility will find Windows Event Logs, Backup Exec Installation logs, Backup
Exec internal application logs, and when present, the Symantec Gather Utility also
executes Bediag.exe. These files can then be used either by you or Symantec
Technical support to resolve your issue more quickly. See “Collecting log file
information for troubleshooting” on page 681.
678 Administrator’s Guide

Generating a diagnostic file for troubleshooting
Chapter 16, Troubleshooting
Contacting Technical Support
Backup Exec includes a diagnostic application (Bediag.exe) that gathers information
about a Windows XP, Windows 2000, or Windows Server 2003 computer for
troubleshooting purposes. You can run it from the media server, or from a remote
computer (see “Running Bediag on a remote computer” on page 681). This application
can be run from within Backup Exec, or it can be run from a command line. The Bediag
command line utility is located in the Backup Exec for Windows Servers directory on
your hard drive (by default, \Program Files\Symantec\Backup Exec).
The type of information collected in the bediag.txt file includes:
■ Account groups, account privileges and environment settings.
■ Backup Exec software version and registry information, Backup Exec Agent listing,
Windows version information, SCSI hardware configuration, SQL Server
information, Driver services information and Windows Services information.
■ Server information, supported shared directories and Windows sockets information.
Note You can also run BE Diagnostics for a remote server (see “Running Bediag on a
remote computer” on page 681)
To create a bediag.txt from within Backup Exec
1. Start Backup Exec.
2. On the Tools menu, select Backup Exec Diagnostics.
Note You can also create a bediag.txt file from the Device view. On the navigation bar,
click Devices. Select the media server. On the Task pane, under General Tasks,
click Properties. Then select the General tab.
3. Click Run Diagnostics. The bediag.txt file will appear.
From a command line prompt on the media server
1. Launch the command prompt.
2. From the directory Program Files\Symantec\Backup Exec\, type bediag
servername (the server can be the local media server or a remote server. If you are
running this from a workstation, type bediag workstationname).
3. The file “Bediag.txt” will be created in the directory containing Bediag.exe (by
default Program Files\Backup Exec\Symantec\).
679

Contacting Technical Support
4. The following switches can be used with the command line option (bediag
[switches] servername):
/a Dump Agent List
/b:[server] Specify a Backup Exec server to poll for service account information
/c Dump Backup Exec software configuration from the registry
/app Dump Application Event log
/sys Dump System Event log
/bex Dump only Backup Exec entries in the Application Event log
/err Dump only error events from any event log
/recs:n Dumps only newest n records from given event logs
***The bex, err and recs switches must be used in conjunction with the app
and/or sys switches
/o:[file] Specifies output job log for append
***Omitting [file] will send output to the screen
/h Dump SCSI hardware subkey from registry
/l Dump Lotus Notes information
/n Dump Windows Socket Network Protocols
/p Dump user privileges
/q Dump Microsoft SQL Server information
/s Dump information on Services
/u Dump Microsoft update information.
/v Dump Server Information
/w Dump Windows version information
/x Dump Microsoft Exchange Server Information
680 Administrator’s Guide

Running Bediag on a remote computer
You can run diagnostics on a remote media server provided:
■ Backup Exec is installed on the remote server.
Chapter 16, Troubleshooting
/? Display usage information
■ Backup Exec services are running.
To run BE diagnostics on a remote media server
1. On the Tools menu, click Backup Exec Diagnostics.
Contacting Technical Support
2. Click Select Server and select the remote media server on which you want to run the
diagnostic utility.
3. Enter the logon credentials for this remote system.
4. Click Run Diagnostics.
Diagnostic information appears in a .txt file.
Collecting log file information for troubleshooting
When troubleshooting an issue with Backup Exec, it may be necessary to review
diagnostic logs from the media server. The Symantec Gather Utility simplifies this
process by creating and compiling a compressed file that includes various system log
files that can be sent to technical support. You can run the Symantec Gather Utility
locally, or you can copy it to another computer.
Note To generate specific log file information or to get log file information for remote
computers, use Bediag.exe see “Generating a diagnostic file for troubleshooting”.
To collect log file information for troubleshooting
1. From the Backup Exec installation directory \Program Files\Symantec\Backup
Exec, double-click VxGather.exe.
2. Check all of the boxes in the Data to gather (if available) field.
681

Contacting Technical Support
3. Use the default Output root directory (required) or specify an alternate one.
If you want to use the
default directory.
If you know the
name of the
directory.
If you do not know
the name of the
directory.
Go to step 4.
4. Enter your case number with the dashes (example 123-456-789).
5. If there are additional files you want added to the compressed file enter them now.
If you know the
name of the file.
If you do not know
the file name.
Type the name of the directory.
Click Browse to browse to the correct
directory.
Type the file name in the Files text box,
and then click Add.
■ Click Browse to browse to the
correct file.
■ Select the file and then click
Open.
■ Click Add.
6. Click Gather.
After the Symantec Gather Utility collects all of the log file information, you will
have the option of viewing all of the data collected by the utility and sending the
results via email or FTP. The files gathered contain detailed information regarding
installation, diagnostics, and error reporting. Reviewing these logs prior to
contacting technical support can reveal the source of the issue. If the solution is not
evident based on the gathered logs, please have these logs available when contacting
support. The support technician may request an email containing the log files.
682 Administrator’s Guide

Using Symantec DirectAssist for troubleshooting
Chapter 16, Troubleshooting
Contacting Technical Support
Symantec DirectAssist is a support tool that you can install on your media server. It
securely gathers and analyzes data about your computer, which you can use to diagnose
and resolve issues. If the issue requires that you involve technical support, you can open
and track a case online through Symantec DirectAssist.
The self service features of Symantec DirectAssist are free. However, in order to submit a
case to Symantec Technical Services you must have either a support contract or an
incident number, which you can purchase from Symantec Technical Services.
To install Symantec DirectAssist:
❖ On the Help menu, click Symantec on the Web and then select Open DirectAssist
e-Support Case.
You will automatically be connected to the Symantec Technical Support site, where you
can learn more about Symantec DirectAssist and download the application.
Related Topics:
“Contacting Technical Support” on page 678
683

Contacting Technical Support
684 Administrator’s Guide

Symantec Backup Exec
Workstation Agents
Chapter
17
Symantec Backup Exec workstation agents let you protect drives and directories on the
workstation with Backup Exec. The Symantec Backup Exec workstation agents include
the following:
■ Backup Exec Windows 98/Me Agent
■ Backup Exec 8.x and 9.x Agent for Unix
The Backup Exec workstation agents are installed with Backup Exec. The files are copied
to the following directory on the media server:
Program Files\Symantec\Backup Exec\Agents
After installing Backup Exec, you can install the agent files from the media server to the
appropriate workstations, and then you can configure the following:
■ Locations on the workstation that you want the media server to access for
operations (published directories or drives).
■ Administrator level access to published directories and drives.
For example, you can assign a password to any directory or drive. Then, before the
directory or drive is backed up, the administrator provides the password. You can
also designate directories or drives as read-only, which prevents data from being
restored to those locations.
Related Topics:
“About the Backup Exec Windows 98/Me Agent” on page 686
“About the Backup Exec 8.x and 9.x Agent for Unix” on page 692
“About troubleshooting workstation agents” on page 699
685

About the Backup Exec Windows 98/Me Agent
About the Backup Exec Windows 98/Me Agent
The Backup Exec Windows 98/Me Agent supplied with Backup Exec provides several
features that are not included with the Microsoft Windows 98/Me agent, such as an
agent status window.
If an earlier version of the Backup Exec Windows 98/Me Agent is already installed on the
workstation, you must shut down the agent before upgrading it.
When the agent is installed, all local fixed disk drives on the workstation are published
at their root level without password protection. You can change the configuration to
publish other directories or to add password protection.
When configuring the Backup Exec Windows 98/Me Agent, you can set a password that
is required to back up from or restore to the published directories and drives on the
workstation. Your password can be up to 32 characters and can include upper- or
lower-case characters.
For Backup Exec 9.x and later, you must create a Backup Exec logon account that uses
the same password as the one you set when configuring the Backup Exec Windows
98/Me Agent. You must add the logon account for each workstation to gain access.
Related Topics:
“About the Backup Exec 8.x and 9.x Agent for Unix” on page 692
“About troubleshooting workstation agents” on page 699
Installing the Backup Exec Windows 98/Me Agent on the
workstation
Before installing the agent, the following requirements must be met:
■ You must have access to the Network option on the workstation’s Control Panel.
■ The server must run the TCP/IP network protocols.
To install the Backup Exec Windows 98/Me Agent on the workstation
1. Log on to the media server from the workstation.
2. Double-click Setup.exe.
The Setup.exe file is located in the following directory on the Backup Exec media
server:
Program Files\Symantec\Backup Exec\Agents\win9x\[language]
686 Administrator’s Guide

Chapter 17, Symantec Backup Exec Workstation Agents
About the Backup Exec Windows 98/Me Agent
Follow the instructions to complete the installation. After installation, you must
reboot the Windows 98/Me workstation for the agent to run properly.
Configuring the Backup Exec Windows 98/Me Agent
When the agent is installed, all local fixed disk drives on the workstation are published
at their root level without password protection. You can change the configuration to
publish other directories or to add password protection.
To configure the Backup Exec Windows 98/Me Agent
1. On the Windows Taskbar, click Start > Settings > Control Panel.
2. Double-click Network.
3. Click the Configuration tab.
4. In the list of installed network components, double-click Backup Exec Agent.
5. Select the appropriate options as follows:
Disable network backup Keeps the workstation from being backed up by the media
server. When Disable Network Backup is enabled, the agent
is not loaded when the workstation is started and the media
server does not recognize the computer as a published agent.
If you enable this option while the agent is running, the agent is
stopped.
Enable network backup Enables the media server to back up from or restore to the
workstation.
Computer name Identifies the workstation with an alphanumeric label (up to 36
characters). The default setting is the name used in the Windows
98/Me network.
687

About the Backup Exec Windows 98/Me Agent
Password Stores a password (up to 32 characters, upper- or lower-case)
required to back up from or restore to the workstation’s
published directories or drives.
To change a password, select this option, then type the new
password in the password field.
For Backup Exec 9.x and later, to access the workstation, you
must create a Backup Exec logon account that uses the same
password as the one typed here. The logon account user name is
ignored. Add this logon account for the workstation.
Current Status Displays the current status of the agent. Status messages
include:
◆ Not Running
◆ Idle
◆ Connected
Not Running indicates that the agent is either disabled or shut
down. Idle indicates the agent has loaded and is waiting for a
connection by a user or the media server. Connected indicates
that a user or the media server has connected to the agent and is
accessing it.
Allow Registry to be
restored
Name, Path, Access
Control
Allows the workstation’s Windows 98/Me registry to be
restored, if necessary.
Lists published directories and drives, or their aliases, and the
level of access assigned. The default setting is all local drives are
published.
Add Used to add directories and drives to the list of published
folders.
Remove Used to remove the selected directory or drive from the list of
published folders.
Details Used to change the access control for published folders.
Related Topics:
“Publishing drives and directories that use the Backup Exec Windows 98/Me Agent” on
page 689
“Configuring the network protocol for the Backup Exec Windows 98/Me Agent” on
page 690
“Editing a Backup Exec logon account” on page 150
“About troubleshooting workstation agents” on page 699
688 Administrator’s Guide

Chapter 17, Symantec Backup Exec Workstation Agents
About the Backup Exec Windows 98/Me Agent
Publishing drives and directories that use the Backup Exec
Windows 98/Me Agent
Before backing up information from drives and directories using the Backup Exec
Windows 98/Me Agent, you must publish drives and directories. When you publish the
drives and directories, you can protect them with a password or designate them as read
only. However, you cannot restore data to drives designated as read only. For each
workstation, you can list up to eight published folders.
To publish drives and directories that use the Backup Exec Windows 98/Me Agent
1. On the Windows Taskbar, click Start > Settings > Control Panel.
2. Double-click Network.
3. Click the Configuration tab.
4. In the list of installed network components, double-click Backup Exec Agent.
5. On the General tab, click Details.
6. Complete the appropriate options as follows:
Path Type the path to the folder you want to protect, or click Browse to
help locate a folder.
Folder Name (Optional) In Folder Name, type an alias that you want to use for
this folder.
Access Control (Optional) Sets or changes access control for a published folder, do
one of the following
Requires Password (PW) Password-protects a published folder. Using a password protects
the published folder from unauthorized backup.
Read Only (RO) Designates the folder as read-only. Clicking Read Only enables
only backup operations to be performed on the path; restore
operations are not allowed.
7. Click OK.
The drives and folders you selected display in the Published Folders window on the
Backup Exec Agent Properties dialog box.
689

About the Backup Exec Windows 98/Me Agent
Configuring the network protocol for the Backup Exec Windows
98/Me Agent
To use the Backup Exec Windows 98/Me agent, the computer on which Backup Exec is
installed must be running the TCP/IP communications protocol. You can use one
protocol or run them both simultaneously.
If you use TCP/IP, configure all computers using the Backup Exec Windows 98/Me Agent
to use their IP addresses.
To set up and run TCP/IP protocols on the media server, see your Microsoft Windows
documentation.
If you use Dynamic Host Configuration Protocol (DHCP) on a media server or a server
that is used for remote administration, and you use the Windows 98/Me Agent on
TCP/IP, you must be aware of the following:
■ When you use DHCP to dynamically configure the IP address of a host computer
that is running Backup Exec for Windows Servers, it is possible that a different IP
address will be assigned to the host computer each time it is restarted.
■ When you install the agent from the server to the workstation, the IP address
assigned to the Backup Exec Windows 98/Me Agent should match the IP address of
the computer running Backup Exec. If the host’s IP address changes each time it is
restarted, agent-to-host communication problems can occur.
■ You can use a DNS host name instead of an IP address to eliminate the need for a
static IP address.
■ To ensure that the Backup Exec Windows 98/Me agent consistently communicates
with the Backup Exec host computer, you should reserve an IP address for the host
running Backup Exec using the Windows DHCP Administrator program. See your
Microsoft Windows documentation for instructions.
To configure the network protocol for the Backup Exec Windows 98/Me Agent
1. On the Windows Taskbar, click Start > Settings > Control Panel.
2. Double-click Network.
3. Click the Configuration tab.
4. In the list of installed network components, double-click Backup Exec Agent.
5. Click the Protocol tab.
690 Administrator’s Guide

6. Select the appropriate options as follows:
Chapter 17, Symantec Backup Exec Workstation Agents
About the Backup Exec Windows 98/Me Agent
TCP/IP Configures the Backup Exec Agent for use with TCP/IP-based
networks. TCP/IP is the communications protocol typically used in
heterogeneous networks.
Configured Media
Servers
7. If you are using TCP/IP, click Add.
8. In the Adding Media Server box, type the host name or IP address of the media
server that is used to back up this computer.
9. Click OK.
Shows all previously configured media servers.
691

About the Backup Exec 8.x and 9.x Agent for Unix
About the Backup Exec 8.x and 9.x Agent for Unix
The Backup Exec 8.x and 9.x Agent for Unix lets Windows Server network
administrators perform backup and restore operations on UNIX workstations and
servers that are connected to the network. This agent must be running on the UNIX
device before backup or restore operations can be performed.
After the agent is configured and the UNIX device is restarted, the workstation is ready
for backup.
When backing up data using the Backup Exec 8.x and 9.x Agent for Unix, Backup Exec
lets you protect data using multiple backup types, that include the following:
■ Full - Back up files - Allow incrementals and differentials using modified time
■ Differential - Using modified time
■ Incremental - Using modified time
■ Working set - Back up files - Changed today
Related Topics:
“Understanding backup methods and their advantages” on page 308
“Requirements for running the Backup Exec 8.x and 9.x Agent for Unix” on page 692
“Installing the Backup Exec 8.x and 9.x Agent for Unix on the workstation” on page 693
“About the agent configuration file” on page 695
“About the Backup Exec Windows 98/Me Agent” on page 686
Requirements for running the Backup Exec 8.x and 9.x Agent for
Unix
Following are requirements for the Backup Exec 8.x and 9.x Agent for Unix:
■ You must have root privileges on the UNIX computer to install the UNIX agent.
■ TCP/IP is required on the media server.
■ The names and IP addresses of each media server used to access UNIX workstations
must be in the /etc/hosts file on the UNIX workstations.
692 Administrator’s Guide

Modifying the /etc/services files
To modify the /etc/services files
Chapter 17, Symantec Backup Exec Workstation Agents
About the Backup Exec 8.x and 9.x Agent for Unix
1. Edit the input file (/etc/services) for the map you want to change.
2. Add the following line, then save and exit the file:
grfs 6101/tcp # Backup Exec Agent
3. Type the following:
cd /var/yp
make services.byname
The make command updates the NIS map according to the changes made to the input
file, then propagates the changes to all other NIS servers on the network.
The Backup Exec 8.x and 9.x Agent for Unix is then installed by using ftp to push the
agent files from the server to the workstation.
Installing the Backup Exec 8.x and 9.x Agent for Unix on the
workstation
When you install the Backup Exec 8.x and 9.x Agent for Unix, you are prompted to
configure it as well. The agent configuration information is saved to a text file called
Agent.cfg that you can edit to change any configuration options.
Before installing the Backup Exec 8.x and 9.x Agent for Unix on a system using a
network name service (for example NIS), you must modify the network’s master
database /etc/services file. Make sure you have root privileges at the master server.
During the initial installation of Backup Exec, the Backup Exec 8.x and 9.x Agent for
Unix files are copied automatically from the Backup Exec installation CD to the
Program Files\Symantec\Backup Exec\Agents\UNIX directory on the media
server.
To install the Backup Exec 8.x and 9.x Agent for Unix on the workstation
1. Log on as root on the media server, and insert the Backup Exec installation CD into
the server’s CD-ROM drive.
2. Transfer the Be_agent.tar file to the Linux or UNIX workstation. Transfer methods
include FTP, NFS, SAMBA, and SCP.
693

About the Backup Exec 8.x and 9.x Agent for Unix
3. Push the Backup Exec 8.x and 9.x Agent from the media server to the workstation in
binary mode.
4. Change directory to the temporary directory on the workstation, and then type the
following:
put be_agnt.tar
5. At the workstation temporary directory prompt, type the following:
tar -xvf be_agnt.tar
6. Run the installation script by typing the following:
./INSTALL
7. If prompted, select a language, and then press Enter.
8. Accept or overwrite the agent installation location. The default location is the
following:
/etc/bkupexec.
9. Type a unique name not used by other Backup Exec 8.x and 9.x Agents for Unix for
the workstation on which you are installing the agent.
Unless you specify otherwise, the network node name is used.
10. Do one of the following:
■ Require a password for this workstation. If you do, you are prompted to type a
password.
■ Do not require a password.
11. Do one of the following:
■ If more than one network interface is available, specify the IP address of a local
network interface for the agent to use.
■ Do not specify the IP address. The agent uses an appropriate interface to
communicate with the media server.
12. Type the path to the directory to include in backup jobs.
13. Type a unique resource name for each published path.
14. Do one of the following:
■ To allow files to be restored to a published path, type y.
694 Administrator’s Guide

Chapter 17, Symantec Backup Exec Workstation Agents
About the Backup Exec 8.x and 9.x Agent for Unix
■ To prevent files from being restored to the published path, type n.
15. Do one of the following:
■ Require a password for each published path.
If you choose to password-protect the path, the password is required before
Backup Exec can perform operations on this path.
■ Do not require a password for each published path.
16. Repeat steps 9-15 to publish directory paths.
17. Type the names of the media servers that will back up your workstation.
18. Accept the default setting of 30 seconds, or type the frequency (in seconds) with
which the agent sends advertisement messages to the media server indicating that
the workstation is accessible.
19. Choose one of the following methods to back up symbolic links:
Method 1 The symbolically linked directory is handled as a special file and
only the information required to create the symbolic link is
backed up.
Method 2 The symbolically linked directory is backed up as a normal
directory. All files and subdirectories within the symbolically
linked directory are also backed up.
About the agent configuration file
The first portion of the Agent.cfg file contains instructions that define and explain each
of the configuration lines. The actual agent configuration commands are found at the
end of the file.
You can edit the agent configuration file, agent.cfg using any text editor.
By default, the Agent.cfg file is installed on each UNIX agent workstation in the
/etc/bkupexec subdirectory.
For Backup Exec 9.x and later, to access the workstation, you must create a Backup Exec
logon account that uses the same password as the one typed here. The logon account
user name is ignored. Add this logon account as the resource credential for the
workstation.
See “Configuring logon accounts” on page 146 and “About selection lists” on page 327.
695

About the Backup Exec 8.x and 9.x Agent for Unix
For problems encountered when passwords are changed, see “About troubleshooting
workstation agents” on page 699.
The following table lists the commands and parameters used with the Backup Exec UNIX
Agent.cfg file. Parameters within brackets [ ] are optional.
Agent.cfg commands and parameters
Command Description
name Use this command to change the name of this workstation. This
name appears in the Backup Exec selection screens. This item is
optional.
If a workstation name is not provided, the workstation’s network
node name (for example, uname -n) is used.
password Use this command to assign a password to this workstation. If you
assign a password, the Backup Exec administrator must type the
password to access this workstation. If a password is not provided
during installation, the Backup Exec administrator must press
Enter when prompted for a password. This item is optional.
696 Administrator’s Guide

Agent.cfg commands and parameters
Command Description
Chapter 17, Symantec Backup Exec Workstation Agents
About the Backup Exec 8.x and 9.x Agent for Unix
export Use this command to specify the directory tree to publish so that
it is accessed by Backup Exec. The following commands are used
with export:
◆ - Use this command to identify the exported
paths of the agent workstation. This name appears in the
Backup Exec Networks window under Backup Exec Agents.
◆ [write_protected] - Use this command if you want the
published path to be accessed for backup operations but not
for restore operations.
◆ - Use this command to assign a password to a
specific published path. The Backup Exec administrator is
required to type the password before the published path can be
accessed by backup operations.
◆ [include_remote]- Use this command to access remotely
mounted (NFS) file systems through their normal mount
points.
export / as ROOT include_remote
◆ - Use this command to prevent locking of
files during backup operations if they are located in remotely
mounted file systems with mount points within a directory
tree.
Example:
export as
[write_protected] [password ]
[include_remote][no_nfs_locking]
tell Use this command to specify a media server name as an argument.
This server name is added to the list of computers to which
advertisements will be sent. This machine name must be found in
the /etc/hosts file.
tell_interval
Use this command to specify the number of seconds the agent
waits before re-advertising itself to the media server. If you type a
number other than the default setting (30 seconds), the number
should not be more than a few minutes or less than 60 seconds.
Longer numbers cause a delay in the workstation’s network
broadcast verification and shorter numbers cause excessive
network traffic. Each advertisement transaction requires eight (8)
network packets.
697

About the Backup Exec 8.x and 9.x Agent for Unix
Agent.cfg commands and parameters
Command Description
follow_symdirs Use this command to specify that the contents of the linked
directories be backed up but not the symbolic links themselves. By
default, the contents of symbolically linked directories are not
backed up, but the symbolic links themselves are.
exclude_file Use this command to specify individual files that are never backed
up. The must include a fully specified path, and
wildcards are not permitted.
exclude_dir Use this command to exclude individual directories or directory
trees from being backed up. The must be fully
specified.
preserve_ctime Use this command to force the agent to ignore the message which
sets object’s (files and directories) attributes when a backup
occurs. Normally, during a backup, the backup engine preserves
an object’s last access timestamp by resetting the last access
timestamp to the value before the backup occurred. When the
agent modifies the objects’ last access timestamp, the OS
internally updates the object’s “ctime.” An object’s ctime is the
time when an object’s attributes (permissions, timestamps, etc.)
were modified. By not resetting the attributes after a backup, the
object’s ctime is not updated. This option does not affect object
attributes set during restore jobs.
Loading the Backup Exec 8.x and 9.x Agent for Unix
If the Agent.cfg file is not located in the Backup Exec 8.x And 9.x Agent for Unix
installation directory, use the -c parameter in conjunction with a path to the location of
the Agent.cfg file when loading the agent. For example,
/etc/bkupexec/./agent.be -c &
To load the Backup Exec 8.x and 9.x Agent for Unix
❖ Use the following command to load the agent:
/etc/bkupexec/./agent.be &
698 Administrator’s Guide

About troubleshooting workstation agents
Chapter 17, Symantec Backup Exec Workstation Agents
About troubleshooting workstation agents
If you change the password for a published directory on a workstation, the directory
cannot be accessed for Backup Exec jobs. Additionally, the Change option on the
Resource Credentials dialog box becomes unavailable. If you encounter this problem, do
any of the following:
■ Modify the job by clearing the selection of the specified published directory, and
then reselecting it. You are prompted for new credentials.
■ Update the corresponding logon account credentials stored in Backup Exec with the
new password for the published directory.
■ At the workstation, disable access to published directories that use passwords and
configure the workstation itself to require password authentication.
Related Topics:
“About the Backup Exec Windows 98/Me Agent” on page 686
699

About troubleshooting workstation agents
700 Administrator’s Guide

Chapter
Using Symantec Backup
Exec with Server Clusters
18
In a server cluster, Backup Exec can protect data on local disks and shared disks, as well
as protect Microsoft SQL and Exchange databases that are configured as virtual server
applications; that is, they contain an IP address resource, a Network Name resource, and
are displayed on the network with a unique server name (the virtual server name).
Clustered servers provide high availability of applications and data to users. In a
clustered server, several servers (called nodes) are linked in a network, and run cluster
software that allows each node access to the shared disks. If a node becomes
unavailable, cluster resources migrate to an available node (called failover). The shared
disks and the virtual server are kept available. During failover, users experience only a
short interruption in service.
Note For offhost backups that use the hardware provider in a Microsoft Cluster Server
(MSCS) or Veritas Cluster Services environment, the media server and the remote
computer must be in different cluster groups. The cluster applications cannot
support devices’ logical unit numbers (LUNs) that have duplicate signatures and
partition layouts, therefore, the snapshots containing the LUNs must be
transported to a host, or remote computer, that is outside the cluster.
Related Topics:
“Installing Backup Exec on a Microsoft Cluster Server” on page 704
“Configurations for Backup Exec and Microsoft Cluster Servers” on page 715
“Backing up Microsoft Cluster Servers” on page 725
“About Restoring data to a Microsoft cluster” on page 729
“Requirements for installing Backup Exec on a Microsoft Cluster Server” on page 703
“Disaster recovery of a cluster” on page 746
“Installing Backup Exec with the CASO option on a Veritas Cluster Server” on page 737
701

How Backup Exec works in a Microsoft Cluster Server
“About Backing up Veritas Cluster Servers” on page 741
“About Restoring data to Veritas Cluster Servers” on page 745
How Backup Exec works in a Microsoft Cluster Server
When you install Backup Exec into a Microsoft Cluster Server (MSCS) environment, you
install it as a virtual server application. You assign an IP address resource, a Network
Name resource (the virtual server name), and a disk resource to Backup Exec.
When a failover occurs, backup jobs that were running are rescheduled. The Backup
Exec services are restarted on a designated failover node, and the backup jobs are
restarted by default. Backup Exec provides an additional rule for cluster failover restart
called Checkpoint Restart. A checkpoint restart option allows backup jobs to continue
from the point at which the jobs were interrupted rather than starting the backup over
again, making the backups faster and requiring fewer media. If the rule to retry jobs on a
cluster failover is enabled, then an additional option can be specified to do a checkpoint
restart when retrying the job. Checkpoint Restart is the only property available for the
Cluster Failover Rule. You can change the default so that jobs are not restarted.
When the failed server comes back online, MSCS can automatically rebalance the
workload in a cluster, called failback, by moving cluster groups back to the server that
has rejoined the cluster. However, by design, Backup Exec does not failback. The backup
jobs will continue to run on the designated failover node. By continuing to run backup
jobs on the designated failover node, any further risk of having to restart the jobs again
when the failed server rejoins the cluster is avoided. Then, when it is convenient, you
can move the Backup Exec cluster group back to the controlling node.
Specific details of how Backup Exec runs in a cluster vary depending on the
configuration you use in the cluster.
Related Topics:
“Configurations for Backup Exec and Microsoft Cluster Servers” on page 715
“Installing Backup Exec on a Microsoft Cluster Server” on page 704
702 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
Requirements for installing Backup Exec on a Microsoft Cluster Server
Requirements for installing Backup Exec on a Microsoft Cluster
Server
■ Two-node clusters are supported with Backup Exec for Windows Servers on
Microsoft Windows 2000 Advanced Server, Windows Server 2003 Enterprise,
Microsoft Windows 2000 DataCenter, and Windows Server 2003 DataCenter.
■ Four-node clusters are supported with Backup Exec for Windows Servers on
Microsoft Windows 2000 DataCenter, Windows Server 2003 Enterprise, and
Windows 2003 DataCenter.
■ Up to eight-node clusters are supported with Backup Exec for Windows Servers on
Microsoft Windows Server 2003 DataCenter.
■ Backup Exec clusters can be installed on a Windows Server 2003 majority node
configuration. However, there must be a shared disk in the configuration in order
for Backup Exec to share its database files between nodes. In this type of
configuration, if the majority of the cluster nodes fail, then the entire cluster will
fail. This configuration normally uses more than two nodes in the cluster
configuration.
■ The controlling node and designated failover nodes must be online during
installation of Backup Exec into the cluster.
■ A unique IP address and a unique network name for the Backup Exec virtual server
is required during installation.
■ During installation of a Backup Exec cluster, the node that runs the installation
should own the shared disk. If you use a physical disk resource that belongs to
another application, the Backup Exec Cluster Wizard will move all the resources
that belong to the other application into the Backup Exec group. It is recommended
that Backup Exec not be installed on the cluster quorum.
■ An individually licensed copy of Backup Exec for Windows Servers, as well as any
applicable agents and options, is required for each active node in the cluster as
defined in the End User License Agreement. When installing an evaluation version
of Backup Exec, a cluster environment is automatically detected and license keys are
not required.
■ When you install Backup Exec clusters in a SAN SSO configuration, all Backup Exec
installations must have the same server configuration. Either all nodes should be
database servers or all nodes should be secondary member servers connecting to the
same primary.
■ All Backup Exec installations into a cluster must either be part of a single cluster
group, or be locally installed on each node. If cluster-aware Backup Exec is installed
in a cluster as well as a locally installed version of Backup Exec (not cluster-aware),
then you cannot log on to the locally installed Backup Exec media server. You can
703

Installing Backup Exec on a Microsoft Cluster Server
only log on using the Backup Exec virtual server name. To be able to log on to the
locally installed Backup Exec media server, you must first use the Cluster
Configuration Wizard to uninstall cluster-aware Backup Exec from all the nodes in
the cluster.
■ Use the same account for Backup Exec services on all nodes in the cluster. If nodes
in a cluster use Backup Exec and have different accounts, change the services to use
the same account.
Related Topics:
“Installing Backup Exec on a Microsoft Cluster Server” on page 704
“Configurations for Backup Exec and Microsoft Cluster Servers” on page 715
Installing Backup Exec on a Microsoft Cluster Server
Note We do not recommend installing Backup Exec on the same disk that the cluster
quorum is installed on. If you have to specify a new drive letter for the quorum
disk during a recovery process, Backup Exec will not recognize the new drive and
will not run. For more information, see “Specifying a new drive letter for the
cluster quorum disk” on page 734.
Note By default, failover from the controlling node to a designated node occurs in
alphabetical order according to the machine name of each node. To change the
order in which failover will occur on the designated nodes, rename the machines.
The Remote Agent is automatically installed on all the nodes in the cluster. If this
installation of Backup Exec will be used to back up remote servers outside the cluster,
install the Remote Agent on those remote servers as well.
To install Backup Exec on a cluster
1. Install Backup Exec on all the nodes that you want in the cluster. Use the same
installation path for each node.
2. From the node that you want to be the active node, start Backup Exec.
3. From the Tools menu, point to Wizards, and then click Cluster Configuration
Wizard.
4. Follow the instructions on the screen.
704 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
Installing Backup Exec on a Microsoft Cluster Server
Note On the Virtual Server Information screen, Backup Exec automatically displays a
default name called BKUPEXECVRS for the virtual server. Type a new default
name if you do not want to use the default.
5. When the Cluster Configuration Wizard completes, create a device pool that
contains all the locally attached storage devices on each node to be used when
failover occurs. This ensures that jobs can be run on the storage devices that are
attached to the failover nodes. For more information, see “Creating device pools for
Microsoft Cluster Servers” on page 708.
Related Topics:
“Creating device pools for Microsoft Cluster Servers” on page 708
“Enabling or disabling checkpoint restart” on page 711
“Configurations for Backup Exec and Microsoft Cluster Servers” on page 715
“Specifying a different failover node” on page 712
Upgrading Backup Exec on a Microsoft cluster
You can upgrade Backup Exec 9.0.4454 and above on the nodes in a cluster without
taking the nodes out of the cluster.
To upgrade Backup Exec 9.0 on a cluster
1. From the Tools menu, point to Wizards, and then click Cluster Configuration
Wizard to uncluster the Backup Exec.
2. Upgrade all the nodes with the options.
3. From the Tools menu, point to Wizards, and then click Cluster Configuration
Wizard to recluster the Backup Exec nodes.
Run the option from the same node that was used to uncluster Backup Exec.
4. Repeat step 3 for each node in the cluster.
To upgrade Backup Exec 9.0.4454 and above on a cluster
1. Select a node to upgrade and make that node the active Backup Exec cluster node.
2. Run the Backup Exec installation program on the active node.
705

Installing Backup Exec on a Microsoft Cluster Server
3. Move the cluster group to the next node you want to upgrade, and then run the
Backup Exec installation program on that node. All of the resources except for the
disk should be offline when moved over to each node for upgrade.
4. Repeat step 3 for each node in the cluster.
Related Topics:
“Installing Backup Exec” on page 71
Installing additional Backup Exec options on a Microsoft cluster
Install additional Backup Exec options on each node of the cluster. For details on
installing each option, see the appropriate section in this guide, or in online Help.
Note If you are using the Advanced Open File Option, set those defaults on each
physical node the option is installed on, not on the virtual server. Because the
default settings for the static volume can be different on each node, Advanced
Open File Option defaults do not fail over.
To install additional Backup Exec options
1. On the controlling node, make sure the Backup Exec group is online before you start
installing additional options.
2. Follow the instructions in “Installing Backup Exec options to the local computer” on
page 85.
3. After the installation is complete on the controlling node, use the cluster
administrator to move the Backup Exec group to the next appropriate node, and
repeat step 2. Be sure to install the same options with the same settings for each
node in the cluster.
To install the Backup Exec Agent for Oracle Server and the Backup Exec Agent for
SAP Applications on other nodes, map a drive to the shared disks where Backup Exec
is installed on the cluster, and run SETUP. For more information, see “Installation
and configuration requirements for the Oracle Agent” on page 1398 and “Symantec
Backup Exec Agent for SAP Applications” on page 1439.
706 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
Installing Backup Exec on a Microsoft Cluster Server
Uninstalling Backup Exec from a Microsoft cluster
To uninstall Backup Exec from a cluster
1. From the Tools menu, point to Wizards, and then click Cluster Configuration
Wizard.
2. Use the wizard to remove cluster-aware Backup Exec from all selected servers.
When unclustering the active node, you can either leave the Backup Exec data on the
shared drive or delete it. If you delete the data, you can make the data available on
the active node.
3. Uninstall Backup Exec from all the nodes.
4. After Backup Exec has been uninstalled, move any resource disks from the Backup
Exec cluster group to another group, and then delete the Backup Exec cluster group.
5. On any node, click Start, point to Settings, and then click Control Panel to uninstall
Backup Exec.
6. Double-click Add/Remove Programs, and then in the list of currently installed
programs, select Symantec Backup Exec for Windows Servers and click
Change/Remove.
Repeat step 5 for all nodes. In the following example, you would move Disk Q to
Cluster Group, and then delete the group Backup Exec, highlighted under Groups in
POWERCLUSTER.
Example of Backup Exec cluster group
707

Creating device pools for Microsoft Cluster Servers
Creating device pools for Microsoft Cluster Servers
When Backup Exec is installed on a cluster, it creates default device pools named All
Devices () for each node in the cluster. If a node has storage devices, those
storage devices are automatically assigned to All Devices (), which is also
the default destination device on that node when you create backup or restore jobs.
However, to allow jobs to run on the storage devices attached to a failover node after a
failover occurs, you must create a device pool that includes the storage devices from all
of the nodes. If the cluster is also configured with tape devices on a shared SCSI bus, then
add the tape device name used by each node to the device pool. You must also select this
device pool as the destination device for all jobs that you want to be restarted.
You can create either a single device pool, or you can create device pools for device or
media types so that when jobs fail over they can be restarted on “like” devices and media.
To create a device pool for a cluster
1. From the controlling node, open Backup Exec.
2. Create a new device pool.
For information on creating device pools, see “Creating device pools” on page 177.
3. Add storage devices and then exit Backup Exec. If there are tape devices on a shared
SCSI bus, then add the tape device name used by each node.
For information on adding devices to a device pool, see “Adding devices to a device
pool” on page 178.
4. Using the cluster administrator, move the Backup Exec resource group to the next
appropriate node.
5. Open Backup Exec, add storage devices for this node to the previous device pool and
then exit Backup Exec. If there are tape devices on a shared SCSI bus, then add the
tape device name used by each node.
6. Repeat step 4 and step 5 for each node in the cluster.
708 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
Using checkpoint restart on Microsoft Cluster Server failover
Using checkpoint restart on Microsoft Cluster Server failover
You can enable or disable checkpoint restart for each backup job run on the cluster (by
default, checkpoint restart is enabled). When checkpoint restart is enabled, jobs that
were interrupted because of a failover continue from the point of interruption rather
than starting over. Files that were already backed up are skipped, and only the
remaining files in the job are backed up when the job is restarted. If this option is not
selected, jobs are restarted from the beginning.
Checkpoint restart works best for the following file types:
■ NTFS
■ GRFS
■ Exchange mailboxes and public folders
■ Exchange 2000 and 2003 IS with multiple storage groups
■ SQL database non-snapshot backups
The following types of files cannot use checkpoint restart:
■ System State
■ Lotus Domino
■ Exchange 5.5 IS and DS
■ Exchange 2000 and 2003 IS with one storage group
■ GRFS Oracle
■ NTFS Image sets
■ NTFS Snapped volumes
■ SQL database snapshot backups
■ SQL transaction log backups
■ NetWare SMS (the checkpoint restart option should be disabled for NetWare
backups using the Remote Agent)
Checkpoint restart is not supported by the following:
■ The Advanced Open File Option.
■ The offhost backup feature in the Advanced Disk-based Backup Option.
■ When the option Collect additional information for synthetic backups is selected
for the synthetic backup feature in the Advanced Disk-based Backup Option.
■ Incremental backups based on the archive bit.
709

Using checkpoint restart on Microsoft Cluster Server failover
Jobs that are restarted from the point of failover display a status of ’Resumed’ in the Job
Monitor.
Before using checkpoint restart, review the following:
■ If a resource was completely backed up prior to a cluster failover, that resource is
skipped upon checkpoint restart, regardless of whether the backup type or file type
of that resource is supported by checkpoint restart. This saves media space and
backup time.
■ If failover occurs in the middle of backing up a resource, the media that was being
used at the time of the failover is left unappendable and new media will be requested
upon restart. It is recommended that you select an appropriate media overwrite
protection level to ensure that media that was used prior to the failover is not
overwritten upon restart.
■ The data that is backed up upon restart is part of a different backup set than the
data that was backed up prior to the failover. Separate catalog backup set entries are
created for the data backed up prior to the failover and after the failover.
In addition, if multiple cluster failovers occur during the backup of a given resource,
a different backup set is created each time the job restarts. These multiple backup
sets allow potential for duplication of backed up data.
It is important to restore the backup sets in the order in which they were backed up.
In addition, you should enable the Restore over existing files option when
performing a restore operation on these backup sets to ensure that all the data
included in the backup set is completely restored.
■ If failover occurs during a post-backup verify job, or a pre-backup or post-backup
database consistency check job, that job starts at the beginning after failover.
■ Entries for full-volume backups that were interrupted by a cluster failover and
resumed from the point of failover do not display in the IDR Restore Wizard.
However, you can restore these backup sets manually after you make the initial
recovery using the IDR Restore Wizard.
■ If the checkpoint restart setting is enabled for an archive backup job that is resumed
when a cluster failover occurs, the files selected for archive are not automatically
deleted from the source volume after the backup completes.
■ If a failover occurs on a clustered managed media server, the job that is recovered
resumes on the active cluster node. The job will not be recovered to any other
managed media servers outside of the Backup Exec cluster.
710 Administrator’s Guide

Enabling or disabling checkpoint restart
Chapter 18, Using Symantec Backup Exec with Server Clusters
Enabling or disabling checkpoint restart
To apply checkpoint restart to backup jobs, make sure that the Error-Handling Rule for
Cluster Failover is enabled. See “Error-handling rules” on page 474.
To enable or disable checkpoint restart
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Properties pane, under Settings, click Clusters.
4. Select or clear Apply CheckPoint Restart (resume jobs from point of failover).
Defaults set in Backup Exec remain the same on the failover nodes as they were on
the controlling node when failover occurs.
5. Enable the Cluster Failover error-handling rule. On the Tools menu, select
Error-Handling rdules.
6. Select the Cluster Failover rule, and then click Edit.
7. Verify that the Enabled field is selected.
711

Specifying a different failover node
Specifying a different failover node
You can:
■ Change the order in which the nodes fail over.
■ Add a failover node to the cluster.
■ Remove a failover node from the cluster.
To change the order in which nodes fail over
■ By default, in a MSCS cluster, failover from the controlling node to a designated
node occurs in alphabetical order according to the machine name of each node. To
change the order in which failover will occur on the designated nodes, rename the
machines in the order in which they should fail over.
■ VCS uses a priority list as the primary method for determining the failover target.
To set the priority in VCS, highlight the Backup Exec group in the VCS Cluster
Explorer and select Tools>System Manager. Modify the priority field to reflect the
desired order.
To add or remove a failover node
Before you add a node to the Backup Exec cluster configuration, you must install Backup
Exec on it. Cluster services for a node should be online before you add or remove it from
the cluster.
If you are removing a node, do not run the cluster configuration wizard from the node
you want to remove.
1. On the controlling node, on the Tools menu, point to Wizards.
2. Click Cluster Configuration Wizard.
3. Follow the instructions on the screen to add or remove a node.
4. If you have added a failover node, also add any locally attached storage devices that
are to be used when failover occurs to the cluster device pool. This ensures that jobs
can be run on the storage devices that are attached to the failover nodes.
If you remove some, but not all, nodes in a cluster, an uninstall of Backup Exec results in
a password being requested for the virtual server and the services continuing to run.
You must remove Backup Exec from all nodes on the cluster, following the procedures
detailed in “Uninstalling Backup Exec from a Microsoft cluster” on page 707.
Related Topics:
“Creating device pools for Microsoft Cluster Servers” on page 708
712 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
Specifying a different failover node
“Specifying a different failover node” on page 712
“Configurations for Backup Exec and Microsoft Cluster Servers” on page 715
713

Designating a new SAN SSO primary server and central administration server in a Microsoft Cluster Server
Designating a new SAN SSO primary server and central
administration server in a Microsoft Cluster Server
To designate a new primary SAN Shared Storage Option server or central
administration server for a cluster environment, use BEUtility.exe. BEUtility enables
you to do various types of configuration and maintenance operations on your Backup
Exec for Windows Servers media servers.
Note In a cluster environment, do not use Change Service Account in BEUtility.exe.
To change a Backup Exec Cluster server from a Database Server to a Member Server
1. Install the new server as a secondary server with the Library Expansion Option and
SAN Shared Storage Option installed.
Make sure connections to the Backup Exec cluster and other member servers are
working properly.
2. Using the cluster administrator, shut down the Backup Exec cluster services.
Be sure to keep the Disk resource online.
3. Move the catalog files from the Backup Exec cluster installation path to the
respective installation paths on the new database server.
4. Use BEUtility.exe to connect all Backup Exec servers to the new database server and
to start all Backup Exec services.
5. Stop and restart the Backup Exec Services on the new database server.
6. Using the Cluster Administrator, move the Backup Exec resource group to the
failover node and make sure services start on that node.
7. Use BEUtility.exe to stop and restart the Backup Exec Services on all the member
servers of the SAN in order for them to connect to the new database server.
To change a Backup Exec Cluster server from a central administration server to a managed
media server
1. Install the new server as a managed media server.
Make sure connections to the Backup Exec cluster and other managed media servers
are working properly.
2. Using the cluster administrator, shut down the Backup Exec cluster services.
714 Administrator’s Guide

Be sure to keep the Disk resource online.
Chapter 18, Using Symantec Backup Exec with Server Clusters
Configurations for Backup Exec and Microsoft Cluster Servers
3. Move the catalog files from the Backup Exec cluster installation path to the
respective installation paths on the new central administration server.
4. Use BEUtility.exe to connect all Backup Exec servers to the new central
administration server and to start all Backup Exec services.
5. Stop and restart the Backup Exec Services on the central administration server.
6. Using the Cluster Administrator, move the Backup Exec resource group to the
failover node and make sure services start on that node.
7. Use BEUtility.exe to stop and restart the Backup Exec Services on all the managed
media servers in order for them to connect to the new central administration server.
Related Topics:
“Multi-node clusters on a fibre channel SAN with the SAN SSO” on page 720
Configurations for Backup Exec and Microsoft Cluster Servers
Backup Exec supports various cluster configurations of between two and eight nodes on
a fibre channel SAN, with locally attached storage devices, or with storage devices on a
shared SCSI bus. You can use any combination of these configurations.
Note If you install the cluster on a private network, use the Cluster Administrator to
enable public communication if necessary.
If you are using a cluster on a fibre channel SAN or with storage devices on a shared
SCSI bus and failover occurs, depending on the capability of your various SAN
components, media might be orphaned in the tape drive until the failed node becomes
active again.
If end-of-job markers were not written to the media before the failover occurred, the
media may be marked as unappendable by the Backup Exec engine when the next
append backup job is run. The media remains unappendable until it is overwritten (or
erased, or the retention period expires, etc.).
If the storage device is a robotic library, you can review the Robotic Library Inventory
report to discover if the media was marked unappendable by the Backup Exec engine. If
the Full column reports a 3, the Backup Exec engine has marked the media as
unappendable.
715

Configurations for Backup Exec and Microsoft Cluster Servers
To add or remove hot-swappable devices in a cluster, run the Hot-swap Device Wizard
on all Backup Exec Cluster nodes. If a server is not updated to recognize a new device,
any job that is targeted to that device may fail. For more information about
hot-swapping devices, see “Adding devices by using the Hot-swappable Device Wizard”
on page 173.
See the following for examples of various cluster configurations:
“Two-node cluster with locally attached storage devices” on page 716
“Two-node cluster with tape devices on a shared SCSI bus” on page 717
“Multi-node clusters on a fibre channel SAN with the SAN SSO” on page 720
Two-node cluster with locally attached storage devices
In this configuration, cluster-aware Backup Exec is installed on the controlling node,
failover occurs to designated nodes in the cluster, and storage devices are locally
attached to each node.
Each node’s locally attached storage devices are automatically assigned to the All
Devices () device pool, which is also the default destination device on that
node when you create backup or restore jobs. You must create a device pool that
includes storage devices on the controlling node and on each failover node in order for
jobs to run when failover occurs. For more information, see “Creating device pools for
Microsoft Cluster Servers” on page 708.
To restore data in this configuration, move media to the failover node’s locally attached
storage device and reinventory before starting a restore operation.
Two-node Cluster with Locally Attached Storage Devices
Backup Exec Virtual Server
Controlling
node
Shared SCSI Bus
for disks
Failover node
Locally attached
Locally attached
storage devices
Heartbeat
storage devices
Related Topics:
“Multi-node clusters on a fibre channel SAN with the SAN SSO” on page 720
716 Administrator’s Guide
LAN

Chapter 18, Using Symantec Backup Exec with Server Clusters
Configurations for Backup Exec and Microsoft Cluster Servers
Two-node cluster with tape devices on a shared SCSI bus
In this configuration, cluster-aware Backup Exec is installed on the controlling node,
failover occurs to designated nodes in the cluster, and tape devices are attached to a
shared SCSI bus that is separate from any shared SCSI bus for disks.
Because each node creates a unique tape device name for the same device, if the drive is
not serialized, this configuration requires you to create a device pool that includes the
tape device name used by each node in order for jobs to run when failover occurs. For
more information, see “Creating device pools for Microsoft Cluster Servers” on page 708.
When failover occurs, a SCSI bus reset is issued. Therefore, tape devices and shared
drives should not be connected to the same SCSI bus; each should be connected to
separate SCSI buses. For more information, see “Configuring a shared SCSI bus for tape
devices” on page 718.
Two-node Cluster with Tape Devices on a Shared SCSI Bus
Controlling
node
Backup Exec Virtual Server
Shared SCSI
Bus for Disks
Shared SCSI
Bus for Tape
Devices
Heartbeat
Related Topics:
“Multi-node clusters on a fibre channel SAN with the SAN SSO” on page 720
Failover node
LAN
717

Configurations for Backup Exec and Microsoft Cluster Servers
Configuring a shared SCSI bus for tape devices
Before configuring a shared SCSI bus for tape devices, please read the following
carefully.
To configure tape devices on a shared SCSI bus, you must have SCSI cables, SCSI
terminators, a SCSI adapter in each cluster server to provide a shared external bus
between the nodes, and at least one tape device on the shared bus.
The tape devices must be connected to a bus that uses the same method of transmission
that the device does (single-ended or differential). Only one transmission method can be
used on a single SCSI bus, however, if the devices use different transmission methods,
you can install a signal converter between the devices. A signal converter converts
single-ended SCSI signals to differential SCSI signals.
Note You must use a signal converter to connect single-ended and differential devices
in order to avoid hardware damage.
You must terminate the SCSI bus at both ends so that commands and data can be
transmitted to and from all devices on the bus. Each SCSI bus must have two
terminators and they must be at each end of the segment.
If a tape device is in the middle of the bus, as shown in “Two-node Cluster with Tape
Devices on a Shared SCSI Bus” on page 717, remove any internal termination in that
device.
If the tape device is at the end of the bus, as shown in “Example of a shared bus with tape
devices at the end of the bus” on page 718, and the tape device has internal termination,
you can use the device’s internal termination to terminate the bus.
Example of a shared bus with tape devices at the end of the bus
Controlling
node
Backup Exec Virtual Server
Shared SCSI
bus for disks
Heartbeat
Shared SCSI
bus for tape devices
Following are methods you can use to terminate a bus:
Failover node
■ SCSI adapters. This method is not recommended because if the server is
disconnected from the shared bus, or if there is a power supply failure, the bus may
not be properly terminated and may be inoperable.
718 Administrator’s Guide
LAN

Chapter 18, Using Symantec Backup Exec with Server Clusters
Configurations for Backup Exec and Microsoft Cluster Servers
■ Pass-through (or feed-through) SCSI terminators. These can be used with SCSI
adapters and with some tape devices. If the tape device is at the end of the bus, you
can attach a pass-through SCSI terminator to terminate the bus. The internal
terminators in the tape device must be disabled. This is a recommended method.
Tip To ensure termination if a power supply failure occurs, turn off the on-board
terminators on the SCSI controller (using the host adapter manufacturer’s
recommended method) and physically terminate the controller with a terminator.
■ Y cables. These can be used with some tape devices. If the tape device is at the end of
the bus, you can attach a terminator to one branch of a Y cable to terminate the bus.
The internal terminators in the tape device must be disabled. This is a recommended
method.
■ Trilink connectors. These can be used with some tape devices. If the tape device is at
the end of the bus, you can attach a terminator to one of the trilink connectors to
terminate the bus. The internal terminators in the tape device must be disabled.
This is a recommended method.
Besides terminating the bus, Y-cables and trilink connectors also allow you to isolate the
devices from the shared bus without affecting the bus termination. You can maintain or
remove that device without affecting the other devices on the shared SCSI bus.
To configure a shared SCSI bus for tape devices
1. Install the SCSI controllers for the shared SCSI bus.
Make sure that the SCSI controllers for the shared SCSI bus are using different SCSI
IDs. For example, on the controlling node, set the SCSI controller ID to 6 and on the
failover node, set the SCSI controller ID to 7.
2. Prepare the SCSI controllers for the shared SCSI bus. Refer to your SCSI host
adapter manufacturer’s documentation for details.
Note Do not have power on to both nodes while configuring the computers, or if both
nodes have power on, do not connect the shared SCSI buses to both nodes.
3. Connect the shared SCSI tape devices to the cable, connect the cable to both nodes,
and then terminate the bus segment using one of the methods discussed in the
previous section.
Related Topics:
“Two-node cluster with tape devices on a shared SCSI bus” on page 717
719

Configurations for Backup Exec and Microsoft Cluster Servers
Multi-node clusters on a fibre channel SAN with the SAN SSO
In this configuration, one or more clusters are attached to a fibre channel storage area
network (SAN), with cluster-aware Backup Exec and the SAN Shared Storage Option
(SAN SSO) installed on the controlling node in each cluster. Shared secondary storage
devices are attached to the fibre channel, although a single storage device can be shared
between one or more clusters. Failover occurs (in alphabetical order of the machine
name) to other designated nodes in the cluster.
Note When using multiple clusters in a SAN SSO environment, it is strongly
recommended that the cluster nodes be connected to the storage devices using a
fibre switch. If you use a hub rather than a fibre switch, the hub will receive a reset
command during a failover event that causes all other components attached to the
hub to be disconnected.
You can designate any server on the fibre channel SAN as the Shared Storage
Option Database server.
You should create a failover device pool for the cluster. For details about creating a
failover device pool, see “Creating device pools for Microsoft Cluster Servers” on
page 708.
This configuration offers increased performance since backups are performed locally
instead of over a network. Additionally, centralized media catalogs are available. Because
the SAN SSO uses a shared catalog database, a tape that has already been cataloged can
be physically moved from one device to another and not have to be recataloged.
Tip The SAN SSO option must be installed on each failover node, with the same
settings that were used on the primary node. Either all nodes should be database
servers or all nodes should be secondary member servers.
Following are examples of multi-node clusters:
720 Administrator’s Guide

Two 2-node Clusters on a Fibre Channel SAN with the SAN SSO
Secondary
Storage
Devices
Controlling
node
Backup Exec
Virtual Server A
Chapter 18, Using Symantec Backup Exec with Server Clusters
Configurations for Backup Exec and Microsoft Cluster Servers
Fibre Channel
SAN
Shared
SCSI Bus for disks
Failover
Heartbeat node
Secondary
server
Backup Exec
Virtual Server B
Shared
SCSI Bus for disks
Controlling
node
Heartbeat
Failover
node
LAN
721

Configurations for Backup Exec and Microsoft Cluster Servers
Four-node Cluster on Fibre Channel SAN with the SAN SSO
Secondary
server
Secondary
Storage
Devices
Controlling
node
Fibre Channel
SAN
Backup Exec
Virtual Server
Heartbeat
Shared Drives
Failover
nodes
For details on installing the SAN SSO, see “Installing the SAN Shared Storage Option” on
page 1549.
Related Topics:
“Designating a new SAN SSO primary server and central administration server in a
Microsoft Cluster Server” on page 714
722 Administrator’s Guide
LAN

Chapter 18, Using Symantec Backup Exec with Server Clusters
Using the Central Admin Server Option with Microsoft clusters and SAN SSO
Using the Central Admin Server Option with Microsoft clusters
and SAN SSO
Managed media servers can be clustered, however, it is not recommended because the
central administration server recovers all failed jobs in a distributed job environment.
The following configurations can be used when installing Backup Exec clusters with the
Central Admin Server Option (CASO) and SAN SSO.
■ Backup Exec cluster with CASO
■ Backup Exec cluster with CASO and SAN Shared Storage Option
■ Backup Exec cluster with the managed media server configuration
■ Backup Exec cluster with the managed media server configuration and SAN Shared
Storage Option
Installing Backup Exec cluster with CASO
1. Install Backup Exec with CASO and any additional options onto your Microsoft
cluster nodes.
2. From the node that you want to designate as the active node, start Backup Exec.
3. From the Tools menu, point to Wizards, and then click Cluster Configuration
Wizard.
4. Follow the instructions on the screen.
5. When the Cluster Configuration Wizard completes, install the managed media
server. Use the virtual Backup Exec cluster name when prompted for the central
administration server.
Installing Backup Exec cluster with CASO and SAN Shared Storage Option
1. Install Backup Exec with CASO, the SAN Shared Storage Option, and any additional
options onto your Microsoft cluster nodes.
2. From the node that you want to designate as the active node, start Backup Exec.
3. From the Tools menu, point to Wizards, and then click Cluster Configuration
Wizard.
4. Follow the instructions on the screen.
723

Using the Central Admin Server Option with Microsoft clusters and SAN SSO
5. When the Cluster Configuration Wizard completes, install the managed media
server. Use the virtual Backup Exec cluster name when prompted for the central
administration server and the primary SAN server.
Installing Backup Exec cluster with the managed media server configuration
1. Install Backup Exec with the managed media server option and any additional
options onto your Microsoft cluster nodes.
All nodes that run Backup Exec in the managed media server cluster configuration
must access the same central administration server. If the nodes do not access the
same central administration server, failovers do not occur properly.
2. From the node that you want to designate as the active node, start Backup Exec.
3. From the Tools menu, point to Wizards, and then click Cluster Configuration
Wizard.
4. Follow the instructions on the screen.
Installing Backup Exec cluster with the managed media server configuration and SAN Shared
Storage Option
1. Install Backup Exec with the managed media server option, SAN Shared Storage
Option, and any additional options onto your Microsoft cluster nodes.
All nodes that run Backup Exec in the managed media server cluster configuration
must access the same central administration server. If the nodes do not access the
same central administration server, failovers do not occur properly.
2. From the node that you want to designate as the active node, start Backup Exec.
3. From the Tools menu, point to Wizards, and then click Cluster Configuration
Wizard.
4. Follow the instructions on the screen.
724 Administrator’s Guide

Backing up Microsoft Cluster Servers
Chapter 18, Using Symantec Backup Exec with Server Clusters
Backing up Microsoft Cluster Servers
To protect all data in the cluster, including file shares, databases, and the cluster
quorum, back up the following:
■ Local disks and System State on each node. The cluster quorum, which contains
recovery information for the cluster and information about changes to the cluster
configuration, is included in the System State backup. For more information, see
“Backing up local disks in a Microsoft cluster” on page 727.
■ All shared disks, including the data in the Microsoft Cluster Server folder on the
Quorum disk. For more information, see “Backing up shared disks in a Microsoft
cluster” on page 727.
■ Virtual servers, which may contain data or contain applications such as Microsoft
SQL Server or Exchange Server. Use Backup Exec database agents to back up
databases. For more information, see “Backing up database files in a Microsoft
cluster” on page 728.
For details on setting up and running backup operations, see “Creating a backup job by
using the Backup Wizard” on page 347.
Note For offhost backup jobs that use the hardware provider, the media server and the
remote computer must be in different cluster groups. The cluster applications
cannot support devices’ logical unit numbers (LUNs) that have duplicate
signatures and partition layouts, therefore, the snapshots containing the LUNs
must be transported to a host, or remote computer, that is outside the cluster.
The Command Line Applet can be used with Backup Exec when Backup Exec is installed
in a cluster. The only limitation is that you cannot use the Command Line Applet to
specify a device for backup. You can use the Command Line Applet to target a device
pool, but not a specific device in that pool.
Related Topics:
“Backing up local disks in a Microsoft cluster” on page 727
“Backing up shared disks in a Microsoft cluster” on page 727
“Backing up database files in a Microsoft cluster” on page 728
“About Backing up Windows 2000 and Windows Server 2003 features in a Microsoft
Cluster” on page 726
725

Backing up Microsoft Cluster Servers
About Backing up Windows 2000 and Windows Server 2003
features in a Microsoft Cluster
You must purchase and install the Backup Exec Remote Agent for Windows Systems on
all remote Windows 2000 and Windows Server 2003 computers that you want backed up.
Without the Remote Agent, the following Windows 2000 and 2003 features cannot be
correctly backed up:
■ Encrypted files
■ SIS files
■ Disk quota data
■ Removable Storage data
■ Remote Storage data
■ Mount points
■ Sparse files
■ Windows Management Instrumentation
■ Terminal Services
■ System State data, including:
■ COM+ Class Registration database
■ Boot and system files
■ Registry
■ Certificate Services database (if the server is operating as a certificate server)
■ Active Directory (if the server is a domain controller)
■ SYSVOL (if the server is a domain controller)
■ Cluster quorum (if the server is part of a cluster)
Note You can select System State or Shadow Copy Components for backup on a remote
computer only when the Remote Agent is installed on the remote computer.
Related Topics:
“About Restoring Windows 2000 and Windows Server 2003 features to a Microsoft
cluster” on page 729
726 Administrator’s Guide

Backing up local disks in a Microsoft cluster
Chapter 18, Using Symantec Backup Exec with Server Clusters
Backing up Microsoft Cluster Servers
Select local disks for backup from the physical node to which they are attached.
To back up local disks in a Microsoft cluster
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. From the backup selections pane, expand the domain that contains the nodes, and
then select the local disks on each node.
When making backup selections for nodes running Windows 2000, be sure to select
System State. For more information, see “Selecting data to back up” on page 315.
4. If you created a device pool for the cluster, select it as the default destination device
so that jobs can restart on the failover node if failover occurs.
5. Configure the remainder of the settings for the backup job.
6. Run the backup job now or schedule it to run later.
Backing up shared disks in a Microsoft cluster
Select shared disks for backup by selecting them from the Microsoft Cluster Server
virtual server or from the Backup Exec virtual server.
To back up shared disks
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the backup selections pane, expand the domain that contains the nodes, and then
select either the Microsoft Cluster Server virtual server or the Backup Exec virtual
server. The virtual servers allow your backup jobs to access shared data via any node
that controls the disk.
4. Select the drive letters that represent the shared disks.
5. If you created a device pool for the cluster, select it as the default destination device
so that jobs can restart on the failover node if failover occurs.
727

Backing up Microsoft Cluster Servers
6. Configure the remainder of the settings for the backup job.
7. Run the backup job now or schedule it to run later.
Note To browse clustered servers in Active Directory Domains, you must enable
Kerberos authentication on each virtual cluster server. You can enable Kerberos
authentication from Microsoft's Cluster Administrator.
Backing up database files in a Microsoft cluster
Select database files for back up from a database icon on a virtual server. If a virtual
server contains a database application such as Microsoft SQL Server or Exchange
Server, use the appropriate Backup Exec database agent to perform the backup
operations; otherwise, only the file system is backed up, not the database files.
To back up database files in a cluster
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. In the backup selections pane, expand the domain that contains the cluster, then
expand the virtual server that contains the database files.
4. Check the database files.
5. Set database-specific defaults. Refer to the specific Backup Exec database agent
documentation for details on how to set backup defaults for the database.
6. If you created a device pool for the cluster, select it as the default destination device
so that jobs can restart on the failover node if failover occurs.
7. Configure the remainder of the settings for the backup job.
8. Run the backup job now or schedule it to run later.
728 Administrator’s Guide

About Restoring data to a Microsoft cluster
Chapter 18, Using Symantec Backup Exec with Server Clusters
About Restoring data to a Microsoft cluster
For all file restore operations, including redirecting restores, use the normal procedures
as described in “Restoring data by setting job properties” on page 488.
When restoring files to shared drives, direct those files to the virtual server or the
controlling node of the resource. When restoring individual database files, such as
Microsoft SQL Server or Exchange Server, direct those files to the virtual server name of
a specific installation of the SQL or Exchange database.
Related Topics:
“Restoring the cluster quorum for Windows 2000 and Windows Server 2003 computers
to a Microsoft cluster” on page 730
“Restoring the cluster quorum to a Windows 2000 or Windows Server 2003 node running
Active Directory to a Microsoft cluster” on page 732
“Specifying a new drive letter for the cluster quorum disk” on page 734
About Restoring Windows 2000 and Windows Server 2003
features to a Microsoft cluster
To fully restore Windows 2000 features to a remote Windows 2000 system, the restore
operation MUST be performed by a Windows 2000 media server, and the Remote Agent
must be installed on the remote system.
You can restore Windows Server 2003 features from either a Windows 2000 media
server or a Windows Server 2003 media server.
729

About Restoring data to a Microsoft cluster
Restoring the cluster quorum for Windows 2000 and Windows
Server 2003 computers to a Microsoft cluster
The cluster quorum is backed up as part of System State.
If Active Directory is running on the target server in the cluster, do not select Restore
cluster quorum. For more information, see “Restoring the cluster quorum to a Windows
2000 or Windows Server 2003 node running Active Directory to a Microsoft cluster” on
page 732.
If you need to specify a new disk to which the cluster quorum will be restored, see
“Specifying a new drive letter for the cluster quorum disk” on page 734.
To restore the cluster quorum
Note If possible, take the other nodes in the cluster offline before restoring the cluster
quorum. If the nodes cannot be taken offline, you should select the Force the
recovery... option on the Advanced Restore Job Properties dialog box (explained
in step 5).
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Settings, click Advanced.
4. Select Restore Cluster Quorum.
5. Select Force the recovery of the cluster quorum even if other nodes are online
and/or disk signatures do not match in the following circumstances:
■ If you are not able to take the other nodes in the cluster offline. When this
option is selected, the cluster service for any nodes that are online is stopped.
■ If the disk that the cluster quorum previously resided on has been changed. The
disk may have been replaced with a new one, or the disk configuration may have
been changed so that the cluster quorum now resides on a different disk. This
option allows the drive letter of the disk that the cluster quorum was on to
remain the same, even if the configuration has changed and the disk signatures
contained in the restore media do not match the disk signatures contained in the
cluster quorum.
6. Continue the restore operation by following the steps in “Restoring data by setting
job properties” on page 488.
730 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
About Restoring data to a Microsoft cluster
7. When the restore operation is complete, use the cluster administrator software to
restart the cluster service on nodes on which it was stopped.
731

About Restoring data to a Microsoft cluster
Restoring the cluster quorum to a Windows 2000 or Windows
Server 2003 node running Active Directory to a Microsoft cluster
To restore the quorum to a node that is a domain controller running Active Directory,
the node must be in Directory Services Restore Mode. The cluster services cannot run in
this mode, so the cluster quorum must be restored separately, after System State is
restored and the node has been rebooted.
To exclude the cluster quorum from being restored with System State, clear the Restore
Cluster Quorum option on the Advanced Restore Job Properties dialog box. When
System State is restored, the cluster quorum is copied to a default location. For Windows
2000 the default location is:
%SystemRoot%\cluster\BackupExec
For Windows Server 2003, the default location is:
%SystemRoot%\windows\repair\backup\bootablesystemstate\clusterdatabase
Then, use the command-line utility clrest.exe to restore the cluster quorum from the
default location to the quorum drive.
To restore the cluster quorum to a node running Active Directory without using Backup Exec
Cluster
Note If possible, take the other nodes in the cluster offline before restoring the cluster
quorum. If the nodes cannot be taken offline, you should use the -f option with
the clrest.exe command, explained in step 9.
1. To restore System State, start the computer in safe (repair) mode (restart the
computer and then press when prompted to select an operating system) and
then select Directory Services Restore Mode.
If this is a local restore, you must also start the Backup Exec services before you
restore the System State data. For instructions on starting the Backup Exec services,
see “Starting and stopping Backup Exec services” on page 123.
2. On the navigation bar, click the arrow next to Restore.
3. Click New Restore Job.
4. In the Restore Selections pane, click System State.
5. On the Properties pane, under Settings, click Advanced.
6. Clear the Restore cluster quorum option. This option must not be selected.
732 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
About Restoring data to a Microsoft cluster
7. Start the restore operation.
During the restore, the cluster quorum files are copied to the default location. For
Windows 2000 the default location is:
%SystemRoot%\cluster\BackupExec
For Windows Server 2003, the default location is:
%SystemRoot%\windows\repair\backup\bootablesystemstate\clusterdatabase
8. When the restore has completed, reboot the target node.
9. After reboot is complete, run clrest.exe from the command line to restore the cluster
quorum from the default location to the quorum disk:
clrest path
where path is the complete path to the cluster quorum; typically, the path is
%SystemRoot%\cluster\BackupExec for Windows 2000 and
%SystemRoot%\windows\repair\backup\bootablesystemstate\clusterdatabase for
Windows Server 2003. A path is required.
You can include other options on the command line to force the restore to proceed
even if other cluster nodes are online, and/or if the disk signatures do not match,
and to specify another disk as the quorum disk:
clrest [-f] path [drive letter]
where
[-f] forces the restore to proceed even if other cluster nodes are online and/or the
disk signatures do not match. When this option is selected, the cluster service for
any nodes that are online is stopped. This option also allows the drive letter of the
disk that the cluster quorum was on to remain the same, even if the configuration
has changed and the disk signatures contained in the restore media do not match
the disk signatures contained in the cluster quorum.
[drive letter] specifies another drive letter for the quorum disk. If you use this option,
the drive letter that the cluster quorum resides on will be changed to the drive letter
specified. Otherwise, the drive letter that the cluster quorum resides on will stay the
same as it was previously.
10. After the cluster quorum is restored, use the cluster administrator to bring the other
cluster nodes online.
733

About Restoring data to a Microsoft cluster
Specifying a new drive letter for the cluster quorum disk
To use the clrest.exe command-line utility to specify a new drive letter for the cluster
quorum disk, restore System State, but not the cluster quorum. When System State is
restored, the cluster quorum is copied to a default location,
%SystemRoot%\cluster\BackupExec.
Then, use clrest.exe with the [drive letter] option to restore the cluster quorum to the
quorum drive, which will be assigned the drive letter you specified.
To specify a new drive letter for the cluster quorum disk on Windows 2000
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. In the Restore Selections pane, click System State.
4. On the Properties pane, under Settings, click Advanced.
5. Clear the Restore cluster quorum option. This option must not be selected.
6. Start the restore operation.
During the restore, the cluster quorum files are copied to the default location
%SystemRoot%\cluster\BackupExec.
7. When the restore has completed, reboot the target node.
8. After reboot is complete, run clrest.exe from the command line to restore the
cluster quorum from the default location to the quorum disk.
clrest path [-f] [drive letter]
where
path is the complete path to the cluster quorum; typically, the pathname is
%SystemRoot%\cluster\BackupExec. A pathname is required.
[-f] forces the restore to proceed even if other cluster nodes are online and/or the
disk signatures do not match. When this option is selected, the cluster service for
any nodes that are online is stopped. This option also allows the drive letter of the
disk that the cluster quorum was on to remain the same, even if the configuration
has changed and the disk signatures contained in the restore media do not match
the disk signatures contained in the cluster quorum.
[drive letter] specifies another drive letter for the quorum disk. If you use this option,
the drive letter that the cluster quorum resides on will be changed to the drive letter
specified. Otherwise, the drive letter that the cluster quorum resides on will stay the
same as it was previously.
734 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
Using Backup Exec with Veritas Cluster Server
9. After the cluster quorum is restored, use the cluster administrator to bring the other
cluster nodes online.
Using Backup Exec with Veritas Cluster Server
If you use Veritas Cluster Server (VCS), there are three possible options for integrating
with Backup Exec. The first option consists of managed media servers installed on each
of the VCS nodes and a central administration server. You can install the central
administration server on any of the nodes or on a system that is not a VCS node.
However, the central administration server must be in the same domain as the VCS
nodes.
Selections for backup are made on the central administration server, and then based on
the backup selections of clustered resources, the central administration server sends the
job to the managed media server on which the clustered resource is currently active. The
central administration server attempts to balance backup jobs of clustered resources so
that the job is run as a local job. If a failover occurs, backup jobs that were running are
rescheduled and then the central administration server restarts the job on the new
active node for the failed resource.
The second option is to cluster the Backup Exec application using Veritas Cluster Server,
thereby making it highly available. A wizard is provided to guide you through the
configuration process.
The third option involves installing the Backup Exec Remote Agent on each of the VCS
nodes. The standalone media server can then be installed on any of the nodes or outside
of the cluster. In this environment, backup jobs for clustered resources are completed
remotely.
Specific details of how Backup Exec runs in a cluster vary depending on the
configuration you use in the cluster.
Related Topics:
““Clustering Backup Exec using Veritas Cluster Server” on page 739” on page 735
“Installing Backup Exec with the CASO option on a Veritas Cluster Server” on page 737
““Installing Backup Exec on a Microsoft Cluster Server” on page 704” on page 736
“Clustering Backup Exec using Veritas Cluster Server” on page 739
735

Requirements for installing Backup Exec with the CASO option on a Veritas Cluster Server
Requirements for installing Backup Exec with the CASO option
on a Veritas Cluster Server
Following are requirements for installing Backup Exec and CASO on a Veritas Cluster
Server:
■ 32-node clusters are supported with Backup Exec for Windows 2000, and Windows
Server 2003 and Microsoft Windows 2000 Advanced Server and Windows Server
2003 Enterprise and DataCenter and Windows Server 2003 DataCenter.
■ An individually licensed copy of Backup Exec for Windows Servers, as well as any
applicable agents and options, is required for each active node in the cluster as
defined in the End User License Agreement. You must enter a license key for each
node in the cluster (the cluster must have at least two nodes).
■ Storage Foundation for Windows Servers High Availability server components must
be installed on the cluster nodes.
■ Storage Foundation for Windows Servers High Availability Administrative Console
components must be installed on the central administration server.
Related Topics:
“Installing Backup Exec on a Microsoft Cluster Server” on page 704
736 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
Installing Backup Exec with the CASO option on a Veritas Cluster Server
Installing Backup Exec with the CASO option on a Veritas
Cluster Server
The Remote Agent is automatically installed on all the nodes in the cluster. If this
installation of Backup Exec will be used to back up remote servers outside the cluster,
install the Remote Agent on those remote servers as well.
To install Backup Exec with the CASO option on a Veritas Cluster Server
1. Install Backup Exec as an managed media server on all the nodes that you want to
include in the cluster. All installations must target local drives. Use the same
installation path for each node.
2. Install the Backup Exec Central Admin Server Option (CASO) on a machine that is
included in the same domain as the cluster nodes.
The Central Admin Server Option can be installed on any of the cluster nodes or
outside of the cluster.
3. If the managed media server contains locally attached drives, create a drive pool
that contains all the locally attached storage devices on each node to use when
failover occurs. This ensures that jobs can run on the storage devices attached to the
failover nodes.
4. If the Backup Exec Central Admin Server Option is not installed, then install the
Backup Exec Remote Agent for Windows Systems on the local drives of all the nodes
in the cluster.
Related Topics:
“Symantec Backup Exec Remote Agent for Windows Systems” on page 913
737

Requirements for clustering Backup Exec using Veritas Cluster Server
Requirements for clustering Backup Exec using Veritas Cluster
Server
■ 32-node clusters are supported with Backup Exec for Windows 2000, and Windows
Server 2003 and Microsoft Windows 2000 Advanced Server and Windows Server
2003 Enterprise and DataCenter and Windows Server 2003 DataCenter.
■ An individually licensed copy of Backup Exec for Windows Servers, as well as any
applicable agents and options, is required for each active node in the cluster as
defined in the End User License Agreement. You must enter a license key for each
node in the cluster (the cluster must have at least two nodes).
■ Storage Foundation for Windows Servers High Availability server components must
be installed on the cluster nodes.
■ A shared volume accessible by all nodes in the cluster.
■ The shared volume must be part of a dynamic cluster disk group.
■ During installation of a Backup Exec cluster, the node that runs the cluster wizard
should have exclusive control over the shared volume.
■ The shared volume cannot reside on a disk with compression enabled.
738 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
Clustering Backup Exec using Veritas Cluster Server
Clustering Backup Exec using Veritas Cluster Server
Clustering Backup Exec makes the application highly available in an active passive
configuration. The Backup Exec services can only run on one cluster node at a time.
Should the active node go offline, the services and any active jobs will be restarted on
another node in the cluster.
To cluster Backup Exec using Veritas Cluster Server
1. Install and configure Veritas Cluster Server on each machine that will be a part of
the cluster. For more information on installing and configuring Veritas Cluster
Server, refer the the Storage Foundation for Windows Servers High Availability
Edition Administrator’s Guide.
2. Install Backup Exec to the local drive on each machine that will be part of the
Backup Exec service group.
3. Create a dynamic disk group and assign a drive letter to the volume that will be used
as the shared disk resource. For more information on creating dynamic disk groups,
refer the the Storage Foundation for Windows Servers High Availability Edition
Administrator’s Guide.
4. Verify that the volume is online and a drive letter is assigned to it only on the node
where the Backup Exec Cluster Configuration Wizard will be run.
5. On the Tools menu, click Wizards>Cluster Configuration Wizard.
6. At the Cluster Configuration Wizard welcome screen click Next.
7. Enter a name for the Backup Exec cluster group or use the default name.
The cluster group name must not contain spaces.
8. The wizard lists the shared location where the Backup Exec application files will be
copied. To specify a different location click Change.
9. Click Next.
10. Enter a name for the Backup Exec virtual server or use the default name.
11. Enter the IP address and subnet mask of the virtual server.
12. Click Next.
13. The wizard will validate the entries.
739

Clustering Backup Exec using Veritas Cluster Server
14. Select the nodes that will participate in the cluster. By default, the node on which
the cluster configuration wizard was run is included as part of the cluster group.
15. Click Next.
16. Click Configure to have the wizard create the service group and move the files to the
shared disk.
740 Administrator’s Guide

About Backing up Veritas Cluster Servers
Chapter 18, Using Symantec Backup Exec with Server Clusters
About Backing up Veritas Cluster Servers
To protect all data in the cluster, including file shares and databases, back up the
following:
■ Local disks and System State on each node
■ All shared disks
■ Virtual servers, which may contain data or contain applications such as Microsoft
SQL Server or Exchange Server. Use Backup Exec database agents to back up
databases.
For details on setting up and running backup operations, see “Creating a backup job by
using the Backup Wizard” on page 347.
Note For offhost backup jobs that use the hardware provider, the media server and the
remote computer must be in different cluster groups. The cluster applications
cannot support devices’ logical unit numbers (LUNs) that have duplicate
signatures and partition layouts, therefore, the snapshots containing the LUNs
must be transported to a host, or remote computer, that is outside the cluster.
The Command Line Applet can be used with Backup Exec when Backup Exec is installed
in a cluster. The only limitation is that you cannot use the Command Line Applet to
specify a device for backup. You can use the Command Line Applet to target a device
pool, but not a specific device in that pool.
Related Topics:
“Backing up local disks in a Veritas cluster” on page 743
“Backing up shared disks in a Veritas cluster” on page 743
“Backing up database files in a Veritas cluster” on page 744
“About Backing Up Windows 2000 and Windows Server 2003 features in a Veritas
cluster” on page 742
741

About Backing up Veritas Cluster Servers
About Backing Up Windows 2000 and Windows Server 2003
features in a Veritas cluster
You must purchase and install the Backup Exec Remote Agent for Windows Systems on
all remote Windows 2000 and Windows Server 2003 computers that you want backed up.
Without the Remote Agent, the following Windows 2000 features cannot be correctly
backed up:
■ Encrypted files
■ SIS files
■ Disk quota data
■ Removable Storage data
■ Remote Storage data
■ Mount points
■ Sparse files
■ Windows Management Instrumentation
■ Terminal Services
■ System State data, including:
■ COM+ Class Registration database
■ Boot and system files
■ Registry
■ Certificate Services database (if the server is operating as a certificate server)
■ Active Directory (if the server is a domain controller)
■ SYSVOL (if the server is a domain controller)
Note You can select System State for backup on a remote computer only when the
Remote Agent is installed on the remote computer.
Related Topics:
“About Restoring Windows 2000 and Windows Server 2003 features to a Veritas cluster”
on page 745
742 Administrator’s Guide

Backing up local disks in a Veritas cluster
Chapter 18, Using Symantec Backup Exec with Server Clusters
About Backing up Veritas Cluster Servers
Select local disks for backup from the physical node to which they are attached.
To back up local disks in a Veritas cluster
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the backup selection pane, expand the domain that contains the nodes, and then
select the local disks on each node.
4. When making backup selections for nodes running Windows 2000, be sure to select
System State. For more information, see “Selecting data to back up” on page 315.
5. If you created a device pool for the cluster, select it as the default destination device
so that jobs can restart on the failover node if failover occurs.
6. Configure the remainder of the settings for the backup job.
7. Run the backup job now or schedule it to run later.
Note If the computer on which you are running a backup using the Advanced Open File
Option is in an environment with the Central Admin Server Option and the Veritas
Cluster Server installed, and if failover occurs to a VCS node, you must manually
clean up the snapshots before restarting the backup on the failover node. Refer to
the VSFW documentation for details.
Backing up shared disks in a Veritas cluster
Select shared disks for backup by selecting them from the Veritas Cluster Server virtual
server.
To back up shared disks
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Backup selection pane, expand the domain that contains the nodes, and then
select either the Veritas Cluster Server virtual server. The virtual servers allow your
backup jobs to access shared data via any node that controls the disk.
743

About Backing up Veritas Cluster Servers
4. Select the drive letters that represent the shared disks.
5. If you created a device pool for the cluster, select it as the default destination device
so that jobs can restart on the failover node if failover occurs.
6. Configure the remainder of the settings for the backup job.
7. Run the backup job now or schedule it to run later.
Backing up database files in a Veritas cluster
Select database files for back up from a database icon on a virtual server. If a virtual
server contains a database application such as Microsoft SQL Server or Exchange
Server, use the appropriate Backup Exec database agent to perform the backup
operations; otherwise, only the file system is backed up, not the database files.
To back up database files in a Veritas cluster
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. In the backup selections pane, expand the domain that contains the cluster, then
expand the virtual server that contains the database files, and then select the
databases.
4. Set database-specific defaults. Refer to the specific Backup Exec database agent
documentation for details on how to set backup defaults for the database.
5. If you created a device pool for the cluster, select it as the default destination device
so that jobs can restart on the failover node if failover occurs.
6. Configure the remainder of the settings for the backup job.
7. Run the backup job now or schedule it to run later.
744 Administrator’s Guide

About Restoring data to Veritas Cluster Servers
Chapter 18, Using Symantec Backup Exec with Server Clusters
About Restoring data to Veritas Cluster Servers
For all file restore operations, including redirecting restores, use the normal procedures
as described in “Restoring data by using the Restore Wizard” on page 487.
When restoring files to shared drives, direct those files to the virtual server or the
controlling node of the resource. When restoring individual database files, such as
Microsoft SQL Server or Exchange Server, direct those files to the virtual server name of
a specific installation of the SQL or Exchange database.
About Restoring Windows 2000 and Windows Server 2003
features to a Veritas cluster
To fully restore Windows 2000 features to a remote Windows 2000 system, the restore
operation MUST be performed by a Windows 2000 media server, and the Remote Agent
must be installed on the remote system.
You can restore Windows Server 2003 features from either a Windows 2000 media
server or a Windows Server 2003 media server.
About backup job failover with Veritas Cluster Servers
A central administration server configuration installed in a Veritas Cluster Server
environment is automatically enabled to failover a job. When you select cluster
resources for backup, only a single clustered resource can be included in the backup job.
This is necessary to ensure that the central administration server re-delegates the
backup job to the designated failover node on the cluster.
If a failover of a clustered resource occurs during backup, the job on the managed media
server stops and notification is sent to the central administration server. The central
administration server then re-delegates the job to the managed media server that has
become the new active node of the failed clustered resource.
745

Disaster recovery of a cluster
Disaster recovery of a cluster
Prepare for recovery by creating a disaster preparation plan, as described in “Key
elements of a disaster preparation plan (DPP)” on page 654.
Prepare to restore SQL, Exchange, Oracle, and Lotus Domino databases in a cluster after
a disaster by reading the sections on preparing for disaster recovery in the appropriate
chapters.
In addition to the initial preparation instructions, further action is required to
completely protect the Microsoft cluster servers. If a disaster occurs, the following
information is required to successfully recover the cluster:
■ General Cluster Information
■ Cluster name
■ Cluster IP address and subnet mask
■ Cluster node names
■ Node IP addresses
■ Local and shared drive letters and partition scheme
■ Disk signatures
■ Cluster Groups
■ Group name
■ Preferred nodes
■ Failover/failback policies
■ Cluster Resources
■ Resource name
■ Resource type
■ Group membership
■ Possible owners
■ Resource dependencies
■ Restart and Looks Alive/Is Alive properties
■ Resource-related parameters
■ Application-specific configuration (SQL Database Character Set)
746 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
Disaster recovery of a cluster
■ If you are recovering a Microsoft Cluster Server, run Dumpcfg.exe from the
Microsoft 2000 Resource Kit or and the Clusterrecovery.exe from the Microsoft 2003
Resource Kit to retrieve the disk signatures from the shared disk. The Microsoft
2000 Resource Kit allows you to replace disk signatures.
■ If you are recovering a Veritas Cluster Server, run Vmgetdrive.exe to retrieve the
disk signatures, disk group, and volume information from the shared disk.
Using IDR to prepare for disaster recovery of a cluster
Backup Exec provides a fully-automated disaster recovery solution that you can
purchase called the Intelligent Disaster Recovery (IDR) Option, which allows you to
quickly and efficiently recover the nodes that comprise the server cluster after a
disaster. Oracle servers and SAP databases cannot be restored using IDR. For more
information about disaster recovery for these options, see the appropriate chapters.
For details on using IDR to prepare for disaster recovery, see “Symantec Backup Exec
Intelligent Disaster Recovery Option” on page 1501.
Note To change the setup, use hardware, or a hardware configuration that is different
from the original configuration, you must perform a manual recovery.
Recovering nodes on the cluster using IDR
If you used Backup Exec’s Intelligent Disaster Recovery to prepare for a disaster, you
can use IDR to recover the nodes to their pre-disaster state.
Note You must create disaster recovery media for each Windows 2000 and Windows
2003 cluster node. Disaster recovery media is customized for a single computer.
You will not be able to use the media interchangeably between the nodes in a
cluster.
When recovering both nodes in a cluster, make sure that the drive letters match the
original cluster configuration. The scaled-back version of Windows that runs the
recovery wizard may detect the hard drives in a different order than what was originally
configured under the original version of Windows.
If the original configuration does not match, then to a certain extent, you can control
the hard drive numbering scheme that Windows devises.
If you cannot get the IDR Disaster Recovery Wizard to properly detect the hard drive
order, you can still manually set up hard drive partitions using the Disk Administrator
option within the Disaster Recovery Wizard. After this is done, you can continue with
automated restore of your backup media afterward.
747

Disaster recovery of a cluster
Note After Windows has been installed, you cannot change the system drive’s letter.
You must restore the system to the same drive letter from which it was backed up.
Use the following sequence to recover the nodes. For detailed instructions, see
“Symantec Backup Exec Intelligent Disaster Recovery Option” on page 1501.
To recover nodes on the cluster using IDR
1. If you are recovering more than one node, disconnect the shared disks. If you are
recovering only one node, the shared disks do not need to be disconnected.
If all nodes in the cluster are unavailable and must be recovered, the cluster cannot
fail over. Disconnect the shared disks before recovery begins.
2. To restore the nodes, follow the steps in “About recovering a computer and using the
Disaster Recovery Wizard” on page 1525.
3. Reconnect the shared drives and bring the nodes online.
4. To restore a database to the shared drives, use the appropriate Backup Exec agent.
For procedures, read the following sections:
■ “Disaster recovery of SQL” on page 1390
■ “Disaster recovery for Exchange Server 5.5” on page 1283
■ “Disaster recovery of a Lotus Domino server” on page 1329
■ “About restoring and recovering Oracle resources” on page 1422
748 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
Disaster recovery of a cluster
Recovering Backup Exec on a Microsoft Cluster using IDR
To fully restore a cluster on which Backup Exec is installed, you can use IDR to restore
the cluster node and all shared disks or you can rebuild the cluster. To remotely restore
the cluster catalog the media that contains the backup sets of the cluster nodes and the
shared disk.
To recover Backup Exec on a Microsoft Cluster with IDR:
1. Replace all shared disks, if necessary.
2. Run the IDR Recovery Wizard on one of the nodes. During this process, use the disk
manager to repartition all shared disks to their original configuration. Restore the
local disk, system state, and the data files to the shared disk.
3. Reboot the server.
The cluster service and all other cluster applications should come online.
4. Run the IDR Recovery Wizard on all other nodes. Restore only the local disk and
system state.
Recovering the entire cluster using a manual disaster recovery
procedure
To recover the entire cluster manually
1. On the first node you want to recover, reinstall Windows, including the last service
pack applied before the failure. For details on how to do this, see “Manual disaster
recovery of Windows computers” on page 658.
2. On the other nodes you want to recover, reinstall Windows, including the last
service pack applied before the failure. Refer to the previous Caution as well.
3. Reinstall the cluster services and bring the cluster online.
■ If you are recovering a Veritas Cluster Server, install the Storage Foundation for
Windows High Availability server components which include Volume Manager
and then use Volume Manager to create disk groups and volumes that match the
original cluster configuration.
749

Disaster recovery of a cluster
■ If you are recovering a Microsoft Cluster Server, after booting the nodes in a
cluster, make sure that the drive letters match the original cluster
configuration. If the original configuration does not match, then to a certain
extent, you can control the hard drive numbering scheme that Windows devises
by using the Disk Administrator.
4. Do one of the following:
■ If you are recovering a Veritas Cluster Server, re-install Backup Exec. For more
information, see“Installing Backup Exec with the CASO option on a Veritas
Cluster Server” on page 737.
■ If you are recovering a Microsoft Cluster Server, use the Cluster Wizard to
reinstall Backup Exec for Windows Servers on the cluster. You must use the same
settings used during the initial installation. For more information, see
“Installing Backup Exec on a Microsoft Cluster Server” on page 704.
5. Catalog the media in the cluster.
6. On the Backup Exec navigation bar on the active node, click Restore.
7. In the Restore selections pane, select the last full backup sets made of the active
node, and then select System State.
8. Do one of the following:
■ If you are recovering a Veritas Cluster Server, proceed to step 9.
■ If you are recovering a Microsoft Cluster Server, on the Properties pane, under
Settings, click Advanced and then select the Restore cluster quorum option
(this option must be selected).
9. Start the restore operation.
10. When the restore has completed, reboot the active node.
11. For each node that you need to recover, repeat step 6 through step 10.
12. After all nodes are recovered, restore the Backup Exec data files, and all other data
files, to the shared disks.
13. To restore a database to the shared disks, use the appropriate Backup Exec agent.
For procedures, read the following sections:
■ “Disaster recovery of SQL” on page 1390
■ “Disaster recovery for Exchange Server 5.5” on page 1283
750 Administrator’s Guide

■ “Disaster recovery of a Lotus Domino server” on page 1329
■ “About restoring and recovering Oracle resources” on page 1422
Chapter 18, Using Symantec Backup Exec with Server Clusters
Disaster recovery of a cluster
751

Disaster recovery of a cluster
Restoring the Microsoft Cluster data files
To fully recover the cluster, the cluster files in the MSCS folder may need to be restored.
If the Quorum disk is still available and has not changed, then you do not have to restore
the data files. If the Quorum disk is new, you need to restore the data files to the new
Quorum disk. You should disable the cluster disk driver before restoring the data files.
To restore the cluster data files
1. Shut down the secondary nodes.
2. Start the primary node.
3. On the Computer Management menu, select System Tools. Then select Device
Manager.
4. Right-click the cluster disk driver, and then select Disable.
5. Click OK.
6. Reboot the primary node.
7. On the Backup Exec navigation bar, click the arrow next to Restore.
8. Click New Restore Job.
9. In the Restore selections pane, select the most recent backup set of the MSCS folder.
The cluster service should not be running.
10. Redirect the restore of the MSCS folder to the designated Quorum disk.
11. After the cluster data files have been restored to the Quorum disk, you can enable
the cluster disk driver and start the cluster service.
12. After the cluster quorum is restored, use the cluster administrator to bring the other
cluster nodes online.
752 Administrator’s Guide

Recovering all shared disks in a Microsoft Cluster
Chapter 18, Using Symantec Backup Exec with Server Clusters
Disaster recovery of a cluster
Recover shared disks using either the Dumpcfg option from the Microsoft 2000
Resource Kit or Clusterrecovery from the Microsoft 2003 Resource Kit, which helps
automate the recovery process or by performing a manual recovery.
To recover all shared disks using Dumpcfg
1. Disable the cluster disk driver on all nodes in order to gain access to the new disk.
2. On the Computer Management menu, select System Tools. Then select Device
Manager.
3. Right-click the cluster disk driver, and then select Disable.
4. Replace and then repartition the shared disk. Use Disk Manager to verify that all
nodes have access to the same shared disk.
5. Run Dumpcfg or Clusterrecovery to replace the disk signature for the Quorum disk.
6. Using a remote Backup Exec server, restore the cluster files to the Quorum disk via
the node that has access to the disk.
7. Enable the cluster disk driver on all nodes.
8. On the Computer Management menu, select System Tools. Then select Device
Manager.
9. Right-click the cluster disk driver, and then select Enable.
10. Reboot all cluster nodes.
To recover all shared disks without using Dumpcfg
1. Uninstall all cluster applications and the cluster software from both nodes.
2. Replace and then use Disk Manager to repartition the shared disk to the previously
saved configuration.
3. Reinstall the cluster software.
4. Reinstall the cluster-aware version of Backup Exec for Windows Servers on the
cluster. For more information, see “Installing Backup Exec” on page 71.
5. Reinstall additional cluster-aware software applications on the shared disk.
6. Use Backup Exec to restore any data from the catalogs.
753

Disaster recovery of a cluster
Recovering all shared disks in a Veritas cluster
You can recover shared disks in a Veritas cluster using the Veritas Volume Manager.
To recover all shared disks using Volume Manager
1. Use Volume Manger to recreate all shared volumes and disk groups.
2. At a command prompt, type: Vmgetdisk and press ENTER or RETURN.
The command creates a file named VmDriveInfo.txt which contains information
about the disk groups and volumes.
3. Use a text editor, such as Notepad to open the VmDriveInfo.txt file.
4. From the directory in which Veritas Cluster Server was installed, use a text editor
such as Notepad to open the Main.cf.
5. Find and replace the GUIDs in Main.cf with the GUIDs in the VmDiskInfo.txt file for
the all the disk groups you want to recover.
Ensure that Lanman and MountV resources start. If you recover SQL or Exchange
you cannot start the SQL or Exchange resource, but you can start the Lanman and
MountV resources to restore data.
6. Restore the shared information using the virtual server backup.
754 Administrator’s Guide

Recovering Backup Exec in a Microsoft cluster
Chapter 18, Using Symantec Backup Exec with Server Clusters
Troubleshooting clusters
If you used the IDR option to prepare disaster recovery media for the shared disks, you
must use a manual process to recover Backup Exec on a shared disk.
To use a manual process to recover Backup Exec on a shared disk
1. Replace the shared disk if necessary, and add that disk to the cluster as a disk
resource.
2. Reinstall the cluster-aware version of Backup Exec for Windows Servers on the
cluster using the same information used in the original installation. For more
information, see “Installing Backup Exec” on page 71.
3. Use Backup Exec to restore any data from the catalogs.
Troubleshooting clusters
After I recovered my cluster and all shared disks, the cluster service will not start. Why
won’t it start and how can I get it started?
The cluster service may not start because the disk signature on the Quorum disk is
different from the original signature. If you have the Microsoft 2000 Resource Kit use
Dumpcfg.exe or Clusterrecovery from the Microsoft 2003 Resource Kit to replace the
disk. For example, type:
dumpcfg.exe /s 12345678 0
Replace 12345678 with the disk signature and replace 0 with the disk number. You can
find the disk signature and the disk number in the event log.
If you do not have the Microsoft 2000 Resource Kit, you can use -Fixquorum to change
the Quorum disk signature.
1. Start the cluster service on one node with the -Fixquorum option in the startup
parameters.
2. Open the Cluster Administrator and right-click the cluster, and then select
Properties.
3. Select the Quorum tab.
4. In the Quorum resource field, select a different disk.
5. Click OK.
755

Troubleshooting clusters
6. Stop the cluster services and then restart them without the -Fixquorum option.
You may run the -Fixquorum option as many times as needed to redesignate a
Quorum disk signature.
7. Bring all other nodes online.
I used the Checkpoint Restart option for my backups. During one of my backups, a
Microsoft cluster failover occurred. Multiple backup sets were created. When I try to verify
or restore using these backup sets, an "Unexpected End of Data" error occurs on the set
that contains the data that was backed up prior to the failover. Why does this occur? Is my
data safe?
You received this error because failover occurred in the middle of backing up the
resource, therefore the backup set was not closed on the media. However, the objects
that were partially backed up in the first backup set were completely backed up again
during restart, ensuring data integrity. Therefore, all of the objects on the media for the
given backup set should still be restored and verified.
I clustered a primary SAN server with a secondary SAN server. Now the device and media
service on the secondary server fails. Why?
This occurs when the secondary server becomes the active node and attempts to connect
to the Backup Exec database on the primary server, which is no longer available. To
correct this, you must use the Backup Exec Utility (BEUTILITY.EXE) or reinstall the
secondary server to be a primary server.
An Advanced Disk Based backup failed due to the application virtual server failover. How do
I clean up Veritas Storage Foundation for Windows cluster disk groups and their associated
volumes?
If the application virtual server fails when you use Veritas Storage Foundation for
Windows (SFW) snapshot provider to perform an advanced disk-based backup, the
backup job will fail. The original cluster disk group that the snapped volumes belong to
has moved from the primary node to a secondary node and the snapped volumes will not
be able to resynchronize with the original volumes.
The following is a description of the steps that occur for an advanced disk-based backup:
1. The snapped volumes are split from the original volumes.
2. The previously split snapped volumes are placed into a new cluster disk group.
3. The new cluster disk group is removed from the physical node where the production
virtual server is currently online and then added to the Symantec Backup Exec
media server.
756 Administrator’s Guide

Chapter 18, Using Symantec Backup Exec with Server Clusters
Troubleshooting clusters
4. The new cluster disk group will eventually be removed from the media server and
then added back into the physical node where it previously resided, regardless of
where the production virtual server is currently located.
5. The new cluster disk group joins the original cluster disk group if it is located in the
same node.
6. The snapped volumes resynchronize with the original volumes.
During this process if the production virtual fails over from the currently active node to
a secondary node, the new cluster disk group cannot rejoin the original cluster disk
group.
To manually re-join the two cluster disk groups and resynchronize the volumes:
1. Import the cluster disk group into the node, if the original cluster disk group is not
already imported into the node where the production virtual server is currently
online.
2. Rejoin the new cluster disk group with the original cluster disk group.
3. Snap back the snapped volumes with their original volumes. Ensure that the option
to synchronize using the original volume is selected.
If you are not able to import the new cluster disk group into the node where the
original cluster disk group is currently located, failover the application virtual
server back to its original node before rejoining the two cluster disk groups. For
detailed instruction on how to perform SFW operations, consult the Veritas Storage
Foundation for Windows user guide.
After I performed a manual failover of a Veritas cluster resource, my backup jobs hang. Why
won’t the backup jobs terminate?
If a manual failover of a Veritas cluster resource occurs, Veritas Cluster Server does not
dismount MountV resources if there are open handles. It is recommended that all
backup jobs complete before performing a manual failover. If a backup job does hang,
you must manually cancel the job before you can complete a manual cleanup process.
757

Troubleshooting clusters
758 Administrator’s Guide

Symantec Backup Exec
Tivoli Storage Manager
Chapter
19
The Backup Exec for Windows Servers Tivoli Storage Manager (TSM) lets you to
combine the speed and localized control of Backup Exec with the TSM policy-based
system of centralized storage management.
The TSM feature lets the TSM server’s storage resources to appear as a tape robotic
library in a list of target devices on the Backup Exec server. Backup Exec administrators
can then direct the output of any Backup Exec job to the TSM server by selecting the
name of the TSM robotic library as the destination when submitting the job.
Related Topics:
“Requirements for the TSM feature” on page 759
“Backup Exec as a TSM client” on page 760
“TSM Backup Exec components” on page 762
Requirements for the TSM feature
You must meet the following requirements before using TSM:
■ Familiarity with TSM terminology and operation, and the operating system on
which the server resides.
■ TSM versions 4.2, 4.2.1, 5.1, 5.1.5 and 5.2
■ Backup Exec for Windows Servers 9.x or later installed on the media server.
■ TCP/IP installed on the media server.
Note The Backup Exec TSM feature does not support the following communication
protocols: SPX, NetBEUI, NetBIOS or any mainframe protocols such as SNA
759

■ The Tivoli Storage Manager Administrator’s Guide and Administrator’s Reference
Guide may also be helpful.
Related Topics:
“TSM Backup Exec components” on page 762
Backup Exec as a TSM client
Backup Exec’s TSM feature lets computers running Backup Exec for Windows Servers to
become clients of a Tivoli Storage Manager server. As a TSM client, Backup Exec can use
the TSM server as storage volumes for its backup jobs.
To become a TSM client, each computer runs Backup Exec for Windows Servers, along
with the appropriate TSM option.
Note The TSM server must be prepared using the BEX.MAC macro before becoming a
TSM client.
760 Administrator’s Guide

TSM example
- AIX, AS/400, HP-UX,
MVS, OS/390, z/OS,
Sun Solaris, VM, and
Windows
- Tivoli Storage Manager
Tivoli Storage Manager
Corporate Network
TSM client TSM client
Windows 2000, Windows XP,
Windows Server 2003
Exchange Server (optional)
SQL Server (optional)
Backup Exec for Windows Server v9.x or later
Backup Exec for Tivoli Storage Manager option
After establishing communication with the TSM Server, Backup Exec recognizes the
TSM server as a virtual single tape drive robotic library and stores the contents of its
backup jobs on it.
Chapter 19, Symantec Backup Exec Tivoli Storage Manager 761

Because the TSM option is implemented within Backup Exec as an add-on logical device
driver, all standard robotic library features are available except LABM. You can also
configure a variable number of logical media slots within the virtual tape robotic
library.Backup Exec architecture and the TSM server
Backup Exec
Scheduler
and
Job Engine
Backup
Exec
Device
Handling
Device
Driver
Device
Driver
Device
Driver
Device
Driver
TCP/IP Protocol
Related Topics:
“TSM Backup Exec components” on page 762
“Requirements for the TSM feature” on page 759
TSM Backup Exec components
TSM Server
Tape Device
Tape Device
Tape Loader
Virtual Tape Loader
To prepare the TSM server to receive and store Backup Exec jobs, a new policy domain
and policy set are created for Backup Exec on the TSM server. A separate policy domain
for Backup Exec is used to distinguish Backup Exec administration console data from
other policy domains used by client data.
Then, a storage pool and two management classes are created in the new policy domain
to help manage the data sent by Backup Exec. Data sent to the TSM server by Backup
Exec is contained in two data streams:
■ The position information (PI) data stream is bound to the new management class
named MC_PI. The PI data stream is directed to the newly-created, disk-based
storage pool, named backupexec_pi.
762 Administrator’s Guide

■ Backup Exec uses the backupexec_pi storage pool to retain position information
about each backup set that it sends to the TSM server’s BACKUPPOOL storage pool.
Migration is turned off, and should remain off, for the backupexec_pi storage pool so
that the position information for each stored file is not migrated off the disk to tape,
but is always immediately available to Backup Exec. If the position information data
were migrated to tape, performance in Backup Exec would be severely impaired.
■ The virtual tape (VT) data stream is bound to the new management class MC_VT.
The VT data stream contains the actual client backup data packaged as objects. This
backup data can be stored on disk or migrated to tape, disk, or RCD and is managed
automatically by the TSM database.
Note The VT data stream must first be written to a disk-based storage pool, then
optionally migrated to tape. Configurations in which the VT data stream is sent
directly to tape are not supported.
Finally, a node named Backupexec is registered on the TSM server. All of the Backup Exec
media servers can share this node, with backup sessions from the servers differentiated
on the TSM server by the media server’s file space name.
Symantec includes a TSM server preparation macro named BEX.MAC that automatically
performs all steps necessary to prepare the TSM server. Regardless of your experience
with TSM, it is extremely important that you use the instructions under Preparing the
TSM Server and Running the BEX Macro to properly configure the TSM server.
From the Backup Exec interface, you can direct output from Backup Exec jobs to the TSM
server by selecting the name of the TSM robotic library as the destination.
Related Topics:
“Preparing the TSM server” on page 764
“BEX.MAC macro command details” on page 772
Chapter 19, Symantec Backup Exec Tivoli Storage Manager 763

Preparing the TSM server
Preparing the TSM server
This section explains the details necessary for preparing your TSM Server to accept the
Backup Exec server as a TSM client. These details include:
■ Allocating storage space using the Volume Formatting Wizard.
■ Creating a storage volume for the backupexec_pi storage pool.
■ Running the BEX.MAC preparation macro.
Note Regardless of your experience with TSM, it is extremely important to install this
TSM option using both the following instructions and the included macro,
BEX.MAC.
The TSM command conventions used within the BEX.MAC macro file may need to
be adjusted to reflect the operating system conventions your TSM server is using.
Related Topics:
“Allocating storage space” on page 764
“Creating the bexpi.dsm storage volume” on page 765
“Running the BEX.MAC macro” on page 766
Allocating storage space
The high-level macro named BEX.MAC contains commands that automate the process of
preparing the TSM server.
Note You must install the Backup Exec for Windows Servers TSM feature to obtain a
copy of the BEX.MAC macro. During the install, the BEX.MAC macro is placed in
the same directory where Backup Exec was installed.
However, for the BEX.MAC macro to run correctly, you must first use the TSM DSMFMT
utility to allocate space for the storage pool, backupexec_pi, used by the position
information (PI) data stream.
The TSM DSMFMT utility is delivered as part of the TSM server, and is used to
pre-allocate the space needed when disk-based storage pools are created. For
information on the DSMFMT utility parameters, see your TSM Administrator’s
Reference Guide.
Related Topics:
“BEX.MAC macro command details” on page 772
764 Administrator’s Guide

Creating the bexpi.dsm storage volume
Chapter 19, Symantec Backup Exec Tivoli Storage Manager
Preparing the TSM server
To format a file as a storage volume for the backupexec_pi storage pool using the Volume
Formatting Wizard
1. Using the Volume Formatting Wizard, in the Storage Management interface, create a
30MB database file named bexpi.dsm, which will act as the storage volume name for
the storage pool backupexec_pi.
For example, if you are using TSM on the Windows 2000 or Windows Server 2003
platforms, and you want to format a 30MB file to be located in the root directory,
select this location when using the wizard. Other paths can be used, but the other
paths must be reflected in the BEX.MAC.
2. After formatting the bexpi.dsm file, edit the BEX.MAC macro to associate the
backupexec_pi storage pool with the bexpi.dsm file. The macro also executes
commands that complete the preparation of the TSM server.
For the BEX.MAC macro to run correctly, the BACKUPPOOL storage pool must exist
on the TSM server.
To manually format a file as a storage volume for the backupexec_pi storage pool
1. From the command prompt on the TSM server, format a 30-MB file named bexpi.dsm
as the storage volume for the storage pool backupexec_pi, by typing:
[drive:][path]dsmfmt [drive:][path]bexpi.dsm 30
For TSM version 4.x, you must access the server command window under the
Reports option.
[drive:][path] dsmfmt The drive and directory location of the DSMFMT utility. The
location of the DSMFMT utility may vary according to the
operating system your TSM server is using.
765

Preparing the TSM server
[drive:][path]
bexpi.dsm
For example, if you are using TSM on Windows 2000, Windows XP, or Windows
Server 2003 platforms and you want to format a 30MB file to be located in the root
directory, type:
dsmfmt bexpi.dsm 30
where is the directory to create the file in.
2. After formatting the bexpi.dsm file, run the BEX.MAC macro to associate the
backupexec_pi storage pool with the bexpi.dsm file. The macro also executes
commands that complete the preparation of the TSM server.
For the BEX.MAC macro to run correctly, the BACKUPPOOL storage pool must exist
on the TSM server.
Related Topics:
“BEX.MAC macro command details” on page 772
Running the BEX.MAC macro
The drive and directory location where you want to create the
bexpi.dsm file. The DSMFMT utility specifies the bexpi.dsm file as
a storage volume for the storage pool backupexec_pi.
Important:
The BEX.MAC macro looks for the bexpi.dsm file in the root or
top-level directory, then associates it with the backupexec_pi
storage pool. If you locate the bexpi.dsm file in a directory other
than the root or top-level, you must edit the BEX.MAC macro and
change the location of the bexpi.dsm file so it can be associated
with the backupexec_pi storage pool.
30 Specifies that the size of the bexpi.dsm file is 30MB. (When using
the Volume Formatting Wizard, this value is expressed in
megabytes by default.)
If you require the file to be a size other than 30MB, use the
following formula to find the maximum filespace needed:
(number of slots +1) x 64K = maximum space required per robotic
library.
Add the maximum space required for each robotic library to find
the total space required by the bexpi.dsm file.
The TSM command conventions used within the BEX.MAC macro file may need to be
adjusted to reflect the operating system conventions your TSM server is using.
766 Administrator’s Guide

To run the BEX.MAC macro
Chapter 19, Symantec Backup Exec Tivoli Storage Manager
Preparing the TSM server
1. Using the Tivoli Server Administration tools, expand the OBJECT VIEW and then
select AUTOMATION and SERVER COMMAND SCRIPTS. See your TSM
administrator’s manual for details on creating Server Command Scripts.
If any errors occur while the macro is executing, no changes or additions are made to
the TSM server, and an error notification number appears on the final line of the
server console. For information on the error code, see your TSM administrator’s
reference guide.
2. If you want each Backup Exec server to have an individual node, you must register
each media server, using a new node name and a new password. Included in the
advantages of sharing a node between all the media servers are:
■ Easy access of backup data between Backup Exec servers since each server is
identified by the file space name of the server submitting the job.
■ Only one administration console and one password are required for any number
of Backup Exec servers.
■ A macro, BEX.MAC, included on the TSM feature CD, that automates the
association of the new storage pool, and the creation of the necessary policy
domain, policy set, management classes, and node registration. With shared
nodes, this macro is run once to complete preparation of the TSM server.
Disadvantages of using individual nodes for each Backup Exec server include:
■ Difficult access of backup data written by other Backup Exec servers since file
space names are not easily shared across nodes.
■ A unique node name and a unique password are required for each Backup Exec
server.
3. After the BEX.MAC macro completes with no errors, enable Backup Exec to run with
TSM. Refer to “Enabling TSM support” on page 768.
767

Enabling TSM support
Enabling TSM support
To install and configure the TSM feature on a Windows computer, see “Installing Backup
Exec options to the local computer” on page 85.
Note During the installation, you must know both the TSM server’s IP and port address
settings.
Related Topics:
“Changing the defaults for Backup Exec for Windows Servers” on page 768
“Preparing the TSM server” on page 764
Changing the defaults for Backup Exec for Windows Servers
When the Backup Exec media server sends backup data to the TSM server, the
management class names, node names and passwords used on the two servers must
match. If the values on the TSM server do not match the values in the Backup Exec
registry key, the TSM feature will not work.
When the TSM feature is installed, the BEX.MAC macro contains the same default names
that are in the Backup Exec server registry key:
HKEY_LOCAL_MACHINE/SOFTWARE/SYMANTEC/BACKUP EXEC FOR
WINDOWS/BACKUP EXEC/ADSM
If you change default names in the BEX.MAC macro, you must make the same changes on
the Backup Exec server by editing fields in the registry key.
If you do not use the BEX.MAC macro to prepare the TSM server, or if you register a node
manually, either use the same values that are in the registry key, or change the registry
key values to match the values you enter on the TSM server.
After you make changes in the registry key, stop and restart the Backup Exec services.
The following screen shows the registry key. Key values appear in hexadecimal format.
768 Administrator’s Guide

Registry Key Values For The TSM Option
Chapter 19, Symantec Backup Exec Tivoli Storage Manager
Changing the defaults for Backup Exec for Windows Servers
Following is a description of the values in the registry key that can be changed. The
values are given as decimal values:
Registry key values
Item Description
CommTimeout: This value must match the Communications Timeout entry in the
DSMSERV.OPT file on the TSM server. Minimum: 1 second
Maximum: 65535 seconds, Default: 60 seconds
If the If closed with X seconds setting is selected in Backup Exec,
(under Advanced node in the Backup Job Properties pane) its value
should not exceed the Communications Timeout setting on the IBM
TSM server.
If the time-out value does exceed the TSM CommTimeout value,
backups may fail with an I/O device error indicated for the TSM
drive. The TSM CommTimeout value must be coordinated with the
CommTimeout value on the TSM server, as described in the TSM
installation documentation.
769

Changing the defaults for Backup Exec for Windows Servers
Registry key values (continued)
Item Description
Enabled: Enables or disables TSM support. When this field is set to 0, TSM is
disabled. Default: 1 (on)
FileSpaceName: Changes the file space name of a media server for which you want
to view or restore data. By default, the machine name is used as the
file space name.
Multiple Backup Exec servers can send backup data to the TSM
server. If the media servers are sharing a node, which is the default,
the TSM server uses the server’s file space name to distinguish
backup sessions.
To be able to view or access backup data, you must use the same file
space name that was used when the data was sent to the TSM
server.
For example, if you backed up data to the TSM server using the
media server with the file space name of ACCT, but you are now on
a media server with the file space name of PUBS, you can view or
restore the backup data from ACCT by changing the file space name
on PUBS to ACCT and cataloging the tapes/slots you want to view.
Maximum length: 1023 characters
Default: MachineName
LoaderSlots: Sets the number of slots you can define in any given magazine
Minimum: 1 slot, Maximum: 255 slots
Default: 10 slots
NodeName: Sets the name of the node used to communicate with the TSM
server. This name must match the node name registered for Backup
Exec on the TSM server.
Maximum length: 63 characters, Default: BackupExec
770 Administrator’s Guide

Registry key values (continued)
Item Description
Related Topics:
“Changing passwords” on page 771
Changing passwords
Chapter 19, Symantec Backup Exec Tivoli Storage Manager
Changing the defaults for Backup Exec for Windows Servers
ObjectMegSize: When Backup Exec sends data to the TSM server, it sends the data
in blocks. For example, 50MB of data is sent to the TSM server in
five 10MB blocks. This key is used to change the default block size.
You may want to change the block size from the 10MB default
according to your system performance. A recommendation is to set
the object size to 1/100 of the available space in the BACKUPPOOL
storage pool, if more than 100 MB are available in that pool.
An indication that the object size is too large, or that the TSM
server is running out of storage space, is if the following errors
appear in the Event Log:
7106: Storage device “TSM Storage” reports an error on a request
to write a file mark to media. The error reported is “Hardware
failure.”
14000: An error occurs while processing an TSM command,
“ANS1311E (RC11) Server out of data storage space,” and
“ANSO2661 (RC2302) The dsmEndTxn vote is ABORT.” Check the
reason field.
Minimum: 0MB, Maximum: 3096MB, Default: 10MB
PI_MgmtClass: Sets the name of the position information management class. This
name must match the PI management class name on the TSM
server.
Maximum length: 29 characters, Default: MC_PI.
Platform: Used to further identify a session on the TSM Client Console
Monitor.
Maximum length: 15 characters, Default: MachineName_01
VT_MgmtClass: Sets the name of the virtual tape management class. This name
must match the VT management class name on the TSM server.
Maximum length: 29 characters, Default: MC_VT.
To change the password for TSM on a Backup Exec server, run ADSMCFG.EXE, found in
the Backup Exec program directory. For example: C:\PROGRAM
FILES\SYMANTEC\BACKUP EXEC\NT.
771

BEX.MAC macro command details
You are prompted to enter a new password, and then to re-enter it to confirm it. You must
make the same password change on the TSM server or you will receive an authentication
failure error when the next Backup Exec session starts.
On a shared node, if the password is changed for one Backup Exec server, it must be
changed for all servers sharing that node.
The TSM server automatically expires node passwords after a specified amount of time.
When the password expires, Backup Exec instructs the TSM server to reuse the previous
password.
Related Topics:
“BEX.MAC macro command details” on page 772
“Viewing TSM-related errors” on page 775
BEX.MAC macro command details
The high-level macro BEX.MAC automates the process of preparing the TSM server to
run with Backup Exec. By using the BEX.MAC macro, you can save time and prevent
errors. In brief, the macro:
■ Associates the storage pool backupexec_pi with the storage volume file bexpi.dsm.
■ Creates a new policy domain named VERITAS.
■ Creates a new policy set in the VERITAS domain named bex_backup.
■ Creates a management class named MC_PI.
■ Creates a management class named MC_VT, and modifies it to be the default
management class for the policy set bex_backup.
■ Creates a backup copy group (inside the MC_PI management class) with a destination
pointing to the backupexec_pi storage pool.
■ Creates a backup copy group (inside the MC_VT management class) with a
destination pointing to the TSM server’s BACKUPPOOL storage pool.
■ Activates all the changes and additions.
■ Registers a node on the TSM server named backupexec with a password of bex.
Note If you change any of the default names used in the BEX.MAC macro, you must
make the same changes on the Backup Exec server.
772 Administrator’s Guide

The following table describes the BEX.MAC macro commands:
BEX.MAC macro commands
Item Description
define stgpool backupexec_pi
disk
define volume backupexec_pi
c:\bexpi.dsm access =
READWrite
Chapter 19, Symantec Backup Exec Tivoli Storage Manager
BEX.MAC macro command details
Creates a storage pool named
backupexec_pi using the disk device class without migration
capabilities.
Backup Exec uses the backupexec_pi storage pool to store
information about each file that it backs up and stores in the TSM
server’s BACKUPPOOL storage pool. Migration is turned off for the
backupexec_pi storage pool so that the information in
backupexec_pi will always be immediately available to Backup
Exec. If the position information data in backupexec_pi were
migrated to tape, performance in Backup Exec would be adversely
affected.
Associates the file c:\bexpi.dsm with the storage pool named
backupexec_pi.
define domain VERITAS Creates a policy domain named VERITAS.
define policyset VERITAS
bex_backup
define mgmtclass VERITAS
bex_backup MC_PI
SPACEMGTECHnique =
NONE
define mgmtclass VERITAS
bex_backup MC_VT
SPACEMGTECHnique =
NONE
assign defmgmtclass
VERITAS bex_backup MC_VT
Creates a policy set in the domain VERITAS named bex_backup.
Creates a management class named MC_PI for the policy set
bex_backup in the domain VERITAS with space management
disabled. The MC_PI management class acts like a map for all the
backup data files that are stored on the TSM server. It is written to
and read from by Backup Exec during almost every operation.
Creates a management class called MC_VT for the policy set
bex_backup in the domain VERITAS. This class is where the bulk of
the data being backed up resides.
Backup Exec stores its data on the TSM server in chunks called
objects. By default, the object size is 10MB, but the size can be
changed. For details on how to change the object size, and when it
might be necessary, see “Changing the defaults for Backup Exec for
Windows Servers” on page 768.
Modifies the management class MC_VT to be the default
management class.
773

BEX.MAC macro command details
BEX.MAC macro commands (continued)
Item Description
define copygroup VERITAS
bex_backup mc_pi
DESTination = backupexec_pi
VERExists = 1 VERDeleted =
0 RETExtra = 0 RETOnly =
NOLimit
define copygroup VERITAS
bex_backup mc_vt
DESTination = BACKUPPOOL
VERExists = 1 VERDeleted =
0 RETExtra = 0 RETOnly =
NOLimit
activate policyset VERITAS
bex_backup
REGister Node backupexec
bex DOMain = VERITAS
BACKDELETE = YES
Creates a backup copy group with a destination pointing to the
backupexec_pi storage pool.
The number of backup versions to keep is set to one because
Backup Exec only recognizes one copy of backup data.
Because Backup Exec does not use the Length of Time To Retain
Only Backup Version feature, it is set to No Limit.
Creates a backup copy group for the VT data stream with a
destination pointing to the TSM server’s BACKUPPOOL storage
pool.
Note The VT data stream must first be written to a disk-based
storage pool, then optionally migrated to tape.
Configurations in which the VT data stream is sent directly
to tape are not supported.
Activates all the previously listed additions/modifications.
Registers a node on the TSM server called backupexec with a
password of bex, using the policy domain called VERITAS, and
allowing the deletion of file spaces.
If you are using individual nodes for each Backup Exec server, you
can use this node registration for one server. You must manually
register all other servers using a unique node name and password,
and using the policy domain VERITAS. You must also change the
default names on the Backup Exec server to match the new node
registration. See “Changing the defaults for Backup Exec for
Windows Servers” on page 768.
774 Administrator’s Guide

Troubleshooting TSM
Chapter 19, Symantec Backup Exec Tivoli Storage Manager
Troubleshooting TSM
If the TSM server and the Backup Exec server cannot communicate after the TSM feature
has been installed, check the following:
■ Are all the necessary API and OPT files copied to the correct locations?
■ Does the DSM.OPT file have the correct TCP/IP address and port number entered?
■ Can you ping the TSM server’s TCP/IP address? If you cannot ping the server, the
support will not work.
Related Topics:
“TSM problem resolutions for Backup Exec for Windows Servers” on page 775
Viewing TSM-related errors
To view TSM-related errors in Backup Exec for Windows Servers, look in the application
log in the Windows event viewer. The DSIERROR.LOG file is located in the directory from
which Backup Exec runs.
If the IBM client is loaded, you can also view error codes listed in a file named DSMRC.H,
located in the TSM API client directory, \ADSM32\API\INCLUDE.
The TSM API code also creates an error log file called DSIERROR.LOG. This file can also
contain information useful for isolating any TSM-related problems when using Backup
Exec.
Related Topics:
“TSM problem resolutions for Backup Exec for Windows Servers” on page 775
TSM problem resolutions for Backup Exec for Windows Servers
Item: TSM Tape and Robotic Library Devices do not appear in the Devices view.
1. Verify the Registry entries for TSM Tape and Robotic Library Devices:
HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\ADAMM\Scsi\Scsi Port
xx\Scsi Bus x\Target Id x\...
Logical Unit Id 0
DeviceName: REG_SZ: MediumChanger40
Identifier: REG_SZ: ADSM Changer Device
Type: REG_SZ: MediumChangerPeripheral
775

Viewing TSM-related errors
Logical Unit Id 1
DeviceName: REG_SZ: Tape41
Identifier: REG_SZ: ADSM Tape Device
Type: REG_SZ: TapePeripheral
2. Verify that TSM is enabled in the Registry:
HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\Backup Exec\ADSM
Enabled: REG_DWORD: 0x1
You may need to restart the Backup Exec services for the changes to take effect.
3. To restart the services, go to Control Panel - Settings. Select the Backup Exec
services, and then click Stop.
4. Click Start.
Item: Hardware Error Detected message box says, “No storage device has been
detected…”.
The Windows Event Viewer will contain an entry under Application Log.
Possible error messages and corrective actions for this problem are listed in the following
table:
TSM troubleshooting guide
Error Message Corrective Action
An error occurred while attempting to load the IBM ADSM32.DLL.
The files ADSM32.DLL, BLKHOOK.DLL, DSCAMENG.TXT and
DSM.OPT must reside in the same directory as Backup Exec.
Verify that these files are
present.
An error occurred while processing a TSM command. (610) The file DSCAMENG.TXT is
missing.
An error occurred while processing a TSM command. Options file
not found.
An error occurred while processing a TSM command. Session
rejected: TCP/IP connection failure.
The file DSM.OPT is
missing.
Verify that TCP/IP is
installed properly.
Ensure the DSM.OPT entry
for TCPServeraddress
points to a valid TSM
server.
776 Administrator’s Guide

TSM troubleshooting guide (continued)
Chapter 19, Symantec Backup Exec Tivoli Storage Manager
Viewing TSM-related errors
Error Message Corrective Action
An error occurred while processing a TSM command. Session
rejected: Unknown or incorrect ID entered.
Ensure that the Backup
Exec node exists on the
TSM server.
Item: If the object size is set too large, or the TSM server is running out of storage space,
the following errors appear in the Event Log:
■ 7106: Storage device “TSM Storage” reports an error on a request to write a file mark
to media. The error reported is “Hardware failure.”
■ 14000: An error occurs while processing a TSM command, “ANS4311E (RC11) Server
out of data storage space,” and “ANSO2661 (RC2302) The dsmEndTxn vote is
ABORT.” Check the reason field.
777

Viewing TSM-related errors
778 Administrator’s Guide

Appendix
Symantec Backup Exec
Central Admin Server Option
A
The Symantec Backup Exec for Windows Servers - Central Admin Server Option (CASO)
is installed as a separate, add-on component of Backup Exec for Windows Servers. If your
organization includes more than one Backup Exec media server, you can benefit from
using CASO.
How CASO works
When CASO is installed in a Backup Exec environment, one media server, known as the
central administration server, delegates jobs to managed media servers across the
network. Job delegation is the automatic load balancing of jobs across available managed
media servers in the CASO environment.
The following graphic shows a local area network (LAN) environment with a central
administration server and several managed media servers.
779

How CASO works
CASO-configured Backup Exec environment - LAN
The next graphic shows a wide area network (WAN) implementation of Backup Exec
with CASO installed. The same communications that occur over a LAN between the
central administration server and the managed media servers take place over a WAN.
780 Administrator’s Guide
LAN

CASO-configured Backup Exec environment - WAN
WAN
Remote
office
Managed media
servers
Jobs
Data
center
Managed media
servers
Jobs
Remote
office
Appendix A, Symantec Backup Exec Central Admin Server Option
Jobs
Remote
office
Managed media
servers
Protected
servers
How CASO works
Managed media
servers
Protected
servers
The following graphic shows CASO installed in a Backup Exec SAN Shared Storage
Network environment.
Jobs
Jobs
Central administration
server
781

How CASO works
CASO-configured Backup Exec environment - SAN Shared Storage Network
Primary
database
server/central
administration
server
Managed media
servers attached
to the SAN
Fibre-to-SCSI
bridges
SCSI tape
libraries
Managed media servers
not attached to the SAN
All backup information in the CASO environment can be centralized on the central
administration server. You can filter this information to display it for each managed
media server, or to display it by media server pools (groups of managed media servers).
The managed media servers are managed by the central administration server. They
perform the actual processing of backup and restore jobs. You create jobs on the central
administration server by associating policies and selection lists. Then, you target the
jobs to run on a managed media server or in a media server pool. The jobs are delegated,
or load-balanced, across the available storage devices on the managed media server or
media server pool. Centralized restore jobs can also be delegated to managed media
servers.
Additionally, the central administration server can function as a managed media server
and process delegated jobs. A managed media server can also run jobs that are created
locally at its local Administration Console.
Other functionality in CASO includes:
■ Centralized operations, such as backup and restore jobs, job monitoring, and
reporting.
■ Centralized information, such as device and media data, job logs, job histories, and
alerts.
■ Centralized creation of policies and selection lists, and the associations between
them. Also, the ability to copy settings to a managed media server for local job
operations. A persistent network connection between the central administration
server and the managed media server is not necessary.
782 Administrator’s Guide
LAN

Appendix A, Symantec Backup Exec Central Admin Server Option
Requirements for installing CASO
■ Media server pools, so that operations can be performed on specific groups of
managed media servers and their attached storage devices.
■ A configurable catalog location to enable centralized, distributed, or replicated
catalogs.
“Choosing the location for device and media data” on page 784
“Installing the central administration server” on page 785
“Upgrading an existing CASO installation” on page 795
Requirements for installing CASO
The system requirements (except RAM) for running CASO follow the minimum
requirements for running Backup Exec for Windows Servers. However, processor speed,
memory, and disk space requirements may increase based on the number of managed
media servers being managed, the number of protected servers being backed up, and the
amount of catalog storage space required.
On the computer on which you install the central administration server, 512 MB RAM is
required. 1 GB RAM is recommended.
Ensure the following:
■ You must have administrative rights on computers on which you want to install the
Central Admin Server Option (CASO).
■ When installing CASO on media servers in multiple domains, the Backup Exec
service account should be in the trusted domain and have administrative rights on
all media servers that are to be managed by the central administration server.
If the Backup Exec database for the central administration server is installed on a
SQL Server instance on a different computer, the account must be a domain account
with local administrative privileges on that computer as well.
■ The central administration server and the managed media servers must be part of a
domain or domains. The Central Admin Server Option is not supported in a
workgroup.
Related Topics:
“System requirements” on page 79
“Installing the central administration server” on page 785
783

Choosing the location for device and media data
Choosing the location for device and media data
During the installation of the Managed Media Server feature, you are prompted to keep
the managed media server’s device and media data either on the central administration
server or in a database on the managed media server.
The following table compares how CASO tasks are performed depending on the location
of the managed media server’s device and media data:
Comparison of CASO tasks
Task Device and media data
on the central
administration server
Delegate jobs from the central administration
server to the managed media server
See “About job delegation in CASO” on
page 818.
Manage storage devices and media on the
managed media server from the central
administration server
Hold, delete, run, cancel, and change the
priority of copied jobs from the central
administration server if the option to monitor
jobs is enabled on the managed media server
See “Configuring CASO” on page 804.
Monitor jobs that are created on the local
managed media server if the option to monitor
jobs is enabled on the managed media server
See “Configuring CASO” on page 804.
Send job status updates, job logs, and job
histories to the central administration server if
the option to monitor jobs is enabled on the
managed media server
See “Configuring CASO” on page 804.
Device and media data
on the managed media
server
Yes No
Instead, you can create
jobs on the central
administration server,
and then copy them to
the managed media
server.
See “Copying jobs
instead of delegating
jobs” on page 826.
Yes No
Yes Yes
Yes Yes
Yes Yes
784 Administrator’s Guide

Comparison of CASO tasks
Task Device and media data
on the central
administration server
Centralize, distribute, or replicate the catalog
See “Changing the catalog location” on
page 816.
Run centralized restore
See “How centralized restore works” on
page 827.
Appendix A, Symantec Backup Exec Central Admin Server Option
Installing the central administration server
Note In a CASO environment, you can add an NDMP Server only to a central
administration server or a managed media server on which the device and media
database is located.
Related Topics:
“Upgrading an existing CASO installation” on page 795
“Setting defaults for managed media servers” on page 805
“Running the Backup Exec Utility” on page 802
Installing the central administration server
Device and media data
on the managed media
server
Yes No
Only a distributed
catalog location can be
selected.
Yes No
You can browse the
backup sets and run
restore operations for
the managed media
server from the central
administration server.
Before you start the installation, review “Choosing the location for device and media
data” on page 784. During the installation of the Managed Media Server feature, you are
prompted to keep the managed media server’s device and media data either on the
central administration server or in a database on the managed media server. Your
choice affects how you can manage jobs in the CASO environment.
To install the Central Admin Server Option (CASO), install the central administration
server first, and then install the managed media servers.
785

Installing a managed media server from the central administration server
To install the central administration server
1. Install Backup Exec and CASO on the server that you want to be the central
administration server by following the instructions in “Installing Backup Exec” on
page 71.
When you are prompted for license keys for Backup Exec and any additional add-on
options to be installed, enter the CASO license key and continue with the
installation.
2. After Backup Exec and CASO are installed on the central administration server, start
Backup Exec and verify that the Media Servers view displays on the navigation bar.
3. From the Media Servers view, verify that Central Administration Server displays in
the Media Server Type column for the media server on which you installed CASO.
4. On the task pane, under Media Server Installation Tasks, click Configure managed
media server defaults.
5. On the Managed Media Servers Defaults dialog box, choose the settings that you
want applied to each new managed media server that you install. For details on these
settings, see “Setting defaults for managed media servers” on page 805.
6. Install a managed media server by following the instructions in “Installing a
managed media server from the central administration server” on page 786.
Installing a managed media server from the central
administration server
After installing the central administration server, you can push-install a managed
media server feature to a stand-alone server.
Before you install a managed media server, decide where to locate the device and media
database for the managed media server. During the installation of the managed media
server, you are prompted to keep the managed media server’s device and media data on
the central administration server or in a database on the managed media server. Your
choice affects how you can manage jobs in the CASO environment. See “Choosing the
location for device and media data” on page 784.
786 Administrator’s Guide

Appendix A, Symantec Backup Exec Central Admin Server Option
Installing a managed media server from the central administration server
To push-install a managed media server from the central administration server
1. On the central administration server’s navigation bar, click Media Servers.
2. In the task pane, under Media Server Tasks, click Install additional managed media
servers.
3. When the Welcome screen displays, click Next to begin the installation wizard.
4. Right-click Backup Exec Servers, and then do one of the following:
To browse to the remote
computer on which you
want to install Backup
Exec
To add a remote
computer manually
◆ Click Add Remote Computer.
◆ Browse the list to select all of the remote computers that you
want to install an option to.
◆ Click Next.
◆ Click Add Remote Computer Manually.
◆ Type the Domain and Computer Name.
◆ Click OK.
5. On the Remote Computer Logon Credentials panel, complete the fields as follows:
User Name Type the user name for an account that has administrative rights
on the remote computer.
Password Type the password for an account that has administrative rights
on the remote computer.
Domain Select the domain in which the remote computer is located.
Use this user name and
password when
attempting to connect to
additional computers
during the installation
Check Use this user name and password when attempting to
connect to additional computers during the installation to avoid
entering credentials separately for each remote computer that
you have selected.
6. On the Remote Installation Types dialog box, select Remote install with licensed
options, and then click Next.
787

Installing a managed media server from the central administration server
7. Do one of the following:
If you have serial
numbers for Backup Exec
and its options
If you have license keys
for Backup Exec and its
options
◆ Go to https://licensing.symantec.com to activate the product.
After you activate the product, Symantec sends license keys to
you. License keys are required to install Backup Exec and its
options. You can access the Web site from any computer that
has Internet access.
◆ When you receive your license keys, go to step 8.
8. Select one of the following methods to enter license keys:.
To enter license keys
manually
To import license
keys from a file
To install an
evaluation version
Go to step 8.
◆ Type a license key into the license key field.
◆ Click Add.
◆ Repeat for each license key for each option or agent that you want
to add.
◆ Click Import.
◆ Select the besernum.xml file.
◆ Leave the license key field blank.
◆ Proceed to step 9.
9. Click Next.
The license keys you entered are saved to the besernum.xml file, located in the
Windows or WINNT directory.
10. On the Backup Exec Features list, select Managed Media Server, and any additional
features to install.
For a description of the standard features that are available for installation with
Backup Exec, see “About Backup Exec’s standard features” on page 78.
All features that are not to be installed have a red X displayed in the feature icon. To
enable any of these options, click the X, and then click This feature will be installed
on hard drive. If the feature icon is shaded, the option is not
available for change.
788 Administrator’s Guide

11. Do one of the following:
To change the directory
where the Backup Exec
files are installed
To accept the default
directory (recommended)
Appendix A, Symantec Backup Exec Central Admin Server Option
Installing a managed media server from the central administration server
Symantec recommends that you do not select a mount point as the destination
directory because if you delete the mount point, Backup Exec is uninstalled.
12. Click Next.
Click Change to select a new directory.
Proceed to step 12.
13. Provide a user name, password, and domain for an Administrator account that the
Backup Exec system services can use, and then click Next.
See “About the Backup Exec services account” on page 74 for more information.
14. Review the text about Symantec tape device drivers, and then click Next.
The Symantec tape device drivers will not be installed during the remote
installation. To install them on the managed media server later, you can run the
Backup Exec Device Configuration Wizard.
15. Type the name of the central administration server with which this managed media
server will communicate.
If you are installing a managed media server that is also configured as a secondary
server in the SAN Shared Storage Option, you must select the primary server as the
central administration server when prompted. The primary server must be the same
server as the central administration server.
If you select another central administration server, or change the central
administration server for this managed media server, then the SAN Shared Storage
Option will not work. The primary server and the secondary server must be the
same, respectively, as the central administration server and the managed media
server.
789

Installing a managed media server from the central administration server
16. Select where to keep the device and media data for this managed media server:
On the central
administration server
On the managed media
server
17. Click Next.
Click this if you want to:
◆ Delegate jobs to this managed media server.
◆ Manage all of the storage devices and media from the central
administration server.
Click this if:
◆ There will not be a persistent network connection between the
central administration server and the managed media server.
◆ You want to reduce network traffic slightly because of a low
bandwidth network connection.
You cannot delegate jobs from the central administration server
to this managed media server, but you can copy jobs to this
managed media server. The copied jobs can then run without a
network connection to the central administration server.
See “Choosing the location for device and media data” on
page 784.
18. Review the features to be installed, verify that Managed Media Server and any
other options that you entered are selected, and then click Next.
All options that are not to be installed have an X displayed in the feature icon. To
enable any of these options, click the icon to clear the X, and then follow the
prompts to install it. If the feature icon is gray, the option is not available for
change.
19. Read the Backup Exec installation review, and then click Install.
The installation process takes several minutes to complete.
When Backup Exec is being installed to a remote computer, if the Microsoft Data
Access Components (MDAC) version on the remote computer needs to be updated to
the version that ships with Backup Exec (MDAC v2.8), you are prompted to restart
the remote computer. Go to step 20.
If the MDAC version does not need to be updated, continue with step 24.
For more information on the MDAC version that is installed with Backup Exec, see
“About Microsoft SQL Server 2005 Express Edition components installed with
Backup Exec” on page 76.
20. If the MDAC version on the remote computer must be updated, restart the remote
computer. Right-click the computer name, and then click Reboot Computer.
790 Administrator’s Guide

Appendix A, Symantec Backup Exec Central Admin Server Option
Installing a managed media server from the central administration server
21. After the computer has restarted, right-click the computer name and select the
Retry Install option. Verify the credentials when prompted.
22. To restart the remote computer now, on the Remote Installation Status dialog box,
right-click the server name, and then click Reboot Computer. You can also wait, and
restart the remote computer after you exit the installation wizard.
The installation status column displays the message that the computer is rebooting.
23. When the installation status indicates that the reboot is 100% complete, right-click
the server name again, and click View Install Log or View Push Log.
An installation job log named bkupinst.htm is created in the Application Data
folder on the computer where Backup Exec is installed. This file lists any errors that
may have occurred during installation. The last line of the log indicates if the
installation was successful and if restarting the computer is required.
24. Click Next, and then click Finish to exit the wizard.
If you did not restart the remote computer, you may need to do it now in order for
the configuration to take effect.
25. (Optional) To install device drivers for the tape storage devices that are connected to
the server, see “Configuring storage devices by using the Device Configuration
Wizard” on page 171.
After restarting the managed media server, the Backup Exec central administration
server and the managed media server begin communicating with one another. The
managed media server defaults that you set from the central administration server
are applied.
26. On the central administration server’s navigation bar, click Media Servers.
27. Make sure that the managed media server name is displayed on the right pane.
If the managed media server is not displayed on the Media Server view, and if your
network contains firewalls, you may need to open some ports between the central
administration server and the managed media server.
See “Installing a managed media server across a firewall” on page 792.
Related Topics:
“Installing Backup Exec to remote computers” on page 87
791

Installing a managed media server from the central administration server
Installing a managed media server across a firewall
If a managed media server is installed outside the firewall that the central
administration server is installed in, or if it is installed in a different firewall, the
following is required:
■ Port 3527 must be open in both directions to enable communication for the Backup
Exec Server service.
■ Port 10000 must be open for the Remote Agent for Windows Systems, which will
allow browsing for remote selections.
■ A SQL port must be open in both directions to the central administration server’s
database to enable database connections.
The Backup Exec SQL instance is configured by default to use a dynamic port. Each
time SQL Server is started, the port number can change. You must change the
dynamic port to a static port. Do one of the following:
■ For a SQL Express instance, see “Changing the dynamic port on a SQL Express
instance to a static port” on page 792
■ For a SQL 2000 or 2005 instance, see “Opening a SQL port for a SQL 2000 or 2005
instance” on page 794
Changing the dynamic port on a SQL Express instance to a static port
You must change the port on which the Backup Exec SQL Express instance for the
central administration server is running from a dynamic port to a static port. Then,
create an alias for the managed media server to allow it to connect to the SQL port on
the central administration server. After changing the port, you must restart the
Backup Exec and Microsoft SQL services on the central administration server.
To change the dynamic port for a SQL Express instance to a static port
1. On the central administration server, click Start > All Programs > Microsoft SQL
Server 2005 > Configuration Tools > SQL Server Configuration Manager.
2. Expand SQL Server 2005 Network Configuration.
3. Click Protocols for BKUPEXEC, and then in the right pane, double-click TPC/IP.
4. On the TCP/IP Properties dialog box, click the IP Addresses tab.
5. Under IPAll, in TCP Dynamic Ports, remove the value and leave the field blank.
6. Under IPAll, type in a port number for TCP Port.
792 Administrator’s Guide

Appendix A, Symantec Backup Exec Central Admin Server Option
Installing a managed media server from the central administration server
The port number can be between 1025 and 65535 and must not be in use by another
application. Refer to “What TCP/UDP ports does Backup Exec use?” on page 674 to
see a list of ports in use by Backup Exec.
7. Under the heading for the specific network interface card that is being used, such as
IP1 or IP2, change Enabled from No to Yes.
8. Under that same heading, in TCP Dynamic Ports, remove the value of 0, and type the
same port number you entered for TCP Port.
9. Click Apply.
10. You must restart the Backup Exec and SQL services.
11. Create an alias for the managed media server to allow it to connect to the SQL port
on the central administration server.
There are many methods available for creating an alias for a computer that allows it
to connect to the SQL port on the central administration server. See “To create an
alias when a SQL Express instance is used” on page 793 as an example of one
method.
To create an alias when a SQL Express instance is used
1. On the managed media server, click Start > SQL Server Configuration Manager.
2. Expand SQL Native Client Configuration.
3. Click Aliases, and then double-click the alias name that contains the central
administration server name and the Backup Exec SQL instance name.
4. On the alias properties dialog box, enter the appropriate information as described in
the following table:
Alias Name Type the name of the central administration server and the
Backup Exec SQL instance name using the format server
name\instance name.
Port No Type the port number of the remote Backup Exec SQL Server
instance that you noted in the previous procedure.
Protocol Select TCP/IP.
793

Installing a managed media server from the central administration server
Server Type the name of the central administration server and the
Backup Exec SQL instance name using the format server
name\instance name.
5. Click Apply, and then click OK.
6. Close the SQL Server Configuration Manager utility.
Opening a SQL port for a SQL 2000 or 2005 instance
You must find the port number on which the Backup Exec SQL 2000 or 2005
instance for the central administration server is running, and then create an alias
for the managed media server.
To open a SQL port for a SQL 2000 or 2005 instance
1. On the central administration server, go to \Program Files\Microsoft SQL
Server\80\Tools\Binn and double-click svrnetcn.exe.
2. On the General tab, select the Backup Exec SQL instance.
3. Under Enabled Protocols, select TCP/IP, and then click Properties.
4. Note the port number that is displayed.
5. Create an alias for the managed media server to allow it to connect to the SQL port
on the central administration server.
There are many methods available for creating an alias for a computer that allows it
to connect to the SQL port on the central administration server. See “To create an
alias when a SQL 2000 or 2005 instance is used” on page 794 as an example of one
method.
To create an alias when a SQL 2000 or 2005 instance is used
1. On the managed media server, to create an alias for the managed media server, go to
\Windows\System32 and double-click cliconfg.exe.
2. On the Alias tab, click Add.
3. In the Server alias field, type:
server name\instance name
794 Administrator’s Guide

4. Under Network libraries, select TCP/IP.
5. In the Server name field, type:
server name\instance name
6. Uncheck Dynamically determine port.
Appendix A, Symantec Backup Exec Central Admin Server Option
Upgrading an existing CASO installation
7. In the Port number field, type the port number of the remote Backup Exec SQL
Server instance.
Related Topics:
“Using Backup Exec with firewalls” on page 405
Upgrading an existing CASO installation
In an existing CASO environment, upgrade the central administration server, and then
upgrade the managed media servers.
If necessary, you can perform rolling upgrades in the CASO environment. That is, you
can upgrade the central administration server first, and then upgrade the managed
media servers over a period of time. Symantec recommends that you do not keep a mix
of versions in the CASO installation for an extended time. Key functionality for
administering managed media servers is missing in a mixed-version environment, and
decreases your ability to properly administer the CASO environment.
After you upgrade the central administration server to Backup Exec 11d, the following
operations are supported on the Backup Exec 10d managed media servers:
■ Backup
■ Restore
■ Inventory
■ Catalog
If the catalogs were located on the central administration server, they remain there
after the upgrade. If the catalogs were located on the managed media servers, then after
the upgrade, they are distributed between the managed media servers and the central
administration server.
Note The migration of Network Storage Executive 8.6 is only supported to Backup Exec
10d. After an upgrade to Backup Exec 10d, then an upgrade to Backup Exec 11d
can be performed.
795

Upgrading an existing CASO installation
Related Topics:
“About catalog locations” on page 814
“Changing the catalog location” on page 816
“Upgrading an existing central administration server” on page 796
“Upgrading an existing managed media server” on page 798
Upgrading an existing central administration server
The central administration server must be upgraded before any managed media servers
are upgraded. For information about performing rolling upgrades, see “Upgrading an
existing CASO installation” on page 795.
Before upgrading Backup Exec, run a database maintenance job to delete job histories
and catalogs that you no longer need in order to shorten the upgrade window.
For details, see “Configuring database maintenance” on page 162.
To upgrade an existing central administration server
1. Verify that the latest service pack for Backup Exec 10d is installed.
2. Place all scheduled jobs on hold on the central administration server and the
managed media servers.
See “Placing an active job on hold” on page 446.
3. Allow all active jobs to complete.
4. From the installation CD browser, select the option to install Symantec Backup Exec.
5. On the Welcome panel, click Next.
6. Select I accept the terms of the license agreement, and then click Next.
7. Check Local Install, and then click Install Backup Exec software and options.
8. Click Next.
796 Administrator’s Guide

9. Do one of the following:
If you have serial
numbers for Backup Exec
and its options
If you have license keys
for Backup Exec and its
options
Appendix A, Symantec Backup Exec Central Admin Server Option
Upgrading an existing CASO installation
10. Enter the license key for the Central Administration Server Option, and for each
Backup Exec option that you want to install, and then click Next.
Read the Installation Review. To add additional license keys, click Back until the
Symantec Backup Exec License Keys page is displayed. Enter the license keys, and
then click Next to continue.
The default location is C:\Program Files\Symantec\Backup Exec.
11. On the Back Up Existing Catalog and Data page, enter or browse to a directory to
which all existing catalogs and data will be backed up. The default location is:
C:\Program Files\Symantec\Backup Exec\Data
If you do not want to keep previous catalogs and data, click Do not back up previous
data and catalogs.
12. Click Next to continue.
An upgrade summary is displayed. When the upgrade is complete, communication
with the managed media servers is automatically enabled.
13. Release all jobs from hold.
See “Placing an active job on hold” on page 446.
14. Upgrade some or all of the managed media servers.
◆ Go to https://licensing.symantec.com to activate the product.
After you activate the product, Symantec sends license keys to
you. License keys are required to install Backup Exec and its
options. You can access the Web site from any computer that
has Internet access.
◆ When you receive your license keys, go to step 10.
Go to step 10.
797

Upgrading an existing CASO installation
Upgrading an existing managed media server
The central administration server must be upgraded before any managed media servers
are upgraded. For information about performing rolling upgrades, see “Upgrading an
existing CASO installation” on page 795.
Before upgrading Backup Exec, run a database maintenance job to delete job histories
and catalogs that you no longer need in order to shorten the upgrade window.
For details, see “Configuring database maintenance” on page 162.
To upgrade an existing managed media server
1. Verify that the latest service pack for Backup Exec 10d is installed.
2. Pause the managed media server to prevent the central administration server from
delegating jobs to it. If jobs are running, let them finish or cancel them before
beginning the upgrade.
See “Pausing and resuming a managed media server” on page 836.
3. On the managed media server that you want to upgrade, do one of the following:
To choose where to keep
the device and media
data
To keep the managed
media server’s device and
media data centralized
on the central
administration server
4. Resume the managed media server.
See “Pausing and resuming a managed media server” on page 836.
Related Topics:
“Running the Backup Exec Utility” on page 802
Follow the instructions in “Installing a managed media server
from the central administration server” on page 786.
Follow the instructions in “Changing a media server to a managed
media server” on page 801.
To move the device and media data to a database on the managed
media server at a later time, you must run a separate application
called Backup Exec Utility. Backup Exec Utility will prompt you to
retarget jobs and media server pools to use the new device and
media data location on the local managed media server.
798 Administrator’s Guide

Appendix A, Symantec Backup Exec Central Admin Server Option
Changing a Backup Exec media server to a central administration server
Changing a Backup Exec media server to a central
administration server
You can change a stand-alone Backup Exec media server to a central administration
server.
To change a Backup Exec media server to a central administration server
1. On the media server that you want to be the central administration server, start
Backup Exec.
2. On the Tools menu, click License Keys and Installation.
3. On the Welcome screen, click Next.
4. Check Local Install, and then click Next.
5. Do one of the following:
If you have serial
numbers for Backup Exec
and its options
If you have license keys
for Backup Exec and its
options
◆ Go to https://licensing.symantec.com to activate the product.
After you activate the product, Symantec sends license keys to
you. License keys are required to install Backup Exec and its
options. You can access the Web site from any computer that
has Internet access.
◆ When you receive your license keys, go to step 6.
Go to step 6.
6. Select one of the following methods to enter license keys:.
To enter license keys
manually
To import license
keys from a file
To install an
evaluation version
◆ Type a license key into the License Key field.
◆ Click Add.
◆ Repeat for each license key for each option or agent that you want
to add.
◆ Click Import.
◆ Select the besernum.xml file.
◆ Leave the license key field blank.
◆ Proceed to step 9.
799

Changing a Backup Exec media server to a central administration server
A license key is not required for a fully functional Evaluation version.
7. Click Next.
The license keys you entered are saved to the besernum.xml file, located in the
Windows or WINNT directory.
8. On the Backup Exec Features list, select Central Administration Server, and any
additional features to install.
For a description of the standard features that are available for installation with
Backup Exec, see “About Backup Exec’s standard features” on page 78
All features that are not to be installed have a red X displayed in the feature icon. To
enable any of these options, click the X, and then click This feature will be installed
on hard drive. If the feature icon is gray, the option is not
available for change.
9. Do one of the following:
To change the directory
where the Backup Exec
files are installed
To accept the default
directory (recommended)
Symantec recommends that you do not select a mount point as the destination
directory because if you delete the mount point, Backup Exec is uninstalled.
10. Click Next.
Click Change to select a new directory.
Proceed to step 10.
11. Read the Backup Exec installation review, and then click Install.
The Backup Exec files are installed to the directory.
12. Click Finish when the Symantec Install Wizard Completed panel displays.
800 Administrator’s Guide

Appendix A, Symantec Backup Exec Central Admin Server Option
Changing a Backup Exec media server to a central administration server
Changing a media server to a managed media server
You can change a stand-alone Backup Exec media server to a managed media server.
Note the following exceptions:
■ If a central administration server is already set for a managed media server, you
must use the Backup Exec Utility to change to another central administration
server.
■ If the Backup Exec SAN Shared Storage Option is installed, the Set Central
Administration Server option is not available on the secondary server.
To change a media server to a managed media server
1. Verify that the central administration server is running.
2. Start Backup Exec at the stand-alone media server.
3. From the Tools menu, click Set Central Administration Server.
4. Enter the name of the central administration server.
An informational alert appears stating that the media server will be managed by the
specified central administration server.
5. Click OK.
6. Click Close.
7. Restart the Backup Exec media server.
8. On the central administration server’s navigation bar, click Media Servers.
The new managed media server displays in the All Media Servers node.
If the managed media server is not displayed on the Media Server view, and if your
network contains firewalls, you may need to open some ports between the central
administration server and the managed media server. See “Installing a managed
media server across a firewall” on page 792.
Related Topics:
“Installing a managed media server from the central administration server” on page 786
“Running the Backup Exec Utility” on page 802
801

Changing a managed media server to a stand-alone media server
Changing a managed media server to a stand-alone media
server
You can change a managed media server to a stand-alone media server by deleting it
from the Media Servers view.
To change a stand-alone media server back to a managed media server again, see
“Changing a media server to a managed media server” on page 801.
To change a managed media server to a stand-alone media server
1. On the central administration server, from the navigation bar, click Media Servers.
2. Select the managed media server that you want to delete.
3. On the task pane, under General Tasks, click Delete.
Running the Backup Exec Utility
To move the location of the device and media data, or to set a different central
administration server for managed media servers, you must run a separate application
called Backup Exec Utility.
Use the Backup Exec Utility only with the guidance of Symantec Technical Support.
Improper use of this utility can result in configuration changes that may prevent
Backup Exec from running.
To run the Backup Exec Utility
1. From the Backup Exec installation directory, in \Program
Files\Symantec\Backup Exec, double-click BEUtility.
2. Refer to the help for information about performing tasks. On the Backup Exec
Utility menu bar, click Help.
802 Administrator’s Guide

Appendix A, Symantec Backup Exec Central Admin Server Option
Uninstalling Backup Exec from a managed media server
Uninstalling Backup Exec from the central administration server
Before you uninstall Backup Exec from the central administration server, you must
delete all managed media servers from the Media Servers view on the central
administration server.
Caution Failure to uninstall in the following sequence may result in long delays when
shutting down Backup Exec services during the uninstall of Backup Exec on
the managed media servers.
To uninstall Backup Exec from the central administration server
1. On the central administration server’s navigation bar, click Media Servers.
2. Select a managed media server.
3. On the task pane, under General Tasks, click Delete.
4. Repeat these steps for each managed media server that is displayed in the Media
Servers view.
5. After deleting all managed media servers, uninstall Backup Exec on the central
administration server. See “Uninstalling Backup Exec” on page 124.
Uninstalling Backup Exec from a managed media server
You must delete the managed media server from the Media Servers view on the central
administration server before you uninstall Backup Exec.
To uninstall Backup Exec from a managed media server
1. On the central administration server, from the navigation bar, click Media Servers.
2. Select the managed media server that you want to delete.
3. On the task pane, under General Tasks, click Delete.
4. After deleting the managed media server from the Media Servers view on the central
administration server, uninstall Backup Exec from the managed media server. See
“Uninstalling Backup Exec” on page 124.
803

Configuring CASO
Configuring CASO
After installing CASO, you can do the following to configure your CASO environment.
Configuring the CASO environment
If you want to... Go to...
Set defaults for a managed media server “Setting defaults for managed media servers”
on page 805
Accommodate a low bandwidth network
connection or reduce network traffic
Customize thresholds for unresponsive
managed media servers to enable job
recovery, and customize how often managed
media servers send active job status updates
Customize settings for job log and job history
information to remain on managed media
servers, or to be copied and moved
automatically to the central administration
server.
Change the location of the device and media
data
Delegate jobs from the central
administration server to any available
devices
Perform operations on a group of managed
media servers
View alerts that are generated on a managed
media server
“Reducing network traffic in CASO” on
page 805
“Setting communication thresholds and
active job status updates” on page 808
“Copying logs and histories to the central
administration server” on page 810
“Running the Backup Exec Utility” on
page 802
“Creating device pools” on page 177
“Grouping managed media servers in pools”
on page 818
“Configuring alerts in CASO” on page 812
Configure notification when alerts occur “Configuring notification in CASO” on
page 813
View default error-handling rules for
recovering failed jobs
Let a delegated backup job use any network
interface to access remote agents if the
selected network interface is unavailable
“Recovering failed jobs in CASO” on page 835
“Enabling managed media servers to use any
available network interface card” on page 814
804 Administrator’s Guide

Reducing network traffic in CASO
Appendix A, Symantec Backup Exec Central Admin Server Option
Configuring CASO
To accommodate a low bandwidth network connection or to reduce network traffic, you
can:
■ Reduce the frequency of job status updates that are sent from the managed media
servers to the central administration server.
■ Prevent jobs that are created on the local managed media servers from being
monitored by the central administration server.
■ Reduce the frequency that job logs and job histories are sent from the managed
media servers to the central administration server.
■ Increase the amount of time that Backup Exec waits before changing the media
server’s status if the media server becomes unresponsive.
■ Keep the catalogs on the managed media server (distributed). If there is a persistent
network connection between the central administration server and the managed
media server, then you can browse the catalog and perform restore operations from
both servers, regardless of the catalog location.
Related Topics:
“Setting defaults for managed media servers” on page 805
“Copying logs and histories to the central administration server” on page 810
“Setting communication thresholds and active job status updates” on page 808
“Changing the catalog location” on page 816
Setting defaults for managed media servers
Backup Exec sets communication defaults automatically. However, you can change the
default settings. Review “Reducing network traffic in CASO” on page 805 for information
on setting defaults to accommodate a low-bandwidth network.
To set defaults for managed media servers
1. On the central administration server’s navigation bar, click Media Servers.
2. Do one of the following:
To set defaults to apply to
a managed media server
when it is installed
◆ On the task pane, under Media Server Installation Tasks, click
Configure managed media server defaults.
◆ Proceed with step 3.
805

Configuring CASO
To set defaults for an
existing managed media
server
To set defaults for a
group of managed media
servers in a pool
◆ Right-click the managed media server for which you want to
configure settings, and then click Properties.
◆ Click the Settings tab.
◆ Proceed with step 3.
◆ Select or create the media server pool that contains the
managed media servers to which you want to apply new
settings.
◆ Right-click the media server pool, and then click Properties.
◆ Click the Settings tab.
◆ Check Apply these settings to all of the managed media
servers in the pool.
◆ Proceed with step 3.
3. On the Settings tab, select the appropriate options as follows.
Fast connection
with the central
administration
server
Slow connection
with the central
administration
server
Click this option to configure frequent communication between the
central administration server and the managed media server. By
default, when you choose this setting, job status updates are sent
every 10 seconds to the central administration server. Job logs and
job histories are sent whenever a job on the managed media server
completes.
Click this option to configure less frequent communication
between the central administration server and the managed media
server. By default, when you choose this setting, job status updates
are sent every 120 seconds to the central administration server.
Job logs and job histories are sent only when a job on the managed
media server fails.
Custom settings Click this option to enable the Edit Custom Settings button.
Click Edit Custom Settings to set specific defaults for job recovery
thresholds, for sending job status updates, and for sending job logs
and histories.
See “Setting communication thresholds and active job status
updates” on page 808 and “Copying logs and histories to the central
administration server” on page 810.
806 Administrator’s Guide

Edit Custom
Settings
Monitor jobs that
are created on the
local managed
media server in
addition to the jobs
that are delegated
from the central
administration
server
Display alert when
the difference in
seconds between
the clocks on the
managed media
server and the
central
administration
server is more than
4. Click OK.
Related Topics:
“Setting communication thresholds and active job status updates” on page 808
“Managing jobs in CASO” on page 834
Appendix A, Symantec Backup Exec Central Admin Server Option
Configuring CASO
Click Edit Custom Settings to set specific defaults for job recovery
thresholds, for sending job status updates, and for sending job logs
and histories.
See “Setting communication thresholds and active job status
updates” on page 808 and “Copying logs and histories to the central
administration server” on page 810.
Check Monitor jobs that are created on the local managed media
server in addition to the jobs that are delegated from the central
administration server to view jobs that are created on the local
managed media server as well as delegated jobs.
You can also hold, delete, run, cancel, and change the priority order
of the jobs that are created on or copied to the local managed media
server.
Note Jobs that are created by policies on the managed media
server cannot be deleted from the central administration
server.
Check Display alert when the difference in seconds between the
clocks on the managed media server and the central
administration server is more than to enable Backup Exec to
create an alert if the clock on the managed media server differs
from the clock on the central administration server. Set the
number of seconds that, if exceeded, generates the alert.
CASO monitors the internal computer clocks on both the managed
media servers and the central administration server. If time
differences develop between the central administration server and
the managed media servers, jobs could run at unexpected times. To
prevent problems, the time reported on managed media server
clocks should match the time reported on the central
administration server clock. If you receive time difference alerts,
reset the managed media server system clock to match the system
clock on the central administration server.
Note If you change the system time on either the managed media
server or the central administration server, you must restart
the Backup Exec services on the system.
807

Configuring CASO
Setting communication thresholds and active job status updates
The communication statuses determine how the central administration server
processes current and future jobs that are delegated to an unresponsive managed media
server. For more information, see “What happens when communication thresholds are
reached” on page 810.
You can change the thresholds that trigger the communication statuses when managed
media servers become unresponsive. You can also set how often the managed media
server sends active job status updates to the central administration server. The
frequency affects the network traffic.
To set communication thresholds and the frequency of active job status updates
1. On the central administration server’s navigation bar, click Media Servers.
2. Do one of the following:
To set defaults to apply to
a managed media server
when it is installed
To set defaults for an
existing managed media
server
To set defaults for a
group of managed media
servers in a pool
◆ On the task pane, under Media Server Installation Tasks, click
Configure managed media server defaults.
◆ Proceed with step 3.
◆ Right-click the managed media server for which you want to
configure settings, and then click Properties.
◆ Click the Settings tab.
◆ Proceed with step 3.
◆ Select or create the media server pool that contains the
managed media servers to which you want to apply new
settings.
◆ Right-click the media server pool, and then click Properties.
◆ Click the Settings tab.
◆ Check Apply these settings to all of the managed media
servers in the pool.
◆ Proceed with step 3.
3. On the Settings tab, click Custom settings, and then click Edit Custom Settings.
808 Administrator’s Guide

4. On the Configuration tab, change the defaults as appropriate:
Communication
Stalled (no more
jobs are queued to
the managed media
server)
No Communication
(jobs are recovered
from the managed
media server)
Send active job
status updates in
seconds to the
central
administration
server
5. Click OK.
Appendix A, Symantec Backup Exec Central Admin Server Option
Configuring CASO
Type the amount of time before the managed media server’s status
changes to Communication Stalled if the managed media server is
unresponsive.
The central administration server does not delegate jobs to the
managed media server when it has a status of Communication
Stalled. Job delegation resumes if the managed media server
returns to an Enabled status before the threshold is exceeded.
The default threshold is five minutes.
Type the amount of time before the managed media server’s status
changes from Communication Stalled to No Communication.
When the status of the managed media server changes from
Communication Stalled to No Communication, the central
administration server marks the active jobs on the managed media
server as Failed. The custom error-handling rule Recovered Jobs is
applied to any job that is active when the No Communication status
appears.
The default threshold is 15 minutes.
Check Send active job status updates in seconds to the central
administration server to send a job status update to the central
administration server. You can adjust the number of seconds that a
managed media server waits between sending job status updates to
the central administration server. To preserve network bandwidth
when many jobs are running, increase the amount of time between
job update statuses. Decrease the amount of time if you want to
send more updates.
The default is 10 seconds, which provides near real-time
monitoring. This setting is recommended only for fast network
connections.
For low bandwidth network connections, consider a setting of 120
seconds. This frequency allows updates to be displayed for a
medium-sized job while still significantly decreasing the network
traffic caused by job status updates.
If you uncheck the check box, job status updates are not sent. Job
progress is not displayed on the central administration server.
When the job is complete, the Job History view on the central
administration server is updated.
809

Configuring CASO
What happens when communication thresholds are reached
In a CASO environment, communications that occur between managed media servers
and the central administration server can sometimes be disrupted even if network
communications are normal. If job-related communication disruptions occur between a
managed media server and the central administration server, the managed media
server’s communication status changes from Enabled to Stalled. The jobs waiting to be
processed by the managed media server are held in the managed media server’s job
queue until the communications are restored.
You can set the amount of time that Backup Exec waits before changing the managed
media server’s status if it becomes unresponsive. The configuration settings use time
thresholds that when exceeded, change the managed media server statuses that are
reported to the central administration server. These statuses include Stalled and No
Communication. When a managed media server’s status changes to Stalled or No
Communication, the central administration server changes how it handles current and
future jobs delegated to the stalled managed media server.
For example, if communications from a managed media server are not received at the
central administration server after the set amount of time, the central administration
server changes the media server’s communication status to Stalled. Job delegation to the
managed media server is suspended as it continues to wait for the managed media
server to return to an Enabled status. Jobs are delegated to other managed media servers
that are represented in the destination device or media server pool.
CASO continues to monitor the amount of time during which no communications are
received from the managed media server. After a set amount of time passes after a
Stalled status appears, CASO changes the status of the managed media server to No
Communication. CASO marks the jobs as Failed, and then begins job recovery by
invoking the custom error handling rule Recovered Jobs for any job that is active at the
time the No Communication status appears.
To change the thresholds set for the communication statuses, go to “Setting
communication thresholds and active job status updates” on page 808.
Copying logs and histories to the central administration server
During and after job processing, job log and job history information is generated for
each job that is processed at each managed media server. By default, this information is
stored locally at the managed media server where the jobs are processed. However, both
job log and job history information can be copied and sent automatically to the central
administration server, depending on the options you select in the Job Logs and
Histories tab.
810 Administrator’s Guide

To copy logs and histories to the central administration server
1. On the central administration server’s navigation bar, click Media Servers.
2. Do one of the following:
To set defaults to apply to
a managed media server
when it is installed
To set defaults for an
existing managed media
server
To set defaults for a
group of managed media
servers in a pool
Appendix A, Symantec Backup Exec Central Admin Server Option
Configuring CASO
◆ On the task pane, under Media Server Installation Tasks, click
Configure managed media server defaults.
◆ Right-click the managed media server for which you want to
configure settings, and then click Properties.
◆ Click the Settings tab.
◆ Select or create the media server pool that contains the
managed media servers to which you want to apply new
settings.
◆ Right-click the media server pool, and then click Properties.
◆ Click the Settings tab.
◆ Check Apply these settings to all of the managed media
servers in the pool.
3. On the Settings tab, click Custom settings, and then click Edit Custom Settings.
4. On the Job Logs and Histories tab, select the appropriate options as follows.
Never Click this option to keep the job log on the managed media server
where the job ran.
Every day at Click this option to send a copy of the job log to the central
administration server every day at the time you specify.
On job completion Click this option to send a copy of the job log to the central
administration server when the job completes.
Only if the job fails Check Only if the job fails to send a copy of the job log to the
central administration server only if the job fails.
811

Configuring CASO
Only when
required by job
type
5. Click OK.
Configuring alerts in CASO
Click this option to send a copy of the job history to the central
administration server whenever the managed media server
processes a job type that requires the central administration server
to store the job history.
The job types Set Copy and Synthetic Backup require job histories
to be stored on the central administration server.
Every day at Click this option to send a copy of the job history to the central
administration server every day at a specified time.
On job completion Click this option to send a copy of the job history to the central
administration server when the jobs complete.
Only if the job fails Check Only if the job fails to send a copy of the job history to the
central administration server only if the job fails.
In a Central Admin Server Option environment (CASO), alerts generated on a managed
media server are automatically rolled up to the central administration server. To see
those alerts on the central administration server, you must configure alert categories to
enable or disable alerts on each managed media server in the CASO environment, and on
the central administration server itself.
After you respond to and clear the active alert on the central administration server, the
alert is cleared on the managed media server as well.
If you enable Backup Exec alerts on a managed media server without enabling alerts on
the central administration server, alerts appear only on the managed media server
where they are generated; they will not appear on the central administration server.
Enable and configure alerts at the central administration server, and then copy the alert
configurations to a managed media server. When the alert is generated on a managed
media server, it appears on both the managed media server and the central
administration server.
On the central administration server, you can view alerts for all managed media servers,
or you can filter the alerts to view only those for a specific managed media server or
media server pool.
812 Administrator’s Guide

To configure specific alerts on the central administration server
1. Start Backup Exec on the central administration server.
2. From the Tools menu, click Alert Categories.
Appendix A, Symantec Backup Exec Central Admin Server Option
Configuring CASO
3. Scroll through the list of alert categories until you find the category you want to
configure.
4. From Category Properties, select the check box Enable alerts for this category.
5. Click OK.
To copy specific alerts to managed media servers.
1. From the Tools menu, select Copy Settings to Media Servers.
2. Under Select Settings to Copy, select the check box for Alert Configuration.
3. Click Add.
4. Enter the name of a managed media server to which the configuration will be copied.
5. Click OK.
6. On the Copy Settings dialog box, click OK.
An alert on the central administration server will confirm that the copy succeeded.
7. Click OK to clear the active alert.
Related Topics:
“Alerts and notifications” on page 527
“Copying configuration settings” on page 156
Configuring notification in CASO
In a Central Admin Server Option (CASO) environment, you can configure a notification
on either the central administration server or the managed media server. Regardless of
where you configure the notification, if it is for a delegated job, it is sent by the central
administration server.
You can choose to notify the local administrator of the managed media server, or the
administrator of the central administration server, or both.
813

Configuring CASO
Related Topics:
“Alerts and notifications” on page 527
Enabling managed media servers to use any available network
interface card
By default, jobs that are delegated or copied to a managed media server from the central
administration server use the network and security settings that are set on the managed
media server.
However, you can select an option on the central administration server to let a job use
any network interface to access remote agents if the selected network interface is
unavailable. Enabling this option for a backup job lets the managed media server use an
alternative network interface to run important backup jobs that would otherwise fail to
run.
To enable managed media servers to use any available network interface card
1. On the central administration server’s navigation bar, click the arrow next to
Backup.
2. Click New Backup Job.
3. In the task pane, under Settings, click Network and Security.
4. Check Allow managed media server to use any network interface to access remote
agents.
5. Click OK.
Related Topics:
“Specifying backup networks” on page 398
About catalog locations
In the CASO environment, you can choose the catalog location. Regardless of the catalog
location, if a persistent network connection is available between the central
administration server and the managed media server, then you can browse the backup
sets in the catalog and perform restore operations from both servers.
Before you change the catalog location, review “Changing the catalog location” on
page 816.
814 Administrator’s Guide

Appendix A, Symantec Backup Exec Central Admin Server Option
Configuring CASO
Distributed catalog
Image files, which are small files that contain information about the backup set, are
distributed to the central administration server from every managed media server.
History files, which contain detailed information about the backup set, remain on the
managed media server.
Note It is important that you back up the catalog files on the managed media server
since most catalog information is kept here when the distributed catalog location
is used.
When the catalog is distributed, the view of the restore selections on the central
administration server displays only the backup set at the volume level. Backup set
details are not displayed if the managed media server that created this backup set is not
available, but the whole volume can be restored from the central administration server.
A distributed catalog provides increased performance, default centralized restore
capability, and decreased network traffic. If a managed media server does not have a
persistent connection to the central administration server, then whenever the managed
media server does connect, the image files in the catalog are automatically distributed to
the central administration server. The temporary increase in network traffic caused by
the catalog distribution is not significant.
Centralized catalog
All catalog files and information for the managed media server are kept on the central
administration server.
Replicated catalog
All catalog files are replicated from the managed media server to the central
administration server. Both the managed media server and the central administration
server store the catalog produced by the managed media server.
Deletions of catalog files are replicated between the managed media server and the
central administration server only when the catalog files are deleted by Backup Exec
according to the catalog settings. If catalog files on the managed media server are
deleted as a result of an archive operation or a manual deletion, the deletions are
replicated the next time that the catalogs are synchronized.
815

Configuring CASO
Changing the catalog location
You can change the catalog location to distributed, centralized, or replicated in the
CASO environment.
Changing the catalog location can cause catalog files to be copied or moved between the
managed media server and the central administration server, which can increase
network traffic. Additionally, you must restart the Backup Exec services on the managed
media server on which the catalog location is changed.
When choosing the catalog location, consider the following:
■ If there is enough available disk space on the managed media server to keep a
distributed or replicated catalog.
■ If there is enough network bandwidth to handle the traffic generated by a
centralized or replicated catalog. Centralized and replicated catalogs require a high
bandwidth network connection.
■ If it is important for your data recovery needs to keep catalog information in one
location. For example, when the catalog location is centralized or replicated, all
catalog information is kept in one location, which makes it easier to back up. When
the catalog location is distributed, most catalog information is kept on the managed
media server.
For details on catalog locations, see “About catalog locations” on page 814.
To change the catalog location
1. On the central administration server, click the Media Servers tab.
2. Right-click the managed media server for which you want to change the catalogs,
and then click Properties.
3. On the media server properties dialog box, click the Advanced tab.
816 Administrator’s Guide

4. Choose one of the following options
Managed media server
(distributed)
Central administration
server (centralized)
Related Topics:
“Restoring data” on page 483
“Setting catalog defaults” on page 485.
“How centralized restore works” on page 827
“How CASO restores data that resides on multiple devices” on page 828
Appendix A, Symantec Backup Exec Central Admin Server Option
Configuring CASO
Click this option to distribute catalog files between the central
administration server and the managed media server.
From the central administration server, you cannot browse
backup sets on a managed media server in a catalog that was
created from Backup Exec version 9x or earlier.
If the device and media data are kept in a local database on the
managed media server, then the distributed location is the only
catalog location that is available.
Select this option if you have a low-bandwidth network
connection.
Click this option to keep all catalog files on the central
administration server.
A high-bandwidth network connection should be available if this
location is selected.
Both servers (replicated) Click this option to replicate all catalog files from the managed
media server to the central administration server.
If a managed media server is unavailable and the device is not
shared (that is, if SAN Shared Storage Option is not installed on
it), you can still browse the catalog from the central
administration server. However, you cannot run a restore job
since the managed media server is unavailable.
A high-bandwidth network connection should be available if this
location is selected.
817

Grouping managed media servers in pools
About job delegation in CASO
Job delegation is the automatic load balancing of jobs among the various storage devices
that are attached to the Backup Exec managed media servers. The job is created on the
central administration server, but can be run on any managed media server.
When the storage devices are logically grouped in device pools, and as the storage
devices become available, they process jobs that are delegated from the central
administration server. For example, if a device pool contains two storage devices and
one is busy processing a job, the central administration server automatically delegates
another job to the idle storage device.
Jobs are automatically created and submitted to the central administration server’s job
queue after a policy is applied to a selection list. Queued jobs are processed in priority
order. Depending on job parameters and system configuration, the central
administration server then delegates jobs to available storage devices in a selected
device pool.
Templates within a policy can be sent to either a device pool, a specific device, or to
devices in a media server pool. Device pools can consist of devices that are attached to a
single managed media server, or they can consist of devices from different managed
media servers. The advantage of job delegation is realized when a template is sent to a
drive pool that spans managed media servers. When multiple managed media servers
and their devices are available to the central administration server for job delegation,
the efficiency of Backup Exec is greatly improved because job processing does not have
to wait for a specific device or managed media server to become available.
Related Topics:
“Configuring CASO” on page 804
“Grouping managed media servers in pools” on page 818
Grouping managed media servers in pools
In a CASO environment, you can group multiple managed media servers together into
media server pools. If you create a pool of managed media servers, all of the device pools
on those managed media servers are available for job delegation. If there are multiple
devices attached to each of the managed media servers in the media server pool, you can
create multiple, smaller device pools that are made up of fewer storage devices. Use this
method to send some jobs to a specific device pool in the media server pool, and send
other jobs to a different device pool in the same media server pool.
Media server pools can contain multiple managed media servers or just one managed
media server. A managed media server can belong to more than one media server pool.
The central administration server can be used as a managed media server and can be
included in the media server pool.
818 Administrator’s Guide

Appendix A, Symantec Backup Exec Central Admin Server Option
Grouping managed media servers in pools
Any managed media server or media server in a pool must be able to access the
destination device for the backup. If there is no intersection between the device and the
managed media server or media server pools, the job does not run. The Job Monitor
displays the following status: Ready; No media server available in media server pool.
An example of a CASO-configured media server pool inside a corporate network
Use a media server pool to do any of the following:
Advantages of a media server pool
Central
administration
server
To See
Apply settings to all of the managed
media servers in the pool
Restrict the backup jobs to a specific
set of managed media servers and
their attached storage devices
View or filter data to be displayed for
media servers in a pool, such as
alerts, statistics, or active jobs
Copy configuration settings and
logon information from a media
server to all media servers in a pool
Media server pool
“Applying settings to all managed media servers in a pool”
on page 825
“Restricting the backup of a selection list to specific
devices” on page 820
“Viewing active job and alert statistics for a media server
pool” on page 824
“Copying configuration settings” on page 156
819

Grouping managed media servers in pools
Restricting the backup of a selection list to specific devices
You can run a job on devices that are on a specific managed media server or on devices
that are in a group of managed media servers. This filter lets you control where certain
jobs are delegated. For example, to always run backups of Exchange databases only on
the devices that are attached to managed media servers in a pool named Exchange
Backups, you could select this option, and then select the Exchange Backups media
server pool.
To restrict the backup of a selection list to specific devices
1. Do either of the following:
■ Create a backup job by setting job properties by following the instructions in
“Creating a backup job by setting job properties” on page 349.
■ Create a backup selection list by following the instructions in “Creating selection
lists” on page 328.
2. On the Properties pane, under Destination, click Device and Media.
3. Check Restrict backup of the selection list to devices on the following media server
or media servers in a pool.
4. Select a media server or media server pool.
5. Continue setting job properties for the job.
Related Topics:
“Creating a media server pool” on page 820
“About job delegation in CASO” on page 818
“Grouping managed media servers in pools” on page 818
Creating a media server pool
To create a media server pool
1. On the central administration server’s navigation bar, click Media Servers.
2. On the task pane, under Media Server Pool Tasks, click New media server pool.
3. Enter a media server pool name and description.
820 Administrator’s Guide

4. Select the media servers you want to add to the pool.
5. Click OK.
Appendix A, Symantec Backup Exec Central Admin Server Option
Grouping managed media servers in pools
Related Topics:
“Grouping managed media servers in pools” on page 818
“Adding managed media servers to a media server pool” on page 821
“Removing a managed media server from a media server pool” on page 823
“Renaming a media server pool” on page 822
“Deleting a media server pool” on page 822
Adding managed media servers to a media server pool
To add managed media servers to a media server pool
1. On the central administration server’s navigation bar, click Media Servers.
2. Select a media server pool to which you want to add managed media servers.
3. On the task pane, under Media Server Pool Tasks, click Add Media Server.
4. Select the media servers you want to add to the pool.
5. Click OK.
The managed media server appears in the media server pool.
Related Topics:
“Renaming a media server pool” on page 822
“Creating a media server pool” on page 820
“Deleting a media server pool” on page 822
“Removing a managed media server from a media server pool” on page 823
821

Grouping managed media servers in pools
Renaming a media server pool
To rename a media server pool
1. On the central administration server’s navigation bar, click Media Servers.
2. Right-click the media server pool that you want to rename, and then click Rename.
3. When prompted, enter a new name for the media server pool.
4. Click OK.
The media server pool is renamed.
Related Topics:
“Adding managed media servers to a media server pool” on page 821
“Creating a media server pool” on page 820
“Removing a managed media server from a media server pool” on page 823
Deleting a media server pool
To delete a media server pool
1. On the central administration server’s navigation bar, click Media Servers.
2. Right-click the media server pool that you want to delete, and then click Delete.
3. When prompted to confirm the delete operation, click Yes.
The media server pool is deleted.
Related Topics:
“Adding managed media servers to a media server pool” on page 821
“Creating a media server pool” on page 820
“Removing a managed media server from a media server pool” on page 823
822 Administrator’s Guide

Appendix A, Symantec Backup Exec Central Admin Server Option
Grouping managed media servers in pools
Removing a managed media server from a media server pool
Removing a managed media server deletes it from a media server pool, but does not
remove it from the All Managed Media Servers node.
To remove a managed media server from a media server pool
1. On the central administration server’s navigation bar, click Media Servers.
2. Select a media server pool from which you want to remove a managed media server.
3. On the right pane, select the managed media server that you want to remove.
4. On the task pane, under Media Server Pool Tasks, click Remove Media Server.
5. Click OK.
The managed media server no longer appears in the media server pool.
Related Topics:
“Adding managed media servers to a media server pool” on page 821
“Creating a media server pool” on page 820
“Deleting a media server pool” on page 822
Viewing general properties for a media server pool
On the General tab of the media server pool properties, you can view the name,
description, and creation date of this media server pool.
To view general properties for a media server pool
1. On the central administration server’s navigation bar, click Media Servers.
2. Right-click the media server pool, and then click Properties.
3. Click the General tab.
The Media Server Pool Properties General tab provides the following information:
Name The name of the media server pool.
Description The description of the media server pool.
823

Grouping managed media servers in pools
Creation date The date and time that this media server pool was created.
4. Click OK.
Related Topics:
“Adding managed media servers to a media server pool” on page 821
“Creating a media server pool” on page 820
“Deleting a media server pool” on page 822
Viewing active job and alert statistics for a media server pool
On the Statistics tab of the media server pool properties, you can view the number of
devices, jobs, and alerts for this media server pool. You can also click links to
immediately view active jobs and alerts.
To view active job and alert statistics for a media server pool
1. On the central administration server’s navigation bar, click Media Servers.
2. Right-click the media server pool, and then click Properties.
3. Click the Statistics tab.
The Media Server Pool Properties Statistics tab provides the following information:
Number of devices Number of storage devices in this media server pool. When
multi-drive robotic libraries attached, each drive in the robotic
library represents a separate device.
Number of active jobs Number of jobs currently in progress in this media server pool.
View jobs... Click this to view all current jobs and job histories for this media
server pool.
The Job Monitor view on the navigation bar is displayed, and the
filters for current jobs and job histories are reset to display jobs for
this media server.
Number of error alerts Number of active error alerts for this media server.
Number of warning
alerts
Number of active warning alerts for this media server.
824 Administrator’s Guide

Number of
informational alerts
4. Click OK.
Appendix A, Symantec Backup Exec Central Admin Server Option
Grouping managed media servers in pools
Applying settings to all managed media servers in a pool
To apply settings to all managed media servers in a pool
Number of active information alerts for this media server.
View alerts... Click this to view all active alerts for this media server. The Alerts
view on the navigation bar is displayed, and the filter is reset to
display active alerts for this media server.
1. On the central administration server’s navigation bar, click Media Servers.
2. Select or create a media server pool that contains the managed media servers to
which you want to apply the settings.
3. Right-click the media server pool, and then click Properties.
4. Click the Settings tab, and then check Apply these settings to all of the managed
media servers in the pool.
5. Make any changes to the defaults.
For details about these settings, see the following:
For communication
settings, the job monitor
setting, or the time
difference setting
For thresholds for
unresponsive managed
media servers, or for how
often active job status
updates are sent by the
managed media server
For setting when job log
and job history details
are sent to the central
administration server
“Setting defaults for managed media servers” on page 805
“Setting communication thresholds and active job status updates”
on page 808
“Copying logs and histories to the central administration server”
on page 810
825

Copying jobs instead of delegating jobs
6. Choose any setting that you want to apply to all of the managed media servers in the
selected media server pool, and then click OK.
Copying jobs instead of delegating jobs
If the managed media server’s device and media data are kept on a local database on the
managed media server, the central administration server cannot delegate jobs to it.
Instead, you can copy policies, selection lists, and configuration settings from the
central administration server to the managed media server. A persistent network
connection to the central administration server is not needed when the jobs are run
locally on the managed media server.
If you associate the policies and selection lists on the central administration server, jobs
are created there. You can then copy the jobs to the managed media server. You can also
copy the policies and selections lists to the managed media server, and then associate
them. The jobs are created on the managed media server.
Use the same names for objects on the central administration server and all of the
managed media servers that you want to copy jobs to. For example, use the same name
for a device pool on the central administration server and on the managed media server.
Then, it is not necessary to customize settings or names for each managed media server
that you copy jobs to.
Related Topics:
“Copying configuration settings” on page 156.
“Copying jobs, selection lists, and policies” on page 440
“Setting defaults for managed media servers” on page 805
Requirements for duplicate backup data and synthetic backup
jobs in CASO
A recurring job from a policy that contains a Duplicate Backup Sets template or a
Synthetic Backup template must be run on the same managed media server where the
job was initially run. The jobs produced from these templates require access to the
media that contains the backup sets that were produced from the preceding jobs.
If you change the target device of the templates within a policy, the jobs resulting from
that template can then be delegated to a different managed media server. However, if
the destination managed media server is still a valid candidate for delegation, it will be
used.
826 Administrator’s Guide

Appendix A, Symantec Backup Exec Central Admin Server Option
How centralized restore works
If you do not change the destination devices in the templates, and if the targeted
managed media server is unavailable, the jobs remain queued, waiting for the targeted
managed media server to become available. If the targeted managed media server is no
longer configured as a managed media server, then you can re-delegate the jobs.
Related Topics:
“Policies and templates” on page 415
“Adding a duplicate backup template to a policy” on page 436
“Creating a synthetic backup by copying the example policy” on page 873
How centralized restore works
Depending on whether the required storage media resides in storage devices or is stored
offsite, initiating restore operations from the central administration server can be an
automated process with little user intervention necessary.
How centralized restore works with online media
You make restore selections and set job properties at the central administration server.
During the data selection process, CASO determines the media required to complete the
restore operation, and then queries the Backup Exec device and media database to
determine the identity of the storage device where the primary media required for the
job currently resides. After you make your selections, set restore job properties, and
launch the restore job, CASO begins the restore operation by delegating the jobs to the
central administration server or managed media servers that control the selected
storage devices. If the data being restored spans multiple storage media, you are
prompted to load additional media as needed to successfully complete the restore
operation.
How centralized restore works with offline media
You make restore selections and set job properties at the central administration server.
During the data selection process, CASO determines the media required to complete the
restore operation, and then queries the Backup Exec device and media database to
determine the identity of the storage device where the primary media required for the
job currently resides. If the media is not found in a storage device, the media is
considered offline. CASO then presents you with a selection of drive pools and storage
devices that are compatible with the type of media being used during the restore
operation, thus giving you the flexibility of choosing a storage device in which to load
your media. After noting the identity and location of the storage device you have
selected to run the job, you:
■ Submit the restore job on hold as a scheduled job
827

How centralized restore works
■ Retrieve the media, place it in the storage device
■ Remove the job from hold at the central administration server, at which time the
restore job begins.
CASO then delegates the job to the managed media server that controls the selected
storage device. If the data being restored spans multiple storage media, you are
prompted to load additional media as needed to successfully complete the restore
operation.
Before restore operations from the central administration server can be initiated, the
following requirements must be met:
■ Managed media server communication status must be Enabled.
■ Managed media servers must be online with all media server statuses showing
Online.
Related Topics:
“Managing media” on page 257
How CASO restores data that resides on multiple devices
If the data selected for restore is located on a single device attached to a managed media
server, then a single restore job is created at, and then delegated from, the central
administration server. However, if the data being selected for restore is located on
multiple devices in the CASO environment, then the single restore job is split into
separate restore jobs, depending on the number of devices involved.
All split restore jobs have the same name as the original job, but are differentiated and
linked with a subscript numeral that is appended to the job name.
For example, if you create a restore job and the data you select for restore resides in one
device on a managed media server, CASO creates one restore job. However, if you create
one restore job and the data you select resides on two or more devices that are attached
to a managed media server, CASO creates two or more restore jobs.
Example of subscript numerals linking split restore jobs
Single restore job
split into multiple
jobs, are visually
linked using a
subscript numeral
appended to the
original job name.
828 Administrator’s Guide

For data stored on a single storage device
1. Data selections
for restore are made
at the central
administration
server.
3. CASO creates one restore job,
which is delegated for processing at
the managed media server where the
data resides.
Appendix A, Symantec Backup Exec Central Admin Server Option
How centralized restore works
2. For data that
resides on one
storage device....
4. The job is
delegated and
processing begins.
829

How centralized restore works
For data stored on multiple storage devices
1. Data selections
for restore are made
at the central administration
server.
2. For data that resides on
multiple storage devices...
3. .CASO creates multiple restore
jobs, which are delegated for
processing to the managed media
servers where the data resides.
Best practices for centralized restore
Symantec recommends the following for best practices when using centralized restore:
■ Select only one resource to restore for each job.
■ Select the same restore device or media server for all of the selections that are in the
same restore job.
■ Select a media server that has compatible devices for all media that is required for
the restore job.
Related Topics:
“Restoring from the central administration server” on page 831
4.Jobs are
delegated
and processing
begins.
830 Administrator’s Guide

Restoring from the central administration server
Appendix A, Symantec Backup Exec Central Admin Server Option
How centralized restore works
Before you create a restore job, review “Best practices for centralized restore” on
page 830.
To restore from the central administration server
1. Follow the instructions for making restore selections in “Creating a restore selection
list” on page 510.
2. On the Restore Job Properties dialog box, in the task pane, under Source, click
Device and Media.
3. Enter or change information as appropriate:
Media or Resource Displays a list of media that is required for the restore, or the
name of the resource that you selected for restore.
Media Location Displays the location of the media. If the media is listed as offline
or unknown, you must retrieve the media, select a device in the
Restore Device or Media Server column, and then place the media
in a device that the managed media server can access.
If the data that is selected for restore resides in a media vault,
then Offline is displayed.
If the data that is selected for restore resides in an unknown
media location, then Unknown is displayed because the media
cannot be found in any of the compatible storage devices that are
candidates to run the job.
Restore Device or Media
Server
4. Set other restore job properties from the Properties pane. See “Restoring data by
setting job properties” on page 488.
5. Click Run Now to start the restore operation.
Related Topics:
“How centralized restore works” on page 827
Displays devices or media servers that are compatible with the
media being restored, and that are possible candidates to process
the restore job.
To support restoring from the central administration server when
the device and media database is on the managed media server, all
media servers, including the central administration server, are
listed in this column.
831

Administering managed media servers
Administering managed media servers
After CASO is installed, you can perform tasks on the managed media servers from the
Media Servers view on the central administration server. Managed media servers are
also displayed in the Job Monitor view, in Current Jobs and in Job History.
Information displayed in the Media Servers view is described in the following table.
Media Servers view
Item Description
Name Displays the name of the managed media server or central
administration server. Along with the name, an icon representing a
managed media server or central administration server is used to help
you quickly differentiate between the two.
See “Administering managed media servers” on page 832.
Description Displays a user-defined description of the managed media server or
the central administration server.
Communication Status Displays the status of communications between the managed media
server and the central administration server. Statuses include:
◆ Enabled - Communications about jobs between the managed media
server and the central administration server are working properly.
◆ Disabled - Communications between the managed media server
and the central administration server have been disabled by the
user.
◆ Stalled - Communications between the managed media server and
the central administration server have not occurred within the
configured time threshold.
See “What happens when communication thresholds are reached”
on page 810.
◆ No communication - No communication about jobs is being
received at the central administration server from the managed
media server. The configured time threshold has been reached.
Jobs sent to the managed media server are recovered. Possible
causes could range from a network failure to hardware failure in
either the managed media server or the central administration
server.
See “Recovering failed jobs in CASO” on page 835.
◆ N/A - This status appears when the computer displayed in the
Name column is a central administration server.
832 Administrator’s Guide

Media Servers view
Item Description
Appendix A, Symantec Backup Exec Central Admin Server Option
Administering managed media servers
Media Server Status Displays the present status of a managed media server. Valid statuses
include:
◆ Online - All managed media server services are running and
communication with the central administration server is
functioning as expected.
◆ Paused - The managed media server has been placed in a Paused
state by the user. Jobs are not delegated to the managed media
server when it is in a Paused state.
◆ Unavailable - A state where no communications have been
received by the central administration server from the managed
media server.
◆ Offline - All managed media server services have been stopped; the
media server cannot run jobs in an offline state.
Media Server Type Displays Backup Exec’s description of the media server. It can be
either a managed media server or a central administration server.
Monitor Jobs Created
Locally
Displays Yes if the option Monitor jobs that are created on the local
managed media server in addition to the jobs that are delegated
from the central administration server is enabled; otherwise, No is
displayed.
If this option is enabled, you can hold, delete, run, cancel, and change
the priority of jobs that were copied from the central administration
server.
See “Setting defaults for managed media servers” on page 805.
Catalog Location Displays the location of the catalog.
See “Changing the catalog location” on page 816.
Version Displays the version of Backup Exec for Windows Servers that is
installed and running on the media server.
Operating System Displays the type of operating system that is installed and running on
the media server.
Operating System Build Displays the build number of the operating system that is installed on
the media server.
833

Administering managed media servers
Icons are used in the Media Server view to help you quickly identify the operational
status of Backup Exec managed media servers that appear in the Results pane. These
icons include the following:
CASO icons
Icon Description
Managing jobs in CASO
Central administration server - This icon represents a Backup Exec
central administration server.
Paused central administration server - This icon represents a Backup
Exec central administration server that has been placed in a Paused
state.
Managed media server - This icon represents a Backup Exec media
server that has been converted to a Backup Exec CASO-configured
managed media server.
Paused managed media server - This icon represents a managed
media server that has been placed in a Paused state.
Disabled managed media server - This icon represents a disabled
managed media server.
No icon appears- A computer name that displays without an
associated icon is marked as Unknown.
To locate the server on which jobs were created, click the Job Setup or Job Monitor view
and scroll to the column labeled Created On. For each job, either Central
administration server or Managed media server is displayed.
If the option to monitor jobs that are created on the local managed media server is
enabled, you can hold, delete, run, cancel, and change the priority of jobs that were
copied from the central administration server. However, if you create jobs on the
managed media server by associating selection lists and policies, then you can only
delete those jobs from the managed media server on which the policy originated.
Related Topics:
“Deleting a job created from a policy” on page 434
834 Administrator’s Guide

“Copying jobs instead of delegating jobs” on page 826
“Setting defaults for managed media servers” on page 805
Recovering failed jobs in CASO
Appendix A, Symantec Backup Exec Central Admin Server Option
Administering managed media servers
The Backup Exec error-handling rule named Recovered Jobs is a custom error-handling
rule that is used by CASO to recover jobs that failed because of issues with internal job
communications. This rule is created when Backup Exec is installed and is enabled by
default.
The retry options for this rule are to retry the job twice, with an interval of five minutes
between the retry attempts. During the first retry attempt, CASO attempts to
re-delegate the jobs to another available managed media server.
If this attempt fails, CASO makes a second attempt at finding another available managed
media server to process the jobs. If no managed media servers are available, the final job
disposition is to place the job on hold until you have fixed the error condition.
Note If you target a job to a media server pool that contains multiple managed media
servers and a job failure occurs, the recovery process uses only the managed
media servers in the media server pool. Managed media servers that are not in the
media server pool are not used for job recovery.
A CASO job with a status of No Communication that is failed and then recovered by
Backup Exec is displayed in the Backup Exec job history view in gray, with a job status of
Recovered. A CASO job that failed due to errors in normal daily activities is displayed in
red text, the same as other failed jobs.
When you open the job history entry for a Recovered job, the reason for the failure is
listed as Job Errors, with an explanation of the type of internal communication error
that occurred. The job history entry also indicates that the job was recovered.
Note Job logs are not created for jobs that are recovered.
The following table describes the CASO error codes that are selected by default for the
Recovered Jobs custom error-handling rule:
Error codes for Recovered Jobs custom error-handling rule
Error code Description
0xE000881B
JOBDISPATCH
The displayed message is: Job failed while being
dispatched. The job will be recovered.
835

Administering managed media servers
Error codes for Recovered Jobs custom error-handling rule
Error code Description
0xE000881D
JOB_CASO_QUEUE
FAILURE
0xE000881E
JOB_CASO_REMOTEMM
S_STARTFAILURE
Related Topics:
“Error-handling rules” on page 474
“Custom error-handling rule for recovered jobs” on page 478
“Setting communication thresholds and active job status updates” on page 808
Pausing and resuming a managed media server
You can pause and resume a managed media server from the central administration
server.
Pausing a managed media server prevents the central administration server from
delegating jobs to it. When paused, the managed media server’s status changes from
Online to Paused, and is reflected as such in the Media Server Status column of the
Results pane.
Caution When installing Backup Exec options at a managed media server, the managed
media server must be paused, so that no further jobs are delegated to it from
the central administration server while the installation process occurs. If jobs
are running, let them finish or cancel them before beginning the installation.
To pause and resume a managed media server
The displayed message is: The job could not be delegated to
the destination managed media server. The managed
media server may not be online, or there may be a
communications failure. The job will be recovered.
The displayed message is: The job failed to start on the
destination managed media server, possibly because a
database error occurred. The job will be recovered.
1. On the central administration server, from the navigation bar, click Media Servers.
2. Select the managed media server you want to pause or resume.
3. From the task pane, under Media Server Tasks, click Paused.
The managed media server status changes from Online to Paused in the Media
Servers Status column, and an icon representing a managed media server in a
paused state appears.
836 Administrator’s Guide

Appendix A, Symantec Backup Exec Central Admin Server Option
Administering managed media servers
4. To resume job delegation to a managed media server, from the task pane, under
Media Server Tasks, click Paused.
The check mark appearing before the Pause selection is removed, and the managed
media server status changes from Paused to Online in the Media Servers Status
column. An icon representing a managed media server in an online state appears.
Related Topics:
“Setting communication thresholds and active job status updates” on page 808
“Administering managed media servers” on page 832
Displaying the actual state of a paused storage device
After pausing managed media server storage devices from the central administration
server, the storage devices appear in the Devices view with both a Paused Managed
Media Server status icon, and the word Paused.
However, when viewing the list of storage devices under the Devices view at the
managed media server, the storage devices that were paused at the central
administration server do not appear as Paused.
You must refresh the Devices view on the managed media server to view the actual state.
Press F5 at the managed media server to display the actual state of the storage devices.
Related Topics:
“Administering managed media servers” on page 832
“Managing devices” on page 167
Disabling and enabling communications
You can disable and enable managed media server communications from the central
administration server.
To disable and enable communications
1. On the central administration server, from the navigation bar, click Media Servers.
2. Select the managed media server that you want to disable or enable.
3. Do one of the following:
■ To disable communications, from the task pane, under Media Server Tasks,
click Communication Enabled.
837

Administering managed media servers
Communications are disabled between the managed media server and the
central administration server. The managed media server’s communications
status changes from Enabled to Disabled in the Communications Status column.
Its status change is also reflected in the Media Server Status column, which
changes from Online to Unavailable. An icon representing a disabled managed
media server appears.
■ To re-enable communications, from the task pane, under Media Server Tasks,
click Communication Enabled.
The managed media server’s communications status changes from Disabled to
Enabled in the Communications Status column. Its status change is also
reflected in the Media Server Status column, which changes from Unavailable to
Online. Finally, an icon representing a fully functioning managed media server
appears.
Related Topics:
“Administering managed media servers” on page 832
“Setting communication thresholds and active job status updates” on page 808
Stopping and starting Backup Exec services for CASO
You can stop and start the Backup Exec services on a managed media server from the
central administration server.
To stop or start Backup Exec services from the central administration server
1. On the central administration server, from the navigation bar, click Media Servers.
2. Select the managed media server on which you want to start or stop services.
3. From the task pane, under Media Server Tasks, click Backup Exec Services.
4. Select the appropriate options.
Server Type the name of a server you want to add to the list, and then click
Add. To import a list of servers, click Import List and select the file
containing the server list.
Start all services Click this to start all Backup Exec services for the selected server.
Stop all services Click this to stop all Backup Exec services for the selected server.
838 Administrator’s Guide

Connecting to a remote managed media server
Appendix A, Symantec Backup Exec Central Admin Server Option
Administering managed media servers
Restart all services Click this to stop all Backup Exec services and then restart the
services for the selected server.
Services credentials Click this to change service account information or to change
startup options.
Refresh Click this to refresh this dialog box.
Remove Server(s) Click this to remove a selected server or servers from the server
list.
To run administrative tasks on a managed media server from the central administration
server, connect to the managed media server using the Backup Exec feature, Connect to
Media Server.
To connect to a remote managed media server
1. Start Backup Exec on the central administration server.
2. From the navigation bar, click Media Servers.
3. Select the managed media server to which you want to connect.
4. From the task pane, under Media Server Tasks, click Connect to media server.
5. If the managed media server name does not appear, enter the computer name in the
Server field.
6. Enter administrator or administrator equivalent logon information for the managed
media server.
7. In the Domain field, enter the computer name of the managed media server.
8. Click OK.
Connection to the managed media server occurs.
After making a remote connection to a managed media server, the central
administration server console is closed and the managed media server console
becomes the active interface.
839

Disaster Recovery in CASO
9. To return to the central administration server console, close the managed media
server console and restart Backup Exec on the central administration server.
Viewing managed media server properties
You can view properties for managed media servers in the Media Servers view on the
central administration server.
To view managed media server properties
1. Start Backup Exec on the central administration server.
2. From the navigation bar, click Media Servers.
3. Select the managed media server for which you want to view properties.
4. On the task pane, under General Tasks, click Properties.
For information on data displayed on the property tabs, see the following table:
General “Viewing a media server’s general properties” on
page 189
System “Viewing a media server’s system properties” on
page 191
Statistics “Viewing a media server’s active job and alert
statistics” on page 192
License Information “Viewing a media server’s installed licenses” on
page 193
Settings “Setting defaults for managed media servers” on
page 805
Advanced “Changing the catalog location” on page 816
Disaster Recovery in CASO
Use the Symantec Backup Exec for Windows Servers - Intelligent Disaster Recovery (IDR)
option to protect both managed media servers and the central administration server in a
CASO environment.
840 Administrator’s Guide

Appendix A, Symantec Backup Exec Central Admin Server Option
Disaster Recovery in CASO
To protect the computers in your CASO environment, see “Symantec Backup Exec
Intelligent Disaster Recovery Option” on page 1501.
Before implementing the IDR option in a CASO environment, review the following:
■ In a CASO environment, all disaster preparation files (*.dr files) created for each
managed media server are centrally located on the central administration server.
■ To create recovery media for any managed media server or central administration
server, the IDR Preparation Wizard must be run at the central administration server.
Or if running on remote administration environment, connect to the central
administration server.
■ If you want managed media servers to be protected using a bootable tape image, you
must run the IDR Preparation Wizard at each of the managed media servers where a
bootable tape device is installed.
■ For CASO, two options appear on the Welcome screen when the IDR Preparation
Wizard is run on a managed media server. These options include:
■ Yes, create the bootable tape image now - For details on creating bootable tape
images, see “Creating a bootable tape image” on page 1514.
■ No, connect to a central administration server - If a bootable tape drive is not
detected on a managed media server, only this option appears.
■ A central administration server must be backed up and restored locally.
841

Disaster Recovery in CASO
842 Administrator’s Guide

Appendix
Symantec Backup Exec
Advanced Open File Option
B
The Symantec Backup Exec for Windows Servers Advanced Open File Option (AOFO) is
installed as a separate, add-on component of Backup Exec for Windows Servers.
The Advanced Open File Option uses advanced open file and image technologies
designed to alleviate issues that are sometimes encountered during backup operations,
such as protecting open files and managing shortened backup windows.
Related Topics:
“About the Advanced Open File Option” on page 843
“Supported snapshot technologies” on page 846
“Best practices for using the Symantec Volume Snapshot Provider” on page 856
About the Advanced Open File Option
When a job is submitted for backup with Advanced Open File selected, a snapshot of
each volume is created, providing a point-in-time record of the data. When creating a
snapshot, Backup Exec uses advanced snapshot technologies to momentarily suspend
write activity to a volume so that a snapshot of the volume can be created.
If the files selected for backup reside on more than one volume, by default Backup Exec
creates a snapshot for each volume that contains data to be backed up. For example, if
the data to be backed up resides on a single volume, a single snapshot is created. If data
resides on four volumes, four snapshots are created. After creating a snapshot, the data
is backed up from the snapshots, and then the snapshots are deleted.
843

About the Advanced Open File Option
During the backup, files can be open and data can be changed. Depending on the
snapshot provider that you are using, open files are handled using different methods.
For details on how the Symantec Volume Snapshot Provider handles open files during a
backup, see “Best practices for using the Symantec Volume Snapshot Provider” on
page 856.
Advanced Open File Option with Symantec Snapshot Provider
1
Start of backup job
During the backup,
data is changed
End of backup job
Backup Exec media
server
Volume C:
A B C
1 2 3
B B
i
Data A D C
Block 1 2 3
Snapshot
C:
Cache file for original data
The illustration represents the following:
1 - A backup begins for volume C on a Windows server using the Advanced Open File
Option.
844 Administrator’s Guide
2
Original Word file (open)
Data
Block
D
3
ii
iii
Changed file

Appendix B, Symantec Backup Exec Advanced Open File Option
About the Advanced Open File Option
2 - A snapshot is taken of volume C, that provides a point-in-time record of the data.
3 - After the snapshot is taken, the backup job starts and the data from volume C is
written to tape.
During the backup job, files can be opened, and data can change. The Advanced
Open File Option allows data to change by making a copy of the original data, named
a cache file. The snapshot tracks the data changes, as illustrated in the cache file
diagram.
For example, an open file such as a Microsoft Word document contains the data
A, B, and C in blocks 1, 2, and 3.
i - During the backup job, "B" changes to "D" in block 2.
ii - The original data in block 2 is copied to a cache file. In this case, "B" is the
original data.
iii - The changed file is now the most current file.
5 - When the snapshot comes to a changed block, it replaces these changed blocks
with the original data from the cache file before being sent to tape. The snapshot
then sends the point-in-time data to Backup Exec. The data is then written to tape.
When the backup is complete, the snapshot is deleted.
Symantec strongly recommends that Backup Exec database agents be used to back up
databases. Backup Exec database agents provide selective restores of data and more
integration with the database application while preventing backups of partial
transactions. Agents also enable backups on a database that is spread across multiple
disk volumes.
If the Advanced Open File Option is selected for a backup job on Microsoft SQL or
Microsoft Exchange Servers, all database files on these servers will automatically be
excluded from the backup. For Oracle Server, to avoid backing up the database files
twice, you should manually exclude any Oracle database files from backup jobs run with
AOFO selected.
You can use the Advanced Open File Option on the same volume as a database to provide
open file support for other applications. The Advanced Open File Option provides
generic protection for flat files when Backup Exec agents are not used, and provides
protection for Microsoft Outlook PST files.
The Advanced Open File Option is not available for use with Extensible Firmware
Interface (EFI) system partition backups.
Related Topics:
“Symantec Backup Exec Agent for Microsoft Exchange Server” on page 1219
“Symantec Backup Exec Agent for Microsoft SQL Server” on page 1335
845

About the Advanced Open File Option
“Symantec Backup Exec Agent for Oracle on Windows or Linux Servers” on page 1397
“Setting defaults for the Advanced Open File Option for backup jobs” on page 850
“Best practices for using the Symantec Volume Snapshot Provider” on page 856
Supported snapshot technologies
To use snapshot technologies with Backup Exec, you must install the Advanced Open
File Option. After making backup selections and choosing the Advanced Open File
Option, you can configure Backup Exec to use the snapshot technologies installed on
your computers.
Backup Exec supports the following snapshot technologies:
■ Symantec Volume Snapshot Provider (VSP).
Installing AOFO will install the Symantec Volume Snapshot Provider (VSP) only.
■ Veritas Storage Foundation by Symantec, formerly known as Veritas Volume
Manager (VM), FlashSnap Option.
■ Microsoft Volume Shadow Copy Service (VSS).
For Microsoft Volume Shadow Copy Service (VSS), you must be using the Windows
Server 2003 platforms.
Third party software vendors also provide additional components that work in
conjunction with the Microsoft Volume Shadow Copy Service. These components,
called Writers, are used to flush application data or file data (if a file is open)
residing in the computer’s memory before the Microsoft Volume Shadow Copy
Service makes a snapshot of the volume to be backed up. See your software
documentation for information about VSS Writers that may be provided by the
application software vendor.
Related Topics:
“Setting defaults for the Advanced Open File Option for backup jobs” on page 850
“Changing the default settings for the Symantec Volume Snapshot Provider” on
page 858
“Using Snap Start on a Veritas Storage Foundation volume” on page 855
“Best practices for using the Symantec Volume Snapshot Provider” on page 856
“Symantec Volume Snapshot Provider cache file location” on page 856
846 Administrator’s Guide

Appendix B, Symantec Backup Exec Advanced Open File Option
About the Advanced Open File Option
Requirements for using the Advanced Open File Option
The following requirements must be met to use the Advanced Open File Option with
snapshot technology. You must purchase the Advanced Open File Option for each
remote Windows computer that you want to back up.
The media server must have
■ Backup Exec for Windows Servers
■ If the Advanced Open File Option is to be used locally, then the media server must
also have:
■ Advanced Open File Option
The remote computer you want to back up with the Advanced Open File Option must
have
■ Windows 2000 or Windows Server 2003
■ Advanced Open File Option
■ Backup Exec Remote Agent for Window Servers (AOFO automatically installs the
Remote Agent)
The server you want to back up with the Advanced Open File Option must have
■ Enough free disk space on at least one volume to cache the data that changes during
the backup job. For more information, see “Adjusting the Symantec Volume Snapshot
Provider cache file size” on page 857.
■ An NTFS, FAT32, or FAT file system. At least one NTFS partition is required to use
Microsoft Volume Shadow Copy Service (VSS).
Note The Advanced Open File Option cannot be used on CD-ROM, floppy diskettes, or
removable media. Additionally, the Checkpoint Restart option is not supported by
the AOFO. For more information about Checkpoint Restart, see “Enabling or
disabling checkpoint restart” on page 711.
When backing up encrypted files with the Advanced Open File Option on Windows 2000
computers, a drive letter for the snapshot will display in Windows Explorer and on the
Backup Exec Administration Console. Do not attempt to access or back up this drive
letter. If no drive letters are available, encrypted files are backed up from the original
volume, and the job is logged as Complete with Exceptions.
To protect remote and local computers, the Backup Exec Remote Agent for Windows
Servers must be installed. The Remote Agent is installed by default on the media server.
847

Installing the Advanced Open File Option
For instructions on installing the Remote Agent to another Windows computer, see
“Installing the Remote Agent to an Itanium-based or x64-based operating system” on
page 104.
Related Topics:
“About the Advanced Open File Option” on page 843
“Setting defaults for the Advanced Open File Option for backup jobs” on page 850
“Changing the default settings for the Symantec Volume Snapshot Provider” on
page 858
“Using Snap Start on a Veritas Storage Foundation volume” on page 855
“Best practices for using the Symantec Volume Snapshot Provider” on page 856
“Symantec Volume Snapshot Provider cache file location” on page 856
Installing the Advanced Open File Option
The Advanced Open File Option is enabled from the media server by entering the AOFO
license key or keys. You must reboot the computer on which you are installing AOFO
after completing the installation.
Before installing AOFO to a remote computer, enable the remote registry service on the
remote computer. Make sure that the logon account used has permissions to modify
remote servers registries.
A 64-bit version of the Advanced Open File Option is also available, and can be installed
with the 64-bit Remote Agent for Windows Servers.
Caution Backup Exec for Windows Servers cannot use versions of the Advanced Open
File Option that are previous to version 9.0. It is recommended that you
uninstall versions previous to version 9.0. You must upgrade the Advanced
Open File Option by purchasing and re-installing it on the local media server
and on all remote computers on which it currently resides.
To install the Advanced Open File Option on a local media server, see “Installing Backup
Exec options to the local computer” on page 85.
To install the Advanced Open File Option on a remote media server, see “Installing
Backup Exec options to remote computers” on page 92.
To install the 64-bit Advanced Open File Option using the 64-bit installation program,
see “Installing the Remote Agent to an Itanium-based or x64-based operating system” on
page 104.
848 Administrator’s Guide

Appendix B, Symantec Backup Exec Advanced Open File Option
Installing the Advanced Open File Option
To install the 64-bit Advanced Open File Option using a command script, see “Using a
command script to install the Remote Agent and AOFO on an Itanium-based or
x64-based operating system” on page 107.
You can also install and uninstall the Advanced Open File Option on remote servers
using the Windows command line. See “Installing and uninstalling the Advanced Open
File Option to remote windows computers using the command line” on page 849.
Related Topics:
“Upgrading Backup Exec options on remote computers” on page 130
Installing and uninstalling the Advanced Open File Option to
remote windows computers using the command line
You can install the Advanced Open File Option (AOFO) using silent mode on a remote
computer using the Windows command line.
Silent mode runs the installation operation without the benefit of a user interface.
To use the command line to install the AOFO on a remote computer
1. Move to a remote server.
2. Map a drive letter to the Backup Exec for Windows Servers media server and change
directories to the Advanced Open file Option install directory using the following
path:
\Program Files\Symantec\Backup Exec\Agents\RAWS32
or copy the RAWS32 directory locally.
3. Open a command prompt and enter the drive letter you mapped in step 2.
4. To install AOFO without advertising enabled, run the following command:
setup.exe /AOFO: -s -boot
To install AOFO with advertising enabled, run the following command:
setup.exe /AOFO: -s /ADVRT:
The -s parameter is used to run the install operation in silent mode, without the
benefit of a user interface.
The parameter -boot is used to automatically reboot your computer. If you want
to do this, add the parameter -boot; if not, you must reboot the computer manually
at your convenience in order to activate the Advanced Open File Option.
849

Setting defaults for the Advanced Open File Option for backup jobs
5. The AOFO files are installed on the remote computer in the following directory:
\Program Files\Symantec\Backup Exec\RAWS
6. The AOFO installation log file is created in \Documents and Settings\All
Users\Application Data\Symantec\Backup Exec\Logs\bkupinst.log.
After the installation finishes, reboot the computer at your convenience in order to
activate the Advanced Open File Option.
Related Topics:
“Selecting data to back up” on page 315
Setting defaults for the Advanced Open File Option for backup
jobs
You can set the Advanced Open File Option defaults for each backup job, or you can set
defaults that are used for every backup job. Jobs saved before you installed the Advanced
Open File Option will continue to use the previous settings for backing up open files. In
order to use the Advanced Open File Option with these jobs, you must edit the job and
on the Advanced Open File dialog box in the backup job properties, select Use Advanced
Open File Option.
After a job is completed, check the section Backup Set Detail Information in the job log
to make sure that Advanced Open File was used during the backup.
850 Administrator’s Guide

To set the Advanced Open File defaults for backup jobs
1. Do one of the following:
To set Advanced Open
File backup options for a
single backup job
To set Advanced Open
File backup options for
all backup jobs
2. Select the appropriate options from the following:
Use Advanced Open File
Option
Automatically select
open file technology
Appendix B, Symantec Backup Exec Advanced Open File Option
Setting defaults for the Advanced Open File Option for backup jobs
On the navigation bar click the arrow next to Backup, and then click
New Backup Job. On the Properties pane, under Settings, click
Advanced Open File
On the Tools menu, click Options. On the Properties pane, under
Job Defaults, click Advanced Open File.
Select this check box to enable Advanced Open File for backup jobs.
If you are enabling this for a single job, or as a default for all
backup jobs, then Advanced Open File backup will be performed if
all requirements are met.
Enables Backup Exec to select the best snapshot method to use for
the type of data being backed up.
However, even if selected, a snapshot method may not be used if
the resources do not meet the requirements for using snapshot
methods. If the volume you select for backup does not meet the
requirements for using the Advanced Open File Option, then the
open file backup options (Never; If closed within 30 seconds; With a
lock; Without a lock) will apply. For more information on the open
file backup options, see Creating a Backup Job.
When the option Automatically select open file technology is
selected and Microsoft Volume Shadow Copy Service (VSS)
provider is selected, then the first available hardware, software, or
system provider is used to perform the snapshot for Microsoft
Volume Shadow Copy Service (VSS).
If you select this option for a Windows Server 2003 computer,
Microsoft Volume Shadow Copy Service (VSS) is used when
Shadow Copy Components and/or Microsoft SQL or Exchange
databases are selected for backup, but Symantec Volume Snapshot
Provider (VSP) is used in all other cases. If the Windows Server
2003 computer does not have VSP installed, Backup Exec uses VSS
as the default.
851

Setting defaults for the Advanced Open File Option for backup jobs
Symantec Volume
Snapshot Provider
Veritas Storage
Foundation for
Windows FlashSnap
Option
Symantec Volume Snapshot Provider (VSP) is the default snapshot
technology for Backup Exec. You can use the AOFO Wizard to help
you configure VSP for use with AOFO. For details on configuring
VSP and using the AOFO Wizard, see “Best practices for using the
Symantec Volume Snapshot Provider” on page 856.
Veritas Storage Foundation for Windows FlashSnap Option was
formerly known as Volume Manager (VM).
The volumes you want to back up with the Veritas Storage
Foundation for Windows FlashSnap Option must first be
snap-started using the Veritas Enterprise Administrator (VEA),
which must be purchased separately. For more information, see
“Using Snap Start on a Veritas Storage Foundation volume” on
page 855.
If the computer on which you are running a backup using the
Advanced Open File Option is in an environment with the Central
Admin Server Option and the Veritas Cluster Server installed, and
if failover occurs to a Veritas Cluster Service node, you must
manually clean up the snapshots before restarting the backup on
the failover node. Refer to the VSFW documentation for details.
When the Veritas Storage Foundation for Windows FlashSnap
Option is used for AOFO backups, the SnapBack of the volume is
done asynchronously since SnapBack can take a long time
(depending on the size of the volume snapped and the changes that
may have occurred during the backup). Rather than hold the job
completion for the length of the time this operation may take, the
job will instead Complete with Success (if no other error occurs).
Use the VERITAS Enterprise Administrator to verify that the
re-synchronization completed.
In rare cases, it is possible that the SnapBack fails and a broken
mirror results. If this occurs, the next FlashSnap job submitted for
the same volume may also fail, with the error Volume cannot be
snapped or Volume has not been Snap-started or is not a dynamic
volume. The job is logged as Completed with Exceptions. Use the
VERITAS Enterprise Administrator to verify why the SnapBack did
not complete and then correct the error.
852 Administrator’s Guide

Microsoft Volume
Shadow Copy Service
Appendix B, Symantec Backup Exec Advanced Open File Option
Setting defaults for the Advanced Open File Option for backup jobs
For use with vendor-specific, third party software, with Windows
Server 2003.
Microsoft Volume Shadow Copy Service (VSS) technology enables
third party hardware and software vendors to create snapshot
plugins for use with Microsoft’s technology.
Microsoft, as well as other third party software vendors, often
provide additional components that work in conjunction with VSS.
These components, called Writers, are used to flush application
data or file data (if a file is open) residing in the computer’s
memory before the Microsoft Volume Shadow Copy Service makes
a snapshot of the volume to be backed up.
See your software documentation for information about VSS
Writers that may be provided by the application software vendor.
Snapshot provider Automatic - Allow VSS to select the snapshot provider
Select this option to enable VSS to select the best provider for
the selected volume. The order in which a snapshot provider is
selected is hardware provider, software provider, and then the
system provider.
System - Use Microsoft Software Shadow Copy Provider
Software - Use Veritas Storage Foundation for Windows
Hardware - Use technology provided by hardware manufacturer
If you select Software or Hardware as the snapshot provider, then:
◆ If multiple volumes are selected, then all volumes must be
snappable by the same type of provider.
◆ Software and hardware providers cannot both be used to snap
different volumes in the same job. You must either create
another job, or select the option Process logical volumes for
backup one at a time.
853

Setting defaults for the Advanced Open File Option for backup jobs
Process logical volumes Enables the backup of multiple volumes in one job, while creating a
for backup one at a time snapshot of only one logical volume at a time. To ensure database
integrity, or if a volume contains mount points, multiple volumes
may need to be snapped at one time. A volume with mount points
to other volumes is considered a logical volume for snapshot
purposes. Therefore, that volume and the mount point volumes
will be snapped together simultaneously.
After the logical volume is snapped and backed up, the snapshot is
deleted before the next logical volume is snapped. This option
increases the ability to meet the minimum quiet time needed to
complete a snapshot.
A logical volume can comprise multiple physical volumes. A single
logical volume can encompass all of the volumes on which
databases reside.
If this option is not selected, then a snapshot for all volumes in the
backup job is created simultaneously. All volumes must meet the
minimum quiet time.
This option is only available for Symantec Volume Snapshot
Provider (VSP) and Microsoft Volume Shadow Copy Service (VSS)
jobs for logical volumes.
Note On computers running Windows Server 2003, if the selection
list for a backup job contains volumes as well as Shadow
Copy Components (SCC), and the options Automatically
select open file technology and Process logical volumes for
backup one at a time are selected, the snapshots for volumes
are created using VSP, and the Shadow Copy Components
snapshots are created using VSS. This is reported in the job
log and job history.
3. If you are configuring the Advanced Open File Option for a specific backup job, you
can start the backup job or select other backup options from the Properties pane.
To monitor the operation while it is processing, click Job Monitor on the navigation
bar, and then double-click the job to view the job activity.
4. If you are configuring the Advanced Open File Option as the default for all backup
jobs, click OK.
5. After the jobs have completed, check the job log to make sure the Advanced Open
File Option is being used during the backup.
Related Topics:
“Selecting data to back up” on page 315
“About selection lists” on page 327
854 Administrator’s Guide

Appendix B, Symantec Backup Exec Advanced Open File Option
Setting defaults for the Advanced Open File Option for backup jobs
“Creating a backup job by setting job properties” on page 349
“About the Advanced Open File Option” on page 843
“Best practices for using the Symantec Volume Snapshot Provider” on page 856
“Changing the default settings for the Symantec Volume Snapshot Provider” on
page 858
“Checking the job log when using the AOFO” on page 862
Using Snap Start on a Veritas Storage Foundation volume
To Snap Start a volume
1. Start Symantec Enterprise Administrator.
2. In the left pane, expand the Localhost object.
3. Under the Localhost object, expand the Volumes object, and then right-click the
volume to Snap Start.
4. On the short cut menu, select Snap, and then select Snap Start.
5. On the Snap Start Volume screen, select either Auto select disks or Manually select
disks.
Auto select disks enables Veritas Storage Foundation to make the disk selection for
you, while Manually select disks enables you to make the selection.
6. Click OK to begin the snap start of the volume.
Snap Starting a volume only needs to be done once. The Snap Start procedure can
take a considerable amount of time because it creates a mirror.
If you are backing up SQL or Exchange databases on the Snap started volume, you
must make your selections using the Backup Exec SQL or Exchange database agents.
Do not select a database or log at the volume level.
Related Topics:
“Selecting data to back up” on page 315
“Symantec Backup Exec Agent for Microsoft SQL Server” on page 1335
“Symantec Backup Exec Agent for Microsoft Exchange Server” on page 1219
855

Setting defaults for the Advanced Open File Option for backup jobs
Best practices for using the Symantec Volume Snapshot Provider
Following are recommended best practices for using AOFO and the Symantec Volume
Snapshot Provider (VSP):
■ Ideally, allow AOFO exclusive use of a disk. This disk should not have any user data,
should never be backed up, and should have the AOFO cache file location directed to
it.
■ Make sure there is sufficient space on the disk to encompass all of the changed data.
Changed data can include user files, system files, and the NTFS Master File Table
(MFT).
■ Exclude the cache file from real-time virus scanning software. Do not run regular
scans or disk utilities such as scan disk or defragmenters during backups with AOFO.
■ Avoid running any processes or programs that would write excessive data to the
drive being protected. Avoid copying large amounts of data to the drive being
protected.
■ Create backup-to-disk folders on a different physical disk than the disk you want to
back up. For example, if AOFO is used to snap volumes during a backup, and if the
destination device is a backup-to-disk folder, the backup-to-disk folder should be on
a separate volume that is not being snapped.
Related Topics:
“About the Advanced Open File Option” on page 843
“Requirements for using the Advanced Open File Option” on page 847
“Setting defaults for the Advanced Open File Option for backup jobs” on page 850
“Changing the default settings for the Symantec Volume Snapshot Provider” on
page 858
“Adjusting the Symantec Volume Snapshot Provider cache file size” on page 857
“Checking the job log when using the AOFO” on page 862.
Symantec Volume Snapshot Provider cache file location
When the Symantec Volume Snapshot Provider (VSP) and the Advanced Open File
Option (AOFO) are used, Backup Exec creates a cache file on the disk to save any changes
that are made to the files on the volume while it is being snapped. Backup Exec
automatically calculates the sizes of the cache files needed for the backup, as well as the
location of the cache files. The cache file is created in a hidden folder named Backup
Exec AOFO Store in the root of the selected volume. The cache file extension is .vsp.
856 Administrator’s Guide

Appendix B, Symantec Backup Exec Advanced Open File Option
Setting defaults for the Advanced Open File Option for backup jobs
Backup Exec locates the Symantec Volume Snapshot Provider (VSP) cache files based on
the following:
■ If you used the AOFO wizard to specify a location for the cache files, this location is
used if it is not write-protected, and if it is not part of the resources that are being
snapped.
If multiple source volumes (the volumes to be snapped) are being snapped, then
multiple cache files (one for each source volume) are located on the volume you
specified (if that volume is not being snapped).
■ If you have not specified a location for the cache file, Backup Exec will attempt to
locate the cache file on volumes other than the source volumes. These volumes
must meet the following requirements. If any of these criteria are not met, the cache
file is created on the source volume.
■ The volumes must be fixed drives.
■ The volumes must use a recognized file system (FAT, FAT32, or NTFS).
■ The volumes must be mounted locally.
■ The volumes must be valid cache file locations. A valid cache file location:
■ Cannot be a location for a snapshot by another job that is currently running.
■ Cannot contain another active cache file.
■ Cannot be write-protected or disabled.
Related Topics:
“About the Advanced Open File Option” on page 843
“Supported snapshot technologies” on page 846
“Setting defaults for the Advanced Open File Option for backup jobs” on page 850
“Checking the job log when using the AOFO” on page 862
Adjusting the Symantec Volume Snapshot Provider cache file
size
When using the Advanced Open File Option with the option, Automatically select open
file technology, Backup Exec chooses the Symantec Volume Snapshot Provider or the
Microsoft Volume Shadow Copy Service as the technology to use when open files are
encountered. Both of these providers use “Copy-on-Write” technology to create
snapshots. The snapshot itself consists of a virtual volume and a cache file. The cache
file keeps track of the changes to the volume being snapped after the snapshot is taken.
Using this technology, Backup Exec can back up data at a point-in-time, while also
ensuring data consistency.
857

Changing the default settings for the Symantec Volume Snapshot Provider
By default, Backup Exec determines the cache file location based on the amount of used
disk space on the volume to be snapped and the availability of free disk space on other
volumes.
The size of the cache file grows based on the amount of time the snapshot is active and
by the rate of data change occurring on the volume during the time the snapshot is
active. By default, Backup Exec sets a predetermined maximum cache file size, which in
cases of heavy disk write activity during a backup job, can be exceeded. In such cases,
the backup job will fail. If this occurs, you can increase the maximum size of the
Advanced Open File Option cache file using the Advanced Open File Option wizard, or by
running backup jobs during periods of low computer usage. In extreme cases, you may
have to allocate a maximum cache file size equal to the used space on the volume being
snapped.
Although rare, running out of disk space due to an insufficient cache size also can occur
when running a backup operation while simultaneously running virus scan or disk
defragmentation operations.
To change the cache file size, use the Advanced Open File Option wizard. For more
information, see “Changing the default settings for the Symantec Volume Snapshot
Provider” on page 858
Related Topics:
“Setting defaults for the Advanced Open File Option for backup jobs” on page 850
“Symantec Volume Snapshot Provider cache file location” on page 856
Changing the default settings for the Symantec Volume
Snapshot Provider
To change the default settings for the configuration options for the Symantec Volume
Snapshot Provider (VSP), use the Advanced Open File Option wizard on the Backup Exec
Administration Console or the AOFO Wizard button on the Advanced Open File dialog
box on the Backup Job Properties page.
Caution Use caution when you manually enter a specific size for the cache file since
that size is used regardless of the size of the volume being backed up, and the
job could fail if there is not enough space.
It is recommended that in most situations, you allow Backup Exec to automatically
calculate the size and location of the cache file for each backup.
858 Administrator’s Guide

Appendix B, Symantec Backup Exec Advanced Open File Option
Changing the default settings for the Symantec Volume Snapshot Provider
To change the Symantec VSP default settings using the AOFO wizard
1. On the Tools menu, select Wizards, and then click Advanced Open File Option
Wizard.
You can also use the AOFO Wizard button on the Advanced Open File Option dialog
box on the Backup Job Properties page.
2. Click Next to continue past the Welcome page.
3. Select a server that the Advanced Open File Option has been installed on, and enter a
user name and password.
Make sure the domain is correct. You can type another domain name, or click the
drop-down arrow to select another domain, and then click Next.
4. Do one of the following:
To use the default cache
file location
To specify alternate
locations for the cache
files
To change or delete
existing cache file
locations
Select Use default, and then click Next.
The default location for the cache file is on the volume that has
the most free space, and that is not selected to be snapped in this
Advanced Open File Option backup. However, if the volume that is
being snapped is the only volume with enough available space,
then the cache file is placed on it.
Symantec strongly recommends that you do not change the
defaults.
Clear the Use default check box. Type a drive and a path that are
located on the computer that is being backed up, or click the
browse button to browse to a local drive and path, click Insert,
and then click Next.
Select the location and then click Edit or Delete. After making
changes, click Next.
859

Changing the default settings for the Symantec Volume Snapshot Provider
5. On the Advanced Open File Option Configuration screen, enter new defaults using
the following table, and then click Next.
Have Backup Exec
calculates the initial and
maximum size of the cache
file
Initial size of the cache file
(1 - 100 percent):
Enables Backup Exec to automatically calculate the initial and
maximum size of the cache file for each backup.
If the cache file is located on the volume that is being snapped,
Backup Exec uses the following calculation:
For both the initial and maximum size, Backup Exec calculates
30 percent of the used space and 90 percent of the free space,
and then uses the smaller number.
If the cache file is located on a different volume than the volume
that is being snapped, Backup Exec uses the following
calculations:
The initial size is zero. For the maximum size, Backup Exec
calculates 30 percent of the free space on the target volume and
uses that figure.
The maximum size cannot be smaller than the initial size. If the
maximum size is calculated to be smaller than the initial size,
Backup Exec sets the maximum size to match the initial size.
Both the initial size and the maximum size must be at least 50
MB.
For information on where the cache file will be located, see
“Symantec Volume Snapshot Provider cache file location” on
page 856.
Sets the initial size of the cache file.
If you choose not to use the default, then type the percentage of
free space that you want the Advanced Open File Option (AOFO)
to use to create the cache file.
Increase this percentage if you receive an error message stating
that the AOFO is out of disk space. This increase enables
additional free space to be allocated on the volume, which can
then be used during the backup.
Symantec recommends that you set the maximum size before
setting the initial size.
860 Administrator’s Guide

Maximum size that the
cache file can grow to:
Number of seconds during
which there can be no disk
activity before the snapshot
is created
Appendix B, Symantec Backup Exec Advanced Open File Option
Changing the default settings for the Symantec Volume Snapshot Provider
Sets the maximum size of the cache file.
If you do not use the default, then type the maximum percentage
to allow for the cache file. If the snapshot exceeds the maximum
percentage, the job will fail and the error will be listed in the job
log.
If the cache file is located on the volume that is being snapped,
Backup Exec uses the number that you type in this field to
calculate the percentage of used space on the volume. Backup
Exec also calculates 90 percent of the free space on the volume
and uses the smaller number.
If the cache file is located on a different volume than the volume
that is being snapped, Backup Exec uses the number that you
type in this field to calculate the percentage of free space on the
volume and uses that number.
The maximum size cannot be smaller than the initial size. If the
maximum size is calculated to be smaller than the initial size,
Backup Exec sets the maximum size to match the initial size.
The maximum size must be at least 50 MB.
Sets the minimum length of quiet time in seconds, in which the
application waits for disk inactivity before the snapshot is
created.
During this time, AOFO is waiting for there to be no drive
activity to ensure that all buffers have been flushed, and
therefore all the data on the drive should be consistent. The
default quiet time is five seconds. In some cases it is necessary to
lower this setting, but this increases the risk of the data on the
drive becoming inconsistent. Decrease this setting if you have
an active disk so that the snapshot can be created before
reaching the maximum length of quiet time.
The recommended minimum length is five seconds, but you can
choose between two and four seconds. This setting should never
be lowered below two. Instead, investigate what applications or
services may be causing excessive disk writes.
You may also want to select the option Process logical volumes
for backup one at a time. This option enables the backup of
multiple volumes in one job, while creating a snapshot of only
one logical volume at a time and increases the ability to meet the
minimum quiet time needed to complete a snapshot. See
“Process logical volumes for backup one at a time” on page 854.
861

Checking the job log when using the AOFO
Number of seconds that the
application tries to obtain
the minimum quiet time,
after which the job fails
6. Review the summary screen. If the configuration is satisfactory, click Finish. To
make more changes, click Back.
7. To configure another server, click Set up another server to run the AOFO Wizard
again.
After you click Finish, the Advanced Open File Option settings for the Symantec
Volume Snapshot Provider are saved.
Related Topics:
“About the Advanced Open File Option” on page 843
“Setting defaults for the Advanced Open File Option for backup jobs” on page 850
“Best practices for using the Symantec Volume Snapshot Provider” on page 856
“Symantec Volume Snapshot Provider cache file location” on page 856
Checking the job log when using the AOFO
Sets the maximum length of time that AOFO waits for disk
inactivity before terminating the creation of the snapshot.
Increase this setting if a backup fails repeatedly with the
message that it could not obtain the minimum quiet time.
Increasing this setting maximizes the length of time used to
create the snapshot. The default is 2,000 seconds.
When a backup completes successfully while using the Advanced Open File Option
(AOFO), information is displayed in the job log. Check the section Backup Set Detail
Information in the job log to make sure that AOFO was used during the backup. If the
backup included more than one volume, this information is repeated for each volume.
If the AOFO fails on initialization, the backup still runs but the job is logged as
Completed with Exceptions in the job log.
If the AOFO fails during the backup of a device, that backup set is terminated and is
reported as an error.
Note Failed AOFO jobs using the Symantec Snapshot Provider (VSP) may leave an
active image on the computer, causing subsequent jobs to fail with an unknown
error. If this occurs, reboot the computer to clear the active image.
Related Topics:
“Setting defaults for the Advanced Open File Option for backup jobs” on page 850
862 Administrator’s Guide

Appendix B, Symantec Backup Exec Advanced Open File Option
Checking the job log when using the AOFO
“Best practices for using the Symantec Volume Snapshot Provider” on page 856
“Symantec Volume Snapshot Provider cache file location” on page 856
863

Checking the job log when using the AOFO
864 Administrator’s Guide

Appendix
Symantec Backup Exec
Advanced Disk-based Backup
Option
C
The Symantec Backup Exec for Windows Servers Advanced Disk-based Backup Option
(ADBO) is installed as a separate, add-on component of Backup Exec for Windows
Servers.
The Advanced Disk-based Backup Option provides the following features:
■ Synthetic backup. This feature uses a policy to enable a full backup to be assembled,
or synthesized, from a baseline and subsequent incremental backups that are also
contained in a policy. The benefits of using a synthetic backup include:
■ A reduced backup window since the synthetic backup can be scheduled outside
of the time-critical backup window.
■ Reduced network traffic since the synthetic backup does not need to access the
network.
■ True image restore. This feature enables Backup Exec to restore the contents of
directories to what they were at the time of any full or incremental backup.
Restore selections are made from a view of the directories as they existed at the time
of the particular backup. Files that were deleted before the time of the backup are
not restored. In true image restore, only the correct versions of files are restored
from the appropriate full or incremental backups that contain them. Previous
versions are not unnecessarily restored and then overwritten.
■ Offhost backup. This feature enables the backup operation to be processed on a
Backup Exec media server instead of on the remote computer, or host computer.
Moving the backup from the remote computer to a media server enables better
backup performance and frees the remote computer as well.
Related Topics:
About the synthetic backup feature on page 866
865

Installing the Advanced Disk-based Backup Option
About true image restore on page 880
About offhost backup on page 887
Installing the Advanced Disk-based Backup Option
ADBO is enabled on the media server when you enter the ADBO license key.
To install the ADBO on a local media server, see “Installing Backup Exec options to the
local computer” on page 85.
About the synthetic backup feature
The synthetic backup feature eliminates the need to perform recurring full backups for
supported remote resources. A policy created for the synthetic backup feature enables
the synthetic backup to be assembled from a full backup (called a baseline) and
subsequent incremental backups that are also contained in the policy.
The resulting synthetic backup then becomes the new baseline, so only incremental
backups are required until the next synthetic backup is created. The synthetic backup is
as current as the last incremental backup that it contains.
The components of the policy for synthetic backup are:
■ Baseline backup. The first backup to run that is associated with the synthetic
backup. The baseline backup runs one time only, and backs up all of the files on the
selected resources when it runs.
■ Recurring incremental backups. Subsequent backups that back up files that are
changed after the baseline backup.
■ Recurring synthetic backups. The process that combines the data from the baseline
backup and the incremental backups to form a synthesized full backup of the
selected resources. This synthesized full backup becomes a new baseline backup,
which can then be combined with subsequent incremental backup sets to form the
next synthesized full backup.
866 Administrator’s Guide

Baseline backup is run from the synthetic backup policy
Backup Exec
media server
Tape library
Incremental backups are run from the synthetic backup policy
Backup Exec
media server
Tape library
Network
Storage device
Network
Incremental
backups
Storage device
Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
About the synthetic backup feature
Resource selected for
backup from the media
server
Baseline backup
(can be backed up
to disk or tape)
Resource selected for
backup from the media
server
Baseline backup
(can be backed up
to disk or tape)
867

What you can back up with synthetic backup
Synthetic backup is run from the policy and assembled from the baseline and incremental backups
Network
Backup Exec
media server
Tape library
Synthetic
backup
Incremental
backups
Storage device
Synthetic backup can only be created within a policy. You can use the Policy Wizard to
create a policy that will contain the necessary job templates for the synthetic backup
feature, or you can copy the example policy for synthetic backup and then modify it to
suit your specific needs, or you can manually create a policy, and then add the necessary
job templates.
For all of the associated backup templates in a policy, you can also use a Duplicate
Backup Set template to create a multi-stage backup strategy for backing up data to disk
and then copying it to tape. For details, see“About duplicate backup set templates” on
page 435.
Related Topics:
Best practices for synthetic backup on page 870
Creating a synthetic backup on page 872
Collecting additional information for synthetic backup and true image restore on
page 871
What you can back up with synthetic backup
Resource selected for
backup from the media
server
Baseline backup
(can be backed up
to disk or tape)
Only file system resources are supported for synthetic backup.
Supported resources include common file system objects, such as volumes, drives,
folders, and System State. Do not include database resources or other unique resources
in the selection list.
Backup Exec will not create synthetic backup jobs when the selection list that is
associated with the synthetic backup policy contains unsupported resources.
868 Administrator’s Guide

Related Topics:
Requirements for synthetic backup on page 869
Creating a synthetic backup on page 872
Requirements for synthetic backup
Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
Requirements for synthetic backup
■ Synthetic backup and the associated templates can only be created in policies.
■ In a policy that contains a synthetic backup, if an encryption key is used, all of the
associated templates must use the same encryption key. The encryption key should
not be changed after the policy has been created. The encryption key that is selected
in the associated templates is automatically applied to the synthetic backup
template.
■ In a policy that contains a synthetic backup, backup templates that create
incremental backup jobs must have backup-to-disk folders as destination devices.
Before you can save a policy that contains the synthetic backup templates, you must
have a backup-to-disk folder that you can select as the destination device for the
required incremental backup jobs.
■ To display the example policy for synthetic backup, a backup-to-disk folder must
already exist or must be created, and the Advanced Disk-based Backup option must
be licensed. Click Tools>Re-create Example Policies to create an example policy for
synthetic backup.
See “Creating a synthetic backup by copying the example policy” on page 873.
■ The option Collect additional information for synthetic backup and for true image
restore must be selected for backup templates for incremental and full backup jobs
created for synthetic backup. This option is on the General page of the Backup Job
Template properties (for details, see “Creating a synthetic backup by adding
templates to a policy” on page 874). This option also enables true image restore for
backup sets (for details, see “About true image restore” on page 880).
■ If the baseline backup job was written to tape, and if you also want to write the
synthetic backup job to tape, two tape drives are required: one to mount the source
job on (the baseline backup) and one to mount the destination job on (the synthetic
backup job).
Following are limitations when running synthetic backup:
■ Only file system resources are supported for synthetic backup. See “What you can
back up with synthetic backup” on page 868.
869

Requirements for synthetic backup
■ If the Central Admin Server Option is installed, the synthetic backup job template
and any associated full and incremental job templates must be run on destination
devices that can all be accessed by the media server that runs the synthetic backup
job. For more information, see “Requirements for duplicate backup data and
synthetic backup jobs in CASO” on page 826.
■ The option Checkpoint Restart is not supported when the option Collect additional
information for synthetic backup and for true image restore is selected. For more
information on Checkpoint Restart, see “Using checkpoint restart on Microsoft
Cluster Server failover” on page 709.
Related Topics:
Collecting additional information for synthetic backup and true image restore on
page 871
Creating a synthetic backup by copying the example policy on page 873
“Creating a synthetic backup by adding templates to a policy”
Best practices for synthetic backup
■ A separate backup template for the baseline backup is optional. If you want the
destination device for the baseline backup to be different from that of the recurring
incremental backups, or if you want the baseline job to run at a different time than
the recurring incremental backups, you must create a separate backup template for
a full backup job to be the baseline backup.
■ Make sure that none of the synthetic backup-related job templates, that is, the
baseline backup template, the recurring incremental backup template, and the
synthetic backup template, are run at the same time. You can use template rules to
enforce when these templates are allowed to run. For more information, see “Setting
template rules” on page 428.
■ If a volume contains a lot of hard links or has SIS (Single Instance Storage) enabled,
you should not select the Use the Microsoft Change Journal if available option.
When the modification of these files is detected, Backup Exec reverts to performing
backups without using the Change Journal, and backups could require more time.
Related Topics:
“About the synthetic backup feature” on page 866
“Creating a synthetic backup by copying the example policy” on page 873
“Policies and templates” on page 415
870 Administrator’s Guide

Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
Requirements for synthetic backup
Collecting additional information for synthetic backup and true
image restore
All of the backup job templates that are created for synthetic backup and true image
restore must have the option Collect additional information for synthetic backup and
for true image restore selected. This option can be selected on the General page on the
backup job template properties when a policy is being created.
This option specifies that Backup Exec collects the information required to detect files
and directories that have been moved, renamed, or newly installed since the last backup,
and then includes those files and directories in the backup jobs. This option also lets
Backup Exec keep track of deleted files so that they are not included in true image
restore of the corresponding backup sets, and are not included in the backup sets
created by synthetic backup.
If this option is not selected, Backup Exec skips these files and directories if their
archive bits are unchanged. If this option is selected, Backup Exec compares path names,
file names, modified times, and other attributes with those from the previous full and
incremental backups. If any of these attributes are new or changed, then the file or
directory is backed up.
For synthetic backup, the first backup that is associated with the synthetic backup
always backs up all of the files, even if it is an incremental backup. Backup Exec starts
collecting the additional information with this first backup, but does not compare it to
any previous backup.
Note For synthetic backup, any job templates using the incremental backup method
and the Collect additional information for synthetic backup and for true image
restore option must use a backup-to-disk folder as the destination device.
This is not a requirement for backup job templates for true image restore.
Related Topics:
About the synthetic backup feature on page 866
Creating a synthetic backup on page 872
Adding a backup template to a policy on page 421
About true image restore on page 880
871

Creating a synthetic backup
Creating a synthetic backup
A synthetic backup can only be created in a policy. There are different methods you can
use to create a policy that contains the necessary job templates for a synthetic backup:
■ Use the Policy Wizard. See “Creating a synthetic backup by using the Policy Wizard”
on page 872.
■ Make a copy of the synthetic backup policy example and then modify the job
templates to suit your specific needs. See “Creating a synthetic backup by copying
the example policy” on page 873.
■ Manually create a policy, and then add the necessary job templates for the synthetic
backup feature. See “Creating a synthetic backup by adding templates to a policy” on
page 874.
Before creating a synthetic backup, review the requirements in “Requirements for
synthetic backup” on page 869.
Related Topics:
About the synthetic backup feature on page 866
Best practices for synthetic backup on page 870
Creating a synthetic backup by using the Policy Wizard
You can use the policy wizard to help you create all of the templates necessary for a
synthetic backup. You can set up the policy to use:
■ A weekly synthetic backup with daily incremental backups.
■ A monthly synthetic backup with a weekly synthetic or incremental backup and
daily incremental backups.
To create a synthetic backup by using the Policy Wizard
1. On the navigation bar, click Job Setup.
2. In the task pane, under Policy Tasks, click New policy using wizard.
3. On the Welcome page, click Next to continue, and follow the instructions in the
wizard to complete the policy.
All of the necessary job templates for synthetic backup will be created in the new
policy.
872 Administrator’s Guide

Related Topics:
About the synthetic backup feature on page 866
What you can back up with synthetic backup on page 868
Requirements for synthetic backup on page 869
Best practices for synthetic backup on page 870
Creating a synthetic backup by copying the example policy on page 873
Creating a synthetic backup by adding templates to a policy on page 874
Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
Creating a synthetic backup
Creating a synthetic backup by copying the example policy
Backup Exec provides example policies that contain standard settings for different
tasks. The example policy for synthetic backup contains the standard settings and job
templates that are required to run a synthetic backup. You can copy this example policy,
rename it, and change the times when the templates are scheduled to run. For
instructions on how to copy an example policy, follow the steps in “Using an example
policy” on page 419.
Note In order for the example policy for a synthetic backup to be displayed, you must
configure a backup-to-disk folder, and then on the Tools menu, click Re-create
Example Policies. The example policy for synthetic backup will be displayed in
the Policies pane in the Job Setup view. The backup template that creates the
incremental backup must have a backup-to-disk folder as the destination device.
To view the synthetic backup policy example, on the navigation bar, click Job Setup. In
the Policies pane, double-click Example: Synthetic Backup.
The example policy for synthetic backup contains the following templates:
■ Baseline Backup - the backup template that creates the baseline backup job. This job
only needs to run once. You can run additional baseline backups whenever you
prefer, although the backup window is reduced by running a synthetic backup
instead of a full backup.
■ Incremental Backup - the backup template that creates the subsequent incremental
backup jobs and runs after the baseline backup job runs.
■ Synthetic Backup - the backup template that creates the synthetic backup job.
The example policy displays the template rules that you can use to set the order in which
the templates should run. All template rules are optional, but they can help you make
sure that the templates run in the proper sequence.
873

Creating a synthetic backup
In the example policy, because a full backup template is included to act as the baseline, it
should be the first template to run, and it only needs to run once. Therefore, the
following rules were added:
■ must complete at least once before any other templates will be
allowed to start. Baseline Backup is selected as the .
■ If start times conflict, will start and upon completion, starts
. Incremental Backup is selected as the and
Synthetic Backup is selected as the .
■ Run only once. Baseline Backup is selected as the .
Related Topics:
What you can back up with synthetic backup on page 868
Requirements for synthetic backup on page 869
Setting template rules on page 428
About the synthetic backup feature on page 866
Best practices for synthetic backup on page 870
Creating a synthetic backup by adding templates to a policy
Creating a new policy for a synthetic backup involves choosing a name and description
for the policy, adding the necessary job templates for synthetic backup to the policy, and
setting up relationships between the templates. After you set up all of the templates for
a synthetic backup in a policy, you can combine the policy with a selection list to create
jobs.
Before creating a synthetic backup, review “Requirements for synthetic backup” on
page 869 and “What you can back up with synthetic backup” on page 868.
To create a synthetic backup by adding templates to a policy
1. On the navigation bar, click Job Setup.
2. On the task pane, under Policy Tasks, click New policy.
3. Type a policy name and description for this synthetic backup policy, and then click
New template.
The Template Selection dialog box appears.
4. Select Backup Template, and then click OK.
874 Administrator’s Guide

Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
Creating a synthetic backup
5. On the Properties pane, under Settings, click General, and specify either of the
following backup methods for the baseline.
■ Select Full - Back up files - Using archive bit (reset archive bit) to add an
optional baseline full backup template.
■ Select Incremental - Back up changed files since last full or incremental -
Using archive bit (reset archive bit) to add a recurring, incremental backup
template.
6. Select the Collect additional information for synthetic backup and for true image
restore option.
7. (Optional) Select the Use the Microsoft Change Journal if available option. For
details see “Using the Windows NTFS Change Journal to determine changed files” on
page 314.
Note If you selected an incremental backup method, then under Destination, click
Device and Media and select a backup-to-disk folder as the destination device.
8. On the Properties pane, under Settings, click Network and Security. For more
information about setting and managing encryption keys, see “Encryption keys” on
page 407.
In a policy that contains a synthetic backup, if an encryption key is used, all of the
associated templates must use the same encryption key. The encryption key should
not be changed after the policy has been created. The encryption key that is selected
in the associated templates is automatically applied to the synthetic backup
template.
If the Central Admin Server Option (CASO) is installed, an option displays to allow
managed media servers to use any network interface to access remote agents. For
more information, see “Enabling managed media servers to use any available
network interface card” on page 814.
9. Under Frequency, click Schedule and set the scheduling options you want to use
(for details, see “Setting the schedule for a template” on page 423).
If you added the optional full backup template for the baseline backup in step 5, you
must configure it to be the first backup template to run. The baseline backup only
needs to run once. You can run additional baseline backups whenever you prefer,
although the backup window is reduced by running a synthetic backup instead of a
full backup.
If you added an incremental backup template, you must configure it to be a
recurring job so that the first instance can become the baseline backup.
875

Creating a synthetic backup
10. Select other options as appropriate, and then click OK.
For details on these options, see “Adding a backup template to a policy” on page 421.
Note In a policy that contains a synthetic backup, backup templates that create
incremental backup jobs must have backup-to-disk folders as destination devices.
11. Do one of the following:
■ If you added the optional full backup template for the baseline backup in step 5,
then continue with the next step to create a backup template for an incremental
backup job.
■ If you added a recurring incremental backup template, go to step 18 on page 876
to add the synthetic backup template
12. On the New Policy dialog box, click New template, and then on the Template
Selection dialog box, select Backup Template again, and then click OK.
13. On the Properties pane, under Settings, click General, and select the backup
method Incremental - Back up changed files since last full or incremental - Using
archive bit (reset archive bit).
14. Select the Collect additional information for synthetic backup and for true image
restore option.
15. (Optional) Select the option Use the Microsoft Change Journal if available. For
details see “Using the Windows NTFS Change Journal to determine changed files” on
page 314.
16. Under Frequency, click Schedule and set the scheduling options you want to use
(for details, see “Setting the schedule for a template” on page 423).
17. Select other options as appropriate, and then click OK.
For details on these options, see “Adding a backup template to a policy” on page 421.
Note In a policy that contains a synthetic backup, backup templates that create
incremental backup jobs must have backup-to-disk folders as destination devices.
18. On the New Policy dialog box, click New template, select Synthetic Backup
Template, and then click OK.
19. On the Properties pane, under Destination, select Device and Media, and complete
the options as described in “Device and media options for backup jobs and
templates” on page 354.
876 Administrator’s Guide

Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
Creating a synthetic backup
20. On the Properties pane, under Settings, click General, and complete the
appropriate options as follows:
Template name Type the name for this job template.
Backup set description Type a description of the information you are backing up.
Preferred source device Select the device used as the destination device for the original
backup job.
21. On the Properties pane, under Settings, click Advanced, and complete the
appropriate options as follows:
Verify after job
completes
Select this option to have Backup Exec automatically perform a
verify operation to make sure the media can be read after the
backup has been completed. Verifying all backups is
recommended.
Compression type Select one of the following:
◆ None. Select this option to copy the data to the media in its
original form. If the data was backed up using software
compression, then it is copied in its software compression
form. Using some form of data compression can help expedite
backups and preserve storage media space.
Hardware data compression should not be used in
environments where devices that support hardware
compression are used interchangeably with devices that do
not have that functionality.
For example, if a drive that does not support hardware
compression is added to a cascaded drive pool that includes
drives supporting the feature, hardware compression is
automatically disabled. You can manually re-enable hardware
compression on the drives that support it, but this results in
media inconsistency. If the drive that supports hardware
compression fails, the compressed media cannot be restored
with the non-compression drive
◆ Hardware [if available, otherwise none]. Select this option to
use hardware data compression (if the storage device supports
it). If the drive does not feature data compression, the data is
backed up uncompressed.
877

Creating a synthetic backup
22. If you want Backup Exec to notify someone when the backup job completes, on the
Properties pane, under Settings, click Notification (see “Assigning notification
recipients for completed jobs” on page 565).
23. Do one or both of the following
■ Under Frequency, click Schedule to set the scheduling options you want to use
(for details, see “Setting the schedule for a template” on page 423).
■ Create template rules, explained in step 1 in the following procedure
“(Recommended) Create template rules to run job templates for synthetic
backup” on page 878.
(Recommended) Create template rules to run job templates for synthetic backup
Note You may want to review the topic “Setting template rules” on page 428 before
creating template rules.
1. On the New Policy dialog box, under Template rules, click New Rule.
2. On the Template Rule Properties dialog box, click the template rules drop down list,
and then do one of the following:
■ If you created a backup template for a full backup job to run as the baseline
backup, select Run only once. Click the First template drop
down list and select the name of the template that you want to run as the
baseline backup, and then click OK.
■ If you created a backup template for a recurring incremental backup job to run
as the baseline backup, go to step 4.
3. Click New Rule again to add another rule.
4. On the Template Rule Properties dialog box, click the template rules drop down list,
and then select must complete at least once before any other
templates will be allowed to start.
5. Click the First template drop down list, select the template name of the baseline
backup, and then click OK.
6. Click New Rule again to add another rule.
7. On the Template Rule Properties dialog box, click the template rules drop down list,
and then select If start times conflict, will start and upon
completion, starts .
878 Administrator’s Guide

Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
Creating a synthetic backup
8. Click the First template drop down list, and select the template name of the
incremental backup.
9. Click the Second template drop down list, select the template name of the synthetic
backup, and then click OK.
10. On the New Policy dialog box, click OK.
The policy is displayed on the Job Setup view, in the Policies pane.
After you create a policy and set up templates in it, you should combine the policy
with a selection list to create jobs. When a policy is combined with a selection list,
Backup Exec creates jobs based on the settings in the templates.
For details on how to create jobs using this policy, see “Creating jobs using policies”
on page 432.
Related Topics:
About the synthetic backup feature on page 866
What you can back up with synthetic backup on page 868
Requirements for synthetic backup on page 869
Best practices for synthetic backup on page 870
879

About true image restore
About true image restore
True image restore enables Backup Exec to restore the contents of directories to what
they were at the time of any full or incremental backup. Restore selections are made
from a view of the directories as they existed at the time of the particular backup. Files
that were deleted before the time of the backup are not restored. In true image restore,
only the correct versions of files are restored from the appropriate full or incremental
backups that contain them. Previous versions are not unnecessarily restored and then
overwritten.
When restoring from backup sets that were created by jobs in a true image restore
policy, you do not have to manually select from the previous full backup, and then select
the incremental backups one after another. The files that you need are automatically
selected from the appropriate backups.
Backup Exec starts collecting the true image restore information beginning with the
next full or incremental backup run by the policy after the option is enabled. The true
image restore information is collected regardless of whether any files were actually
changed.
For true image restore, Backup Exec also collects the information required to detect files
and directories that have been moved, renamed, or newly installed from a tar or zip
archive. Those files and directories are included in true image restore incremental
backups for this policy. Depending on how the files were packaged and how they were
installed, some newly installed files are not backed up by normal incremental backups.
With true image restore enabled, Backup Exec compares path names with path names
from the previous full or incremental backup. If a name is new or changed, the file or
directory is backed up. The following are examples where using true image restore backs
up files that would not otherwise be backed up:
■ A file named C:\pub\doc is moved to or installed in C:\spec\doc. Here, the archive bit
of files and subdirectories inside that directory is unchanged but C:\pub\doc is new
in the C:\spec\ directory and is backed up.
■ A directory named C:\security\dev\ is renamed as C:\security\devices\. Here, the
archive bit of files and subdirectories inside that directory is unchanged but
C:\security\devices\ is a new directory and is backed up.
880 Administrator’s Guide

Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
About true image restore
The following table lists the files backed up in the C:\user\doc directory during a series
of backups between December 1, 2006 and December 4, 2006. The Collect additional
information for synthetic backup and for true image restore option was selected for
the templates in the policy that created the backup jobs.
Example table of files backed up because true image restore is enabled
Day Type of
Backup
December 1,
2006
December 2,
2006
December 3,
2006
December 4,
2006
Files Backed Up in C:\user\doc
Full file1 file2 dirA\fileA dirB\fileB file3
Incremental file1 file2 dirA\fileA ---------------- ----------------
Incremental file1 file2 dirA\fileA ---------------- ----------------
Incremental file1 file2 ----------------
-
----------------
-
----------------
-
Note: Dashes (-----------------) indicate that the file was deleted prior to this backup.
Assume that you are going to restore the December 4, 2006 version of the C:\user\doc
directory.
■ If you perform a regular restore of the full backup set followed by a regular restore
of subsequent incremental backup sets, the restored directory contains all files and
directories that ever existed in C:\user\doc from December 1, 2006 (last full backup)
through December 4, 2006:
file1
file2
dirA\fileA
dirB\fileB
file3
file4
■ If you perform a true image restore of the December 4, 2006 backup, the restored
directory has only the files and directories that existed at the time of the
incremental backup on December 4, 2006:
file4
881

About true image restore
file1
file2
file4
Backup Exec does not restore any of the files that were deleted prior to the
December 4, 2006 incremental backup.
The restored directory does not include the dirA subdirectories, even though they
were backed up on December 4, 2006. Backup Exec does not restore these directories
because they did not exist at the time of the incremental backup, which was the
reference for the true image restore.
A true image restore preserves files that are currently in the directory but were not
present when the backup was completed. Assume you created a file named file5
after the incremental backup occurred on December 4, 2006, but before doing the
restore. In this case, the directory contains the following files after the restore:
file1
file2
file4
file5
Related Topics:
Collecting additional information for synthetic backup and true image restore on
page 871
Best practices for true image restore on page 883
True image catalogs on page 885
Creating a policy for true image restore on page 883
Restoring a backup set enabled for true image restore on page 885
Troubleshooting tips for true image restore on page 887
Requirements for running true image restore
■ Backup Exec version 11d must be installed on the media server.
■ The Backup Exec Remote Agent version 11d for Windows Systems must be installed
on any remote computers that you want to back up.
■ The Advanced Disk-based Backup Option (ADBO) must be installed on the media
server.
882 Administrator’s Guide

Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
Creating a policy for true image restore
■ The backup sets must be created by a policy that contains full and incremental job
templates in which the option Collect additional information for synthetic backup
and for true image restore is enabled.
True image restore supports the following resource types:
■ Windows and Unix file system backups.
■ Windows system state and EFI partition backups.
Related Topics:
Collecting additional information for synthetic backup and true image restore on
page 871
True image catalogs on page 885
Restoring a backup set enabled for true image restore on page 885
Troubleshooting tips for true image restore on page 887
Best practices for true image restore
■ If a volume contains many hard links or has SIS (Single Instance Storage) enabled,
you should not select the Use the Microsoft Change Journal if available option.
When the modification of these files is detected, Backup Exec reverts to performing
backups without using the Change Journal, and backups could require more time.
■ You should avoid creating many incremental backups between full backups.
Symantec recommends that you run weekly full backups.
Related Topics:
About true image restore on page 880
Troubleshooting tips for true image restore on page 887
Creating a policy for true image restore
Before you can perform a true image restore, you must:
■ Set up a policy that includes templates for weekly or monthly full and daily
incremental backups.
■ Select the Collect additional information for synthetic backup and for true image
restore option in each template.
883

Creating a policy for true image restore by using the Policy Wizard
Symantec recommends that you set up a policy with a minimum of a weekly full backup
and a daily incremental backup. You can add other templates as needed. Review “Best
practices for true image restore” on page 883.
For instructions on how to create a policy and templates, see “Creating a new policy” on
page 416. You can also use the Policy Wizard to create a policy for true image restore. See
“Creating a policy for true image restore by using the Policy Wizard” on page 884.
When the Central Admin Server Option (CASO) is installed, Backup Exec ensures that
full and incremental backups that have the Collect additional information for
synthetic backup and for true image restore option enabled are sent to a device that is
accessible by the same media server. If it is not possible to send the full and incremental
backups to devices that are accessible by the same media server, the policy cannot be
created. You are prompted to change the policy and resubmit it. Additionally, a true
image restore operation is delegated to the media server that has access to the device
that contains the selected backup set.
Related Topics:
Collecting additional information for synthetic backup and true image restore on
page 871
About true image restore on page 880
Requirements for running true image restore on page 882
Restoring a backup set enabled for true image restore on page 885
Troubleshooting tips for true image restore on page 887
Creating a policy for true image restore by using the Policy
Wizard
You can use the Policy Wizard to help you create all of the templates necessary to enable
backup sets for true image restore. Before you create templates, review “Best practices
for true image restore” on page 883.
To create a policy for true image restore by using the Policy Wizard, see “To create a
policy using the Policy Wizard” on page 417.
Related Topics:
About true image restore on page 880
Requirements for running true image restore on page 882
Restoring a backup set enabled for true image restore on page 885
Troubleshooting tips for true image restore on page 887
884 Administrator’s Guide

True image catalogs
Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
True image catalogs
Catalogs contain information about objects that were backed up during a backup job and
that are contained in the backup set created from that job. True image catalogs for
incremental backups contain additional information about all selected files and
directories that were on the volume at the time of the backup job and about the latest
backed-up versions of those objects. This additional information creates a true image of
the entire volume as of the time of the backup job, even though the incremental backup
job backed up only the changed files. In addition, true image catalogs track deleted files,
so files that were deleted before the time of the incremental backup are not restored.
Caution If you delete a true image catalog, you can no longer perform true image
restore for the backup sets contained in that catalog.
Related Topics:
Collecting additional information for synthetic backup and true image restore on
page 871
About true image restore on page 880
Troubleshooting tips for true image restore on page 887
Restoring a backup set enabled for true image restore
When backups are enabled for true image restore, you can choose restore selections
from a view of the volume as it existed at the time of the selected backup.
You can view or choose true image backup sets by clicking Restore on the navigation
tab. True image restore selections are only displayed on the View by Resource tab. True
image restore selections cannot display on the View by Media tab.
If you select true image backup sets in View by Resource, and then click the View by
Media tab, you are prompted to cancel all of the selections first. If you then select one of
the same backup sets on the View by Media tab, the set is restored without true image
functionality even though it is a true image backup set.
You can also enable true image restore on a duplicate copy of a backup set, which
provides support for multi-stage backup, or backup staging. For example, the first stage
of a backup that is enabled for true image restore is written to disk, and is then later
copied to tape. If the backup set on the disk becomes unavailable, you can use the true
image restore selections on the tape. Backup Exec automatically selects the most
suitable duplicate backup sets that are available. The most suitable backup sets of the
duplicate backup sets that are available, using the following order of preference:
■ A backup set in a backup-to-disk folder.
885

Restoring a backup set enabled for true image restore
■ A backup set that is on a tape already in a drive, or in a slot of a robotic library.
■ Any other known duplicate copy.
Note Only backup sets created by Backup Exec version 11d installations are supported
for true image restore. When a previous version of the Remote Agent is used, you
can still select backup sets to be restored from a true image view, but the restore
operation performs traditional restores of backup sets. The restore operation
starts from the prior full backup and processes incremental backups forward to
the selected backup set. Deleted and renamed files are also restored. A message in
the job log informs you that true image restore was not performed, but that all
appropriate backup sets were automatically selected.
A unique icon represents the true image backup sets. Each true image backup set shows
the entire selection list as it appeared on disk when the backup ran. Different icons
distinguish between the objects backed up in the viewed backup job and objects backed
up in previous backups.
True image restore icons
True image
icon for
backup sets
Related Topics:
About true image restore on page 880
Requirements for running true image restore on page 882
Creating a policy for true image restore on page 883
True image catalogs on page 885
About duplicate backup set templates on page 435
Icon indicates
that the file
is in a prior
image
886 Administrator’s Guide

Troubleshooting tips for true image restore
Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
About offhost backup
Errors that can occur in regular restore jobs can also occur in true image restore jobs. If
you cannot restore using true image backup sets, try restoring from individual backup
sets in the View by Media tab.
Troubleshooting tips for true image restore operations
Problem Explanation
The job fails with the error “Error
retrieving catalog information.”
You cannot expand the View by
Resource restore selections to display
the true image restore selections.
Related Topics:
About true image restore on page 880
Requirements for running true image restore on page 882
True image catalogs on page 885
About offhost backup
Most likely, one or more prior catalogs are not present.
If the catalog of the selected set is present but some prior
catalogs are not present, check the job log to find this
specific catalog error.
If any prior catalogs are missing, the restore view cannot
be expanded.
Offhost backup enables Backup Exec to move backup processing from the host
computer, which is the remote computer that contains the volumes selected for backup,
to the Backup Exec media server. The offhost backup creates a snapshot of the volume
or volumes that are selected for backup on the remote computer. The snapshots are then
imported to the media server, where they are backed up.
The following illustrates the basic method for performing an offhost backup.
887

About offhost backup
Offhost Backup
Attached SAN
device
Remote computer
After the backup, the snapshots are deported from the media server and mounted back
on the remote computer and resynchronized with the source volume. This process
requires solutions from hardware or software providers that can support transportable
snapshots, that is, snapshots that can be imported to and deported from the media
server. The Microsoft Volume Shadow Copy Services (VSS) provider that you select is
used for each volume in the offhost backup. An offhost backup job is performed on one
remote computer at a time.
Offhost backup supports the following:
■ Microsoft Volume Shadow Copy Service (VSS).
■ Veritas Storage Foundation for Windows (VSFW).
■ Backups for NTFS volumes that use the full, incremental, and differential backup
methods.
888 Administrator’s Guide
1
1. A snapshot of the selected volume on
the remote computer is mirrored to the
attached SAN device.
2. The mirror is split and the snapshot is
imported to the media server.
3. The media server backs up the
snapshot.
3
2
Backup Exec
media server
Tape
library

Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
About offhost backup
■ Microsoft SQL Server 2000 database backups by the Backup Exec Agent for
Microsoft SQL Server. For more information, see “Using the ADBO with the SQL
Agent” on page 1346.
■ Microsoft Exchange Server 2003 (Service Pack 1) database backups by the Backup
Exec Agent for Microsoft Exchange Server. For more information, see ““Setting
defaults for the Advanced Open File Option for backup jobs” on page 850.” on
page 1224.
Related Topics:
Requirements for offhost backup when using the Veritas Storage Foundation for
Windows Provider on page 890
Setting offhost backup options for backup jobs on page 892
Troubleshooting the offhost backup on page 895
Browsing remote computers for installed snapshot providers on page 894
Restoring offhost backup data on page 895
Requirements for offhost backup
The following requirements must be met to use offhost backup.
Offhost backup requirements
Computer: Requirement:
Media server ◆ Backup Exec for Windows Servers version 10.0 or
later.
◆ Backup Exec Advanced Disk-based Backup Option.
Remote computer ◆ Backup Exec Remote Agent for Windows Servers
version 10.0 or later.
Media server and the remote
computer
◆ Microsoft Windows Server 2003, Standard,
Datacenter, or Enterprise Edition with Service Pack 1
and the most recent Volume Shadow Copy Services
(VSS) patches.
◆ Selected Microsoft VSS hardware or software
provider. Otherwise, the snapshots of the volumes
cannot be deported to the media server.
◆ Ability to access disks that are shared between the
media server and the remote computer.
889

About offhost backup
Note The option Checkpoint Restart is not supported for offhost backup. For more
information on Checkpoint Restart, see “Using checkpoint restart on Microsoft
Cluster Server failover” on page 709.
When performing offhost backup, the option Use the Microsoft Change Journal if
available can only be selected for differential and incremental backups when the
modified time method is also selected.
Related Topics:
About offhost backup on page 887
Best practices for using offhost backup on page 891
Troubleshooting the offhost backup on page 895
Browsing remote computers for installed snapshot providers on page 894
Requirements for offhost backup when using the Veritas Storage
Foundation for Windows Provider
If you are using the Veritas Storage Foundation for Windows (VSFW) FlashSnap option
provider, read the following before running an offhost backup:
■ VSFW version 4.2 or later must be installed on the media server and on the
computer that contains the volumes that you want to back up.
■ The VSFW FlashSnap option must be installed on the computer that contains the
volumes that you want to back up.
■ Use the VSFW FlashSnap Snap Start command to mirror the volumes on the remote
computer. The offhost backup option does not create mirrored volumes or
resynchronize volumes that are already created and split. For details on using Snap
Start, see “Using Snap Start on a Veritas Storage Foundation volume” on page 855.
■ Confirm that the mirrored volumes that you create with the VSFW FlashSnap option
reside on disks that are shared between the remote computer (the computer
containing the volumes to be backed up) and the media server.
■ All volumes selected for offhost backup using the VSFW FlashSnap provider must
belong to the same disk group. A maximum of seven volumes can be snapped at one
time.
■ Do not select dynamic volumes and basic volumes for the same offhost backup job
because the VSFW FlashSnap option cannot perform snapshots of basic volumes.
Symantec recommends that you use other backup methods for backing up basic
volumes if the VSFW FlashSnap provider is selected.
890 Administrator’s Guide

Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
About offhost backup
■ If the computer on which you want to perform an offhost backup is in an
environment with the Central Admin Server Option and the Veritas Cluster Server
installed, and if failover occurs to a Veritas Cluster Server node, you may need to
manually clean up the snapshots before restarting the offhost backup on the
failover node. Refer to the VSFW documentation for details.
Related Topics:
Troubleshooting the offhost backup on page 895
Browsing remote computers for installed snapshot providers on page 894
Best practices for using offhost backup
■ Keep source volumes and snapped volumes from sharing the same physical disks. If
this is not maintained, then any attempt to split the snapshot volume from the
original volume fails.
■ Most hardware and software providers have some limitation about the types of
volumes that are transportable. Therefore, Symantec recommends that you use
offhost backup jobs only for backing up data for which all dependent volumes, or
mounted volumes, can be imported and deported.
■ Using offhost backup to back up Veritas Storage Foundation for Windows (VSFW)
volumes requires that snapshot volumes in shared storage be transferred from host
to host. Make sure that VSFW volumes that are backed up with offhost backup
reside in VSFW disk groups that have either the “private protection” or “cluster disk
group” disk group property. Private dynamic disk group protection and cluster disk
group property settings use hardware locking techniques to protect a dynamic disk
group that is located on shared storage from being accessed by other hosts that are
connected to the shared storage pool.
■ The offhost backup will fail if any one volume that you select for backup is only
supported by a Microsoft Volume Shadow Copy Services (VSS) provider and cannot
be imported or deported, or if the required VSS hardware provider is not on a
Symantec-approved compatibility list. You can choose to continue the backup if the
offhost backup fails. For a list of supported devices, see:
http://support.veritas.com/rd/bews-compatibility.htm
■ The Hitachi Raid Manager log cannot be on a volume being snapped. Hitachi
executes I/O to its Raid Manager log file during the snapshot commit process, and
the VSS coordinator blocks I/O to any drive being snapped. Therefore, if the log
directory for Raid Manager is on the volume that is being snapped, then log I/O is
blocked and the snap process is deadlocked.
891

About offhost backup
■ If the Central Admin Server Option (CASO) is installed, for jobs that use offhost
backup, you must manually select the destination device that will run the job rather
than allowing the job to be delegated by the central administration server.
Otherwise, the job could be delegated to a media server that does not have offhost
capability. See “Grouping managed media servers in pools” on page 818.
■ When performing an offhost backup using a VSS hardware provider in a Microsoft
Cluster Server (MSCS) or Veritas Cluster Server environment, the media server and
the remote computer must not be in the same cluster group. The cluster applications
cannot support devices’ logical unit numbers (LUNs) that have duplicate signatures
and partition layouts, therefore, the snapshots containing the LUNs must be
transported to a host, or remote computer, that is outside the cluster. See “Using
Symantec Backup Exec with Server Clusters” on page 701.
Related Topics:
About offhost backup on page 887
Requirements for offhost backup on page 889
Requirements for offhost backup when using the Veritas Storage Foundation for
Windows Provider on page 890
Setting offhost backup options for backup jobs on page 892
Browsing remote computers for installed snapshot providers on page 894
Troubleshooting the offhost backup on page 895
Setting offhost backup options for backup jobs
You can set the offhost backup options for each backup job, or you can set defaults that
are used for every backup job.
For details on how to create a backup job, and for definitions of all other backup options,
see “Creating a backup job by using the Backup Wizard” on page 347. For offhost
backups, the option Use the Microsoft Change Journal if available can only be selected
for differential and incremental backups when the modified time method is also
selected.
Note If the Central Admin Server Option (CASO) is installed, for jobs that use offhost
backup, you must manually select the destination device that will run the job
rather than allowing the job to be delegated by the central administration server.
Otherwise, the job could be delegated to a media server that does not have offhost
capability. See “Grouping managed media servers in pools” on page 818.
892 Administrator’s Guide

To set offhost backup options for backup jobs
1. Do one of the following:
To set offhost backup
options for a single
backup job
To set offhost backup
options for all backup
jobs
2. Select the appropriate options, and then click OK.
Use offhost backup to
move backup processing
from remote computer
to media server
Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
About offhost backup
◆ On the navigation bar, click the arrow next to Backup.
◆ Click New Backup Job.
◆ On the Properties pane, under Settings, click Advanced
Disk-based Option.
◆ On the Tools menu, click Options.
◆ On the Properties pane, under Job Defaults, click Advanced
Disk-based Backup Option.
Select this check box to enable offhost backup. If you are enabling
this for a single job, or as a default for all backup jobs, then an
offhost backup of all volumes will be performed if all requirements
are met. For more information about offhost backup, see “About
offhost backup” on page 887.
Snapshot provider Automatic - Use hardware if available; otherwise use software.
Select this option to enable VSS to select the best provider for the
selected volume.
Software - Use Veritas Storage Foundation for Windows.
Hardware - Use technology provided by hardware manufacturer:
If you select Software or Hardware as the snapshot provider, then:
◆ The provider must support transportable snaps.
◆ If multiple volumes are selected, then all volumes must be
snappable by the same type of provider.
◆ Software and hardware providers cannot both be used to snap
different volumes in the same job. You must either create
another job, or make sure that the option Process logical
volumes for offhost backup one at a time is selected.
893

About offhost backup
If any of the selected
resources do not
support offhost backup
Process logical volumes
for offhost backup one
at a time
◆ Continue the backup job (offhost backup is not used): Select
this to allow the backup job to complete even if any of the
volumes selected do not support offhost backup, or if an error
that is related to the snapshot or volume import occurs. The
backup will run according to all the other options that have
been set for this job.
◆ Fail the backup job (further selections are not backed up after
failure occurs): Select this to terminate the offhost backup job
if any of the selected volumes do not support offhost backup, or
if an error that is related to the snapshot or volume import
occurs.
Enables the backup of multiple volumes in one job, while creating a
snapshot of only one logical volume at a time. To ensure database
integrity, or if a volume contains mount points, multiple volumes
may need to be snapped at one time.
After the logical volume is snapped and backed up, the snapshot is
deleted before the next logical volume is snapped. This option
increases the ability to meet the minimum quiet time needed to
complete a snapshot.
A logical volume can comprise multiple physical volumes. A single
logical volume can encompass all of the volumes on which
databases reside.
Related Topics:
About offhost backup on page 887
Requirements for offhost backup on page 889
Requirements for offhost backup when using the Veritas Storage Foundation for
Windows Provider on page 890
Best practices for using offhost backup on page 891
Troubleshooting the offhost backup on page 895
Browsing remote computers for installed snapshot providers
You can view which snapshot providers are installed on a remote computer before
running an offhost backup for selected resources on that computer.
The Microsoft Volume Shadow Copy Services (VSS) hardware or software provider that
you select when creating an offhost backup must also be installed on the remote
computer that you want to back up. If the snapshot provider is not installed on the
remote computer, the snapshots of the volumes cannot be imported to the media server.
894 Administrator’s Guide

To browse remote computers for installed snapshot providers
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Properties pane, under Source, click Selections.
Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
Troubleshooting the offhost backup
4. On the backup selections tree, right-click the remote computer that contains the
volumes you want to back up, and then click List Snapshot Providers.
5. View the list of the available snapshot providers on the remote computer.
Related Topics:
Requirements for offhost backup when using the Veritas Storage Foundation for
Windows Provider on page 890
Requirements for offhost backup on page 889
Best practices for using offhost backup on page 891
Setting offhost backup options for backup jobs on page 892
Restoring offhost backup data
Restoring data backed up with the offhost backup method is a standard restore
operation. Data is restored directly from the backup media to the original volumes on
the remote computer.
Related Topics:
“Restoring data” on page 483
Troubleshooting the offhost backup
Offhost backup requires that the VSS providers and the volumes that are to be
transported are set up correctly. Not all arrays are supported with the Advanced
Disk-based Option. For a list of supported devices, see:
http://support.veritas.com/rd/bews-compatibility.htm
In order to troubleshoot offhost backup issues, Symantec recommends that you use the
tools that are available from the VSS provider to verify the setup that is required for
offhost backup. The minimum setup requirements are:
895

Troubleshooting the offhost backup
■ All volumes to be backed up are snappable.
■ Volumes are shared between the remote computer and the media server.
For example, when using Veritas Storage Foundation for Windows (VSFW) as the
provider, you can use the Veritas Enterprise Administrator (VEA) to verify
snapshots of the volumes, split the snapped volumes into a different Disk Group
(DG), deport the DG from the remote computer and import it to the media server. All
providers will have similar administration console or command-line tools that will
allow you to take a snapshot of volumes, and deport and import volumes.
It is also required that an offhost backup job contain only volumes that can be
transported to the media server for backup. Please read the requirements section
carefully. For more information, see “Requirements for offhost backup” on page 889
and “Requirements for offhost backup when using the Veritas Storage Foundation
for Windows Provider” on page 890.
Other factors to consider are:
■ Microsoft Windows Server 2003 Enterprise or Data Center edition must be installed
on both the media server and the remote computer.
■ Microsoft XML Core Services (MSXML4) must be installed and running on both the
media server and the remote computer.
Troubleshooting offhost backup issues depends to an extent on the VSS provider used
for the snapshots, but there are setup issues that are common to all providers that may
cause offhost backup to fail:
■ Volumes are not shared
For offhost backup to work, all volumes must reside on disks that are shared
between the remote computer and the Backup Exec media server. It is the backup
administrator's responsibility to confirm this. If the volumes are not shared, the
import operation will fail, and you may need to clean up the snapshots and
resynchronize the volumes manually.
■ VSS Provider installation
The provider used for snapshot must be installed on both the media server as well as
on the remote computer. If the provider is not installed on the media server, the
import operation will fail, and you may need to clean up the snapshots and
resynchronize the volumes manually.
■ All volumes are not transportable
All volumes selected for backup must be transportable to the media server. If
Microsoft SQL or Exchange, or other database applications are selected for backup,
make sure that the databases and log files reside on transportable volumes.
■ VSS Provider selection
896 Administrator’s Guide

Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
Troubleshooting the offhost backup
In addition to being transportable, all volumes selected for backup must be
snappable by the same provider. It is the backup administrator's responsibility to
ensure that all volumes in a backup job are supported by the same VSS provider.
■ Log path location
Log files created by the provider or by its supporting application during normal
snapshot operation should not reside on any of the volumes being snapped. This
prevents VSS from flushing the write buffers, and the snapshot will time-out.
Change the log path to another volume.
■ Provider or VSS services not started
Make sure that the provider service is running and make sure that the Microsoft
Windows "Volume Shadow Copy" service has not been disabled.
■ Credentials
Make sure that the machine-level credentials used for the job are the same on both
the media server and the remote computer. Incorrect credentials will cause
snapshots or the backup to fail.
■ Central Admin Server Option (CASO) environment
If a backup job is configured in a CASO environment, you must target the job to
media servers on which the selected VSS provider is installed rather than allowing
the job to be delegated by the central administration server. Otherwise, the job
could be delegated to a media server that does not have offhost capability. See
“Grouping managed media servers in pools” on page 818.
■ Clusters
When performing an offhost backup in a Microsoft Cluster Server (MSCS) or Veritas
Cluster Server environment, the media server and the remote computer must not be
in the same cluster group. The cluster applications cannot support devices' logical
unit numbers (LUNs) that have duplicate signatures and partition layouts;
therefore, the snapshots containing the LUNs must be transported to a media server
that is outside the cluster in which the host cluster resides. See “Using Symantec
Backup Exec with Server Clusters” on page 701.
If you are using an Hitachi 9970 and attempt to protect a Microsoft Cluster Server
(MSCS) resource using the Advanced Disk-based Backup Option (ADBO), you may
receive the following error message:
The job failed with the following error: A failure occurred
querying the Writer status.
To correct this problem, do the following:
Make sure the RM Shadow Copy Provider for Volume Snapshot Service is present
and running.
897

Troubleshooting the offhost backup
If the service is not running, run RMVSSPRV.exe from c:\horcm\tool.
If the service is still not running, contact Hitachi for support.
Offhost backup failures when using VSFW as a provider
Following are the most common causes of snapshot failure and offhost backup failure
when using the Veritas Storage Foundation for Windows (VSFW) software provider:
■ Volume has not been snap started. Backup Exec requires that you first snap start all
volumes using the Veritas Enterprise Administrator administration console or
command-line interface before attempting an offhost job (see “Using Snap Start on a
Veritas Storage Foundation volume” on page 855). If you already performed the snap
start for a previous snapshot operation, you must either snap start the volume again
(to another physical disk) or snap back the previous snapshot volume. For details on
how to snap back, refer to the documentation for the Veritas Storage Foundation for
Windows software provider.
■ Volumes to be backed up are basic volumes. VSFW allows only dynamic volumes to
be snapped.
■ You are trying to back up a volume that resides on a disk with other volumes and so
the disk group cannot be deported.
■ Any attempt to split the snapshot volumes from the source volumes will fail if the
snapshot volumes and the source volumes share the same physical disks. The
administrator must keep the source volumes and the snap volumes from sharing the
same physical disks.
■ Offhost backup requires that VSFW version 4.1 or later be installed on both the
remote computer and on the media server. Previous releases are not supported.
Compatible VSFW software versions must reside on both the media server and the
remote computer. It is recommended that the same version of VSFW be installed on
both computers.
■ All dynamic volumes designated for backup must be in the same Disk Group (DG).
Multiple disk groups in the same offhost job are not supported.
■ Ensure that there are no more than seven volumes in a single snapshot operation.
When more volumes are installed, they cannot all be snapped within the ten-second
time-out that VSS imposes for snapshots to complete, and the snapshot will fail.
■ Basic volumes and dynamic volumes cannot be mixed in a backup job that uses the
offhost feature. A workaround is to make sure that the option Process logical
volumes for offhost backup one at a time is selected. This restriction also applies to
dynamic volumes that are mounted by mount points on basic volumes.
■ Dynamic boot and system volumes are restricted from VSFW FlashSnap
functionality for compatibility reasons. Therefore, dynamic boot and system
volumes are not supported for an offhost backup.
898 Administrator’s Guide

Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
Troubleshooting the offhost backup
Note Most VSS providers have some limitation about the types of volumes that are
transportable. Therefore, it is recommended that you do not use offhost backup
jobs for complete system protection. A best practice is to use offhost backup jobs
to back up databases and logs when all of the dependent volumes on which data
resides are transportable. Any volumes that are used to host mount points for
data volumes must also be transportable because the offhost backup must snap
both the data volumes and the volume with the mount point for backup.
Offhost backup issues when using a hardware provider
Hardware disk array vendors may support VSS snapshots and the transporting of
volumes to the media server for backup in a SAN environment. Using hardware
providers requires a sound understanding of how disk arrays are configured for shared
access between the remote computer and the media server in a SAN.
Consult the documentation for your hardware disk array on how to set up such disk
arrays for offhost backup. Specifically, note any limitations on using the disk arrays in
context with VSS snapshots, and note how to verify if the volumes are transportable. It
is highly recommended that you make use of any tools provided by the vendor to help
verify the setup and for troubleshooting issues.
Offhost backup issues when using Hitachi hardware
■ Hitachi supports only basic disks for offhost backup. If a computer uses a
combination of dynamic and basic disks, a complete system backup using the
offhost backup feature is not possible when the Hitachi provider is used.
■ Veritas Cluster Server (VCS) is not supported with the Hitachi provider. The Hitachi
provider does not support dynamic disks for offhost backup.
Related Topics:
Requirements for offhost backup on page 889
Requirements for offhost backup when using the Veritas Storage Foundation for
Windows Provider on page 890
Best practices for synthetic backup on page 870
899

Troubleshooting the offhost backup
900 Administrator’s Guide

Appendix
Symantec Backup Exec
Active Directory Recovery
Agent
901
D
The Symantec Backup Exec for Windows Servers Active Directory Recovery Agent
(ADRA) is installed as a separate, add-on component of Backup Exec for Windows
Servers.
Using the ADRA, you can restore Active Directory or Active Directory Application Mode
(ADAM) objects and attributes without having to perform an authoritative or
non-authoritative full restore.
Related Topics:
“Requirements for the Active Directory Recovery Agent” on page 901
“Installing the Active Directory Recovery Agent” on page 903
“About the Active Directory Recovery Agent” on page 903
“About restoring individual Active Directory and ADAM objects” on page 905
Requirements for the Active Directory Recovery Agent
You must meet the following requirements before you can restore individual objects and
attributes using the ADRA:
■ Although it is enabled by default, you must verify that the option Enable the restore
of individual objects from Active Directory backups is selected when you create the
backup. This check box is located on the Microsoft Active Directory node of the
Backup Job Properties dialog box.
Individual attributes and properties can be restored from full Active Directory and
ADAM backups only if this option is selected during backup. If this option is not
enabled, you cannot restore individual Active Directory objects and attributes. If the
backup is disk based, the restore will take significantly less time than if the backup

Requirements for the Active Directory Recovery Agent
was to tape. Restoring from tape requires the creation of a temporary hard disk
staging location where the data from tape is first copied. As such, a restore from
tape will take more time since the entire backup set must be read in order to extract
the selected attributes and properties.
Note If you want to restore individual Active Directory or ADAM objects and
attributes from tape to a 64-bit computer, you must move the tape to a media
server that is running a 64-bit operating system. See “About restoring
individual Active Directory and ADAM objects” on page 905.
Note If you want to use a backup-to-disk folder as the destination device for the full
mode backup, the backup-to-disk folder must reside on a local NTFS volume.
■ You must have a full mode backup of the ADAM or the Windows System State
(where Active Directory is installed).
■ You must use one of the following Windows operating systems on the computer
where Active Directory is in use:
■ Windows XP Professional x64 Edition
■ Windows 2000 Server with Service Pack 4.
ADRA does not support re-animation of objects from the Active Directory
Deleted Objects container on a Windows 2000 domain controller. It is
recommended that individual restores of deleted objects be done by a
Backup Exec Remote Agent on a Windows 2003 domain controller, if one
exists in the same domain. Deleted objects can only be restored using an
agent on a Windows 2000 domain controller if the Recreate deleted object
check box is checked.
■ Windows Server 2003 with Service Pack 1 or later
■ Windows Server 2003 R2
■ You must use a version of the Windows operating system that supports minifilter
drivers on the media server that runs the restore job. Minifilter drivers are
supported in the following Windows operating systems:
■ Windows 2000 with both Service Pack 4 and the Windows 2000 Rollup Patch
1 installed
■ Windows Server 2003 with Service Pack 1 or later installed.
■ You must be running Backup Exec Remote Agent for Windows Servers version 11 on
the computer where Active Directory is installed.
■ You must designate a location on the media server disk where Backup Exec can
temporarily place the objects and attributes that are being restored when you
restore from tape.
902 Administrator’s Guide

Appendix D, Symantec Backup Exec Active Directory Recovery Agent
Installing the Active Directory Recovery Agent
Related Topics:
“Installing the Active Directory Recovery Agent” on page 903
“About the Active Directory Recovery Agent” on page 903
“About restoring individual Active Directory and ADAM objects” on page 905
Installing the Active Directory Recovery Agent
ADRA is installed locally as a separate, add-on component of Backup Exec for Windows
Servers.
For instructions on installing ADRA on the local media server, see “Installing Backup
Exec options to the local computer” on page 85.
Related Topics:
“About the Active Directory Recovery Agent” on page 903
“About restoring individual Active Directory and ADAM objects” on page 905
About the Active Directory Recovery Agent
ADRA works with backups of the Windows System State (where Active Directory is
installed) and ADAM.
When you back up the Windows System State, the Active Directory is included in the
backup job, because Active Directory is a component of Windows System State. To
restore individual Active Directory objects and attributes, select them from the View by
Resource tab on the Restore Job Properties view.
You can also use ADRA to restore individual ADAM objects and attributes. You can
select individual ADAM objects and attributes for restore from the View by Resource tab
on the Restore Job Properties view. If multiple ADAM instances are backed up, each
instance appears under the Active Directory Application Mode node.
903

About the Active Directory Recovery Agent
View by Resource view - ADAM and Active Directory nodes
ADAM node
Individual Active Directory objects
You do not have to restart your computer when the restore job completes.
ADRA also lets you restore tombstoned objects from the Active Directory Deleted
Objects container if:
■ their tombstone lifetimes have not passed.
■ they have not been purged from the Deleted Objects container.
Active Directory node
■ you are restoring to a Windows 2003 or Windows XP X64 system.
It is recommended that Active directory and ADAM backups be backed up to a
backup-to-disk folder before you back them up to tape. This provides you with shorter
backup windows, while also allowing you to administer Active Directory or ADAM
without requiring the individual cataloging of the backed up objects and properties.
When backing up any Windows Active Directory or ADAM application database directly
to tape, it is possible that the objects and properties added or deleted during the backup
will not match the individual objects and properties that are available for restore from
the backup set. The back up of the database is a snapshot backup of the live Active
Directory or ADAM database and the cataloging of the individual Active Directory or
ADAM objects occurs after the snapshot is performed. Since the catalog operation
catalogs objects and properties from the live Active Directory or ADAM database, object
and property changes can occur after the snapshot was taken.
Related Topics:
“About restoring individual Active Directory and ADAM objects” on page 905
“About recreating purged Active Directory and ADAM objects” on page 908
904 Administrator’s Guide

Appendix D, Symantec Backup Exec Active Directory Recovery Agent
About restoring individual Active Directory and ADAM objects
About restoring individual Active Directory and ADAM objects
Before starting the restore job, review “Restoring data” on page 483 for information on
finding and viewing specific data to restore, as well as for details on restore options and
restore jobs.
When you restore Active Directory and ADAM objects from tape, you must specify an
on-disk staging location where the objects will be placed prior to being restored. The
staging location must be a path on a local NTFS volume on the media server running the
restore job and the Backup Exec service account must also have access to it.
Note If you previously defined a default staging location in the option, Path on media
server for staging temporary restore data when restoring individual items from
tape under Tools>Options>Restore, you can override the default by specifying an
alternate staging location for each Active Directory and ADAM restore job by
entering a path in the Advanced node found under Settings on the Restore Job
Properties pane.
Backup Exec only supports full restores of the Active Directory database to a 64-bit
computer from a 32-bit media server. You can use the 32-bit media server to create a tape
backup of a 64-bit computer. After creating the tape backup, you can restore individual
Active Directory or ADAM objects and attributes from the tape to a 64-bit computer only
by moving the tape to a media server running on a 64-bit operating system.
Because of the potentially large file sizes that are created on the disk specified in the
staging location path, system volumes should not be used as a staging location.
Note Because restoring objects from tape requires the creation of a staging location,
restoring from tape requires more time than if you are restoring from disk.
By default, ADRA restores Active Directory or ADAM objects from the Active Directory
Deleted Objects container if their tombstone lifetimes have not passed.
When objects in Active Directory are deleted, they are removed from their current Active
Directory or ADAM container, converted into tombstones, and then placed in the Active
Directory Deleted Objects container where their tombstone lifetime is monitored. After
their tombstone lifetime passes, the tombstones are purged from the Active Directory
Deleted Objects container, which permanently deletes the objects from the Active
Directory and ADAM databases.
905

About restoring individual Active Directory and ADAM objects
Note When restoring Active Directory user objects, you must reset the object’s user
password and then re-enable the object’s user account. For ADAM user objects,
you must reset the object’s user password and then re-enable the object’s user
account. For Active Directory user objects, use the Microsoft Active Directory
Users and Computers application. For ADAM user objects, use ADSI Edit.
For Active Directory computer objects, you must reset the object’s account. For
more information, see “Resetting the Active Directory computer object account”
on page 911.
Note ADRA does not support re-animation of objects from the Active Directory Deleted
Objects container on a Windows 2000 domain controller. It is recommended that
individual restores of deleted objects be done by a Backup Exec Remote Agent on a
Windows 2003 domain controller, if one exists in the same domain. If a Windows
2003 domain controller is not available in the domain, deleted objects can only be
restored using an agent on a Windows 2000 domain controller if the Recreate
deleted object check box is checked.
For more information, see your Microsoft Active Directory documentation.
Related Topics:
“Inventorying media” on page 238
“Cataloging media while reviewing devices or media” on page 284
“Restoring individual objects from an Active Directory backup” on page 906
“Path on media server for staging temporary restore data when restoring individual
items from tape” on page 497
“Restoring individual objects from an ADAM backup” on page 908
“About recreating purged Active Directory and ADAM objects” on page 908
“Resetting the Active Directory computer object account” on page 911
Restoring individual objects from an Active Directory backup
To restore individual objects from an Active Directory backup
1. On the navigation bar, click the down arrow next to Restore.
2. Click New Restore Job.
906 Administrator’s Guide

Appendix D, Symantec Backup Exec Active Directory Recovery Agent
About restoring individual Active Directory and ADAM objects
3. In the View by Resource pane, double-click a backup set that contains the most
recent System State backup.
If you want to restore Active Directory objects from a previous backup, select the
appropriate backup set.
4. Double-click System State.
5. Double-click the most recent System State snapshot.
6. Double-click Active Directory.
7. In the Results pane, select the appropriate object or objects.
8. If you are restoring from tape:
■ On the properties pane, under Settings, click Advanced.
■ If you have not set a default temporary staging location, type a path in the box
titled Path on media server for staging temporary restore data when restoring
individual from backup media.
9. Click Run Now to start the restore job or select other restore options from the
Properties pane.
Any Active Directory or ADAM object or property that is selected for restore will
overwrite existing objects and properties, even if you selected Skip if file exists or
Skip if existing file is more recent on the General Restore Job Properties dialog box.
10. If you restored a a deleted user object, use the Microsoft Active Directory Users and
Computers application to reset the object’s user password and re-enable the object’s
user account. If you restored a computer object, see “Resetting the Active Directory
computer object account” on page 911.
Related Topics:
“Restoring individual objects from an ADAM backup” on page 908
“About recreating purged Active Directory and ADAM objects” on page 908
907

About recreating purged Active Directory and ADAM objects
Restoring individual objects from an ADAM backup
To restore individual objects from an ADAM backup
1. On the navigation bar, click the down arrow next to Restore.
2. Click New Restore Job.
3. In the View by Resource pane, double-click Active Directory Application Mode.
4. Double-click the appropriate ADAM instance.
5. Double-click the appropriate backup set.
6. In the Results pane, select the appropriate object or objects.
7. If you are restoring from tape:
■ On the properties pane, under Settings, click Advanced.
■ If you have not set a default temporary staging location, type a path in the box
titled Path on media server for staging temporary restore data when restoring
individual from backup media.
8. Click Run Now to start the restore job or select other restore options from the
Properties pane.
Any Active Directory or ADAM object or property that is selected for restore will
overwrite existing objects and properties, even if you selected Skip if file exists or
Skip if existing file is more recent on the General Restore Job Properties dialog box.
9. If you restored a deleted user object, use the ADSI Edit application to reset the
object’s user password and re-enable the object’s user account.
Related Topics:
“Restoring individual objects from an Active Directory backup” on page 906
“About recreating purged Active Directory and ADAM objects” on page 908
About recreating purged Active Directory and ADAM objects
You can attempt to recreate deleted objects if their tombstone lifetimes have passed and
the objects have been purged from the Active Directory Deleted Objects container.
However:
908 Administrator’s Guide

Appendix D, Symantec Backup Exec Active Directory Recovery Agent
About recreating purged Active Directory and ADAM objects
■ Most applications will not recognize a recreated object since recreated objects are
not identical to the original deleted object. Recreated objects are assigned new
global unique identifiers (GUIDs) and security identifiers (SIDs) that cannot be
identified by the applications that created the original object.
■ Attributes created by the Windows operating system cannot be recreated when a
purged object is recreated. Hence, objects that rely on attributes set by the operating
system will not be recognized by Windows when the objects are recreated.
Related Topics:
“Recreating purged Active Directory objects” on page 909
“Recreating purged ADAM objects” on page 910
“About restoring individual Active Directory and ADAM objects” on page 905
Recreating purged Active Directory objects
You can attempt to recreate deleted Active Directory objects after they have been
purged from the Active Directory Deleted Objects container by restoring the object from
a prior Active Directory backup.
To recreate purged Active Directory objects
1. On the navigation bar, click the down arrow next to Restore.
2. Click New Restore Job.
3. In the View by Resource pane, double-click a backup set that contains the most
recent System State backup.
If you want to restore Active Directory objects from a previous backup, select the
appropriate backup set.
4. Double-click System State.
5. Double-click the most recent System State snapshot.
6. Double-click Active Directory.
7. In the Results pane, select the appropriate objects.
8. On the Properties pane, under Settings, click Microsoft Active Directory.
9. Check Recreate deleted objects that cannot be restored from the Active Directory
Deleted Objects container.
909

About recreating purged Active Directory and ADAM objects
10. If you are restoring from tape:
■ On the properties pane, under Settings, click Advanced.
■ If you have not set a default temporary staging location, type a path in the box
titled Path on media server for staging temporary restore data when restoring
individual from backup media.
11. Click Run Now to start the restore job or select other restore options from the
Properties pane.
Any Active Directory or ADAM object or property that is selected for restore will
overwrite existing objects and properties, even if you selected Skip if file exists or
Skip if existing file is more recent on the General Restore Job Properties dialog box.
12. Use the Microsoft Active Directory Users and Computers application to reset the
object’s user password and re-enable the object’s user account.
Related Topics:
“Recreating purged ADAM objects” on page 910
“About restoring individual Active Directory and ADAM objects” on page 905
“Resetting the Active Directory computer object account” on page 911
Recreating purged ADAM objects
You can attempt to recreate deleted ADAM objects after they have been purged from the
Active Directory Deleted Objects container by restoring the object from a prior ADAM
backup.
To recreate purged ADAM objects
1. On the navigation bar, click the down arrow next to Restore.
2. Click New Restore Job.
3. In the View by Resource pane, double-click Active Directory Application Mode.
4. Double-click the appropriate ADAM instance.
5. Double-click the appropriate backup set.
6. In the Results pane, select the appropriate objects.
7. On the Properties pane, under Settings, click Microsoft Active Directory.
910 Administrator’s Guide

Appendix D, Symantec Backup Exec Active Directory Recovery Agent
About recreating purged Active Directory and ADAM objects
8. Check Recreate deleted objects that are no longer in the Active Directory Deleted
Objects container.
9. If you are restoring from tape:
■ On the properties pane, under Settings, click Advanced.
■ If you have not set a default temporary staging location, type a path in the box
titled Path on media server for staging temporary restore data when restoring
individual from backup media.
10. Click Run Now to start the restore job or select other restore options from the
Properties pane.
Any Active Directory or ADAM object or property that is selected for restore will
overwrite existing objects and properties, even if you selected Skip if file exists or
Skip if existing file is more recent on the General Restore Job Properties dialog box.
11. Use the ADSI Edit application to reset the object’s user password and re-enable the
object’s user account.
Related Topics:
“Recreating purged Active Directory objects” on page 909
“Resetting the Active Directory computer object account” on page 911
Resetting the Active Directory computer object account
In Active Directory, computer objects are derived from user objects. Some attributes
associated with a computer object cannot be restored when you restore a deleted
computer object unless the attributes were saved through schema changes when the
computer object was originally deleted. Because computer object credentials change
every 30 days, the credentials from the backup may not match the credentials stored on
the actual computer.
When a computer object is restored it is disabled if the userAccountControl property was
not preserved in the deleted object.
You must use the Microsoft Active Directory Users and Computers application to reset a
computer object.
911

About recreating purged Active Directory and ADAM objects
To reset a computer object’s account
1. Remove the computer from the domain.
2. Re-join the computer to the domain. The SID for the computer remains the same
since it is preserved when a computer object is deleted. However, if the tombstone
expired and a new computer object was recreated, the SID will be different.
Related Topics:
“Recreating purged ADAM objects” on page 910
912 Administrator’s Guide

Appendix
Symantec Backup Exec
Remote Agent for Windows
Systems
E
The Symantec Backup Exec Remote Agent for Windows and NetWare Systems (Remote
Agent) is installed as a separate, add-on component that must be used for the backup
and restore of remote Windows or NetWare resources. This section details how to
protect remote Windows resources.
For specific information on protecting remote NetWare resources, see “Symantec Backup
Exec Remote Agent for NetWare Systems” on page 923.
The Remote Agent is a system service that runs on remote Windows servers and
workstations. The Remote Agent provides faster backup processing by locally
performing tasks that in typical backup technologies, require extensive network
interaction. The Remote Agent processes backup data into a continuous stream that the
media server then processes as a single task. This method provides better data transfer
rates over traditional technologies, which require multiple requests and
acknowledgments between the media server and the remote server.
The Remote Agent enables you to:
■ Back up and restore in firewall environments.
■ Back up and restore using a specified local network if the media server and the
remote computer are on the same subnet.
■ Display the remote computer in the media server's Favorite Resources node.
■ Back up and restore the Extensible Firmware Interface (EFI) on Intel Itanium-based
operating systems when the Remote Agent is installed.
■ Attain significant performance increases when running modified backups (for
example, differential and incremental). This occurs because file selection is
performed locally by the Remote Agent instead of across the network as performed
by traditional network backup applications.
913

Requirements for the Remote Agent for Windows Systems
Note Network hardware has a major impact on performance. Performance is directly
related to the capabilities of the networking hardware in the media server and the
remote device. Higher network bandwidth ratings also contribute to faster
operation processing.
Related Topics:
“Requirements for the Remote Agent for Windows Systems” on page 914
“Installing the Remote Agent for Windows Systems” on page 97
“Setting default backup network and security options” on page 400
“Using Backup Exec with firewalls” on page 405
“About the Backup Exec Shadow Copy Components file system” on page 341
“The Remote Agent Utility for Windows Systems” on page 917
Requirements for the Remote Agent for Windows Systems
Because a Remote Agent is also a Client Access License (CAL), you must install the
Remote Agent on any remote Windows computer that you want to back up. You cannot
fully protect resources on a remote server until a Remote Agent has been installed.
At the media server (Backup Exec server), you must enter Remote Agent license keys for
each remote Windows computer that you want to protect. To back up a remote Windows
computer from more than one media server, you must enter the same Remote Agent
license key on each media server.
Backup Exec database agents and the Advanced Open File Option (AOFO) also include a
Remote Agent that allows you to protect one remote Windows computer. The Remote
Agent license is enabled when you enter the license keys for the database agents and
AOFO in the media server.
You must install the Remote Agent on Windows XP Professional and Windows 2000
Professional computers in order to protect them; however, a Remote Agent license key is
not required for these installations.
Note If a previous version of the Remote Agent is installed, it is automatically upgraded
when you initiate a new Remote Agent installation. Previous versions of the
Remote Agent are automatically detected on the remote computers and replaced
with the new version during installation of the new Remote Agent. The name of
the system service may have changed when the upgrade is complete.
The Remote Agent is available for 32-based, Itanium-based, and x64-based operating
systems.
914 Administrator’s Guide

Appendix E, Symantec Backup Exec Remote Agent for Windows Systems
Installing the Remote Agent for Windows Systems
You must purchase the Remote Agent and install it to back up and restore data that
resides on the following operating systems:
■ Microsoft Windows XP Professional
■ Microsoft Windows XP Professional x64 Edition
■ Microsoft Windows 2000 Server Product Family (with Service Pack 4)
■ Microsoft Windows Server 2003 x64 Editions
■ Microsoft Windows Server 2003 R2
■ Microsoft Windows XP 64-bit Edition
■ Microsoft Windows Server 2003 for Itanium-based Systems (with Service Pack 1)
To protect the Workstation versions of these platforms, you must install the Remote
Agent on each platform; however a license is not required for computers running
Windows workstation operating systems.
Related Topics:
“Installing the Remote Agent for Windows Systems” on page 97
Installing the Remote Agent for Windows Systems
You can install the Remote Agent for Windows Systems using many methods, depending
on your environment. For instructions on installing the Remote Agent, see “Installing
the Remote Agent for Windows Systems” on page 97.
Backing up data using the Remote Agent for Windows
Systems
You must install the Remote Agent on all remote Windows computers that you want to
be backed up. For application-specific data, such as SQL databases or Exchange
databases, the appropriate Backup Exec Agent should be installed to provide full backup
and restore capability for that data.
Without the Remote Agent, the following Windows features cannot be backed up
correctly:
■ Encrypted files
■ SIS files
■ Disk quota data
915

Stopping and starting the Remote Agent for Windows Systems
■ Removable Storage data
■ Remote Storage data
■ Mount points
■ Sparse files
■ Shadow Copy Components on Windows Server 2003
■ System State on Windows 2000, Windows XP, or Windows Server 2003
■ System State data, including:
■ COM+ Class Registration database
■ Boot and system files
■ Registry
■ Certificate Services database (if the server operates as a certificate server)
■ Active Directory (if the server is a domain controller)
■ SYSVOL (if the server is a domain controller)
■ Cluster quorum
Stopping and starting the Remote Agent for Windows
Systems
The Remote Agent is automatically started as a service when Windows is started on the
remote computer.
To stop or start the Remote Agent for Windows Systems
1. On a Windows computer, right-click My Computer, and then click Manage.
2. On the Computer Management dialog box, double-click Services and Applications
and then click Services.
3. In the Results pane, right-click the Backup Exec Remote Agent for Windows
Systems service. Click Stop to stop the Remote Agent or click Start to start the
Remote Agent.
916 Administrator’s Guide

The Remote Agent Utility for Windows Systems
Appendix E, Symantec Backup Exec Remote Agent for Windows Systems
The Remote Agent Utility for Windows Systems
The Remote Agent Utility is installed when the Remote Agent is installed on a remote
Windows computer.
Features in the Remote Agent Utility
To: Go to:
Start the Remote Agent Utility, or
open the Registry Editor, the Services
window, or the Event Viewer on the
remote Windows computer
View current activity on the remote
Windows computer
Configure the Remote Agent to send
information about itself, such as its
version and IP address, to a media
server
Configure the Remote Agent Utility
for backup and restore operations of
Oracle instances
Configure the Remote Agent Utility
for backup and restore operations of
DB2 instances
Starting the Remote Agent Utility
To start the Remote Agent Utility
“Starting the Remote Agent Utility” on page 917
“Viewing activity on the remote computer” on page 918
“Publishing the remote Windows computer to media
servers” on page 919
“Configuring the Oracle Agent on Windows computers”
on page 1399
“Configuring the DB2 Agent on Windows computers” on
page 1465
1. On the computer on which the Remote Agent is installed, on the taskbar, click Start
> All Programs > Symantec Backup Exec for Windows Servers > Backup Exec
Remote Agent Utility.
When the Remote Agent Utility is running, an icon appears in the system tray. You
can double-click this icon to view the utility.
2. To open the Registry Editor, the Services window, and the Event Viewer on the
remote Windows computer, right-click the Remote Agent Utility icon in the system
tray, and then click Tools.
917

The Remote Agent Utility for Windows Systems
Related Topics:
“Viewing activity on the remote computer” on page 918
“Publishing the remote Windows computer to media servers” on page 919
Viewing activity on the remote computer
To view activity on the remote computer
1. On the computer on which the Remote Agent is installed, on the taskbar, click Start
> All Programs > Symantec Backup Exec for Windows Servers > Backup Exec
Remote Agent Utility.
If the Remote Agent Utility is already running, you can double-click its icon in the
system tray.
2. Click the Status tab.
3. Complete the appropriate options as follows:
Start the Remote Agent
Utility every time you
log on
4. Click OK.
Check Start the Remote Agent Utility every time you log on to
display the Remote Agent Utility when you log on to this computer.
Refresh interval Type the number of seconds for the Remote Agent Utility to wait
before refreshing the status of the computer. The default setting is
to refresh every 5 seconds.
Media server Name of the media server that is processing the current operation.
Source Media or share that is being processed.
Current folder Name of the current directory, folder, or database (depending on
the specific agent) that is being processed.
Current file Name of the current file that is being processed.
5. To display an activity status on the remote computer, position the cursor over the
Remote Agent icon in the system tray.
918 Administrator’s Guide

Possible statuses are:
■ Idle
■ Backup is running
■ Restore is running
■ Backup and Restore are running
Appendix E, Symantec Backup Exec Remote Agent for Windows Systems
The Remote Agent Utility for Windows Systems
■ The Backup Exec client service, BEREMOTE.EXE, is not running on the
computer
■ Snapshot in progress
Related Topics:
“Viewing activity on the remote computer” on page 918
“Publishing the remote Windows computer to media servers” on page 919
Publishing the remote Windows computer to media servers
Use the Remote Agent Utility to add, change, or delete the media server names or IP
addresses that this remote computer publishes to. Each media server that you add to the
list on the Publishing tab displays this remote computer in its backup selection tree,
under Favorite Resources.
This information that the Remote Agent publishes includes the version of the Remote
Agent and the remote computer’s IP addresses. Because the remote computer’s IP
address is published to the media server, the media server can connect to and display
the remote computer even if it is in an unknown domain.
For each media server that is published to, you can specify a local backup network for
operations between the media server and the remote computer. Directing jobs to a
specified local network rather than to a corporate network isolates the backup data
traffic so that other connected networks are not affected when operations are
performed between the media server and the remote computer. For more information,
see “Specifying backup networks” on page 398.
To publish the remote Windows computer to media servers
1. On the computer on which the Remote Agent is installed, on the taskbar, click Start
>All Programs >Symantec Backup Exec for Windows Servers > Backup Exec
Remote Agent Utility.
When the Remote Agent Utility is running, an icon appears in the system tray. You
can double-click this icon to view the utility.
919

The Remote Agent Utility for Windows Systems
2. Click the Publishing tab.
3. Complete the appropriate options as follows :
Enable the Remote
Agent to publish
information to the
media servers in the list
Check Enable the Remote Agent to publish information to the
media servers in the list to allow the remote agent to send
information about itself, such as its version and IP address, to all of
the media servers in the list. The media servers display the remote
agent in the backup selections tree, under Favorite Resources and
under Domains.
By default, the name of the media server that push-installed this
remote agent is displayed in this list. If the remote agent is also a
media server, the name is displayed as 127.0.0.1.
To stop the information from being sent to all of the media servers,
uncheck Enable the Remote Agent to publish information to the
media servers in the list. The list of media servers is preserved, but
the Remote Agent does not send any information about itself to the
media servers.
Publishing interval Specify an interval, in minutes, for the Remote Agent to send
information about its status to the media servers in the list. The
default interval is 240 minutes. This is the recommended setting to
appropriately balance system responsiveness with network traffic.
The maximum interval allowed is 720 minutes.
Add Click Add to add the media server name or IP address to the Media
server list.
Edit Select a name or address in the list, and then click Edit to make
changes.
Remove Select a name or address in the list, and then click Remove to
delete a media server name or IP address from the list. The Remote
Agent no longer publishes information to the media server. You
cannot select the remote computer for backup from the media
server’s Favorite Resources node.
920 Administrator’s Guide

Published names for
this agent
4. Click OK.
Appendix E, Symantec Backup Exec Remote Agent for Windows Systems
The Remote Agent Utility for Windows Systems
Displays the names that this remote computer is published as
under a media server’s Favorite Resources node. These names can
include:
◆ The fully qualified domain name.
◆ The computer name.
◆ The NetBIOS computer name.
◆ Virtual Service names, which are the names given to clustered
resources that are hosted by the remote computer.
◆ Oracle RMAN Real Application Cluster (RAC) name, which is
the virtual name used by computers in a RAC for the computer
that hosts the Oracle application. This name is displayed in a
media server’s backup selection list under the Oracle RAC node.
Related Topics:
“Installing the Remote Agent and the Advanced Open File Option to a remote computer
in the backup selections list” on page 99
“Viewing activity on the remote computer” on page 918
“About the Favorite Resources node” on page 318
“Adding a Windows system to the Favorite Resources node” on page 319
“Deleting a Windows system from the Favorite Resources node” on page 320
921

The Remote Agent Utility for Windows Systems
922 Administrator’s Guide

Appendix
Symantec Backup Exec
Remote Agent for NetWare
Systems
F
The Symantec Backup Exec Remote Agent for NetWare Systems (Remote Agent) is
installed as a separate, add-on component that must be used for the backup and restore
of remote NetWare resources. For information on protecting remote Windows
resources, see “Symantec Backup Exec Remote Agent for Windows Systems” on
page 913.
The Remote Agent allows network administrators for Windows servers to perform
backup and restore operations on NetWare servers that are connected to their network.
The Remote Agent supports NetWare 5.1, NetWare 6.0, and NetWare 6.5. Because the
Remote Agent is also a Client Access License (CAL), it enables you to fully protect your
NetWare data and to perform accelerated backups of NetWare data. You cannot select
data and special files on resources for a remote NetWare server for backup until a
Remote Agent has been installed.
The Remote Agent is a NetWare Loadable Module (NLM) installed on the NetWare
server. The Remote Agent provides faster backups by locally performing tasks that in
typical backup technologies require extensive network interaction. For example, instead
of waiting for requests and data packets to be sent between the NetWare server and the
media server each time a file is selected for backup, the Remote Agent processes backup
data into continuous streams that use Novell’s Storage Management Services (SMS) and
that the media server then processes as a single task. The Remote Agent is fully Novell
SMS-compliant.
Related Topics:
“Requirements for installing the Remote Agent for NetWare Systems on a NetWare
server” on page 924
“About installing the Remote Agent for NetWare Systems on a NetWare server” on
page 924
923

Requirements for installing the Remote Agent for NetWare Systems on a NetWare server
“About backing up NetWare servers” on page 927
“About backing up NetWare servers” on page 927
“Setting default options for the Remote Agent for NetWare Systems” on page 933
“About backing up the NetWare Directory Services (NDS)” on page 928
Requirements for installing the Remote Agent for NetWare
Systems on a NetWare server
The following are required to install the Remote Agent on a NetWare server:
■ The Backup Exec for Windows Servers media server must have network access via
the TCP/IP protocol to the remote NetWare server.
■ The computer from which the installation program is running must be able to access
the NetWare server.
■ You must have administrative privileges on the NetWare server on which the agent
is being installed.
Related Topics:
“About backing up NetWare servers” on page 927
“About installing the Remote Agent for NetWare Systems on a NetWare server” on
page 924
“About backing up NetWare servers” on page 927
“Setting default options for the Remote Agent for NetWare Systems” on page 933
“About backing up the NetWare Directory Services (NDS)” on page 928
About installing the Remote Agent for NetWare Systems on a
NetWare server
When you install the Remote Agent on the NetWare server, the following occurs:
■ A directory called BKUPEXEC is created in the SYS: volume, and the latest tested
versions of the NLMs needed by Backup Exec to process NetWare-specific requests
are copied to the BKUPEXEC/NLMS directory.
■ The BESTART.NCF and BESTOP.NCF files are created and placed in the
SYS:SYSTEM directory. These files contain commands to load the appropriate NLMs
that allow the NetWare server to be backed up.
924 Administrator’s Guide

About installing the Remote Agent for NetWare Systems on a NetWare server
Note The Remote Agent is installed remotely from the Windows media server.
If you have previously installed the Remote Agent on NetWare servers, run
BESTOP from each NetWare console before installing the Remote Agent on those
servers again.
For instructions on installing the Remote Agent on NetWare servers, see “Installing
Backup Exec options to remote computers” on page 92.
When Backup Exec is installed, the TCP/IP protocol is selected for use by default.
However, you can change the default settings through the Options-Network and
Security dialog box. For more information, see “Setting default options for the Remote
Agent for NetWare Systems” on page 933.
Related Topics:
“Installing Backup Exec options to remote computers” on page 92
“Adding BESTART to the Autoexec.ncf file on the NetWare server” on page 926
Publishing NetWare servers to the NetWare agents list
In order for Backup Exec to display a NetWare server in the NetWare Agents list, the
agent must either publish its existence or you must manually add the servers running
the Remote Agent.
Running BESTART at the NetWare server automatically loads Novell’s SMDR.NLM
component, which publishes the availability of the server for backups using the TCP/IP
protocol. This protocol must be enabled on the network and in Backup Exec’s Network
and Security dialog box in order for the servers to be automatically added to the
NetWare Agents list. To access the Network and Security dialog box, click Tools, then
click Options, and then click Network and Security.
If your network cannot run this protocol, you must manually add the NetWare server
names to Backup Exec’s server list. For information about manually adding NetWare
servers, see “Setting default options for the Remote Agent for NetWare Systems” on
page 933.
If you are manually adding a NetWare server to the Backup Exec User-defined Selections
node, you must do one of the following:
■ Configure name resolution for your network.
■ Publish the NetWare servers on which the Remote Agent is installed on the media
server. To configure publishing, you must edit the ADVRTMS.DAT file on each
NetWare server you want to protect.
Appendix F, Symantec Backup Exec Remote Agent for NetWare Systems
925

About installing the Remote Agent for NetWare Systems on a NetWare server
To edit the Advrtms.dat file
1. On the NetWare server that you want to back up, navigate to the Remote Agent for
NetWare Systems installation directory.
2. With a text editor, open the Advrtms.dat file.
3. Add the NetWare server’s IP address.
4. Save the Advrtms.dat file.
Related Topics:
“Adding BESTART to the Autoexec.ncf file on the NetWare server” on page 926
Adding BESTART to the Autoexec.ncf file on the NetWare server
After installing the Remote Agent on the NetWare server, you should load the latest
Novell patches. You can also add the BESTART command, which loads the Remote Agent
whenever the server is booted, to the Autoexec.ncf file.
To edit the NetWare server’s Autoexec.ncf file
1. Add the command BESTART as the last line in the Autoexec.ncf file so that the
Remote Agent is automatically started each time the NetWare server is booted.
2. After saving the Autoexec.ncf file, reboot the NetWare server in order for the
changes to take effect.
Related Topics:
“Unloading the Remote Agent for NetWare Systems” on page 926
Unloading the Remote Agent for NetWare Systems
If you added BESTART as the last line in the Autoexec.ncf file on the NetWare server,
the Remote Agent is automatically loaded whenever the Autoexec.ncf file is executed on
the NetWare server. You can unload it by typing a command.
To unload the Remote Agent
1. At the NetWare server’s console prompt, type:
bestop
926 Administrator’s Guide

2. Press ENTER.
All NLMs associated with the Agent will be unloaded.
Related Topics:
“About backing up NetWare servers” on page 927
About backing up NetWare servers
Appendix F, Symantec Backup Exec Remote Agent for NetWare Systems
About backing up NetWare servers
The first time you access the NetWare servers for backup, you may be prompted for a
username and password. The usernames and passwords you enter to gain initial access
to remote servers and workstations are kept in a password database. This database
prevents you from having to type usernames and passwords each time you need to
access remote devices and also allows Backup Exec to log on to servers and attach to
agent workstations for unattended jobs.
To back up the NetWare file system, you must have an account on the NetWare server
with the following rights:
Necessary rights for NFS backup
To do this: You need these rights:
Backup Read files
File scan
Modify file attributes
Access control
Restore Write files
Create files
File scan
Modify file attributes
Access control
Archive Read files
File scan
Modify file attributes
Erase files
927

About backing up NetWare servers
To back up, and restore when necessary, the NDS Tree, you must have a user account on
the NetWare server that has the following rights to the [Root] object of the NDS Tree:
Necessary rights for NDS backup
To do this: You need these rights:
Backup/
Restore
Object rights
Supervisor
Browse
Create
Delete
Rename
Inheritable
Property rights, All properties
Supervisor
Compare
Read
Write
Add Self
Inheritable
Note White check boxes for these rights will display with black check marks in the
Trustees of [Root] dialog box. With default rights only, these check boxes will be
gray with gray check marks.
Related Topics:
“Backing up NetWare servers” on page 930
“Setting default options for the Remote Agent for NetWare Systems” on page 933
About backing up the NetWare Directory Services (NDS)
Novell strongly recommends using replication to provide the first line of protection for
NDS in a multi-server installation. Additionally, the NDS database should still be backed
up on a regular basis in case it is needed to replace objects that have been accidentally
deleted.
Note that if you have multiple servers in the NDS tree, the entire NDS can be backed up
from any of those servers. There is no need to back up all of NDS from all of the NDS
TSAs in the tree unless you are doing it for redundancy purposes.
Depending on your environment (single-server, multi-server, single administrator, or
multi-administrator), you must perform replication of partitions and backups to provide
protection for NDS. Following are some backup strategies that can be applied:
■ Single-server strategy. NDS installations that consist of a single network server
must rely completely on Backup Exec for Windows Servers to provide protection for
the directory database, since the built-in replication feature cannot be used.
928 Administrator’s Guide

Appendix F, Symantec Backup Exec Remote Agent for NetWare Systems
About backing up NetWare servers
You should back up the entire NDS database whenever any type of backup (either
full or modified) is performed. If the NDS database rarely changes, that is, if the
objects stored within and/or their properties and values are seldom modified, then
less frequent backups may be performed.
As with file system backups, the administrator must consider what might be lost if a
disaster occurs on the day the next full backup is to be performed. Be sure to figure
in the time it will take to rebuild the changes to the directory manually, if just such a
disaster were to occur.
■ Single administrator - multiple servers strategy. NDS installations that have a single
network administrator (a single object with supervisor rights to the entire directory
database), and multiple servers should rely almost entirely on the built-in
replication features of NDS for fault tolerance. If a disaster occurs on a specific
server, NDS remains intact and available from replicas stored on other servers.
When the failed server is repaired, NDS is reinstalled using Novell’s INSTALL NLM
on NetWare 4.1 and NWCONFIG.NLM on NetWare 5.x and later. Replicas are then
placed back onto the server, if required.
The NDS database should still be backed up regularly in case it is needed to replace
objects that have been accidentally deleted.
■ Multiple administrator strategy. NDS installations that have multiple network
administrators, each with access to only a portion of the directory tree, are faced
with additional challenges when designing a backup strategy. Within this type of
installation, it is rare that an object has full rights to the entire directory tree, as is
the case with many smaller- to medium-sized networks.
Instead, the tree is logically broken into smaller components. For example,
partitions with specific administrators assigned the responsibility to manage each
component. While this type of installation offers the highest level of network
security, it brings with it the most complicated level of disaster recovery.
The best method for implementing fault tolerance should remain partition
replication. Because it is likely that Inherited Rights Filters (IRFs) will be applied at
the container level, a properly replicated directory offers a much quicker
restoration in the event of a disaster. If possible, you should create an object that has
full rights as a trustee of the root of the NDS tree, and perform full backups on the
NDS tree, instead of partial backups. Doing so reduces the complexity of rebuilding
NDS in the event of a disaster.
You should refer to your Novell documentation for more information on configuring
and managing NDS replicas and partitions.
Related Topics:
“About backing up NetWare servers” on page 927
“Backing up NetWare servers” on page 930
929

About backing up NetWare servers
“Setting default options for the Remote Agent for NetWare Systems” on page 933
Backing up NetWare servers
Backup Exec does not support backing up double-byte character sets for NetWare
servers that have a double-byte code page loaded.
Full, differential, and incremental jobs that specify using the modified time reverts to
using the archive bit for NetWare servers included in the job.
To back up a NetWare server
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
Backup selections
3. Double-click Favorite Resources.
4. Double–click NetWare Agents.
5. Double-click the NetWare computer icon for the NetWare server you want to back
up.
930 Administrator’s Guide

Appendix F, Symantec Backup Exec Remote Agent for NetWare Systems
About backing up NetWare servers
When logging on to the NetWare server, you may need to provide a fully
distinguished and typeless name, such as .admin.novell.
A fully distinguished, or complete, name consists of different object types, such as
common name (CN), Organizational Unit (OU) objects, and Organization (O) objects.
When the abbreviations for these objects are not included as part of the object’s
complete name, the naming is referred to as a typeless name. For more information
about complete, partial, typeful, or typeless names, refer to your Novell NetWare
documentation.
6. Check the check box preceding the volume icon to select the directories that you
want to back up, or double-click the volume to select directories.
NetWare File System and NetWare Directory Services (Novell Directory) are listed
separately. Each directory that you want to back up must be selected.
The following screen shows a NetWare server (BOBG_NW5) that has both the file
system and the NetWare Directory Services selected for backup:
Backup selections for NetWare server
7. If you want to change the backup default, on the Properties pane, under Settings,
click NetWare SMS.
8. Select or clear the Back up compressed files in decompressed form option. If you
select this option, Backup Exec decompresses, or expands, compressed files as they
are backed up. If you select this option, the server may run out of memory or disk
space. Also, the backup job will take longer due to the extra time involved in file
decompression.
9. Continue creating the job by following the procedures in “Creating a backup job by
setting job properties” on page 349.
Related Topics:
“About restoring NetWare servers” on page 932
“Restoring NetWare servers” on page 932
931

About restoring NetWare servers
About restoring NetWare servers
Before restoring your NetWare server, you may want to read about restore operations in
general in “Restoring data” on page 483.
If you have more than one server in the NDS tree, it is not necessary to restore NDS since
a replica should be available from another server. The only time an NDS restore
operation needs to be done is to replace objects that have been deleted accidentally.
Because information about partitions and replicas would probably change between a
backup of NDS and any subsequent restores, this information is not saved by SMS when
a backup of NDS is performed. Thus, when NDS is backed up, it appears as though all
objects are stored in a single partition.
However, if information about partitions is available when the restore operation is
performed, objects are restored to the proper partition.
Related Topics:
“Restoring NetWare servers” on page 932
Restoring NetWare servers
To restore NetWare servers
1. On the navigation bar, click the arrow next to Restore.
1. Click New Restore Job.
2. Select the data you want to restore. For details on how to select data, see “Selecting
data to restore” on page 508.
3. If you want to change the Restore option default, on the Properties pane, under
Settings, click NetWare SMS.
4. Select or clear the Restore volume restriction option. If you select this option,
Backup Exec restores NetWare volume restrictions. Restoring volume restrictions is
not recommended unless you are performing disaster recovery.
5. (Optional) If you want to redirect the restore to another server, under Destination,
click File Redirection and complete the options.
If you restore NetWare data to a Windows volume, trustee data associated with the
files is not restored. If the file was compressed by NetWare and was backed up in a
compressed format, you cannot restore it to a Windows volume.
932 Administrator’s Guide

Appendix F, Symantec Backup Exec Remote Agent for NetWare Systems
Setting default options for the Remote Agent for NetWare Systems
If you are redirecting a restore operation, note the following:
■ Only data can be included in a redirected restore operation; NDS objects cannot
be redirected.
■ Data backed up from a Novell server can be restored to a Windows volume; again,
NDS objects cannot be redirected.
6. Complete the restore job by following the procedures described in “Restoring data by
setting job properties” on page 488.
If you clear the Preserve tree option on the General Restore Job Properties and the
target directory is the volume root, Backup Exec will still use the Preserve tree option
and data will still be restored with its original directory intact.
Related Topics:
“Setting default options for the Remote Agent for NetWare Systems” on page 933
“Saving configuration information for the NetWare server” on page 935
Setting default options for the Remote Agent for NetWare
Systems
By default, Backup Exec detects NetWare servers that are publishing using the TCP/IP
protocol. If these protocols are made unavailable, the NetWare remote agents are not
detected and the NetWare Agents node does not appear under Favorite Resources in the
backup selections tree.
Note If a protocol is not installed on the system, it will not be available in this dialog.
For example, if the TCP/IP protocol is not installed on the media server, the TCP/IP
protocol check box is grayed out and made unavailable.
You can also set network defaults for all backup and restore operations performed on the
NetWare servers by Backup Exec, including specifying a dynamic port range to be used
by the remote agent. You can override some of these defaults each time you create a
backup or restore job.
To specify TCP dynamic port ranges on the media server
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Network and Security.
933

Setting default options for the Remote Agent for NetWare Systems
3. Specify a TCP dynamic port range by clicking Enable remote agent TCP dynamic
port range and enter the port ranges.
4. Click OK.
5. Restart Backup Exec.
To change backup and restore defaults for the NetWare server
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click NetWare SMS.
3. Select the appropriate options as follows:
4.
Display the following
servers
Back up compressed files
in decompressed form
Restore volume
restrictions
Backup Exec checks the registry for a list of NetWare servers. If
the list does not exist, Backup Exec creates it using the wildcard
(*) default so that all servers that are published using the Service
Location Protocol (TCP/IP protocol) can be seen. Backup Exec
displays these servers in this field.
If you add a server name to this list, Backup Exec must be able to
resolve the name to a TCP/IP address. If Backup Exec cannot
resolve the name to a TCP/IP address, the server name appears in
the server list, but Backup Exec is unable to connect to it. Backup
Exec will be able to resolve the name if the NetWare server names
and IP addresses are in your network’s Domain Naming Services
(DNS) database. If these names and IP addresses are not in DNS,
you must manually add the names and IP addresses to the media
server’s HOSTS file, which usually is found in the
\WINDOWS\SYSTEM 32\Drivers\ETC directory.
For these changes to take effect, you must restart the Backup
Exec administration console.
Click this to decompress, or expand, compressed files as they are
backed up. If you select this option, the server may run out of
memory or disk space. Also, the backup job will take longer due to
the extra time involved in file decompression.
In most cases, this option should not be selected.
Click this to restore NetWare volume restrictions. Restoring
volume restrictions is not recommended unless you are
performing a disaster recovery job.
934 Administrator’s Guide

To manually add a server to the server list:
■ Click Add.
Appendix F, Symantec Backup Exec Remote Agent for NetWare Systems
Saving configuration information for the NetWare server
■ Type the name of the server you want to add, and then click OK.
To delete a server from the server list:
■ Select the server you want to delete.
■ Click Delete.
5. After all servers have been added or deleted, and the NetWare SMS default options
have been selected, click OK.
Related Topics:
“Saving configuration information for the NetWare server” on page 935
“Disaster recovery of NetWare servers” on page 936
Saving configuration information for the NetWare server
Use the Bediag.nlm utility to create an ascii file called Bediag.fax that includes useful
configuration information for your server.
Keep a copy of the Bediag.fax available so that if you have to contact Technical Support,
you can quickly provide system configuration information.
To create the Bediag.fax file
1. At the NetWare system console prompt, type:
load SYS:BKUPEXEC/NLMS/BEDIAG
The Bediag.fax file is created.
You can use the following options when loading Bediag.nlm: (for example, load
bediag /c)
/c - outputs the file to the screen
/s - gathers information for SCSI devices only
/n - exclude information for SCSI devices
2. View the Bediag.fax file with a text editor or word processor.
The information in this file includes:
■ The contents of your Config.sys and Autoexec.bat files.
■ Contents of the Startup.ncf file.
935

Disaster recovery of NetWare servers
■ The amount of memory available.
■ The contents of your Autoexec.ncf file.
■ A listing of the NLMs that are currently loaded on your server, including the
version numbers and the date stamp.
■ Configuration settings for your server, including volumes and individual
namespace support.
3. On the print-out of the Bediag.fax, write the Supervisor user and password.
Keep this print-out locked in a safe place.
Related Topics:
“Disaster recovery of NetWare servers” on page 936
Disaster recovery of NetWare servers
To manually recover NetWare servers if a disaster occurs, you must:
■ Reinstall NetWare.
■ Reinstall the Remote Agent.
■ Use the information from BEDIAG.FAX to restore your server configuration.
■ Restore your latest backups.
Intelligent Disaster Recovery for NetWare is available as a separate add-on option to
Backup Exec for NetWare Servers. For more information, see the Symantec Backup
Exec for NetWare Servers Administrator’s Guide.
Related Topics:
“About backing up NetWare servers” on page 927
“About restoring NetWare servers” on page 932
936 Administrator’s Guide

Appendix
Symantec Backup Exec
Remote Agent for Linux or
Unix Servers
G
The Symantec Backup Exec for Windows Servers Remote Agent for Linux or Unix
Servers (Remote Agent) is installed as a separate, add-on component that enables
Windows Server network administrators to perform backup and restore operations on
Linux and UNIX hosts that are connected to the network. This agent must be running on
these computers before backup or restore operations can be performed.
After the agent is configured, the Linux and UNIX host computers are ready for backup.
When backing up data using the Remote Agent, Backup Exec enables you to protect data
using multiple backup types. These include:
■ Full
■ Differential - Using modified time
■ Incremental - Using modified time
■ Working set
Only full backups are supported with the Remote Agent when using the Backup Wizard.
Selecting any other method of backup through the Backup Wizard will still result in a
full backup being performed. To specify differential or incremental backups using
modified time, make the selection from the backup properties window.
Related Topics:
“Requirements for the Remote Agent for Linux or UNIX Servers” on page 938
“Installing Remote Agent for Linux or Unix Servers using the SSH (Secure Shell)
protocol” on page 943
“About protecting Novell Open Enterprise Server components on SUSE Linux Enterprise
Server” on page 949
937

Requirements for the Remote Agent for Linux or UNIX Servers
“Creating a Linux or UNIX logon account” on page 946
Requirements for the Remote Agent for Linux or UNIX Servers
The following platforms and file systems are supported:
Supported platforms and file systems
Platform File system Architecture
HP-UX 11.11i,
HP-UX 11.11.i v 2
Red Hat Enterprise
Linux (RHEL) 3, 4
SuSE Linux Enterprise
Server (SLES) 9, 10
Novell Open
Enterprise Server 1.0
with SP1
SuSE Linux
Professional 9
Note For the latest supported platforms, see the Symantec Software Compatibility List
on the Symantec Support web site.
The following should be in place before you install the Remote Agent:
■ Root privileges are required on Linux and UNIX hosts in order to install the Remote
Agent for Linux or Unix Servers.
■ Access to a mounted CD-ROM drive.
HFS, VxFS PA-RISC
ext2, ext3, VxFS i386, x86_64
ext2, ext3, VxFS, Reiser i386, x86_64
ext2, ext3, VxFS, Reiser, NSS i386
ext2, ext3, VxFS, Reiser i386
Solaris 8, 9, 10 VxFS, UFS SPARC
Miracle Linux 3, 4 ext2, ext3, VxFS, Reiser i386
Red Flag Linux 4.1, 5 ext2, ext3, VxFS, Reiser i386
■ TCP/IP, which is used for communication with the UNIX host computers, is required
on the media server.
938 Administrator’s Guide

Appendix G, Symantec Backup Exec Remote Agent for Linux or Unix Servers
Installing the Remote Agent for Linux or UNIX Servers
Caution If the Backup Exec 8.x and 9.x Agent for UNIX is installed on a UNIX host, and
you are installing the Remote Agent on the same host, you must disable the
existing Backup Exec 8.x and 9.x Agent for UNIX before installing the Remote
Agent. Otherwise, the Remote Agent will not run properly after it is installed.
For information on disabling or enabling either of the agents, see “The Remote
Agent for Linux and Unix Servers and the Backup Exec 8.x and 9.x Agent for
UNIX” on page 955.
Related Topics:
“Installing the Remote Agent for Linux or UNIX Servers” on page 939
“Installing Remote Agent for Linux or Unix Servers using the SSH (Secure Shell)
protocol” on page 943
“Creating a Linux or UNIX logon account” on page 946
“Backing up Linux and UNIX servers” on page 947
“Requirements for Novell Open Enterprise Server” on page 949
“Backing up OES components” on page 950
“Restoring Novell OES components” on page 951
“Restoring Novell OES components” on page 951
“Manually uninstalling the Remote Agent for Linux or Unix Servers” on page 953
Installing the Remote Agent for Linux or UNIX Servers
See the following topics when installing the Remote Agent for Linux or UNIX Servers on
Linux and UNIX hosts.
■ To install the Remote Agent from the Backup Exec for Windows Servers CD, see
“Installing Remote Agent for Linux or Unix Servers by using the installation script”
on page 940.
■ To install the Remote Agent using the SSH protocol, see “Installing Remote Agent for
Linux or Unix Servers using the SSH (Secure Shell) protocol” on page 943.
■ To manually uninstall the Remote Agent, see “Manually uninstalling the Remote
Agent for Linux or Unix Servers” on page 953.
■ To manually start the Remote Agent daemon, see “Manually starting the Remote
Agent for Linux or Unix Servers” on page 954.
939

About creating the beoper group
Related Topics:
“Installing Remote Agent for Linux or Unix Servers using the SSH (Secure Shell)
protocol” on page 943
“Manually uninstalling the Remote Agent for Linux or Unix Servers” on page 953
About creating the beoper group
To back up and restore Linux and UNIX hosts, the beoper group must exist on each host
or in the NIS domain’s group file. The Remote Agent installer by default will create the
beoper group and add root as a member if a NIS server is not detected. The group must
be created manually if the host machine is a member of a NIS domain.
Caution If the beoper group is not created by the Remote Agent installer or is not
created manually, connections to the hosts from the Backup Exec media
server will fail.
When creating the group manually, do the following at each Linux and UNIX host where
the Remote Agent will be installed. For hosts that are members of a NIS domain, refer to
the NIS documentation for information on adding groups to a NIS domain.
■ Create the group beoper. When creating the group, use lowercase letters.
■ After creating the beoper group, add all users to the group that should be granted
rights to protect the Linux and UNIX hosts with Backup Exec.
For more information on creating groups, see your Linux and UNIX system
documentation.
Related Topics:
“Publishing Linux and UNIX hosts to a media server” on page 944
“About editing the ralus.cfg file” on page 945
“About ralus.cfg format components” on page 945
“Creating a Linux or UNIX logon account” on page 946
Installing Remote Agent for Linux or Unix Servers by using the
installation script
The Remote Agent for Linux or UNIX Servers installation script is capable of installing
the agent to both local and remote Linux and UNIX based computers (hosts).
940 Administrator’s Guide

Installing Remote Agent for Linux or Unix Servers by using the installation script
It is recommended that you install the software from a Linux or UNIX host using the
Backup Exec for Windows Servers CD and the push installation technology built into the
installation script. Installing the agent in this manner enables you to install it on
multiple remote Linux and UNIX hosts in the least amount of time possible. You can also
take the Backup Exec for Windows Servers CD to the target hosts and locally install the
software. In either case, you need to know the computer names of the Linux and UNIX
hosts where the software will be installed.
Caution If the Backup Exec 8.x and 9.x Agent for UNIX is installed on a UNIX host, and
you are installing the Remote Agent on the same host, you must change the
existing agent name in the Backup Exec 8.x and 9.x Agent for UNIX
configuration file, agent.cfg, before installing the Remote Agent. Otherwise,
the Remote Agent will not run properly after it is installed.
Modify the agent name in the configuration parameter, Name in
/etc/bkupexec/agent.cfg to any name besides the name you are using.
After modifying the name, save the agent.cfg file and then run the Remote
Agent installer.
To install the Remote Agent on Linux and UNIX hosts
1. At a Linux or UNIX host, place the Backup Exec for Windows Servers CD in the
CD-ROM drive.
2. Logon to the target computer with root privileges.
3. Navigate to Remote Agent for Linux or UNIX Servers installer on the Backup Exec
CD using the following path: /
4. At the command prompt, type the following command:
./installralus.
5. Type the name of a Linux or UNIX host on which to install the Remote Agent and
press Enter. When typing multiple host names, use spaces between each name.
6. After the installer successfully checks for a valid Linux or UNIX host operating
system during the initial system check, press Enter.
7. After reviewing the package installation summary, press Enter.
8. Press Enter to start the Remote Agent installation requirements precheck.
Appendix G, Symantec Backup Exec Remote Agent for Linux or Unix Servers
941

Installing Remote Agent for Linux or Unix Servers by using the installation script
If you are running the Backup Exec 8.x and 9.x Agent for UNIX, a message appears
informing you that the Backup Exec 8.x and 9.x Agent for UNIX will be disabled, but
not uninstalled. Press ENTER to disable the Backup Exec 8.x and 9.x Agent for UNIX
and continue with the install process. If you do not want to disable the Backup Exec
8.x and 9.x Agent for UNIX, the Remote Agent installer will terminate and exit and
the Remote Agent will not be installed.
9. Press Enter after the Remote Agent installer installation requirements check
completes.
10. Type the host name or IP address of the Backup Exec media server that you want the
Remote Agent to publish to and press Enter. If you need to specify additional media
servers, type Y and then press Enter; otherwise press Enter.
11. Verify that the IP address and/or hostname information is correct and press Enter.
If changes need to be made, type N then press Enter to modify the information.
12. Read the beoper group requirement and then press Enter.
13. To start the NIS server scan, press Enter.
14. Examine the results of the NIS server scan. If a NIS server is detected the Remote
Agent installer is unable to create the beoper group and it must be done manually. If
no NIS server is detected press Enter to have the installer scan for the beoper group
and root membership.
15. If no beoper group is found, press Enter to have the installer create the group or
type N and then press Enter to create the group manually after the installation.
16. Press Enter to have the installer select the next available Group ID (GID) or type Y
and then press Enter to specify a GID.
17. Press Enter to have the root user added as a member to the beoper group. To
manually add the account, type N and then press Enter.
18. Press Enter to begin the installation.
A message appears stating the installation has completed successfully after the
installation finishes.
19. Press Enter.
20. The installralus log file is saved to the following location on the host:
/var/tmp/vxif/installralus/installralus.log
942 Administrator’s Guide

Installing Remote Agent for Linux or Unix Servers by using the installation script
Related Topics:
“Publishing Linux and UNIX hosts to a media server” on page 944
“About editing the ralus.cfg file” on page 945
“About ralus.cfg format components” on page 945
“Creating a Linux or UNIX logon account” on page 946
Installing Remote Agent for Linux or Unix Servers using the SSH
(Secure Shell) protocol
By default, the Remote Agent installer uses RSH (Remote Shell) when remotely
installing the Remote Agent. Symantec recommends that you use SSH (Secure Shell)
instead. To remotely install the Remote Agent using the SSH protocol, the following
steps must be performed to enable temporary SSH trust relationships between the
computers involved.
To install the Remote Agent using the SSH protocol
1. On the SSH client computer from where the Remote Agent agent is being installed,
run the following command:
ssh-keygen -b 1042 -t dsa
2. Accept the defaults, including no passphrase.
An ssh key for the computer is created in the file /.ssh/id_dsa.pub
3. On each remote computer where you want to install the Remote Agent agent, check
to see if a /.ssh/authorized_keys2 file exists.
4. Do one of the following:
■ If the file does not exist, copy the /.ssh/id_dsa.pub file on the ssh client to
/.ssh/authorized_keys2 on each ssh server system.
■ If the file does exist, create a backup of the /.ssh/authorized_keys2 file and
append the contents of the /.ssh/id_dsa.pub file to the original.
5. On each remote computer where you want to install the Remote Agent agent, verify
that the sshd_config file on each ssh server contains the uncommented keyword:
PubkeyAuthentication yes
The sshd_config file is usually located in /etc/ssh or /etc/opt/openssh.
Appendix G, Symantec Backup Exec Remote Agent for Linux or Unix Servers
943

Publishing Linux and UNIX hosts to a media server
6. If the keyword is not found or is set to no, add the keyword and restart sshd. An ssh
start/stop script should be located within /etc/init.d.
The client computer must issue one ssh command to each ssh server so that its key
fingerprint is received, and it becomes a known host. Successive ssh-issued
commands are answered without prompting for a password, passphrase, or
confirmation. You can now successfully run the Remote Agent install script using
the -usessh option. After the installation finishes, you can restore the backup copies
of /.ssh/authorized_keys2 on each server.
Related Topics:
“About creating the beoper group” on page 940
“Publishing Linux and UNIX hosts to a media server” on page 944
Publishing Linux and UNIX hosts to a media server
Linux and UNIX hosts must publish themselves to a Backup Exec media server before
you can back them up. To establish communications, the Remote Agent installation
program creates a configuration file named ralus.cfg on each Linux and UNIX host
where the Remote Agent is installed. This file contains IP information that Linux and
UNIX hosts use to publish themselves to a media server, where they appear in the
Linux/Unix Servers node in the backup selections tree.
A ralus.cfg configuration file also contains a list of Backup Exec media servers that you
want to use to back up a particular Linux and UNIX host. Since multiple media servers
can back up the same Linux and UNIX host, there is no limit to the number of media
servers that can be listed in the ralus.cfg file.
Backup Exec media server entries in the ralus.cfg file are entered using either the media
server name from a naming service provider such as DNS or NIS, or by using an IP
address.
Related Topics:
“About editing the ralus.cfg file” on page 945
“About ralus.cfg format components” on page 945
“About file and directory exclusions in ralus.cfg” on page 946
944 Administrator’s Guide

About editing the ralus.cfg file
Appendix G, Symantec Backup Exec Remote Agent for Linux or Unix Servers
Publishing Linux and UNIX hosts to a media server
You can add or delete media servers from the list of media servers found in a Linux or
UNIX host ralus.cfg file. Adding a media server to the list expands the number of media
servers that can back up the host, while deleting a media server removes it from the list
of media servers from which it can be backed up. You can also modify naming
information for a media server such as its DNS name or IP address.
A media server entry in a ralus.cfg file conforms to a specific format, which you must
follow to ensure a successful publish from the host to the media server.
Related Topics:
“About ralus.cfg format components” on page 945
“About file and directory exclusions in ralus.cfg” on page 946
About ralus.cfg format components
The ralus.cfg format contains three components. The first component (A) is a required
string.
The second component is a unique identifier followed by an equal sign (=). A unique
identifier can consist of sequential numbers, letters or alpha-numeric characters. For
example: 1, 2, 3 or A, B, C. You can also use AA, BB, CC, or A1, A2, B1, B2. Whatever
unique identifier you decide to use must be unique if you list multiple media servers in
the ralus.cfg file.
The third component of the ralus.cfg format is the actual media server IP address or its
naming-service accessible name. For example, a DNS name, hosts file name, or NIS
name. When entering this information, do not use spaces.
Ralus.cfg formatting example
A = Required string
B = Required and unique identifier (the order or appearance is irrelevant)
C = File or directory to be excluded
Editing a ralus.cfg file can be done using any Linux or UNIX text editor.
Related Topics:
“About editing the ralus.cfg file” on page 945
945

Creating a Linux or UNIX logon account
“About file and directory exclusions in ralus.cfg” on page 946
About file and directory exclusions in ralus.cfg
You may have files and directories on the Linux and UNIX hosts that you do not want to
back up. Rather than manually deselecting them when making backup selections, you
can enter file and directory exclusion information in the ralus.cfg file. After the
information is added, the file and directories are ignored and will not be backed up.
File and directory exclusions in the ralus.cfg file
A = Required string
B = Required and unique identifier (the order or appearance is irrelevant)
C = File or directory to be excluded
Related Topics:
“Creating a Linux or UNIX logon account” on page 946
“Backing up Linux and UNIX servers” on page 947
Creating a Linux or UNIX logon account
On initial access of the Linux and UNIX host, a Logon Account Selection screen appears
stating that the system logon account used by Backup Exec to access to the Linux and
UNIX host has failed, and that access to the UNIX or Linux host is denied. To proceed, a
new logon account must be created for the host using credentials that allow access to
the host.
Note The logon account credentials you provide during the creation of logon account
used during the initial access of the host are stored by Backup Exec. These
credentials will be used again when making future backup selections from the
Linux and UNIX host. However, if the access credentials for the host change, a new
Backup Exec Linux and UNIX host logon account will need to be created in order to
access the host.
Use the following steps to add logon credentials for the Linux and UNIX host.
946 Administrator’s Guide

To add logon credentials
Appendix G, Symantec Backup Exec Remote Agent for Linux or Unix Servers
Backing up Linux and UNIX servers
1. In Backup Job Properties pane under Favorite Resources, expand Linux/Unix
Servers.
2. Double-click the desired Linux or UNIX host.
A Logon Account Selection screen appears stating that the Backup Exec System
Logon Account failed to access the host.
3. On the Logon Account Selection screen, click New.
4. Add account credentials for the host and then click OK.
Credentials supplied for the Linux or UNIX host must have root privileges that can
be authenticated by the host.
User name The user name required to access the Linux or UNIX host. This
name must have root privileges, which can be authenticated by the
host.
Password The password used to access the host.
Confirm password The same password entered in the Password field, which is used to
confirm the password was entered correctly in the Password field.
Account name A label you enter to name the logon account.
Notes Pertinent notes about the account.
5. After authenticating the credentials entered, access to the host is granted and
backup selections can be made.
Related Topics:
“Backing up Linux and UNIX servers” on page 947
Backing up Linux and UNIX servers
After making backup selections, job properties for the Linux and UNIX host backup jobs
should be set. Job properties specifically targeted to Linux and UNIX backup jobs are
found in the Backup Job Properties pane under Linux, Unix, and Macintosh.
Use the following steps to set the backup job properties.
947

Backing up Linux and UNIX servers
To back up Linux and UNIX servers
1. After making backup selections from the UNIX or Linux host, from the Backup Job
Properties dialog box, under Settings, click Linux, Unix, and Macintosh. The
following options appear:
Preserve change time Use this option to prevent the Remote Agent from changing an
object’s (files and directories) attributes when a backup occurs.
Normally, during a backup, Backup Exec preserves an object’s last
access timestamp by resetting the last access timestamp to the
value before the backup occurred. When Backup Exec modifies the
objects’ last access timestamp, the Linux or UNIX operating system
internally updates the object’s “ctime.” An object’s ctime is the time
when an object’s attributes (permissions, timestamps, etc.) have
been modified. If the attributes are not changed by the Remote
Agent after a backup, the object’s ctime will not change. This option
does not affect object attributes set during restore operations.
Follow local mount
points
Follow remote mount
points
Back up contents of
soft-linked directories
Use this option to have Backup Exec follow local mount points
when backing up data. For more information on local mount points,
see your Linux or UNIX documentation.
Use this option to have Backup Exec follow remote mount points
when backing up data. For more information on remote mount
points, see your Linux or UNIX documentation.
Use this option to back up the contents of directories that are linked
using soft links.
Linux and UNIX computers use many soft-links, some of which may
point to parent directories. Selecting this option can result in
duplicate data being backed up to tape, and it can also cause backup
jobs to continue indefinitely.
This option can be useful in certain situations. For example, you
can use this option to back up a single directory that contains
soft-links to data you want backed up.
When this option is selected, the soft-links themselves are not
backed up but the data they point to is.
When this option is not selected, the soft-links are backed up, but
the data is not.
For more information on soft-linked directories, see your Linux or
UNIX documentation.
Lock remote files Use this option if the Remote Agent requires exclusive access to the
files on remote systems connected through Network File System
(NFS).
948 Administrator’s Guide

About protecting Novell Open Enterprise Server components on SUSE Linux Enterprise Server
Backup method for
eDirectory (Linux only)
2. Make the appropriate selections or use the default selections provided.
3. Click General in the Properties pane of the Backup Job Properties screen.
4. In the list box for Backup method for files, select Full - Back up files - Using modified
time rather than Full - Back up files - Using archive bit (reset archive bit), as the
concept of an archive bit is not valid in UNIX environments.
Related Topics:
“About protecting Novell Open Enterprise Server components on SUSE Linux Enterprise
Server” on page 949
“Restoring Novell OES components” on page 951
About protecting Novell Open Enterprise Server components
on SUSE Linux Enterprise Server
Symantec Backup Exec for Windows Servers supports backup and restore of the
following Novell Open Enterprise Server (OES) components:
■ Novell iFolder
■ Novell eDirectory
■ Novell Groupwise
■ Novell Storage Services (NSS)
Select a backup method for backing up eDirectory data. Selections
include Full Backup and Incremental - since last full or incremental.
Related Topics:
“Requirements for Novell Open Enterprise Server” on page 949
“Backing up OES components” on page 950
“Backing up Linux and UNIX servers” on page 947
Requirements for Novell Open Enterprise Server
Backup Exec requires the following to back up and restore the Novell Open Enterprise
Server:
■ Novell Open Enterprise Server with Service Pack 1
Appendix G, Symantec Backup Exec Remote Agent for Linux or Unix Servers
949

About protecting Novell Open Enterprise Server components on SUSE Linux Enterprise Server
■ The iFolder TSA must be enabled
■ The GroupWise TSA must be enabled
■ A local user that is part of the beoper group (eDirectory users are not supported)
Related Topics:
“Backing up OES components” on page 950
“Backing up Linux and UNIX servers” on page 947
Backing up OES components
To back up OES components
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the backup selections list, under Favorite resources, expand Linux/Unix Servers.
4. Double-click the Linux or UNIX host you want to back up.
A Logon Account Selection screen appears stating that the Backup Exec System
Logon Account failed to access the host.
5. Select a logon account to access the host, and then click OK.
6. Select the appropriate data to back up.
7. On the Properties pane, under Settings, click Linux, Unix, and Macintosh.
8. Select the appropriate backup options.
For information on Linux and UNIX backup options, see “Backing up Linux and
UNIX servers” on page 947.
9. If you are backing up eDirectory data, select a backup method under the heading
Novell OES.
10. Click Run Now.
Related Topics:
“Backing up Linux and UNIX servers” on page 947
“Setting Linux/Unix properties for Remote Agent restore jobs” on page 951
950 Administrator’s Guide

Restoring Novell OES components
To restore Novell OES components
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
4. In the restore selections list, select the appropriate data to restore.
Appendix G, Symantec Backup Exec Remote Agent for Linux or Unix Servers
Restoring Novell OES components
5. On the Properties pane, under Settings, click Linux, Unix, and Macintosh.
6. Select the appropriate Linux/UNIX restore options.
For information on Linux/UNIX restore options, see “Setting Linux/Unix properties
for Remote Agent restore jobs” on page 951.
7. Click Run Now.
Related Topics:
“Restoring Novell OES components” on page 951
Setting Linux/Unix properties for Remote Agent restore jobs
This procedure details how to select restore job properties for Linux and UNIX servers,
and provides definitions for Linux and UNIX-specific restore options. For details on how
to create a restore job, and for definitions of all other restore options see “Restoring data”
on page 483.
When restoring Novell OES components, the entire Novell NDS database is first restored
to a set of on-disk DIB files. After the NDS database is restored to the DIB file set, the
NDS database is taken offline. The DIB files are then renamed to NDS, which overwrites
the offline NDS database with the contents of the DIB file set.
951

Uninstalling the Remote Agent for Linux or Unix Servers
To set restore properties for Linux and UNIX servers and Novell OES components
❖ After making backup selections from the UNIX or Linux host, from the Restore Job
Properties dialog box, under Settings, click Linux, Unix, and Macintosh. The
following options appear:
Lock remote files Use this option if the Remote Agent requires exclusive access to
the files on remote systems connected through Network File
System (NFS).
Restore DIB set Check the check box to activate the restore of the Novell Directory
Services database.
Activate DIB after verify Select this option to have Backup Exec rename the database to
NDS after the verification process completes successfully.
Open database when
finished
Verify database after
restore
Roll forward log
directory
Related Topics:
“Restoring Novell OES components” on page 951
Uninstalling the Remote Agent for Linux or Unix Servers
The Remote Agent for Linux or UNIX Servers installer is capable of uninstalling the
agent from both local and remote UNIX hosts.
To uninstall the Remote Agent for Linux or UNIX Servers
1. At a UNIX host, place the Backup Exec for Windows Servers CD in a CD-ROM drive.
2. Logon to the target computer with root privileges.
Select this option to have Backup Exec open the database after the
restore completes.
Select this option to verify the database after the restore
completes
Specify the location of the roll forward log directory
Leave backup file on disk Select this option to keep the Novell DIB file set on the hard drive.
952 Administrator’s Guide

Appendix G, Symantec Backup Exec Remote Agent for Linux or Unix Servers
Manually uninstalling the Remote Agent for Linux or Unix Servers
3. Navigate to Remote Agent for Linux or Unix Servers uninstaller on the Backup Exec
CD using the following path:
/uninstallralus
4. At the command prompt, type the following command:
uninstallralus
5. Enter the name of a UNIX host or hosts on which to uninstall the Remote Agent and
press Enter. When entering multiple host names, use spaces between each name.
6. Press Enter after the Remote Agent package check completes successfully.
7. Press Enter when prompted, Are you sure you want to uninstall RALUS
packages? [y,n,q] .
The removal of the Remote Agent for Linux or UNIX Servers begins. A message
appears stating the removal process has completed successfully, after the uninstaller
finishes.
8. Press Enter.
The uninstallation summary, and uninstallralus log files are saved to the following
locations on the UNIX host:
Uninstallation summary:
/opt/VRTS/install/logs/uninstallralus.summary
Uninstallralus log:
/opt/VRTS/install/logs/uninstallralus.log
After the log files are saved, the Remote Agent for Linux or UNIX Servers uninstall is
complete.
Related Topics:
“Manually uninstalling the Remote Agent for Linux or Unix Servers” on page 953
Manually uninstalling the Remote Agent for Linux or Unix
Servers
In some cases, you may want to manually uninstall the Remote Agent. Or you may want
to manually start and stop the Remote Agent daemon. This section guides you through
the steps required to run these manual processes.
953

Manually starting the Remote Agent for Linux or Unix Servers
To manually uninstall the Remote Agent for Linux or Unix Servers
1. Connect to the target UNIX host as the root user using a terminal session.
2. Stop the Remote Agent daemon.
3. Change to the /opt/VRTSralus/bin directory.
4. Execute the VRTSralus.service-uninstall script to remove the Remote Agent
daemon initialization files.
■ On HP-UX systems, the following line must be manually removed from the
/etc/inittab file:
/opt/VRTSralus/bin/VRTSralus.init.
5. Remove all the Remote Agent files from the UNIX host using the following
command:
rm -r /etc/VRTSralus /opt/VRTSralus /var/VRTSralus
Related Topics:
“Manually stopping the Remote Agent for Linux or Unix Server daemon” on page 954
Manually starting the Remote Agent for Linux or Unix Servers
To manually start the Remote Agent for Linux or Unix Servers daemon
1. Connect to the target UNIX host as the root user using a terminal session.
2. Issue the following startup command:
/etc/init.d/VRTSralus.init start
Related Topics:
“Manually stopping the Remote Agent for Linux or Unix Server daemon” on page 954
Manually stopping the Remote Agent for Linux or Unix Server
daemon
Use the following steps to manually stop the Remote Agent daemon.
954 Administrator’s Guide

The Remote Agent for Linux and Unix Servers and the Backup Exec 8.x and 9.x Agent for UNIX
To manually stop the Remote Agent for Linux or Unix Servers daemon
1. Connect to the target UNIX host as the root user using a terminal session.
2. Type the following stop command:
/etc/init.d/VRTSralus.init stop
Related Topics:
“The Remote Agent for Linux and Unix Servers and the Backup Exec 8.x and 9.x Agent
for UNIX” on page 955
“Troubleshooting the Remote Agent for Linux or Unix Servers” on page 956
The Remote Agent for Linux and Unix Servers and the Backup
Exec 8.x and 9.x Agent for UNIX
Both the Backup Exec 8.x and 9.x Agent for UNIX and the Remote Agent can be installed
together on the same host, but only one can be running at one time. If you are manually
installing the Remote Agent and the Backup Exec 8.x and 9.x Agent for UNIX is already
installed, the Backup Exec 8.x and 9.x Agent for UNIX must be disabled. After disabling
the Backup Exec 8.x and 9.x Agent for UNIX, proceed with the manual Remote Agent
installation.
Use the following steps to disable/enable the Backup Exec 8.x and 9.x Agent for UNIX.
To disable the Backup Exec 8.x and 9.x Agent for UNIX
1. On the UNIX host, kill all processes named agent.be.
2. Rename the Backup Exec 8.x and 9.x Agent for UNIX binary
/etc/bkupexec/agent.be to
etc/bkupexec/agent.be.disabled.
To enable the Backup Exec 8.x and 9.x Agent for UNIX
1. On the UNIX host where the Backup Exec 8.x and 9.x Agent for UNIX was disabled,
kill all processes named beremote, which are the processes used by the Remote
Agent.
2. Rename the Backup Exec 8.x and 9.x Agent for UNIX binary
/etc/bkupexec/agent.be.disabled to etc/bkupexec/agent.be
3. Start the Backup Exec 8.x and 9.x Agent for UNIX as usual or restart the host.
Appendix G, Symantec Backup Exec Remote Agent for Linux or Unix Servers
955

Troubleshooting the Remote Agent for Linux or Unix Servers
To disable the Remote Agent for Linux or Unix Servers Agent
1. On the UNIX host, kill all processes named beremote.
2. Rename the RALUS binary /opt/VRTSralus/bin/beremote to
/opt/VRTSralus/bin/beremote.disabled.
To enable the Remote Agent for Linux or Unix Servers Agent
1. On the UNIX host where the Remote Agent was disabled, kill all processes named
agent.be, which are the processes used by the Backup Exec 8.x and 9.x Agent for
UNIX.
2. Rename the RALUS binary /opt/VRTSralus/bin/beremote.disabled to
/opt/VRTSralus/bin/beremote.
3. Start the Remote Agent as usual or restart the host.
Related Topics:
“Troubleshooting the Remote Agent for Linux or Unix Servers” on page 956
Troubleshooting the Remote Agent for Linux or Unix Servers
RALUS is installed on a UNIX or Linux server in a NIS domain, but Backup Exec is unable to
browse resources on the server. What should I do?
Verify the nsswitch.conf file configuration as follows:
If the group and passwd lines in the nsswitch.conf file are set to compat mode, additional
configuration of the /etc/passwd and /etc/group files is necessary. Refer to the
nsswitch.conf man pages for additional information on configuring nsswitch.conf to use
compat mode.
Alternatively, change the passwd and group lines to "nis files" so that the UNIX or Linux
system validates the user through NIS. If the NIS server is unavailable or the user is not
found, the local files are used for validation.
I’m unable to load beremote agent. When attempting to load beremote in console mode,
"./beremote --log-console" shows the following message. “ACE_SV_Semaphore_Complex:
no space left on device.” Now what?
This issue occurs when the computer reaches its maximum limit on allowable
semaphores. It can occur when there an unexpected termination of the beremote agent.
When the beremote agent unexpectedly terminates, beremote is unable to clean up some
956 Administrator’s Guide

Appendix G, Symantec Backup Exec Remote Agent for Linux or Unix Servers
Troubleshooting the Remote Agent for Linux or Unix Servers
of the semaphore resources it used. There may be other processes that may also have
caused the use of semaphores to have reached the limit. There is no safe way to recover
the computer from this condition unless you restart the computer.
If you have other processes running it may not be feasible to restart the computer. In this
case, you can run a series of commands that let you list and then clean up all semaphores
in use by the operating system. Unfortunately, there is no way to correlate which
semaphores are being used by the beremote agent, so be careful when selecting
semaphores for cleanup. Cleaning up semaphores of other programs in use can cause
those applications to become unstable.
To list semaphores, use the following command:
ipcs –a
To remove semaphores for each identifier listed by the ipcs -a command, use the
following command:
ipcrm –s
A ‘user attention’ icon appears
Related Topics:
“Symantec Backup Exec Remote Agent for Linux or Unix Servers” on page 937
957

Troubleshooting the Remote Agent for Linux or Unix Servers
958 Administrator’s Guide

Appendix
Symantec Backup Exec
Remote Agent for Macintosh
Systems
H
The Remote Agent for Macintosh Systems (Remote Agent) is installed as a separate,
add-on component that enables Windows Server network administrators to perform
backup and restore operations on Macintosh computers that are connected to the
network. This agent must be running on these computers before backup or restore
operations can be performed.
After the agent is configured, the Macintosh computers are ready for backup.
When backing up data using the Remote Agent for Macintosh, Backup Exec enables you
to protect data using multiple backup types. These include:
■ Full
■ Differential - Using modified time
■ Incremental - Using modified time
■ Working set
Only full backups are supported with the Remote Agent when using the Backup Wizard.
Selecting any other method of backup through the Backup Wizard will still result in a full
backup being performed. To specify differential or incremental backups using modified
time, make the selection from the backup properties window.
Related Topics:
“Requirements for the Remote Agent for Macintosh Systems” on page 960
“Installing the Remote Agent for Macintosh Systems by using the SSH (Secure Shell)
protocol” on page 963
“Backing up Macintosh computers” on page 969
959

Requirements for the Remote Agent for Macintosh Systems
Requirements for the Remote Agent for Macintosh Systems
The following platforms and file systems are supported:.
Supported Macintosh platforms and file systems
Platform Version File System
Macintosh OS X 10.3, 10.4 (PowerPC) Native
Macintosh OS X Server 10.3, 10.4 (PowerPC) Native
Note For the latest supported platforms, see the Symantec Software Compatibility List
on the Symantec Support web site.
The following should be in place before you install the Remote Agent:
■ You must be a member of a group that has Admin privileges on the Macintosh
computer at which you are installing the Remote Agent for Macintosh Systems.
■ Access to a mounted CD-ROM drive.
■ TCP/IP, which is used to communicate with the Macintosh computer computers, is
required on the media server.
Caution If the Backup Exec 8.x and 9.x Agent for Macintosh is installed on a Macintosh
computer, and you are installing the Remote Agent on the same computer, you
must disable the existing Backup Exec 8.x and 9.x Agent for Macintosh before
installing the Remote Agent. Otherwise, the Remote Agent will not run
properly after it is installed. For information on disabling or enabling either of
the agents, see “The Remote Agent for Macintosh Systems and the Backup
Exec 8.x and 9.x Agent for Macintosh” on page 973.
Related Topics:
“Installing the Remote Agent for Macintosh Systems” on page 961
“Installing the Remote Agent for Macintosh Systems by using the SSH (Secure Shell)
protocol” on page 963
“Backing up Macintosh computers” on page 969
960 Administrator’s Guide

Appendix H, Symantec Backup Exec Remote Agent for Macintosh Systems
Installing the Remote Agent for Macintosh Systems
Installing the Remote Agent for Macintosh Systems
See the following topics when installing the Remote Agent for Macintosh Systems on a
Macintosh computer.
■ To install the Remote Agent from the Backup Exec for Windows Servers CD, see
“Installing the Remote Agent for Macintosh Systems using the installation script”
on page 961.
■ To install the Remote Agent using the SSH protocol, see “Installing the Remote
Agent for Macintosh Systems by using the SSH (Secure Shell) protocol” on page 963.
■ To manually start the Remote Agent daemon, see “Manually starting the Remote
Agent for Macintosh Systems daemon” on page 972.
■ To manually stop the Remote Agent daemon, see “Manually stopping the Remote
Agent for Macintosh Systems daemon” on page 972
Installing the Remote Agent for Macintosh Systems using the
installation script
The Remote Agent for Macintosh Systems installation script is capable of installing the
agent to both local and remote Macintosh based computers.
It is recommended that you install the software from a Macintosh computer using the
Backup Exec for Windows Servers CD and the push installation technology built into the
installation script. Installing the agent in this manner enables you to install it on
multiple remote Macintosh computers in the least amount of time possible. You can also
take the Backup Exec for Windows Servers CD to the target computers and locally install
the software. In either case, you need to know the computer names of the Macintosh
computers where the software will be installed.
Caution If the Backup Exec 8.x and 9.x Agent for Macintosh is installed on a Macintosh
computer, and you are installing the Remote Agent on the same computer, you
must change the existing agent name in the Backup Exec 8.x and 9.x Agent for
Macintosh configuration file, agent.cfg, before installing the Remote Agent.
Otherwise, the Remote Agent will not run properly after it is installed.
Modify the agent name in the configuration parameter, Name in
/etc/bkupexec/agent.cfg to any name besides the name you are using.
After modifying the name, save the agent.cfg file and then run the Remote
Agent installer.
961

Installing the Remote Agent for Macintosh Systems
To install the Remote Agent for Macintosh Systems using the installation script
1. At a Macintosh computer, place the Backup Exec for Windows Servers CD in the
CD-ROM drive.
The Backup Exec for Windows Servers CD will mount in /Volumes/Symantec.
2. Open a Finder window and then browse to Applications>Utilities.
3. Open Terminal.
4. In Terminal, type sudo ./installrams.
5. Enter a password, which should be the password of the currently logged in user.
6. Enter the name of a Macintosh computer or computers on which to install the
Remote Agent and press Enter. When entering multiple computer names, use spaces
between each name.
7. After the installer successfully checks for a valid Macintosh computer operating
system during the initial system check, press Enter.
8. After reviewing the package installation summary, press Enter.
9. Press Enter to start the Remote Agent installation requirements precheck.
If you are running the Backup Exec 8.x and 9.x Agent for Macintosh, a message
appears informing you that the Backup Exec 8.x and 9.x Agent for Macintosh will be
disabled, but not uninstalled. Press Enter to disable the Backup Exec 8.x and 9.x
Agent for Macintosh and continue with the install process. If you do not want to
disable the Backup Exec 8.x and 9.x Agent for Macintosh, the Remote Agent installer
will terminate and exit and the Remote Agent will not be installed.
10. Press Enter after the Remote Agent installer installation requirements check
completes.
11. Enter the computer name or IP address of the Backup Exec media server that you
want the Remote Agent to publish to and press Enter. If you need to specify
additional media servers, type Y then Enter; otherwise, press Enter.
12. Verify that the IP address and/or computer name information is correct and press
Enter. If changes need to be made, type N, and then press Enter to modify the
information.
13. Press Enter to begin the installation.
962 Administrator’s Guide

Appendix H, Symantec Backup Exec Remote Agent for Macintosh Systems
Installing the Remote Agent for Macintosh Systems
A message appears stating the installation has completed successfully after the
installation finishes.
14. Press Enter.
The installrams log file is saved to the following location on the Macintosh
computer:
/var/tmp/vxif/installrams/installrams.log
Related Topics:
“Publishing Macintosh computers to a media server” on page 965
“About editing the ralus.cfg file” on page 965
“About ralus.cfg format components” on page 966
“Backing up Macintosh computers” on page 969
Installing the Remote Agent for Macintosh Systems by using the
SSH (Secure Shell) protocol
By default, the Remote Agent installation program uses RSH (Remote Shell) when
remotely installing the Remote Agent. Symantec recommends that you use SSH (Secure
Shell) instead. To remotely install the Remote Agent using the SSH protocol, you must
establish and then test a trust relationship between the client computer and each
computer where you want to install the Remote Agent.
To establish a trust relationship, SSH must be enabled on each computer where you
want to install the Remote Agent. If SSH is not enabled, use the following steps to enable
it:
To establish a trust relationship and enable SSH
1. To enable SSH, open System Preferences.
2. Click Sharing.
3. Check the name of the check box for Remote Login.
4. On the SSH client computer from where you are installing the Remote Agent, log in
as root.
5. Run the following command:
ssh-keygen -b 1042 -t dsa
963

Installing the Remote Agent for Macintosh Systems
6. Accept the defaults, including no passphrase.
The command creates an SSH key for the computer, along with a directory in root's
home directory called .ssh. The SSH key resides in a file called id_dsa.pub.
7. On each remote computer where the Remote Agent is installed, verify that
/var/root/.ssh/authorized_keys2 file exists.
If the file does not exist Copy the file, id_dsa.pub, from the SSH client to
/var/root/.ssh/authorized_keys2 to each computer. You may have
to create the directory /var/root/.ssh.
If the file does exist Create a backup of the file, authorized_keys2, and then append
the contents of the id_dsa.pub file to the original
authorized_keys2 file.
To test the trust relationship
1. On the SSH client computer from where the Remote Agent is being installed, log in
as root.
2. Run the following command:
ssh root@
The following prompt may appear:
Are you sure you want to continue connecting (yes/no)?
3. Type yes.
If the trust is properly configured, a shell prompt appears for the remote computer.
If a password prompt appears, the trust is not properly configured. Verify that you
have performed each of the steps listed above.
After testing the trust relationship, close the shell.
4. Run the following command to install the Remote Agent to the client computer:
./installralus -usessh.
Related Topics:
“Publishing Macintosh computers to a media server” on page 965
“About editing the ralus.cfg file” on page 965
“About ralus.cfg format components” on page 966
“Backing up Macintosh computers” on page 969
964 Administrator’s Guide

Appendix H, Symantec Backup Exec Remote Agent for Macintosh Systems
Installing the Remote Agent for Macintosh Systems
Publishing Macintosh computers to a media server
Macintosh computers must publish themselves to a Backup Exec media server before
you can back them up.To establish communications, the Remote Agent installation
program creates a configuration file named ralus.cfg on each Macintosh computer
where the Remote Agent is installed. This file contains IP information that the
Macintosh computers use to publish themselves to a media server, where they appear in
the Macintosh Systems node in the backup selections tree.
A ralus.cfg configuration file also contains a list of Backup Exec media servers that you
want to use to back up a particular Macintosh computer. Since the same Macintosh
computer can be backed up by multiple Backup Exec media servers, there is no limit to
the number of Backup Exec media servers that can be listed in the ralus.cfg file.
Backup Exec media server entries in the ralus.cfg file are entered using either the media
server name from a naming service provider such as DNS, NIS, or an IP address.
Related Topics:
“About editing the ralus.cfg file” on page 965
“About ralus.cfg format components” on page 966
“Backing up Macintosh computers” on page 969
About editing the ralus.cfg file
You can add or delete Backup Exec media servers from the list of media servers found in
a Macintosh computer ralus.cfg file. Adding a media server to the list expands the
number of media servers that can back up the Macintosh computer, while deleting a
media server removes it from the list of media servers to which it advertises itself. You
can also modify naming information for a media server such as its DNS name or IP
address.
A Backup Exec media server entry in a ralus.cfg file conforms to a specific format, which
must be followed to ensure communication between the media server and the Macintosh
computer.
Related Topics:
“Publishing Macintosh computers to a media server” on page 965
“About ralus.cfg format components” on page 966
“Backing up Macintosh computers” on page 969
965

Installing the Remote Agent for Macintosh Systems
About ralus.cfg format components
The ralus.cfg format contains three components. The first component (A) is a required
string.
The second component is a unique identifier followed by an equal sign (=). A unique
identifier can consist of sequential numbers, letters or alpha-numeric characters. For
example: 1, 2, 3 or A, B, C. You can also use AA, BB, CC, or A1, A2, B1, B2. Whatever
unique identifier you decide to use must be unique if you list multiple Backup Exec media
servers in the ralus.cfg file.
The third component of the ralus.cfg format is the actual Backup Exec media server IP
address or its naming-service accessible name. For example, a DNS name, computers file
name, or NIS name). When entering this information, do not use spaces.
Ralus.cfg formatting example
A = Required string
B = Required and unique identifier (the order or appearance is irrelevant)
C = File or directory to be excluded
Editing a ralus.cfg file can be done using any UNIX text editor.
Related Topics:
“About editing the ralus.cfg file” on page 965
“About file and directory exclusions in ralus.cfg” on page 966
About file and directory exclusions in ralus.cfg
You may have files and directories on the Macintosh computers that you do not want to
backed up. Rather than manually deselecting them when making backup selections, you
can enter file and directory exclusion information in the ralus.cfg file. After the
information is added, the file and directories are ignored and will not be backed up.
966 Administrator’s Guide

File and Directory Exclusions in the ralus.cfg File
A = Required string
B = Required and unique identifier (the order or appearance is irrelevant)
C = File or directory to be excluded
Related Topics:
“Backing up Macintosh computers” on page 969
“Backing up Macintosh computers” on page 969
Creating a Macintosh logon account
Appendix H, Symantec Backup Exec Remote Agent for Macintosh Systems
Creating a Macintosh logon account
On initial access of the Macintosh computer, a Logon Account Selection screen appears
stating that the system logon account used by Backup Exec to access to the Macintosh
computer has failed, and that access to the Macintosh computer is denied. To proceed, a
new logon account must be created for the Macintosh computer using credentials that
allow access to the Macintosh computer.
Note The logon account credentials you provide during the creation of logon account
used during the initial access of the Macintosh computer are stored by Backup
Exec. These credentials will be used again when making future backup selections
from the Macintosh computer. However, if the access credentials for the Macintosh
computer change, a new Backup Exec Macintosh computer logon account will need
to be created in order to access the computer.
To create a Macintosh logon account
1. In Backup Job Properties pane under Favorite Resources, expand Macintosh
Systems.
2. Double-click the desired Macintosh computer.
A Logon Account Selection screen appears stating that the Backup Exec System
Logon Account failed to access the Macintosh computer.
3. On the Logon Account Selection screen, click New.
4. Add account credentials for the Macintosh computer and then click OK.
967

Creating a Macintosh logon account
Credentials supplied for the Macintosh computer must have Admin privileges that
can be authenticated by the Macintosh computer.
User name The user name required to access the Macintosh computer. This
name must have Admin privileges, which can be authenticated by
the Macintosh computer.
Password The password used to access the Macintosh computer.
Confirm password The same password entered in the Password field, which is used
to confirm the password was entered correctly in the Password
field.
Account name A label you enter to name the logon account.
Notes Pertinent notes about the account.
5. After authenticating the credentials entered, access to the Macintosh computer is
granted and backup selections can be made.
Related Topics:
“Backing up Macintosh computers” on page 969
968 Administrator’s Guide

Backing up Macintosh computers
Appendix H, Symantec Backup Exec Remote Agent for Macintosh Systems
Backing up Macintosh computers
After making backup selections, job properties for the Macintosh computer backup jobs
should be set. Job properties specifically targeted to Macintosh backup jobs are found in
the Job Properties pane under Linux, Unix, and Macintosh.
Use the following steps to set the backup job properties.
To back up a Macintosh computer
1. After making backup selections from the Macintosh computer, from Properties,
under Settings, click Linux, Unix, and Macintosh. The following options appear:
Preserve change
time
Follow local mount
points
Follow remote
mount points
Use this option to prevent the Remote Agent from changing an object’s
(files and directories) attributes when a backup occurs. Normally,
during a backup, Backup Exec preserves an object’s last access
timestamp by resetting the last access timestamp to the value before
the backup occurred. When Backup Exec modifies the objects’ last
access timestamp, the Macintosh operating system internally updates
the object’s “ctime.” An object’s ctime is the time when an object’s
attributes (permissions, timestamps, etc.) have been modified. If the
attributes are not changed by the Remote Agent after a backup, the
object’s ctime will not change. This option does not affect object
attributes set during restore operations.
Use this option to have Backup Exec follow local mount points when
backing up data. For more information on local mount points, see your
Macintosh documentation.
Use this option to have Backup Exec follow remote mount points when
backing up data. For more information on remote mount points, see
your Macintosh documentation.
969

Backing up Macintosh computers
Back up contents of
soft-linked
directories
Use this option to back up the contents of directories that are linked
using soft links.
Macintosh computers use many soft-links, some of which may point to
parent directories. Selecting this option can result in duplicate data
being backed up to tape, and it can also cause backup jobs to continue
indefinitely.
This option can be useful in certain situations. For example, you can
use this option to back up a single directory that contains soft-links to
data you want backed up.
When this option is selected, the soft-links themselves are not backed
up but the data they point to is.
When this option is not selected, the soft-links are backed up, but the
data is not.
For more information on soft-linked directories, see your Apple
Macintosh documentation.
Lock remote files Use this option if the Remote Agent requires exclusive access to the
files on remote systems connected through Network File System (NFS).
2. Make the appropriate selections or use the default selections provided.
3. Click General in the Properties pane of the Backup Job Properties screen.
4. In the list box for Backup method for files, select Full - Back up files - Using modified
time rather than Full - Back up files - Using archive bit (reset archive bit), as the
concept of an archive bit is not valid in Macintosh environments.
Related Topics:
“Backing up Macintosh computers” on page 969
“Requirements for the Remote Agent for Macintosh Systems” on page 960
“Troubleshooting the Remote Agent for Macintosh Systems” on page 974
970 Administrator’s Guide

Appendix H, Symantec Backup Exec Remote Agent for Macintosh Systems
Uninstalling the Remote Agent for Macintosh Systems
Uninstalling the Remote Agent for Macintosh Systems
The Remote Agent for Macintosh Systems installer is capable of uninstalling the agent
from both local and remote Macintosh computers.
To uninstall the Remote Agent for Macintosh Systems on the Macintosh computer
1. At a Macintosh computer, place the Backup Exec for Windows Servers CD in a
CD-ROM drive.
2. Logon to the target computer with Admin privileges.
3. Navigate to Remote Agent for Macintosh Systems uninstaller on the Backup Exec
CD using the following path:
/RAMS//uninstallrams
4. At the command prompt, type the following command:
./uninstallrams
5. Enter the name of a Macintosh computer or computers from which to uninstall the
Remote Agent and press Enter. When entering multiple computer names, use
spaces between each name.
6. Press Enter after the Remote Agent package check completes successfully.
7. Press Enter when prompted, Are you sure that you want to uninstall
RALUS packages from ? [y,n,q] .
The uninstall begins. A message appears stating the removal process has completed
successfully, after the uninstaller finishes.
8. Press Enter.
The uninstallation summary, and uninstallrams log files are saved to the following
locations on the Macintosh computer:
Uninstallation summary:
/opt/VRTS/install/logs/uninstallrams.summary
Uninstallrams log:
/opt/VRTS/install/logs/uninstallrams.log
After the log files are saved, the Remote Agent uninstall is complete.
971

Uninstalling the Remote Agent for Macintosh Systems
Related Topics:
“Manually starting the Remote Agent for Macintosh Systems daemon” on page 972
“Manually stopping the Remote Agent for Macintosh Systems daemon” on page 972
Manually starting the Remote Agent for Macintosh Systems
daemon
To manually start the Remote Agent for Macintosh Systems daemon
1. Connect to the target Macintosh computer as the root user using a terminal session.
2. Issue the following startup command:
/etc/init.d/SystemStarter start VRTSrams
Related Topics:
“Manually stopping the Remote Agent for Macintosh Systems daemon” on page 972
“Uninstalling the Remote Agent for Macintosh Systems” on page 971
Manually stopping the Remote Agent for Macintosh Systems
daemon
Use the following steps to manually stop the Remote Agent for Macintosh Systems
daemon.
To manually stop the Remote Agent for Macintosh Systems daemon
1. Connect to the target Macintosh computer as the root user using a terminal session.
2. Issue the following stop command:
/etc/init.d/SystemStarter stop VRTSrams
Related Topics:
“Manually starting the Remote Agent for Macintosh Systems daemon” on page 972
“Uninstalling the Remote Agent for Macintosh Systems” on page 971
972 Administrator’s Guide

The Remote Agent for Macintosh Systems and the Backup Exec 8.x and 9.x Agent for Macintosh
The Remote Agent for Macintosh Systems and the Backup
Exec 8.x and 9.x Agent for Macintosh
Both the Backup Exec 8.x and 9.x Agent for Macintosh and the Remote Agent can be
installed together on the same computer, but only one can be running at one time. If you
are manually installing the Remote Agent and the Backup Exec 8.x and 9.x Agent for
Macintosh is already installed, the Backup Exec 8.x and 9.x Agent for Macintosh must be
disabled. After disabling the Backup Exec 8.x and 9.x Agent for Macintosh, proceed with
the manual Remote Agent installation.
Use the following steps to disable or enable the Backup Exec 8.x and 9.x Agent for
Macintosh.
To disable the Backup Exec 8.x and 9.x Agent for Macintosh
1. On the Macintosh computer, kill all processes named agent.be.
2. Rename the Backup Exec 8.x and 9.x Agent for Macintosh binary as follows:
/etc/bkupexec/agent.be to etc/bkupexec/agent.be.disabled.
To enable the Backup Exec 8.x and 9.x Agent for Macintosh
1. On the Macintosh computer where the Backup Exec 8.x and 9.x Agent for Macintosh
was disabled, kill all processes named beremote, which are the processes used by
the Remote Agent.
2. Rename the Backup Exec 8.x and 9.x Agent for Macintosh binary as follows:
/etc/bkupexec/agent.be.disabled to etc/bkupexec/agent.be
3. Start the Backup Exec 8.x and 9.x Agent for Macintosh as usual or reboot the
computer.
To disable the Remote Agent for Macintosh Systems
1. On the Macintosh computer, kill all processes named beremote.
2. Rename the Remote Agent binary /opt/VRTSrams/bin/beremote to
/opt/VRTSrams/bin/beremote.disabled.
To enable the Remote Agent
Appendix H, Symantec Backup Exec Remote Agent for Macintosh Systems
973

Troubleshooting the Remote Agent for Macintosh Systems
1. On the Macintosh computer where the Remote Agent was disabled, kill all processes
named agent.be, which are the processes used by the Backup Exec 8.x and 9.x
Agent for Macintosh.
2. Rename the Remote Agent binary /opt/VRTSrams/bin/beremote.disabled to
/opt/VRTSrams/bin/beremote.
3. Start the Remote Agent as usual or restart the computer.
Related Topics:
“Troubleshooting the Remote Agent for Macintosh Systems” on page 974
Troubleshooting the Remote Agent for Macintosh Systems
The Remote Agent is installed on a Macintosh server in a NIS domain, but Backup Exec is
unable to browse resources on the server. What do I do?
Verify the nsswitch.conf file configuration as follows:
If the group and passwd lines in the nsswitch.conf file are set to compat mode,
additional configuration of the /etc/passwd and /etc/group files is necessary. Refer to
the nsswitch.conf man pages for additional information on configuring nsswitch.conf to
use compat mode.
Alternately, change the passwd and group lines to "nis files" so that the Macintosh
system validates the user through NIS. If the NIS server is unavailable or the user is not
found, the local files are used for validation.
I’m unable to load beremote agent. When attempting to load beremote in console mode,
"./beremote --log-console" shows the following message. “ACE_SV_Semaphore_Complex:
no space left on device.” Now what?
This issue occurs when the computer reaches its maximum limit on allowable
semaphores. It can occur when there an unexpected termination of the beremote agent.
When the beremote agent unexpectedly terminates, beremote is unable to clean up some
of the semaphore resources it used. There may be other processes that may also have
caused the use of semaphores to have reached the limit. There is no safe way to recover
the computer from this condition unless you restart the computer.
If you have other processes running it may not be feasible to restart the computer. In
this case, you can run a series of commands that let you list and then clean up all
semaphores in use by the operating system. Unfortunately, there is no way to correlate
which semaphores are being used by the beremote agent, so be careful when selecting
semaphores for cleanup. Cleaning up semaphores of other programs in use can cause
those applications to become unstable.
974 Administrator’s Guide

Appendix H, Symantec Backup Exec Remote Agent for Macintosh Systems
Troubleshooting the Remote Agent for Macintosh Systems
To list semaphores, use the following command:
ipcs –a
To remove semaphores for each identifier listed by the ipcs -a command, use the
following command:
ipcrm –s
Related Topics:
“Symantec Backup Exec Remote Agent for Macintosh Systems” on page 959
975

Troubleshooting the Remote Agent for Macintosh Systems
976 Administrator’s Guide

Appendix
Backup Exec Desktop and
Laptop Option
The Backup ExecDesktop and Laptop Option (DLO) provides automated file protection
for desktops and laptops (collectively referred to as desktops). Protection is provided
whether the computer is connected to the network or offline. When the desktop is not
connected to the network, the files are backed up to a user data folder on the desktop.
When the computer reconnects to the network, the files are backed up from the local
desktop user data folder to the designated network user data folder.
Users who have multiple computers can synchronize the data between their computers
so the most up-to-date file versions are available on all of their computers.
Note This product is intended to provide file-level protection for desktop user data and
is not intended to provide a full system backup.
How the Desktop and Laptop Option Works
DLO is comprised of the
■ DLO Administration Console
■ DLO database
■ DLO Maintenance Service
■ Desktop and Laptop Agent (Desktop Agent)
The Desktop Agent is installed and run on desktop computers.
Note The DLO Administration Console and database are part of Backup Exec and run on
the Backup Exec media server. The DLO Administration Console runs in a separate
window that you access from Backup Exec.
977
I

How the Desktop and Laptop Option Works
From the DLO Administration Console, the Administrator can:
■ Create profiles for groups of users or computers. Profiles enable you to control the
desktop user’s level of interaction with the Desktop Agent, define the types of files
that can be backed up, set the schedule for backups, and configure additional
settings for the Desktop Agent.
■ Create network user data folders. Network user data folders are locations on the
network where data from protected desktops is stored.
■ Create Automated User Assignments. Automated User Assignments determine the
Storage Location and profile to which users are assigned when they install the
Desktop Agent.
Note Automated User Assignments are not used if users are manually added to
DLO.
■ Add users manually to DLO. Instead of using Automated User Assignments, you can
manually add users to DLO and assign a profile and Storage Location to them. This is
particularly useful when network shares already exist for user data storage. Users
can be added individually or multiple users can be added at the same time by
importing them from a list.
■ View history log files, receive alerts, and restore files to a desktop from the
Administration Console.
The Desktop Agent resides on the desktops and laptops that you want to protect. The
desktop user’s level of interaction with the Desktop Agent can vary depending on how
the Administrator has configured the profile assigned to the user. The Desktop Agent
may run in the background, automatically protecting files. Alternatively, desktop users
with full access to the Desktop Agent interface can schedule backups, select which types
of files to back up, restore files, synchronize file versions between different computers,
and view the status of their backups.
Related Topics:
“Configuring DLO” on page 1019
“About DLO Profiles” on page 1020
“About Backup Selections” on page 1033
“About DLO Storage Locations” on page 1053
“About Automated User Assignments” on page 1060
978 Administrator’s Guide

How the Desktop and Laptop Option Works
Relationship Between Backup Exec and the Desktop and Laptop Option Components
- Desktop Agent
- Desktop User Data
Folder
Administration Console on the media server or a remote server
Storage Locations
Desktops and Laptops
- Backup Exec Administration Console
- Backup Exec media server
- Desktop Agent install share
-DLO Maintenance Server
The BE and DLO Administration
Consoles, the DLO
Maintenance Server and the
DLO file servers can reside on
the media server or remote
servers.
If you use Backup Exec to
protect the file servers that
host the Network User Data
DLO File Server Folders remotely, the Remote
Agent for Windows Servers is
required.
DLO File Server
- Desktop Agent
- Desktop User Data
Folder
979

What’s New in DLO
What’s New in DLO
Many new features have been added to Backup Exec DLO version 11d:
Expanded Operating System Support
DLO now supports Microsoft Windows XP 64-bit operating systems for the DLO
Administration Console and the Desktop Agent. The Desktop Agent will install and run
on these platforms in 32-bit compatibility mode with all features and functions available.
For additional information, see “System Requirements for the Administration Console”
on page 986 and “System Requirements for the Desktop Agent” on page 1158.
Backup Exec DLO Default License Limit
The default Backup Exec DLO license now allows up to five desktop users to back up their
data. The license limit is based on the number of users. Each user can back up their data
from one or more computers. Users installed after the 5th Desktop Agent user are
disabled until the license is upgraded.
Delta File Transfer
DLO can now be configured so that after the initial backup of a file, subsequent backups
transmit only those parts of the file that have changed. See “Using Delta File Transfer”
on page 1048 for more information.
Backup of Lotus Notes NSF Files at the Message Level
DLO now supports the backup of Lotus Notes NSF email files at the message level. See
“Backing Up Lotus Notes NSF Files Incrementally” on page 1180 for additional
information.
Microsoft SQL 2005 and Microsoft SQL Express Support
DLO now supports Microsoft SQL 2005 and Microsoft SQL Express for the
administration database. The media server can be configured to use Microsoft's SQL
2005 Server or SQL Express database. See “Installing the Backup Exec Desktop and
Laptop Option” on page 987 for additional information.
Alternate Stream Backup
DLO now protects all of the alternate streams for a file, including security streams.
980 Administrator’s Guide

What’s New in DLO
Expanded Global Exclude Options
DLO now provides expanded Global Exclude options that enable you to specify the
attributes of files that you want to exclude from backups, or that you do not want to
compress, encrypt, or back up with Delta File Transfer. You can also exclude attachments
to emails or specific email folders from backup. See “Configuring Global Exclude Filters”
on page 1065 for additional information.
Improved filtering of Email files
DLO now provides the capability to filter email files during backup using the expanded
Global Excludes options. Folders can be excluded using name filters. Attachments can be
excluded by type or size. In addition, DLO can be configured to exclude messages
received on or before a specific date. See “Configuring Global Exclude Filters” on
page 1065 for additional information.
Expanded Configuration of Default Settings
Default settings can now be easily configured from one integrated dialog box. See “DLO
Default Settings” on page 1000 for additional information.
Connection-Based Policies
Backups can now be easily disabled or limited for certain connection types. See
“Add/Edit Connection Policy” on page 1031
Notification Alerts
DLO includes the following methods to notify you or others of alerts:
■ SMTP
■ MAPI
■ Lotus Notes email
■ Paging
■ Printing
■ Net Send
See “Configuring Alerts for Notification” on page 1112 for additional information.
981

What’s New in DLO
Active Directory
DLO can now use Active Directory settings to configure Connection Policies and
Automated User Assignments. See “Add/Edit Connection Policy” on page 1031 and “New
Automated User Assignment Dialog Box Options” on page 1062 for additional
information.
Symantec LiveUpdate
DLO will now use Symantec LiveUpdate to deliver selected security patches to the
Desktop Agents. Backup Exec will use LiveUpdate to deliver selected patches to the DLO
Administration Console. Significant upgrades will still be delivered using website
downloads or CDs.
982 Administrator’s Guide

Before you install
Before you install DLO, you should consider the following:
Pre-installation considerations
Item Description
Domains and Active
Directory
Before you install
The media server and DLO Storage Locations must be in a Windows
Domain or Active Directory. Computers running the Desktop Agent can be
outside of a Windows Domain or Active Directory, but they must
authenticate with the domain or directory to access the media server or
Storage Locations.
Server loading DLO can be treated as a network file server. The ideal server for DLO has a
fast network connection and a fast set of disks. The CPU is not as critical
as these other factors for the DLO file server.
The number of Desktop Agents that can successfully back up to one DLO
installation depends on many factors. Multi-client testing of DLO has
found that when there are more than 400 clients concurrently attached to
a DLO server running Windows 2000 Advanced Server, file operations may
begin to fail when Paged Pool memory runs out. For this reason, it is not
recommended to configure DLO to run more than 400 concurrent backups
of this size when using DLO with Windows 2000. This limitation was not
observed when running DLO with Windows 2003.
Authentication DLO Administration Console
The DLO Administration Console can be managed by any user who has full
admin rights on the media server where DLO is installed. The user’s
account must be a domain account and must have rights to create network
shares and manage permissions of network shares and directories on any
remote server used for Storage Locations or network user data folders.
This is commonly accomplished by using a domain administrator account,
or can be accomplished by granting a standard domain account local
administrative rights to the servers hosting the DLO resources. See “About
Administrator Accounts” on page 996 for additional information.
Desktop Agent
DLO requires domain accounts. Every Desktop Agent user must log in to
DLO using a domain account. If you have users who log in using local
accounts, they can still use DLO, but they must have domain credentials to
authenticate with DLO.
983

Before you install
Pre-installation considerations
Item Description
Database Selection By default DLO installs its own instance of SQL Express 2005. DLO can
also be manually configured to use an existing SQL Express 2005, SQL
Server 2000, SQL Server 2005, or MSDE 2000 instance. You must use a
local database instance. Remote instances are not supported.
Note If you use an existing database instance, named pipes must be
enabled. If DLO installs its own SQL Express 2005 instance, named
pipes will be enabled automatically.
The following are pros and cons for these server options:
SQL Express 2005
Pros
◆ Free
◆ Unless you back up more than 1000 Desktop Agents per media server,
SQL Express should be sufficient for most needs.
Cons
◆ The database is limited to a single processor, resulting in slower I/O to
the database under load.
◆ 4 GB table size maximum for SQL Express, although DLO is unlikely to
reach this limit.
SQL Server
Pros
◆ Allows reasonable scalability beyond 1000 Desktop Agents.
◆ Database tools are included with SQL Server.
Cons
◆ Cost, however you do not need to purchase a SQL Server client license
for each Desktop Agent.
MSDE
◆ Free
◆ Unless you back up more than 1000 Desktop Agents per media server,
MSDE should be sufficient for most needs.
Cons
◆ The number of concurrent connections to the database is limited,
resulting in slower I/O to the database under load.
◆ 2 GB table size maximum for MSDE, although DLO is unlikely to reach
this limit.
984 Administrator’s Guide

Pre-installation considerations
Item Description
Before you install
Time Synchronization All computers running the DLO Administration Console or the Desktop
Agent should be set to a common time. This can be accomplished by
configuring the Windows Time Synchronization service on the network.
See www.microsoft.com for additional information.
Firewalls DLO is designed to work in firewall environments. In order for DLO to
function properly in a firewall environment, network file shares must be
visible after establishing a remote connection such as VPN. If file sharing
is not allowed, DLO will not be able to transfer files to or from the network
user data folder. Desktop computer files will still be protected to the
desktop user data folder, and will be transferred when the network user
data folder is accessible.
MDAC Support for the
DLO Administration
Console
MDAC Support for the
Desktop Agent
DLO supports versions 2.7 and 2.8 of MDAC, however MDAC 2.8 is
the default and is installed during the installation if it is not
already installed. When MDAC 2.8 is installed, a restart may be
required, and a computer administrator must complete the
installation process. If a non-administrator logs on first after the
MDAC 2.8 installation, the process generates a number of errors.
To avoid these errors when MDAC 2.7 is already installed, or if you
do not want to install MDAC 2.8, you can force the use of MDAC 2.7
by modifying the CmdLine value in the setup.ini file in the DLO
installation set by adding REQUIREDMDACVERSION=”2.7”.
Example:
CmdLine=REQUIREDMDACVERSION=”2.7” /l*v
%TEMP%\DLOConsoleInstall.log
The Desktop Agent supports versions 2.7 and 2.8 of MDAC, however
MDAC 2.8 is the default and is installed during the Desktop Agent
installation if it is not already installed. When MDAC 2.8 is installed, a
restart may be required, and a computer administrator must complete the
installation process. If a non-administrator logs on first after the MDAC
2.8 installation, the process generates a number of errors. To avoid these
errors when MDAC 2.7 is already installed, you can force the use of MDAC
2.7 by modifying the CmdLine value in the setup.ini file in the Desktop
Agent installation set by adding REQUIREDMDACVERSION=”2.7”.
Example:
CmdLine=/qf DEFAULTMEDIASERVER=”SERVERNAME”
DLODBINSTANCENAME=”BKUPEXEC” LAUNCHCLIENT=”1”
REQUIREDMDACVERSION=”2.7” /l*v “%TEMP%\DLOAgentInstall.log”
985

System Requirements for the Administration Console
System Requirements for the Administration Console
The following are the minimum system requirements for running this version of the DLO
Administration Console.
Minimum System Requirements
Item Description
Operating System ◆ Microsoft Windows 2000 family
◆ Microsoft Windows Server 2003 server family
◆ Microsoft Windows Server 2003 x64 Editions
◆ Microsoft Windows Server 2003 R2
◆ Microsoft Windows XP Service Pack 1 or later
◆ Microsoft Windows XP Professional x64 Edition
Internet Browser Internet Explorer 5.01 or later; however, version 5.5 is recommended
Processor Pentium system
Memory Required: 256 MB RAM
Recommended: 512 MB or more for better performance
Disk Space 150 MB hard disk space required after Microsoft Windows is installed
(typical installation)
Other Hardware ◆ Network interface card
◆ CD-ROM drive
◆ Printer supported by Windows (optional)
◆ Mouse (recommended)
Note Windows Domains and Active Directory are supported. Other authentication
schemes, such as Novell E-Directory and NIS+, are not supported.
986 Administrator’s Guide

Installing the Backup Exec Desktop and Laptop Option
Installing the Backup Exec Desktop and Laptop Option
The Symantec Backup Exec Desktop and Laptop Option is installed as a separate add-on
component of Backup Exec for Windows Servers to protect data on desktops.
To install DLO, see “Installing Backup Exec to a local computer” on page 81.
If you prefer to install DLO from the Command Line (Silent Mode), see “Installing Backup
Exec using the command line (silent mode)” on page 111 and “Command line switches
for Backup Exec silent mode installation” on page 112.
After you install and configure the settings for the desktop users, you can install the
Desktop Agent or direct the desktop users on how to install it. The Desktop Agent is
installed from the Desktop Agent install share, which is created when DLO is installed on
the Backup Exec media server.
Note The Backup Exec media server and any Storage Locations must be in a Windows
Domain or Active Directory. Computers running the Desktop Agent can be outside
of a Windows Domain or Active Directory, but they must authenticate with the
domain or directory to access the media server or Storage Locations. You will be
prompted to provide domain credentials.
Related Topics:
“Configuring DLO” on page 1019
“Deploying the Desktop Agent” on page 988
“Installing the Desktop Agent” on page 1158
Note Novell E-Directory, NIS+ and other non-Windows Domain or Active Directory
authentication schemes are not supported.
Before installing DLO, review “Before you install” on page 983. This section discusses a
number of topics that should be considered before installing DLO.
987

Installing the Backup Exec Desktop and Laptop Option
Deploying the Desktop Agent
When you install DLO from the Backup Exec installation CD, the Desktop Agent install
set is created on the Backup Exec media server in a directory that is shared and available
via a UNC path. There are several ways to deploy the Desktop Agent from the Desktop
Agent install share to the desktop computer.
Desktop Agent Deployment Methods
Deployment Methods Description
Push Install The Desktop Agent can be push installed using the Backup Exec
installer (see “Installing Backup Exec options to remote computers” on
page 92).
After a push install of the Desktop Agent, it may take up to two
minutes for the Desktop Agent to start up on the desktop computer.
To push install DLO to a computer running Windows XP with the
Windows Firewall enabled, File and Print Sharing must be enabled on
the desktop computer before performing the push install. File and
Print Sharing is configured in the Windows Firewall Exceptions tab.
email Send a hypertext link to the install files or include the install files as an
attachment.
Web page Place the install files on your company’s intranet.
Logon scripts Create a file that includes commands for installing the Desktop Agent.
Then assign the script to the User Properties for the employees who
need to use DLO. The commands are executed automatically when the
user logs on to the network. For more information about logon scripts,
refer to your Microsoft Windows documentation.
Microsoft Systems
Management Server
(SMS)
Related Topics:
“Installing the Desktop Agent” on page 1158
Use this automated system to distribute the Desktop Agent install set
to the desktop computers, which then initiate the installation. For
more information about SMS, refer to your Microsoft documentation.
CD-ROM To distribute the Desktop Agent installation files on a CD-ROM, place
the contents of the \\media server\DLO Agent share on the CD-ROM.
Users can then run setup.exe from the CD-ROM. The installed Desktop
Agent will be correctly associated with the media server.
988 Administrator’s Guide

Desktop Agent Installation Options
Installing the Backup Exec Desktop and Laptop Option
The Desktop Agent installation can be customized to meet specific needs. For example, it
can run silently with no user interface displayed, or it can display either a basic or
complete user interface. This and other customizations are accomplished by modifying
the SETUP.INI file in the DLO Agent setup directory.
▼ To customize the Desktop Agent installation:
1. In the Desktop Agent setup directory, open the SETUP.INI file for editing.
2. Modify the value that begins CmdLine= /qf as shown below:
Desktop Agent CmdLine Installation Options
Original command Options
Desktop Agent
installation interface
Set the Default Media
Server
Launch the Desktop
Agent
Specify the Required
MDAC Version
Modify the /qf term to change the interface that the Desktop
Agent user sees during installation of the Desktop Agent.
/qf
The full user interface is displaced, and a cancel button is
provided.
/qb
A basic progress dialog is displayed and the cancel button is
enabled.
/qb!
A basic user interface displayed. There is no cancel button.
/qn
The installation will be silent installation.
Note For a completely silent install, you will need to run
“setup.exe /s” after modifying the SETUP.INI file.
DEFAULTMEDIASERVER specifies the media server to which the
Desktop Agent will attach after installation.
The LAUNCHCLIENT option specifies whether or not the Desktop
Agent should be launched immediately following installation.
To launch immediately, set LAUNCHCLIENT=”1”
To prevent immediate launch, set LAUNCHCLIENT=”0”
DLO uses MDAC 2.8 by default. Force the use of MDAC 2.7 by
adding the following:
REQUIREDMDACVERSION=2.7
989

Installing the Backup Exec Desktop and Laptop Option
Desktop Agent CmdLine Installation Options
Original command Options
Suppress Reboot To suppress a reboot, even if one is required, add the following:
REBOOT=ReallySuppress
Logging Options Logging options can be modified by changing the l*v variable.
l*v “%TEMP%\DLOAgentInstall.log”
Turns on verbose logging and create a log file at the specified
location.
Note For additional Windows Installer logging options, see
http://support.microsoft.com/kb/314852/EN-US/.
3. Save and close the SETUP.INI file.
Examples:
For a silent installation, edit CmdLine in the SETUP.INI file as follows:
Original:
CmdLine=/qf DEFAULTMEDIASERVER=”Desktop3” LAUNCHCLIENT=”1” /l*v
“%TEMP%\DLOAgentInstall.log”
Modified:
CmdLine=/qn DEFAULTMEDIASERVER=”Desktop3” LAUNCHCLIENT=”1” /l*v
“%TEMP%\DLOAgentInstall.log”
For an installation with a basic interface but no option to cancel the installation, edit
CmdLine in the SETUP.INI file as follows:
Original:
CmdLine=/qf DEFAULTMEDIASERVER=”Desktop3” LAUNCHCLIENT=”1” /l*v
“%TEMP%\DLOAgentInstall.log”
Modified:
CmdLine=/qb! DEFAULTMEDIASERVER=”Desktop3” LAUNCHCLIENT=”1” /l*v
“%TEMP%\DLOAgentInstall.log”
990 Administrator’s Guide

Installing the Backup Exec Desktop and Laptop Option
Preparing for a Manual Push Deployment of the Desktop Agent
The following should be done before attempting a manual push deployment of the
Desktop Agent. These steps are not necessary when using the Backup Exec push
installer.
1. From the \\\DLOAgent directory the following files are required:
■ *.mst
■ *.cab
■ DLOBuildInfo.ini
■ *.msi
2. Run the msiexec command using, as a base, the value in setup.ini from the cmdline
key:
/qf DEFAULTMEDIASERVER=""
DLODBINSTANCENAME="" LAUNCHCLIENT="1"
REQUIREDMDACVERSION="2.8" TRANSFORMS="1033.mst" /l*v
"%TEMP%\DLOAgentInstall.log"
The default values are as follows:
Default Values
Item Default
DEFAULTMEDIASERVER Media server name. This value is
assigned when DLO is installed and is
the name of the computer on which the
media server is installed.
DLODBINSTANCENAME Specifies the SQL instance name. It is
recommended that you do not modify
this value.
LAUNCHCLIENT “1”
REQUIREDMDACVERSION "2.8"
TRANSFORMS "1033.mst"
3. For a silent installation, replace /qf with /qn. To install without user interaction, but
with a display of the installation progress, replace /qf with /qb.
991

Installing the Backup Exec Desktop and Laptop Option
4. If MDAC 2.7 is being used, you must replace REQUIREDMDACVERSION="2.8" with
REQUIREDMDACVERSION="2.7". No other values are valid. The installation will
fail if the MDAC version on target system is less than the REQUIREDMDACVERSION
value.
5. TRANSFORMS should be set to one of the mst files, according to the language used
by the desktop user:
1031.mst = German
1033.mst = English
1034.mst = Spanish
1036.mst = French
1040.mst = Italian
1041.mst = Japanese
1042.mst = Korean
2052.mst = Chinese (PRC) (Simplified)
6. The specification of the TRANSFORMS property is required, and will affect the
installer user interface and the start menu shortcuts. The DLO Agent is installed
with support for all eight languages, regardless of the transform chosen.
7. MSI 3 . 1 is required on the target systems. The MSI 3.1 installer is included in:
\\\DLOAgent\WindowsInstaller-KB893803-v2-x86.exe
992 Administrator’s Guide

Post Installation Tasks
Setting a Recovery Password
Post Installation Tasks
When the DLO Administration Console opens for the first time, the Recovery Password
Wizard opens. You must set a recovery password using this wizard or DLO will not run. If
you upgraded from a previous revision and previously set a recovery password, you will
not be prompted to set a recovery password. DLO will use the existing password.
The recovery password enables you to retrieve encrypted data that would otherwise be
lost if the DLO database is damaged or corrupted.
Once set, this recovery password can only be changed using the DLO command line
interface tools.
Related Topics:
“Checking Data Integrity” on page 993
“-SetRecoveryPwd Command” on page 1152
“-EmergencyRestore Command” on page 1152
Checking Data Integrity
The Data Integrity Scanner simplifies the process of scanning network user data from
previous DLO backups to detect unrestorable backup data. It verifies that all data is
encrypted using the most recent user key, and ensures that all data has the correct
recovery key for emergency restoration.
When Desktop Agents are upgraded, they will automatically perform a data integrity
check. When the Administration Console is opened, it identifies Desktop Agents that
have not been checked for integrity. If any are found, a dialog will open stating that one
or more computers have not yet been validated by the Data Integrity scanner and ask if
they should be scanned.
▼ To Check Data Integrity:
1. From the Tools menu, select Wizards and then Data Integrity Scanner.
2. Click Next.
993

Post Installation Tasks
3. If you would like to set advanced options, click Advanced Options. Select the
appropriate options and then click OK.
4. Click Start.
5. Review the scan results.
If the scan identified data encrypted with outdated keys but you did not choose to
quarantine the data, you can run the scan again after setting advanced options to
quarantine this data.
6. Click Next.
Data Integrity Scanner Advanced Options
Item Description
Permanently remove
previously quarantined
data
Quarantine data
encrypted with outdated
keys
Include computers that
have already been
validated
7. Click Finish.
Related Topics:
“Setting a Recovery Password” on page 993
“-SetRecoveryPwd Command” on page 1152
“-EmergencyRestore Command” on page 1152
Select this check box to cause all previously quarantined data
to be deleted.
Select this check box to quarantine all files with outdated
keys. If this option is not checked, data is scanned without
being quarantined. After data is quarantined, the Desktop
Agent backs up a new version of the file with the correct
encryption key.
Select this check box to force all data to be rescanned, even if
it has previously been validated.
Verbose output Select this check box to receive detailed information from the
scan.
994 Administrator’s Guide

Changing DLO Service Credentials
Post Installation Tasks
When DLO is installed, you must specify account credentials to be used to run the DLO
Administration Service. This account is used to create Storage Locations and network
user data folders, and must have rights to create shares on any computers where backup
data is to be stored. Using a Domain Administrator account is recommended. To create
Storage Locations in another Domain, there must be appropriate trust relationships in
effect.
▼ To change DLO Service Credentials:
1. On the Tools menu, select Manage Service Credentials.
2. Select Change DLO Service Account Information.
3. Enter account credentials as follows:
Service Account Information
Item Description
Change DLO service
account information
Select this check box to change the DLO service account
information.
User name Type the user name for the account to be used.
Domain name Enter the domain for this account.
Password Type the password for this account.
Confirm password Type the password again to confirm.
995

Post Installation Tasks
About Administrator Accounts
The DLO Administration Console can be managed by any user who has full administrator
rights on the media server. The user’s account must be a domain account and must have
rights to create network shares and manage permissions of network shares and
directories on any remote server used for Storage Locations or network user data folders.
This is commonly accomplished by using a domain administrator account.
When searching for files to restore, or when viewing history logs, the DLO
Administration Console accesses the network user data folders using the credentials of
the currently logged in user. If this user does not have the correct permissions to access a
resource, a dialog is displayed explaining this. If a DLO administrator attempts to access
a network user data folder, but is not logged in with an account with rights to access to
this folder, DLO will prompt for credentials. If credentials are input, they will be used to
access the folder, but will not be saved.
Automated Permissions Management
To configure DLO to automatically manage permissions for accessing network user data
folders, an administrator on the media server can create and configure DLO
administrator accounts for users using the DLO Administrator Account Management
dialog. Adding DLO Administrator accounts allows additional users to use the DLO
console without adding them to the administrators group on the media server.
DLO administrator accounts can be managed in one of two ways:
■ Granting individual users administrative access to DLO
This is the default configuration for DLO account management. You can grant a list
of individuals rights to manage DLO. If you use a list of individuals, you can specify
which individuals will have full restore rights, and which will have limited restore
rights.
See “Using A List of Individual Accounts to Manage DLO Permissions” on page 997
for instructions on configuring DLO to use a list of individual DLO administrators.
■ Using domain groups to manage DLO administrators
You can choose to specify domain groups to specify DLO administrators. If you
specify domain groups, one group can granted full restore privileges, and a second
group can be granted limited restore privileges. The domain groups must already
exist or be created by a domain administrator. For DLO, we recommend using the
groups DLOFullAdmin and DLOLimitedAdmin. The full administrator group is used
to grant administrators read access to user’s data, whereas the limited administrator
group only supplies list access, thus protecting the user’s data from unauthorized
access.
996 Administrator’s Guide

Post Installation Tasks
When accessing a network user data folder, the DLO console automatically checks
the folder to ensure it can read the files and data within. If the Console is unable to
access the folder, DLO uses the specified domain administrator group to set
permissions on the files and folders it needs to access. By making these files and
folders a member of the specified DLO administrator group, all DLO administrators
are thus automatically granted permissions to access the necessary resources.
See “Using Domain Groups to Manage DLO Permissions” on page 998 for
instructions on configuring DLO to use domain groups to manage DLO permissions.
Limited Restore
The purpose of the limited restore feature is to prevent restoration of data to an alternate
location by unauthorized users. By default, DLO administrators cannot restore a desktop
user’s files to an alternate location, providing an additional level of data security. A DLO
administrator can be granted full restore privileges, which allows the administrator to
restore data to an alternate location. When a DLO administrator has limited restoration
rights, there may be other administrative functions that they are not able to perform.
Using A List of Individual Accounts to Manage DLO Permissions
An administrator on the media server can create and configure DLO administrator
accounts for individual users. Accounts can be individually configured to specify full or
limited restore rights as discussed in “About Administrator Accounts” on page 996.
Alternatively, DLO can be configured to use domain groups for permissions
management. See “Using Domain Groups to Manage DLO Permissions” on page 998 for
additional information.
▼ To configure DLO to use a list of individual accounts for permissions management:
1. On the DLO Administration Console Network menu, select Administrator
Accounts.
2. Click Permissions.
3. Uncheck or verify unchecked the Use domain groups to manage access to network
user data folders checkbox.
Note When the Use domain groups to manage access to network user data folders
checkbox is checked, domain groups are listed on the Administrator Account
Management dialog. When this box is unchecked, individual user accounts are
once again listed. If you change from one type of account management to
another, the previous settings are retained for future use. For example, if you
have a list of individual DLO administrators and then change your
997

Post Installation Tasks
4. Click OK.
configuration to use domain groups instead, the list of individual accounts is
saved and will once again be used if the Use domain groups to manage access
to network user data folders checkbox is unchecked.
5. Do one of the following:
■ Click Add to add a new DLO administrator account. Continue with step 6.
■ Click Edit to modify an existing DLO administrator account. Continue with
step 6.
■ Click Remove to delete an existing DLO administrator account. Continue with
step 7.
6. Define the administrator account as follows:
Add Administrator Account Options
Item Description
User Name Type the name of the user you want to give administrative rights
to. Use the format DomainName\UserName
Description Type a description for this administrator account.
Notes Type any relevant notes regarding the administrator account.
Grant administrator full
restore privileges
7. Click OK twice.
Select this check box to allow this DLO administrator full restore
privileges, including the ability to restore desktop user data to an
alternate location.
Note Allowing someone other than the desktop user who owns
the data to restore files to an alternate location can
compromise data security.
Using Domain Groups to Manage DLO Permissions
An administrator on the media server can create and configure DLO administrator
accounts for users using the DLO Administrator Account Management dialog. One
method of managing DLO administrative access is to use domain groups to specify who
998 Administrator’s Guide

Post Installation Tasks
has rights to administer DLO. Two groups can be specified. The first group is granted full
restore privileges. The second group has limited restore privileges as discussed in “About
Administrator Accounts” on page 996.
Alternatively, DLO can be configured to use a list of accounts for permissions
management. See “Using A List of Individual Accounts to Manage DLO Permissions” on
page 997 for additional information.
▼ To configure DLO to use domain groups for permissions management:
1. On the DLO Administration Console Network menu, select Administrator Accounts
to open the Administrator Account Management dialog.
2. Click Permissions.
3. Check or verify checked the Use domain groups to manage access to network user
data folders checkbox.
Note When the Use domain groups to manage access to network user data folders
checkbox is checked, domain groups are listed on the Administrator Account
Management dialog. When this box is unchecked, individual user accounts are
once again listed. If you change from one type of account management to
another, the previous settings are retained for future use. For example, if you
have a list of individual DLO administrators and then you change your
configuration to use domain groups instead, the list of individual accounts is
saved and will once again be used if the Use domain groups to manage access
to network user data folders checkbox is unchecked.
4. Select the appropriate options as follows:
Select Restore Type
Restore Type Description
For DLO administrators with
full restore privileges, use the
domain group
For DLO administrators with
limited restore privileges, use
the domain group
To grant DLO administrators in a specified domain group
full restore privileges including the ability to restore a
desktop user’s files to an alternate location, enter or browse
to a fully qualified domain group.
Example: Enterprise\DLOFullAdmins
o grant DLO administrators in a specified domain group
limited restore privileges that do not include the ability to
restore a desktop user’s files to an alternate location, enter
or browse to a fully qualified domain group.
Example: Enterprise\DLOLimitedAdmins
999

Post Installation Tasks
5. Click OK twice.
DLO Default Settings
When you start DLO for the first time, defaults are already configured. You can adjust the
defaults to meet the needs of your environment. Default settings are available for
profiles, backup selections and Global Settings. In the short term, you can run DLO to
back up and restore desktop and laptop computers safely by using only the defaults set
during installation.
You can change default settings for profiles, backup selections and Global Settings.
Note Changes to Global Settings take place immediately and apply globally to all
Desktop Agents. Changes to the default profile and backup selection settings apply
only to new profiles and backup selections and do not affect those that already
exist.
Changing Default Profile Settings
The default DLO profile settings can be modified as described below.
▼ To change default profile settings
1. On the DLO navigation bar, click Setup.
2. On the task pane, under Tool Tasks, click Options.
3. In the properties pane, under New Profile Defaults , click General.
4. Set the options as explained in “General Profile Properties” on page 1020.
5. In the properties pane, under New Profile Defaults, click User Settings.
6. Set the profile user settings options as explained in “Profile User Settings Dialog
Box” on page 1023.
7. In the properties pane, under New Profile Defaults, click Schedule.
8. Set the profile schedule options as explained in “Profile Schedule Dialog Box” on
page 1027.
9. In the properties pane, under New Profile Defaults, click Options.
1000 Administrator’s Guide

Post Installation Tasks
10. Set the profile options as explained in “Additional Profile Options” on page 1029.
Changing Default Backup Selection Settings
The default DLO backup selection settings can be modified as described below.
▼ To change default backup selection settings
1. On the DLO navigation bar, click Setup.
2. On the task pane, under Tool Tasks, select Options.
3. Under New Backup Selection Defaults in the Properties pane, click Revisions and
set backup selection revision options as described in “Backup Selection Revision
Control” on page 1041.
4. In the Properties pane under New Backup Selection Defaults, click Options.
5. Set the backup selection options as explained in “Backup Selection Options” on
page 1042.
Changing Default Global Settings
The default DLO global settings can be modified as described below.
▼ To change default Global Settings
Note These settings apply immediately to all Desktop Agents.
1. On the DLO navigation bar, click Setup.
2. On the task pane underTool Tasks, select Options.
3. In the Properties pane under Global Settings, click Options.
4. Set global options as follows:
Global Settings Options
Item Description
Disable
1001

Post Installation Tasks
Global Settings Options
Item Description
All Desktop Agents Checking this box will prevent all Desktop Agents from backing
up.
Incremental backups of
Outlook PST files
Incremental backups of
Lotus Notes email files
Reports
Generate reports in PDF
format
Generate reports in
HTML format
Other
Time to delay Desktop
Agent startup after user
logs in
Desktop Agent low disk
error threshold
Desktop Agent low disk
warning threshold
Desktop Agent low quota
warning threshold
Check this box to prevent the incremental backup of Microsoft
Outlook PST files for all users.
See “Backing up Outlook PST files Incrementally” on page 1179
for additional information.
Check this box to prevent the incremental backup of Lotus Notes
files for all users.
See “Backing Up Lotus Notes NSF Files Incrementally” on
page 1180 for additional information.
Select Generate reports in PDF format to have reports run in pdf
format if the Adobe Acrobat Reader is installed. If the reader is not
installed, the reports will run in HTML format.
Select Generate reports in HTML format to have reports run in
html format.
Check this option and enter the number of seconds to delay the
start of the Desktop Agent after the user logs in. The Desktop
Agent start is only delayed if this option is checked and the
Desktop Agent is started from the startup menu.
Enter a percentage of available disk space. When there is less than
this percentage of disk space available, the Desktop Agent stops
writing to the desktop user data folder.
Enter a percentage of available disk space. When there is less than
this percentage of disk space available, a warning is issued.
Enter a percentage of the desktop user data folder storage limit. If
the available percentage of allocated disk space drops below this
level, a warning is generated.
For example, if the desktop user data folder is limited to 30 MB and
the low quota warning threshold is set at 10%, a warning is
generated when less than 3MB are available.
1002 Administrator’s Guide

Post Installation Tasks
5. In the Properties pane under Global Settings, click Desktop Agent Intervals.
6. Set the Desktop Agent Interval defaults as follows:
Desktop Agent Interval Options
Item Description
How long to wait before
retrying the backup of a
previously busy file
How long to wait before
retrying the backup of a
previously failed file
How long to retain
backups of files that
have been removed from
backup selections
Minimum time between
history updates
Minimum time between
postings of the same
alert
Enter the number of minutes DLO waits before it retries the
backup of previously busy file.
If the wait time is reduced, Desktop Agent computers spend more
CPU time and disk I/O trying to backup files if they are busy. If the
time is set higher, files are backed up less frequently. The
recommended default is 5 minutes.
Enter the number of minutes to wait before retrying the backup of
a file that previously failed to back up.
If the wait time is reduced, Desktop Agent computers spend more
CPU time and disk I/O trying to backup files that previously failed
to back up. If the time is set higher, files are backed up less
frequently. The recommended default is 60 minutes.
Enter the number of days to retain backups of files that have been
removed from backup selections.
Increasing the retention time causes the files to be left on the
server for a longer time after they have been removed from the
backup selection. Setting a shorter retention time provides more
space in the backup folders, but reduces the time during which
users can restore files that have been removed from the backup
selections. The recommended default is 30 days.
Enter the number of minutes to wait between history updates.
If there is a lot of activity, a reduced time between updates causes
the computers to spend more CPU time and disk I/O to update
history. A higher wait time reduces the frequency of history
updates. The recommended default is 15 minutes.
Enter the number of hours to wait between postings of the same
alert.
When there is a recurring alert, it shows up only once during the
specified time interval. If the time is set too low, the alert log can
fill up with multiple postings of the same alert. The recommended
default is 24 hours.
1003

Post Installation Tasks
Desktop Agent Interval Options
Item Description
Minimum time between
closing a job log and
starting a new one
Minimum time between
maintenance cycles
Minimum time between
checking for changes to
Lotus Notes email files
Time during which
Desktop Agents
randomly respond to
restart requests
7. In the Properties pane under Global Settings, click User Activity Settings.
8. Set the User Activity Settings defaults as follows:
User Activity Settings
Item Description
Enable user activity
restrictions
Limit network bandwidth
usage to
Enter the number of minutes to wait between closing a job log and
starting a new one.
When the time between job logs is reduced, more job logs appear.
The recommended default is 30 minutes.
Enter the number of minutes to wait between maintenance cycles.
A lower time between maintenance cycles means more CPU time
and disk I/O is spent conducting maintenance. Maintenance cycles
remove obsolete files and folders. The recommended default is
1440 minutes, which is 24 hours.
Enter the number of minutes between checks for changes to Lotus
Notes files.
A lower time results in more CPU time and disk I/O is used to
determine if Lotus notes files have changed. The recommended
default is 30 seconds.
Enter the number of minutes during which the Desktop Agents
will randomly respond to restart requests.
When a large number of Desktop Agents are restarted, for example
when network user data folders are moved, the Desktop Agents are
restarted randomly over a specified period of time. This prevents
the potential for overloading DLO by starting a large number of
Desktop Agents at the same time.
The recommended default is 30 minutes.
Check Enable user activity restrictions to determine how DLO
will perform tasks when users are interacting with their desktop
computers. User activity is based on typing and mouse movement.
Enter the maximum network bandwidth that DLO will use when
the user is interacting with the desktop computer.
1004 Administrator’s Guide

User Activity Settings
Item Description
Restrictions will be
removed when there has
been no user activity for
x seconds
Maximum scanner items
per second
9. In the Properties pane under Global Settings, click LiveUpdate.
10. Set the LiveUpdate defaults as follows:
LiveUpdate Options
Item Description
Enable Desktop Agent
scheduled automatic
updates
When checking for
updates
Post Installation Tasks
Enter the number of seconds of user inactivity after which DLO
will no longer restrict jobs.
Scanner items per second limits the number of items processed
per second during a file system scan. File system scans occur
during the first backup of a desktop computer, after an abnormal
system shutdown, or if the change journal is truncated. This
setting reduces the impact of the scan on the desktop computer
while the user is active.
Check Enable Desktop Agent scheduled automatic updates to
turn on scheduled automatic updates.
Select one of the following:
◆ Automatically download and install all available Desktop
Agent updates
◆ Only notify Desktop Agents of available updates (updates will
not be installed or downloaded)
Frequency Select one of the following as the frequency to use to check for
updates:
◆ Once
◆ Daily
◆ Weekly
◆ Monthly
Interval Select the time to check for updates. The specific options available
will vary with the frequency selected.
1005

Post Installation Tasks
Configuring DLO to Use a Specific Port for Database Access
You might want to configure DLO to use a specific port for database access. This may be
necessary, for example, if a fixed port is already being used for the SQL Server, you may
need to configure DLO to use the same port to access the DLO database.
▼ To configure DLO for alternate database access through a specific port:
1. Select a unique port number for the DLO database and then use svrnetcn.exe to set
the new port number.
2. On computers that run the DLO Administration Console from outside the firewall,
create the following registry key as a DWORD value if it does not exist and set the
DBUseTCP flag to 1:
HKLM\SOFTWARE\Symantec\DLO\3.0\AdminConsole\DBUseTCP
3. On computers that run the Desktop Agent from outside the firewall, create the
following registry key as a DWORD value if it does not exist and set the DBUseTCP
flag to 1:
HKCU\Software\Symantec\DLO\3.0\Client\DBUseTCP or
HKLM\SOFTWARE\Symantec\DLO\3.0\Client\DBUseTCP
4. Set the DBTcpPort on the computers modified in steps 2 and 3 to the port number
you set in step 1.
5. Restart the modified computers.
Using Backup Exec Retrieve With DLO
DLO can be configured to integrate with Backup Exec Retrieve, a feature of the Symantec
Continuous Protection Server (CPS). Backup Exec Retrieve allows desktop users to view,
search and restore files directly to their workstation using a web browser.
Backup Exec Retrieve is optimized for Microsoft Internet Explorer (6.0 or later). Backup
Exec Retrieve also works with other web browsers, although screen layouts may vary.
Backup Exec Retrieve is protected by Windows-level security. Desktop users are
prompted for Windows domain logon information. This information is used to restrict
the files that you can view and retrieve.
If you protect a server, users of Backup Exec Retrieve can only access files and folders
originally written to a share. That is, unless a folder is shared from a file server, you
cannot see or retrieve the files.
1006 Administrator’s Guide

Updating DLO
Updating DLO
To enable DLO integration with CPS, the CPS Continuous Management Service (CMS)
must be installed on the same computer as the Backup Exec Media Server. Additionally,
the administrator must install a Continuous Protection Agent (CPA) on each DLO file
server. The CPA installation can be performed by manually running setup on each
machine, or using the push-install mechanism in the CPS Administration Console. See
the Symantec Backup Exec Continuous Protection Server Administrator’s Guide for more
information.
Desktop users can search and restore files backed up with DLO as explained in “Restoring
files using Backup Exec Retrieve” on page 1204.
Updatesto Backup Exec are periodically provided by “Symantec LiveUpdate” or released
on CD. Updates to the Desktop Agent install set are included, although the Desktop
Agent updates are not automatically installed. DLO will now use Symantec LiveUpdate to
deliver selected security patches to the Desktop Agents. Backup Exec will use
LiveUpdate to deliver selected patches to the DLO Administration Console. Significant
upgrades will still be delivered using website downloads or CDs.
Updating the DLO Administration Console
The default installation directory for Backup Exec DLO version 11d and later is:
C:\Program Files\Symantec\Backup Exec\DLO
If Backup Exec DLO is upgraded from a previous version that was installed in a different
location, the installation will be moved to this new location.
▼ To update the DLO Administration Console:
1. Install the DLO Administration Console as directed in “Installing the Backup Exec
Desktop and Laptop Option” on page 987.
2. Start the DLO Administration Console and set a recovery password using the
Recovery Password Wizard, which automatically starts the first time DLO version
10.0 or later is opened after installation. For more information on the Recovery
Password Wizard, see “Setting a Recovery Password” on page 993.
3. If you are updating from DLO version 9.1, run the Data Integrity Scanner to detect
DLO backup files that are no longer being used, verify that all data is encrypted with
the most recent user key, and ensure that all data has the correct recovery key for
emergency restoration. See “Checking Data Integrity” on page 993 for additional
information.
1007

Updating DLO
Updating the Desktop Agent
As soon as the media server is updated, either through a full install, hotfix or Service
Pack release, the Desktop Agents will need to be updated in one of the following ways:
From the Desktop Agent Computer:
To manually update the Desktop Agents, from the Desktop Agent computer, run the
following:
\\\DLOAgent\update_10.0\Setup.exe.
From the Backup Exec Administration Console:
The Desktop Agent updates can also be remotely installed using the Backup Exec push
install feature.
From the DLO Administration Console using the Command Line Interface Tool:
The DLO Command Line Interface Tool can automatically offer updates to the Desktop
Agents using the publish command.
▼ To upgrade Desktop Agents from the DLO Administration Console using the Command
Line Interface:
1. Update the media server as directed in the update documentation.
2. From the command line on the media server, change to the DLO installation
directory.
Default installation directory:
Example C:\Program Files\symantec\Backup Exec\DLO
3. Run DLOCommandu.exe with the update option to add the configuration file and
make note of the ID number returned when this command is run:
DLOCommandu -update -add -f “dloagent\update_10.0\DLOAgentUpdate_BE.ini
Note If the configuration file has been moved or renamed, you will need to specify
the full path and file name in the command above.
Sample output:
ID=3
Name= 10.0 Update
1008 Administrator’s Guide

Updating DLO
Description=Updates Backup Exec DLO Desktop Agent from 9.1 to 10.0
Version=3.0 Build=3.XX.XX
srcPath=\\MediaServerName\DLOAgent\update_10.0
cmdPath=%DOWNLOADDIR%
cmdName=setup.exe
cmdArgs=-s
4. Run DLOCommandu.exe with the publish command to make the update available to
Desktop Agent users.
DLOCommandu -update -publish -UI y -U UserName
DLOCommandu -update -publish -UI y -P ProfileName
Where y is the ID number returned when the 'add' command was run in step 3.
Using an asterisk in place of UserName or ProfileName will publish the update
to all users.
When this command is executed, it will return a list of all users targeted for
update. Users will be updated the next time the Desktop Agent application is
started.
Note For more information on the -update command and additional command
options, see “-Update Command” on page 1149.
Related Topics:
“DLO Command Line Interface Management Tools” on page 1139
Running the Desktop Agent Upgrade Silently
Desktop Agents can be upgraded silently. During a silent upgrade, the user will not be
prompted to download and start the upgrade, but they will still be prompted to confirm
that they want to actually perform the upgrade.
▼ To run the Desktop Agent upgrade silently:
1. From the Desktop Agent upgrade folder, open the DLOAgnetUpdate_BE.ini file for
editing.
2. Set PromptUser=0.
3. Save and Close the file.
1009

Updating DLO
4. Run the upgrade using one of the methods described in “Updating the Desktop
Agent” on page 1008.
Upgrading From NetBackup Professional to DLO
The NetBackup Professional (NBUP) to Desktop Agent upgrade is only available for
NBUP customers running version 3.51.20 or later. If you are not running 3.51.20,
consider upgrading your NBUP server and clients before upgrading to the Desktop
Agent.
This mechanism installs the Desktop Agent onto desktop computers that are currently
running the NBUP client. You can remove the NBUP client when installing the Desktop
Agent or leave the NBUP client installed and run both applications concurrently. These
two options will appear as separate upgrades in the NBUP Console, so you can remove
NBUP from some profiles and continue to run NBUP for other profiles.
The upgrade from NBUP to DLO requires two additional components that are distributed
with the Desktop Agent install set:
■ A DLO Client (Remove NBUP).VPK file that contains instructions and an executable
to upgrade the system to DLO and remove NBUP at the same time.
■ A DLO Client (Leave NBUP).VPK file that contains instructions and an executable to
upgrade the system to DLO and leave NBUP installed but increment the version
number so that it appears NBUP was upgraded.
MDAC Version Support for the Desktop Agent
DLO supports versions 2.7 and 2.8 of Microsoft Data Access Components (MDAC),
however MDAC 2.8 is the default and is installed during the Desktop Agent installation if
it is not already installed. When MDAC 2.8 is installed, a restart may be required, and a
computer administrator must complete the installation process. If a non-administrator
logs on first after the MDAC 2.8 installation, the process generates a number of errors.
To avoid these errors when MDAC 2.7 is already installed, you can force the use of MDAC
2.7 by modifying the package.ini file in the Upgrades folder created in step 3 below. In
the package.ini file, add REQUIREDMDACVERSION=”2.7” to the DefaultRuleXML line.
Example:
DefaultRuleXML=TRANSFORMS=”%%%%LANG_FILE%%%%
” REBOOT=ReallySuppress LAUNCHCLIENT=”0” REQUIREDMDACVERSION=”2.7”
setup.ini
1010 Administrator’s Guide

▼ To upgrade from NetBackup Professional to DLO:
Updating DLO
1. Contact Technical Support to receive the NBUP to Desktop Agent upgrade. The two
files you will need are DLOAgent_LeaveNBP.vpk and DLOAgent_RemoveNBP.vpk.
2. From the NBUP server, or any computer with the NBUP console installed, launch the
appropriate file; DLO Client (leave NBUP).vpk or DLO Client (remove NBUP).vpk.
This will upload the upgrade package to the NBUP server. Repeat this process for the
other vpk file to make make both the leave and remove NBUP options available for
selection in various profiles.
3. Create a folder entitled DLOAgent in C:\Program Files\Veritas NetBackup
Professional\Upgrades, or in the appropriate location if you installed NBUP in a
location other than the default.
4. Copy the entire contents of the DLOAgent share on the media server into the
DLOAgent folder on the NBUP server.
5. Launch the NBUP Console.
6. Open the profile properties and select the Upgrades tab. Select the appropriate
upgrade (leave NetBackup Professional or remove NetBackup Professional) and
enable it by checking the Enable this upgrade check box. Select the other options
you want for this upgrade.
7. through step 6 for each NBUP Profile you want to upgrade to DLO.
8. Follow the standard procedure for upgrading NBUP (“Check for upgrade now” in the
console or refresh the client). See the NetBackup Professional Administrator’s Guide
for additional information.
If the Desktop Agent installation is successful, the NBUP version number in the
NBUP administration console will change to 9.1.0.0 for computers that still have
NetBackup Professional installed or 0.0.0.1 for computers on which NetBackup
Professional was removed.
1011

Using the DLO Administration Console
Using the DLO Administration Console
Backup Exec DLO Administration Console
Main menu bar Navigation bar Results pane
Task pane Selection pane Preview pane Status bar
The DLO Administration Console is launched from the Job Setup view in Backup Exec.
From the DLO Administration Console you can configure DLO and manage desktop
backup and restore operations.
1012 Administrator’s Guide

Using the DLO Administration Console
▼ To access the DLO Administration Console from Backup Exec or the Backup Exec Web
Administration Console (BEWAC):
1. On the navigation bar, click Job Setup.
2. In the task pane under Backup Strategy Tasks, click Configure desktop and laptop
backups.
Accessing DLO from the Backup Exec Administration Console
Related Topics:
“Configuring DLO” on page 1019
“About DLO Storage Locations” on page 1053
“About DLO Profiles” on page 1020
“About Automated User Assignments” on page 1060
“Managing Desktop Agent Users” on page 1074
1013

Using the DLO Administration Console
Showing the Task Pane
When it is turned on, the Task Pane appears on the left side of the DLO Administration
Console. Actions can be initiated from the Task Pane, and these actions vary with the
selected view.
▼ To show the Task Pane:
❖ From the View menu, verify that Task Pane is checked, or select it.
Using the DLO Overview View
The DLO Overview view provides two options, the Getting Started view and a System
Summary.
The Getting Started View
The Getting Started view provides convenient links to help you set up and manage DLO.
From this page, you can easily perform the following tasks or access the help associated
with them:
■ Create a profile
■ Create a Storage Location
■ Create an Automated User Assignment
■ Add users
■ Deploy the Desktop Agent
■ Set preferences and default settings
■ Manage alerts and notifications
■ Run reports
1014 Administrator’s Guide

Backup Exec Getting Started View
▼ To access the Getting Started view:
1. On the DLO navigation bar, click Overview.
2. Click the Getting Started tab.
System Summary
Using the DLO Administration Console
The System Summary overview provides the DLO administrator with a brief summary of
the current state of desktop backups, server status, and alerts.
1015

Using the DLO Administration Console
Backup Exec DLO System Summary
▼ To access the DLO System Summary
1. On the DLO navigation bar, click Overview.
2. Click the System Summary tab.
1016 Administrator’s Guide

Using the DLO Administration Console
The following information is available in the System Summary overview:
System Summary
Item Description
Desktop Computer Status Summary
Last Backup Result Summarizes the completion status of the last operation performed
on each computer protected by DLO. Totals are provided for the
number of computers that completed the last job successfully, with
errors, with warnings, or for which the last job was cancelled.
◆ With Errors - The last operation was completed, but errors were
generated.
◆ With Warnings - The last operation was completed, but
warnings were generated.
◆ Cancelled - The job was cancelled or refreshed by the user
during the job.
◆ Successful - The job was successfully completed without
warnings or errors, and it was not cancelled or refreshed by the
user during the job.
Note Errors take precedent over warnings, so if there are both
errors and warnings, the last backup result will say With
Errors.
Pending Jobs Lists restore jobs requested by the DLO administrator that have not
yet been run.
Alert Summary
Active Alerts Lists alerts that have not been cleared by the DLO administrators
and have not yet been removed by the alert grooming process. Alert
grooming is managed from the Backup Exec Administration
Console. See “Configuring alert category properties” on page 540
for additional information.
Server Summary
Server Status Lists the status of each DLO server.
Server status can be Running or Stopped.
Server Load Lists the number of desktops being protected by DLO and the total
number of installed Desktop Agent users. These numbers may not
be the same if some users are protecting multiple computers with
DLO. Both online and offline users are counted.
1017

Connecting to DLO on a different Backup Exec Media Server
Connecting to DLO on a different Backup Exec Media Server
To connect to DLO on a different Backup Exec media server, the user account needs to
have full administrator rights to the media server and it must also be a domain account.
▼ To connect to DLO on a Backup Exec media server:
1. On the DLO Administration Console Network menu, click Connect to Media Server.
2. Select the appropriate options as follows:
Connect to media server dialog box options
Item Description
Server Enter the name of the media server you want to connect to, or
select a media server from the drop-down menu.
Login information
User name Type the user name for an account with administrator access to the
media server.
Password Type the password for this account.
Domain Enter the domain for this account.
3. Click OK.
Related Topics
“About Administrator Accounts” on page 996
1018 Administrator’s Guide

Configuring DLO
Configuring DLO
In order for DLO to back up user data, you must set up the following options in the
following order:
1. Create a profile, which determines what files are backed up, when the files are backed
up, and the level of interaction the desktop user has with the Desktop Agent.
For additional information, see “About DLO Profiles” on page 1020.
2. Determine where user data will be stored on the network. DLO requires an individual
user data folder on the network for each desktop user. If Storage Locations are used,
they will automatically create network user data folders for each new Desktop Agent
user. If network data storage folders already exist for each user, they can be added to
DLO individually or many users can be imported at one time using a list.
For additional information, see “About DLO Storage Locations” on page 1053 and
“Managing Desktop Agent Users” on page 1074.
3. Create an Automated User Assignment to automatically assign a Storage Location
and profile to new users, or configure new users manually.
For additional information, see “About Automated User Assignments” on page 1060.
You can set up DLO by using the Desktop and Laptop Configuration Wizard, or by setting
options manually. The DLO configuration wizard provides a series of wizards that help
you set up DLO in the correct order.
The configuration wizard appears when the DLO Administration Console is opened
unless the Always show this wizard at startup box is unchecked. The configuration
wizard can also be accessed as described below.
▼ To access the Configuration Wizard:
1. On the DLO navigation bar, click Setup.
2. On the task pane under Getting Started, select DLO Configuration using wizard.
3. If you want the Configuration Wizard to display each time the DLO Administration
Console is started, select Always show this wizard at startup.
Related Topics:
“About DLO Profiles” on page 1020
“About DLO Storage Locations” on page 1053
“About Automated User Assignments” on page 1060
“Managing Desktop Agent Users” on page 1074
1019

About DLO Profiles
About DLO Profiles
Profiles are used to customize settings for specific groups of similar users. For example, a
group of highly technical users may require the ability to modify the backup selections
and schedules while less experienced users may require a fully automated backup
service. In a profile, you can set the following:
■ Backup file and folder selections
■ Desktop and network user data folder storage limits
■ Backup schedules
■ The desktop user’s level of interaction with the Desktop Agent
■ Logging options
■ Network bandwidth usage
You cannot modify settings for individual Desktop Agent users from the DLO
Administration Console unless an individual user is the only user assigned to a profile.
However, you can grant permission to Desktop Agent users to modify their own settings.
Creating a New Profile
New profiles can be created to meet the specific needs of desktop users, and to support
the existing IT environment.
▼ To create a new profile:
1. On the DLO navigation bar, click Setup.
2. In the Settings pane, click Profiles.
3. In the task pane under Settings Tasks, click New Profile.
4. Click the General tab in the New Profile dialog box.
5. Select the appropriate options as follows.
General Profile Properties
Item Description
Profile Name Type the name of the new profile that you want to create. The profile
name cannot contain any of the following characters:
\”@#$%^&*()=+|/{}[]’
1020 Administrator’s Guide

General Profile Properties (continued)
Item Description
Description Type a description for the profile.
About DLO Profiles
Enable Profile Clear this check box to disable the profile. Profiles are enabled by default.
User Bandwidth Settings
Limit bandwidth
(KB/sec)
Yield bandwidth to
other programs
Storage Limits
Limiting the bandwidth for DLO data transfer is a means to manage the
trade-off between backup speed vs. the impact of backups on the local
computer, network, and server. The default limit is meant to be a
conservative setting to minimize the impact of backups, but many factors
come into play, such as network speed, connection type, the amount of
data backed up and the total number of computers backing up to DLO.
If computer performance is not impacted, but DLO data transfer is slow, a
higher bandwidth setting may be more suitable. If computer
performance is noticeably impacted during backups, a lower value will
reduce the impact of backups on computer performance, but backups will
take longer to complete.
Select Limit bandwidth (KB/sec) and enter a specific maximum
bandwidth setting to control the rate at which data is sent to the network
user data folder.
Data transfer is only limited when data is written to the network user
data folder, not when it is written to the desktop user data folder. Data
transfer is not limited during the incremental backup of Outlook PST
files or Lotus Notes NSF files.
Enables DLO to reduce data transfer over the network when other
applications on the desktop computer are transferring data. DLO
automatically resumes normal data transfer rates when other
applications are not using this resource.
The yield bandwidth option monitors network traffic on the desktop
computer. If DLO is using more than 90% of the total current traffic, DLO
is not throttled. When DLO traffic drops below 90% of the total network
traffic on the desktop, and total traffic is over 60% of the maximum
traffic seen on the connection, then DLO throttles itself to use only the
otherwise unused portion of the connection. For example, if there was
70% total usage, DLO will throttle itself to 30% of maximum.
Note Selecting this option can improve system performance when other
network-intensive applications are running at the same time. Data
transfer is only limited when data is written to the network user
data folder, not when it is written to the desktop user data folder.
1021

About DLO Profiles
General Profile Properties (continued)
Item Description
Limit network user
data folder to (MB)
Enable desktop
user data folder
Limit desktop user
data folder to
Limits the disk space available on the network to store DLO backup files
and type the amount of space you want to use for storage.
Enables the use of the desktop user data folder.
When Enable desktop user data folder is checked, files are copied to the
desktop user data folder first, and then they are copied to the network
user data folder from the desktop user data folder. This is true even when
DLO is configured to keep zero revisions in the desktop user data folder.
When Enable desktop user data folder is unchecked, files are copied
straight to the network user data folder from the original location.
Advantages to enabling the desktop user data folder:
◆ Offline protection is provided because revisions can be stored locally
as well as on the network.
◆ Because files are more quickly saved to the local computer than to the
network, the time a file is held open for backup is reduced.
Advantages to disabling the desktop user data folder:
◆ If local revisions are not required, this option will prevent backup
files from being stored in the desktop user data folder. No revisions
are saved in the desktop user data folder even if backup selections
specify that a certain number of revisions should be stored locally.
◆ Works well for desktop users with very limited disk space.
◆ When the DLO administrator disables the desktop user data folder or
the number of revisions retained in this folder is set to zero, DLO will
still create empty place holders in the desktop user data folder. The
place holders can be seen in the Desktop User data folder, but contain
no data. They indicate which files and folders have been backed up
and saved to the network user data folder.
Limits the disk space available to store DLO backup files.
A percentage of the total disk space (%)
Select this option and enter a percentage to limit the amount of disk
space used for storing backup files in the desktop user data folder to a
percentage of the local drive.
A size (MB)
Select this option and enter a size in MB to limit the desktop user data
folder to a specific maximum size.
Note While limiting available disk space for the desktop user data folder
can prevent overloading of the desktop hard drive, backups can fail
to run if the desktop user data folder space limit is reached.
1022 Administrator’s Guide

About DLO Profiles
6. From the backup selections tab, click the backup selections that you want to apply to
users of this profile.
You can add, modify, and delete backup selections for a profile from this dialog box.
When a new backup selection is created, it is available for selection in all profiles.
Changes made to a backup selection in one profile will impact all other profiles that
use the backup selection. Similarly, when a backup selection is deleted, the change
impacts all profiles that use the backup selection. For more information, see “About
Backup Selections” on page 1033.
7. From the User Settings tab, select the appropriate options as follows:
Note When a user is given the ability to change any of the following settings, the new
settings will apply only to that user and not to other users assigned to the same
profile.
Profile User Settings Dialog Box
Item Description
Desktop Agent display
settings
Select one of the following options to determine the desktop user’s
level of interaction with the Desktop Agent:
◆ Display the complete interface. Select this option to enable
desktop users to access all Desktop Agent options.
◆ Display only the status. Select this option to enable desktop
users to view the status of backup jobs. With this option,
desktop users cannot change settings for the Desktop Agent or
access any options other than the status.
Desktop users can right-click the system tray icon to open the
status view or exit the program.
◆ Display only the system tray icon. Select this option to display
the Desktop Agent icon in the system tray in the lower right
corner of the screen.
Desktop users can right-click the system tray icon to exit the
program.
◆ Do not display anything. Select this option to run the Desktop
Agent in the background. The desktop user cannot view the
Desktop Agent.
1023

About DLO Profiles
Profile User Settings Dialog Box (continued)
Item Description
Allow Users to Select the options below to enable desktop users to configure the
following features of the Desktop Agent. These options are only
available if Display the complete interface was selected above.
Restore data When selected, users in this profile can restore their backed up
files.
For more information, see “Restoring Files Using the Desktop
Agent” on page 1199.
Add user-defined backup
selections
Modify profile backup
selections
Customize backup
selection revision policy
settings
Change backup selection
encryption settings
Change backup selection
compression settings
Customize profile logging
settings
Enables users in this profile to create and modify backup
selections. This option does not allow users to modify backup
selections made by the DLO administrator in the profile.
Note With this option selected, users can add a backup selection
that will back up a folder that is excluded from the profile
backup selections. The only way to prevent users in a profile
from backing up a specific folder is to uncheck this option.
For more information, see “About Backup Selections” on
page 1033, “Modifying Backup Selections in the Standard View”
on page 1170 or “Modifying Backup Selections in the Advanced
View” on page 1177.
Enables users in this profile to modify backup selections created
by the DLO administrator for the profile. For more information,
see “About Backup Selections” on page 1033 or “Modifying Backup
Selections in the Advanced View” on page 1177.
Enables users in this profile to modify the revision policy settings.
Users cannot change these settings if this option is not checked.
For more information, see “Backup Selection Revision Control
Dialog Box” on page 1175.
Enables users in this profile to turn encryption of backup files on
or off. For more information, see “Backup Selection Options” on
page 1176.
Enables users in this profile to turn compression of backup files
on or off. For more information, see “Backup Selection Options”
on page 1176.
Enables users in this profile to customize profile logging settings.
For more information, see “Setting Customized Options” on
page 1185.
1024 Administrator’s Guide

Profile User Settings Dialog Box (continued)
Item Description
Customize profile email
settings
Move local user data
folder
Change groom policy
settings
About DLO Profiles
Enables users in this profile to customize mail settings in the
profile. For more information, see “Setting Customized Options”
on page 1185.
Enables users in this profile to move the local user data folder to a
new location. For more information, see “Moving the Desktop
User Data Folder” on page 1187.
Enables users in this profile to customize grooming settings.
For more information, see “Setting Customized Options” on
page 1185.
Synchronize files Enables users in this profile to synchronize data across all of their
computers that run the Desktop Agent.
For more information, see “Synchronizing Desktop User Data” on
page 1190.
Customize local disk
quota
Enables users in this profile to limit the amount of disk space that
can be used to store backup files in the desktop user data folder.
For more information, see “Setting Customized Options” on
page 1185.
Modify backup schedule Enables users in this profile to modify the schedule on which their
files are backed up.
For more information, see “Changing Backup Job Schedule
Options” on page 1183.
Customize connection
policies
Cancel scheduled or
manual jobs
Enables users in this profile to customize connected based
policies.
For more information, see“Customizing Connection Policies” on
page 1188.
Enables users in this profile to cancel both scheduled and
manually initiated jobs. Scheduled jobs will run again at the next
scheduled time. Manual jobs must be restarted manually.
For more information, see “Suspending or Cancelling a Job” on
page 1196.
Suspend jobs Enables users in this profile to suspend jobs for a specified
amount of time. For more information, see “Suspending or
Cancelling a Job” on page 1196.
1025

About DLO Profiles
Profile User Settings Dialog Box (continued)
Item Description
Disable Desktop Agent Enables users in this profile to disable the Desktop Agent from the
tray icon. They will also have the ability to re-enable the Desktop
Agent once it has been disabled.
Work Offline Enables users in this profile to set the Desktop Agent to work
offline. See “Changing Your Connection Status” on page 1163 for
additional information.
Save encrypted
passwords used by DLO
Suppress errors and
warnings
When user goes offline,
automatically go back
online after
When user suspends a
job or disables the
Desktop Agent,
automatically resume or
enable after
8. Click the Schedule tab.
Check Save encrypted passwords used by DLO to allow users to
automatically authenticate to the media server or storage location
in the event of an authentication failure. This could happen, for
example, when the desktop user logs in using a local or
cross-domain account. Keeping this option unchecked will cause
DLO to prompt the user to enter a password each time DLO
authenticates to a DLO resource while using an account which
requires domain credentials in order to authenticate to a DLO
resource.
Check this option to prevent error and warning message boxes
from being displayed when a user is not interacting with the
Desktop Agent.
Enter the time after which a user will automatically go back online
after they have manually placed the Desktop Agent in an offline
state.
Enter the time after which a job will be resumed or the Desktop
Agent enabled after the user suspends a job or disables the
Desktop Agent.
1026 Administrator’s Guide

9. Select the appropriate options as follows:
Profile Schedule Dialog Box
Item Description
Run backups
About DLO Profiles
Whenever a file changes Select this option to back up files whenever they change.
On NTFS drives, backups will occur automatically whenever a file
changes. For FAT drives, you must enter a backup interval in the
Back up changed files every field.
According to a schedule Select this option to back up files according to a customized
schedule.
Click Edit schedule to configure the backup schedule. The backup
schedule is configured in step 10.
When initiated by the
user
Logout/Restart/Shutdown options
Select this option to enable desktop users to determine when to
back up their files.
Do nothing Select Do nothing from the drop-down menu to proceed with a
logout, restart or shutdown even when there are files that require
backup.
Note If a job is already running, a prompt asks if the user would
like to logout, restart or shutdown when the job is complete.
Prompt user to run job Select Prompt user to run job from the drop-down menu to have
DLO ask if a backup should be run before proceeding with the
logout, restart or shutdown.
Note If a job is already running, a prompt asks if the job should be
cancelled in order to continue with the logout, restart or
shutdown.
Run job immediately Select Run job immediately from the drop-down menu to back up
waiting files without prompting before proceeding with a logout,
restart or shutdown.
Note If a job is already running, a prompt asks if the job should be
cancelled in order to continue with the logout, restart or
shutdown.
1027

About DLO Profiles
Profile Schedule Dialog Box (continued)
Item Description
Run job as scheduled Select Run job as scheduled from the drop-down menu to proceed
with a logout, restart or shutdown and back up files according to
the schedule.
Note If a job is already running, a prompt asks if the job should be
cancelled in order to continue with the logout, restart or
shutdown.
Run job at next login Select Run job at next login from the drop-down menu to proceed
with a logout, restart or shutdown without prompting, and run a
job the at the next login.
Note If a job is already running, a prompt asks if the job should be
cancelled in order to continue with the logout, restart or
shutdown.
10. If you selected Edit schedule in the previous step, select the appropriate options as
follows, and then click OK:
Backup Schedule Dialog Box
Items Description
Run on these days Select the days on which you want to back up files.
Frequency
Run once at Select this option to run a single backup on the days you selected at
the time specified.
Run every Select this option to run backups at the specified time interval on
the days you selected.
From If you selected Run every, select the beginning of the time interval
over which you want backups to begin.
1028 Administrator’s Guide

Backup Schedule Dialog Box (continued)
Items Description
11. Click the Options tab.
12. Select the appropriate options as follows:
About DLO Profiles
Until If you selected Run every, select the end of the time interval over
which you want backups to begin.
Note This field specifies the end of the time period within which
backups will begin. If a backup is in progress at this time, it
will continue to run to completion.
Start backup jobs over a
period of
Select this option to stagger start times for backup jobs. Rather than
starting all backup jobs at exactly the time indicated, DLO will
distribute the start times over the specified interval to better
distribute the demands on the server and network.
Note Events such as file copies, file grooms, errors and warnings are logged by DLO
and can be viewed as discussed in “Monitoring Alerts on the DLO
Administration Console” on page 1105.
Additional Profile Options
Item Description
Log file maintenance
Keep log files for a
minimum of (days)
After minimum number
of days, delete oldest log
files when combined size
exceeds (MB)
Logging options
Specify the minimum number of days to keep log files. Log files
will not be deleted until they are at least as old as specified.
Note Log files will not be deleted until their combined size
exceeds the setting for the combined size of all log files,
which is discussed below.
Enter the maximum combined size of all log files to be retained
before the oldest log files are deleted.
Note You may have more than the specified number of MB of log
files stored if none of the log files is as old as specified in the
Keep log files for a minimum of (days) setting.
Log groom messages Select this check box to create logs for grooming operations.
1029

About DLO Profiles
Additional Profile Options (continued)
Item Description
Log information
messages for backup
13. Click the Connection Policies tab to disable or limit backups for specific connection
types.
14. Click Add.
Select this check box to create logs for all backup operations.
Log warning messages Select this check box to create logs for all operations that generate
warnings.
Mail options
Enable incremental
backups of Outlook PST
files
Enable incremental
backups of Lotus Notes
email files
Select this check box to enable incremental backups of Microsoft
Outlook Personal Folder (PST) files. Incremental backups must be
enabled to allow PST files to be backed up while they are open.
If this option is not checked, PST files that are configured in
Outlook will be fully backed up each time the PST file is saved,
which generally occurs when Outlook is closed.
When Outlook PST files are backed up incrementally, only one
revision is maintained regardless of the number of revisions set in
the backup selection.
Note Microsoft Outlook must be your default mail application for
DLO to perform incremental backups of PST files.
Note Synchronized files cannot be backed up incrementally.
For additional information, see “Backing up Outlook PST files
Incrementally” on page 1179.
Select this check box to enable incremental backups of Lotus
Notes email files. Additional configuration may be necessary. See
“Backing Up Lotus Notes NSF Files Incrementally” on page 1180.
When Lotus Notes NSF files are backed up incrementally, only one
revision is maintained regardless of the number of revisions set in
the backup selection.
1030 Administrator’s Guide

15. Create a new connection policy and configure it as follows:
Add/Edit Connection Policy
Item Description
Connection Type
About DLO Profiles
Dialup Select Dialup from the drop-down menu to limit or disable
backups when using a dialup connection.
IP address range Select IP address range from the drop-down menu to limit or
disable backups for a specific IP address range.
Specify whether you want the connection policy to apply to
computers that are or are not in the IP address range you specify.
Select IPv6 or IPv4 and enter the IP address range for the
connection policy.
Note IPv6 addresses are only supported on Windows XP and later
operating systems and will not be enforced for Desktop
Agents running on Windows 2000. An additional connection
policy using IPv4 addresses may be desired for Desktop
Agents on Windows 2000 computers.
Active Directory Select Active Directory from the drop-down menu to limit or
disable backups using Active Directory. Select Configure to
configure the Active Directory settings. See “Customizing
Connection Policies” on page 1188 for details on configuring
connection policy settings for Active Directory.
Desktop Agent Behavior
Disable network backup Select Disable network backup to prevent users from backing up
to the network user data folder. Backups will continue to the
desktop user data folder.
Disable network backup
for files greater than
Limit network bandwidth
usage to
Select Disable network backup for files greater than to prevents
users from backing up files larger than a specified size based on
the connection type. Enter a files size in KB.
Select Limit network bandwidth usage to and enter a value in
KB/sec to restrict the usage of network bandwidth to the specified
value.
1031

About DLO Profiles
Add/Edit Connection Policy
Item Description
Enforce policy according
to scheduled window
16. Click OK.
Related Topics:
“About Backup Selections” on page 1033
“Monitoring Alerts on the DLO Administration Console” on page 1105
“Modifying Desktop Agent Settings” on page 1182
Copying a Profile
When you create a new profile, it may be desirable to begin with a copy of an existing
profile with a configuration similar to that required for the new profile. The copy can
then be modified as required to meet the needs of a new group of desktop users.
▼ To copy a profile:
1. On the DLO navigation bar, click Setup.
2. In the Settings pane, click Profiles.
3. Right click on the profile you want to copy.
4. Click Copy.
5. Type a name for the new profile.
6. Type a description of the new profile.
7. Click OK.
Check the Enforce policy according to scheduled window to cause
the connection policy to apply only during the specified period of
time.
Click Schedule to set the time during which the policy will be in
affect. Schedules can be set to run weekly or for a specific date
range.
1032 Administrator’s Guide

Modifying a Profile
About Backup Selections
Profiles can be modified as required to meet the changing needs of user groups.
Note Modifications to a profile will cause users of that profile to cancel jobs, load
settings, restart backup engines and scan their backup selection tree.
▼ To modify a profile:
1. On the DLO navigation bar, click Setup.
2. In the Settings pane, click Profiles.
3. In the Results pane, select the profile you want to modify.
4. In the task pane, under General Tasks, click Properties.
5. Modify the profile properties as needed.
6. Click OK.
Related Topics
“Creating a New Profile” on page 1020
About Backup Selections
Backup selections specify which files and folders you want to back up on desktops.
Backup selections created by DLO administrators within profiles are called profile
backup selections. Desktop users can also create backup selections or modify profile
backup selections if the DLO administrator has provided them with sufficient rights.
Backup selections are easily customized to meet a wide variety of needs. With in each
backup selection you can:
■ Specify the path to be backed up.
■ Choose to include or exclude subfolders, file types, or specific folders.
■ Set the number of revisions retained for each file in the backup selection, the
frequency with which they are saved, and instructions on how long to retain backup
files.
■ Configure the backup selection to transfer only the changed portions of files.
■ Compress or encrypt the files for transmission and storage.
1033

About Backup Selections
■ Specify how long to retain backup files after the source files are deleted.
Caution Symantec strongly recommends that you consider disk space when choosing
backup selections for desktops and laptops. A large number of local copies may
cause the Desktop Agent user's computer to run out of disk space. For example,
you may want to avoid selecting entire drives for backup or synchronization.
Related Topics:
“Default Backup Selections” on page 1034
“Removing Default Backup Selections From a Profile” on page 1035
“Adding a Backup Selection” on page 1035
“Defining General Backup Selection Properties” on page 1037
“Including and Excluding Files or Folders from a Backup Selection” on page 1038
“Revision Control” on page 1039
“Setting Options for a Backup Selection” on page 1042
“Using DLO Macros in Backup Selections” on page 1044
“Modifying a Backup Selection” on page 1046
“Deleting Backup Selections” on page 1046
Default Backup Selections
DLO is configured to back up commonly used files and folders by default. You can add
additional backup selections or cancel the use of default backup selections. The
following are backed up by default:
Default Backup Selections
Backup Selection Description
My Documents All files in My Documents
My Favorites Internet Explorer Favorites
Outlook PST Files PST files in the default location
My Desktop All files on the Desktop
Notes Files (Multi-user) Lotus Notes data for multiple user install
1034 Administrator’s Guide

Default Backup Selections
Backup Selection Description
Notes Archive (Multi-user) Lotus Notes archive for multiple user install
Notes Files (Single-user) Lotus Notes data for single user install
Notes Archive (Single-user) Lotus Notes archive for single user install
About Backup Selections
Note The default backup selections assume applications are using default paths. If
custom paths were used during installation or modified thereafter, you will need to
customize the backup selections to insure they work properly. See “Modifying a
Backup Selection” on page 1046 for additional information.
Removing Default Backup Selections From a Profile
Default profile backup selections are appropriate for most DLO installations. In some
cases, it may be desirable to remove or replace default backup selections.
▼ To remove default backup selections from a profile:
1. On the DLO navigation bar, click Setup.
2. In the Settings pane, click Profiles.
3. In the Results pane, select the profile you want to modify.
4. In the task pane, under General Tasks, click Properties.
5. Click the Backup Selections tab.
6. Uncheck those backup selections you do not want to use.
7. Click OK.
Adding a Backup Selection
When a new backup selection is created for a profile, that profile backup selection is
available for selection in all other profiles.
1035

About Backup Selections
▼ To add a backup selection:
1. On the DLO navigation bar, click Setup.
2. In the Settings pane, click Profiles.
3. In the Results pane, select the profile for which you want to add a backup selection.
4. In the task pane, under General Tasks, click Properties.
5. Click the Backup Selections tab in the Profile Properties dialog box.
6. Click Add.
A dialog box explains that if you customize NTFS permissions or directory attributes
such as compression or encryption for backed up files or folders, these settings will
not be backed up. You must reapply these settings after restoring the files. If you use
a password for a Microsoft Outlook PST file, you must reset the password after
restoring a PST file.
7. Read the message that displays, and then click OK.
8. Do any of the following to customize the backup selection properties:
■ To set general backup selection properties including the name, description and
folder to be backed up, see “Defining General Backup Selection Properties” on
page 1037.
■ To include or exclude specific files from this backup selection, see “Including and
Excluding Files or Folders from a Backup Selection” on page 1038.
■ To set revision control for this backup selection, see “Setting Revision Control for
a Backup Selection” on page 1040.
■ To set Delta File Transfer, encryption and compression options for this backup
selection, see “Setting Options for a Backup Selection” on page 1042.
9. Click OK twice.
1036 Administrator’s Guide

Defining General Backup Selection Properties
About Backup Selections
When a backup selection is created, the name, description and path to be backed up are
specified in the backup selection general dialog box. Once the backup selection is
created, the name, description and backup path can be modified as needed.
1. Open the Backup Selection dialog box as described in one of the following
procedures:
■ “Adding a Backup Selection” on page 1035
■ “Modifying a Backup Selection” on page 1046
2. From the General tab in the Backup Selection dialog box, select the appropriate
options as follows:
Backup Selection General Dialog Box
Item Description
Name Type a descriptive name for the backup selection.
Description Type a clear description of the backup selection. This description
may include, for example, the folder selected, the group of users it
was created for, or the purpose for creating the backup selection.
Folder to back up
Type a folder name Select this option to add a specific folder to the backup selection.
Type the path to the folder, including the folder name. For
example, to add a folder named MyData on drive C, type
C:\MyData.
Note See “Using DLO Macros in Backup Selections” on page 1044
for information on using macros to define the folders
backed up by a backup selection.
Select a pre-defined
folder
3. Click OK.
Select this option to choose a pre-defined folder from the list
provided.
Note See “Using DLO Macros in Backup Selections” on page 1044
for information on the macros used to define the
pre-defined folders.
Include subfolders Check this option to also back up all subfolders in the specified
directory. This option is selected by default.
1037

About Backup Selections
Including and Excluding Files or Folders from a Backup Selection
Each backup selection can be configured to either include all files and folders, or to
include or exclude specific files and folders. In addition, specific file types or folders can
be specified for inclusion or exclusion using wildcards.
Files and folders can also be excluded from all backups for all users using global exclude
filters. Several file types are excluded by default. These global excludes can be viewed or
modified in the Global Excludes dialog box.
Related Topics:
“DLO Default Settings” on page 1000
“Configuring Global Exclude Filters” on page 1065
▼ To include or exclude files or folders from a backup selection:
1. Open the Backup Selection dialog box as described in one of the following
procedures:
■ “Adding a Backup Selection” on page 1035
■ “Modifying a Backup Selection” on page 1046
2. From the Include/Exclude tab in the Backup Selection dialog box, select the
appropriate options as follows:
Backup Selection Include/Exclude Dialog Box
Item Description
Include all file types Select this option to include all file types in this backup selection.
Include and exclude only
the items listed below
Select this option to include or exclude only specific files or file
types. When this option is selected, a wildcard include is added to
back up all files not specifically excluded.
3. To add a filter to the Include/Exclude list, verify that you selected Include and
exclude only the items listed below in step 2, and click Add Include or Add Exclude.
4. If you selected Add Exclude, you will be notified that all previously backed up files
matching this exclude will be deleted from this backup selection. Click Yes to
continue or No to cancel.
1038 Administrator’s Guide

5. Select the appropriate options as follows:
Add Include Filter or Add Exclude Filter Dialog Box Options
Item Description
6. Click OK.
Revision Control
About Backup Selections
Filter Type the name of the file or the folder that you want to include or
exclude. You can use wildcards.
For example, type *.mp3 to either include or exclude all files with
the file extension .mp3, or type unimportant.txt to include or
exclude all files in the backup selection with this specific file name.
Click Extensions to select a predefined filter to either include or
exclude all files with a given file extension.
Description Type a description of this include or exclude filter.
Apply to Select one of the following:
◆ Files to apply this filter to files.
◆ Folders to apply this filter to folders.
◆ Files and Folders to apply this filter to both files and folders.
Revisions are versions of a file at a specific point in time. You configure revision settings
when you create a backup selection. When a file is changed and backed up, DLO stores a
new revision. DLO will store and maintain a specific number of revisions for all files in a
backup selection. Because backup selections are configured separately, the number of
revisions retained in each backup selection can vary.
When the number of revisions is exceeded, DLO removes the oldest revision,
maintaining only the specified number of revisions in the Desktop and network user
data folders.
You can limit the number of revisions retained in a given period of time. If you are
working on a document and backing it up frequently, all of your revisions could
potentially be just a few minutes apart. By specifying that you want to retain only two
revisions every 24 hours, at least 120 minutes apart, you can retain older revisions for a
longer period of time. While some intermediate versions will not be retained, it does
support situations in which returning to an older revision is needed.
1039

About Backup Selections
Another consideration in determining the number of revisions to retain is the amount of
storage space required to store the data. The amount of space required for backups can
be estimated by multiplying the number of revisions retained by the amount of data
protected.
Example If you are retaining three revisions of each file and
have 10 MB of data to back up, approximately 30 MB of
disk space are required if file sizes remain
consistent between revisions.
Although compression can improve the space utilization, it varies significantly with file
type and other factors. Typical compression ratios are approximately 2:1, so in the
previous example, the maximum disk space usage might be reduced to approximately 15
MB.
File Grooming
The Desktop Agent grooms revisions based on backup selection settings and does this as
new revisions are created. The oldest revision is deleted when a new revision is created
that exceeds the limit. See step 2 on page 1041 for revision control settings.
Maintenance grooming is the process of removing backups of deleted files. It occurs at
most once every 24 hours. Maintenance grooming occurs during the first backup that
runs after 24 hours have passed since the last maintenance grooming.
Setting Revision Control for a Backup Selection
The number of revisions retained in the desktop user data folder and network user data
folder are specified for each backup selection and can be customized to meet specific
user requirements. In addition, the time between revisions can be specified.
▼ To set revision control for a backup selection:
1. Open the Backup Selection dialog box as described in one of the following
procedures:
■ “Adding a Backup Selection” on page 1035
■ “Modifying a Backup Selection” on page 1046
1040 Administrator’s Guide

About Backup Selections
2. From the Revision Control tab in the Backup Selection dialog box, select the
appropriate options for both the Desktop and network user data folders:
Backup Selection Revision Control
Item Description
Number of revisions
desktop user data folder Type the number of revisions to keep in the desktop user data
folder for each file in the backup selection.
Note When Outlook PST files or Lotus Notes NSF files are backed
up incrementally, only one revision is maintained
regardless of the number of revisions set in the backup
selection.
Limit to Check this option to limit the number of revisions retained in a
given amount of time, and specify the following:
◆ Revisions. Select the number of versions to retain.
◆ Within the last x hours. Select the time period during which
you want to retain the versions.
◆ At least x minutes apart. Select the minimum amount of time
that must elapse between backups in this backup selection.
Note The oldest revision is deleted when a new revision is created
that exceeds one of these limits.
network user data folder Select the number of revisions to keep in the network user data
folder for each file in the backup selection.
Limit to Check this option to limit the number of revisions retained in a
given amount of time, and specify the following:
◆ Revisions. Select the number of versions to retain.
Revision Age
◆ Within the last x hours. Select the time period during which
you want to retain the versions.
◆ At least x minutes apart. Select the minimum amount of time
that must elapse between backups in this backup selection.
Note The oldest revision is deleted when a new revision is created
that exceeds one of these limits.
1041

About Backup Selections
Backup Selection Revision Control (continued)
Item Description
Discard all revisions in
the desktop user data
folder older than
Discard all revisions in
the network user data
folder older than
Setting Options for a Backup Selection
DLO backup selections can be further customized by settings options for Delta File
Transfer, compression and encryption. In addition, you can specify how long to keep
backup files after the original source files are deleted.
1. Open the Backup Selection dialog box as described in one of the following
procedures:
■ “Adding a Backup Selection” on page 1035
Enter the number of days after which all revisions in the desktop
user data folder will be deleted.
Note The most recent revision will not be discarded.
Enter the number of days after which all revisions in the network
user data folder will be deleted.
Note The most recent revision will not be discarded.
■ “Modifying a Backup Selection” on page 1046
2. From the Options tab in the Backup Selection dialog box, select the appropriate
options as follows:
Backup Selection Options
Item Description
Delta File Transfer Each time a file is backed up, only the part of the file that has
changed is transferred and stored in the network user data folder.
In addition, Delta file transfer uses compression. Enabling this
option requires that you have installed and configured a
maintenance server. See“Adding a new Maintenance Server” on
page 1049 for additional information.
Compression Each time a file is backed up, files in this backup selection will be
compressed for data transfer over the network and for storage in
the Desktop and network user data folders.
This affects files created after this feature is activated. Previously
stored files will not be compressed.
Delta File Transfer also uses compression.
1042 Administrator’s Guide

Backup Selection Options (continued)
Item Description
3. Click OK to save the backup selection.
About Backup Selections
Encryption Select this option to encrypt files for transfer and to store files
from this backup selection in an encrypted format in the network
user data folder.
This affects files transmitted and stored after this feature is
activated. Previously stored files will not be encrypted.
The AES (Advanced Encryption Standard) and a 128 bit key length
are used. If enabled, versions are stored unencrypted in the
desktop user data folder, and encrypted in the network user data
folder. Transfer over the network is encrypted.
When source files are deleted, delete the backed up files from the:
desktop user data folder
after
network user data folder
after
Indicate the number of days after which DLO will delete all file
versions from the desktop user data folder after the source file has
been deleted from the desktop.
Indicate the number of days after which DLO will delete all file
versions from the network user data folder after the source file
has been deleted from the desktop.
1043

About Backup Selections
Using DLO Macros in Backup Selections
You can type macros into the Type a folder name field of the backup selection dialog box
to automatically back up specific folders. For more information on configuring the Type
a folder name field, see “Backup Selection General Dialog Box” on page 1037. The
following macros are supported:
Folder Macros for use with Backup Selections
Backup Selection Macro Folders backed up
%LOCALFIXEDDRIVES% All local fixed drives.
Note DLO is not designed to back up removable media.
Attempting to back up a floppy disk or CDROM may
result in errors.
%MACHINENAME% Represents the desktop user's computer name.
Example: C:\documents\%machinename% represents
C:\documents\UsersMachineName.
%CURRENTUSERNAME% Represents the username of the currently logged-on user.
Example: If the local administrator is logged on to the
computer, C:\documents\%currentusername%
represents 'C:\documents\Administrator'
%CURRENTUSERPROFILE% All files and folders in the C:\Documents and
Settings\current user profile directory.
%CURRENTUSERMYDOCS% The My Documents directory for the user who is logged
on.
%CURRENTUSERFAVORITES% The Favorites directory for the user who is logged on.
%CURRENTUSERPRINTHOOD% The Printers directory for the user who is logged on.
%CURRENTUSERNETHOOD% The Network Locations directory for the user who is
logged on.
%CURRENTUSERDESKTOP% The Desktop directory for the user who is logged on.
%CURRENTUSERRECENT% The Recent Files directory for the user who is logged on.
1044 Administrator’s Guide

Folder Macros for use with Backup Selections (continued)
Backup Selection Macro Folders backed up
About Backup Selections
%PROGRAMFILES% The Windows Program Files directory. Example:
%PROGRAMFILES%\lotus\notes\data\archives
%LOCALAPPDATA% The Windows local application data directory:
Documents and Settings\\Local
Settings\Application Data”
The following additional pre-defined folder macros are available for selection in the
backup selection dialog box:
Macros for Pre-defined Folders in the Backup Selection dialog
Folder Name Pre-Defined Folder Macro Folders Backed Up
My Documents %CURRENTUSERMYDOCS% The My Documents directory for the
user who is logged on.
Desktop %CURRENTUSERDESKTOP% The Desktop directory for the user
who is logged on.
Favorites %CURRENTUSERFAVORITES% The Favorites directory for the user
who is logged on.
PrintHood %CURRENTUSERPRINTHOOD% The Printers directory for the user
who is logged on.
NetHood %CURRENTUSERNETHOOD% The Network Locations directory for
the user who is logged on.
Recent %CURRENTUSERRECENT% The Recent Files directory for the
user who is logged on.
All local fixed drives %LOCALFIXEDDRIVES% All local fixed drives.
Note When you enter a path that uses a macro, a backslash is automatically added
immediately following the macro. For example, if you type
%LOCALFIXEDDRIVES%\Documents, an extra backslash is added and it appears
as “x:\\Documents” in the Desktop Agent backup selection advanced view. It does
not show at all in the Desktop Agent backup selection Standard view. The correct
way to type this macro is %LOCALFIXEDDRIVES%Documents. This properly
resolves to x:\Documents.
1045

About Backup Selections
Modifying a Backup Selection
Profile backup selections can be modified from the DLO Administration Console.
▼ To modify a backup selection:
1. On the DLO navigation bar, click Setup.
2. In the Settings pane, click Profiles.
3. In the results pane, click the profile you want to modify.
4. In the task pane, under General Tasks, click Properties.
5. Click the Backup Selections tab.
6. Select the backup selection you want to modify, and click Modify.
Note The Type a folder name field in the General tab is grayed out in this view. If
the path in this field is longer than the display, hold the curser over the path
for a moment to display the entire path.
7. Click OK to indicate that you read the message stating that modifying this backup
selection will change all profiles that are using this selection.
8. Change the backup selection as described in the following topics:
“Defining General Backup Selection Properties” on page 1037
“Including and Excluding Files or Folders from a Backup Selection” on page 1038
“Setting Revision Control for a Backup Selection” on page 1040
“Setting Options for a Backup Selection” on page 1042
9. Click OK twice.
Deleting Backup Selections
Before you can delete a backup selection, you must be sure that it is not in use by any
profiles. When you delete a backup selection from one profile, DLO deletes it from every
profile.
When you delete a backup selection, the backup versions are deleted in the same manner
as when source files are deleted. They will be groomed after the number of days specified
in the backup selection.
1046 Administrator’s Guide

▼ To delete a backup selection:
1. On the DLO navigation bar, click Setup.
2. In the Settings pane, Click Profiles.
About Backup Selections
3. In the results pane, click the profile that contains the backup selection you want to
delete.
4. In the task pane, under General Tasks, click Properties.
5. From the Backup Selections tab, select the backup selection you want to delete.
6. Click Delete.
7. Click Yes.
Related Topics:
“Backup Selection Options” on page 1042
1047

Using Delta File Transfer
Using Delta File Transfer
The Delta File Transfer feature enables incremental transfer and storage of backup data.
When this option is enabled, the initial backup requires transfer of the entire file.
Subsequent backups require only the transfer of the parts of the file that have changed,
reducing the bandwidth required and improving backup speed.
Excluding files from Delta File Transfer
Delta File Transfer is not limited to certain programs or file types, but does offer the
ability to exclude certain file types. Default excludes are configured for Delta File
Transfer because these file types do not benefit from this technology. This is usually
because the file types are already highly compressed. For more information on excluding
files from Delta File Transfer, see “Configuring Global Exclude Filters” on page 1065.
Working Offline
Delta File Transfer is only used to transfer and store backup files on in the network user
data folder. Backup files stored in the Desktop User Data Folder are not stored using
deltas. If a Desktop Agent user is working offline, the local revisions are stored in their
entirety in the desktop user data folder. When the user is once again working online,
Delta File Transfer is used to transfer data to the network user data folder.
Requirements for Delta File Transfer
Delta File Transfer requires the use of the DLO maintenance server. The maintenance
server manages the deletion of previous delta revisions from storage locations. The
maintenance server is only required when the Delta File Transfer option is enabled, but it
is installed by default when DLO is installed. Only one maintenance server is required,
but in large installations it may be more efficient to have one maintenance server for
each Storage Location host (i.e. File Server).
The maintenance server is installed on the media server by default when DLO is
installed. If the media server is also the Storage Location host, then no additional steps
are required to configure the maintenance server.
Maintenance Server Technical Information and Tips
The Desktop Agent uses Windows RPC over named pipes to communicate with the
maintenance server. For the maintenance server to function, named pipe traffic must not
be blocked at any point between the DLO Client and the maintenance server.
The rolloff operation for delta revisions can require significant bandwidth. For this
reason, the maintenance server should be installed on the computer that is hosting the
Storage Location.
1048 Administrator’s Guide

Using Delta File Transfer
However, there are situations where the maintenance server cannot be installed on the
same computer as the Storage Location server. For example, the maintenance server
cannot be installed on a NAS device. In this case, the maintenance server should be
installed on a computer with a high bandwidth connection to the Storage Location.
A maintenance server can manage one or more Storage Locations. A maintenance server
will always manage the Storage Locations located on same computer as the maintenance
server. The maintenance server can be configured to manage additional Storage
Locations hosts, ie. File Servers, from the DLO Console. The maintenance server uses
delegation to access remote Storage Locations. See “Configuring a Maintenance Server
for Delegation” on page 1050 for additional information.
Enabling Delta File Transfer for a Backup Selection
Delta File Transfer is off by default. It can be enabled for a given backup selection by
selecting Delta in the Backup Selection Options tab as explained in “Delta File Transfer”
on page 1042.
In addition, if a maintenance server manages file servers that are on a target other than
itself, the maintenance server must be configured for delegation as explained in
“Configuring a Maintenance Server for Delegation” on page 1050.
Delta File Transfer can also be selected as the default compression type by changing the
application default settings for compression. If the default compression setting is
changed to Delta, all new backup selections will use Delta compression by default. See
“DLO Default Settings” on page 1000 for additional information.
Adding a new Maintenance Server
After you install a new maintenance server, you must add the maintenance server to
DLO. After adding the maintenance server to DLO, you can then specify which file
servers it is to manage as explained in “Reassigning a File Server” on page 1052.
▼ To add a new Maintenance Server:
1. Verify that the new maintenance server has been installed.
Note A default maintenance server is installed with DLO. A stand-alone
maintenance server can also be installed by running the installer and selecting
Maintenance Server as the installation type. See “Installing Backup Exec
options to the local computer” on page 85 for additional information.
2. From the DLO Console, on the DLO navigation bar, click Setup.
1049

Using Delta File Transfer
3. In the task pane, under Manage Tasks, click Maintenance servers.
4. Click Add.
5. Navigate to the computer where the maintenance server is installed.
6. Select this computer.
7. Click OK.
Configuring a Maintenance Server for Delegation
When a maintenance server is configured to manage Storage Locations hosted by a
different computer, they must be configured to access these locations on behalf of
desktop users running the Desktop Agent. This configuration is managed using Active
Directory.
Note For detailed information on delegating Active Directory administration, see the
Microsoft website:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologie
s/directory/activedirectory/actdid1.mspx
▼ To configure a maintenance server for delegation:
1. Verify that the following conditions are met:
■ Domains are Windows 2000 or later. NT 4 domains are not supported.
■ Both the Desktop Agent user’s account and the maintenance service's account
must be in the same forest.
■ Desktop Agent user and computer accounts must be in mutually trusted
domains.
■ Desktop and server operating systems must be Windows 2000 or later
2. Confirm that the desktop user account is configured for delegation. See “Confirm
that the Desktop User’s Account is Configured for Delegation” on page 1050.
3. Confirm that the server process account is trusted for delegation.“Confirm that the
Server Process Account is Trusted for Delegation” on page 1051.
Confirm that the Desktop User’s Account is Configured for Delegation
This process verifies that the desktop agent user’s account can be delegated.
1050 Administrator’s Guide

▼ To confirm that the desktop user’s account is configured for delegation
1. Log on to the domain controller using a domain administrator account.
Using Delta File Transfer
2. On the taskbar, click the Start button, point to Programs and then Administrative
Tools and click Active Directory Users and Computers.
3. Under the domain, click the Users folder.
4. Right-click the user account to be delegated and click Properties.
5. Click the Account tab.
6. In the Account options list, verify that the Account is sensitive and cannot be
delegated is not selected.
7. Click OK.
Confirm that the Server Process Account is Trusted for Delegation
This process verifies that the account used to run the maintenance server process is
allowed to delegate client accounts.
▼ To confirm that the server process account is trusted for delegation
1. Log on to the domain controller using a domain administrator account.
2. On the taskbar, click the Start button, point to Programs and then Administrative
Tools and click Active Directory Users and Computers.
3. Right-click the Computers folder and click Properties.
4. Right-click the computer on which the maintenance server runs and then click
Properties.
5. On the General page, click Trust computer for delegation.
6. Click OK.
1051

Using Delta File Transfer
Changing the Default Maintenance Server
When DLO is installed, a maintenance server is installed and set as the default
maintenance server. New storage locations are automatically assigned to the default
maintenance server when they are created. If you want new storage locations to be
assigned to a different maintenance server by default, you must change this setting.
▼ To change the default maintenance server:
1. From the DLO Console, on the DLO navigation bar, click Setup.
2. In the task pane, under Manage Tasks, click Maintenance servers.
3. In the Maintenance Servers list, check the box for the maintenance server you want
to set as the default.
4. Click OK.
Reassigning a File Server
You can reassign a file server to another maintenance server that is recognized by DLO.
For example, when you create a new storage location, it is automatically assigned to the
default maintenance server. You may want to reassign it to a different maintenance
server.
▼ To Reassign a File Server
1. Verify that the new maintenance server has been installed and configured.
2. On the DLO navigation bar, click Setup.
3. In the task pane under Manage Tasks, click Maintenance servers.
4. Select the maintenance server currently manages the file server.
5. Click Edit.
6. Select the file server you want to reassign.
7. Click Reassign.
8. Select the new maintenance server from the drop-down menu.
9. Click OK three times.
1052 Administrator’s Guide

About DLO Storage Locations
About DLO Storage Locations
Storage Locations are locations on network computers where network user data folders
are automatically created. The Desktop and Laptop Option stores each user’s data in two
places. First, it is stored in the desktop user data folder on the user's computer to provide
protection and restore capabilities even when the computer is disconnected from the
network. The data is then additionally stored in a network user data folder, which is
located on the network. This provides an additional level of protection, and enables the
files to be backed up to secondary media when the server is backed up.
When a user is automatically added to DLO using an Automated User Assignment, a
network user data folder is created in a Storage Location as specified in the Automated
User Assignment. If network shares already exist for desktop users, they can be specified
as network user data folders when users are manually added to DLO. If existing network
shares are used as network user data folders, Storage Locations are not used.
DLO supports the use of hidden shares (for example; “Share$”) as Storage Locations on
NTFS volumes or as network user data folders for FAT32 volumes, but they cannot be
created with the DLO Administration Console. They must be created and configured
manually. See “Using Hidden Shares as Storage Locations” on page 1054 for additional
information.
Supported Storage Location Configurations
The following table summarizes supported configurations for DLO Storage Locations:
Storage Location Configuration Support
Description Supported Not Supported
All media server platforms X
Windows 2000 NAS/SAK NAS devices X
Local media server direct-attached storage X
SAN X
Windows-networking accessible NAS Devices (Quantum,
Network Appliance, etc.)
FAT, FAT32 and NTFS partitions are supported as Storage
locations, although FAT and FAT32 are not recommended.
NTFS is the preferred file system for Storage Locations
X
X
1053

About DLO Storage Locations
Storage Location Configuration Support (continued)
Description Supported Not Supported
NetWare 3.1x, 4.x, or E-Directory Storage Locations X
UNIX file systems or SAMBA shares on UNIX systems X
Using Hidden Shares as Storage Locations
DLO supports the use of hidden shares (for example; “Share$”) as Storage Locations on
NTFS volumes or as network user data folders for FAT32 volumes, but these shares must
be manually created and configured. They cannot be created with the DLO
Administration Console. Hidden shares cannot be used for FAT based Storage Locations.
The following permissions should be used:
Permission Settings for Hidden Shares
Drive Type User or Group Permissions
Share Permissions on NTFS Volumes
Administrator Allow Full Control, Change, Read
Everyone Allow Full Control, Change, Read
Security Permissions on NTFS Volumes
Administrator Full control
Everyone Allow Read & Execute
Allow List Folder Contents
Allow Read
Special security
permissions or
advanced settings
Advanced Security Permissions on NTFS Volumes
Allow Traverse Folder/Execute File
Allow List Folder/Read Data
Allow Read Attributes
Allow Read Extended Attributes
Allow Read Permissions
Administrator Allow Full Control
1054 Administrator’s Guide

Permission Settings for Hidden Shares (continued)
Drive Type User or Group Permissions
Everyone Allow Traverse Folder / Execute File
Allow List Folder / Read Data
Allow Read Attributes
Allow Read Extended Attributes
Allow Read Permissions
Share Permissions on FAT Volumes
Administrator Allow Full Control, Change, Read
Owner Allow Full Control, Change, Read
Full Admin Group Allow Full Control, Change, Read
Limited Admin Group Allow Read
Creating DLO Storage Locations
About DLO Storage Locations
A Storage Location should be used by only one media server. If you set up multiple media
servers to use the same Storage Location and the Storage Location is deleted from one
media server, the other media server no longer be able to access it.
Storage Locations must be in a Windows Domain or Active Directory. Computers running
the Desktop Agent can be outside of a Windows Domain or Active Directory, but they
must authenticate with the domain or directory to access the media server or Storage
Locations. User’s are be prompted to provide domain credentials when the Desktop
Agent is launched.
If your original files reside on an NTFS volume, then the desktop user data folder and the
network user data folder should also be NTFS. If your original files are on NTFS and
either the desktop user data folder or network user data folder are on a FAT or FAT32
volume, you may see duplicate entries in the Restore and Restore Search screens. If
duplicates do appear, you can select either file to restore.
Once created, Storage Locations cannot be modified, but they can be deleted if there are
no users or Automated User Assignments assigned to them. You can move users to new
Storage Locations. For more information, see “Moving Desktop Agent Users to a new
Network User Data Folder” on page 1079.
1055

About DLO Storage Locations
Note If you receive errors when creating Storage Locations, verify that the login account
for the service named MSSQL$BKUPEXECDLO has sufficient rights to create
directories and change permissions for the Storage Locations. Use the Windows
Service Control Panel to change the login account for the MSSQL$BKUPEXECDLO
instance. You can avoid these problems if you specify a domain account when you
install Backup Exec.
▼ To create DLO Storage Locations:
Note After you create Storage Locations, you cannot modify them.
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click File Servers.
3. In the task pane, under Settings Tasks, click New Storage Location.
4. Select the appropriate options as follows.
New Storage Location Dialog Box
Item Description
Computer name Type a computer name or browse to a computer on which to create
the Storage Location.
Path Type or browse to a location on the computer where the Storage
Location will be created.
Note Storage Locations should be in the same domain as the
media server or in a domain that trusts the media server’s
domain.
1056 Administrator’s Guide

5. Click OK.
About DLO Storage Locations
Configuring a Remote Windows Share or NAS Device for DLO
Storage Locations
DLO Storage Locations can be created on remote Windows shares or network attached
storage devices.
Case 1
New Storage Location Dialog Box (continued)
Item Description
Storage Location name Type a name for the new Storage Location. The name cannot
contain any of the following characters: \”@#$%^&*()=+|/{}[]’
Summary The Summary field automatically displays the location and
format of network user data folders that will be created for new
users assigned to this Storage Location. Network user data folders
are automatically created in the Storage Location.
DLO uses the %USERDOMAIN% and %USERNAME% variables to
determine the actual folder path for each user who is assigned to a
Storage Location. DLO uses the user’s domain and user name to
create a unique network user data folder name for that user. If the
user is logged on with credentials that do not allow access to the
Storage Location, the user will be prompted to enter alternate
domain credentials.
The network administrator can access this folder, but cannot
configure the variables.
▼ To create Storage Locations when the DLO administration service is a full administrator
on the remote system
1. Validate that DLO 5.1 MP1 or later is installed.
2. Ensure that the account credentials used for DLO services have full administrator
rights to the remote storage location or NAS device.
3. Make sure that the volume desired to be used for DLO has been assigned a drive
letter on the remote storage location or NAS device.
Note See hardware vendor documentation on share creation and naming.
1057

About DLO Storage Locations
4. Create a new Storage Location as directed in the DLO Administrator's Guide. Use the
browse feature to indicate the location on the computer where the Storage Location
will be created. This will insure that the path and the DLO service account are valid.
Case 2
The DLO administration service does not run as an administrator level user, but the DLO
administration groups have been assigned the appropriate permission levels on a
pre-existing share.
▼ How to configure Storage Locations using non-administrator case:
1. Configure DLO to use existing domain groups to automatically manage access to
network user data folders as explained in “About Administrator Accounts” on
page 996. Check the Automatically grant DLO Administrators access to network user
data folders checkbox and provide the required domain groups. Provide two groups: a
group for full-DLO administrators and a group for limited-DLO administrators.
2. From the Administrator Account Management dialog, add the appropriate domain
user accounts to the account manager. If the user will have full administrator rights,
check the "Grant administrator full restore privileges" checkbox in the Add
Administrator Account dialog. In addition to other users, be sure to grant the DLO
Administration Service full restore privileges.
3. Create a folder on the remote storage location using an administrator, or
administrator equivalent user.
4. Share the new folder. Ensure that 'Everyone' has full-access to the share.
5. Modify the folder's security permissions such that the full-DLO administrator group
has full-control of the folder and that the limited-DLO administrator group has
modify-control of the folder.
6. Using the DLO console, create a new Storage Location. Specify the machine name,
drive and path, and share name for the folder just created.
Note Do not use the browse buttons at any point during the storage location
creation as they will cause the process to fail.
7. Once the required fields are completed, click OK
1058 Administrator’s Guide

About DLO Storage Locations
8. Storage Locations manually created when the DLO Admin Service does not have full
administrator rights to the server hosting the DLO Storage Location cannot be
deleted from the DLO Admin Console. Attempting to do so will result in an error. To
manually remove the Storage Location:
a. Move or delete all users in the Storage Location.
b. Manually remove the Storage Location share and folder from the server.
c. Delete the Storage Location from the DLO Admin Console.
Deleting DLO Storage Locations
Before you can delete DLO Storage Locations, you must delete or reassign users and
Automated User Assignments that use the Storage Location. The Storage Location
associated with a user or Automated User Assignment is listed when you select Users or
Automated User Assignments from the Setup view.
Note When a Storage Location is created using an existing share on a remote computer
and DLO does not have full computer rights, the Storage Location cannot be
deleted from the Administration Console. To remove the Storage Location, first
delete the Storage Location share and then delete the Storage Location from the
Administration Console.
▼ To delete Storage Locations:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, expand the file servers list by clicking the ‘+’ next to File
Servers.
3. In the selection pane, Click the File Server on which the Storage Location resides.
4. In the results pane, click the storage location you want to delete.
5. In the task pane, under General Tasks, click Delete.
6. Click Yes.
Related Topics:
“Managing Desktop Agent Users” on page 1074
“Modifying Automated User Assignments” on page 1063
1059

About Automated User Assignments
“Deleting Automated User Assignments” on page 1065
About Automated User Assignments
Automated User Assignments are instructions that are applied when the Desktop Agent
is first run on a desktop. The Automated User Assignment assigns a profile and network
user data folder to each user who is automatically configured by DLO. These settings can
be changed from the DLO Administration Console at a later time if necessary.
Note If a user is added manually to DLO, a Storage Location and profile are selected by
the DLO administrator. The Automated User Assignment will not be used. For
more information, see “Managing Desktop Agent Users” on page 1074.
Automated User Assignments are assigned to desktop users based either on their
domain and group, or using Active Directory settings. Because users may match the
criteria for more than one Automated User Assignment, the Automated User
Assignments are prioritized. When the Desktop Agent is run for the first time, the
Desktop Agent user’s domain and group credentials are checked against those of the
Automated User Assignment starting with the highest priority assignment. When a
match is made, the share and profile specified in that Automated User Assignment are
assigned to the new user.
Modifying Automated User Assignments does not affect users who have already been
configured. Only new users configured with the Automated User Assignment will use the
new settings.
1060 Administrator’s Guide

Viewing Automated User Assignments
About Automated User Assignments
For information on modifying Automated User Assignment priorities, see “Changing the
Priority of Automated User Assignments” on page 1064.
Creating Automated User Assignments
Automated User Assignments are assigned to Desktop Agent users based either on
domain and group settings or Active Directory settings. The Automated User
Assignment determines which Storage Location and Profile are assigned to the user.
▼ To create a new Automated User Assignment:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Automated User Assignments.
Automated User Assignments
listed in order of priority
3. In the task pane under Settings Tasks, click New user assignment.
1061

About Automated User Assignments
4. Select the appropriate options as follows:
New Automated User Assignment Dialog Box Options
Item Description
User Assignment
User assignment
name
Assign using Domain
and Group
Type a name for the Automated User Assignment. The Automated
User Assignment name cannot contain the following characters:
\”@#$%^&*()=+|/{}[]’
Select this option to match Desktop Agent users to Automated User
Assignments based on their domain and group.
Domain Select the domain to which this Automated User Assignment will
apply.
Group Select the group to which this Automated User Assignment will apply.
Assign Using Active
Directory
Select this option to match Desktop Agent users to Automated User
Assignments based on Active Directory settings.
Configure Click the Configure button to configure the User Assignment using
Active Directory. See step 5 below for information on configuring the
Active Directory settings.
Storage Location/Profile
Storage Location Select a Storage Location to be assigned to the users in the selected
domain and group.
Profile Select a profile to be assigned to the users in the selected domain and
group.
1062 Administrator’s Guide

About Automated User Assignments
5. If you chose to use Active Directory to configure the User Assignment in step 4,
configure the Active Directory settings as follows and click OK:
Active Directory Object Dialog
Item Description
Object For Automated User Assignments, the only option is
User.
In LDAP Directory Type or browse to the LDAP directory.
Note When selecting Active Directory user accounts, you
must select the specific directory that holds the
user accounts. Be sure not to select the user groups
directory. Browse to or type the exact path of the
specific user accounts directory for which you are
creating this rule.
All objects in this directory Select this option to apply the connection policy to all
objects in the specified directory.
Only the objects in this directory
that match the criteria below
6. Click OK.
Modifying Automated User Assignments
Select this option to apply the connection policy only to
those objects in the specified directory that match the
criteria entered.
Attributes Select an attribute from the drop-down menu or type a
custom attribute.
Condition Select the appropriate condition. Available options
include =, .
Value Type a value to complete the criteria that will be used to
determine matches. Wildcards can be used to specify the
value.
Modifying an Automated User Assignment affects only users added to the assignment
after it has been modified. Existing Desktop Agent users are unaffected.
Settings for existing Desktop Agent users can be modified from the Setup view of the
DLO Administration Console. For more information see “Modifying Desktop Agent User
Properties” on page 1077.
1063

About Automated User Assignments
▼ To modify an Automated User Assignment:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Automated User Assignments.
3. In the results pane, select the Automated User Assignment you want to modify.
4. In the task pane, under General Tasks, select Properties.
5. Modify the Automated User Assignment properties.
Changing the Priority of Automated User Assignments
When you create an Automated User Assignment, DLO assigns a priority to it so that
when a user is a member of more than one domain and group, it is clear which
Automated User Assignment will be used. The most recently created Automated User
Assignments have the lowest priority. You can change the priority of Automated User
Assignments.
▼ To change the priority of Automated User Assignments:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Automated User Assignments.
3. In the results pane, select the Automated User Assignment for which you want to
change the priority.
4. In the task pane, under Settings Tasks, select Move priority up or Move priority
down.
Viewing Automated User Assignment Properties
▼ To view Automated User Assignments:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Automated User Assignments.
3. In the results pane, select an Automated User Assignment.
1064 Administrator’s Guide

4. In the task pane, under General Tasks, select Properties.
Deleting Automated User Assignments
Configuring Global Exclude Filters
You can delete Automated User Assignments when you no longer need them.
▼ To delete an Automated User Assignment:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Automated User Assignments.
3. Click the Automated User Assignment to be deleted.
4. In the task pane, under General Tasks, click Delete.
5. Click Yes.
Related Topics:
“About Automated User Assignments” on page 1060
“New Automated User Assignment Dialog Box Options” on page 1062
“Modifying Automated User Assignments” on page 1063
“Changing the Priority of Automated User Assignments” on page 1064
“Moving Desktop Agent Users to a new Network User Data Folder” on page 1079
“Modifying Desktop Agent User Properties” on page 1077
Configuring Global Exclude Filters
DLO global exclude options enable you to specify the attributes of files that you want to
exclude from all backups, or that you do not want to compress, encrypt, or back up with
Delta File Transfer. You can also exclude attachments to emails or specific email folders
from backup. Global excludes apply to both Profile backup selections and user created
backup selections for all Desktop Agent users who back up to the media server on which
the excludes are configured.
The files you exclude are listed on the Include/Exclude tab in the advanced view on the
Desktop Agent and on the Include/Exclude tab for a profile's backup selection on the
DLO Administration Console. Items configured for the global exclude list are not
available for selection on the selection list.
1065

Configuring Global Exclude Filters
Caution Adding a global exclude will cause all previous backups matching the global
exclude to be deleted.
To configure global excludes, see the following procedures:
“Specifying Files and Folders to Exclude from all Backups” on page 1066
“Specifying Email to Exclude from All Backups” on page 1067
“Specifying Files and Folders to Exclude from Compression” on page 1069
“Specifying Files and Folders to Exclude from Encryption:” on page 1070
“Specifying Files and Folders to Exclude from Delta File Transfer” on page 1071
“Using DLO Macros to Define Global Excludes” on page 1073
Specifying Files and Folders to Exclude from all Backups
File and Folder global excludes are used to specify which files and folders, or file and
folder types, are to be excluded from all backups for all users.
▼ To specify files and folders to exclude from all backups:
1. From the Tools menu in the DLO Administration Console, select Global Excludes.
2. Select the Files/Folders tab. Default Files/Folders global excludes are listed.
3. To exclude all files greater than a specific size, check the Exlude all files greater
than check box and enter a size in KB.
4. To Exclude all files modified before a specified date, check the Exclude all files
modified before check box and enter a date.
1066 Administrator’s Guide

Configuring Global Exclude Filters
5. To add a new Files/Folders global exclude, click Add and configure as follows:
Add Global Exclude Filter Dialog
Item Description
Filter The filter determines which files or folders will be excluded
from backup by the global exclude. Type a file name, wildcard,
or macro for the files you want to exclude.
Examples:
Wildcard: *.tmp
File name: pagefile.sys
Macro: %WINDIR%
Note When using wildcards, you must use the asterisk (*)
wildcard. For example, *.tmp will return all results with
the .tmp extension while .tmp will return only files
explicitly named .tmp.
Description Type a description of the global exclude.
Apply to Indicate whether this global exclude should apply to files,
folders, or both files and folders.
6. Click OK.
7. To edit a global exclude filter, click Edit and configure as described in the step 5
above.
8. To delete a global exclude filter, click the filter to be deleted and click Delete. Click
Yes to delete the filter or No to cancel.
9. Click OK.
Specifying Email to Exclude from All Backups
Email global excludes are used to specify the type of emails to be excluded from all
backups for all users.
Note Lotus Notes emails cannot be filtered by attachment size or type.
1067

Configuring Global Exclude Filters
▼ To specify email attachments to exclude from all backups:
1. From the Tools menu in the DLO Administration Console, select Global Excludes.
2. Select the Email tab.
3. To exclude from all backup attachments greater than a specific size, check the
Exlude all attachments greater than check box and enter a size in KB. This feature
does not apply to Lotus Notes emails.
4. To Exclude from all backup messages received before a specified date, check the
Exclude all messages received before check box and enter a date.
5. To Add a new email global exclude, click Add and configure as follows:
Add Global Email Exclude Filter Dialog
Item Description
Attachment file type The filter determines which attachment file types will be
excluded from backup by the global exclude.
Note Lotus Notes emails cannot be filtered by attachment
type.
Filters can be file names or wildcards.
Examples:
Wildcard: *.tmp
File name: pagefile.sys
Note When using wildcards, you must use the asterisk (*)
wildcard. For example, *.tmp will return all results with
the .tmp extension while .tmp will return only files
explicitly named .tmp.
Mail folder name Type the name of the mail folder you would like to exclude
from backup.
Description Type a description of the global exclude.
6. Click OK.
7. To edit a global email filter, click the filter you want to change. Click Edit and
configure as described in the “Add Global Email Exclude Filter Dialog” table above.
8. To delete a global email filter, click the filter to be deleted and click Delete. Click Yes
to delete the filter or No to cancel.
1068 Administrator’s Guide

9. Click OK.
Configuring Global Exclude Filters
Specifying Files and Folders to Exclude from Compression
Compressed file global excludes are used to specify the type of files or folders to be
excluded from compression for all users.
▼ To specify files and folders to exclude from compression:
1. From the Tools menu in the DLO Administration Console, select Global Excludes.
2. To exclude files or folders from compression, select the Compressed Files tab.
Default compressed files global excludes are listed.
3. To exclude all files greater than a specific size from compression, check the Exlude
all files greater than check box and enter a size in KB.
4. To Add a new compressed file global exclude, click Add and configure as follows:
Add Global Compression Exclude Filter Dialog
Item Description
Filter The filter determines which files or folders will be excluded
from compression by the global exclude. Filters can be file
names, wildcards or macros.
Examples:
Wildcard: *.tmp
File name: pagefile.sys
Macro: %WINDIR%
Note When using wildcards, you must use the asterisk (*)
wildcard. For example, *.tmp will return all results with
the .tmp extension while .tmp will return only files
explicitly named .tmp.
Description Type a description of the global exclude.
Apply to Indicate whether this global exclude should apply to files,
folders, or both files and folders.
5. Click OK.
1069

Configuring Global Exclude Filters
6. To edit a global exclude filter, click the filter you want to change. Click Edit and
configure as described in the “Add Global Compression Exclude Filter Dialog” table
above.
7. To delete a global exclude filter, click the filter to be deleted and click Delete. Click
Yes to delete the filter or No to cancel.
8. Click OK.
Specifying Files and Folders to Exclude from Encryption:
Encrypted file global excludes are used to specify which files or folders, or file and folder
types, are to be excluded from encryption for all users.
▼ To configure encrypted file global excludes
1. From the Tools menu in the DLO Administration Console, select Global Excludes.
2. To exclude files or folders from encryption, select the Encrypted Files tab. Default
encrypted files global excludes are listed.
3. To exclude files greater than a specific size from encryption, check the Exlude all
files greater than check box and enter a size in KB.
4. To Add a new encrypted file global exclude, click Add and configure as follows:
Add Global Encryption Exclude Filter Dialog
Item Description
Filter The filter determines which files or folders will be excluded
from encryption by the global exclude. Filters can be file
names, wildcards or macros.
Examples:
Wildcard: *.tmp
File name: pagefile.sys
Macro: %WINDIR%
Note When using wildcards, you must use the asterisk (*)
wildcard. For example, *.tmp will return all results with
the .tmp extension while .tmp will return only files
explicitly named .tmp.
Description Type a description of the global exclude.
1070 Administrator’s Guide

Add Global Encryption Exclude Filter Dialog (continued)
Item Description
5. Click OK.
Configuring Global Exclude Filters
Apply to Indicate whether this global exclude should apply to files,
folders, or both files and folders.
6. To edit a global encryption exclude filter, click the filter you want to change. Click
Edit and configure as described in the “Add Global Encryption Exclude Filter Dialog”
table above.
7. To delete a global encryption exclude filter, click the filter to be deleted and click
Delete. Click Yes to delete the filter or No to cancel.
8. Click OK.
Specifying Files and Folders to Exclude from Delta File Transfer
Delta File Transfer global excludes are used to specify which files or folders, or file and
folder types, are to be excluded from Delta File Transfer for all users.
▼ To specify files and folders to exclude from Delta File Transfer:
1. From the Tools menu in the DLO Administration Console, select Global Excludes.
2. To exclude files or folders from Delta File Transfer, select the Delta File Transfer tab.
Default Delta File Transfer global excludes are listed. File types excluded by default
from Delta File Transfer are generally file types that do not benefit from this
technology.
Note Files and Folders backed up using Delta File Transfer are also compressed with
standard compression. If a file is in a backup selection that uses Delta File
Transfer, but is excluded from Delta File Transfer via a global excludes filter, it
is still compressed with standard compression unless it is also excluded from
standard compression via another global excludes filter.
3. To exclude files greater than a specific size from Delta File Transfer, check the
Exlude all files greater than check box and enter a size in KB.
4. To exclude files smaller than a specific size from Delta File Transfer, check the
Exlude all files less than check box and enter a size in KB.
1071

Configuring Global Exclude Filters
5. To Add a new Delta File Transfer global exclude, click Add and configure as follows:
Add Global Delta File Transfer Exclude Filter Dialog
Item Description
Filter The filter determines which files or folders will be excluded
from Delta File Transfer by the global exclude. Filters can be
file names, wildcards or macros.
Examples:
Wildcard: *.tmp
File name: pagefile.sys
Macro: %WINDIR%
Note When using wildcards, you must use the asterisk (*)
wildcard. For example, *.tmp will return all results with
the .tmp extension while .tmp will return only files
explicitly named .tmp.
Description Type a description of the global exclude.
Apply to Indicate whether this global exclude should apply to files,
folders, or both files and folders.
6. Click OK.
7. To edit a global Delta File Transfer exclude filter, click the filter you want to change.
Click Edit and configure as described in the “Add Global Delta File Transfer Exclude
Filter Dialog” table above.
8. To delete a global Delta File Transfer exclude filter, click the filter to be deleted and
click Delete. Click Yes to delete the filter or No to cancel.
9. Click OK.
Related Topics:
“Using Delta File Transfer” on page 1048
Excluding Files that are Always Open
On desktop computers running Windows XP and Windows 2000, the following folders
and file types are generally always open and DLO is unable to back them up. Adding
these files to the Global Excludes list, or backup selection exclude list will prevent them
from always being listed in the pending files list on the Desktop Agent.
1072 Administrator’s Guide

■ C:\Windows\System32\Config
Configuring Global Exclude Filters
■ registry hives and logs, including *.DAT.LOG, *.LOG and the files system, SECURITY,
default, SAM, and software
■ C:\Windows\System32\wbem
■ *.EVT
■ *.LOG (in particular, STI_Trace.log, WIADEBUG.LOG, WIASERVC.LOG)
■ *.DAT (in particular, NTUSER.DAT, USRCLASS.DAT)
Related Topics:
“About Backup Selections” on page 1033
“Configuring Global Exclude Filters” on page 1065
Using DLO Macros to Define Global Excludes
The following macros are typically used for excluding files using the global exclude
option, but can also be used in backup selections.
Global Exclude Macros
Macro Folder
%TEMP% The temp directory for the user who is logged on.
%WINDIR% The Windows directory.
Example: C:\Windows or C:\Winnt
%WEBTEMP% The web cache for the user who is logged on.
%RECYCLED% Recycle bins
%SYSTEM% The Windows system directory.
Example: C:\Windows\system or C:\Winnt\system
1073

Managing Desktop Agent Users
Managing Desktop Agent Users
The DLO Administrator manages Desktop Agent users from the DLO Administration
Console. From this interface, users or groups of users can be manually added to DLO,
enabled or disabled, moved to a new network share, or assigned a different profile.
Desktop Agent users are added to DLO either automatically using Automated User
Assignments, or manually from the DLO Administration Console.
Related Topics:
“About Automated User Assignments” on page 1060
“Adding a Single Desktop User to DLO” on page 1075
“Importing Multiple Desktop Users Who Have Existing Network Storage” on page 1076
“Viewing a List of Desktop Agent Users” on page 1081
“Modifying Desktop Agent User Properties” on page 1077
“Enabling or Disabling DLO Access For a Desktop User” on page 1077
“Deleting a User from DLO” on page 1078
“Moving Desktop Agent Users to a new Network User Data Folder” on page 1079
Manually Creating New Network User Data Folders
If network shares already exist for desktop user backups, they can be added to DLO as
network user data folders, or new shares can be created and added to DLO for this
purpose. To create or use an existing network share as a network user data folder, the
folder must have the appropriate security attributes.
▼ To manually create network user data folders and set security attributes:
1. Create or locate a network share on the computer where backup files will be stored.
2. Right-click the share you created in step 1, and then select Properties.
3. Click the Sharing tab.
4. Verify that Share this folder is selected.
5. Click Permissions.
6. Select the following permissions for user Everyone: Full Control, Change, Read
7. Click OK.
1074 Administrator’s Guide

8. Click the Security tab.
9. Click Advanced.
Managing Desktop Agent Users
10. Verify that the Inherit from parent the permission entries that apply to child
objects check box is not checked.
11. Add Administrator and Everyone and give them full control permissions.
12. In this share, create a data folder for each user who will use this Storage Location, or
verify that a data folder already exists.
13. Right-click the data folder for a user.
14. Select Properties.
15. Select Security.
16. Verify that the Inherit from parent the permission entries that apply to child
objects check box is not checked.
17. Add Administrator and the user who will be assigned to the user data folder to the
share permission list.
18. Set full permission for Administrator and the user.
Adding a Single Desktop User to DLO
Desktop users can be configured manually rather than with Automated User
Assignments (see “About Automated User Assignments” on page 1060). This allows the
use of existing network folders that are dedicated to storing backup data for specific
users. These network folders become the DLO network user data folders.
When a single desktop user is added to DLO, the user data folders are added manually so
Storage Locations are not required, but they can be used if it is desirable to place the
network user data folder in this location.
After adding a desktop user manually, the settings that you assign (the user data folder
and the profile) are applied the first time the desktop user runs the Desktop Agent.
▼ To add a single desktop user:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, Click Users.
1075

Managing Desktop Agent Users
3. In the task pane, under User Tasks, click New user.
4. Complete the appropriate options as follows:
New User Properties
Item Description
Enable User Select this option to enable this user to use the Desktop Agent, or
clear it to prevent the user from using the Desktop Agent.
User Browse to the username or type it in the form
DomainName\UserName.
Profile Select the profile that you want to assign to this user.
User data folder Do one of the following:
network user data folder Select this option and type the path or browse to an existing
network user data folder where this desktop user’s backup files
will be stored. This must be an existing folder, and the security
attributes must be set for the folder according to your
organization’s needs. For example, determine which users can
access the folder.
Note A Storage Location is not required when an existing
network share is used as the network user data folder.
Storage Location Select this option to choose an existing Storage Location. The
network user data folder for the new user will be placed in this
Storage Location.
Importing Multiple Desktop Users Who Have Existing Network
Storage
If you want to configure multiple new desktop users who already have an existing
location on the network to store data, you can import a list of the users using a comma
separated values (CSV) file. This feature cannot be used to import network user data
folders for existing Desktop Agent users.
The file must be in the following format and have the following information for each
user:
user name, domain, profile, user data folder
Example JSmith,enterprise,Default,\\Server1\Userdata\jsmith
1076 Administrator’s Guide

▼ To import multiple desktop users from a file:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Users.
3. In the task pane, under User Tasks, click Import users using wizard.
4. Follow the wizard prompts.
Modifying Desktop Agent User Properties
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Users.
Users are listed in the results pane.
3. Select the user you want to modify.
4. In the task pane, under General Tasks, select Properties.
5. Select the appropriate options as follows:
User Properties
Item Description
Enabling or Disabling DLO Access For a Desktop User
Managing Desktop Agent Users
Enable User Select this option to enable this user to use the Desktop Agent, or
clear it to prevent the user from using the Desktop Agent.
User The name of the user. This field cannot be edited.
Profile Select a profile to apply to this user.
network user data folder This is the location where the user’s backup files are to be stored.
It cannot be modified. To move a user to a new location, see
“Moving Desktop Agent Users to a new Network User Data Folder”
on page 1079.
This option allows to you either allow or prevent a user from using the Desktop Agent.
1077

Managing Desktop Agent Users
▼ To enable or disable DLO access for a desktop user:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Users. Users are listed in the results pane.
3. Select the user you want to modify.
4. In the task pane, under General Tasks, select Properties.
5. Do one of the following:
■ Clear the Enable user check box to prevent the desktop user from backing up
data with the Desktop Agent.
■ Check the Enable user check box to allow the desktop user to back up data with
the Desktop Agent.
Deleting a User from DLO
If you want to permanently remove a user from the DLO database, you can delete the
user’s entry from DLO. Before deleting the user from the DLO Administration Console
database, you should uninstall the Desktop Agent from the user’s desktop. Otherwise,
the user will automatically be re-added if the Desktop Agent is run by the user and a
matching user assignment exists in DLO. If you cannot uninstall the Desktop Agent from
the user’s computer, disable the user (see “Enabling or Disabling DLO Access For a
Desktop User” on page 1077).
▼ To delete a user from the DLO database:
1. Uninstall the Desktop Agent from the user’s computer.
2. On the DLO navigation bar, click Setup.
3. In the selection pane, click Users.
4. Click the user or users you want to delete.
5. In the task pane, under General Tasks, click Delete.
6. To delete the data stored in the user data folder, check Delete data stored in the user
data folder.
1078 Administrator’s Guide

Managing Desktop Agent Users
When the Delete data stored... option is selected, backup data is deleted from the
network user data folder, but not from the desktop user data folder. When the
Desktop Agent is uninstalled from the desktop computer, an option is provided to
delete the desktop user data folder.
7. Click Yes or Yes to All to delete the user.
Note If you delete a user from the DLO Administration Console without first
uninstalling the Desktop Agent from the user’s desktop, the Desktop Agent on
that user's computers will close automatically.
Moving Desktop Agent Users to a new Network User Data Folder
When Desktop Agent users are moved to new network user data folders, the contents of
each network user data folder is moved to a new directory. The new directories can be
existing Storage Locations or other directories on the network.
When the network user data folder is moved to a UNC location (for example,
\\myserver\userdata\username) rather than an existing Storage Location, the
permissions on the new location may need to be modified. The local administrator group
and the owner of the files must have read and change permissions for the network user
data folder, and the Everyone group should be removed.
For additional information on using existing directories on the network as network user
data folders, see “Manually Creating New Network User Data Folders” on page 1074.
After the data is successfully moved, the data in the old network user data folders is
deleted. Subsequent backups will be stored in the new location for each user.
▼ To move one or more Desktop Agent users to a new network user data folder:
Note When the transfer is complete, each affected Desktop Agent will shut down and
then automatically restart within a 30 minute window.
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Users.
3. Select one or more user to be moved.
4. In the task pane, under User Tasks, click Move network user data folder.
1079

Managing Desktop Agent Users
5. Select the appropriate options as follows:
Move User
Item Description
User Lists the domain and user name of the selected user or users.
From Lists the current network user data folder location.
Destination
Move the user data
folder to an existing
Storage Location
Move the contents of the
user data folder to an
alternative location
6. Click Start to begin the data transfer.
Migrating A Desktop User to a New Computer
When a desktop user receives a new computer, DLO can be used to migrate user data to
the new computer. DLO accomplishes this task by staging a user’s backed up data on the
new computer using a restore process. When the user logs in, the data is restored to the
same location it occupied on the original computer. The final restoration of data occurs
automatically when the user logs in and does not require a connection to the media
server.
▼ To Migrate a Desktop User to a New Computer
Select this option to choose an existing Storage Location from
the drop-down list. A new network user data folder will be
created in the new Storage Location for each user who is moved.
Select this option to specify a new Storage Location. Type the
path in the box provided, or click Browse and navigate to the new
location. A new network user data folder will be created in the
new Storage Location for each user who is moved.
1. Restore the user data as described in “Restoring Files and Folders from the DLO
Administration Console” on page 1088
2. In step 8, select “Stage this user data on an alternate computer for a new DLO
installation.” The data is staged on the new computer.
When the owner of the staged data logs in to the new computer, DLO moves the
staged data to the same location it occupied on the original computer, completing the
data migration process.
1080 Administrator’s Guide

Viewing a List of Desktop Agent Users
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Users to list users in the results pane.
Managing Desktop Computers
Managing Desktop Computers
Desktop computers can be easily managed from the DLO Administration Console. You
can view and modify computer properties as well as enable, disable or delete computers
from the console. In addition, an immediate backup can be run on one or more selected
computers.
Modifying Computer Properties
Computer properties can be viewed and modified from the DLO Administration Console.
Computer properties are based on the profile to which the desktop computer owner is
assigned. Computer properties can also be changed by the desktop user if that user has
sufficient rights assigned in the profile.
▼ To view and modify computer properties:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Computers.
3. Right-click the computer for which you want to modify properties, and click
Properties.
4. To modify the backup schedule for the computer, click the Schedule tab.
1081

Managing Desktop Computers
5. Configure the schedule as follows:
Profile Schedule Dialog Box
Item Description
Use Profile schedule Select this option in the drop-down menu to use the scheduling
options specified in the profile.
Note If this option is selected, additional settings on the
Schedule tab cannot be modified.
Use customized schedule Select this option in the drop-down menu to specify a customized
schedule that differs from the profile schedule.
Run jobs
Whenever a file changes Select this option to back up files whenever they change.
On NTFS drives, backups will occur automatically whenever a file
changes. For FAT drives, you must enter a backup interval in the
Back up changed files every field.
According to a schedule Select this option to back up files according to a customized
schedule.
Click Edit schedule to configure the backup schedule. The backup
schedule is configured in step 10 of “Creating a New Profile.” .
Manually Select this option to require that the DLO Administrator or
desktop user initiate backups manually.
Log on/off options
Automatically run jobs
when logging on
Automatically run jobs
when logging off
Select this to begin a backup after the desktop user logs on to the
computer.
Select this to begin a backup when the desktop user logs off the
computer.
1082 Administrator’s Guide

Managing Desktop Computers
6. To modify computer options, click the Options tab and configure the computer
options as follows:
Additional Profile Options
Item Description
Use Profile options Select this option from the drop-down menu to use settings
specified in the profile.
Note If this option is selected, additional settings on the Options
tab cannot be modified.
Use customized options Select this option from the drop-down menu to specify settings
that differ from the profile options.
Note This option must be selected to enable access to additional
settings on the Options tab.
Limit disk space usage on
my computer to
Log file maintenance
Keep log files for a
minimum of (days)
After minimum number
of days, delete oldest log
files when combined size
exceeds (MB)
Logging options
Select this check box to limit disk space usage on the desktop
computer.
To limit the usage to a percent of drive space, select % and type
the maximum percentage of drive space to use.
To limit the usage to a specific size, select MB and type the
maximum number of MB to use on the local drive.
Type the minimum number of days to keep log files. Log files will
not be deleted until they are at least as old as specified.
Note Log files will not be deleted until their combined size
exceeds the setting for the combined size of all log files,
which is discussed below.
Type the maximum combined size of all log files to be retained
before the oldest log files are deleted.
Note You may have more than the specified number of MB of log
files stored if none of the log files are as old as specified in
the keep log files for a minimum of (days) setting.
Log groom messages Select this check box to create logs for grooming operations.
Log information
messages for backup
Select this check box to create logs for all backup operations.
1083

Managing Desktop Computers
Additional Profile Options (continued)
Item Description
Log warning messages Select this check box to create logs for all operations that generate
warnings.
Mail options
Enable incremental
backups of Outlook PST
files
Enable incremental
backups of Lotus Notes
email files
Select this check box to enable incremental backups of Microsoft
Outlook Personal Folder (PST) files. Incremental backups must be
enabled to allow PST files to be backed up while they are open.
If this option is not checked, PST files that are configured in
Outlook will be fully backed up each time the PST file is saved,
which generally occurs when Outlook is closed.
When Outlook PST files are backed up incrementally, only one
revision is maintained regardless of the number of revisions set in
the backup selection.
Note DLO is unable to perform incremental backups of Outlook
PST files unless Outlook is your default mail application.
When you restore Microsoft Outlook PST files, the restored PST
file will differ from the original PST file as explained in “Restoring
Microsoft Outlook Personal Folder Files” on page 1203.
Note Synchronized files cannot be backed up incrementally.
For additional information, see “Backing up Outlook PST files
Incrementally” on page 1179.
Select this check box to enable incremental backups of Lotus
Notes email files. Additional configuration may be necessary. See
“Backing Up Lotus Notes NSF Files Incrementally” on page 1180.
When Lotus Notes NSF files are backed up incrementally, only one
revision is maintained regardless of the number of revisions set in
the backup selection.
7. To view the computer backup folders, click the Backup Folders tab.
8. To modify the computer backup selections, click the Backup Selections tab.
See “Adding a Backup Selection” on page 1035. Profile backup selections are not
listed, and can only be modified directly in the profile as described in “Modifying a
Backup Selection” on page 1046.
9. To view synchronized selections for a computer schedule, click the Synchronized
Selections tab.
1084 Administrator’s Guide

Managing Desktop Computers
Synchronized selections can only be viewed from the Administration Console. They
are configured on the Desktop Agent as described in “Synchronizing Desktop User
Data” on page 1190.
10. To view and modify connection policies, click the Connection Policies tab.
Profile defined connection policies can only be modified in the profile. See
“Customizing Connection Policies” on page 1188.
Enabling or Disabling a Desktop Computer
When a computer is disabled, the Desktop Agent remains on the desktop computer. The
Desktop Agent can be used to restore files and view history, but backups are disabled and
the user cannot modify Desktop Agent settings.
▼ To enable or disable a desktop computer:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Computers.
3. In the results pane, select one or more computers to be enabled or disabled.
4. Right-click the selected computers and click Enable to enable the Desktop Agent to
run on the selected computers, or click Disable to prevent the Desktop Agent from
running on the selected computers.
Deleting a Desktop Computer from DLO
Deleting a desktop computer from DLO removes the computer from the DLO database
and deletes the backed up files. This feature is most commonly used for a desktop
computer that is no longer in use. Deleting a computer does not disable the Desktop
Agent software. If subsequent backups are performed by the Desktop Agent, the
computer entry will be added back to DLO. To prevent further backups from the
computer, disable the computer rather than deleting it.
▼ To delete a desktop computer from DLO:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Computers.
3. In the results pane, select one or more computers to be deleted.
1085

Backing up a Desktop from the Administration Console
4. In the task pane, under General Tasks, click Delete.
5. When asked if you want to delete each selected computer and all backup files, click
Yes.
Backing up a Desktop from the Administration Console
The DLO Administration Console can be used to run an immediate backup on one or
more desktop computers. This allows the administrator to force a backup of a computer
running in manual or scheduled mode.
▼ To run an immediate backup on a desktop computer:
1. On the DLO navigation bar, click Setup.
2. In the selection pane, click Computers.
3. In the results pane, select one or more computers on which to run an immediate
backup.
4. In the task pane, under Computer Tasks, click Run backup now.
Setting Blackout Windows
DLO can be configured to stop backups at specific times to selected file servers, or to file
servers managed by a specific maintenance server. This is done by configuring blackout
windows. When a blackout window is configured for a selected resource, backups to
network user data folders are suspended during the specified period.
Blackout windows are specific to the resource for which they are created. To use the same
schedule for two different resources, you must configure them separately.
▼ To configure a blackout window for a network resource:
1. On the DLO navigation bar, click Setup.
2. In the task pane, under Tool Tasks, click Blackout windows.
3. From the File Server list, select a network resource for which you want to configure a
blackout window.
4. Do one of the following:
1086 Administrator’s Guide

Backing up a Desktop from the Administration Console
■ To edit an existing schedule, select it from the drop-down menu.
■ To create a new schedule click New.
5. Configure the schedule as follows:
Blackout Window Schedule
Item Description
Enable Schedule Select this check box to activate this schedule.
Occurs Select the frequency of occurrence. Selections include on a specific
date and weekly.
Starts at Enter the start time for the blackout window.
For a blackout window on a specific date, enter the date on which the
blackout window is to start.
For a weekly blackout window, select the day of the week on which the
blackout window is to start.
Ends at Enter the end time for the blackout window.
For a blackout window on a specific date, enter the date on which the
blackout window is to end.
For a weekly blackout window, select the day of the week on which the
blackout window is to end.
6. Click OK.
Deleting a Blackout Window Schedule
▼ To delete a blackout window schedule:
1. On the DLO navigation bar, click Setup.
2. In the task pane, under Tool Tasks, click Blackout windows.
3. Under Schedules, select the schedule to be deleted.
4. Click Delete.
5. Click OK>
1087

Restoring Files and Folders from the DLO Administration Console
Restoring Files and Folders from the DLO Administration
Console
The administrator can restore files and folders to a desktop computer from the DLO
Administration Console.
Note DLO can overwrite a file which is in use by staging the file to be restored when
the desktop computer restarts. Using this feature requires that the currently
logged on user of the desktop computer has administrative rights on the
desktop computer. Alternatively, the file can be restored by first closing the
application which is using the file, or by restoring the file to an alternate
location.
▼ To restore files and folders from the DLO Administration Console:
1. On the DLO navigation bar, click Restore.
2. In the Computer pane, click the desktop from which the data to be restored
originated.
3. In the Backup Folder pane tree view, select the folder containing the files you want
to restore.
4. To restore the entire folder, check the folder in the Backup Folder pane.
5. To restore specific files, check the files in the File Version pane.
6. If multiple versions exist for a file, select the radio button for the file version you
want to restore.
Note When a desktop user deletes an original file, the backup files are retained until
they are deleted by the file grooming process. If an original file has been
deleted, but backup files are still available, the icon for the file in the restore
view will have a small red ‘x’ to indicate the deletion of the original file. See
“File Grooming” on page 1040 for additional information.
7. In the task pane, under Restore Tasks, click Restore files to open the Restore dialog.
1088 Administrator’s Guide

Restoring Files and Folders from the DLO Administration Console
8. Select the appropriate options as follows, and then click OK:
Restore Dialog Box
Item Description
Restore destination
Restore to original computer Select this option to restore the selected files or folders to
the computer from which they were originally backed up.
Note When files or folders are restored to the original
desktop computer, the job is submitted to the
Desktop Agent and is run when the Desktop Agent
connects to the media server. The job may run
immediately if the desktop computer is currently on
the network, or the job may be pending for some time
if the desktop computer is not connected to the
network.
Restore to original folder Select this option to restore the file or folder to its original
location.
Redirect the restore to an
alternate folder
Restore to an alternate
computer
Redirect the restore to a
folder on an alternate
computer
Stage this user data on an
alternate computer for a
new DLO installation
Select this option to restore the file or folder to a different
location on the original desktop.
Click Browse to browse to the folder where you would like
to restore the file.
Select this option to restore the selected items to a network
or local drive on a computer other than the one from which
they were originally backed up.
Note When files or folders are restored to a folder on an
alternate computer, the restore job is processed
immediately from the network user data folder by
DLO. The job is not queued to the Desktop Agent.
Select this option to restore the data to a selected folder on
an alternate computer.
Select this option to migrate user data to a new computer.
See “Migrating A Desktop User to a New Computer” on
page 1080 for additional information.
1089

Restoring Files and Folders from the DLO Administration Console
Restore Dialog Box (continued)
Item Description
Preserve folder structure Check this box to restore the data with its original directory
structure intact. If you clear this option, all data (including
the data in subdirectories) is restored to a single folder in
the path you specify.
Restore Options
If file already exists: Select Do not overwrite to cancel the restoration of files
that already exist in the destination folder.
Select Prompt to be prompted before overwriting the file if
it already exists in the destination folder.
Select Overwrite to overwrite the file without prompting if
it already exists in the destination folder.
Restore deleted files Select this option if you would like to restore files even
though the original has been deleted.
Preserve security attributes on
restored files
9. Click OK.
Note If you customize NTFS permissions or directory attributes, such as compression or
encryption for files or folders, you must reapply these settings after restoration. If
you use a password for your PST file, you must reset the password after restoring
your PST file.
10. In the Restore Summary dialog box, review the selected restore settings, and do one
of the following:
■ Click Print to print a copy of the restore summary.
■ Click Restore to continue with the restore.
11. Click OK when the restore job completes.
Select Preserve security attributes on restored files to
preserve security information in restored files.
You may need to uncheck this box to successfully restore a
file if the source file security conflicts with the destination
security. Unchecking this option causes the security
information to be removed from the restored file.
1090 Administrator’s Guide

Searching for Files and Folders to Restore
▼ To search for desktop files and folders to restore:
1. On the DLO navigation bar, click Restore.
Restoring Files and Folders from the DLO Administration Console
2. In the Computer pane, click the desktop on which you would like to search for files to
restore.
3. In the task pane, under Restore Tasks, click Search for files to restore.
4. Select the appropriate options as follows:
Search Dialog Box Options
Item Description
Search for file names with this
text in the file name
5. Click Search.
Type all or part of the name of the file or folder you want
to find. Wildcard entries are accepted, for example
*proj.doc.
Modified Select this option to search for files that were modified
during a specific time frame, and then select the time
frame.
Today Select this option to search for files modified on the
current calendar day.
Within the past week Select this option to search for files modified in the last
calendar week.
Between Select this option to search for files modified during a
range of days.
Of the following type Select this check box to select a file type from the list
provided.
Of the following size Select this check box and then enter information as
follows:
◆ Select from equal to, at least, or at most in the first
drop-down menu.
◆ Type a file size.
◆ Select KB, MB, or GB.
1091

Restoring Files and Folders from the DLO Administration Console
6. In the results pane, check the items to be restored.
In some cases the Restore Search view may contain duplicate entries for the same
file. If this occurs, you can select either file to restore and receive the same outcome.
7. Click Restore.
8. Select the appropriate options as outlined in “Restoring Files and Folders from the
DLO Administration Console” on page 1088.
9. Click OK.
1092 Administrator’s Guide

How to Recover DLO Servers and User Data
How to Recover DLO Servers and User Data
DLO stores information in two major locations: the media server and the File Server. The
media server stores the configuration database and the File Server stores the user data.
The following recovery scenarios are discussed:
■ “Recovering Data for a Single User Using DLO Emergency Restore” on page 1094
■ “Recovering Data for a Single User without Using DLO Emergency Restore” on
page 1095
■ “Recovering a Damaged or Corrupt media server” on page 1096
■ “Recovering a damaged or corrupt File Server” on page 1096
This article assumes that both the media server and File Server are periodically backed
up to another disk, tape, or other media. Also note that for many DLO installations the
media server and File Server are on the same computer.
About Encrypted User Data
DLO encrypts user data using a user-specific, randomly generated encryption-key. The
encryption-keys are stored in DLO's configuration database on the media server. The
encryption-keys are also stored, in encrypted form, on the File Server, as detailed in the
next section.
About DLO Emergency Restore and Recovery Passwords
DLO's Emergency Restore feature is used to recover Desktop Agent user data from the
File Server in the event that the configuration database is lost. Emergency Restore can
also simplify the task of restoring user data for users that have been deleted via the DLO
Console. To use the Emergency Restore feature, a Recovery Password must have been
established before the database was lost or the user was deleted. If user data is restored
from another media then the Recovery Password that was in effect when the user data
was backed up must be used to recover the data.
A Recovery Password is established when the DLO Console is first launched. For older
versions of DLO, a recovery password had to be manually established using the DLO
command line interface. The recovery password is used to encrypt each user's
encryption-key so the key can safely be stored on the File Server. The Emergency Restore
feature prompts the administrator for the Recovery Password, which is used to decrypt
the user's encryption-key. The encryption-key is then used to decrypt the user's data. If a
recovery password has not been established the Emergency Restore feature cannot be
used to restore encrypted user data.
1093

How to Recover DLO Servers and User Data
Changing Recovery Passwords
If the Recovery Password must be changed the administrator must be aware that the
former Recovery Password will still be in affect for former backups of the File Server.
The Recovery Password should only be changed if mandated for security reasons, such as
a compromised password. If possible the Recovery Password should never be changed.
Changing or establishing a Recovery Password will never aide in restoring existing user
data. In fact, it can make it more difficult: changing the Recovery Password can result in
multiple Recovery Passwords being in use at the same time.
For example, consider the case where a recovery password “pwd1” is established when
DLO is installed. Each user's encryption-key is encrypted with the Recovery Password
stored on the File Server. When the File Server is backed up, the backup copies all use the
Recovery Password “pwd1”. If the recovery password is subsequently changed to “pwd2”,
the user encryption-keys on the File Server will be changed to be encrypted with the new
Recovery Password. Subsequent backups of the File Server will use the Recovery
Password “pwd2”. Now there are backups of the File Server using both “pwd1” and
“pwd2” as the Recovery Password. When the Emergency Restore feature is used, the
administrator will have to use the Recovery Password that was in affect at the time the
File Server was backed up.
What Happens When a User is Deleted via the DLO Console
When a user is deleted using the DLO Console all data associated with the user is deleted.
This includes the configuration data, stored on the media server, and the user data,
stored on the File Server. The method for restoring data for a deleted user depends upon
whether a Recovery Password has been established or not.
Recovering Data for a Single User Using DLO Emergency Restore
The Emergency Restore feature can be used to restore data for a deleted user if the user
data can be restored from a backup of the File Server and a Recovery Password was
established prior making the backup. See the section “About DLO Emergency Restore and
Recovery Passwords” on page 1093 for more information on Recovery Passwords.
▼ To recover data for a single user using DLO Emergency Restore:
1. Restore the user-data to its original location on the File Server or to any other
temporary location.
2. Use the DLO Command Line Interface to restore the data to DLO.
dlocommandu -emergencyrestore -w -ap
1094 Administrator’s Guide

How to Recover DLO Servers and User Data
Recovering Data for a Single User without Using DLO Emergency
Restore
If the Recovery Password was not established or has been lost, restoring data for a
deleted user requires that both the media server and the File Server be restored to a
single point in time before the user was deleted.
1. Take both the File Server and media server offline
2. Backup both the File Server and media server. Ensure that the backup includes the
DLO configuration database and the all user data. This backup will be used to restore
DLO back to its current state once the data is recovered. If any DLO data is not backed
up it may be impossible to return to the current state.
3. Restore the user data to the File Server. If possible, restore just the data for the user
being restored. If unsure, the entire volume on the File Server can be restored,
provided that precaution was taken in step 2 to ensure the entire volume was backed
up.
4. Restore the configuration database to the media server. The default database path is
C:\Program Files\Symantec\Backup Exec\Data.
5. Restart the media server.
6. Use the DLO Console to restore the user's data. Select “Restore to an alternate
computer” and restore the data to a temporary location.
7. Restore both the File Server and media server back to the most recent state.
1095

How to Recover DLO Servers and User Data
Recovering a Damaged or Corrupt media server
There are two cases for recovering a damaged or corrupt media server.
Case 1
A non-system disk on the media server fails or is otherwise corrupted.
The recovery procedure for Case 1 is as follows:
1. Fix or replace the failed disk
2. Restore the entire disk from the backup copy
3. Restart the computer
Case 2
The media server's system hard drive fails, or the media server computer needs to be
replaced with a new computer then the recovery procedure is as follows:
The recovery procedure for Case 2 is as follows:
1. Setup the computer with the operating system software. Be sure to use the same
computer name as the failed media server.
2. Install DLO on the new media server. Be sure to use the same version of DLO as was
installed on the failed media server.
3. Restore the DLO database files, overwriting the database files created when DLO was
installed. The default database path is C:\Program Files\Symantec\Backup
Exec\Data.
4. Restart the computer
Recovering a damaged or corrupt File Server
If a non-system disk on the File Server fails or is otherwise corrupted the recovery
procedure is as follows:
1. Fix or replace the failed disk
2. Restore the entire disk from the backup copy
3. Restart the computer
1096 Administrator’s Guide

How to Recover DLO Servers and User Data
If the File Server's system hard drive fails, or the file server computer needs to be
replaced with a new computer then the recovery procedure is as follows:
1. Setup the computer with the operating system software. Be sure to use the same
computer name as the failed File Server.
2. If the File Server had the DLO Maintenance Server installed, then install the DLO
Maintenance Server on the computer. Be sure to use the same version of DLO as was
installed on the failed File Server.
3. Restore the DLO file data.
1097

Monitoring DLO Job Histories
Monitoring DLO Job Histories
Use the History view on the DLO Administration Console to view information about the
status of Desktop Agent jobs. These jobs include backup, restore, synchronization, and
move user jobs. History logs are generated by each desktop running the Desktop Agent
and are viewed in either the DLO Administration Console or the Desktop Agent Console.
You can filter history logs so that old or less important logs are not displayed, or so that
only backup or restore job logs display.
Viewing the DLO Job History
By default, the history logs are updated when a job runs and an hour has passed since the
last update. However, if the job's status changes, the history log is updated immediately
to reflect the new status.
▼ To display the History view in the DLO Administration Console:
❖ On the DLO navigation bar, click History.
The History view includes a computer history and a job history for each desktop that
is displayed. The History pane displays all desktops that are backed up with the
Desktop Agent and provides the following summary information:
Computer History pane
Item Description
User The user name of the user who is logged on to the desktop that generated
the message.
Computer The name of the desktop that generated this message.
Last Backup Result The outcome of a completed backup, for example, Success, Warnings,
Failed, Canceled.
For descriptions of possible backup outcomes, see “Desktop Computer
Status Summary” on page 1017.
Profile The name of the Profile to which the desktop user who is logged on to the
desktop belongs.
For more information on profiles, see “About DLO Profiles” on page 1020
1098 Administrator’s Guide

Computer History pane (continued)
Item Description
The Job History pane displays the following information:
Monitoring DLO Job Histories
Backup Mode The backup mode specified in the profile. Backup modes include:
Desktop Data Folder
Size
Network Data Folder
Size
Network Data Folder
Path
Job History pane
Item Description
◆ Continuous. The backup occurs whenever a file changes.
◆ Scheduled. The backup occurs according to a schedule.
◆ Manual. The backup occurs when initiated by the desktop user.
The current size of the desktop user data folder.
The current size of the network user data folder.
The location of the network user data folder.
Start Time The time the job was started.
End Time The time the job ended.
Operation The operation performed in this job, such as backup or restore.
Status The current status of the job, such as active, completed, completed
with errors, completed with warnings, canceled, or failed.
Files Protected (Desktop) The number of files copied to the desktop user data folder during
the job.
Size Protected (Desktop) The total bytes of data copied to the desktop user data folder during
the job.
Files Protected (Network) The number of files copied to the network user data folder during
the job.
Size Protected (Network) The total bytes of data copied to the network user data folder during
the job.
Errors The number of errors, if any, that were generated during the job.
1099

Monitoring DLO Job Histories
Setting Job History View Filters
The job history view can be filtered to show only the type of jobs you wish to view. You
can filter jobs by type, alerts received during the job, or by the time period in which the
job was run.
▼ To set job history view filters:
1. On the DLO navigation bar, click History.
2. Click the desktop for which you want to view the history.
3. On the task pane, under Job History View Filters, click one of the following:
Type of Jobs Viewed in the History View
Item Description
List all jobs Lists history logs for all jobs that have run on the selected desktop.
These may include backup, synchronization, restore, or move user
jobs.
List backup jobs only Lists history logs only for backup jobs that have run on the
selected desktop.
List restore jobs only Lists history logs only for restore jobs that have run on the
selected desktop.
4. Filter job history logs based on alerts received by selecting one or more of the
following:
Selections to Filter Job Histories Based on Alerts Received
Item Description
Show successful jobs Lists history logs for all successful jobs on the selected desktop.
Show jobs with warnings Lists history logs for all jobs that generated warnings on the
selected desktop.
Show jobs with errors Lists history logs for all jobs that generated errors on the selected
desktop.
Show canceled jobs Lists history logs for all jobs that were cancelled on the selected
desktop.
1100 Administrator’s Guide

Monitoring DLO Job Histories
5. Select a time frame for filters to be displayed by selecting one of the following:
Time Frame for Job Histories viewed
Item Description
Show last 24 hours Lists history logs that have been generated in the last 24 hours,
and that meet all other filtering criteria.
Show last 7 days Lists history logs that have been generated in the last 7 days, and
that meet all other filtering criteria.
Show all Lists all history logs that also meet all other filtering criteria.
Viewing History Logs
History logs are listed for each job on a desktop computer. They are viewed in the DLO
ADministration Console History view.
▼ To view a history log in the DLO Administration Console:
1. On the DLO navigation bar, click History.
2. In the History pane, select the computer for which you want to view a history log.
3. In the Job History pane, click the log you want to view.
4. In the task pane, under General Tasks, click View history log file to display the log
file viewer with all log messages for this job.
1101

Monitoring DLO Job Histories
Log File Viewer
5. To filter the results, select the appropriate options as follows:
Log File Viewer Filtering Options
Item Description
Search for log entries in
All log files Select this option to show all log entries in the log file viewer.
Current log file Select this option to search only those log entries in the current
log file.
With timestamp Select this check box to search only those log entries within a
specified time period. The options include:
Today - Show only log files that were created today.
Within the last week - Show all log files created in the last week.
Between dates - Show all log files created between the dates
entered.
1102 Administrator’s Guide

Log File Viewer Filtering Options (continued)
Item Description
6. Click Search.
7. Double click on a log entry to view additional details.
8. Click Close.
Searching History Logs
Monitoring DLO Job Histories
Of the following type Select this check box to show only logs of the indicated type. The
available selections will vary depending on the log file, but may
include the following:
◆ Backup
◆ Restore
◆ Move User
◆ Maintenance
With File names
containing
Select this check box to enter a filename, or filename type.
Wildcard entries are supported.
Example: *gold.doc
Note When using wildcards you must use the ‘*’ wildcard. For
example, *.tmp will return all results with the .tmp
extension while .tmp will return only files explicitly named
.tmp.
Limit search to Check this option to limit the log files displayed to one of the
following types of log entries:
◆ Informational entries only
◆ Error and warning entries only
◆ Error entries only
◆ Warning entries only
◆ Local data folder entries only
◆ Local data folder error entries only
◆ Network data folder entries only
◆ Network data folder error entries only
History log files are easily searched using the Log File Viewer. This enables you to refine
the list of jobs to only those of interest.
1103

Monitoring DLO Job Histories
▼ To search for log files using the DLO Administration Console:
1. On the DLO navigation bar, click History.
2. In the task pane, under General Tasks, click Search log files to display the log file
viewer.
3. Set filtering options as discussed in step 5 on page 1102.
4. Click Search.
5. Double click on a log entry to view additional details.
6. Click Close.
1104 Administrator’s Guide

Monitoring Alerts on the DLO Administration Console
Monitoring Alerts on the DLO Administration Console
Alerts appear in DLO when the system needs administrator attention. Alerts help the
DLO administrator understand the current condition of DLO jobs by displaying
information on jobs.
Alerts can be generated to provide general information, or they can be in response to a
problem. When an alert is generated due to a problem, the alert contains information
about the problem, and in some cases, recommendations on how to fix it.
The DLO Administrator can choose to display all alerts, or to limit the type of alerts that
appear.
Active alerts display the alerts that are active in the system and need a response from the
operator. Alert history displays alerts that have been responded to or alerts that have
been automatically cleared from the system.
In addition, the status bar at the bottom of the screen displays an alert icon. The icon
that displays in the status bar is for the most severe type of alert in the Active alerts list.
Therefore, if the current or most recent alert is not the most severe, the icon in the status
bar will not match the icon for the most recent alert in the alert list.
Alerts are filtered by the Desktop Agent to minimize the load on DLO. By default, alerts
are limited to one of each type in 24 hours. For example, you will see only one “Local Out
of Disk Condition” alert in a 24-hour period from a desktop running the Desktop Agent.
Note “Backup/Restore complete” alerts cannot be filtered. If you enable these alerts,
they are generated each time a backup or restore job completes.
Active alerts that are older than a specified number of days are cleared and moved into
the alert history. The alerts in the history will be deleted if they have been cleared for
more than a specified number of days. When alerts in the history have been cleared for a
given number of days, which by default is seven days, they are deleted by a Backup Exec
archive operation.
If an alert is manually cleared, it is moved into the alert history. Deleting an alert
manually removes it permanently.
You can set up DLO to notify recipients when alerts occur. See “Configuring Alerts for
Notification” on page 1112 for additional information.
1105

Monitoring Alerts on the DLO Administration Console
DLO Administration Console Alerts View
Following are descriptions of the types of alerts:
Alert Categories
Alert Type Description
Informational Notifies you that an expected action has occurred, such as the
successful completion of a backup or restore job.
Warning Notifies you of a potential issue. For example, an alert is generated
when a backup has not been completed on a desktop within a given
time frame, or if the disk quota limitations are being approached.
Error Notifies you of an active or pending danger to the application or its
data. An error would be generated, for example, if a backup failed to
complete, or if a desktop has exceeded its disk quota limitations.
1106 Administrator’s Guide

Possible alerts are listed in the following table:
DLO Alerts
Type Name Description
Errors
Warnings
A backup job has
completed with errors
A restore job has
completed with errors
An error has occurred on
the fileserver
Desktop user data folder
disk space full
Desktop user data folder
storage limit has been
reached
Filename, directory name,
or volume label syntax is
incorrect.
Network user data folder
disk space full
Network user data folder
storage limit has been
reached
Unable to configure the
Desktop Agent
A backup job has
completed with warnings
Monitoring Alerts on the DLO Administration Console
A backup job has completed, but errors were generated.
A restore job has completed, but errors were generated.
The volume containing the desktop user data folder is full.
There is insufficient free disk space to back up the current
file. The file will be copied directly to the network user data
folder.
The specified disk storage limit was reached when
attempting to add a new revision to the desktop user data
folder.
Indicates either a storage system problem that requires
attention, or a file name denied by SRM software. If the
latter, these files should be added to DLO’s global exclude
list. See “Configuring Global Exclude Filters” on page 1065
for additional information.
The volume containing the network user data folder is full.
There is insufficient free disk space to back up the current
file.
The specified disk storage limit was reached when
attempting to add a new revision to the network user data
folder.
A new user has connected, but for an unknown reason,
cannot be configured properly.
A backup job has completed, but warnings were generated.
1107

Monitoring Alerts on the DLO Administration Console
DLO Alerts (continued)
Type Name Description
A restore job has
completed with warnings
A restore job has not
completed in 1 hour
A restore job has not
completed in 12 hours
A restore job has not
completed in 24 hours
Desktop user data folder
approaching storage limit
Desktop user data folder
disk space low
Evaluation period daily
reminder
Evaluation period has
expired
Network user data folder
approaching storage limit
Network user data folder
disk space low
A restore job has completed, but warnings were generated.
A restore job was submitted, but an hour has passed and
the restore job is not complete.
A restore job was submitted, but 12 hours have passed and
the restore job is not complete.
A restore job was submitted, but 24 hours have passed and
the restore job is not complete.
The amount of stored backup data in a user’s desktop user
data folder is approaching the specified size limit.
The volume containing the desktop user data folder is
running low.
This reminder specifies the number of days remaining in
the evaluation period for the Symantec Desktop and
Laptop Option
The DLO evaluation period has expired. A license is
required to continue to use DLO.
The amount of stored backup data in a user’s network user
data folder is approaching the specified size limit.
The volume containing the network user data folder is
running low.
No backups in 14 days A desktop computer has not performed a backup for 14
days.
No backups in 28 days A desktop computer has not performed a backup for 28
days.
No backups in 7 days A desktop computer has not performed a backup for 7
days.
No matching automated
user assignment
A new user connected, but no matching Automated User
Assignment was found.
1108 Administrator’s Guide

DLO Alerts (continued)
Type Name Description
Informational
A backup job has
completed
A restore job has been
queued
A restore job has
completed
PST file was skipped
because it is not
configured in Outlook
Configuring Alerts
▼ To configure alerts:
1. On the DLO navigation bar, click Alerts.
2. In the task pane, under Alert Tasks, click Configure alerts.
Monitoring Alerts on the DLO Administration Console
A backup job has completed successfully.
A restore job was initiated from the media server.
A restore job has completed successfully.
A PST file on the desktop computer was not backed up
because it was not configured in Microsoft Outlook.
User was configured A new user connected and was successfully configured.
3. Check the alerts you want to receive, and clear the check boxes for the alerts you do
not want to receive.
1109

Monitoring Alerts on the DLO Administration Console
Configure Alerts Dialog Box
4. To send notification to recipients when the selected alerts are generated, do the
following:
Note Alerts must be configured for notification before selecting recipients. See
“Configuring Alerts for Notification” on page 1112 and “Configuring Recipients for
Notification” on page 1116 for additional information.
■ Select one or more alerts from the list. To select multiple alerts, click one item and
press or while clicking the other items.
■ Check the Send notification of selected alert to recipients check box.
■ Click Recipients.
■ Select the recipients to receive notification of the alerts.
■ Click OK.
5. Click OK.
Managing DLO Alerts
From the Alerts view in the DLO Administration Console, you can view a subset of alerts,
clear alerts, and move alerts to a history log.
1110 Administrator’s Guide

▼ To view DLO alerts:
1. On the DLO navigation bar, click Alerts.
Monitoring Alerts on the DLO Administration Console
2. Select Active alerts to view active alerts, or Alert history to view alerts that have
been cleared.
Note Alerts that are older than a specified number of days are cleared and moved
into alert history. The number of days is specified in the Backup Exec
Administration Console.
3. To filter alerts by type, select one or more options from Active Alerts View Filters or
Alert History View Filters in the task pane as described below:
Active Alerts View Filters
Item Description
Show errors Lists error alerts for the selected view.
Show warnings Lists warning alerts for the selected view.
Show information Lists informational alerts for the selected view.
4. To view the properties of an alert, right-click the alert in the Active Alerts or Alert
History list and select properties.
5. If a log file is associated with the alert, a link is provided to the log file. Click this link
to view the log file.
6. Click Close to close the Alert Information dialog.
Clearing DLO Alerts
Alerts are set by default to move to the alert history after a specified; however, some
alerts may appear frequently and fill the Active alerts pane. You may want to clear these
alerts to the Alert history pane before they are automatically moved by the system.
▼ To clear DLO alerts:
1. On the DLO navigation bar, click Alerts.
2. If needed, filter the Alerts view as described in “To view DLO alerts:” on page 1111.
1111

Configuring Alerts for Notification
3. From the alert list, select one or more alerts that you want to clear.
4. In the task pane, under Alert Tasks, do one of the following:
■ Select Respond to clear only the selected alerts.
■ Select Respond OK to all to change the status of all alerts to cleared.
Configuring Alerts for Notification
DLO has several methods to notify you of alerts:
■ SMTP
■ MAPI
■ Lotus Notes email
■ Pagers
■ Printers
■ Net Send
To use notifications you must perform the following:
■ Configure the methods you want to use to notify the recipient. Printer and Net Send
notification methods do not require pre-configuration.
■ Configure recipients. Recipients are individuals, computer consoles, printers, or
groups. They can be configured to use one or more of the notification methods.
■ Assign the recipients to alerts or jobs for notification.
Configuring Alert Notification Methods
DLO can be configured to notify individuals of specified alerts using the following
methods:
■ SMTP email Notification. See “Configuring SMTP Email for Notification” on
page 1113.
■ MAPI email Notification. See “Configuring MAPI email for Notification” on
page 1114.
■ VIM (Lotus Notes) email Notification. See “Configuring VIM email for Notification”
on page 1115.
■ Pager Notification. See “Configuring a Pager for Alert Notification” on page 1115.
1112 Administrator’s Guide

Configuring SMTP Email for Notification
Configuring Alerts for Notification
You must have an SMTP-compliant email system, such as a POP3 mail server to receive
alert notification messages using the SMTP notification method.
▼ To configure the SMTP email notification method:
1. From the Tools menu, click Email and Pager Notification.
2. Click the SMTP Configuration tab.
3. Select the appropriate options as follows:
SMTP Configuration dialog box
Item Description
Enable Select this check box to activate the notification method.
SMTP mail server Type the name of an SMTP mail server on which you have a valid
user account. DLO will not check the server name or the email
address for validity.
SMTP port Defaults to a standard SMTP port. In most cases, the default
should not have to be changed.
Sender Name Type the name of the user from whom the notification message
will be sent.
Sender email address Type the email address of the user from whom the notification
message will be sent.
The email address should contain a name that identifies the user
to the mail server, followed by an at sign (@) and the host name
and domain name of the mail server. For example,
john.smith@company.com.
Enable SMTP
Authentication
Select this check box to enable SMTP authentication
SMTP server login Type the SMTP server login credentials
sender password Type the password for this login.
confirm password Re-type the password again to confirm.
1113

Configuring Alerts for Notification
4. Click OK.
Related Topics:
“Configuring Recipients for Notification” on page 1116
Configuring MAPI email for Notification
You must have a MAPI-compliant email system, such as Microsoft Exchange to receive
alert notification messages using the MAPI notification method.
Note If you install Outlook after installing DLO, you must stop and restart the DLO
Administration Service for MAPI email notification to work and to save the MAPI
configuration settings.
▼ To configure MAPI alert notification:
1. From the Tools menu, click Email and Pager Notification.
2. Click the MAPI Configuration tab.
3. Select the appropriate options as follows:
MAPI Configuration dialog box
Item Description
Enable Select this check box to activate the notification method.
Mail server name Type the name of the Exchange server. You must use an
Exchange server to which the DLO service account has access.
Mailbox name of sender Type the mailbox from whom the notification message will be
sent, for example, John Smith. The name appears in the From
field in the message and does not require a full address.
Note The DLO services must be running under a domain
account that has rights to the Exchange mailbox used for
MAPI notification to save the MAPI configuration settings.
4. Click OK.
Related Topics:
“Configuring Recipients for Notification” on page 1116
1114 Administrator’s Guide

Configuring VIM email for Notification
Configuring Alerts for Notification
You must have a VIM (Lotus Notes) compliant email system to receive alert notification
messages using the VIM notification method.
▼ To configure VIM alert notification:
1. From the Tools menu, click Email and Pager Notification.
2. Click the VIM Configuration tab.
3. Select the appropriate options as follows:
VIM Configuration dialog box
Item Description
Enable Select this check box to activate the notification method.
Notes client directory Type the path of the directory in which the Notes client is
located.
Mail password Type the password that enables you to connect to the Notes
client.
Confirm mail password Re-type the password that enables you to connect to the Notes
client.
4. Click OK.
Related Topics:
“Configuring Recipients for Notification” on page 1116
Configuring a Pager for Alert Notification
You can configure DLO to page you with alert notification messages. You must have a
modem set up on your system to use the pager notification method. You must be sure
that the modem you are using can communicate properly with your paging service in
order for pager notification to work properly. Before you set up pager notification,
contact your paging service for information about the recommended brand of modem to
use with your paging service.
1. From the Tools menu, click Email and Pager Notification.
2. Click the Pager Configuration tab.
1115

Configuring Recipients for Notification
3. Select the appropriate options as follows:
Item Description
Enable Check Enable to activate this alert
notification method.
Select a modem for
sending pages
4. Click OK.
Select a modem from the list. Only
modems that are recognized in
Windows appear in the list.
Configuring Recipients for Notification
Recipients are individuals with a predefined notification method, computer consoles,
printers, or groups. Recipient configuration consists of selecting a notification method
and defining notification limits. After you create entries for the recipients, you can
assign them to alerts or jobs. The following types of recipients can be configured for
notifications:
■ Person. An individual that has a predefined method of notification such as SMTP,
MAPI, or VIM email, or a pager. You must configure the notification method before
you can enable it for the recipient.
■ SNMP Trap. SNMP Traps are sent to a computer that is configured to receive them.
■ Net Send. A computer that serves as a notification recipient.
■ Printer. A specific printer to which notifications can be sent.
■ Group. A group of one or more recipients, including person recipients, Net Send
recipients, and other groups.
Related Topics:
“Configuring Alerts for Notification” on page 1112
Configuring SMTP Mail for a Person Recipient
You can configure a person recipient to receive SMTP email notification messages if you
have configured the SMTP notification method.
1116 Administrator’s Guide

▼ To configure SMTP mail for a person recipient:
1. From the Tools menu, click Recipients.
2. Click New.
3. Click Person .
4. Click OK.
Configuring Recipients for Notification
5. In the Name field, type the name of the recipient that you want to configure.
6. Click the SMTP Mail tab.
7. Select the appropriate options as follows:
SMTP Mail dialog box
Item Description
Enable Select this check box to activate this notification method for the
recipient.
Address Type the email address of the person to whom the notification
message will be sent. For example, john.smith@company.com.
Test Enables you to test the notification configuration for the
recipient.
Limit the number of notifications sent
Enable Select this check box to activate the option.
Notify me a maximum of x
times within x minutes
Reset the notification
limits after x minutes
Type the total number of notifications that can be sent to the
recipient for all alerts that are generated within a specified
number of minutes. After the specified number of notifications
have been sent, additional notifications are not sent until the
specified minutes have been reached. The maximum number of
minutes you can set is 1440, which is the number of minutes in a
day.
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications that are sent
is reset to zero.
1117

Configuring Recipients for Notification
SMTP Mail dialog box (continued)
Item Description
Limit when notifications can be sent
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
Notification for Recipients” on page 1129.
8. Click OK.
Configuring MAPI Mail for a Person Recipient
You can configure a person recipient to receive MAPI email notification messages if you
have configured the MAPI notification method.
▼ To configure MAPI mail for a person recipient:
1. From the Tools menu, click Recipients.
2. Click New.
3. Click Person .
4. Click OK.
5. In the Name field, type the name of the recipient that you want to configure.
6. Click the MAPI Mail tab.
7. Select the appropriate options as follows:
MAPI Mail dialog box
Item Description
Enable Select this check box to activate this notification method for the
recipient.
1118 Administrator’s Guide

MAPI Mail dialog box (continued)
Item Description
8. Click OK.
Configuring VIM Mail for a Person Recipient
Configuring Recipients for Notification
Mailbox Type the email address or mailbox name of the recipient to
whom the notification message will be sent. For example,
john.smith@company.com or John Smith.
Test Enables you to test the notification configuration for the
recipient.
Limit the number of notifications sent
Enable Select this check box to activate the option.
Notify me a maximum of x
times within x minutes
Reset the notification
limits after x minutes
Limit when notifications can be sent
Type the maximum number of notifications sent to the recipient
for all alerts generated within the specified number of minutes.
After the specified number of notifications have been sent,
additional notifications are not sent until the specified minutes
have been reached. The maximum number of minutes that can
be set is 1440, which is the number of minutes in a day.
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications sent is reset
to zero.
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
Notification for Recipients” on page 1129.
You can configure a person recipient to receive VIM email notification messages if you
have configured the VIM notification method.
1119

Configuring Recipients for Notification
▼ To configure VIM mail for a person recipient:
1. From the Tools menu, click Recipients.
2. Click New.
3. Click Person .
4. Click OK.
5. In the Name field, type the name of the recipient that you want to configure.
6. Click the VIM Mail tab.
7. Select the appropriate options as follows:
VIM Mail dialog box
Item Description
Enable Select this check box to activate this notification method for the
recipient.
Address Type the email address of the recipient to whom the notification
message will be sent. For example, JohnSmith@company.com.
Test Enables you to test the notification configuration for the
recipient.
Limit the number of notifications sent
Enable Select this check box to activate the option.
Notify me a maximum of x
times within x minutes
Reset the notification
limits after x minutes
Limit when notifications can be sent
Type the total number of notifications sent to the recipient for all
alerts generated within the specified number of minutes. After
the specified number of notifications have been sent, additional
notifications are not sent until the specified minutes have been
reached. The maximum number of minutes that can be set is
1440, which is the number of minutes in a day.
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications sent is reset
to zero.
1120 Administrator’s Guide

VIM Mail dialog box (continued)
Item Description
Configuring a Pager for a Person Recipient
Configuring Recipients for Notification
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
Notification for Recipients” on page 1129.
You can configure a person recipient to receive notification messages by pager if you
have configured the pager notification method.
▼ To configure a pager for a person recipient:
1. From the Tools menu, click Recipients.
2. Click New, and then click Person .
3. Click OK.
4. In the Name field, type the name of the recipient that you want to configure.
5. Click the Pager tab.
6. Select the appropriate options as follows:
Pager dialog box
Item Description
Enable Select this check box to activate this notification method for the
recipient.
Carrier Phone Type the area code and phone number to access the paging
service provider’s modem. The paging service number may be
different from the number you enter to manually send a page.
Country/region name and
code
Enter the country or region name and country code in which the
pager is located.
1121

Configuring Recipients for Notification
Pager dialog box (continued)
Item Description
Pager Pin Type the pager identification number provided by the paging
service provider. You will have a pin if you use TAP services and
in most cases, the number is the last seven digits of the pager’s
phone number.
Advanced Pager setup options
Advanced Enables you to configure additional settings for the pager. For
more information about the options, see “Advanced Pager
Information dialog box” on page 1123.
Test Enables you to test the notification configuration for the
recipient.
Limit the number of notifications sent
Enable Select this check box to activate the option.
Notify me a maximum of x
times within x minutes
Reset the notification
limits after x minutes
Limit when notifications can be sent
Type the total number of notifications sent to the recipient for all
alerts generated within the specified number of minutes. After
the specified number of notifications have been sent, additional
notifications are not sent until the specified minutes have been
reached. The maximum number of minutes that can be set is
1440, which is the number of minutes in a day.
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications sent is reset
to zero.
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
Notification for Recipients” on page 1129.
1122 Administrator’s Guide

Configuring Recipients for Notification
7. Click Advanced to configure advanced pager setup options and select the
appropriate options as follows:
Advanced Pager Information dialog box
Item Description
Pager Configuration
Password Type the password for the pager, if one is required.
Message Length Type the maximum number of characters you want to use for
messages. The number is determined by the paging service
provider.
Retrys Type the number of times you want the paging service provider to
retry the page. The number is determined by the paging service
provider.
Pager type
Numeric Select this option if you are configuring a pager that accepts only
numbers.
Alpha-numeric Select this option if you are configuring a pager that accepts letters
and numbers.
Modem Configuration
Modem Baud Rate Select the speed of the modem. The speeds that appear are limits
set by the paging service; select the appropriate speed regardless of
the modem speed rating.
Data bits, Parity, Stop
bit
Select the communication protocol. In most cases, you should use
the Windows default.
8. Click OK to save the settings in the Advanced Pager Information dialog box, and then
click OK to save the pager configuration settings.
1123

Configuring Recipients for Notification
Configuring a SNMP Trap Recipient
▼ To configure a SNMP Trap as a recipient:
1. From the Tools menu, click Recipients.
2. Click New.
3. Click SNMP Trap.
4. Click OK.
5. Select the appropriate options as follows:
SMTP Mail dialog box
Item Description
Name Type a name for the SNMP Trap recipient.
Host Type the name of the SNMP host computer.
Port Enter the SNMP port number. The default SNMP port is 162.
Limit the number of notifications sent
Enable Select this check box to activate the option.
Notify me a maximum of x
times within x minutes
Reset the notification
limits after x minutes
Limit when notifications can be sent
Type the total number of notifications sent to the recipient for all
alerts generated within the specified number of minutes. After
the specified number of notifications have been sent, additional
notifications are not sent until the specified minutes have been
reached. The maximum number of minutes that can be set is
1440, which is the number of minutes in a day.
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications sent is reset
to zero.
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
1124 Administrator’s Guide

SMTP Mail dialog box (continued)
Item Description
6. Click OK.
7. Click Close.
Configuring a Net Send Recipient
Configuring Recipients for Notification
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
Notification for Recipients” on page 1129.
You can configure Net Send to send notification messages to a target computer or user.
Note If the target computer has Internet pop-up advertisement blocking software
installed, the Net Send notification message will not display.
▼ To configure a Net Send recipient:
1. From the Tools menu, click Recipients.
2. Click New and then click Net Send.
3. Click OK.
4. Select the appropriate options as follows:
Net Send Recipient Properties dialog box
Item Description
Name Type the name of the recipient for whom you are configuring the
notification.
Target Computer or User
Name
Type the name of the computer or user to whom you are sending
the notification. You should enter a computer rather than a user
because the Net Send message will fail if the user is logged off
the network.
Note If the target computer has Internet pop-up advertisement
blocking software installed, the Net Send notification
message will not display.
1125

Configuring Recipients for Notification
Net Send Recipient Properties dialog box (continued)
Item Description
All Computers Select All Computers to send the notification to all the
computers in the network.
Test Enables you to test the notification configuration for the
recipient.
Limit the number of notifications sent
Enable Select this check box to activate the option.
Notify me a maximum of x
times within x minutes
Reset the notification
limits after x minutes
Limit when notifications can be sent
5. Click OK.
Type the total number of notifications sent to the recipient for all
alerts generated within the specified number of minutes. After
the specified number of notifications have been sent, additional
notifications are not sent until the specified minutes have been
reached. The maximum number of minutes that can be set is
1440, which is the number of minutes in a day.
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications sent is reset
to zero.
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
Notification for Recipients” on page 1129.
1126 Administrator’s Guide

Configuring a Printer Recipient
Configuring Recipients for Notification
You can select installed printers as a notification method for recipients; however, fax
printer devices are not supported by DLO. Only printers that were configured using the
same username and password as the DLO service account can be selected.
▼ To configure a printer recipient:
1. From the Tools menu, click Recipients.
2. Click New and then click Printer.
3. Click OK.
4. Select the appropriate options as follows:
Printer Recipient Properties dialog box
Item Description
Name Type the recipient for whom you are configuring the notification.
You cannot use a fax printer device to receive the notification.
Target Printer Select the name of the printer to which the notification message
will be sent.
Test Enables you to test the notification configuration for the
recipient.
Limit the number of notifications sent
Enable Select this check box to activate the option.
Notify me a maximum of x
times within x minutes
Reset the notification
limits after x minutes
Limit when notifications can be sent
Type the total number of notifications sent to the recipient for all
alerts generated within the specified number of minutes. After
the specified number of notifications have been sent, additional
notifications are not sent until the specified minutes have been
reached. The maximum number of minutes that can be set is
1440, which is the number of minutes in a day.
Select this check box to enter the number of minutes that must
be reached before the notification limits are reset. When the time
limit has been reached, the number of notifications sent is reset
to zero.
1127

Configuring Recipients for Notification
Printer Recipient Properties dialog box (continued)
Item Description
Enable Select this check box to activate the option and configure the
length of time the recipient is available for notification.
Schedule Enables you to select the days and times when notifications can
be sent to the recipient. For more information, see “Scheduling
Notification for Recipients” on page 1129.
Configuring a Group Recipient
Groups are configured by adding recipients as group members. A group contains one or
more recipients and each recipient receives the notification message. Members of the
group can be a combination of individual persons, computers, printers, or other groups.
▼ To configure a group recipient:
1. From the Tools menu, click Recipients.
2. Click New and then click Group.
3. Click OK.
4. In the Group Name field, type the name of the group for whom you are configuring
the notification.
5. Do one of the following:
Item Description
To add members to the
group
To remove members from
the group
6. Click OK.
The new group can be added to other groups.
Select recipients from the All Recipients list, and then
click Add to move them to the Group Members list.
Select recipients from the Group Members list, and then
click Remove to move them to the All Recipients list.
1128 Administrator’s Guide

Scheduling Notification for Recipients
Configuring Recipients for Notification
During the recipient configuration process, you can enable the Limit when notifications
can be sent option to select the times of the day and the days of the week the recipient is
available to receive the notification messages. You can modify the schedule after the
recipient is configured by editing recipient notification properties.
See “Configuring Recipients for Notification” on page 1116 for more information on the
recipient configuration process.
▼ To configure the notification schedule for recipients:
1. On the Recipient Properties dialog box, under the Limit when notifications can be
sent group box, click Enable to activate the option.
Note To access the Recipient Properties dialog box, click Recipients from the Tools
menu. Click New to create a new recipient or select an existing recipient and then
click Properties.
2. Click Schedule.
3. Do any of the following:
Scheduling Notification
Item Description
Include work days Clear the Include work days check box to exclude Monday through
Friday from 8 A.M. to 6 P.M.
Include
weeknights
Note You can select any combination of Include work days, Include weeknights, or
Include weekends, or click any single hour of the chart to select or clear that
hour.
4. Click OK.
Clear the Include weeknights check box to exclude Monday through
Friday from 6 P.M. to 8 A.M.
Include weekends Clear the Include weekends check box to exclude Saturday and Sunday,
24 hours a day.
1129

Configuring Recipients for Notification
Editing Recipient Notification Properties
You can edit the recipient notification properties at any time and change the recipient
information, such as an email address, telephone number, or schedule.
▼ To edit the recipient notification properties:
1. From the Tools menu, click Recipients.
2. Select the recipient you want to edit.
3. Click Properties.
4. Edit the properties for the selected recipient.
You can edit any of the properties except for the recipient name in the Name field. To
modify the recipient name, you must create a new recipient, and then delete the old
one.
5. Click OK.
1130 Administrator’s Guide

Editing Recipient Notification Methods
Configuring Recipients for Notification
You can configure new notification methods or edit existing notification methods after
you configure recipients.
▼ To edit notification methods:
1. From the Tools menu, click Recipients.
2. Select the recipient to be edited and click Properties.
3. Edit notification properties for the following types of notification methods:
■ SMTP Configuration. See “SMTP Configuration dialog box” on page 1113.
■ MAPI Configuration. See “MAPI Configuration dialog box” on page 1114.
■ VIM Configuration. See “VIM Configuration dialog box” on page 1115.
■ Pager Configuration. Click Enable to activate or clear the notification method,
and then select a modem from the Configured Modems list.
4. Click OK.
Removing Recipients
You can delete recipients that do not want to receive notification messages; however, the
recipient is permanently removed upon deletion. If you want to keep the recipient, but do
not want the recipient to receive notifications, clear the Enable check box in the
recipient properties.
▼ To remove a recipient:
1. From the Tools menu, click Recipients.
2. Select the recipient you want to delete, and then click Remove.
1131

DLO Reports
3. Click OK.
DLO Reports
4. You can start the job after configuring the new recipients or edit recipient properties
or select other options from the Properties pane.
DLO provides a variety of reports that show detailed information about your DLO
operations. When you generate a report, you can specify filter parameters or a time
range for the data that you want to include in the report. If Adobe Acrobat is detected,
reports are displayed in Adobe Portable Document Format (PDF). If Adobe Acrobat is not
detected, the reports are displayed using HTML. Both PDF and HTML reports can be
saved and printed.
▼ To view the list of available reports:
❖ The following reports are available on the Reports view:
DLO Reports
Report Name Description
Active Alerts A list of all currently active alerts arranged chronologically.
Active Alerts by Computer A list of all currently active alerts sorted by computer name.
Active Alerts by User A list of all currently active alerts from all computers sorted
alphabetically by Desktop Agent user name.
Alert History A chronological list of alerts that have been sent by all
computers in the past.
Alert History by Computer A list of alerts that have been sent by all computers in the past,
sorted by computer name.
Alert History by User A list of alerts that have been sent by all computers in the past,
sorted by Desktop Agent user name.
Failed Backups A chronological list of computers that have a failed status for
the last backup.
1132 Administrator’s Guide

DLO Reports (continued)
Report Name Description
Related Topics:
“Viewing Report Properties” on page 1134
“Running a Report” on page 1133
Running a Report
DLO Reports
Failed Backup by Computer A list of computers that have a failed status for the last backup,
sorted by computer name.
Note Only the last backup result is stored in the DLO database,
so it is only possible to report the last backup result for
each desktop computer and not a complete history of
failed jobs.
Failed Backup by User A list of computers that have a failed status for the last backup,
sorted by Desktop Agent user name.
Note Only the last backup result is stored in the DLO database,
so it is only possible to report the last backup result for
each desktop computer and not a complete history of
failed jobs.
Last Backup Status A chronological list of the last backup status for all Desktop
Agent computers.
Last Backup Status by
Computer
When you run a report, you can specify filtering criteria to determine which items will be
included in the report. After the report is generated, only the items that match the
entered criteria appear in the report. If no criteria are entered, all available entries are
included in the report.
▼ To run a report:
1. On the navigation bar, click Reports.
A list of the last backup status for all Desktop Agent computers,
sorted by computer name.
Last Backup Status by User A list of the last backup status for all Desktop Agent computers,
sorted by Desktop Agent user name.
2. On the Reports pane, select the report you want to run.
1133

DLO Reports
3. In the task pane, under Reports Tasks, click Run report now.
4. Select the appropriate parameters for the data you want to include in the report from
the following available parameters:
Report Filters
Item Description
Computer Select this option to create a report for a specific computer, and
then enter a desktop computer name.
User Select this check box to create a report for a specific desktop user,
and then enter the user’s name.
Days Select this option to create a report for a specific number of days,
and then enter the number of days.
5. Click OK to run the report. The report can be printed or saved before it is closed.
6. Click OK to close the report.
Viewing Report Properties
Report properties provide a summary of information about each report. The properties
can be viewed, but not edited.
▼ To view Report Properties:
1. On the navigation bar, click Reports.
2. On the Reports pane, select the report for which you want to view properties.
3. In the task pane, under General tasks, click Properties.
The Report dialog box provides the following information:
Report Properties
Item Description
Title The name of the report.
Description
The type of data that is included in the report.
1134 Administrator’s Guide

Report Properties (continued)
Item Description
Category
4. Click OK.
DLO Reports
Classification for the report. Available report categories
include:
◆ Alerts
◆ Last Backup Status
◆ Failed Jobs
Author The creator of the report.
Subject
The version of the product for which the report was
created.
Keywords The primary information used to categorize the report.
File name
File size
Creation Date
The file name of the report template.
The size of the report template.
The date the report was installed on the system.
1135

Maintaining the DLO Database
Maintaining the DLO Database
The Desktop and Laptop Option uses an MSDE database instance named BKUPEXECDLO,
which operates separately from the Backup Exec database instance. You can maintain
both the Backup Exec database and the DLO database using the Backup Exec database
maintenance options. Use BEUtility to perform database operations on BKUPEXECDLO.
The DLO database is backed up and restored automatically each time the Backup Exec
database is backed up or restored.
If you use BEUtility to repair or recover the DLO database, all DLO Administration
Consoles must be closed. Otherwise, the operation will fail.
For more information about performing database maintenance, see “Configuring
database maintenance” on page 162.
For more information about using BEUtility to perform database operations, see
“Running the Backup Exec Utility” on page 802.
Clustering the Desktop and Laptop Option
To cluster DLO in a Backup Exec cluster configuration, you must install DLO on each
cluster node.
You cannot add DLO to an existing Backup Exec cluster. Either add DLO when you
configure a cluster, or uncluster an existing cluster, add DLO, and then reconfigure the
cluster.
If the Desktop Agent was installed from a cluster node that is now inactive, it will not
reconnect to the cluster following the unclustering process.
▼ To install Backup Exec 11.x and the Desktop and Laptop Option to an existing cluster:
1. Install Backup Exec 11.x on the active cluster node. Be sure to include the Desktop
and Laptop Option during the Backup Exec installation.
2. Install Backup Exec 11.x on each failover node. Be sure to include the Desktop and
Laptop Option during the Backup Exec installation.
Note Install Backup Exec when the node has access to the shared cluster disk.
3. From the server you used in step 1, complete the Cluster Configuration Wizard from
the Backup Exec console to configure the cluster-aware Backup Exec media server. Be
sure to include all cluster nodes where DLO was installed.
1136 Administrator’s Guide

Clustering the Desktop and Laptop Option
▼ To upgrade an existing Backup Exec 9.x or 10.x cluster that includes DLO:
1. Install Backup Exec 11.x on the active Backup Exec cluster node. Be sure to include
the Desktop and Laptop Option during the Backup Exec installation.
2. Install Backup Exec 11.x on each failover node. Be sure to include the Desktop and
Laptop Option during the Backup Exec installation.
Note Install Backup Exec when the node has access to the shared Backup Exec cluster
disk.
3. From the server you used in step 1, use the Cluster Configuration Wizard to
reconfigure cluster-aware Backup Exec with the same virtual server name. Add all
cluster nodes that were upgraded.
▼ To upgrade an existing Backup Exec 9.x or 10.x cluster and add DLO to the cluster:
1. Install Backup Exec 11.x on the active Backup Exec cluster node. Do not select the
DLO option.
2. Install Backup Exec 11.x on each failover node. Do not select the DLO option.
Note Install Backup Exec when the node has access to the shared Backup Exec cluster
disk.
3. Use the Cluster Configuration Wizard on the active Backup Exec cluster node to
uncluster all nodes. Click No when you are prompted to remove data on the shared
drive. Click Yes when you are prompted to make the data available to the local node.
4. Install DLO on all cluster nodes. All nodes must have DLO before you can recluster
them.
5. From the server you used in step 3, use the Cluster Configuration Wizard to
reconfigure cluster-aware Backup Exec with the same virtual server name.
6. Add all cluster nodes that were upgraded.
The DLO services are added to the Cluster Administrator.
1137

Clustering the Desktop and Laptop Option
▼ To reconnect a Desktop Agent to a cluster node after you uncluster DLO:
1. In the .dlo\.notify directory on the desktop user's Storage Location, create a text file
named NewMediaServerDesktopMachineName. For example, in the file named
NewMediaServerAdmin123, the desktop computer name is Admin123.
2. In the text file, type the name of the new DLO server on the first line and save the
file.
3. Repeat steps 1 and 2 for all desktops that will use a new DLO server.
If the desktop is running, it should connect to the new server. If the desktop is not
running, it should connect to the new server the next time it runs.
▼ To move a Storage Location in a DLO cluster environment:
Note These steps must be performed before you take DLO out of the cluster.
1. If the Storage Location is on a shared drive or virtual server, you must move the user
data for all of the Storage Location users. Move the user data to a Storage Location on
the local node.
2. Modify all automated user assignments that are configured to use the Storage
Location on the shared drive or virtual server so that they use another Storage
Location on the local node.
3. Verify that all user data was moved off the Storage Location on the shared drive or
virtual server and then delete it from the shared drive or virtual server.
Related Topics:
“Using Backup Exec with Veritas Cluster Server” on page 735
“Uninstalling Backup Exec from a Microsoft cluster” on page 707
“Installing the Backup Exec Desktop and Laptop Option” on page 987
“Installing Backup Exec on a Microsoft Cluster Server” on page 704
1138 Administrator’s Guide

DLO Command Line Interface Management Tools
DLO Command Line Interface Management Tools
DLO provides a number of powerful command line system tools to manage DLO server
operations as outlined in the following sections:
■ “DLO Command Syntax” on page 1139
■ “Commands in Detail” on page 1140
DLO Command Syntax
DLO Command Line Interface commands are run from the installation directory and are
executed with the DLOCommandu command.
Note The default installation directory for Backup Exec DLO version 11d and later is:
C:\Program Files\Symantec\Backup Exec\DLO
If Backup Exec DLO is upgraded from a previous version that was installed in a
different location, the installation will be moved to this new location.
DLOCommandu is executed as follows:
DLOCommandu [remote-server-options] command
[command-options-and-arguments] [log-file-option]
Remote Server Options
Remote server options allow you to specify the name of the remote server on which you
want to run a command. You can also enter your username and password if required.
Remote server options are as follows:
Remote Server Options
Option Description
–C Remote computer name, default to local computer
–N Fully qualified user name, e.g. Enterprise\GFord. The default is
the current user
–W User password if –n is specified
1139

DLO Command Line Interface Management Tools
Commands in Detail
See the following topics for detailed information on available commands:
■ “-AssignSL Command” on page 1140
■ “-EnableUser Command” on page 1141
■ “-ChangeServer Command” on page 1143
■ “-KeyTest Command” on page 1144
■ “-ListProfile Command” on page 1145
■ “-ListSL Command” on page 1146
■ “-ListUser Command” on page 1147
■ “-LogFile Command” on page 1148
■ “-Update Command” on page 1149
■ “-EmergencyRestore Command” on page 1152
■ “-SetRecoveryPwd Command” on page 1152
■ “-NotifyClients Command” on page 1153
■ “-InactiveAccounts Command” on page 1153
-AssignSL Command
The –AssignSL command is used to assign a new Storage Location to existing users
when the existing Storage Location is no longer available. The new Storage Location
must be managed by the same media server
Caution If the existing Storage Location is accessible, use the Move User command
to move users to a new Storage Locations. See “Moving Desktop Agent
Users to a new Network User Data Folder” on page 1079 for additional
information.
Desktop Agent users can be assigned to new Storage Locations based on User
account name, profile name, profile ID, Storage Location, Storage Location ID, and
File server.
The Desktop Agent that is being moved will be disabled until the media server is
notified that the move is complete.
Syntax:
DLOCommandu –assignsl –NI [–A | –F | –P | –PI | –S | –SI | –U ]
1140 Administrator’s Guide

DLO Command Line Interface Management Tools
Note Wildcard matches (*) are permitted in profile, Storage Location and user
names.
Quotation marks are required around names if the name contains a space or
colon.
Command Options:
–AssignSL Options
Option Description
–NI The -NI option is used to specify the name of the new storage
location.
–A Assigns a new storage location to all users.
–F Assigns a new storage location to users with storage locations on
the named file server.
–P Assigns a new storage location to users with named profile.
–PI Assigns a new storage location to users with given profile id.
–S Assigns a new storage location to users with named storage
location.
–SI Assigns a new storage location to users with the given storage
location ID.
–U Assigns a new storage location to named user account only.
Examples:
DLOCommandu –assignsl –NI DLO_SL02 –A
DLOCommandu –assignsl –NI DLO_SL03 –U mmouse
-EnableUser Command
The -EnableUser command is used to enable or disable a user. Users can be
enabled or disabled by All, file server (all storage locations), profile name, profile ID,
storage location name, storage location ID or username.
1141

DLO Command Line Interface Management Tools
Use this command if you want to force the desktop computer to refresh from the
media server.
Syntax:
DLOCommandu -enableuser [ –E | –D ] [ –A | –F | –P | –PI | –S | –SI | –U ]
Note Wildcard matches (*) are permitted in profile, Storage Location and user
names.
Quotation marks are required around names if the name contains a space or
colon.
Command Options:
–EnableUser Command Options
Option Description
–A Enables or disables all users on the media server.
–E | –D Enables or disables a user account. The default value is to enable a
user (i.e. –E).
–F Enables or disables users with storage locations on the named file
server.
–P Enables or disables users with the specified profile name.
–PI Enables or disables users that are assigned to the specified profile.
–S Enables or disables users assigned to the specified storage
location.
–SI Enables or disables users in the specified storage location.
–U Enables or disables only the user with the specified user name.
Examples:
DLOCommandu –enableuser –E –A
DLOCommandu –enableuser –D –U mmouse
1142 Administrator’s Guide

-ChangeServer Command
DLO Command Line Interface Management Tools
The -ChangeServer command is used to reassign users to another media server.
Each desktop user must back up to a network user data folder that is managed by the
same media server to which the user is assigned. If a matching automated user
assignment is available on the new media server, the user is automatically assigned
a profile and storage location. If a matching automated user assignment is not
available, the user can be manually configured.
When a Desktop Agent user is reassigned from one media server to another, the
user’s current profile settings and existing backup files are not moved. They remain
on the original file server.
Syntax:
DLOCommandu –ChangeServer –M [ –A | –F | –P
| –PI | –S | –SI | –SP | –U
]
Note Wildcard matches (*) are permitted in profile, Storage Location and user
names.
Quotation marks are required around names if the name contains a space or
colon.
1143

DLO Command Line Interface Management Tools
Command Options:
–ChangeServer Command Options
Option Description
–A Switches all users (default).
–F Switches users with storage locations on the named file server.
–M The new media server name.
–P Switches users based on profile name.
–PI Switches users based on profile id.
–S Switches users based on storage location name.
–SI Switches users based on storage location id.
–SP Switches users based on storage location path.
–U Switches users based on user name.
Examples:
DLOCommandu –ChangeServer –M sunshine –P Desktop*
DLOCommandu –ChangeServer –M sunshine –SP \\moonlight\EngDept
DLOCommandu –ChangeServer –M sunshine –SP
\\moonlight\EngDept\Enterprise–MNoel
-KeyTest Command
The -KeyTest command scans network user data to identify encrypted data that
cannot be restored with the current encryption key.
Syntax:
DLOCommandu –KeyTest
1144 Administrator’s Guide

DLO Command Line Interface Management Tools
Command Options:
The following options can be used independently or in combination.
–KeyTest Command Options
Option Description
-f The -f option forces a full scan for all users even if the data has
already been validated.
-quar The -quar option quarantines any unrestorable data encountered.
Data that cannot be restored with the current encryption key is
quarantined in the .dloquarantine folder in the user’s network
user data folder. If this option is not specified the data will be
scanned and reported but will not be quarantined.
-purge The -purge option deletes any previously quarantined data.
Examples:
Check for unrestorable data that has not
previously been validated, or that was backed up
by an old version of the Desktop Agent:
Scan all data, even if it has been previously
validated, to identify unrestorable data.
Quarantine unrestorable data.
-ListProfile Command
The -ListProfile command is used to list profiles of Desktop Agent users.
Syntax:
DLOCommandu –listprofile [ –A | –P ]
DLOCommandu –keytest
DLOCommandu –keytest -f -quar
Note Wildcard matches (*) are permitted in profile, Storage Location and user
names.
Quotation marks are required around names if the name contains a space or
colon.
1145

DLO Command Line Interface Management Tools
Command Options:
–ListProfile Command Options
Option Description
–A Lists settings for all profiles (default).
–P Lists settings for only the specified profile.
Examples:
DLOCommandu –listprofile –A
DLOCommandu –listprofile –P yourprofile
-ListSL Command
The -ListSL command is used to list the DLO storage locations.
Syntax:
DLOCommandu –listsl [ –A | –F | –S ]
Note Wildcard matches (*) are permitted in profile, Storage Location and user
names.
Quotation marks are required around names if the name contains a space or
colon.
1146 Administrator’s Guide

Command Options:
–ListSL Command Options
Option Description
–A Lists all storage locations (default)
Examples:
DLOCommandu –listsl –A
DLOCommandu –listsl –F yourserver
DLOCommandu –listsl –S yourSL
-ListUser Command
DLO Command Line Interface Management Tools
–F Lists storage locations for the named server
–S Lists only the named storage location
The -ListUser command is used to list by All, file server, profile name, profile ID,
storage location name, storage location ID, or user name.
Syntax:
DLOCommandu –listuser [ –A | –F | –P | –PI | –S | –SI | –U ]
Note Wildcard matches (*) are permitted in profile, Storage Location and user
names.
Quotation marks are required around names if the name contains a space or
colon.
1147

DLO Command Line Interface Management Tools
Command Options:
–ListUser Command Options
Option Description
–A Lists settings for all users (default)
–F Lists settings for users with storage locations on the named file
server
–P Lists settings for users by profile name
–PI Lists settings for users by profile id
–S Lists settings for users by storage location name
–SI Lists settings for users by storage location id
–U Lists settings for users by user name
Examples:
DLOCommandu –listuser –A
DLOCommandu –listuser –P yourprofile
DLOCommandu –listuser –U mmouse
DLOCommandu –listuser –U m*
-LogFile Command
The LogFile option allows administrators to change the path or name of the LogFile.
And, since every command overwrites the LogFile, to track all events (logs), you
must change the path\name of the next LogFile to retain older versions.
The default path is the “\Logs” folder under the installed path:
C:\Program Files\Symantec\Backup Exec\NT\DLO\LogsIf DLO was
upgraded from a previous version, the original directory structure is used. The
default path for the “\Logs” folder in previous releases was:
C:\Program Files\VERITAS\Backup Exec\NT\DLO\Logs
Syntax:
–LogFile
1148 Administrator’s Guide

DLO Command Line Interface Management Tools
Note Wildcard matches (*) are permitted in profile, Storage Location and user
names.
Quotation marks are required around names if the name contains a space or
colon.
Command Options:
–LogFile Command Options
Option Description
Specifies the path to the new LogFile
Specifies the filename for the new LogFile
Examples:
DLOCommandu –logfile test.log
DLOCommandu –logfile “c:\test.log”
-Update Command
The -Update command is used to list, add, remove, and publish Desktop Agent
updates. See “Updating DLO” on page 1007 for detailed information on updating the
Desktop Agent software.
Syntax:
DLOCommandu –update [ –list | –add | –remove | –publish ]
Subcommands:
The following subcommands allow you to list, add, remove or publish updates. See
“Command Options:” on page 1150 for a description of the available options for each
command.
–Update SubCommands
SubCommand Description
–List [-A|–UI ] Lists settings for previously used updates.
1149

DLO Command Line Interface Management Tools
–Update SubCommands
SubCommand Description
–Add –F Adds an “update definition file” to the updates list
and assigns it a unique update ID number. The
update ID number is used when the update is
published with the -publish command.
–Remove [-UI |–A] Removes a file or files from the update list.
–Publish [-R] –UI [–P
|–PI |–U
]
Command Options:
–Update Command and Sub-Command Options
Option Description
–A Updates all
Makes the specified updates available to users.
Users can be identified by using the following
options:
-P Profile name
–PI Profile RecordID. To obtain the profile
RecordID, run the -listprofile command.
–U User name
–F Specifies a text file that contains update records
–U Specifies a fully qualified user name, such as
Enterprise\JFord
–P Specifies a profile name
–PI Specifies a profile record id
–R Designates to unpublish
–UI Specifies an update record id
Note Wildcard matches (*) are permitted in profile, Storage Location and user
names.
Quotation marks are required around names if the name contains a space or
colon.
1150 Administrator’s Guide

Examples:
❖ To list published updates:
Lists settings for all published updates
DLOCommandu -update -list -A
To list details of a specific update:
DLOCommandu -update -list -UI
DLO Command Line Interface Management Tools
❖ To add a file to the update list and assign it an ID number
Prepares an update file to be published and assigns it a unique Record ID number.
The Record ID number is returned when the following command is executed:
DLOCommandu -update -add -f cntlfile.txt
❖ To publish an update to make it available to Desktop Agents
Makes updates available to users. You can specify whether to make this available to
all users, specific users, or users in a profile. You can also use wildcards to specify
profile and user names.
To publish an update for a profile:
DLOCommandu -update -publish -UI -P
DLOCommandu -update -publish -UI 63 -P yourprofile
To publish an update for a specific user:
DLOCommandu -update -list -UI -U
To publish an update for all users:
DLOCommandu -update -list -UI -U *
❖ To remove a file from the update list
Removes a file from the update list. If the file was previously published, it must be
unpublished before removing it.
To unpublish:
DLOCommandu -update -publish -R -UI 33
To remove:
DLOCommandu -update -remove -UI 3
1151

DLO Command Line Interface Management Tools
-EmergencyRestore Command
The -Emergency Restore command uses the DLO administrator’s recovery
password to restore user data that would otherwise be unavailable if the DLO
database is damaged or corrupted. The recovery password must be known to execute
this command. The data will be restored to the specified location in the original data
structure, but it will no longer be encrypted. See “Setting a Recovery Password” on
page 993 for more information.
Syntax:
DLOCommandu –EmergencyRestore -W -AP
Command Options:
–EmergencyRestore Command Options
Option Description
Specifies the full path to the user share directory
-W Specifies the recovery password
-AP Specifies the path to which data will be restored
-SetRecoveryPwd Command
The -SetRecoveryPwd command is used to change the recovery password, which
enables you to retrieve encrypted data that would otherwise be lost if the DLO
database is damaged or corrupted. The -SetRecoveryPwd command now updates the
password for existing users as well as new users.
Once set, this recovery password can only be changed using the DLO command line
interface tools.
See “Setting a Recovery Password” on page 993 for more information.
Syntax:
DLOCommandu –SetRecoveryPwd
1152 Administrator’s Guide

-NotifyClients Command
DLO Command Line Interface Management Tools
The -NotifyClients command forces the Desktop Agents to refresh the profile settings
immediately, or the next time the Desktop Agent connects if it is offline.
Syntax:
DLOCommandu –notifyclients
-InactiveAccounts Command
The -InactiveAccounts command is used to list and delete accounts that have not been
used in a specified number of days.
To list inactive accounts:
dlocommandu -inactiveaccounts -list -days
This command returns a list of inactive accounts. The list includes the following
information, which is used to delete specific accounts:
■ computer name
■ computer ID
■ domain\user name
■ userID
To delete specific inactive accounts:
dlocommandu –inactiveaccounts -delete –U -M -days
dlocommandu –inactiveaccounts -delete –UI -MI -days
Where –U and -M are used to delete the user and computer by name and –UI and -MI
are used to delete the user and computer by ID.
To delete ALL accounts inactive for a specified number of days:
dlocommandu -inactiveaccounts -delete -a
1153

DLO Command Line Interface Management Tools
-RenameDomain Command
The -RenameDomain command is used after a Windows NT domain has been renamed.
Running the RenameDomain command changes each Desktop Agent user’s record to
reflect the new domain name and changes the path for the network user data folder. It
also notifies each Desktop Agent of the change.
Syntax:
DLOCommandu –RenameDomain
-RenameMS Command
The -RenameMS command is used when a media server has been renamed. Running the
RenameMS command updates the installation share, storage location paths and network
user data folder paths. It also notifies each Desktop Agent of the change.
Syntax:
DLOCommandu –RenameMS
-LimitAdminTo Command
The -LimitAdminTo command limits administration of DLO to the specified group or
user.
Syntax:
DLOCommandu –LimitAdminTo -NAU
DLOCommandu –LimitAdminTo -NAU
1154 Administrator’s Guide

Command Options
-LimitAdminTo Command Option
Option Description
-NAU The -NAU option is used to add a new
DLO administrator or to add a group
that can be used of DLO
administrators.
-DAU The -DAU option is used to delete a
DLO administrator or a DLO
administration group.
-L The -L option lists all of the current
DLO administrators and groups.
-IOProfile Command
DLO Command Line Interface Management Tools
The -IOProfile command enables a profile to be exported from one media server, and
then imported to another media server. An option is also provided to import global
settings.
Note When a profile is imported, it does not initially have any users assigned to it, so
there is no immediate impact. When global settings are imported, they
immediately apply to all Desktop Agent users assigned to the server.
❖ To export a profile:
DLOCommandu –C -IOProfile -DBF -E
This exports the requested named profile (-E) from the specified server (-C) into the
named file (-DBF). It is not necessary to specify the master server name with the -C
option if the profile is on the same server where the command is run.
❖ To import a profile:
DLOCommandu –C < server name> -IOProfile -DBF
This imports the profile in the given file (-DBF) into the named server (-C.)
❖ To import the console settings for DLO administrator account management in
addition to the profile, use the IPRCS option as follows:
1155

DLO Command Line Interface Management Tools
DLOCommandu –C < server name> -IOProfile -DBF -IPRGCS
❖ To import the global settings in addition to the profile, use the IPRGS option as
follows:
DLOCommandu –C < server name> -IOProfile -DBF -IPRGS
1156 Administrator’s Guide

About the Desktop Agent
About the Desktop Agent
The Desktop Agent is the component of the Backup Exec Desktop and Laptop Option
that protects files on desktop and laptop computers (collectively referred to as desktops)
by backing up data to the desktop’s local drive and to a Storage Location on the network.
The DLO administrator initially configures the Desktop Agent. If the DLO administrator
has set your profile so that you can view the complete Desktop Agent and modify
settings, then you can restore files, synchronize files between multiple desktops,
configure backup selections, set schedules, view history and more.
Your profile determines the level of interaction between you and the Desktop Agent. The
administrator may also configure the Desktop Agent to run without a user interface,
with a fully functional user interface, or somewhere in between.
Features and Benefits of the Desktop Agent
The Desktop Agent provides the following features:
■ Data Protection. Selected files on the desktop are automatically copied to user data
folders on the desktop’s local drive and on the network. The Desktop Agent can be
configured so that no user interaction is required. Files are protected automatically
when the desktop is online or offline. Backup Exec protects the data by backing up
the network user data folders on the DLO file server.
■ Data Availability. A user can access data from multiple desktops in multiple locations
if they are using the same login credentials on each desktop. Users can also restore
previous file revisions, even when the desktop is offline, if they are saving at least
one file revision in the desktop user data folder.
■ Synchronization. A user that accesses multiple computers with the same login
credentials can configure folders to be synchronized on each of the computers. When
a synchronized file is changed on one computer, the updated file is copied to the
network user data folder and also to the desktop user data folder on all other
computers that are configured for synchronization.
1157

System Requirements for the Desktop Agent
System Requirements for the Desktop Agent
The following are the minimum system requirements for running this version of the
Desktop Agent.
Minimum System Requirements
Item Description
Operating System Microsoft Windows 2000
Microsoft Windows XP Service Pack 1 (SP1) or later
Microsoft Windows XP Professional x64 Edition
Note The Desktop Agent is not supported on any server operating
system, including Windows Server 2003, Windows Storage
Server 2003, and Windows 2000 Server.
Processor Pentium system
Memory Required: 256 MB RAM
Recommended: 512 MB (or more for better performance).
Internet Browser Internet Explorer 5.01 or later; however, version 5.5 is recommended.
Disk Space 25 MB hard disk space required after Microsoft Windows is installed
(typical installation). Additional space may be required if the desktop
user data folder is enabled.
Other Hardware Network interface card or a virtual network adapter card.
Installing the Desktop Agent
The DLO administrator determines who installs the Desktop Agent. It can be either the
administrator or the desktop user. Administrator rights are required to install the
Desktop Agent. After the Desktop Agent is installed on a desktop, anyone who logs on to
that desktop can use the Desktop Agent. The logged on user will only have access to DLO
backup files associated with the logged on account.
All computers running the DLO Administration Console or the Desktop Agent should be
set to a common time. This can be accomplished by configuring the Windows Time
Synchronization service on the network. See www.microsoft.com for additional
information.
1158 Administrator’s Guide

Installing the Desktop Agent
Note You must have administrative rights to the desktop on which you want to install
the Desktop Agent. If you need to restart the desktop during installation, you must
use the same administrator login again to ensure that the installation completes
successfully.
▼ To install the Desktop Agent:
1. From the desktop on which you want to install the Desktop Agent, browse to the
network server where the installation files for the Desktop Agent are stored. The
default location is \\\DLOAgent. If you
are unsure of the location, contact the administrator.
2. Double-click the file setup.exe.
3. On the Welcome screen, click Next.
4. Read the license agreement, and then click I accept the terms in the license
agreement.
5. Click Next.
6. Do one of the following:
a. To change the location on the desktop’s local drive where the Desktop Agent will
be installed, click Change and enter the alternate location, then click OK.
b. To install the Desktop Agent in the default location, continue with step 7.
The default installation location is C:\Program Files\Symantec\Backup
Exec\NT\DLO.
7. Click Next.
8. Click Install.
9. Click Finish to install the Desktop Agent.
1159

Configuring the Desktop Agent
Configuring the Desktop Agent
The following topics are useful for reference when configuring the Desktop Agent:
■ “Connecting to the media server” on page 1160
■ “Using local accounts on desktop computers” on page 1160
■ “Using Alternate Credentials for the Desktop Agent” on page 1161
■ “Resetting Dialog Boxes and Account Information” on page 1163
■ “Changing Your Connection Status” on page 1163
■ “Disabling the Desktop Agent” on page 1164
■ “Enabling the Desktop Agent” on page 1164
Connecting to the media server
The Desktop Agent communicates with the DLO database and services on the media
server during normal operation. When using the Desktop Agent, you must connect to the
media serverusing a domain account.
Note If you connect to the media server with one set of credentials, and then attempt to
connect to the server using DLO with a different set of credentials, authentication
may fail. Restart the computer to reconnect.
When new information is available for the Desktop Agent, the Desktop Agent receives a
notification of this new information and retrieves it. This will happen, for example, when
settings or synchronized files change or if a software update is available. The Desktop
Agent and the media server do not contact each other directly.
Caution If you attempt to connect to a server using characters in the share name that
do not exist on the code page for the local system, the connection will fail. Code
pages map character codes to individual characters, and are typically specific
to a language or group of languages.
Using local accounts on desktop computers
You can log in to your desktop with a local account. If you log on to your desktop with a
local account, the Desktop Agent prompts you for your user name and password for your
domain account.
The following should be considered when using local accounts on desktops that run the
Desktop Agent:
1160 Administrator’s Guide

Configuring the Desktop Agent
■ You can only use a set of domain credentials with one local account. If you use more
than one local account on a desktop or laptop computer, you should either disable
DLO for other accounts or have unique domain credentials for each account. See “To
log on with alternate credentials or to disable accounts:” on page 1162 for additional
information.
Example If you usually log on to the desktop computer as
‘myusername’, you should have a domain account to use
for DLO with this account. If you also occasionally
log on as ‘administrator’, DLO can be disabled when
you are logged on to this account. Alternately, you
can provide a unique set of domain credentials to use
for DLO when you are logged on as ‘administrator’.
■ Multiple users of the same desktop computer can all use DLO, but must provide
unique credentials for the desktop computer and unique domain credentials for
connection with the Desktop Agent.
■ DLO does not support the Fast User Switching feature of Windows XP.
Related Topics:
“Using Alternate Credentials for the Desktop Agent”
Using Alternate Credentials for the Desktop Agent
The account used by the Desktop Agent is the logon account by default, but could be an
alternate account if one has been specified, such as when connecting across domains.
If you are logged on with credentials that are not recognized by the Desktop Agent, you
can specify alternate credentials for Desktop Agent operation and save the account
information for future sessions. If you prefer, you can disable an account for Desktop
Agent operations so that the Desktop Agent will not run when you are logged on with the
account currently being used. This dialog allows you to save this account info for future
connections.
Note If you have a previously established network connection to the media server and it
does not match the account the Desktop Agent is using, the Desktop Agent will
attempt to reconnect as the Desktop Agent user. If this fails, the following error
displays: “Multiple connections to a server or shared resource by the same user,
using more than one user name, are not allowed. Disconnect all previous
connections to the server or shared resource and try again.“ The account used by
the Desktop Agent is the logon account by default, but could be an alternate
account if one has been specified; for example, to connect across domains.
1161

Configuring the Desktop Agent
Using alternate credentials to work across domains
In a cross-domain configuration where there is no trust relationship, if multiple users
are running the same Desktop Agent, each user must provide a unique user name and
password in the media server domain. If different users use the same credentials, DLO
displays an error message stating that the user is already connected to the media server.
Note For information on resetting accounts that have been disabled for Desktop Agent
operation, see “To reset dialogs and account information:” on page 1163.
▼ To log on with alternate credentials or to disable accounts:
1. When you are logged on to the desktop computer with an account that is not
recognized by the Desktop Agent, the Alternate Credential dialog box will appear.
2. Specify Desktop Agent logging options as outlined below:
Alternate Credentials
Item Description
Use this account Select this option to enable the Desktop Agent to run when you are
using the account under which you are currently logged on.
Username Enter the user name for an account that is authorized for Desktop
Agent operation.
Password Enter the password for the account to be used for Desktop Agent
operation.
Domain Type the domain for the account to be used for Desktop Agent
operation.
Save my password Check Save my password to have DLO save and use this password
in the future to automatically authenticate to the media server or
storage location in the event of an authentication failure.
Note This option will only appear if the DLO administrator has
enbled this option. On newly-deployed Desktop Agents, this
option will not show until the second time the Desktop
Agent connects to the media server.
Disable this account Select this option to prevent the Desktop Agent from running
when you are using the account under which you are currently
logged on.
3. Click OK.
1162 Administrator’s Guide

Resetting Dialog Boxes and Account Information
Configuring the Desktop Agent
While using DLO, you can suppress dialogs by checking the Don’t show me this message
again check box. These dialogs can be reset so they will once again be displayed. If
passwords and account information are cleared, the Desktop Agent will prompt for this
information if it is required to access a resource.
▼ To reset dialogs and account information:
1. From the Tools menu, click Options.
2. If you want to reset any information dialogs suppressed by the Don’t show me this
message again check box, click Reset dialogs.
3. Click Yes when prompted to reset the dialogs.
4. If you want to clear any passwords and account information that the Desktop Agent
has stored, click Reset accounts.
5. Click Yes when prompted to clear the accounts.
6. Click OK.
Changing Your Connection Status
When you are using the Desktop Agent, your connection status is displayed in the lower
right corner of the Desktop Agent Console. When the Desktop Agent is in offline mode,
the following are true until you choose to work online again:
■ Files are not transferred to the network user data folder. Pending files remain in the
pending files list with a status of “Pending network.”
■ Job logs are not copied up to the network user data folder.
■ Alerts are not posted to the media server.
▼ To change your connection status:
1. Click the connection status on the lower right corner of the Desktop Agent.
2. Do one of the following:
■ Click Work Offline to place the Desktop Agent in offline mode.
■ Click Work online to place the Desktop Agent in online mode.
1163

Configuring the Desktop Agent
Note The DLO Administrator sets a maximum time after which the Desktop Agent will
automatically be returned to the online mode, assuming a network connection is
available.
Disabling the Desktop Agent
If your Profile allows it, you can disable the Desktop Agent.
▼ To disable the Desktop Agent:
1. From the Windows system tray, right-click the Desktop Agent icon.
2. Click Disable. This option will be grayed out if you do not have permission to take
this action.
Enabling the Desktop Agent
If the Desktop Agent has been disabled, and your Profile allows it, you can re-enable the
Desktop Agent.
▼ To enable the Desktop Agent:
1. From the Windows system tray, right-click the Desktop Agent icon.
2. Click Enable. This option will be grayed out if you do not have permission to take this
action.
1164 Administrator’s Guide

About the Desktop Agent Console
About the Desktop Agent Console
The Desktop Agent Console is the user interface for the Desktop Agent. Access to the
Desktop Agent Console is controlled by the DLO administrator. The DLO administrator
may choose from the following:
Display the complete interface. Enables desktop users to access all Desktop Agent
options.
Display only the status. Enables desktop users to view the status of backup jobs, but they
cannot change Desktop Agent settings or access options other than status. Desktop users
can right-click the system tray icon to open the status view or exit the program.
Display only the system tray icon. The desktop user sees only the Desktop Agent icon in
the system tray in the lower right corner of the screen. Desktop users can right-click the
system tray icon to exit the program.
Do not display anything. The Desktop Agent runs in the background. The desktop user
cannot view the Desktop Agent.
1165

About the Desktop Agent Console
Views menu
Tools Menu
Desktop Agent Console
Tasks Menu
Menu bar
Tasks bar Status bar Connection Status
1166 Administrator’s Guide

The Desktop Agent Console has the following components:
Desktop Agent Console Features
Item Description
About the Desktop Agent Console
Menu bar The menu bar appears across the top of the screen. To display a menu,
click the menu name. Some menu items are not available until an item is
selected from the console screen.
Tasks bar The Tasks bar appears on the left side of the Desktop Agent Console. To
hide the Tasks bar, from the View menu, select Tasks Bar. Actions are
initiated from the tasks bar, and these actions vary with the selected
view.
Views menu The Views menu appears in the Tasks bar and enables you to navigate to
the following views:
Status Provides job status, lists pending jobs, and summarizes recent backup
activity. See “Viewing the Desktop Agent Status” on page 1195 for
additional information.
Backup
Selections
Synchronized
Selections
Enables you to define what data is protected by the Desktop Agent. See
“Using the Desktop Agent to Back Up Your Data” on page 1168 for
additional information.
Enables you to configure the Desktop Agent to maintain a user’s
selected files and folders on multiple computers so that the most recent
backed up version is always available to the user. See “Synchronizing
Desktop User Data” on page 1190 for additional information.
1167

Using the Desktop Agent to Back Up Your Data
Desktop Agent Console Features (continued)
Item Description
Restore Enables the user to restore backed up data and search for backed up
files. See “Restoring Files Using the Desktop Agent” on page 1199 for
additional information.
History Displays Desktop Agent error, warning, and informational messages.
Tasks menu Actions are initiated from the tasks menu. These actions vary with the
selected view.
Tools menu
Options Enables you to do the following:
◆ Reset dialogs that have been suppressed by the Don’t show me this
message again check box.
◆ Clear passwords and account information that the Desktop Agent
has stored. See “Resetting Dialog Boxes and Account Information”
on page 1163 for additional information.
Note To ensure that you have the latest status and settings at any time while using the
Desktop Agent, from the Tasks menu, click Refresh.
Using the Desktop Agent to Back Up Your Data
When data is backed up by the Desktop Agent, it is transferred to the user data folder on
the desktop’s local drive. Then, the data is transferred to a network user data folder,
which is assigned by the DLO Administrator. Network user data folders are typically also
backed up by Backup Exec, which provides an additional level of protection.
Caution If you attempt to connect to a server using characters in the share name that
do not exist on the code page for the local system, the connection will fail. Code
pages map character codes to individual characters, and are typically specific
to a language or group of languages.
For information on backing up and restoring Microsoft Outlook PST files, see “Backing
up Outlook PST files Incrementally” on page 1179 and “Restoring Microsoft Outlook
Personal Folder Files” on page 1203.
1168 Administrator’s Guide

Using the Desktop Agent to Back Up Your Data
Select files that you want to protect from the Backup Selections view. Backup selections
are initially assigned by the administrator, but if the DLO administrator has set your
profile so that you can view the complete Desktop Agent and modify settings, then you
can choose your backup selections.
You can change Desktop Agent settings and backup selections when you are working
offline. The settings will be stored until you are once again working online, at which time
they are automatically transferred. If the administrator has also made changes that
conflict with the changes made on the Desktop Agent, the changes made by the
administrator will be used.
You can view and modify backup selections using two views: standard and advanced. The
standard view lists the contents of your local drives, allowing you to check off files and
folders to be backed up. It also uses default backup selection settings to add new
selections. The advanced view provides more configuration options for selections.
A backup selection consists of:
■ A folder or list of folders
■ Criteria for the files to be included or excluded from the backup
■ Limits on the number of file revisions to retain
■ Settings for compression, backup file deletion, and encryption
Managing Revisions
Revisions are versions of a file at a specific point in time. When a file is changed and
backed up, DLO stores a new revision. DLO stores and maintains a specific number of
revisions for all files in a backup selection. Because each backup selection is configured
separately, the number of revisions retained can vary for different backup selections.
When the number of revisions is exceeded, DLO removes the oldest revision,
maintaining only the specified number of revisions in the desktop and network user data
folders.
You can limit the number of revisions DLO retains in a given period of time. If you are
working on a document and backing it up frequently, all of your revisions could
potentially be just a few minutes apart. By specifying that you want to retain only 2
revisions every 24 hours, at least 120 minutes apart, you can retain older revisions for a
longer period of time. While some intermediate versions will not be retained, it does
support situations in which returning to an older revision is needed.
Another consideration in determining the number of revisions to retain is the amount of
storage space required to store the data. The amount of space required for backups can
be estimated by multiplying the number of revisions retained by the amount of data
protected.
1169

Using the Desktop Agent to Back Up Your Data
Example If you are retaining three revisions of each file and
have 10 MB to back up, approximately 30 MB of disk
space will be required.
Although compression can improve the space utilization, it varies significantly with file
type and other factors.
Alternate Stream Backup
DLO now protects all of the alternate streams for a file, including security streams. If a
new version of a file contains only alternate stream data modifications, the new version
replaces the old version without impacting the revision count.
Related Topics:
“Modifying Backup Selections in the Standard View” on page 1170
“Adding Backup Selections in the Advanced View” on page 1172
“Backing up Outlook PST files Incrementally” on page 1179
“Restoring Microsoft Outlook Personal Folder Files” on page 1203
“Restoring Files with Alternate Stream Data” on page 1204
File Grooming
The Desktop Agent grooms revisions based on backup selection settings and does this as
new revisions are created. The oldest revision is deleted when a new revision is created
that exceeds the limit.
Maintenance grooming is the grooming off of deleted files. It occurs at most once every
24 hours. Maintenance grooming occurs during the first backup that runs after 24 hours
have passed since the last maintenance grooming.
Modifying Backup Selections in the Standard View
The Backup Selections Standard view provides a list of drives, folders, and files that you
can select for backup.
Note Profile backup selections are those that were specified by the DLO administrator in
your profile. You cannot modify profile backup selections in the standard view. You
can only modify the backup selections that you create on the Desktop Agent.
Profile backup selections are displayed in the standard view with gray check boxes.
1170 Administrator’s Guide

Using the Desktop Agent to Back Up Your Data
They can be modified in the advanced view if the administrator has granted you
sufficient rights. See “Modifying Backup Selections in the Advanced View” on
page 1177 for additional information.
When you create new backup selections in the standard view, the default backup
selection settings are used. When you add new subfolders and files to the backup
selection using the standard view, these new backup selections will have the same
settings as the main folders.
In the Desktop Agent Backup Selection Standard view, files and folders are represented
in a tree view where users can select or deselect files and folders for backup. When the
check box next to a file or folder is grayed out, the selection was defined by the
administrator and can only be changed if the administrator has granted this right in the
profile definition. When a red 'X' appears in the check box next to a file or folder, this
item has been globally excluded from all backups by the administrator and cannot be
selected.
Standard View
▼ To modify backup selections in the Backup Selections Standard view:
1. Under Views in the Desktop Agent Tasks Bar, click Backup Selections.
2. Click Standard view.
3. Select the folders and files you want to back up.
1171

Using the Desktop Agent to Back Up Your Data
Expand selections by clicking the plus sign (+) and collapse selections by clicking the
minus sign (-).
Note To return to the last saved settings at any time, click Undo changes.
4. Click Save changes to save the new settings or Undo changes to return to the last
saved settings.
After clicking Save, previously backed-up selections that were unchecked are treated
like deleted backup selections and will no longer be backed up. The backup files for
this selection will be deleted after the number of days specified in the backup
selection settings. The source files for the deleted backup selection will not be
deleted by the Desktop Agent.
Checked folders that were not previously checked are added to the backup selections
for this desktop.
Adding Backup Selections in the Advanced View
▼ To add a backup selection in the Backup Selections advanced view:
1. Under Views in the Desktop Agent Tasks Bar, click Backup Selections.
2. Click Advanced view.
3. Click Add.
4. From the General tab in the Backup Selection dialog box, select the appropriate
options as follows:
Backup Selection General Dialog Box
Item Description
Name Type a descriptive name for the backup selection.
Description Type a clear description of the backup selection. This description
may include, for example, the folder selected, the group of users it
was created for, or the purpose for creating the backup selection.
Folder to back up
1172 Administrator’s Guide

Backup Selection General Dialog Box (continued)
Item Description
Using the Desktop Agent to Back Up Your Data
Type a folder name Select this option to add a specific folder to the backup selection.
Type the path to the folder, including the folder name. For
example, to add a folder named MyData on drive C, type
C:\MyData.
Note Once a backup selection is created, the folder cannot be
modified.
Select a pre-defined
folder
Select this option to choose a pre-defined folder from the list
provided.
Include subfolders Check this option to also back up all subfolders in the specified
directory. This option is selected by default.
5. From the Include/Exclude tab, select the appropriate options as follows:
Backup Selection Include/Exclude Dialog Box
Item Description
Include all file types Select this option to include all file types in this backup selection.
Include and exclude only
the items listed below
Select this option to include or exclude only specific files or file
types.
6. To add a filter to the Include/Exclude list, verify that you selected Include and
exclude only the items listed below in step 5, and click Add Include or Add Exclude.
7. If you selected Add Exclude, you will be notified that all previously backed up files
matching this exclude will be deleted from this backup selection. Click Yes to
continue or No to cancel.
1173

Using the Desktop Agent to Back Up Your Data
8. Select the appropriate options as follows and then click OK.
Add Include Filter or Add Exclude Filter Dialog Box Options
Item Description
Filter Type the name of the file or the folder, or a wildcard description of
the file or folder that you want to include or exclude from backup
selections.
For example, type *.mp3 to either include or exclude all files with
the file extension .mp3 in this Backup selection, or type
unimportant.txt to include or exclude all files in the backup
selection with this specific file name.
Click Extensions to select a predefined filter to either include or
exclude all files with a given file extension.
Description Type a description of this include or exclude filter.
Apply to Select one of the following:
◆ Files to apply this filter to files or
◆ Folders to apply this filter to folders.
◆ Files and Folders to apply this filter to both files and folders.
1174 Administrator’s Guide

Using the Desktop Agent to Back Up Your Data
9. From the Revision Control tab, select the appropriate options for both the Desktop
and network user data folders as follows:
Backup Selection Revision Control Dialog Box
Item Description
Number of Revisions
desktop user data folder Type the number of revisions to keep in the desktop user data
folder for each file in the backup selection.
Note When Outlook PST files are backed up incrementally, only
one revision is maintained regardless of the number of
revisions set in the backup selection.
Limit to Check this option to limit the number of revisions retained in a
given amount of time, and specify the following:
◆ Revisions. Select the number of versions to retain.
◆ Within the last x hours. Select the time period during which
you want to retain the versions.
◆ At least x minutes apart. Select the minimum amount of time
that must elapse between backups in this backup selection.
Note The oldest revision is deleted when a new revision is created
that exceeds one of these limits.
network user data folder Select the number of revisions to keep in the network user data
folder for each file in the backup selection.
Limit to Check this option to limit the number of revisions retained in a
given amount of time, and specify the following:
◆ Revisions. Select the number of versions to retain.
◆ Within the last x hours. Select the time period during which
you want to retain the versions.
◆ At least x minutes apart. Select the minimum amount of time
that must elapse between backups in this backup selection.
Note The oldest revision is deleted when a new revision is created
that exceeds one of these limits.
1175

Using the Desktop Agent to Back Up Your Data
Backup Selection Revision Control Dialog Box (continued)
Item Description
Revision Age
Discard all revisions in
the desktop user data
folder older than
Discard all revisions in
the network user data
folder older than
Enter the number of days after which all revisions in the desktop
user data folder will be deleted.
Note The latest revision will not be discarded.
Enter the number of days after which all revisions in the network
user data folder will be deleted.
Note The latest revision will not be discarded.
10. From the Options tab, select the appropriate options as follows:
Backup Selection Options
Item Description
Delta File Transfer If you choose Delta File Transfer, each time a file is backed up, only
the part of the file that has changed is transferred and stored in
the network user data folder. In addition, Delta file transfer uses
compression. Enabling this option requires that the DLO
administrator has installed and configured a maintenance server.
Compression When you select compression, each time a file is backed up, files in
this backup selection will be compressed for data transfer over the
network and for storage in the Desktop and network user data
folders.
This affects files created after this feature is activated. Previously
stored files will not be compressed.
Delta File Transfer also uses compression.
Encryption Check this option to encrypt files for transfer and to store files
from this backup selection in an encrypted format in the network
user data folder.
This affects files transmitted and stored after this feature is
activated. Previously stored files will not be encrypted.
The AES (Advanced Encryption Standard) and a 128 bit key length
are used. If enabled, versions are stored unencrypted in the
desktop user data folder, and encrypted in the network user data
folder. Transfer over the network is encrypted.
1176 Administrator’s Guide

Backup Selection Options (continued)
Item Description
When source files are deleted, delete the backed up files from the:
desktop user data folder
after
network user data folder
after
11. Click OK to save your changes.
Using the Desktop Agent to Back Up Your Data
Modifying Backup Selections in the Advanced View
From the advanced view, backup selections created on the Desktop Agent and those
created by the DLO administrator in the profile can be modified if the profile grants
sufficient rights to the Desktop Agent user.
1. Under Views in the Desktop Agent Tasks Bar, click Backup Selections.
2. Click Advanced view.
Indicate the number of days after which DLO will delete all file
versions from the desktop user data folder after the source file has
been deleted from the desktop. The default setting is 60 days.
Indicate the number of days after which DLO will delete all file
versions from the network user data folder after the source file
has been deleted from the desktop. The default setting is 60 days.
3. Select the backup selection you want to change, and then click Modify.
4. Profile backup selections are those set by the DLO administrator. If the backup
selection is a profile backup selection, and if the user has been granted sufficient
rights, it can be modified by selecting Use custom selection in the drop-down menu.
Once this option is selected, your backup selection will no longer be updated when
the administrator updates the profile backup selection.
You can return to the profile backup selection settings at any time by selecting Use
Profile selection in the drop-down menu. Once you make this selection, your profile
will be updated if the DLO administrator modifies the profile backup selection.
1177

Using the Desktop Agent to Back Up Your Data
Use Custom Selection
5. Modify the backup selection properties as needed. For detailed information on
backup selection settings, review the instructions for setting up a backup selection
beginning with step 4 on page 1172.
6. Click OK.
Deleting Backup Selections in the Advanced View
When you delete a backup selection, the backup files are deleted by the Backup Exec
grooming process after the number of days specified in the backup selection. For
additional information, see “Backup Selection Options” on page 1176.
▼ To delete a backup selection:
1. Under Views in the Desktop Agent Tasks Bar, click Backup Selections.
2. Click Advanced view.
3. Select the backup selection you want to delete.
4. Click Remove.
5. Click Yes to verify that you want to delete this backup selection, or click No to cancel.
1178 Administrator’s Guide

Backing up Outlook PST files Incrementally
Using the Desktop Agent to Back Up Your Data
DLO is configured to back up PST files incrementally by default. Incremental backup of
PST files is controlled by the administrator in the Profile, or by the desktop user in
Options dialog if the desktop user has been granted sufficient rights.
Note Outlook must be the default mail application to perform incremental backups of
Outlook PST files.
The following should be considered when backing up PST files incrementally:
■ When Outlook PST files are backed up incrementally, only one revision is maintained
regardless of the number of revisions set in the backup selection.
■ When you restore Microsoft Outlook PST files, the restored PST file will differ from
the original PST file as explained in “Restoring Microsoft Outlook Personal Folder
Files” on page 231.
■ Synchronized files cannot be backed up incrementally.
■ When a DLO profile is configured to limit the bandwidth usage during data transfer
to the network user data folder, bandwidth is not limited during the incremental
transfer of PST files.
Related Topics:
“Setting Customized Options” on page 1185
Setting Outlook as the Default Email Application
DLO is unable to perform incremental backups of Outlook PST files unless Outlook is
your default mail application.
▼ To specify Outlook as your default mail application in your internet options:
1. Open Internet Explorer.
2. On the Tools menu, click Internet Options.
3. Select the Programs tab.
4. Select Microsoft Office Outlook in the email list.
Note If you do not intend to use Outlook as your default mail application, you can
disable the warning message about incremental backups in the Desktop Agent
selecting Settings in the Views menu and deselecting enable incremental
backups of Outlook PST files in the Options tab.
1179

Using the Desktop Agent to Back Up Your Data
Pending PST Files
When an Outlook PST file is included in a DLO backup selection, it will appear in the
Desktop Agent pending queue whenever the PST file is closed. Because PSTs are a shared
resource, opening and closing of PST files is controlled by a process called MAPI. Both
DLO and Outlook access PSTs via the MAPI process. MAPI opens a PST upon request
from the application. MAPI may or may not, depending on the version in use, close a PST
in response to the following:
■ An application such as DLO or Microsoft Outlook detaches from the PST, such as
when Outlook is closed
■ DLO startup
■ After 30 minutes of inactivity in the PST
When the PST is closed DLO does one of the following. If the PST is being handled
incrementally via MAPI (see section on incremental PSTs) DLO determines if the PST has
been backed up in its entirety. If it has already been backed up then the entry is simply
removed from the Desktop Agent pending queue because DLO knows the PST is in sync.
If the PST is not being handled incrementally, the PST will be backed up in its entirety at
this time.
Related Topics:
“Restoring Microsoft Outlook Personal Folder Files” on page 1203
Backing Up Lotus Notes NSF Files Incrementally
The following types of Lotus Notes NSF Files can be backed up incrementally:
NSF Files That Can Be Backed Up Incrementally
File Name Location Description
BOOKMARK.NSF Notes\Data directory Contains saved bookmarks and Welcome Page
information.
NAMES.NSF Notes\Data directory This file contains contacts, connections,
locations and Personal Address Book
information.
A_.NSF This is an email archive file. Email must be
archived to be incrementally backed up by
DLO. See Lotus Notes documentation for
additional information on archiving email.
1180 Administrator’s Guide

Using the Desktop Agent to Back Up Your Data
When a file is backed up incrementally, there is no progress indicator in the Desktop
Agent Status view, and only one revision is retained.
Note When a DLO profile is configured to limit the bandwidth usage during data
transfer to the network user data folder, bandwidth is not limited during the
incremental transfer of Lotus Notes NSF files.
Preparing to Back Up Lotus Notes NSF Files Incrementally Using DLO
Lotus Notes must already be installed before the Desktop Agent is installed. If Lotus
Notes is installed after the Desktop Agent, you must run the Desktop Agent installer
again to repair the installation. Additionally, if Lotus Notes is open during the Desktop
Agent installation, Lotus Notes must be restarted.
Lotus Notes email files can only be backed up incrementally with DLO if the emails have
been archived. Once emails are archived, the resulting archive file can be backed up
incrementally. See the Lotus Notes documentation for information on archiving emails.
▼ To configure the Desktop Agent for incremental backup of Lotus Notes files:
1. Verify that Lotus Notes was installed before the Desktop Agent was installed, or that
the Desktop Agent installer was run again after Lotus Notes was installed to repair
the installation.
2. Verify that emails to be backed up have been archived in Lotus Notes.
3. Verify that the Lotus Notes NSF files to be backed up have been selected in the
appropriate backup selection. See “Using the Desktop Agent to Back Up Your Data”
on page 1168 for additional information on backup selections.
4. Under Tools in the Desktop Agent Tasks Bar, click Options.
5. Select the Options tab.
6. Check Enable message level incremental backups of Lotus Notes email files.
7. Click OK.
1181

Modifying Desktop Agent Settings
Using the Desktop Agent when Lotus Notes is not Configured for
the Current User
When a user logs in to a computer that has both DLO and Lotus Notes installed, but that
user is not yet configured in Lotus Notes, a debugging DOS-window may appear which
contains the following errors:
Created new log files as C:\Documents and
Settings\\Local Settings\Application Data\Lotus\Notes\Data\log.nsf.
A previous process with the process ID failed to
terminate properly.
The DOS-window cannot be closed without manually exiting the DLO process, but can be
remedied by configuring the current user for Lotus Notes. Once the user is configured,
the errors will no longer be generated at login for that user.
Deleting Lotus Notes E-mail Files
If a Lotus Notes E-mail message is deleted before it is backed up by DLO, it will not be
backed up.
Modifying Desktop Agent Settings
If the DLO administrator has set your profile so that you can view the complete Desktop
Agent and modify settings, you can use the Settings view to modify the following:
■ Backup job schedule options
■ Desktop user data folder location
■ Desktop user data folder disk space limits
■ Log file disk space limits
■ Logging level
■ Bandwidth usage
The Desktop Agent will continue to use settings specified in the profile until you
specifically elect to use customized schedules or options as described in “Changing
Backup Job Schedule Options” on page 1183 and “Setting Customized Options” on
page 1185.
1182 Administrator’s Guide

Modifying Desktop Agent Settings
You can change Desktop Agent settings and backup selections when you are working
offline. The settings will be stored until you are once again working online, at which time
they are automatically transferred. If the administrator has also made changes that
conflict with the changes made on the Desktop Agent, the changes made by the
administrator will be used.
Note Changing settings on one Desktop Agent causes settings to be loaded on other
Desktop Agents that use the same authentication. This will cancel and restart any
running jobs.
Changing Backup Job Schedule Options
You can change backup job schedule options if the DLO administrator has set your profile
so that you can view the complete Desktop Agent and modify settings.
▼ To change backup schedule options:
1. In the tasks bar, under Tools, click Settings.
2. Click the Schedule tab.
3. Select the appropriate options as follows, and then click OK:
Job Schedule Options
Item Description
Use Profile schedule Select Use Profile schedule from the drop-down menu to use the
scheduling options specified in the profile.
Note If this option is selected, additional settings on the
Schedule tab cannot be modified.
Use custom schedule Select Use custom schedule from the drop-down menu to specify
a customized schedule that differs from the profile schedule.
Run jobs:
Whenever a file changes Select Whenever a file changes to back up files automatically
whenever they change.
Note Automatic backup whenever a file changes is available only
for NTFS file systems. For FAT file systems, type a number
of minutes or hours between backups in the Back up
changes files every field.
1183

Modifying Desktop Agent Settings
Job Schedule Options (continued)
Item Description
According to a schedule Select this option to back up files according to a schedule. The
default is to run a backup at 11:00 P.M. every Monday, Tuesday,
Wednesday, Thursday, and Friday.
Click Modify... to change this default.
Manually Select Manually to run a backup only when you initiate it.
Logout/Restart/Shutdown options
Do nothing Select Do nothing from the drop-down menu to proceed with a
logout, restart or shutdown even when there are files that require
backup.
Note If a job is already running, a prompt asks if the user would
like to logout, restart or shutdown when the job is complete.
Prompt user to run job Select Prompt user to run job from the drop-down menu to have
DLO ask if a backup should be run before proceeding with the
logout, restart or shutdown.
Note If a job is already running, a prompt asks if the job should
be cancelled in order to continue with the logout, restart or
shutdown.
Run job immediately Select Run job immediately from the drop-down menu to back up
waiting files without prompting before proceeding with a logout,
restart or shutdown.
Note If a job is already running, a prompt asks if the job should
be cancelled in order to continue with the logout, restart or
shutdown.
Run job as scheduled Select Run job as scheduled from the drop-down menu to proceed
with a logout, restart or shutdown and back up files according to
the schedule.
Note If a job is already running, a prompt asks if the job should
be cancelled in order to continue with the logout, restart or
shutdown.
Run job at next login Select Run job at next login from the drop-down menu to proceed
with a logout, restart or shutdown without prompting, and run a
job the at the next login.
Note If a job is already running, a prompt asks if the job should
be cancelled in order to continue with the logout, restart or
shutdown.
1184 Administrator’s Guide

Setting Customized Options
Modifying Desktop Agent Settings
You can change additional Desktop Agent settings, such as disk space used by the
desktop user data folder, if the DLO administrator has set your profile so that you can
view the complete Desktop Agent and modify settings.
▼ To set customized options:
1. On the tasks bar, under Tools, and then click Options.
2. Click the Options tab.
3. Select Use custom options from the drop-down menu.
4. Select the appropriate options as follows, and then click OK:
Options Dialog Box
Item Description
Use Profile options Select Use Profile options from the drop-down menu to use the
scheduling options specified in the profile.
Note If this option is selected, additional settings on the Schedule
tab cannot be modified.
Use customized options Select Use customized options from the drop-down menu to specify
a customized schedule that differs from the profile schedule.
Note This option must be selected to enable access to additional
settings on the Options tab.
Limit disk space usage
on my computer to:
Log file maintenance
Select Limit disk space usage on my computer to to limit the
amount of space used on the computer to store backup files.
%
Select % to enter a percentage of the hard disk space that can be
used to store backup files.
MB
Select MB to enter the maximum number of megabytes of disk
space that can be used to store backup files.
1185

Modifying Desktop Agent Settings
Options Dialog Box (continued)
Item Description
Keep log files for a
minimum of (days)
After minimum number
of days, delete oldest log
files when combined
size exceeds
Logging options
Specify the minimum number of days to keep log files. Log files will
not be deleted until they are at least as old as specified.
Note Log grooming occurs each time a log is created. Log files will
not be deleted until the minimum age has been reached and,
when the combined size of all log files, is also reached.
Enter the maximum combined size of all log files to be retained
before the oldest log files are deleted.
Note You may have more than the specified number of MB of log
files stored if none of the log files are as old as specified in the
Keep log files for a minimum of (days) setting.
Log groom messages Select Log groom messages to create logs for grooming operations.
Log information
messages for backup
Select Log information messages for backup to create logs for all
backup operations.
Log warning messages Select Log warning messages to create logs for all operations that
generate warnings.
Enable message level
incremental backups of
Outlook PST files
Enable messsage level
incremental backups of
Lotus Notes email files
Select Enable incremental backups of Outlook PST files to enable
incremental backups of Microsoft Outlook Personal Folder (PST)
files. Incremental backups must be enabled to allow PST files to be
backed up while they are open.
If this option is not checked, PST files that are configured in
Outlook will be fully backed up each time the PST file is saved,
which generally occurs when Outlook is closed.
For additional information, see “Backing up Outlook PST files
Incrementally” on page 1179.
Check Enable incremental backups of Lotus Notes email files to
enable the configuration of DLO for incremental backup of certain
Lotus Notes NSF files. Additional steps may be necessary to insure
backup of these files. See “Backing Up Lotus Notes NSF Files
Incrementally” on page 1180 for additional information.
Unchecking this box will prevent the incremental backup of Lotus
Notes files.
1186 Administrator’s Guide

Moving the Desktop User Data Folder
Modifying Desktop Agent Settings
You can change the location of the desktop user data folder if the DLO administrator has
set your profile so that you can view and modify the complete Desktop Agent and modify
settings.
▼ To move the desktop user data folder:
1. In the tasks bar, under Tools, click Settings.
2. Click the Backup Folders tab.
3. Click Move.
Settings Dialog Box, Backup Folders tab
4. In the Browse for folder dialog box, choose a new location for the desktop user data
folder.
5. Click OK.
6. When prompted to continue, click Yes.
7. Click OK.
1187

Modifying Desktop Agent Settings
Customizing Connection Policies
The Desktop Agent can be configured to disable or limit backups for certain connection
types. For example, if the DLO administrator has granted you sufficient rights, you can
choose to disable backups when you are connected via a dialup connection, and continue
backing up when you are connected to a higher speed connection.
When backups are limited by a connection policy, files are backed up to the desktop user
data folder. Files are transferred to the network user data folder when connection
policies are no longer limiting backups. If the desktop user data folder is disabled, no
offline protection is provided.
When connection policies are created using Active Directory settings to define the
policies, and two or more policies match a specific user or computer, the most restrictive
policy is used.
Example:
One connection policy that matches a specific user or computer disables backups to the
network user data folder of all files over 500 KB. A second connection policy that also
matches the computer or user disables all backups to the network user data folder. The
second policy will be used because it is more restrictive to limit all backups than just
backups of large files.
▼ To customize connection policies:
1. Under Tools in the Desktop Agent Tasks Bar, click Settings, and then click the
Connection Policies tab.
2. Select the appropriate options as follows, and then click OK
Add/Edit Connection Policy
Item Description
Connection Type
Dialup Select Dialup from the drop-down menu to limit or disable
backups when using a dialup connection.
1188 Administrator’s Guide

Add/Edit Connection Policy
Item Description
Modifying Desktop Agent Settings
IP address range Select IP address range from the drop-down menu to limit or
disable backups for a specific IP address range.
Specify whether you want the connection policy to apply to
computers that are or are not in the IP address range you specify.
Select IPv6 or IPv4 and enter the IP address range for the
connection policy.
Note IPv6 addresses are only supported on Windows XP and later
operating systems and will not be enforced for Desktop
Agents running on Windows 2000. An additional connection
policy using IPv4 addresses may be desired for Desktop
Agents on Windows 2000 computers.
Active Directory Select Active Directory from the drop-down menu to limit or
disable backups using Active Directory. Select Configure to
configure the Active Directory settings. See step 3 on page 1190
for details on configuring connection policy settings for Active
Directory.
Desktop Agent Behavior
Disable network backup Select Disable network backup to prevent users from backing up
to the network user data folder. Backups will continue to the
desktop user data folder.
Disable network backup
for files greater than
Limit network bandwidth
usage to
Enforce policy according
to scheduled window
Select Disable network backup for files greater than to prevents
users from backing up files larger than a specified size based on
the connection type. Enter a files size in KB.
Select Disable network backup for files greater than to prevents
users from backing up files larger than a specified size based on
the connection type. Enter a files size in KB.
Check the Enforce policy according to scheduled window to cause
the connection policy to apply only during the specified period of
time.
Click Schedule to set the time during which the policy will be in
affect. Schedules can be set to run weekly or for a specific date
range.
1189

Synchronizing Desktop User Data
3. If you selected Active Directory in step 2 above, configure the Active Directory
settings as follows and click OK:
Active Directory Object Dialog
Item Description
Object Select the Active Directory Object you want to use to
configure the connection policy. You can select either
Computer or User.
In LDAP Directory Type or browse to the LDAP directory.
All objects in this directory Select this option to apply the connection policy to all
objects in this directory.
Only the objects in this directory
that match the criteria below
4. Click OK to close the Add/Edit Connection Policy dialog.
5. Click OK to close the Settings dialog.
Synchronizing Desktop User Data
Select this option to apply the connection policy only to
those objects in the directory that match the specified
criteria.
Attributes Select an attribute from the drop-down menu or type in a
custom attribute.
Condition Select the appropriate condition. Available options
include =, .
Value Type a value to complete the criteria that will be used to
determine matches. Wildcards can be used to specify the
value.
Your backed up data is stored in the desktop user data folder on the local drive of each
desktop running the Desktop Agent, and in the network user data folder. If you have
multiple desktops, your network user data folder contains copies of backed up files from
each desktop. When a folder is synchronized using the Desktop Agent, only one copy of
the folder and its contents is included in the network user data folder. When the file is
changed on one desktop, it is stored in the desktop user data folder on that computer,
1190 Administrator’s Guide

Synchronizing Desktop User Data
and then uploaded to the network user data folder the next time a DLO job is run. It is
then available for download to another synchronized desktop computer the next time
that computer runs a job.
After a folder is synchronized, the Desktop Agent checks the network user data folder
each time the desktop is connected to the network and a job is run. If new file versions
are available in any of the synchronized folders, the Desktop Agent downloads the new
version to the user data folder on the desktop. If you change a file on your current
desktop and change the same file on one of your other backed up computers without
synchronizing the files, a conflict will occur and you will be prompted to select which file
revision to use.
By synchronizing backed-up data, you can work on a file on any of your desktops with
the assurance that you are working on the most recent version.
The Synchronized Selections view displays folders backed up on your other desktops
that are available for synchronization. Select any of these folders that you want to
synchronize with the current desktop computer.
Synchronized Selections View
Note If you customize NTFS permissions or folder attributes for compression or
encryption, you must reapply these settings after restoration or synchronization.
1191

Synchronizing Desktop User Data
How Synchronization Works
When a DLO job runs, DLO does the following to back up and synchronize files:
■ Backs up files that changed on the desktop.
■ Makes synchronized files available to the other computers with which the desktop is
synchronized.
■ Downloads synchronized files that were changed on another computer and uploaded
since the last DLO job ran.
■ Retains all conflicting versions of files. You can then choose which version to use.
When you back up files, you can set various filters, such as which types of files to include,
exclude, compress or encrypt. When you synchronize files between computers, the filters
are combined. For example, if one of the synchronized files is compressed and encrypted,
all synchronized files will be compressed and encrypted automatically. If the original
backup selection backed up only .jpg files, the synchronized file set will include only .jpg
files.
If the settings for a synchronized folder are changed after the folder is synchronized, and
the folder is later unsynchronized, the folder will revert to the original backup selection
settings. For example, if the original backup selection backed up only .jpg files and the
folder is later synchronized and set to back up all files, if the folder is then
unsynchronized, it will once again backup only .jpg files.
If the number of files backed up on different computers varies, DLO synchronizes the
largest number of files. For example, if you back up three files on computer A and back
up five files on computer B, DLO synchronizes five files.
Synchronized selections are subject to limitation by global excludes in the same manner
as backup selections. See “Configuring Global Exclude Filters” on page 1065 for
additional information.
You can manage synchronization using the following options:
■ Standard view: Enables you to create new synchronization sets.
■ Advanced view: Enables you to modify settings for each synchronization set.
Note To use the synchronization feature, all synchronized computers must be running
the same version of the Desktop Agent and the clocks on all of the user’s
computers must be synchronized.
▼ To synchronize a folder across multiple desktops:
1. Under Views in the Desktop Agent Tasks Bar, click Synchronized Selections.
2. Click Standard view.
1192 Administrator’s Guide

Synchronizing Desktop User Data
Desktops available for synchronization appear in the Remote Computers pane.
Note A desktop must have the same owner and must be backed up with the Desktop
Agent to appear in the Synchronized Selections view. Only backed up folders
are available for synchronization.
3. Select the folders that you want to synchronize.
4. When the Choose Local Folder dialog box appears, type or browse to the location
where the synchronized files are to be stored.
5. Click OK.
6. Click Save changes to save the selections or Undo changes to return to the last saved
settings.
▼ To view or change a synchronized folder:
1. Under Views in the Desktop Agent Tasks Bar, click Synchronized Selections.
2. Select the Advanced view radio button.
3. Click the folder to be viewed or modified.
4. Click Modify.
The General tab in the Synchronized Folder dialog box identifies the location where
synchronized files from this selection will be stored, and also lists other computers
synchronizing with the selected folder.
5. Configure the synchronization folder settings as described for backup selection
configuration, beginning with step 5 on page 1173.
6. Click OK.
▼ To remove a synchronized folder:
Note When a synchronized selection is deleted, the backup files are deleted in the same
manner as when source files are deleted. They will be groomed away after the
number of days specified in the backup selection.
1. Under Views in the Desktop Agent Tasks Bar, click Synchronized Selections.
2. Click the Advanced View radio button.
1193

Synchronizing Desktop User Data
3. Click the synchronization selection to be deleted.
4. Click Remove.
5. When prompted, if you want to delete the backup selection, click Yes to continue or
No to cancel.
Resolving Conflicts with Synchronized Files
If a synchronized file is modified on more than one computer without updating the file
with the Desktop Agent, a conflict will occur and you will be prompted to determine
which file version to keep. For example, a conflict will occur if the same file is modified
on both your desktop computer and your laptop and your laptop is disconnected from
the network. When your laptop is subsequently connected to the network, the conflict
will be detected.
▼ To resolve a conflict with a synchronized file:
1. Under Views in the Desktop Agent Tasks Bar, click Status.
If a conflict is identified, a resolve conflicts button will appear in the Status view.
2. Click the Conflicts have been found link to open the Resolve Conflicts wizard.
3. Review the information on synchronization conflicts and click Next.
4. Select the file you wish to resolve.
5. Click the Open Folder button.
6. Manage the revisions as required.
For example, to keep an older revision, you can delete the newer revision and rename
the conflicting revision back to it's original name.
7. Click Finish.
1194 Administrator’s Guide

Viewing the Desktop Agent Status
Synchronizing Desktop User Data
The Desktop Agent Status view provides a summary of Desktop Agent operations,
including:
Desktop Agent Operations
Item Description
Status Displays the current state of Desktop Agent jobs, displays when
backups will run, and summarizes the results of the last backup.
Details This link is located just below the status summary if a backup selection
has been made for a FAT drive. It provides scheduling details based on
current Desktop Agent settings.
Show/Hide Pending Files Hides or displays pending files. This selection toggles between Hide
pending files and Show pending files when you click the link.
Usage Summary
Network Usage Displays the total amount of data stored in the network user data
folder for this computer.
Local Usage Displays the total amount of data stored in the desktop user data
folder on this computer.
Details This link is located just below the status summary and provides
detailed information on folder usage for user data. For additional
information, see “Viewing Usage Details” on page 1197.
1195

Synchronizing Desktop User Data
Desktop Agent Status View
Starting a Pending Job in the Status View
▼ To run a pending job from the Status view:
1. Under Views in the Desktop Agent Tasks Bar, click Status.
2. Under Tasks in the Desktop Agent Tasks Bar, click Run job.
All pending jobs will be run, such as backup, synchronization or restore jobs.
Suspending or Cancelling a Job
If the DLO administrator has set your profile so that you can suspend and cancel jobs,
you can do this by pressing the Suspend button. The available options depend on the
type of job being suspended. When you click Suspend, a dialog opens specifying the
options available
Note The DLO administrator sets the maximum time after which a suspended job will
resume.
1196 Administrator’s Guide

.
Options for Suspending Jobs
Type of Job Running Options
Viewing Usage Details
Synchronizing Desktop User Data
Continuous ◆ Suspend the job and resume after a specified number of
minutes.
Manual ◆ Suspend the job and resume after a specified number of
minutes.
◆ Cancel the job until it is started again manually.
Scheduled ◆ Suspend the job and resume after a specified number of
minutes.
◆ Cancel the job until it is scheduled to run again.
The Desktop Agent Status view provides a summary of information on both local and
network disk space used to store your data. Additional usage details and a grooming
function are available in the Usage Details dialog:
■ Total disk space currently used on the network and desktop computer to store your
backup data.
■ Quotas, or maximum allowed storage space which can be used to store your data on
the network and desktop computers.
■ The disk space available on the network and desktop computer for storing your data.
■ An option to immediately delete old revisions and deleted files.
■ Links to additional information and help.
Note The link to usage details is only available when the Desktop Agent is idle. It will
not be shown when a job is running.
▼ To view usage details and groom files:
1. Under Views in the Desktop Agent Tasks Bar, click Status.
2. Under Usage Summary in the Status pane, click Details to open the Usage Details
dialog.
1197

Synchronizing Desktop User Data
3. Review the usage information and take the appropriate actions as described below:
Usage Details
Item Description
Usage
Local Summarizes disk space usage on the desktop computer for storing
your data. The following information is provided:
Using - The total disk space on the desktop computer currently
being utilized to store your backup data.
Quota - The maximum amount of disk space you can use to store
your backup data on the desktop computer. The quota limit is set
by the administrator in the profile, but can be modified from the
Desktop Agent Settings view if you have been given rights to
modify settings. For additional information, see “Modifying
Desktop Agent Settings” on page 1182.
Available - The amount of free disk space available on the desktop
computer for storing your data without exceeding a quota. If there
is no quota, the Desktop Agent will reserve a small amount of disk
space so the drive will not fill completely with backup data.
Network Summarizes disk space usage on the network for storing your
data. The following information is provided:
Using - The total disk space on the network currently being
utilized to store your backup data.
Quota - The maximum amount of disk space you can use to store
your backup data on the network.
Available - The amount of free disk space available on the network
for storing backup data for the current user without exceeding a
quota.
Synchronized Files Summarizes disk space usage for storing synchronized data. The
following information is provided:
Using - The total disk space on the network currently being
utilized to store your synchronized data.
1198 Administrator’s Guide

Usage Details (continued)
Item Description
Restoring Files Using the Desktop Agent
Restoring Files Using the Desktop Agent
Remove deleted files Select this option to immediately and permanently delete all files
that are marked as deleted in your Network and desktop user data
folders. The periodic maintenance cycle will otherwise delete
these files after the amount of time specified in your assigned
profile.
Clicking this button will open the Remove Deleted Files dialog.
Choose from the following options:
◆ Remove only the deleted files that currently meet the backup
selection deleted files criteria.
Additional information
Click here to view last
job log
◆ Remove all deleted files.
Check the Remove files from the network user data folder check
box to additionally groom deleted files from the network user data
folder.
Click here to open the Log File Viewer. For additional information
on the log file viewer, see “Monitoring Job History in the Desktop
Agent” on page 1205.
If the DLO administrator has set your profile to include restoring files, then you can use
the Desktop Agent to restore files to the original or an alternate directory. If a Desktop
Agent user has more than one desktop computer running DLO, files can be selected from
all available backups on each of the user’s desktops, but can only be restored to the
current desktop computer.
For information on backing up and restoring Microsoft Outlook PST files, see “Backing
up Outlook PST files Incrementally” on page 1179 and “Restoring Microsoft Outlook
Personal Folder Files” on page 1203.
1199

Restoring Files Using the Desktop Agent
Restore View
Red ‘x’ indicates
original file deleted
If you customize NTFS permissions or directory attributes, such as compression or
encryption for files or folders, you must reapply these settings after restoration.
If you disconnect from the network while the Desktop Agent is running, you may
encounter a slow response when browsing the Restore view. From the Tasks menu, select
Refresh to fix this problem.
Note DLO can overwrite a file which is in use by staging the file to be restored when
the computer restarts. Using this feature requires administrative rights on the
Desktop Agent computer. Alternatively, the file can be restored by first closing
the application which is using the file, or by restoring the file to an alternate
location.
1200 Administrator’s Guide

▼ To restore data:
1. Under Views in the Desktop Agent Tasks Bar, click Restore.
2. In Show, select one of the following revision display options:
Restore File Version Display Options
Item Description
Restoring Files Using the Desktop Agent
All revisions All file revisions will be displayed and available as restore
selections.
Latest revision Only the latest file revision will be displayed and available as a
restore selection.
Revisions modified on
or after
3. Select the items you want to restore.
In some cases the Restore Search view may contain duplicate entries for the same
file. If this occurs, you can select either file to restore and receive the same outcome.
Note When you delete a file, the backup files are retained until they are deleted by
the file grooming process. If an original file has been deleted, but backup files
are still available, the icon for the file in the restore view will have a red ‘x’ to
indicate the deletion of the original file. See “File Grooming” on page 1170 for
additional information.
4. Click Restore.
5. Select the appropriate options as follows, and then click OK:
Restore Dialog Box Options
Item Description
Restore to the original
folders on this computer
Redirect the restore to
an alternate folder on
this computer
If selected, enter a date and time after which revisions will be
displayed and available as restore selections, then click OK.
Select this option to restore files and folders to their original
location.
Select this option to restore files and folders to an alternate folder
on the same computer.
1201

Restoring Files Using the Desktop Agent
Restore Dialog Box Options (continued)
Item Description
Preserve folder structure Select this option to restore the data with its original directory
structure. If you clear this option, all data (including the data in
subdirectories) is restored to the path you specify.
Options
If file already exists Select one of the following:
◆ Do not overwrite
◆ Prompt
◆ Overwrite
Restore deleted files Select this option if you want to restore files even though the
source file has been deleted.
Preserve security
attributes on restored
files
Searching for Desktop Files to Restore
▼ To search for desktop files and folders to restore:
Select Preserve security attributes on restored files to preserve
security information in restored files.
You may need to uncheck this box to successfully restore a file if
the source file security conflicts with the destination security.
Unchecking this option causes the security information to be
removed from the restored file.
1. Under Views in the Desktop Agent Tasks Bar, click Restore.
2. Click Search for files to restore under Tasks in the Desktop Agent Tasks Bar to open
the Search dialog box.
1202 Administrator’s Guide

3. Select the appropriate options as follows, and then click OK:
Search Dialog Box Options
Item Description
Search for file names with this
text in the file name
Restoring Microsoft Outlook Personal Folder Files
Restoring Files Using the Desktop Agent
When you restore Microsoft Outlook Personal Folder (PST) files, the following
differences will exist between the restored PST and the original PST:
■ The file size will be different.
Type all or part of the file name or folder you want to
find.
Modified Select this option to search for files that were modified
during a specific time frame. Then specify the time
frame.
Today Select this option to search for files modified on the
current calendar day.
Within the past week Select this option to search for files modified in the last
calendar week.
Between Select this option to search between calendar dates.
Of the following type Select this check box to select a file type from the list
provided.
Of the following size Select this check box and then enter information as
follows:
◆ Select from equal to, at least or at most in the first
drop-down menu
◆ Type a file size.
◆ Select KB, MB, or GB.
■ Any rule that points to a folder inside a PST file will no longer work. You must edit
the rule to point to the correct folder.
■ Restored PST files will have Inbox, Outbox, and Sent Items folders, even if the
original files did not have them.
1203

Restoring Files Using the Desktop Agent
■ If you use a password for your PST file, you must reset the password after restoring
your PST file.
Related Topics:
“Backing up Outlook PST files Incrementally” on page 1179
Restoring Deleted Email Messages
The default behavior when deleting a message from a mail archive may differ depending
on the mail application. With Lotus Notes, there is a “soft delete” feature that allows a
message to be maintained in a special folder, the “Trash,” for a measured interval
(default is 48-hours). After that, the message is permanently deleted. Outlook behaves in
much the same manner. Deleted messages are moved to the “Deleted Items” folder but
there is no time limit associated with this action. Outlook will permanently delete a
message when the user empties the Deleted Items folder.
In either case, the Desktop Agent will replicate the delete during the next backup
operation. In the event a user accidentally deletes a message from a mail archive, they
will need to recover that file from the appropriate folder assuming the file has not been
permanently deleted by the mail application. Because there are no versions maintained
for email archives, permanently deleted messages will be unavailable after the time limit
has expired or the user has manually emptied the folder.
Restoring Files with Alternate Stream Data
DLO now protects all of the alternate streams for a file, including security streams. If a
new version of a file contains only changes to alternate stream data, the file replaces the
previous version and does not impact the revision count. Only revisions with actual data
changes are treated as new revisions.
FAT partitions do not use alternate data streams. If a file is restored from an NTFS
partition to a FAT partition, the alternate steam data will not be included in the restored
file.
When a file is restored, one of the options is to preserve the security attributes on
restored files. If this option is not checked, the security attributes are removed from the
restored file. This option is set in the restore dialog box. See “Restore Dialog Box
Options” on page 1201 for additional information.
Restoring files using Backup Exec Retrieve
When DLO is configured for use with Backup Exec Retrieve, you can use a web browser to
search for DLO files and restore them to your computer. The search results include all
backed up versions of the DLO file in the network user data folder that match the search
1204 Administrator’s Guide

Monitoring Job History in the Desktop Agent
criteria. You can also search based on recent activity. A unique icon distinguishes DLO
files. For detailed information on restoring files using Backup Exec Retrieve, see the
Symantec Backup Exec Continuous Protection Server Administrator’s Guide
For information on configuring Backup Exec Retrieve, see “Using Backup Exec Retrieve
With DLO” on page 1006.
Monitoring Job History in the Desktop Agent
When a backup, restore, or synchronization operation takes place, details of that
operation are stored in log files. Log files can be viewed, searched and saved as text files.
The History View summarizes the following information and provides access to the full
logs.
You can choose to view the backup history or restore history by selecting the appropriate
tab at the bottom of the History window.
Job History View Information
Item Description
Started The date and time the operation started
Ended The date and time the operation ended
Status The status of the job, such as Active, Completed, Cancelled
or Failed.
Files Transferred (Local) The total number of files transferred to the desktop user
data folder during the listed job.
Size Transferred (Local) The total number of bytes of data transferred to the desktop
user data folder during the listed job.
Files Transferred (Network) The total number of files transferred to the network user
data folder during the listed job.
This information is only available for the backup history,
not the restore history.
Size Transferred (Network) The total number of bytes of data transferred to the
network user data folder during the listed job.
This information is only available for the backup history,
not the restore history.
Errors The number of files that failed to copy and produced errors.
1205

Monitoring Job History in the Desktop Agent
History View
Viewing Log Files
▼ To view history logs:
1. Under Views in the Desktop Agent Tasks Bar, click History.
2. To view backup logs, select the Backup tab, or to view restore logs, select the Restore
tab.
3. Select the appropriate History view filter from the Show drop-down menu as follows:
History View Filtering Options
Item Description
All logs All history logs are displayed
All logs with errors History logs for all jobs that generated errors are displayed.
1206 Administrator’s Guide

History View Filtering Options (continued)
Item Description
Monitoring Job History in the Desktop Agent
Logs filtered by date All logs generated after a specified date and time are displayed.
Enter the date and time after which logs are to be displayed in the
Filter by date dialog box and click OK.
4. Click the job history entry for which you want to view the history log.
5. Click View log to open the log file viewer.
6. If required, click Save As to save the log file as a text file.
7. Click Close to exit the log file viewer.
Searching for Log Files
The Log File Viewer has a powerful search mechanism to help you locate the log files you
want to view.
▼ To search for log files:
1. Under Views in the Desktop Agent Tasks Bar, click History.
2. Click the Search link, which is located under the History pane, to open the Log File
Viewer.
3. Enter filtering parameters as described below:
Log File Viewer Filtering Options
Item Description
Search for log entries in
All log files Select this option to show all log entries in the log file viewer.
Current log file Select this option to search only those log entries in the current
log file.
1207

Monitoring Job History in the Desktop Agent
Log File Viewer Filtering Options (continued)
Item Description
With timestamp of Check the With Timestamp of box to search only those log entries
within a specified time period. The options include:
Today - Show only log files that were created today.
Within the last week - Show all log files created in the last week.
Between dates - Show all log files created between the dates
entered.
Of the following type Check the Of the following type check box to show only logs of the
indicated type. You may select one of the following types:
◆ Backup
◆ Restore
◆ Move User
◆ Maintenance
◆ Error
◆ Warning
With Filenames
containing
Filter
Informational entries
only
Error and warning
entries only
4. Click Search.
Check the With Filename like check box and enter a filename, or
file type. Wildcard entries are supported.
Example: *gold.doc
Note When using wildcards you must use the ‘*’ wildcard. For
example, *.tmp will return all results with the .tmp
extension while .tmp will return only files explicitly named
.tmp.
Select Informational entries only to display only informational
entries.
Select Error and warning entries only to display both error and
warning entries.
Error entries only Select Error entries only to display only error entries.
Warning entries only Select Warning entries only to display only entries for warnings.
5. To view detailed information for a log file entry, expand the tree view for the entry by
clicking on the ‘+’ check box.
1208 Administrator’s Guide

6. If required, click Save As to save the log file as a text file.
7. Click Close when finished.
Log file grooming
Troubleshooting
Log grooming occurs each time a log is created. Log files are not deleted until they have
reached both the minimum age and maximum combined size of all log files settings. If
the administrator has granted you sufficient rights in your profile, you can modify these
settings in the Desktop Agent settings Options tab as described in “Setting Customized
Options” on page 1185.
Troubleshooting
This section addresses problems or questions that may be encountered while running
the DLO Administration Console or the Desktop Agent, and provides solutions for these
problems.
It is divided into the following sections:
■ “Using DLO with Other Products”
■ “Troubleshooting the DLO Administration Console”
■ “Troubleshooting the Desktop Agent”
Using DLO with Other Products
The following are known compatibility issues.
Symantec Storage Exec
SYMANTEC Storage Exec is a policy-based storage resource manager for controlling file
and application disk usage in Microsoft Windows environments. DLO and Storage Exec
are compatible, but care must be taken to avoid conflicts between DLO backup selections
and Storage Exec policies. If DLO is configured to back up a specific file type and Storage
Exec is set to prevent this file type from being copied to the server, a conflict will result.
DLO will attempt to back up the file, but the operation will fail. The DLO history log will
indicate that the file failed to copy to the network user data folder.
To prevent this conflict, DLO backup selections and Storage Exec policies must be
reviewed to identify any potential conflicts. If a conflict is found, the policies must be
manually revised to eliminate the conflict.
1209

Troubleshooting
WinCVS
When DLO runs concurrently with WinCVS, permission denied errors are sometimes
generated when checking out source. This can be avoided by excluding any directories
named cvs using global excludes or backup selection excludes.
Windows XP Service Pack 2
If you are using Windows XP with Service Pack 2 you must enable file sharing to use the
browse button in the DLO Administration Console Restore view.
PGP Desktop 8.1
When running DLO with PGP Personal Desktop 8.1, you cannot create a mounted drive
or unmount a drive which is in a DLO Backup Selection unless DLO is shut down.
Troubleshooting the DLO Administration Console
I modified an Automated User Assignment, but the change isn’t reflected for existing
Desktop Agent users.
Automated User Assignments are only used once to assign a profile and Storage Location
to a new Desktop Agent user. An Automated User Assignment can be modified to change
the profile and Storage Location settings, but these changes will only apply to new users.
Users that have already been configured will not be affected by subsequent changes in
the Automated User Assignment.
This also applies to existing users who install the Desktop Agent on another desktop.
The new installation will use the existing user settings and will store data in the user’s
existing user data folder. Automated User Assignment changes will not affect an existing
user, even if the Desktop Agent installation is on a new computer.
Settings for an existing desktop user can be changed by modifying the profile to which
the user is assigned, or by reassigning that user to a new profile or Storage Location.
Related Topics:
“Modifying Desktop Agent User Properties” on page 1077
“Managing Desktop Agent Users” on page 1074
“About Automated User Assignments” on page 1060
“About DLO Profiles” on page 1020
“Moving Desktop Agent Users to a new Network User Data Folder” on page 1079
1210 Administrator’s Guide

Troubleshooting
A desktop user ran the Desktop Agent and received an error indicating “Unable to configure
the Desktop Agent. No settings found for the current user and no automatic user
assignments match.” What does this mean?
This message means that DLO could not find the user or an Automated User Assignment
that matched the user's domain and group.
Users are added to DLO in one of two ways:
1. An Automated User Assignment that matches the user’s domain and group assigns a
profile and Storage Location to the Desktop Agent and adds the user to DLO. Check
that you have created Automated User Assignments that match the Domain and
Group to which the user running the Desktop Agent belongs.
You can also create an Automated User Assignment that will cover all domains and
all groups to catch any users who might not match a more specific Automated User
Assignment. Such a “catchall” Automated User Assignment would typically be set to
the lowest priority.
2. Users are manually added to DLO. This process requires that you assign a profile and
either a Storage Location or user data folder to the new user.
Be sure that the user has a matching Automated User Assignment, or is added manually
before running the Desktop Agent.
Related Topics:
“About Automated User Assignments” on page 1060
When do I need a network user data folder, and when do I need a Storage Location?
Every Desktop Agent user must have a network user data folder, which is used to store
backup data. Storage Locations are locations on the network where network user data
folders are automatically created and maintained. They are not required if existing
network shares are used to store user data.
If you want DLO to automatically create network user data folders, use a Storage
Location. When new users are added to a Storage Location, network user data folders are
automatically created for them within the Storage Location.
Alternately, if you would like to use existing network shares as network user data folders,
or if you want to create network user data folders manually, then do not use Storage
Locations.
Related Topics:
“Configuring DLO” on page 1019
1211

Troubleshooting
I'm trying to create a Storage Location on a remote file server, and I am receiving an error
indicating the MSDE Database Instance for the Desktop and Laptop Option needs to have
access to the remote file server. What do I need to do?
To create Storage Locations on a remote file server, you must use an account that has
administrative rights on the remote file server. To change the account credentials used to
create the Storage Location, see “Changing DLO Service Credentials” on page 995.
I manually added a new user and assigned the user to an existing Storage Location. I don't
see a new user data folder for the new user in this Storage Location. Isn't it supposed to
create one?
user data folders are created only after the Desktop Agent is both installed on the
desktop and run by the new user.
How do I prevent a user from backing up data?
1. On the navigation bar, click Setup. In the Settings pane, click Users.
2. Select the user you do not want to be able to perform backups.
3. Under General Tasks in the Task pane, select Properties.
4. Clear the Enable user check box.
5. Select OK.
The user's status will display as Disabled.
In a backup selection, I selected to encrypt or compress my user's data. However, data that
has already been backed up is not encrypted or compressed. Why is this?
DLO does not retroactively apply changes to encryption and compression settings to user
data that is already backed up. Any data backed up after these settings have changed will
use the new settings.
I would like to prevent files of specific types from being backed up. How can I set up DLO to
always exclude files like *.mp3 or *.gho?
On the Tools menu, select Global Excludes. In this dialog box, you can add specific file
types that will be excluded in all backup selections for all profiles.
Backups do not seem to be running for all users, or specific files are not being backed up.
If backup jobs are not running for a group of users, check the profile for these users to
verify that backups are scheduled.
If specific files are not being backed up, review the backup selections in the profile to
verify that the files are selected for backup.
1212 Administrator’s Guide

Troubleshooting
I just tried to restore a file, but it doesn’t appear to have been restored.
When restoring existing files to their original location, verify that you have selected
Prompt or Overwrite in the Restore dialog box to replace the file. If you select Do not
overwrite, the file will not be restored.
In a profile, I configured backup selections to encrypt files. Now I need to recover files for a
user. Do I need an encryption key to restore this data?
As an Administrator running the DLO Administration Console, you can redirect a restore
of encrypted user data to an alternate computer or location, and it will be decrypted
during the restore.
I would like to restore data to a user's computer, but that user is out of the office. Do I have
to wait until that user returns to the office before I can start the restore?
DLO can queue restore jobs to desktops. If the user is offline now, you can queue a restore
job through the Restore view in the DLO Administration console.
Another option is to restore the data to an alternate location, such as the administration
computer or a network drive.
How can I protect open files?
DLO does not protect open files. It will attempt to back up files when they are closed or
saved. If a file cannot be backed up because it is open (for example, a Word document you
are editing) it will remain in the Desktop Agent's pending list. The Desktop Agent will
attempt to back up the file at the next backup time. This also means that certain files
opened by the operating system will not be backed up, they never close when the
operating system is running.
The exception to this is protection of open PST files. The Desktop Agent is designed to
protect open PST files if they are part of the profile or user's backup selections.
Incremental backups must be enabled for open file backups of PST files.
Related Topics:
“Excluding Files that are Always Open” on page 1072
The History view in the DLO Administration Console doesn’t show the most recent backup
for all users.
The DLO Administration Console is automatically updated when a job runs, but not more
than once per hour.
1213

Troubleshooting
Troubleshooting the Desktop Agent
This section addresses potential problems or questions that may be encountered while
running the Desktop Agent, and provides solutions for these problems.
Do I have to install Backup Exec on every desktop I want to protect?
No. You must install the Desktop Agent on every desktop you want to protect. It is not
necessary to install Backup Exec.
I installed the Desktop and Laptop option, but I do not know how to install the Desktop
Agent on users’ computers.
The Desktop Agent can be installed by running the installation program from the share
where DLO is installed as described below, or it can be push installed using the Backup Exec
installer (see “Installing Backup Exec options to remote computers” on page 92).
The Desktop Agent installation program is located in a share where you installed DLO.
This share will have a name in the following format: \\\DLOAgent.
Using Windows Explorer, browse to this share from the desktop that you want to protect
with the Desktop Agent. Run Setup.exe from this share. You must be an administrator
on the desktop to install the Desktop Agent software.
Symantec recommends that DLO administrators run the Configuration Wizard to
familiarize themselves with the application.
Can I install the Desktop Agent on Windows Servers or media servers?
Because the Desktop Agent is designed to protect user data rather than critical server
data, it cannot be installed on Windows Servers or media servers.
I am receiving the following error while authenticating through the Desktop Agent to the
media server: “Failed to Initialize database. 0x800A0E7D”
You attempted to connect to the media server with an account that is not in the same
domain, or a trusted domain, as the media server. For DLO to function properly, the media
server must be in a Windows Domain.
I have a desktop and a laptop computer protected by the Desktop Agent. Why can't I move
my laptop to a new Storage Location?
When a user has multiple computers running the Desktop Agent, all backup data is
stored in the same network user data folder. If you want to move your data to a new
Storage Location, you must move the entire network user data folder for all of your
computers to that new location.
1214 Administrator’s Guide

Troubleshooting
I am trying to synchronize files between my desktop and laptop computers, but I cannot see
my other computer in the Synchronization View in the Desktop Agent.
To synchronize data between two computers, the same user account must be used when
running the Desktop Agent on each computer. For example, the user Domain\MyUser
must have backed up data on Computer A and Computer B in order for synchronization
to take place between these two computers.
If you are sure you have backed up data while running the Desktop Agent under the same
user account on both of your computers, select Refresh in the Desktop Agent's
Synchronization View to make the synchronization selections available. If this is not
successful, Exit from the File menu and restart the Desktop Agent application.
What files or folders can I synchronize between my computers?
Any data backed up by a backup selection are eligible for synchronization. These backup
selections may be defined by the DLO Administrator in the profile or in a backup
selection created with the Desktop Agent.
I would like to share my synchronized data with my co-workers. How can I do this?
The Desktop and Laptop Option does not provide functionality for sharing files between
users. Synchronization is designed to share files between a single user's computers.
1215

Glossary of Terms
Glossary of Terms
Administrator
The user that configures DLO using the Backup Exec DLO Administration Console. This
user must have administrative rights to operate the console.
Authentication
The process of validating a user’s credentials.
Automated User Assignments
Rules that assign profiles and Storage Locations to a specified group of desktop users.
Settings are applied the first time a user runs the Desktop Agent.
Backup Exec Administration Console
The administrator’s interface with Backup Exec.
Compression
A method of reducing data to expedite transmission time or storage volume.
DLO Administration Console
The administrator’s interface with the Desktop and Laptop Option.
DLO backup selection
The files and folders on a desktop or laptop that are selected for backup by the DLO
Administrator or desktop user.
DLO database
The location where policy settings and status information are stored.
DLO file server
The computer that hosts DLO Storage Locations. This computer can be the Backup Exec
media server or another server.
Delta File Transfer
Delta File Transfer is a compression process that allows only the changed portion of a file
to be transferred once the complete original file is backed up. Delta File Transfer reduces
bandwidth use and disk storage requirements.
1216 Administrator’s Guide

Glossary of Terms
Desktop Agent install share
The network share where the Desktop Agent install files are located. This folder is set up
on the Backup Exec media server when DLO is installed, and facilitates the installation of
the Desktop Agent on desktops.
Desktop Agent
The DLO software that runs on desktop and laptop computers.
Desktop Agent console
The user interface for the Desktop Agent software.
Encryption
A process used to ensure data security of files and folders on disk and during data
transfer.
Open file handling
The process by which files currently in use can be backed up.
Optimization
The process of reducing network traffic and file storage through technologies such as
compression.
Profile
Revision
DLO settings configured by the administrator and that apply to users or groups of users.
A version of a file at a specific point in time.
Storage Location
A shared location on the network in which network user data folders and backup files are
stored.
Synchronization
The process that maintains the most recent version of selected files and folders belonging
to the same user on multiple desktops. Synchronization is available for files and folders
that are backed up by DLO.
1217

Glossary of Terms
Task
User
An accessible program function that varies with the view selected in the DLO
administration console or Desktop Agent console.
The person who operates the desktop or laptop computer on which the Desktop Agent is
run.
User data folder
The folder in which user backup data is stored. There is a user data folder on each desktop
that is protected by the Desktop Agent, and one user data folder on the network for each
Desktop Agent user.
User name
The user name used for Windows authentication.
View
The main navigational interface in the DLO Administration Console.
1218 Administrator’s Guide

Appendix
Symantec Backup Exec Agent
for Microsoft Exchange
Server
The Symantec Backup Exec for Windows Servers Agent for Microsoft Exchange Server
(Exchange Agent) enables network administrators to perform backup and restore
operations on Microsoft Exchange Servers that are connected to a network.
About the Backup Exec Exchange Agent
J
The Exchange Agent lets you integrate backups of Microsoft Exchange Server databases
with network backups without separate administration or dedicated hardware.
The Exchange Agent for Exchange 2000, 2003, and 2007 installations provides the
following features:
■ Increased performance of mailbox backup and restore through a granular restore
feature for mail messages and folders that are backed up with the Information Store.
This option lets you restore individual mail messages and folders from full, copy, and
incremental backups of the Information Store.
■ Continuous backup of the Exchange Server when Backup Exec Continuous Protection
Server (CPS) is installed. The CPS backup job provides complete recovery to any
point in time of the Information Store, including the latest complete transaction log.
When you also enable recovery points to run at intervals between the full backups,
you can restore individual messages or folders at a point in time when the recovery
point was created. Even without recovery points, you can restore individual
messages or folders from a full backup.
■ The ability to select storage groups for backup and restore jobs, or to select one or
more databases within the storage group for backup and restore jobs.
1219

Requirements for using the Exchange Agent
■ The ability to recover individual databases or storage groups by using the Recovery
Storage Group feature of Exchange Server 2003 for non-snapshot backups. On
Exchange 2007, you can restore snapshot backups to a recovery storage group.
■ Snapshot backup and offhost backup on Exchange Server 2003 or Exchange Server
2007 instances that run on Windows Server 2003.
Related Topics:
“Installing the Exchange Agent” on page 1223
“Backup strategies for Exchange” on page 1225
“Recommended configurations for Exchange” on page 1223
“Symantec Backup Exec Advanced Disk-based Backup Option” on page 865
“About the Advanced Open File Option” on page 843
Requirements for using the Exchange Agent
The media server must meet the following requirements:
Media server requirements for the Backup Exec Exchange Agent
Media server requirements Description
Exchange Server 2007 only To back up Microsoft Exchange Server 2007, you must
install the Exchange Management Tools for Microsoft
Exchange Server 2007 on the media server. The
management tools can be installed during a custom
install of Microsoft Exchange Server 2007.
Exchange Agent Symantec Backup Exec for Windows Servers Microsoft
Exchange Server Agent (Exchange Agent) must be
licensed and installed.
Access The media server must have access to the Exchange
Server.
Backup Exec services account You must use a Backup Exec services account that has
domain and local administrator rights on every Exchange
server that you want to back up or restore.
To support the Backup Exec Resource
Discovery feature, which allows
detection of new backup resources
within a Windows domain
Microsoft Exchange System Manager utility must be
installed.
1220 Administrator’s Guide

Media server requirements for the Backup Exec Exchange Agent
Media server requirements Description
To back up Exchange data from any
node of a Veritas Cluster Server
To support the restore of individual
mail messages and folders from
Information Store backups
To support Backup Exec Continuous
Protection Server
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Requirements for using the Exchange Agent
Microsoft Exchange System Manager utility must be
installed on all nodes.
A version of a Microsoft Windows operating system that
supports minifilter drivers must be installed:
◆ Microsoft Windows 2000 Server (with Service Pack 4
and Update Rollup 1 for Service Pack 4)
◆ Microsoft Windows Server 2003 (with at least Service
Pack 1)
◆ Microsoft Windows Server 2003 R2 Editions
The following Windows operating systems are supported:
◆ Microsoft Windows 2000 Server (with at least Service
Pack 4 and Update Rollup 1 for Service Pack 4)
◆ Microsoft Windows Server 2003 (with at least Service
Pack 1)
◆ Microsoft Windows Server 2003 R2 Editions
◆ Microsoft Windows XP Professional (with at least
Service Pack 2)
The following must be installed:
◆ The Backup Exec CPS Continuous Protection Agent
◆ The Backup Exec CPS Exchange Protection Agent
Both CPS agents must use the Backup Exec service
account. The service account must have domain and local
administrator rights.
To view the CPS console from the media server, the CPS
Administration Console must be installed on the media
server.
Additionally, the CPS Protection Server (the media server)
and the CPS Business Server (the Exchange Server) must
be in the same domain unless the domains are trusted.
For information on installing the Continuous Protection
Server components, see the Symantec Backup Exec
Continuous Protection Server Administrator’s Guide.
1221

Requirements for using the Exchange Agent
The following are requirements for the Exchange Server with the Backup Exec Exchange
Agent:
Exchange Server requirements
Exchange Server requirements Description
Exchange Server 2007 only To support individual mailbox message and folder
restores from Information Store backups, you must
download and install the Microsoft Exchange Server
MAPI Client and Collaboration Data Objects package on
the Exchange 2007 server. This package can be found on
the Microsoft Web site.
For operations on all Exchange
resources
You must use the Microsoft System Manager utility to
grant the Exchange Administrator role to the user
account at the Administrative Group level (for all
Administrative Groups if there is more than one).
To support snapshot backups You must use Microsoft Exchange Server 2003 or
Exchange 2007 running on Windows Server 2003 or later.
Note To select incremental or differential backup
methods, Exchange Server 2003 Service Pack 1 or
later must be installed.
To support Backup Exec Continuous
Protection Server
The following must be installed:
◆ The Backup Exec CPS Continuous Protection Agent
◆ The Backup Exec CPS Exchange Protection Agent
Both CPS agents must use the Backup Exec service
account. The service account must have domain and local
administrator rights. The service account must also be
able to query the location of the transaction logs on the
local active Exchange server.
For information on installing the Continuous Protection
Server components, see the Symantec Backup Exec
Continuous Protection Server Administrator’s Guide.
Related Topics:
“Using resource discovery to search for new resources” on page 339
“About selecting individual mailboxes for backup” on page 1252
“Continuous protection for Exchange data” on page 1235
1222 Administrator’s Guide

Installing the Exchange Agent
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Installing the Exchange Agent
The Exchange Agent is installed locally as a separate, add-on component of Backup Exec
for Windows Servers to protect local or remote Exchange Server databases.
For information on installing the Exchange Agent, see “Installing Backup Exec options to
the local computer” on page 85.
Recommended configurations for Exchange
Before starting backups for Exchange, read the following recommendations for
configuring Exchange to make it easier to restore from backups:
Recommendations for configuring Exchange for better restore
Recommendation Description
Put transaction log files on a separate
physical disk from the database.
Make Write Cache unavailable on the
SCSI controller.
Make circular logging unavailable if
possible.
This is the single most important configuration affecting
the performance of Exchange. This configuration also has
recovery implications, since transaction logs provide an
additional recovery resource.
The Windows operating system does not use buffers, so
when Exchange receives a write complete notice from
Windows, the write-to-disk has been completed. If Write
Cache is enabled, Windows responds as though a
write-to-disk has been completed, and will provide this
information to Exchange (or other applications)
incorrectly. The result could be data corruption if there is
a system crash before the operation is actually written to
disk.
Circular logging minimizes the risk that the hard disk will
be filled with transaction log files. But, if a solid backup
strategy is in place, transaction log files are purged during
the backup, thus freeing disk space. If circular logging is
enabled, transaction log histories are overwritten,
incremental and differential backups of storage groups
and databases are disabled, and recovery is only possible
up to the point of the last full or copy backup.
Note Continuous backup of Information Store
transaction logs with the Backup Exec Continuous
Protection Server is not supported if circular
logging is enabled.
1223

Exchange mailbox access requirements
Recommendations for configuring Exchange for better restore
Recommendation Description
Avoid making the Exchange Server a
domain controller.
Install Exchange into a domain that
has at least two domain controllers.
Related Topics:
“Reviewing the circular logging setting for Exchange” on page 1229
“Setting defaults for the Advanced Open File Option for backup jobs” on page 850.
“Setting offhost backup options for backup jobs” on page 892
“Exchange mailbox access requirements” on page 1224
Exchange mailbox access requirements
For disaster recovery purposes, it is much easier to restore
Exchange if you don’t have to restore the Active Directory
first.
Active Directory replication is not possible with only one
domain controller in a domain. If the domain controller
fails and corrupts the Active Directory, some transactions
may not be recoverable if they were not included with the
last backup. With at least two domain controllers in a
domain, databases on the failed domain controller can be
updated using replication to fill in missing transactions
after the database backups have been restored.
Backup Exec must have access to a uniquely named mailbox within the Exchange
organization for Information Store operations, depending on how the backup and restore
jobs are configured.
Access to a uniquely named mailbox is required when:
■ You back up individual mailboxes separately from the Information Store (also called
the legacy mailbox backup method). Note that this is not supported on Exchange
2007.
■ You configure a backup job to be processed on a device that is not a backup-to-disk
folder, and for which you enable the option to restore individual mail messages and
folders, and you select any backup method other than a snapshot backup.
■ You restore mailboxes and public folders.
You must use a Backup Exec logon account to connect to the Exchange server when you
select mailboxes or public folders for backup. Backup Exec attempts to find a mailbox
with the same name as the user name that is stored in the Backup Exec logon account.
1224 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Backup strategies for Exchange
If you use a Backup Exec logon account that stores a unique user name and has a
corresponding mailbox with the same name, then you are not prompted for an additional
logon account. Otherwise, you must choose or create a Backup Exec logon account that
stores the name of a unique mailbox within the Exchange organization.
A unique name does not share the first five characters in another mailbox name. For
example, if EXCH1 is entered as the mailbox name, and there is another mailbox name
such as EXCH1BACKUP, then Backup Exec cannot accept the name. You are prompted to
choose another mailbox name.
You can choose or create a logon account that meets any of the following requirements:
■ A logon account for which the user name matches a unique mailbox name.
■ A logon account that uses a unique alias to a mailbox. The user account that
connects to the Exchange Server must also have access to this mailbox.
■ A logon account that uses the full computer name for a mailbox. The user account
that connects to the Exchange server must also have access to this mailbox. An
example of a full computer name is:
/O=Exchange_Organization/OU=Administrative_Group/CN=Recipients/
CN=mailbox_name
Related Topics:
“About restoring individual mailboxes and folders from the Information Store” on
page 1230
“Creating a Backup Exec logon account” on page 149
Backup strategies for Exchange
Backup Exec incorporates online, nondisruptive Exchange database protection as part of
everyday backup routines, which increases the chance of data recovery and minimizes
data loss without inhibiting daily activity. Backup Exec protects Exchange data,
including the individual storage group, database, mailbox, and public folder with full,
copy, incremental, and differential backups.
To decide which backup methods to use, consider the following:
■ In small office environments with relatively small numbers of messages passing
through the system, a daily full backup will provide good data protection and the
quickest recovery. If log file growth becomes an issue, consider using incremental
online backups at midday to provide an added recovery point and manage the log file
growth for you automatically.
1225

Backup strategies for Exchange
■ In large environments, incremental backups should be used to provide more frequent
recovery point options throughout the day and to manage log file growth. Many
shops run full backups on a weekly basis, preferring to run incremental backups
throughout the week to keep backup run time to a minimum. The trade-off with this
technique occurs at recovery time when you must recover from the full backup and
from each incremental backup as well.
What works best for you is based on the size of your environment, the number of
transactions processed each day, and the expectations of your users when a recovery is
required.
Consider the following backup strategies:
■ Run Backup Exec Continuous Protection Server (CPS) jobs weekly or daily. The full
backups and the replicated transaction logs provide complete recovery to any point
in time of the Information Store, including the latest complete transaction log. You
can also restore individual messages or folders from the CPS backup.
When you enable recovery points to run at intervals between the full backups, you
can restore individual messages or folders at a point in time when the recovery point
was created. Another advantage of recovery points is that log growth is controlled
because the transaction logs are truncated after each recovery point runs.
■ Run full backups with the option to enable the restore of individual items selected so
that you can restore individual mail messages and folders without restoring the
entire database. Depending on your environment, run full backups:
■ As frequently as possible, no less than once a day.
■ Daily with differential backups used at regular periods throughout the day.
■ Every few days (no less than weekly) with frequent incremental backups in
between each full backup.
■ Run Exchange backup jobs separately from other backup jobs.
1226 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Backup strategies for Exchange
In addition to backing up Exchange storage groups, you should also back up the following
on a regular basis:
Backup selections for Exchange configuration data
Recommended backup
selections for
configuration data
Description
File system Back up folders and drives containing files for Windows and Exchange.
Usually, this is the root drive C:\ but may be different in each
environment.
Note Back up the C:\ drive, but do not back up the virtual drive that is
created by Exchange, if this virtual drive exists in your
environment. It is intended only to provide Explorer access to
the Exchange data, but all file system functions may not be
replicated. Backup and restore operations are not recommended
or supported.
Windows registry Back up the registry by running a full backup.
System State and/or
Shadow Copy
Components
Key Management Service
(KMS) database
Site Replication Services
(SRS) database
Select System State and run a full backup to back up the following:
◆ The Internet Information Service (IIS) metabase
◆ The Windows registry
For more information on backing up System State and Shadow Copy
Components, see “Selecting data to back up” on page 315.
If the entire server must be restored, you must restore System State
before restoring Exchange 2000. You must also restore both System
State and Shadow Copy Components before restoring Exchange Server
2003 or Exchange Server 2007.
Back up the Key Management Service database by selecting the KMS
icon in Backup Selections, and then running a full backup. Local or
remote backups can be performed on the KMS database.
Note KMS is not available in either Exchange Server 2003 or
Exchange Server 2007.
If Exchange 2000 or 2003 is running in an Exchange Server 5.5
environment, back up the Site Replication Services (SRS) database by
selecting the SRS icon in Backup Selections, and then running a full
backup. This data is used for interoperability with Exchange Server
5.5.
1227

Backup strategies for Exchange
Backup selections for Exchange configuration data (continued)
Recommended backup
selections for
configuration data
Description
Active Directory To back up Active Directory, select System State on the domain
controllers and run a full backup.
When there are configuration changes on the Exchange server
database, such as when objects are added, modified, or deleted, back
up the Active Directory on the domain controllers.
Note Spread multiple domain controllers throughout each domain for
efficient Active Directory replication, and so that if one domain
controller fails, redundancy is still provided.
Note Exchange mail messages and folders that are in the Information Store backup can
be restored individually without having to restore the entire database. Selecting
individual Exchange mailboxes for backup separately from the Information Store
uses legacy backup methods, and is no longer required for individual mailbox
recovery. See “About restoring individual mailboxes and folders from the
Information Store” on page 1230.
Related Topics:
“About restoring individual mailboxes and folders from the Information Store” on
page 1230
“Backing up Exchange” on page 1245
“Preparing for disaster recovery of Exchange Server” on page 1280
Automatic exclusion of Exchange data during volume-level
backups
If you select a volume that contains Exchange data for backup, the Exchange Agent uses
Active File Exclusion to automatically exclude Exchange data that should not be included
in a volume-level backup. For example, .EDB and .STM files, as well as transaction log
files, should not be part of a volume-level backup because they are opened for exclusive
use by Exchange.
Without this exclusion, during a non-snapshot backup, these files appear as in use -
skipped. During a snapshot backup, these files may be backed up in an inconsistent state,
which could create restore issues.
1228 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Backup strategies for Exchange
While it is not recommended, if you want to include Exchange data in a volume-level
backup, you must first dismount the storage groups that you want backed up, and then
run the backup job.
Reviewing the circular logging setting for Exchange
When circular logging is enabled, you cannot run incremental and differential backups
of Exchange databases and storage groups, or run backup jobs for which continuous
protection is enabled. These types of backups rely on a complete history of logs.
When circular logging is enabled, transaction log files that have already been committed
to the database are overwritten, preventing the accumulation of logs. The log files are
overwritten whether or not a full or incremental backup has been run, and a history of
previous logs since the last full or incremental backup is not maintained.
When circular logging is disabled, transaction log files accumulate on the disk until:
■ A full or incremental backup is performed
■ A recovery point is run as part of a continuous backup of Exchange.
After these operations, the log files that have all transactions committed to the database
are deleted.
Related Topics:
“Backup strategies for Exchange” on page 1225
1229

About restoring individual mailboxes and folders from the Information Store
About restoring individual mailboxes and folders from the
Information Store
Exchange mailboxes and folders are always backed up with the Information Store.
However, you do not have to back up Exchange mailboxes separately from the
Information Store in order to restore an individual mailbox. If you select the option to
enable the restore of individual items, you can restore individual mail messages and
folders from the Information Store without having to restore the entire database. When
you select the option to enable the restore of individual items, then Backup Exec collects
additional information for the catalog. This information enables you to restore single
mail messages or folders from Information Store backups.
The options for selecting individual mailboxes for backup are only enabled by default if
you are upgrading from a previous Backup Exec version and you have existing jobs for
mailbox backups. See “About selecting individual mailboxes for backup” on page 1252.
Following are requirements for backup and restore operations when an Information
Store backup is enabled for the restore of individual items:
Requirements for Information Store backups that are enabled for the restore of individual items
Task Requirements
If the destination device for the backup job is a
backup-to-disk folder
If the destination device for the backup job is to
a device other than a backup-to-disk folder
The backup-to-disk folder must be configured
as follows:
◆ It must reside on a local NTFS volume.
◆ It cannot be a removable backup-to-disk
folder.
◆ It cannot contain junction points.
◆ The option Allocate the maximum size for
backup-to-disk files cannot be set. See
“Setting defaults for new backup-to-disk
folders” on page 226.
◆ If the backup-to-disk folder is in a device
pool that contains other types of devices, set
the priority of the backup-to-disk folder to 1
so that it processes the job. See “Creating a
backup-to-disk folder” on page 222.
Backup Exec must have access to a uniquely
named mailbox within the Exchange
organization for backup and restore of the
Information Store.
See “Exchange mailbox access requirements”
on page 1224.
1230 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Snapshot and offhost backups with the Exchange Agent
Requirements for Information Store backups that are enabled for the restore of individual items
Task Requirements
If you create full backups and incremental
backups
If you restore individual items from an
Information Store backup set that is on a device
other than a backup-to-disk folder
Snapshot and offhost backups with the Exchange Agent
The Exchange Agent supports the Microsoft Volume Shadow Copy Service (VSS), a
snapshot provider service only available on Windows Server 2003 or later. Using VSS, a
point in time view of the Exchange database is snapped and then backed up, leaving the
actual Exchange database open and available for users. Offhost backup enables the
backup operation to be processed on a Backup Exec media server instead of on the
Exchange server. Moving the backup from the Exchange server to a media server enables
better backup performance and frees the remote computer as well.
The Exchange Agent snapshot does not support:
■ NAS configurations
■ The Exchange 2003 Recovery Storage Group feature
■ Exchange 2000 on Windows Server 2003. To avoid errors, Symantec recommends
that you create a separate, non-snapshot backup job for the Exchange 2000 Server or
Exchange Server 2003 on Windows 2000.
■ Backup of the Site Replication Services (SRS)
■ Mixing snapshot backups and non-snapshot backups
◆ The full and the incremental job templates
must be in a policy, and must have a
backup-to-disk folder as the destination
device.
If you run only a full backup of the
Information Store, the full job template does
not have to be in a policy.
See “Creating a new policy” on page 416.
Backup Exec must temporarily stage the entire
database to a path on an NTFS volume on the
media server to extract individual items. You
must specify this path.
See “About restoring individual Exchange mail
messages and folders from Information Store
backups” on page 1264.
1231

Snapshot and offhost backups with the Exchange Agent
Due to a Microsoft Exchange limitation, if non-snapshot backups are run as part of a
data protection scheme, then snapshot backups should not be run. If snapshot
backups are run, non-snapshot backups should not be done.
■ Backup jobs for which the option Continuously back up transaction logs with Backup
Exec Continuous Protection Server is enabled.
Some features for snapshot and offhost backup are available for use with the Exchange
Agent when using VSS. License keys are not required to use the features listed in the
following table:
Available Backup Exec options when using a snapshot method with the Exchange Agent
Backup Exec option Available feature
Backup Exec Advanced Open File Option
(AOFO)
Backup Exec Advanced Disk-based Option
(ADBO)
◆ Microsoft Volume Shadow Copy Service
◆ Process logical volumes for backup one at
a time
Note The Advanced Open File Option settings
apply to all backup selections in the job,
including file system and database
selections.
Process logical volumes for offhost backup
one at a time
The type of backup method that is available when using VSS with the Exchange Agent
depends on the version of Exchange Server, and are listed in the following table:
Available backup methods for Exchange snapshot versions
Exchange version Available backup methods
Exchange 2003 ◆ Full
◆ Copy
Exchange 2003 with Service Pack 1 or later ◆ Full
◆ Copy
◆ Differential
◆ Incremental storage group level snapshot
backup
◆ Individual database restore
Exchange 2007 ◆ LCR/CCR - Back up from the passive copy or
the active copy.
1232 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Snapshot and offhost backups with the Exchange Agent
Troubleshooting Exchange Agent snapshot and offhost jobs
An Exchange Agent snapshot job fails on the following conditions:
■ The Exchange Agent snapshot fails.
■ You run a migrated or new snapshot backup for data on Exchange 2000 Server or
Exchange Server 2003 on Windows 2000. Snapshot backups of Exchange are only
supported for Exchange Server 2003 on Windows Server 2003. The job does not fall
back to a non-snapshot backup because Exchange snapshot and non-snapshot
backups are not interoperable.
The snapshot backup continues for resources that are supported, and the job can
successfully complete with exceptions. To allow the snapshot to continue for the
supported resources, do one of the following:
■ Check Process logical volumes for backup one at a time on the Backup Job
Properties for the Advanced Open File Option.
■ Check Process logical volumes for offhost backup one at a time on the Backup
Job Properties for the Advanced Disk-based Backup Option.
■ If incremental or differential backup methods are selected, and Exchange Server
2003 Service Pack 1 or later is not installed.
■ If the option Continuously back up transaction logs with Backup Exec Continuous
Protection Server is selected on the backup job properties.
■ If circular logging is enabled, and incremental or differential backup methods are
selected.
Configuring a snapshot backup with the Exchange Agent
Symantec recommends that you perform consistency checks before running a snapshot
backup. For more information, see “Perform consistency check before backup when
using Microsoft Volume Shadow Copy Service (VSS) snapshot provider” on page 1250.
To configure a snapshot backup with the Exchange Agent
1. Follow the instructions in “Backing up Exchange” on page 1245.
2. Follow the instructions in “Setting defaults for the Advanced Open File Option for
backup jobs” on page 850.
3. Ensure that either the Microsoft Volume Shadow Copy Service option or the
Automatically select open file technology option is selected.
1233

Snapshot and offhost backups with the Exchange Agent
4. If resources that are not supported for snapshot backup are included in the backup
selection list, check Process logical volumes for backup one at a time to allow the
job to complete with errors.
5. Schedule or start the backup job.
Related Topics:
“Backing up data” on page 345
“Snapshot and offhost backups with the Exchange Agent” on page 1231
“Troubleshooting Exchange Agent snapshot and offhost jobs” on page 1233
“About restoring Exchange data from snapshot backups” on page 1262
Configuring an offhost backup with the Exchange Agent
Symantec recommends that you perform consistency checks before running an offhost
backup. For more information, see “Perform consistency check before backup when
using Microsoft Volume Shadow Copy Service (VSS) snapshot provider” on page 1250.
To configure an offhost backup with the Exchange Agent
1. Follow the instructions in “Backing up Exchange” on page 1245.
2. Follow the instructions in “Setting offhost backup options for backup jobs” on
page 892.
3. Ensure that the snapshot provider that you select is Automatic - Use hardware if
available; otherwise use software.
The options for job disposition are not available.
4. If resources that are not supported for offhost backup are included in the backup
selection list, check Process logical volumes for offhost backup one at a time to
allow the job to complete with errors.
5. Schedule or start the backup job.
Related Topics:
“Backing up data” on page 345
“Snapshot and offhost backups with the Exchange Agent” on page 1231
“Troubleshooting Exchange Agent snapshot and offhost jobs” on page 1233
1234 Administrator’s Guide

Continuous protection for Exchange data
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Continuous protection for Exchange data
The Symantec Backup Exec Continuous Protection Server (CPS) combines data
protection with replication technology and disk-based data protection. When CPS
components are installed on the media server and on the Exchange server, you can
continuously protect Exchange data.
For information on what CPS components to install, see “Media server requirements for
the Backup Exec Exchange Agent” on page 1220 and “Exchange Server requirements” on
page 1222.
To enable continuous protection, you check Continuously back up transaction logs with
Backup Exec Continuous Protection Server, on the backup job properties for Exchange
backups. Backup Exec then protects the Information Store with a recurring full backup to
a backup-to-disk folder on a local NTFS volume. You can enable recovery points that run
between the full backups. Transaction logs that are created after the full backups are
continuously replicated to a backup-to-disk folder.
The full backups and the replicated transaction logs provide complete recovery to any
point in time of the Information Store, including the latest complete transaction log.
When you also enable recovery points to run at intervals between the full backups, you
can restore individual messages or folders at a point in time when the recovery point was
created. Even without recovery points, individual messages or folders can be restored
from a full backup.
For continuous protection of Exchange, the following items are required:
Requirements for configuring continuous protection for Exchange
Requirement Description
Install the Backup Exec Continuous Protection
Server (CPS) components.
Specify a recurring schedule for the full backup
of the Information Store as part of the CPS job.
See “Requirements for using the Exchange
Agent” on page 1220.
See “Scheduling jobs” on page 368.
1235

Continuous protection for Exchange data
Requirements for configuring continuous protection for Exchange
Requirement Description
Select a backup-to-disk folder as the destination
device for the CPS job.
The backup-to-disk folder must be configured
as follows:
◆ It must reside on a local NTFS volume.
◆ It cannot be a removable backup-to-disk
folder.
◆ It cannot contain junction points.
◆ The option Allocate the maximum size for
backup-to-disk files must not be selected.
See “Setting defaults for new backup-to-disk
folders” on page 226.
Note You must select a specific backup-to-disk
folder. If you select a device pool, even if
it contains a backup-to-disk folder, the
job will fail.
See “About backup-to-disk folders and files” on
page 218.
Make circular logging unavailable. If circular logging is enabled, the recurring full
backup of the Information Store will complete
without errors, but recovery points will fail.
See “Reviewing the circular logging setting for
Exchange” on page 1229.
Select the Exchange server name, not an IP
address, in the backup selections list.
Selecting an IP address for an Exchange server
in the backup selections list on the media server
is not supported.
All backup operations that are related to the continuous protection of the Exchange
Server are handled as a single job. This job is displayed in the Current Jobs view on the
Job Monitor. The status of this job changes according to the operation that is running.
1236 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Continuous protection for Exchange data
The statuses for the different operations are listed in the following table:
Continuous protection job statuses
Continuous protection operation Status on the Job Monitor in the Current Jobs view
When the recurring full backup for
the Information Store is running
When transaction logs are being
replicated
When a recovery point is running
Note The job name is displayed with
Exchange Recovery Point
appended to it.
When the recovery point is complete, on the Job Monitor, in the Job History view, the
recovery point is displayed with Exchange Recovery Point appended to the name of the
full job. If error-handling rules are enabled, they apply to recovery points that fail.
To view the continuous protection job for transaction log replication, or to view related
errors, you must go to the CPS Administration Console. If the Continuous Protection
Server Administration Console component is installed on the media server, you can view
the CPS console.
The continuous protection feature does not support:
■ The Microsoft Volume Shadow Copy Service (VSS) snapshot provider.
■ The delegation of continuous protection-related jobs to managed media servers in a
Central Admin Server Option (CASO) environment.
■ Circular logging, if recovery points are used.
■ Exchange Server 5.5.
Active; CPS backup job running
Scheduled; CPS backup job running
Note You cannot right-click this job to edit the
properties. You must click Job Setup, and then
right-click the job to edit properties.
Running
Related Topics:
“Viewing the CPS console from Backup Exec” on page 1238
“About using recovery points to restore individual items to a point in time” on page 1238
“Best practices for continuous protection of Exchange” on page 1239
“Error-handling rules” on page 474
1237

Continuous protection for Exchange data
Viewing the CPS console from Backup Exec
If the Continuous Protection Server Administration Console component is installed on
the media server, you can view the CPS console. The continuous backup job is displayed
on the CPS console with ‘Backup Exec’ appended to the name. The job is listed as an
Exchange Log Backup job type, with a status type of Running.
To view the CPS console from Backup Exec
❖ On the Tools menu, click Continuous Protection Server.
About using recovery points to restore individual items to a point
in time
As part of the continuous protection of Exchange, you can enable Backup Exec to make
recovery points at intervals that you specify. Recovery points create backup sets that you
can browse from the Restore view. You can recover individual messages or folders from a
point in time when either a full backup or recovery point was run. Each time a recovery
point is made, it also truncates the transaction logs so that log growth is controlled.
Recovery points start to run at the specified intervals after the recurring full backup has
started. However, recovery points do not run if the full backup is active. The recovery
points start running again at the specified interval when the full backup has completed.
Replication of the transaction logs is continuous, even when the full backup is active.
If you change the specified interval for the recovery points, the new interval applies after
the next full backup or recovery point runs.
The recovery point only affects Exchange resources in the backup selection list.
Resources that are not related to Exchange, but are in the same backup selection list, are
not affected by recovery points.
Performance impacts of setting recovery point frequency for the Information Store
transaction logs include the following:
Results of changing the default interval for recovery points
Making recovery points Results
If recovery points are set to occur
more frequently than the default rate
of every 8 hours
◆ The Job Monitor view and the restore selections list
may become crowded and difficult to read.
◆ The performance of the Exchange server may be
slower than when the recovery points are set to occur
at the default rate.
1238 Administrator’s Guide

Results of changing the default interval for recovery points
Making recovery points Results
If recovery points are set to occur less
frequently than the default rate of
every 8 hours
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Continuous protection for Exchange data
Transaction logs are also deleted less frequently and
therefore use more disk space.
Recovery points can only be created as part of the continuous protection strategy. If you
choose not to use recovery points, individual mail messages and folders can only be
recovered from the last full backup.
Caution Transaction logs are deleted when recovery points occur. This may affect other
Backup Exec jobs for the Exchange Server, or other jobs that are created by
third-party applications.
Related Topics:
“Best practices for continuous protection of Exchange” on page 1239
“Backing up Exchange” on page 1245
“Continuous protection for Exchange data” on page 1235
Best practices for continuous protection of Exchange
Note the following items when using continuous protection as part of your backup
strategy:
■ Symantec recommends that you back up only one Exchange server for each
continuous backup job. Create a separate selection list for each Exchange server
resource.
■ If you must copy backup sets to tape for offsite storage or vaulting, create a job to
duplicate backup sets. You can configure the job to copy the backup sets to tape after
each occurrence of the full backup job.
If the job template is in a policy, create a duplicate backup sets template to copy the
backup sets after the last incremental backup before the full backup to tape.
If necessary, you may consider creating a copy job to run before the full backup to
copy all of the transaction logs as well as the full backup sets to tape.
■ Consider creating a custom filter to limit the display of recovery points in the Job
History view.
1239

Setting default backup and restore options for Exchange data
Related Topics:
“Creating selection lists” on page 328
“Adding a duplicate backup template to a policy” on page 436
“About managing custom filters” on page 466
“Backing up Exchange” on page 1245
Setting default backup and restore options for Exchange data
You can use the defaults set by Backup Exec during installation for all Exchange backup
and restore jobs, or you can choose your own defaults.
To set default backup and restore options for Exchange
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Microsoft Exchange.
1240 Administrator’s Guide

3. Select the appropriate options as follows:
Information Store backup
method
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Setting default backup and restore options for Exchange data
Select one of the following backup methods:
◆ Full - Database & Logs (flush committed logs). Select this
method to back up the databases as well as their associated
transaction log files. After the databases and transaction logs
are backed up, the transaction log files for which all
transactions committed to the database are then deleted.
◆ Copy - Databases & Logs. Select this method to back up the
databases as well as their associated transaction log files.
However, the transaction logs are not deleted after being
backed up.
You can use the copy method to make a full backup of a
database without disturbing the state of ongoing incremental
or differential backups.
◆ Differential - Logs. Select this method to back up all of the
transaction logs that have been created or modified since the
last full backup. However, the transaction logs are not deleted
after being backed up.
To restore from differential backups, the last differential
backup and the last full backup are required.
◆ Incremental - Logs (flush committed logs). Select this method
to back up all of the transaction logs that have been created
or modified since the last full or incremental backup, and
then delete the transaction logs that have been committed to
the database.
To restore from incremental backups, the last full backup and
all incremental backups done since the last full backup are
required.
To review available backup methods for snapshots, see
“Available backup methods for Exchange snapshot versions”
on page 1232.
Note If circular logging is enabled, incremental, differential,
and continuous protection backups cannot be performed.
1241

Setting default backup and restore options for Exchange data
Enable the restore of
individual mail messages
and folders from
Information Store backups
(Exchange 2000 or later;
incremental backups
supported with
policy-based jobs only)
Enable legacy mailbox
support (not recommended
- use information store
instead)
No loss restore (do not
delete existing transaction
logs)
Check Enable the restore of individual mail messages and
folders from Information Store backups to enable the restore of
individual mail messages and folders from full or copy backups
of the Information Store.
Symantec recommends that if this option is selected, you should
select a backup-to-disk folder on a local NTFS volume as the
destination device. Additional requirements are listed in
“Requirements for Information Store backups that are enabled
for the restore of individual items” on page 1230. If data must be
restored from a tape, then the media server must stage the
restore of the entire database to a temporary path to extract
individual items.
Note This option is automatically enabled when Continuously
back up transaction logs with Backup Exec Continuous
Protection Server is checked. This lets you restore
individual messages or folders from a CPS backup.
If you plan to restore individual mailboxes and messages, and
you run incremental backups of the Exchange database, you
must select a backup-to-disk folder on a local NTFS volume as
the destination device. Do not select a tape device, as restoring
individual mailboxes and messages from incremental Exchange
backup sets on tape is not supported.
Check Enable legacy mailbox support to select individual
mailboxes for backup with the Information Store. See “Backing
up individual Exchange mailboxes” on page 1255 for a
description of these fields. Note that a separate job to back up
mailboxes is not necessary. See “About restoring individual
mailboxes and folders from the Information Store” on page 1230.
You must check Enable legacy mailbox support to enable the
mailbox backup methods to appear on the Exchange Backup
Properties page.
If you are upgrading from a previous version of Backup Exec,
Enable legacy mailbox support is checked by default. Jobs for
mailbox backups can continue as scheduled.
Uncheck Enable legacy mailbox support to make the mailbox
resources unavailable on the backup selections tree.
Select this to preserve the existing transaction logs on Exchange
Server 5.5. Transaction logs on the storage media are then
restored and added to the existing set of transaction logs on
Exchange Server 5.5. When the restore operation finishes,
Exchange Server 5.5 automatically updates its databases with
the uncommitted transactions found in the existing and newly
restored transaction logs. This option is selected by default.
1242 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Setting default backup and restore options for Exchange data
Restore public folder Select this to restore only Exchange 5.5 Information Store’s
public database (PUB.EDB). Although this database cannot be
backed up separately from the Information Store’s private
database (PRIV.EDB), it can be restored separately.
Restore private mailboxes Select this to restore only Exchange 5.5 Information Store’s
private database. Although this database cannot be backed up
separately from the Information Store’s public database
(PUB.EDB), it can be restored separately.
If the Restore public folder and Restore private mailboxes
options are selected independently, the No loss restore option is
automatically selected and cannot be cleared.
Temporary location for log
and patch files
Type a location where the associated log and patch files are to be
kept until the database is restored. The default location is \temp.
If storage groups are being restored, a subdirectory in \temp is
created for each storage group. The log and patch files for each
storage group are kept in the corresponding subdirectory.
If Commit after restore completes is selected for the restore job,
the log and patch files in the temporary location are applied to
the database, and then the current log files are applied. After the
restore is complete, the log and patch files are automatically
deleted from the temporary location (including any
subdirectories). See “About restoring Exchange data” on
page 1258.
Note Make sure the temporary location for log and patch files is
empty before you start a restore job. If a restore job fails,
check the temporary location (including subdirectories) to
make sure that any log and patch files from a previous
restore job were deleted.
1243

Setting default backup and restore options for Exchange data
Automatically recreate
user accounts and
mailboxes
Related Topics:
“Backup strategies for Exchange” on page 1225
Select this check box to recreate the user accounts and their
mailboxes if they do not already exist on the destination server.
The restore job fails if a mailbox that is being restored does not
exist on the destination server.
The option Back up the information used to automatically
recreate user accounts and mailboxes must have been selected
for backup. See “About selecting individual mailboxes for
backup” on page 1252.
When you check Automatically recreate user accounts and
mailboxes, you are prompted for a password for accounts that
are recreated.
If the user account was recently deleted, and if the Active
Directory tombstone for the object has not expired, then you
must reset the user account password. For Active Directory user
objects, use the Microsoft Active Directory Users and Computers
application.
Note Automatically recreate user accounts and mailboxes
applies only if mailboxes are being restored to their
original location. If the mailbox restore is being redirected,
the user account and mailbox must already exist on the
target server.
Change password... Click this to specify a password to use when user accounts and
mailboxes are automatically recreated on the destination server.
When restoring individual
mail messages and folders,
restore over existing
messages and folders
Check When restoring individual mail messages and folders,
restore over existing messages and folders to replace an existing
item with the message or folder. Check this when you are
restoring from a continuous protection recovery point backup or
from an Information Store backup for which the restore of
individual items was enabled. A new object ID is not created for
the message or folder; only the contents and properties are
replaced.
If this check box is not checked, or if the original message or
folder does not exist, then the message or folder is recreated as a
new message or folder.
If this check box is not checked and if the original message or
folder does exist, then the message or folder is skipped.
For more information, see “About restoring individual mailboxes
and folders from the Information Store” on page 1230 or “About
using recovery points to restore individual items to a point in
time” on page 1238.
1244 Administrator’s Guide

“Snapshot and offhost backups with the Exchange Agent” on page 1231
“About restoring Exchange data” on page 1258
Backing up Exchange
To back up Exchange data, you can select:
■ Multiple storage groups
■ Individual storage groups
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Backing up Exchange
■ Individual databases (not supported if using snapshot technology)
Symantec recommends that you select individual storage groups for backup rather than
selecting individual databases in storage groups. Although you can select individual
databases in a storage group for backup, the transaction logs for the entire storage group
are backed up for each database selected.
For example, if you select four databases in a storage group for backup, the entire
collection of transaction logs for the storage group is also backed up four times. The
transaction logs are not deleted until a full backup is run on every database in the
storage group. You can still restore an individual database from a storage group backup.
Note To perform incremental and differential backups of storage groups, or to perform a
backup job for which continuous protection is enabled, make sure that circular
logging is not enabled on the storage group.
To back up Exchange
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Properties pane, under Source, click Selections.
1245

Backing up Exchange
4. View the Exchange data that you want to back up by doing one or both of the
following:
To display Exchange data
on local or remote
computers:
To display Exchange data
from a server cluster:
5. Do one of the following:
◆ Click the domain name icon or icons that contain the
Exchange installations
◆ Expand the actual Windows computer icon that contains the
Exchange installation.
Note You must select the Exchange server name, not an IP
address, in the backup selections list. Selecting an IP
address for an Exchange server in the backup selections list
on the media server is not supported.
◆ On the virtual server, click the domain name icon or icons that
contain the Exchange installations
◆ Expand the actual Windows computer icon that contains the
Exchange installation.
To select all Exchange Check Microsoft Information Store.
storage groups for backup
To select specific storage
groups
Expand the Microsoft Information Store icon, and then select
individual storage groups.
6. If prompted, select a logon account that you can use to connect to the Exchange
Server.
7. On the Properties pane, under Settings, click Microsoft Exchange.
1246 Administrator’s Guide

8. Select the appropriate options as follows:
Backup method
(Information Store
backups)
Continuously back up
transaction logs with
Backup Exec Continuous
Protection Server
Select one of the following backup methods:
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Backing up Exchange
◆ Full - Database & Logs (flush committed logs). Select this
method to back up the databases as well as their associated
transaction log files. After the databases and transaction logs
are backed up, the transaction log files for which all
transactions are committed to the database are then deleted.
◆ Copy - Databases & Logs. Select this method to back up the
databases as well as their associated transaction log files.
However, the transaction logs are not deleted after being
backed up.
You can use the copy method to make a full backup of a
database without disturbing the state of ongoing incremental
or differential backups.
◆ Differential - Logs. Select this method to back up all of the
transaction logs that have been created or modified since the
last full backup. However, the transaction logs are not deleted
after being backed up.
To restore from differential backups, the last differential
backup and the last full backup are required.
◆ Incremental - Logs (flush committed logs). Select this method
to back up all of the transaction logs that have been created or
modified since the last full or incremental backup, and then
delete the transaction logs that have been committed to the
database.
To restore from incremental backups, the last full backup and
all incremental backups done since the last full backup are
required.
To review available backup methods for snapshots, see
“Available backup methods for Exchange snapshot versions”
on page 1232.
Note If circular logging is enabled, incremental, differential,
continuous protection backups cannot be performed.
Check Continuously back up transaction logs with Backup Exec
Continuous Protection Server to enable a full restore of the
Exchange database that includes transaction logs that are
continuously protected between full backups.
Review “Requirements for configuring continuous protection for
Exchange” on page 1235 before you check this box.
You may also want to review “Best practices for continuous
protection of Exchange” on page 1239.
1247

Backing up Exchange
Make a recovery point
that creates browsable
backup sets and
truncates logs every
Check Make a recovery point that creates browsable backup sets
and truncates logs every to create backup sets that you can
browse from the Restore view. You can recover individual
messages or folders from a point in time when the last recovery
point was run. Each time a recovery point is made, it also
truncates the transaction logs so that log growth is controlled.
If circular logging is enabled, the recurring full backup of the
Information Store completes without errors, but recovery points
fail.
If you do not check Make a recovery point that creates browsable
backup sets and truncates logs every, then individual mail
messages and folders can be restored only from the CPS backup.
The default interval is 8 hours. The minimum interval that you
can set is every 15 minutes. The maximum interval is 1 year. If you
change the specified interval for the recovery points, the new
interval applies after the next full backup or recovery point is run.
Before you change the default interval, review performance
factors for setting recovery point intervals in “About using
recovery points to restore individual items to a point in time” on
page 1238.
1248 Administrator’s Guide

Enable the restore of
individual mail messages
and folders from
Information Store
backups
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Backing up Exchange
Check Enable the restore of individual mail messages and folders
from Information Store backups to enable the restore of
individual mail messages and folders from full or copy backups of
the Information Store.
Symantec recommends that if this option is selected, you should
select a backup-to-disk folder on a local NTFS volume as the
destination device. Additional requirements are listed in
“Requirements for Information Store backups that are enabled for
the restore of individual items” on page 1230. If data must be
restored from a tape, then the media server must stage the restore
of the entire database to a temporary path to extract individual
items.
Additionally, if your backup strategy for the Information Store
includes full and incremental backups, these job templates must
both be created in a policy, with a backup-to-disk folder as the
destination device.
Note This option is automatically enabled when Continuously
back up transaction logs with Backup Exec Continuous
Protection Server is checked. This lets you restore
individual messages or folders from a CPS backup. This
option cannot be unchecked when the continuous
protection option is checked.
If you plan to restore individual mailboxes and messages, and you
run incremental backups of the Exchange database, you must
select a backup-to-disk folder on a local NTFS volume as the
destination device. Do not select a tape device, as restoring
individual mailboxes and messages from incremental Exchange
backup sets on tape is not supported.
Guide Me Click Guide Me to start a wizard that helps you choose backup job
properties for backing up Exchange data.
1249

Backing up Exchange
Perform consistency
check before backup
when using Microsoft
Volume Shadow Copy
Service (VSS) snapshot
provider
Continue with backup if
consistency check fails
Select this option if you want a consistency check to be performed
when the option Microsoft Volume Shadow Copy Service is
selected. The option Microsoft Volume Shadow Copy Service is
automatically used whenever a software backup is selected on the
Advanced Disk-based Backup Option backup properties. You can
also select the Microsoft Volume Shadow Copy Service on the
Advanced Open File Option backup property page.
The consistency check, which is run on the snapshot, determines
if possible data corruption exists.
If this option is selected, and the dependent option Continue with
backup if consistency check fails is not selected, then data for
specific Exchange objects that are determined to be corrupt are
not backed up. All other non-corrupt Exchange objects are backed
up.
For example, if any transaction log file for a Storage Group is
corrupt, then none of the transaction log files are backed up for
that Storage Group when the Continue with backup if
consistency check fails option is not selected. However, the
Exchange database files are backed up if Backup Exec determines
they are not corrupt. Similarly, if a specific Exchange database file
is corrupt, then backup is skipped only for that corrupt database
file. All other non-corrupt database files and transaction log files
are backed up.
Note When the option Continue with backup if consistency
check fails is enabled, then all Exchange data is backed up
regardless if corrupt files exist.
See “Snapshot and offhost backups with the Exchange Agent” on
page 1231.
Select this option if you want the backup job to continue even if
the consistency check fails. You may want the job to continue if
you think a backup of the database in its current state is better
than no backup at all, or if you are backing up a very large
database that may have only a small problem.
1250 Administrator’s Guide

If Exchange 2007
backup source
is LCR or CCR only
Backup Method
(Mailbox backups)
Enable single instance
backup for message
attachments
(for mailbox and public
folder backups only)
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Backing up Exchange
Select one of the following backup sources if the Exchange 2007
backup source is a CCR or LCR database:
◆ Back up from the passive copy and if not available, try the
active copy (Recommended).
When you use this option for a local continuous replication
(LCR) or a cluster continuous replication (CCR) database,
Backup Exec backs up the passive copy of the database by
default. However, if the passive copy is not available, Backup
Exec backs up the active database. During the backup,
database performance degradation can occur.
◆ Back up from the passive copy only (job fails if not available).
Select this option when you do not want to affect the
performance of the active database.
If you select this option and the passive database is
unavailable, the backup job fails. In this case, neither the
active nor the passive database is backed up.
◆ Back up from the active copy only (job fails if not available).
Select this option to only back up from the active database.
The active database contains newer information than the
passive copy. Therefore, when you back up the active database,
you have a backup of the most recent database data.
If you select this option and the active database is unavailable,
the backup job fails. Therefore, neither the active nor the
passive copy is backed up.
Select a mailbox backup method.
See “Backing up individual Exchange mailboxes” on page 1255 for
a description of these backup methods.
See “Backing up individual Exchange mailboxes” on page 1255 for
a description of this option.
Guide Me Click Guide Me to start a wizard that helps you choose the
appropriate options when you want to back up Exchange
mailboxes.
Related Topics:
“About restoring individual mailboxes and folders from the Information Store” on
page 1230
“Reviewing the circular logging setting for Exchange” on page 1229
1251

Backing up Exchange
“About backup-to-disk folders and files” on page 218
About selecting individual mailboxes for backup
In previous versions of Backup Exec, you backed up individual Exchange mailboxes
separately from the Information Store so that you could restore individual mailboxes. In
this version of Backup Exec, you can enable the option to restore individual mail
messages and folders from Information Store backups.
Restoring individual mailboxes from an Information Store backup that is on tape may be
slower than restoring mailboxes from a legacy mailbox backup. If you have only a few
mailboxes, and if you can only back up to tape, you may prefer to use the legacy mailbox
backup methods.
Note Exchange 2007 does not support individual mailbox backup.
If you must back up individual Exchange mailboxes separately from the Information
Store, then consider the following:
When using legacy backup methods for mailboxes
Recommendation Description
Use full and incremental
backups
Continue to back up the
Information Store
Consider running full backups of mailboxes or public folders on a
regular basis. Supplement the full backups with incremental or
differential backups to keep backup run time to a minimum.
Note If you plan to restore individual mailboxes and messages, and
you run incremental backups of the Exchange database, you
must select a backup-to-disk folder on a local NTFS volume as
the destination device. Do not select a tape device, as restoring
individual mailboxes and messages from incremental Exchange
backup sets on tape is not supported.
See “About restoring individual Exchange mail messages and
folders from Information Store backups” on page 1264 and
“Restoring individual Exchange public folder messages from
tape and duplicating Exchange backup sets” on page 1266.
Do not substitute mailbox backups for backups of the entire
Information Store. You cannot perform a complete restore of Exchange
Server from a mailbox backup. You can only perform a complete
restore of Exchange Server from backups of the Information Store.
1252 Administrator’s Guide

When using legacy backup methods for mailboxes
Recommendation Description
Recover deleted items
rather than restoring
them
Exclude unwanted or
unnecessary folders from
the backup
Enable single-instance
backup for message
attachments
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Backing up Exchange
Consider using the Exchange System Manager utility to adjust the
deletion settings in each Store’s properties. Deleted items can be
retained for a period of time, allowing them to be recovered rather
than restored. See your Microsoft Exchange Server documentation for
details.
When you select a mailbox or public folder for backup, by default all
folders and subfolders are included. You can exclude specific folders
and subfolders. See “Including or excluding files for backup” on
page 325.
For example, to exclude all mail in the Deleted Items folder, type:
\**\Deleted Items\*
To exclude all mail in the Sent Items folder, type:
\**\Sent Items\*
When backing up mailboxes and public folders, you can choose to back
up only a single copy of all identical message attachments. When an
identical attachment is found, a reference to that attachment is
retained. The actual attachment is backed up only once at the end of
the backup set.
Enabling single instance backup for message attachment increases
backup performance since duplicate attachments are backed up only
once.
Note If the backup job does not complete, the message attachments
may not be included in the backup set. Rerun the backup until it
successfully completes.
If you used the incremental backup method, running the job
again does not back up the same messages and attachments. You
must run a full or copy backup to ensure that all messages and
attachments are backed up completely.
1253

Backing up Exchange
When using legacy backup methods for mailboxes
Recommendation Description
Do not back up special
system mailboxes created
by Exchange
Select public folders from
only one Exchange server
Although these special system mailboxes can be backed up, it is not
necessary or useful. The following are common examples of special
system mailboxes. There may be others depending on the Exchange
server configuration and environment.
◆ System Attendant
◆ Any mailbox name starting with SMTP or System Mailbox
Also, when selecting objects from the mailbox tree, all objects are
displayed as messages. Some non-message objects can be identified by
the subject line. For example, if you create a Calendar event named
Appointment1, that name is displayed in the subject line for that
object. However, some objects such as Forms and Views do not have a
subject line (even though they can be named) and may not be easily
identifiable.
The same public folders may appear for multiple Exchange servers
since public folders can be replicated. Selecting public folders on
multiple Exchange servers only increases the time and media required
for the backup and does not provide any additional protection.
Note Antivirus software may impact mailbox backup performance and could result in
incorrect job log errors. Mail messages and the attachments will be fully backed up
and fully restorable despite job log errors that may be generated when verifying
the attached files.
Mailboxes are displayed in a server-centric view; that is, only mailboxes on the selected
Exchange server are displayed in the backup selections list. Public folders may be
displayed on more than one server since public folders can be replicated to many servers.
In versions of Backup Exec prior to 8.6, mailboxes could be selected for backup from a
site-centric view, which listed all mailboxes in the Exchange Organization, not just
mailboxes on the selected server. Even though only the server-centric view is now
available for Exchange mailboxes, you can still restore mailbox backup sets that were
created using a site-centric view.
If you select mailboxes from the same server, they are placed together in one backup set
on the storage media. If you select mailboxes from more than one server, then the
mailboxes are placed in separate backup sets according to the server.
1254 Administrator’s Guide

Backing up individual Exchange mailboxes
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Backing up Exchange
Review the information in “About selecting individual mailboxes for backup” on
page 1252.
To back up individual Exchange mailboxes
1. On the Tools menu, click Options.
2. On the properties pane, under Job Defaults, click Microsoft Exchange.
3. Check Enable legacy mailbox support (not recommended - use Information Store
instead).
4. Click OK.
5. On the navigation bar, click the arrow next to Backup.
6. Click New Backup Job.
7. On the Properties pane, under Source, click Selections.
8. View the Exchange mailboxes or public folders that you want to back up by doing one
or all of the following:
To select Exchange
mailboxes or public
folders from local or
remote computers:
To select Exchange
mailboxes or public
folders from a clustered
Exchange server:
Click the domain name icon or icons that contain the Exchange
mailboxes. Expand the Microsoft Exchange Mailbox icon that
contains the Exchange mailboxes or public folders.
On the virtual server, click the domain name icon or icons that
contain the Exchange mailboxes. Expand the Microsoft Exchange
Mailbox icon that contains the Exchange mailboxes or public
folders.
9. Select the mailboxes or individual messages, mailboxes, and folders that you want to
back up.
When you select a mailbox or public folder, all folders and subfolders are included in
the backup by default. For a faster backup, consider using Advanced File Selections
to exclude some folders, such as Deleted Items or Sent Items, and subfolders from
the backup.
Because public folders can be replicated on multiple Exchange servers, select public
folders from only one Exchange server.
1255

Backing up Exchange
10. If prompted, select a logon account that allows you to connect to the Exchange
mailboxes or public folders.
For information on using logon accounts when making backup selections, see
“Exchange mailbox access requirements” on page 1224.
11. On the Properties pane, under Settings, click Microsoft Exchange.
12. Select a backup method for the Information Store.
13. Select the following options as appropriate:
Mailbox backup method ◆ Full - Back up messages - Reset archive bit. Select this method
to back up all messages in the selected mailboxes. This option
is set by default.
A time/date stamp that is placed in each folder indicates that
the messages have been backed up.
◆ Copy - Back up messages. Select this method to back up all
messages in the selected mailboxes. A time/date stamp is not
used, so incremental and differential backups are not affected.
Use the copy method to make a full backup of the mailboxes
without disturbing the state of ongoing incremental or
differential backups.
◆ Differential - Back up changed messages. Select this method to
back up all of the messages that have been created or modified
in the selected mailboxes since the last full backup.
The time/date stamp that is placed on the folders during the
last full backup is used to determine which messages have
been modified since the last full backup. The time/date stamp
is not updated during the differential backup.
◆ Incremental - Back up changed messages - Reset archive bit.
Select this method to back up only the messages that have
been modified in the selected mailboxes since the last full or
incremental backup.
The time/date stamp that is placed on the folders during the
last full or incremental backup is used to determine which
messages have been modified since the last full or incremental
backup. The time/date stamp is updated during the
incremental backup.
1256 Administrator’s Guide

Enable single instance
backup for message
attachments (for mailbox
and public folder backups
only)
Back up the information
used to automatically
recreate user accounts
and mailboxes
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Backing up Exchange
14. If necessary, select other backup options from the Properties pane that you want to
apply to these selections.
15. Schedule or start the backup job.
Check Enable single instance backup for message attachments to
back up only a single copy of all identical message attachments.
When an identical attachment is found, a reference to the
attachment is retained. The actual attachment is backed up at the
end of the backup set.
Enabling single instance backup for message attachment
increases backup performance since duplicate attachments are
backed up only once.
Uncheck Enable single instance backup for message attachments
if you want each identical copy of a message attachment to be
backed up and kept in order on the backup set.
Note If the backup job does not complete, the message
attachments may not be included in the backup set. Run the
backup until it completes successfully completed.
If the incremental backup method was used, running the job
again will not back up the same messages and attachments.
You must run a full or copy backup to ensure that all
messages and attachments are backed up completely.
Check Back up the information used to automatically recreate
user accounts and mailboxes if you want to recreate user
accounts and mailboxes during a restore.
This option is not checked by default.
Related Topics:
“Exchange mailbox access requirements” on page 1224
“When using legacy backup methods for mailboxes” on page 1252
“Backing up data” on page 345
1257

About restoring Exchange data
About restoring Exchange data
You can use the defaults for all Exchange restore jobs, or you can choose your own
defaults. You can also change the defaults for any specific restore job.
For information about restoring Exchange data from specific backup strategies, review
the following table:
Restoring Exchange data
For information about Go to
Required configuration and tasks before
restoring Exchange data
Using the recovery storage group to recover
data from an older backup copy of the store
without disturbing client access to current data
Restoring Exchange data from snapshot
backups
Restoring the Exchange database from
continuous protection backup sets and
restoring individual mail messages and folders
Restoring individual mail messages and folders
from Information Store backups for which the
option to restore individual items was enabled
Restoring Exchange mailboxes and folders from
a backup that is separate from the Information
Store backup
Restoring individual Exchange public folder
messages from tape
“Requirements for restoring Exchange 2000,
2003, and 2007” on page 1259
“About restoring Exchange 2003 and Exchange
2007 data using the recovery storage group” on
page 1260
“About restoring Exchange data from snapshot
backups” on page 1262
“Restoring Exchange data from continuous
protection backups” on page 1263
“About restoring individual Exchange mail
messages and folders from Information Store
backups” on page 1264
“About restoring Exchange mailboxes and
public folders from mailbox backups” on
page 1265
“Restoring individual Exchange public folder
messages from tape and duplicating Exchange
backup sets” on page 1266
Configuring a restore job for Exchange data “Restoring Exchange data” on page 1267
Restoring Exchange data to a server other than
the one from which it was backed up
“About redirecting Exchange restore data” on
page 1273
1258 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
About restoring Exchange data
Requirements for restoring Exchange 2000, 2003, and 2007
Review the following before restoring Exchange 2000, 2003, and 2007:
■ The storage groups and databases must already exist on the target server, and must
have the same names as the original storage groups or databases.
■ The target server must have the same Organization and Administrative Group name
as the source server.
Before you start the restore, do the following:
Required tasks before restoring Exchange data
Task Description
Configure the target databases so that they can
be overwritten
Requirements for restoring Exchange Server 5.5
Review the following before restoring an Exchange Server 5.5:
To configure the databases, do the following in
the order presented:
◆ Open the Exchange System Manager utility.
◆ Right-click the database that you want to
overwrite.
◆ Click Properties.
◆ On the Database tab, select This database
can be overwritten by a restore.
Dismount databases that are being restored To dismount a database, do one of the following:
◆ Use the Exchange System Manager utility.
◆ When creating a restore job, on the Backup
Exec Restore Job Properties pane, under
Settings, click Microsoft Exchange. Check
Dismount database before restore.
■ Restoring an Exchange Server 5.5 Directory Store to an Exchange Server other than
the original is not supported; only Information Store data can be restored to a
different computer.
■ The Exchange System Attendant service must be running on the target server.
If you are restoring Exchange data to more than one Windows computer, the System
Attendant service must be running on each target computer.
■ The target server must have access to the original Security Account Manager (SAM)
information If you are restoring the Exchange Directory.
1259

About restoring Exchange data
If the recovered server does not have access to the SAM information from the
original domain, and the Directory Store is restored, none of the Exchange data is
accessible after the restore. This is because the Exchange Directory uses SID
(Security Identifier) information for authenticating access to objects and the restored
SID information will not match SID information from the SAM in the new domain.
■ The Directory and Information Store services are stopped when the corresponding
stores are restored. Users cannot access them until the restore is complete and the
services are restarted.
About restoring Exchange 2003 and Exchange 2007 data using
the recovery storage group
The Recovery Storage Group (RSG) feature in Exchange Server 2003 and Exchange
Server 2007 lets you to mount a second copy of an Exchange mailbox store on any
Exchange server in the same Exchange Administrative Group as the original while the
original store is still running and serving clients. This allows you to recover data from an
older backup copy of the store without disturbing client access to current data. See your
Microsoft Exchange documentation for instructions on creating the recovery storage
group and adding the mailbox stores you want to restore to it.
After the RSG is created and one or more stores are added to it, you can restore online
backup sets to it. Then you can use the version of the EXMerge utility in Exchange 2003
and Exchange 2007 to extract mailbox data from the stores into .PST files, and optionally
merge the extracted data back into the online stores.
If the RSG resides on a different Exchange server than the databases you are restoring,
see “About redirecting Exchange storage group and database restores” on page 1273.
Following are requirements for restoring Exchange Server 2003 and Exchange Server
2007 data using the Recovery Storage Group (RSG):
■ Data cannot be restored from a snapshot backup (Exchange 2003 only).
■ If multiple stores are selected for restore, mailbox stores in the RSG must come from
the same storage group. You cannot add mailbox stores from different storage groups
to the RSG at the same time.
■ Public folder stores are not supported for restore using the RSG.
■ Do not mount mailbox stores in the RSG before the restore. If you do mount the
stores before the restore, then you must dismount them. Select This database can be
overwritten by a restore on the database property page in Exchange System
Manager, and delete any files created in the data path for the RSG and added stores
prior to restoring them.
Any files created in the data path for the RSG and added store or stores, should be
deleted as well, if stores were mounted prior to the restore.
1260 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
About restoring Exchange data
■ On the server that hosts the RSG, there must be a storage group with the same name
as the original storage group for the data you are restoring. If no such storage group
exists on the server, then you can use that name for the RSG when you create it.
■ The Active Directory topology of the Exchange system must be intact and in the
same state it was in when the backup was made. You cannot restore mailbox stores
that were deleted and recreated. In addition, you cannot recover mailboxes from
stores if the mailboxes were deleted and purged from the system or moved to other
servers or mailbox stores.
■ Only Exchange mailbox stores from Exchange 2000 Server with Service Pack 3 or
later can be restored to the RSG. Restored mailbox stores are upgraded to the store
version currently running on the RSG server.
■ When the RSG exists on a server, the mailbox stores that it contains are the only
stores that can be restored on that server by default. Symantec recommends that you
create the RSG only when you intend to recover data using it, and remove the RSG
from the server after the data recovery is complete.
Refer to your Microsoft Exchange Server documentation for more information on the
requirements and restrictions of recovering Exchange data using the RSG.
Related Topics:
“Restoring Exchange data” on page 1267
“About redirecting Exchange storage group and database restores” on page 1273
Restoring an Exchange 2007 database to a recovery storage group
Use the following steps to restore an Exchange 2007 database to a recovery storage group
on an Exchange 2007 server. After restoring the database to the recovery storage group,
see your Microsoft Exchange documentation for further Exchange recovery information.
To restore an Exchange 2007 database to a recovery storage group
1. Make sure that a recovery storage group exists on the destination Exchange 2007
server, and that a recovery database exists within the recovery storage group. If
either of these do not exist, you must create them before continuing. To create a
recovery storage group or a recovery database, see your Microsoft Exchange
documentation.
2. On the navigation bar, click the arrow next to Restore.
3. Click New Restore Job.
4. On the Restore Job Properties pane, under Source, click Selections.
1261

About restoring Exchange data
5. Select an Exchange 2007 database to restore.
6. On the Restore Job Properties pane, under Destination, click Microsoft Exchange
Redirection.
7. Click Redirect Exchange sets.
8. In the Restore to server field, type the name of the destination Exchange 2007 server.
9. Click Redirect using Volume Shadow Copy Service (VSS) snapshot provider.
10. Click Redirect to Recovery Storage Group (RSG)(Exchange 2007 only).
11. Click Run Now.
Backup Exec restores the Exchange 2007 database to the destination recovery
storage group. After the restore job completes, see your Microsoft Exchange
documentation for further Exchange 2007 recovery information.
Related Topics:
“Restoring Exchange data” on page 1267
“About redirecting Exchange storage group and database restores” on page 1273
About restoring Exchange data from snapshot backups
Note the following when restoring Exchange data from snapshot backups:
■ If circular logging is enabled, only point-in-time, loss restores are possible.
Roll-forward, no-loss restores cannot be performed.
■ Individual database restores cannot be performed. The job will fail.
■ The following options are not applicable to restores of Exchange 2003 snapshot
backups. Exchange will use the soft-recovery process when restored databases are
mounted.
■ Restore all transaction logs; do not delete existing transaction logs (no loss
restore)
■ Restore all transaction logs until point-in-time; skip transaction logs after this
time
■ Purge existing data and restore only the databases and transaction logs from the
backup sets
■ Path on Exchange Server for temporary storage of log and patch files
1262 Administrator’s Guide

■ Commit after restore completes
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
About restoring Exchange data
■ Data cannot be restored from a snapshot backup to a Recovery Storage Group (RSG)
(Exchange 2003 only). See “About restoring Exchange 2003 and Exchange 2007 data
using the recovery storage group” on page 1260.
Related Topics:
“About selecting individual mailboxes for backup” on page 1252
“Restoring Exchange data” on page 1267
Restoring Exchange data from continuous protection backups
The full backups and the replicated transaction logs provide a complete restore to any
point in time of the Information Store, including the latest complete transaction log.
Note After a restore of a storage group or mailbox store that is being protected by a CPS
job has completed, you must re-run the CPS backup job to start the replication and
recovery points again. Right-click the scheduled CPS backup job, and click Run
now.
If you enabled recovery points to run at intervals between the full backups, you can
restore individual messages or folders at a point in time when the recovery point was
created. Even without recovery points, you can restore individual messages or folders
from a full backup.
To restore the entire Information Store to the time of a full backup or recovery point
1. Select backup sets from the full backup or the recovery point that contains the point
in time that you want to restore to.
2. On the Microsoft Exchange Restore Job Properties dialog box, click Purge existing
data and restore only the databases and transaction logs from the backup sets.
To restore up to the latest full transaction log
1. Select backup sets from the last full backup or recovery point.
2. On the Microsoft Exchange Restore Job Properties dialog box, click Restore all
transaction logs; do not delete existing transaction logs (no loss restore).
1263

About restoring Exchange data
To restore to a point in time between full backups or recovery points
1. Select backup sets from any full backup or recovery point and specify the point in
time.
2. On the Microsoft Exchange Restore Job Properties dialog box, click Restore all
transaction logs until point in time; skip transaction logs after this time.
3. Specify the point in time.
Related Topics:
“Restoring Exchange data” on page 1267
“Continuous protection for Exchange data” on page 1235
“About redirecting Exchange restore data” on page 1273
About restoring individual Exchange mail messages and folders
from Information Store backups
If you checked Enable the restore of individual mail messages and folders from
Information Store backups on the backup job properties for the Information Store
backups, you can restore individual messages and folders from that backup.
This option is automatically enabled when Continuously back up transaction logs with
Backup Exec Continuous Protection Server is checked. This lets you restore individual
messages or folders from a CPS backup.
Note Individual mailboxes and messages cannot be restored from incremental Exchange
backup sets that are on tape. See “Enable the restore of individual mail messages
and folders from Information Store backups” on page 1249.
If you restore individual items from an Information Store backup set that is on a device
other than a backup-to-disk folder, then Backup Exec must temporarily stage the entire
database to a path on the media server to extract individual items. Because of the
potentially large file sizes that are created in the staging location path, system volumes
should not be used as a staging location.
To enter the path, on the Restore Job Properties pane, under Settings, click Advanced,
and then enter a path in Path on media server for staging temporary restore data when
restoring individual items from tape. For more information about this path, see
“Advanced options for restore jobs” on page 494.
Backup Exec must also have access to a uniquely named mailbox in the Exchange
organization. See “Exchange mailbox access requirements” on page 1224.
1264 Administrator’s Guide

Related Topics:
“Restoring Exchange data” on page 1267
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
About restoring Exchange data
About restoring Exchange mailboxes and public folders from
mailbox backups
You can restore individual mailboxes, messages, and public folders from backups that
were created by legacy methods, including backup sets that were created when:
■ Individual mailboxes were backed up from the Microsoft Exchange Mailboxes
selection.
■ Individual public folders were backed up from the Microsoft Exchange Public Folders
selection.
Following are notes about restoring mailboxes or public folders from legacy backup
methods:
■ Mailbox backup sets that were created using a site-centric view in versions of Backup
Exec prior to 8.6 may require multiple jobs to be run in order to restore all the
mailboxes:
■ Mailboxes that resided on the target server restore normally.
■ Mailboxes that resided on other servers must be redirected to those servers.
■ If you restore mailboxes from a backup created with a version of Backup Exec prior to
8.5, and mailboxes with duplicate Display Names reside on the server, select those
mailboxes for restore separately and follow the instructions in “About redirecting
restores of mailboxes or public folders that were backed up separately from the
Information Store” on page 1275.
■ The option Restore Over Existing Files in the Advanced Restore Job Properties does
not apply to mailboxes or public folders. If other selections are restored in addition
to mailboxes or public folders, and the option Restore Over Existing Files is selected,
it applies only to the other selections; mailboxes and public folders are not restored
over existing objects. For details on this option, see “General settings options for
restore job” on page 492.
■ Do not restore special system mailboxes created by Exchange.
The following are common examples of special system mailboxes, but there may be
others depending on the Exchange server configuration and environment.
■ System Attendant
■ Any mailbox name starting with SMTP or System Mailbox (Exchange 2000 or
later)
1265

About restoring Exchange data
■ Microsoft Schedule + Free/Busy Connector (Exchange Server 5.5)
■ Directory Service (Exchange Server 5.5)
Related Topics:
“Requirements for restoring Exchange 2000, 2003, and 2007” on page 1259
“Restoring Exchange data” on page 1267
“About redirecting restores of mailboxes or public folders that were backed up separately
from the Information Store” on page 1275
“About restoring individual mailboxes and folders from the Information Store” on
page 1230
Restoring individual Exchange public folder messages from tape and
duplicating Exchange backup sets
You can restore individual Exchange public folder messages from tape if you used the
Exchange Full or Copy backup method to do the original backup. You cannot, however,
restore individual public folder messages if the public folder was originally backed up
with the Exchange incremental backup method.
To restore individual public folder messages, the backup sets that contain the messages
that you want to restore must first be duplicated to a backup-to-disk folder.
Use the following steps to duplicate on-tape Exchange backup sets to a backup-to-disk
folder.
To restore individual Exchange public folder messages and duplicate on-tape Exchange
backup sets
1. Place the tape containing the required Exchange backup sets into a tape drive.
2. On the menu bar, click File, and then click New > Duplicate Backup Sets Job.
3. Click Duplicate existing backup sets.
4. Click OK.
5. Select the Exchange backup sets that you want to duplicate.
6. On the Properties pane, under Destination, click Device and Media.
7. In the Device list box, select a backup-to-disk folder.
8. Click Run Now.
1266 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
About restoring Exchange data
9. After the job completes, run a restore job to restore the individual public folder
messages from the Exchange backup sets that are duplicated in the backup-to-disk
folder.
Related Topics:
“Restoring Exchange data” on page 1267
Restoring Exchange data
This procedure details how to select restore job properties for Exchange, and provides
definitions for restore options specific to Exchange. For details on how to create a restore
job, and for definitions of all other restore properties, see “Restoring data” on page 483.
Use the Exchange System Manager utility to manually dismount any databases that are
being restored or check Dismount database before restore when creating the restore job.
For other requirements for restoring Exchange data, see “Requirements for restoring
Exchange 2000, 2003, and 2007” on page 1259.
Note After a restore of a storage group or mailbox store that is being protected by a CPS
job has completed, you must re-run the CPS backup job to start the replication and
recovery points again. Right-click the scheduled CPS backup job, and click Run
now.
To restore Exchange data
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
4. In the restore selections list, select the backup sets that you want to restore, or
expand the backup sets to select individual items for restore.
For information about restoring specific data, see “About restoring Exchange data”
on page 1258.
5. On the Properties pane, under Settings, click Microsoft Exchange.
1267

About restoring Exchange data
6. Select the appropriate options as follows:
Automatically recreate
user accounts and
mailboxes
When restoring individual
mail messages and folders,
restore over existing
messages and folders
Check Automatically recreate user accounts and mailboxes
when restoring mailboxes to recreate the user accounts and their
mailboxes if they do not already exist on the target server. The
restore job fails if a mailbox that is being restored does not exist
on the destination server.
The option Back up the information used to automatically
recreate user accounts and mailboxes must have been selected
for backup. See “About selecting individual mailboxes for
backup” on page 1252.
When Automatically recreate user accounts and mailboxes is
checked, the password that is entered on the Exchange Options -
Set Application Defaults dialog box is used as the password for
accounts that are recreated. See “Setting default backup and
restore options for Exchange data” on page 1240.
If the user account was recently deleted, and if the Active
Directory tombstone for the object has not expired, then you
must reset the user account password. Click Start > Control
Panel > Administrative Tools > Active Directory Users and
Computers. Right-click the user account that you want to
restore, and then click Reset password. You are prompted for the
new user password.
Note Automatically recreate user accounts and mailboxes
applies only if mailboxes are being restored to their
original location. If the mailbox restore is being redirected,
the user account and mailbox must already exist on the
target server.
Check When restoring individual mail messages and folders,
restore over existing messages and folders to replace an existing
item with the message or folder. A new object ID is not created
for the message or folder; only the contents and properties are
replaced.
If this check box is not checked, or if the original message or
folder does not exist, then it is recreated as a new message or
folder; that is, a new object ID is created for it by Backup Exec.
If this check box is not checked and if the original message or
folder does exist, then the message or folder is skipped.
1268 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
About restoring Exchange data
Exchange 5.5 Use the following options with Exchange v5.5 servers:
No loss restore (do not
delete existing transaction
logs)
Check No loss restore (do not delete existing transaction logs) to
preserve the existing transaction logs on the Exchange 5.5
Server. Transaction logs from the storage media are then
restored and added to the existing set of transaction logs on the
Exchange server. When the restore operation finishes, Exchange
automatically updates its databases with the uncommitted
transactions found in the existing and newly restored
transaction logs. This option is selected by default.
If you are restoring individual databases into a storage group, the
No loss restore check box should be selected. If this check box is
not selected, uncommitted transactions for other databases in
the storage group may be lost.
Note This option is not applicable to snapshot backups.
Restore public folder Check Restore public folder to restore only the Information
Store’s public database (PUB.EDB). Although this database
cannot be backed up separately from the Information Store’s
private database (PRIV.EDB), it can be restored separately.
Restore private mailboxes Check Restore private mailboxes to restore only the Information
Store’s private database. Although this database cannot be
backed up separately from the Information Store’s public
database (PUB.EDB), it can be restored separately.
If the Restore public folder and Restore private mailboxes
options are selected independently, the No loss restore option is
automatically selected and cannot be cleared.
Guide Me Click Guide Me to start a wizard that helps you choose restore
job properties for Exchange Server 5.5 data.
1269

About restoring Exchange data
Exchange 2000 and later Use the following options with Exchange 2000 and later.
Restore all transaction
logs; do not delete existing
transaction logs (no loss
restore)
Restore all transaction logs
until point-in-time; skip
transaction logs after this
time
Purge existing data and
restore only the databases
and transaction logs from
the backup sets
Select this option to preserve the existing transaction logs on the
Exchange server. Transaction logs from the storage media are
then restored and added to the existing set of transaction logs on
the Exchange server. When the restore operation finishes,
Exchange automatically updates its databases with the
uncommitted transactions found in the existing and newly
restored transaction logs. This option is selected by default.
If you are restoring individual databases into a storage group,
you should select this option. If this option is not selected,
uncommitted transactions for other databases in the storage
group may be lost.
If continuous protection is enabled, select backup sets from the
last full backup or recovery point to restore up to the latest full
transaction log.
Note This option is not applicable to snapshot backups.
Select this option to restore transactions from a transaction log
up to and including a point in time in the transaction log. After
the point in time, recovery from the transaction log is stopped.
If continuous protection is enabled, select the backup sets from a
full backup or a recovery point, and then specify the point in
time.
In the date and time box, select the part of the date that you want
to change. Enter a new date, or click the arrow to display a
calendar from which you can select a date.
Then, select the part of the time you want to change, and enter a
new time.
Select this option to delete the existing transaction logs. Only
the databases and transaction logs from the backup sets are
restored.
If continuous protection is enabled, select the backup sets from a
full backup or a recovery point that you want to restore the
database to.
1270 Administrator’s Guide

Path on Exchange Server
for temporary storage of
log and patch files
Dismount database before
restore
Commit after restore
completes
Mount database after
restore
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
About restoring Exchange data
Type a location where the associated log and patch files are to be
kept until the database is restored. The default location is \temp,
and a subdirectory is created for each storage group. The log and
patch files for each storage group are kept in the corresponding
subdirectory.
Make sure the temporary location for log and patch files is empty
before you start a restore job. If a restore job fails, check the
temporary location (including subdirectories) to make sure any
previous log and patch files from a previous restore job were
deleted.
Note This option is not applicable to snapshot backups.
Check Dismount database before restore if you want Backup
Exec to automatically take the Exchange database offline before
the restore job runs. If this option is not selected, you must
manually take the database offline before the restore job can run.
When restoring a snapshot backup, or when restoring an
individual Exchange database from a snapshot, all databases in a
storage group must be taken offline. Selecting this option
automatically takes all databases in a storage group offline.
Check Commit after restore completes if your selection contains
the last backup set to be restored. This option directs the restore
operation to replay the log files and roll back any uncompleted
transactions. If this option is not selected, the database is left in
an intermediate state and is not yet usable.
If Commit after restore completes is checked when an
intermediate backup is being applied, you cannot continue to
restore backups. You must restart the restore operation from the
beginning.
After the database is restored, the log and patch files in the
temporary location are applied to the database, and then the
current log files are applied. After the restore is complete, the log
and patch files are automatically deleted from the temporary
location (including any subdirectories).
Note This option is not applicable for snapshot backups.
Check Mount database after restore to mount the database so
that it is available to users. This check box is only available if
Commit after restore completes is selected.
Guide Me Click Guide Me to start a wizard that helps you choose restore
job properties for Exchange Server data.
1271

About restoring Exchange data
If you checked Enable the restore of individual mail messages and folders from
Information Store backups on the backup job properties, and if the backup job was
sent to a device other than a backup-to-disk folder, then Backup Exec must
temporarily stage the entire database to a path on the media server to extract
individual items.
Because of the potentially large file sizes that are created in the staging location
path, system volumes should not be used as a staging location.
7. To enter the path, on the Restore Job Properties pane, under Settings, click
Advanced, and then enter a path in Path on media server for staging temporary
restore data when restoring individual items from tape. For more information
about this path, see “Advanced options for restore jobs” on page 494.
8. Select other restore options from the Properties pane as appropriate, and then start
the restore job.
9. For Exchange 5.5, do the following:
After the job completes, restart the destination Exchange server or start the
Exchange services manually. You can also put a batch file in a post-job command to
restart the services. See “Advanced options for restore jobs” on page 494.
When the Exchange server is back online, run the Directory Store/Information Store
(DS/IS) consistency adjuster to resolve any inconsistencies.
Results of the consistency adjustment appear in the Windows Event Log. For more
information concerning the DS/IS consistency adjuster, refer to your Exchange
documentation.
10. Run a full backup of the restored databases.
Related Topics:
“About restoring Exchange mailboxes and public folders from mailbox backups” on
page 1265
“Requirements for restoring Exchange 2000, 2003, and 2007” on page 1259
1272 Administrator’s Guide

About redirecting Exchange restore data
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
About redirecting Exchange restore data
With Backup Exec, you can restore Exchange data to the server from which it was backed
up or redirect the Exchange data to another Exchange server. When redirecting
Exchange data, the service pack on the Exchange server where data is being redirected
should be the same as the service pack on the original Exchange server. Review
requirements for the following before redirecting restore data:
Redirected restore requirements
For requirements on redirecting this restore Go to
Exchange 2000, 2003, and 2007 storage group
and databases, including public folders
Exchange Server 5.5 Information Store
database
Exchange mailboxes or public folders backed up
separately from the Information Store
Before starting the redirected restore job, review “Restoring data” on page 483 for
information on finding and viewing specific data to restore, as well as for details on
restore options and submitting restore jobs. After completing the restore, it is
recommended that a full backup of the restored databases be performed.
Related Topics:
“Redirecting Exchange restore data” on page 1277
“About redirecting Exchange storage group and
database restores” on page 1273
“About redirecting Exchange Server 5.5
database restores” on page 1274
“About redirecting restores of mailboxes or
public folders that were backed up separately
from the Information Store” on page 1275
About redirecting Exchange storage group and database restores
Following are requirements for redirecting Exchange 2000, 2003, and 2007 storage group
and database restores:
■ The storage groups and databases must already exist on the target server, and must
have the same names as the original storage groups or databases.
■ The destination server must have the same Organization and Administrative Group
name as the source server.
■ The destination databases must be configured so that they can be overwritten. Using
the Exchange System Manager utility, right-click the database you want to overwrite,
click Properties, and then on the Database tab, select This database can be
overwritten by a restore.
1273

About redirecting Exchange restore data
You cannot redirect the restore of:
■ A version of Exchange server database to a different version of the database. Service
packs for both Exchange servers should also be the same.
■ Site Replication Service (SRS) and Key Management Service (KMS). These services
are dependent on the computer they reside on; redirection to another computer is
not supported and could result in the loss of functionality of these services.
Note KMS is not available in Exchange Server 2003 or Exchange Server 2007.
Related Topics:
“About redirecting Exchange restore data” on page 1273
“Redirecting Exchange restore data” on page 1277
About redirecting Exchange Server 5.5 database restores
Only the Information Store database can be restored to a server other than its original
server. The Directory Store database must be restored to its original server; it cannot be
restored through redirection.
When you redirect the restore of the Information Store database, the services are
stopped while the store is restored. Users cannot access the database until the restore is
complete and the services restarted.
Following are restrictions for redirecting Exchange Server 5.5 database restores:
Restrictions for redirecting restores of Exchange Server 5.5 databases
Restriction Description
The Site and Organization names
of the original and destination
servers must match.
The No loss restore option cannot
be selected.
Backup Exec does not prevent redirection of an Information
Store when the Site and Organization names differ. If the Site
and Organization names are different, the redirected restore
may appear to complete successfully but the IS service will
fail to start afterward.
The No loss restore option must be unchecked so that any
transaction logs on the destination server are removed to
avoid an incompatibility that would prevent the Information
Store service from starting.
The No loss restore option appears on the Restore Job
Properties for Exchange Server 5.5 dialog box.
1274 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
About redirecting Exchange restore data
Restrictions for redirecting restores of Exchange Server 5.5 databases (continued)
Restriction Description
The Directory Store cannot be
restored through redirection.
Before starting the restore job, review “Restoring data” on page 483 for information on
finding and viewing specific data to restore, as well as for details on restore options and
submitting restore jobs.
Related Topics:
“About redirecting Exchange restore data” on page 1273
“Redirecting Exchange restore data” on page 1277
You cannot redirect a restore job in which you have selected
to restore one or more Exchange Server 5.5 Directory
databases.
About redirecting restores of mailboxes or public folders that
were backed up separately from the Information Store
You can redirect the restore of individual mailboxes or public folders from backup sets
that were created when individual mailboxes or public folders were backed up from the
Microsoft Exchange Mailboxes selection.
Note Backup Exec does not support this feature in Exchange 2007.
If you select a single mailbox or public folder, or one or more messages from a single
mailbox, you can redirect that restore to another existing mailbox or public folder on the
same server or to a different server. If any of the folders in the original mailbox do not
exist in the destination mailbox, they are created during the restore.
If you select more than one mailbox or public folder, or folders and messages from more
than one mailbox, you can only redirect the restore to another server. Mailboxes and
public folders with the same names as those selected must already exist on the target
server.
Following are requirements for redirecting the restore of mailboxes and public folders:
■ If the mailboxes or public folders do not already exist on the target server, you must
create them before redirecting the restore. Automatic recreation of mailboxes on the
target server is not enabled for redirected restores.
■ To ensure that Backup Exec can access mailboxes or public folders on the server that
you are redirecting the restore to, click Tools>Option>Microsoft Exchange, and
ensure that Enable legacy mailbox support is checked. Click the destination server
in the backup selections tree. Select Microsoft Exchange Mailboxes, and then verify
1275

About redirecting Exchange restore data
that the target mailbox is displayed in the list of mailboxes. If you are prompted for a
logon account, use a logon account that stores the credentials of a user account that
is unique and has a corresponding mailbox of the same name. See “Exchange
mailbox access requirements” on page 1224.
■ More than one mailbox can exist with the same Display Name. When the restore of a
mailbox is redirected in Backup Exec, it is redirected to the target mailbox’s Display
Name. If a duplicate Display Name exists, then the data may be restored to the wrong
mailbox.
To prevent restoring the data to the wrong mailbox, type the name of the target
mailbox exactly as it appears when browsing to the mailbox in the backup selections
list, including the brackets surrounding the mailbox directory identifier (for
example, “Mailbox Name [mailboxname]”).
Following are requirements for redirecting the restore of individual messages to another
mailbox.
■ When redirecting the restore of mailbox data, all destination mailboxes must already
exist before the restore begins. The contents of the restored mailboxes are placed in
the destination mailboxes.
For example, Mailbox 1 consists of Top of Information Store, Inbox, and Folders 1
and 2, each containing some mail messages. If you back up Mailbox 1 and then you
restore Mailbox 1 to the existing Mailbox 2, then all of Mailbox 1, including the Top
of Information Store, Inbox, Folders 1 and 2, and messages, are restored to
Mailbox 2. Note that Mailbox 1 itself is not created under Mailbox 2.
Redirecting the restore of Mailbox 1 to Mailbox 2
If you redirect the restore of Mailbox 1\Top of Information Store\Folder 2 to
Mailbox 2, the contents of Mailbox 1\Top of Information Store\Folder 2, Message 5
and Message 6, are placed in Mailbox 2 in the same folder as they were in Mailbox 1,
as illustrated in the following graphic.
1276 Administrator’s Guide

Redirecting Mailbox 1\Top of Information Store\Folder 2 to Mailbox 2
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
About redirecting Exchange restore data
Related Topics:
“About redirecting Exchange restore data” on page 1273
“About restoring Exchange mailboxes and public folders from mailbox backups” on
page 1265
“Redirecting Exchange restore data” on page 1277
Redirecting Exchange restore data
Use the following steps to redirect Exchange data.
To redirect the restore of Exchange data
1. Follow the instructions for the restoring Exchange data in “Requirements for
restoring Exchange 2000, 2003, and 2007” on page 1259.
2. After selecting options on the Restore Job Properties dialog box, on the Properties
pane, under Destination, click Microsoft Exchange Redirection.
3. Select the appropriate options as follows:
Redirect Exchange sets Check Redirect Exchange sets to enable the Restore to server
and Server logon account fields.
Restore to server Enter the name of the computer to which you are restoring, using
the format \\server name.
1277

About redirecting Exchange restore data
Server logon account Use a Backup Exec logon account that stores the credentials of a
Windows user account. The default logon account is displayed by
default. To use another logon account, click Change. For more
information about logon accounts, see “Exchange mailbox access
requirements” on page 1224.
Redirect using Volume
Shadow Copy Service (VSS)
snapshot provider
Redirect to Storage Group
and Database (Exchange
2007 only)
Check Redirect using Volume Shadow Copy Service (VSS)
snapshot provider to enable one of the following options.
Click this option to enable the Restore to Database and Restore
to Storage Group fields.
Restore to Storage Group Type the name of an existing storage group. Use this option
when you want to redirect the restore of one or more Exchange
2007 databases to a different storage group. (Exchange 2007
only)
Restore to Database Type the name of a Exchange 2007 database that you want to
restore. Use this option when you want to redirect the restore of
a single Exchange 2007 database.(Exchange 2007 only)
When you redirect a database restore, the storage group and
database names you specify must already exist on the
destination Exchange server.
Redirect to Recovery
Storage Group (RSG)
(Exchange 2007 only)
Redirect to drive and path
(Exchange 2003 and 2007)
Click this option to redirect the restore of an Exchange mailbox
database to a recovery storage group.
You can use a recovery storage group and the Exchange 2003 or
2007 Mailbox Merge Wizard to help you restore individual user
mailbox data.
To use this option, you must create a recovery storage group. You
must also create, within the recovery storage group, a database
for each database you plan to restore. Each database you create
in the recovery storage group must use the same name as the
database that you want to restore. During a redirected restore
operation, the Exchange Agent automatically detects and uses
the recovery storage group.
For more information on recovery storage groups, see your
Microsoft Exchange Server 2007 documentation.
Click this option to enable the Restore to drive and Restore to
path fields.
1278 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
About redirecting Exchange restore data
Restore to drive Select a destination drive on which to restore the Exchange
database. Click the ellipsis button to view local and network
drives.
Restore to path Type a path to where you want to restore the Exchange database.
Redirect mailboxes or
public folders
Check Redirect mailboxes or public folders to enable the
options to redirect mailbox backup sets and public folder backup
sets.
Redirect mailbox sets Click this option to enable the redirection of mailbox backup
sets.
Restore to mailbox Enter the name of the mailbox to which you are redirecting this
restore. The mailbox must already exist on the target server.
Mailbox logon account Enter a logon account that has rights to the target mailbox. To
select a logon account, click Change. To clear an existing logon
account, click Clear.
Redirect public folder sets Click this option to enable the redirection of public folder backup
sets.
Restore to public folder Enter the name of the public folder to which you are redirecting
this restore. The public folder must already exist on the target
server.
Public folder logon account Enter a logon account that has rights to the public folder that
you are redirecting to. To select a logon account, click Change. To
clear an existing logon account, click Clear.
4. Start the redirected restore job or select other restore options from the Properties
pane.
5. If you are restoring Exchange Server 5.5, do the following:
After the restore job completes, reboot the destination Exchange server or start the
Exchange services manually. You can also put a batch file in a post-job command to
restart the services. See “Advanced options for restore” on page 494.
When the Exchange server is back online, run the Directory Store/Information Store
(DS/IS) consistency adjuster in order to resolve any inconsistencies. Results of the
consistency adjustment can be found in the Windows Event Log.
For more information concerning the DS/IS consistency adjuster, refer to your
Exchange documentation.
1279

Preparing for disaster recovery of Exchange Server
6. After the restore is complete, Symantec recommends that you run a full backup of
the restored databases.
Related Topics:
“About redirecting Exchange restore data” on page 1273
“About redirecting Exchange storage group and database restores” on page 1273
“About redirecting restores of mailboxes or public folders that were backed up separately
from the Information Store” on page 1275
Preparing for disaster recovery of Exchange Server
A disaster preparation plan is an absolute necessity for restoring Exchange efficiently
and effectively in the event of a catastrophic failure. Because Exchange uses Windows
security for authentication, disaster recovery of Exchange cannot be separated from the
disaster recovery of Windows.
Planning ahead reduces the time needed to recover. It is critical to build a kit that
includes items such as:
■ An operating system configuration sheet
■ A hard drive partition configuration sheet
■ Any RAID configuration
■ A hardware configuration sheet
■ EISA/MCA configuration disks
■ An Exchange configuration sheet
■ A Windows emergency repair diskette
To perform the actual recovery, you will need:
■ An installed copy of Backup Exec for Windows Servers
■ The latest full, incremental, and differential backups of the Exchange databases you
want to recover. If CPS backups are enabled, you can use recovery points to recover
the Exchange database.
■ The Microsoft Exchange Server Installation CD
■ Any service packs that were applied to the original installation
1280 Administrator’s Guide

Disaster recovery for Exchange
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Disaster recovery for Exchange
This procedure guides you through a complete restoration of Exchange using Backup
Exec. You should have already performed all the appropriate preparation as detailed in
“Preparing for disaster recovery of Exchange Server” on page 1280.
If the Exchange 2000 Server being recovered contains the Site Replication Service (SRS)
and/or Key Management Service (KMS), then before you begin the disaster recovery,
refer to your Exchange documentation for details on recovering those databases.
Always log in to Windows using the Administrator account (or an Administrator
equivalent) during this procedure. Other requirements include:
■ The storage groups and databases must already exist on the target server, and have
the same names as the original storage groups or databases.
■ The destination server must have the same Organization and Administrative Group
name as the source server.
■ The destination databases must be configured so that they can be overwritten. Using
the Exchange System Manager utility, right-click the database you want to overwrite,
click Properties, and then on the Database tab, select This database can be
overwritten by a restore.
If you purchased the Intelligent Disaster Recovery option, see “About Microsoft
Exchange recovery notes” on page 1536 for directions on using Intelligent Disaster
Recovery to recover the Exchange server.
To perform disaster recovery for Exchange 2000 or later
1. Recover the Windows server first.
For instructions, see “Returning to the last known good configuration” on page 655.
Make sure you restore the Exchange Server 2000 Server or later files that existed on
all disk partitions.
When the Windows 2000 server disaster recovery procedure is complete (after the
last reboot), you must recover the Exchange server.
2. From the Services applet, verify the Microsoft Exchange Information Store service is
started.
3. Start Backup Exec.
4. Catalog the media that contains the latest backup of the Exchange 2000 Server or
later storage groups you want to recover.
5. On the navigation bar, click the arrow next to Restore.
1281

Disaster recovery for Exchange
6. Click New Restore Job.
7. On the Properties pane, under Source, click Selections.
8. Select the latest full backups of each storage group for restore.
If continuous protection is enabled, you can select the backup sets from a full backup
or a recovery point.
If the Exchange 2000 Server being recovered contains the Site Replication Service
(SRS) and/or Key Management Service (KMS), then select those databases for restore
as well.
9. If necessary, select all subsequent incremental storage group backups.
If differential backups are to be restored, only the most recent differential storage
group backups need to be selected.
10. On the Properties pane, under Settings, click Microsoft Exchange.
11. Click the Purge existing data and restore only the databases and transaction logs
from the backup sets option.
12. In the Path on Exchange Server for temporary storage of log and patch files field,
type a location where the associated log and patch files are to be kept until the
database is restored.
Make sure the temporary location for log and patch files is empty before you start a
restore job. If a restore job fails, check the temporary location (including
subdirectories) to make sure any previous log and patch files from a previous restore
job were deleted.
13. If your selection contains the last backup set to be restored, check Commit after
restore completes.
Do not check this if you still have backup sets to restore.
If Commit after restore completes is checked when an intermediate backup is being
applied, you cannot continue to restore backups and you must restart the restore
operation from the beginning.
After the database is restored, the log and patch files in the temporary location are
applied to the database, and then the current log files are applied. After the restore is
complete, the log and patch files are automatically deleted from the temporary
location (including any subdirectories).
14. If you want the databases to be immediately available to users after the recovery,
check Mount database after restore.
1282 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Disaster recovery for Exchange Server 5.5
15. Start the restore job or select other restore options on the Properties pane.
16. After completing the restore, it is recommended that a full backup of the restored
databases be performed.
Disaster recovery for Exchange Server 5.5
This procedure guides you through a complete restoration of Exchange Server 5.5 using
Backup Exec. You should have already performed all the appropriate preparation as
detailed in “Preparing for disaster recovery of Exchange Server” on page 1280.
Always log on to Windows using the Administrator account (or an Administrator
equivalent) during this procedure.
To properly recover Exchange, the Directory Store needs to be restored to a server that
has the same computer name, and Domain, Organization, and Site name as the original.
If these conditions are not met, the recovery will not be successful. Even if the only
Directory Store backup available is of the original Directory Store, restore it, and then
backfill changes from another server in the site.
If you purchased Intelligent Disaster Recovery, see “About Microsoft Exchange recovery
notes” on page 1536 for directions on using Intelligent Disaster Recovery to recover your
Exchange server.
To perform disaster recovery for Exchange Server 5.5
1. Recover the Windows server first.
For instructions, see “Returning to the last known good configuration” on page 655.
Make sure you restore the Exchange Server files that existed on all disk partitions.
When the Windows server disaster recovery procedure is complete (after the last
reboot), recover the Exchange server.
2. Do one of the following:
This step is necessary because the Microsoft Exchange Directory service may pause
when there is no database to use because you have not restored it yet. However, if you
have tools that can kill a process such as KILL or PVIEWER, then kill the
DSAMAIN.EXE process and go to step 4 on page 1284.
■ For Windows 2000, click Start, point to Settings, and then click Control Panel.
Double-click Administrative Tools, and then double-click Services. Right-click
Microsoft Exchange Directory service, and then click Properties. On the
General tab, under Startup, click Disabled, and then click OK.
1283

Disaster recovery for Exchange Server 5.5
■ For Windows NT, click Start, point to Settings, and then click Control Panel, and
then double-click Services. Double-click Microsoft Exchange Directory service,
change the Startup Type to Disabled, and then click OK.
3. Restart the computer.
Upon reboot, a message is displayed stating that not all services could be started.
4. Double-click the Microsoft Exchange Directory service, and then change the
Startup Type to Automatic.
5. Click OK.
6. Verify that the Exchange System Attendant service is started.
7. Start Backup Exec.
8. Catalog the tapes that contain the latest full, incremental, and differential backups
of the Exchange Stores you want to recover.
9. On the navigation bar, click the arrow next to Restore.
10. Click Restore.
11. On the Properties pane, under Source, click Selections.
12. On the restore selections list, select the latest full backups of the Directory and
Information Stores for restore.
13. Select all subsequent incremental Directory and Information Store backups.
If differential backups are to be restored, only the last differential Directory and
Information Store backups (the newest) need to be selected.
14. On the Properties pane, under Settings, click Microsoft Exchange.
15. Check Restore public folder and Restore private mailboxes.
16. Uncheck No loss restore (do not delete existing transaction logs).
17. Start the restore job.
18. After the restore has completed, insert the Microsoft Exchange Server installation
CD into the CD-ROM drive, open a command window, and copy the contents of the
\setup\your processor type\bootenv directory on the Exchange CD to the
\exchsrvr\mtadata directory on your hard drive:
1284 Administrator’s Guide

Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
Disaster recovery for Exchange Server 5.5
For example, assuming your Exchange installation is on drive C, your CD-ROM drive
is drive D, and your processor type is Intel, you would type the following in a
command window:
copy d:\setup\i386\bootenv\*.* c:\exchsrvr\mtadata
Note If you use File Manager or Windows Explorer to copy the files, you must remove
the READ ONLY file attribute from the files after you copy them. If you do not
remove this file attribute, the Microsoft Exchange Message Transfer Agent service
will not start.
19. Using a command window, execute the following:
\EXCHSRVR\BIN\ISINTEG -PRI -test mailbox, message, folder
\EXCHSRVR\BIN\ISINTEG -PUB -test mailbox, message, folder
\EXCHSRVR\BIN\MTACHECK
If these diagnostics report errors, refer to your Exchange documentation regarding
these utilities.
20. Do one of the following:
For Windows 2000 ◆ Click Start, point to Settings, and then click Control Panel.
21. Start ALL of the Exchange services that have Automatic as a Startup Type.
This should include:
■ Microsoft Exchange Directory
■ Microsoft Exchange Information Store
■ Microsoft Exchange Message Transfer Agent
■ Microsoft Exchange System Attendant
◆ Double-click Administrative Tools, and then double-click
Services.
For Windows NT ◆ Click Start, point to Settings, and then click Control Panel.
◆ Double-click Services.
22. After the Exchange server is back online, it is recommended that you use the
Exchange Administrator to run the Directory Store/Information Store (DS/IS)
consistency adjuster in order to resolve any inconsistencies. Results of the
consistency adjustment can be found in the Windows Event Log.
1285

Disaster recovery for Exchange Server 5.5
For more information about the DS/IS consistency adjuster, refer to your Microsoft
Exchange Server documentation.
23. After completing the restore, it is recommended that a full backup of the restored
databases be performed.
1286 Administrator’s Guide

Appendix
Symantec Backup Exec Agent
for Microsoft SharePoint
Portal Server
K
The Symantec Backup Exec Agent for Microsoft SharePoint Portal Server (SharePoint
Agent) is an optional, add-on component to Backup Exec for Windows Servers. The
SharePoint Agent enables network administrators to perform backup and restore
operations on SharePoint Portal Server installations that are connected to a network.
SharePoint backups can be integrated with network backups without separate
administration or dedicated hardware.
The SharePoint Agent supports installations of the following items:
■ SharePoint Portal Server 2001
■ SharePoint Portal Server 2003
■ Windows SharePoint Services 2.0
Related Topics:
“Using the SharePoint Agent with SharePoint Portal Server 2001” on page 1289
“Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows
SharePoint Services” on page 1299
1287

Requirements for the SharePoint Agent
Requirements for the SharePoint Agent
The SharePoint Agent has the following requirements:
■ The SharePoint Agent must be installed on the media server.
■ The Backup Exec Remote Agent for Windows Systems (Remote Agent) must be
installed on each remote SharePoint Portal Server that will be protected. In addition,
for SharePoint Portal Server 2003, the Remote Agent must be installed on each SQL
server in the server farm.
■ The credentials specified by the logon account used for backing up and restoring
SharePoint Portal Server data must have local administrative rights on the servers
where SharePoint components are installed. Additionally, to back up and restore
individual documents in workspaces or backward-compatible document libraries, the
account must be granted the Coordinator role in SharePoint on all folders to be
accessed in the workspace or document library.
For more information on granting permissions on folders in the workspace or
backward-compatible document libraries, see your SharePoint Portal Server
documentation.
■ The credentials specified by the logon account used for backing up and restoring the
Single Sign-on database must be either the account name or a member of the group
that is specified in the "Account name" field in the Single Sign-on Settings section of
the Manage Settings for Single Sign-on administration page in SharePoint Portal
Server.
■ Internet Information Services (IIS) rights can affect database backups and restores.
Ensure that the logon account used for backup and restore has rights to access the
IIS sites. Integrated Windows Security should be enabled within the IIS rights.
Installing the SharePoint Agent
The SharePoint Agent must be installed on the media server. If Backup Exec is not
already installed, see “Installing Backup Exec” on page 71.
To install the SharePoint Agent, see “Installing Backup Exec options to the local
computer” on page 85.
To install the Remote Agent, see “Installing Backup Exec options to remote computers”
on page 92.
1288 Administrator’s Guide

Using the SharePoint Agent with SharePoint Portal Server 2001
Using the SharePoint Agent with SharePoint Portal Server
2001
You can back up and restore the SharePoint Portal Server, an entire SharePoint
workspace, or the individual documents that are contained in the SharePoint
workspaces. If you choose to back up the individual documents, you can quickly restore
them without restoring the entire SharePoint Portal Server.
When you are backing up the SharePoint Portal Server, the SharePoint Agent includes
the following data in the backup:
■ Microsoft Web Storage System files
■ Microsoft Search Service (MSSearch) system resources, which include the property
store, subscriptions store, full-text index files, and propagated indexes
■ SharePoint Portal Server configuration information, including Web Storage System
configuration information, content source information, server properties, and access
accounts
■ The Applications folder, which contains a subfolder for each workspace on the server
■ Shortcuts or content sources that reference the local file system
■ Individual documents that are contained in the workspaces
SharePoint Agent does not back up the following data:
■ Content source crawls (a content source is a URL that SharePoint Portal Server uses
as a starting point to search, or crawl, for content in documents stored outside the
workspace) scheduled using Microsoft Windows 2000 Scheduled Tasks
■ Scheduled tasks for processing subscriptions
■ Gatherer logs
■ Lotus Notes configuration information
For more information about the various types of data stored on SharePoint Portal Server,
see your Microsoft SharePoint Portal Server documentation.
Note SharePoint Portal Server is available only for Windows 2000.
Related Topics:
“Requirements for the SharePoint Agent” on page 1288
“Installing the SharePoint Agent” on page 1288
“Backing up SharePoint Portal Server 2001” on page 1290
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint Portal Server
1289

Using the SharePoint Agent with SharePoint Portal Server 2001
“About restoring SharePoint Portal Servers and SharePoint Portal workspaces” on
page 1291
“Redirecting SharePoint Portal Server restore jobs” on page 1294
“Disaster recovery of a SharePoint Portal Server” on page 1297
Backing up SharePoint Portal Server 2001
There are no SharePoint-specific options to configure when you back up SharePoint
Portal Server 2001.
When backing up SharePoint Portal Server 2001, a full backup will be performed, which
backs up the entire SharePoint Portal Server database and all relevant data from other
dependent data stores.
Related Topics:
“Creating a backup job by setting job properties” on page 349
Backing up the SharePoint Portal Server database
To back up the SharePoint Portal Server database
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. From the Backup Selections pane, under Local Selections, select Microsoft
SharePoint Portal Server. If SharePoint Portal Server is installed remotely, expand
Remote Selections and then browse to the server where SharePoint Portal Server is
installed.
4. Start the backup job or select other backup options from the Properties pane.
1290 Administrator’s Guide

Using the SharePoint Agent with SharePoint Portal Server 2001
Backing up folders and documents from a SharePoint Portal
workspace
You can back up the individual documents that are contained in the SharePoint Portal
Workspace, which will enable you to quickly restore individual documents without
restoring the entire SharePoint Portal Server database.
To back up folders and documents from a SharePoint Portal workspace
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. From the Backup Selections pane, under Local Selections, expand Microsoft
SharePoint Portal Workspaces. If SharePoint Portal Server is installed remotely,
expand Remote Selections.
4. Select the folders and/or documents in the workspace that you want to back up.
5. Start the backup job or select other backup options from the Properties pane.
About restoring SharePoint Portal Servers and SharePoint Portal
workspaces
You can restore the entire SharePoint Portal Server or the individual documents that are
contained in the SharePoint Portal Workspaces if the documents were backed up
separately. You can redirect the restore of a SharePoint Portal Server to a different server
than the one from which it was backed up. In addition, you can redirect the restore of
SharePoint Portal Workspaces to an alternate workspace or file share.
There are some limitations on what information can be restored in SharePoint Portal
workspaces. The Microsoft SharePoint Portal Workspaces interface in Backup Exec is
intended to provide backup and restore of individual documents stored in the Documents
subfolder for each workspace and should not be used as a substitute for SharePoint
Portal Server database backup. Many of the other files and folders contained in the
workspace are controlled by the SharePoint Portal Server software and may not restore
successfully into the workspace even though they are available for backup. In addition,
when restoring individual documents, the creation date and modification date properties
do not restore.
Note SharePoint Portal Server must be installed on the target server before you can
restore a SharePoint Portal Server.
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint Portal Server
1291

Using the SharePoint Agent with SharePoint Portal Server 2001
Related Topics:
“Restoring data by setting job properties” on page 488
Restoring a SharePoint Portal Server
Caution When you restore a SharePoint Portal Server database, all SharePoint data on
the target server is overwritten.
To restore a SharePoint Portal Server
1. Place the media containing the data you want to restore in the storage device.
2. On the navigation bar, click the arrow next to Restore.
3. Click New Restore Job.
4. Navigate to and select the SharePoint Portal Server database you want to restore.
5. On the Properties pane, set the appropriate options.
6. Start the restore job.
Restoring a SharePoint Portal workspace
Individual SharePoint documents are always restored to SharePoint workspaces as
checked out to the credentials specified by the logon account used for the restore. The
documents must be checked in or published by that user before others can use them.
If you try to restore over a document that is published or checked in, the restore will fail.
If you try to restore over a document that is checked out, the restore will fail if the
document is checked out to a user that differs from the logon account credentials used
for the restore.
Previous versions of individual documents that existed when the documents were backed
up are not preserved when they are restored into a workspace, and the document
versions are reset. The only way to preserve version history for documents is to restore
the entire SharePoint Portal Server database.
Documents that exist in the target location may be overwritten by the restore depending
on the overwrite properties for the restore job. If an existing document is overwritten,
then the version history for that document is lost as well.
1292 Administrator’s Guide

To restore SharePoint Portal workspace data
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
Using the SharePoint Agent with SharePoint Portal Server 2001
3. Navigate to and select the SharePoint workspace data you want to restore.
4. On the Properties pane, set the appropriate options.
5. Start the restore job.
Related Topics:
“Backing up folders and documents from a SharePoint Portal workspace” on page 1291
“Redirecting SharePoint Portal Server restore jobs” on page 1294
Restoring previous versions of documents from workspace
backups
The SHADOW folder, at the root of the workspace, contains previous versions of the
documents that exist in the workspace at the time of backup. If you select the SHADOW
folder to include in a workspace backup, you can have access to the previous versions of
the documents in the workspace. However, you cannot restore the previous versions
directly back into the workspace. You must restore them to an alternate location and
then manually copy them into the workspace.
To restore previous versions of documents from workspace backups
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Navigate to the backup sets that contain the workspace data from which you want to
restore.
4. Under the backup set, expand the SHADOW folder and then navigate to the folder
that contains the documents you want to restore.
5. Proceed with the steps in “Redirecting restored workspace data to a file path” on
page 1296.
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint Portal Server
1293

Using the SharePoint Agent with SharePoint Portal Server 2001
Redirecting SharePoint Portal Server restore jobs
Before redirecting the restore of a SharePoint Portal Server database, the SharePoint
Portal Server software must be installed on the target server.
Caution When you restore a SharePoint Portal Server database, all SharePoint data on
the target server is overwritten.
To redirect a SharePoint Portal Server restore job
1. Place the media containing the data you want to restore in the storage device.
2. On the navigation bar, click the arrow next to Restore.
3. Click New Restore Job.
4. Navigate to and select the SharePoint Portal Server database you want to restore.
5. On the Properties pane, under Destination, click Microsoft SharePoint Redirection.
6. Under SharePoint Portal Server 2001, select the Redirect SharePoint Portal Server
2001 sets check box.
7. In the Restore to server field, enter the name of the SharePoint server to which you
are restoring. Use the following format: \\servername.
8. Use the default logon account as indicated, or click Change to select a different one.
9. On the Properties pane, select other job properties that might be appropriate for
your environment.
10. Start the restore job.
After the restore completes, it is recommended that you perform a full backup of the
restored SharePoint Portal Server databases.
Related Topics:
“Backing up SharePoint Portal Server 2001” on page 1290
“Restoring a SharePoint Portal Server” on page 1292
1294 Administrator’s Guide

Using the SharePoint Agent with SharePoint Portal Server 2001
Redirecting restored workspace data to another workspace
Before redirecting the restore of SharePoint Portal workspace data, the SharePoint Portal
Server software must be installed on the target server. If any of the folders in the original
workspace do not exist in the destination workspace, they will be created during the
restore.
Caution When you restore SharePoint Portal workspace data, any documents that exist
in the target location and that have the same name as the documents being
restored may be overwritten, depending on the overwrite properties for the
restore job.
To redirect restored workspace data to another workspace
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Navigate to and select the SharePoint Portal workspace data you want to restore.
4. On the Properties pane, under Destination, click Microsoft SharePoint Redirection.
5. Select the Redirect SharePoint document sets check box, and then select Redirect
to workspace or document library (Web Storage System-based only).
6. In the Restore to server field, type the name of the SharePoint server to which you
are restoring. Use the following format: \\servername.
7. In the Restore to workspace or document library field, type the name of the
workspace to which you are restoring. If you have not yet created the workspace, you
must do so before starting the restore operation.
8. Use the default logon account as indicated, or click Change to select a different one.
9. On the Properties pane, select other job properties that might be appropriate for
your environment.
10. Start the restore job.
Related Topics:
“Backing up folders and documents from a SharePoint Portal workspace” on page 1291
“Restoring a SharePoint Portal workspace” on page 1292
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint Portal Server
1295

Using the SharePoint Agent with SharePoint Portal Server 2001
Redirecting restored workspace data to a file path
To redirect restored workspace data to a file path
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Navigate to and select the SharePoint Portal Server data you want to restore.
4. On the Properties pane, under Destination, click Microsoft SharePoint Redirection.
5. Select the Redirect SharePoint document sets check box, and then select Redirect
to path.
6. In the Restore to drive and Restore to path fields, enter the drive letter and path to
which you want to direct the restore, or click the ellipsis (...) button to browse to the
location.
You can also enter a UNC path (\\servername\share) in the Restore to drive field.
7. Use the default logon account as indicated, or click Change to select a different one.
8. On the Properties pane, select other job properties that might be appropriate for
your environment.
9. Start the restore job.
Related Topics:
“Backing up folders and documents from a SharePoint Portal workspace” on page 1291
“Restoring a SharePoint Portal workspace” on page 1292
1296 Administrator’s Guide

Using the SharePoint Agent with SharePoint Portal Server 2001
Disaster recovery of a SharePoint Portal Server
Because SharePoint Portal Server uses Windows 2000 security for authentication,
disaster recovery of a SharePoint Portal Server cannot be separated from the disaster
recovery of Windows 2000.
If you purchased the Intelligent Disaster Recovery (IDR) option, see “Symantec Backup
Exec Intelligent Disaster Recovery Option” on page 1501 for directions on using IDR to
recover a Windows 2000 server. For specific notes on using IDR with SharePoint Portal
Server, see “About SharePoint Portal Server recovery notes” on page 1537.
You must recover the Windows 2000 server first. For more information, see “Manual
disaster recovery of Windows computers” on page 658. After recovery of the Windows
2000 server is complete (after the last reboot), the SharePoint Portal Server software is
installed but is not functional. You must remove SharePoint Portal Server and then
reinstall it before the SharePoint data can be restored.
Always log on to the Windows 2000 server using the Administrator account (or an
Administrator equivalent) during disaster recovery. You need:
■ A copy of Backup Exec for Windows Servers with the SharePoint Agent installed
■ The latest backup of the SharePoint Portal Server you want to recover
■ The SharePoint Portal Server CD
■ Any SharePoint Portal Server service packs that were applied to the original
installation
Caution You cannot completely recover a SharePoint Portal Server database using
backups of individual workspaces. You must use a backup of the SharePoint
Portal Server database to complete the disaster recovery.
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint Portal Server
1297

Using the SharePoint Agent with SharePoint Portal Server 2001
Uninstalling and reinstalling the SharePoint Portal Server
software
To uninstall and reinstall the SharePoint Portal Server software
1. Use Add/Remove Programs in the Windows Control Panel to uninstall the
SharePoint Portal Server software. Restart the server when the uninstall operation
completes.
2. Insert the SharePoint CD and install the SharePoint Portal Server software using the
appropriate options for your environment. When the New Workspace Wizard starts,
click Cancel.
3. If applicable, install any SharePoint Portal Server service packs that were applied to
the original installation.
Best practices for SharePoint Portal Server 2001
Symantec recommends the following practices for SharePoint Portal Server 2001.
■ Perform full backups of Microsoft SharePoint Portal Server 2001, in addition to
individual workspace backups. Even though workspace backups may be more useful
for granular recovery of individual documents on a day-to-day basis, you must have a
full backup to complete a disaster recovery.
■ Keep a record of all service packs and hotfixes that are installed on the SharePoint
server when you perform backups. SharePoint restores may not complete
successfully if the databases were backed up at a different patch level.
■ Ensure that the SHADOW folder is included in your selections when you back up
workspace data. This folder contains previous versions of the current documents
that exist in the workspace at the time of backup. While these previous versions
cannot be restored directly into that workspace, it is possible to restore them to an
alternate location, provided that the SHADOW folder is protected.
1298 Administrator’s Guide

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
Using the SharePoint Agent with SharePoint Portal Server
2003 and Windows SharePoint Services
You can use the SharePoint Agent to back up and restore SharePoint Portal Server 2003
farm components, which include:
■ Configuration database
■ Portal sites and their associated databases
■ Content database
■ User Profile database
■ Services database
■ Index databases
■ Team databases
■ Windows SharePoint Services sites and their associated databases
■ Single Sign-on database
■ Document Library Store (Web Storage System-based)
■ Document Libraries (Web Storage System-based)
■ Individual documents can be backed up from and restored to Web Storage
System-based document libraries, or redirected to file paths.
■ Document Libraries / Picture Libraries (Microsoft SQL Server based)
■ Individual documents can be restored from full database backups.
In addition, you can back up and restore Windows SharePoint Services components,
which include:
■ Configuration database
■ Team sites and their associated Content database
■ Document Libraries / Picture Libraries (Microsoft SQL Server based)
■ Individual documents can be restored from full database backups.
Selecting SharePoint resources for backup
Backup Exec provides a hierarchical tree view of SharePoint resources in two locations in
the Selection tree:
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint Portal Server
1299

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
■ In the selection tree, a node titled Microsoft SharePoint Server Farms displays a
logical view of the topology of each SharePoint server farm on your network. Backup
Exec automatically discovers SharePoint farms when you browse to a SharePoint
front-end Web server and adds the farms to this node. Additionally, you can add
farms manually using the Add Server Farm menu option.
■ A node titled Microsoft SharePoint Resources displays for any server that has locally
installed SharePoint resources. For single-server SharePoint deployments, all of the
SharePoint resources are listed and are selectable for backup. For SharePoint server
farm deployments, this node lists only the SharePoint resources that reside locally
on this server and that can be selected for backup from this node. On front-end Web
servers, this node lists the entire farm topology, but only the resources that reside
locally can be selected for backup.
Adding a server farm to the backup selections list
If a farm that you want to back up does not display under the Microsoft SharePoint
Server Farms node on the Backup Job Properties dialog box, you can manually add that
farm to the list.
To add a server farm to the backup selections list
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. In the selection tree, right-click Microsoft SharePoint Server Farms and then click
Add Server Farm.
4. In the Web server name field, type the name of a Web server that belongs to the farm
you want to add.
5. In the Server farm name field, type a name for the farm or use the default name. The
name you type here will display under the Microsoft SharePoint Server Farms node.
Backup Exec lists the names of discovered Web servers in parentheses after the
server farm name in the Selection tree.
The following characters cannot be used in farm names: ` ~ ^ * ( ) { } \ ; : ’ " , < > / ?
6. Click OK.
Backup Exec adds the new server farm to the Microsoft SharePoint Server Farms
node under Backup Exec Agents and contacts the specified Web server to retrieve the
remainder of the farm topology.
1300 Administrator’s Guide

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
When you create jobs to protect the SharePoint resources for the server farm, make
backup selections from this server farm node. In addition, back up the default
Microsoft SQL databases (master, model, msdb, pubs) for each Microsoft SQL
instance that hosts SharePoint databases.
Please note that after a server farm is added to Microsoft SharePoint Server Farms,
the SharePoint databases hosted on Microsoft SQL instances can no longer be
selected for backup directly from the Microsoft SQL Server resource nodes.
If you change the SharePoint server farm topology after it has been added to
Microsoft SharePoint Server Farms, you must browse the server farm node so that
Backup Exec can recognize and save the changes.
Disabling or enabling communication between a Web server and
Backup Exec
Backup Exec communicates with the Web servers that participate in SharePoint server
farms to discover the farm topology. This process may take some time if Backup Exec
attempts to communicate with a Web server that is unavailable. If you know that a
particular Web server in a farm will be unavailable for a period of time, you can disable
the communication between the Web server and Backup Exec.
To disable or enable communication between a Web server and Backup Exec
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. In the selection tree, right-click Microsoft SharePoint Server Farms, and then click
Manage Server Farms.
4. Select the farm that contains the Web server you want to disable or enable, and then
click Properties.
5. To prevent Backup Exec from communicating with a Web server, clear the check box
next to that Web server’s name. If the Web server is now available to communicate
with Backup Exec, select the check box next to the Web server’s name.
When you disable communication with a Web server, Backup Exec removes the name
of that Web server from the server farm name under the Microsoft SharePoint
Server Farms node.
6. Click OK, and then click Close.
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint Portal Server
1301

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
Changing the name of a farm
When Backup Exec adds a farm, it creates a default name for the farm. You can change
the default farm name to a name that is meaningful to you.
To change the name of a farm
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. In the selection tree, right-click Microsoft SharePoint Server Farms, and then click
Manage Server Farms.
4. Select the farm whose name you want to change, and then click Properties.
5. Type the new farm name in the Server farm name field. Then name you type here
will display under the Microsoft SharePoint Server Farms node. Backup Exec lists
the names of discovered Web servers in parentheses after the server farm name in
the Selection tree.
The following characters cannot be used in farm names: ` ~ ^ * ( ) { } \ ; : ’ " , < > / ?
6. Click OK, and then click Close.
Deleting a farm from the Microsoft SharePoint Server Farms
node
If a server farm is no longer in use or is no longer valid, you can remove it from the
Microsoft SharePoint Server Farms node.
Note If Backup Exec is installed on the same server that is used as a Web server in a
farm, you cannot delete that farm.
To delete a farm from the Microsoft SharePoint Server Farms node
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. In the selection tree, right-click Microsoft SharePoint Server Farms, and then click
Manage Server Farms.
1302 Administrator’s Guide

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
4. Select the farm you want to delete, and then click Delete.
Backing up SharePoint resources
Each portal site will have a minimum of three databases: Content databases, Services
databases, and User Profile databases. Symantec recommends that you back up these
databases together.
To back up SharePoint resources
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. Select the SharePoint resources you want to back up. For information about selecting
SharePoint resources, see “Selecting SharePoint resources for backup” on page 1299.
4. On the Properties pane, under Settings, select Microsoft SharePoint.
5. Select the appropriate options as follows:
Backup method: ◆ Full - Back up entire database. Select this to back up the entire
database.
◆ Differential - Back up database changes only. Select this to
back up only the changes made to the database since the last
full backup.
Note The differential backup method cannot be used to back up
Index databases or Document Libraries. The Full backup
method will be used to back up these resources.
Enable the restore of
individual documents
from the database backup
(available for full backups
only)
Perform consistency
check before backup of
Microsoft SQL databases
used by Microsoft
SharePoint
Continue with backup if
consistency check fails
Check this option to enable the restore of individual documents
from database backups. This option is only available when
performing full backups. The option will be grayed out if
Differential - Back up database changes only has been selected as
the backup method.
Check this option to run a full consistency check (including
indexes) of the Microsoft SQL databases used by Microsoft
SharePoint before backing up the databases.
Check this option to continue with the backup operation even if
the consistency check fails.
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint Portal Server
1303

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
6. Start the backup job or select other backup options from the Properties pane.
About selecting SharePoint resources for restore
Backup Exec provides the following hierarchical tree views of SharePoint resources in
the Selections tree when using the Resource View:
Hierarchical tree view
Node name Node description
Server Farm node This node represents a logical view of the topology for the SharePoint
resources that have been backed up from the farm. The name that
displays for this node matches the name you defined for the server
farm in Backup Selections under the Microsoft SharePoint Server
Farms node. If you expand the nodes for each SharePoint component
that appears in this view, the backup sets for that component are
displayed and can be selected for restore.
Individual Server nodes Each server from which SharePoint components were backed up
contains a Microsoft SharePoint Resources node. This node will
display the SharePoint components that resided locally on the server
when they were backed up. If you expand the nodes for each
SharePoint component that appears in this view, the backup sets for
that component are displayed and can be selected for restore.
Restoring SharePoint resources
You can restore the following resources:
■ Portal sites and their associated databases: each portal site will have a minimum of
three databases: Content databases, Services databases, and User Profile databases.
Symantec recommends that you restore these databases together.
■ Windows SharePoint Services sites and their associated databases
■ Document library stores (Web Storage System-based)
■ Individual documents that are contained in Document or Picture libraries (Web
Storage System-based or Microsoft SQL Server-based)
■ Configuration databases: the Configuration database contains all of the
configuration information for the entire SharePoint Server farm. Use caution when
restoring this database because any changes made to the farm topology after the
backup from which you are restoring will be lost. For more information, refer to the
Microsoft SharePoint Portal Server 2003 documentation.
1304 Administrator’s Guide

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
■ Single sign-on databases: you can restore Configuration databases and Single
Sign-on databases back to the original location only.
To restore SharePoint resources
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Select the full and differential backup sets that correspond to the SharePoint data
you want to restore.
If you restore the SharePoint resources for a portal site in one job, the Index database
is restored last. If you are restoring in separate jobs, you must restore the Index
database last.
4. On the Properties pane, under Settings, select Microsoft SharePoint.
5. To bring the databases online, verify that the Bring restored databases online and
reconnect previous database links check box is selected. When restoring portal sites
or Windows SharePoint Services sites, this option also re-establishes the link
between the restored databases and their corresponding sites.
If you are restoring full or differential backup sets in separate restore jobs, clear this
option for all jobs except the last job. You should select the option for the last restore
job in the sequence. Also, you may be prompted to insert media that you have
already used.
6. Set additional restore options on the Properties pane or start the restore job.
Related Topics:
“Redirecting a restore job for SharePoint” on page 1308.
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint Portal Server
1305

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
Restoring SharePoint document libraries (Web storage
system-based)
Individual SharePoint documents are always restored to SharePoint document libraries
as checked out to the credentials specified by the logon account used for the restore. The
documents must be checked in or published by that user before others can use them.
If you try to restore over a document that is published or checked in, the restore will fail.
If you try to restore over a document that is checked out, the restore will fail if the
document is checked out to a user that differs from the logon account credentials used
for the restore.
To restore SharePoint document libraries (Web storage system-based)
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Select the SharePoint Document Library data you want to restore.
4. Set additional restore options on the Properties pane or start the restore job.
Restoring previous versions of documents from document library
(Web storage system-based) backups
The SHADOW folder, at the root of the Document Library, contains previous versions of
the documents that existed in the Document Library at the time of backup. If you select
the SHADOW folder to include in a Document Library backup, you can have access to the
previous versions of the documents. However, you cannot restore the previous versions
directly back into the Document Library. You must restore them to an alternate location
and then manually copy them into the Document Library.
To restore previous versions of documents from document library (Web storage
system-based) backups
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Navigate to the SharePoint Document Library that contains the documents you want
to restore.
4. Under the backup set, expand the SHADOW folder and then select the documents
you want to restore.
1306 Administrator’s Guide

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
5. Proceed to “Redirecting the restore of individual documents to a file path” on
page 1310".
Restoring individual documents (Microsoft SQL Server-based)
from full database backups
You can restore individual documents and images from full SharePoint database backup
jobs if you selected the following option during the backup job:
Enable the restore of individual documents from the database backup (available for full
backups only).
The option to enable the restore of individual documents is not available for differential
backup jobs.
Restore jobs from disk-based backups take less time to process than restore jobs from
tape-based backups. If you restore from a tape-based backup, you must specify a path on
the media server for Backup Exec to use as a temporary staging location for data.
To restore individual documents from full database backups
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Navigate to the backup set for the appropriate content database, and then select the
documents or images that you want to restore.
4. On the Properties pane, under Settings, click Microsoft SharePoint.
5. Do one of the following:
To replace existing Check Restore over existing documents (applies to SQL based
documents with
document libraries only).
documents of the same
name from the restore job
To prevent the
replacement of existing
files with files of the
same name from the
restore job.
Uncheck Restore over existing documents (applies to SQL based
document libraries only).
6. If you are restoring from tape, do the following steps:
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint Portal Server
1307

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
■ On the Properties pane, under Settings, select Advanced.
■ Specify the path for a temporary staging location in the option titled Path on
media server for staging temporary restore data when restoring individual items
from tape.
The path must reside on the Backup Exec media server. Symantec recommends
that you avoid using system volumes for temporary staging locations.
7. Set additional restore options on the Properties pane, or start the restore job.
Redirecting a restore job for SharePoint
Follow these steps to redirect a restore job to an existing site on a Web server in a farm.
To redirect a restore job for SharePoint
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Select the SharePoint resources you want to restore.
You can restore Configuration databases and Single Sign-on databases back to the
original location only.
4. On the Properties pane, under Settings, select Microsoft SharePoint Redirection.
5. Under SharePoint Portal Server 2003, select Redirect SharePoint Portal Server
2003 sets.
6. In the Restore to site field, type the URL of the site to which you want to restore the
data. For example, http://portalsite1 or https://portalsite1
In order to restore to a site, the site must already exist.
7. In the Using Web server field, type the name of the Web server on which the site
resides.
You must create the target SharePoint Portal Server 2003 portal site or Windows
SharePoint Services site on the specified Web server with the same database
structure as the source site before running the restore job.
1308 Administrator’s Guide

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
8. To bring the databases online, verify that the Bring restored databases online and
reconnect previous database links option is selected. When restoring portal sites or
Windows SharePoint Services sites, this option also re-establishes the link between
the restored databases and their corresponding sites.
If you are restoring full or differential backup sets in separate restore jobs, clear this
option for all jobs except the last job. You should select the option for the last restore
job in the sequence. You may be prompted to insert media that you have already
used.
9. Use the default logon account as indicated, or click Change to select a different one.
10. Set additional restore options on the Properties pane, or start the restore job.
Redirecting the restore of document library (Web storage
system-based) data to another document library
Before redirecting the restore of SharePoint Portal document library data, the SharePoint
Portal Server software must be installed on the target server. If any of the folders in the
original document library do not exist in the destination document library, they will be
created during the restore.
Caution When you restore SharePoint Portal document library data, any documents
that exist in the target location and that have the same name as the documents
being restored may be overwritten, depending on the overwrite properties for
the restore job.
To redirect the restore of document library data to another document library
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Navigate to and select the SharePoint Portal document library data you want to
restore.
4. On the Properties pane, under Destination, click Microsoft SharePoint Redirection.
5. Select the Redirect SharePoint document sets check box, and then select Restore to
workspace or document library (Web Storage System-based only).
6. In the Restore to server field, type the name of the SharePoint server to which you
are restoring. Use the following format: \\servername.
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint Portal Server
1309

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
7. In the Restore to workspace or document library field, type the name of the
document library to which you are restoring. If you have not yet created the
document library, you must do so before starting the restore operation.
8. Use the default logon account as indicated, or click Change to select a different one.
9. On the Properties pane, select other job properties that might be appropriate for
your environment.
10. Start the restore job.
Redirecting the restore of individual documents to a file path
To redirect individual documents to a file path
1. Place the media containing the data you want to restore in the storage device.
2. On the navigation bar, click the arrow next to Restore.
3. Click New Restore Job.
4. Navigate to and select the SharePoint documents that you want to restore.
5. On the Properties pane, under Destination, click Microsoft SharePoint Redirection.
6. Select the Redirect SharePoint document sets check box, and then select Redirect
to path.
7. In the Restore to drive and Restore to path fields, enter the drive letter and path to
which you want to direct the restore, or click the ellipsis (...) button to browse to the
location.
You can also enter a UNC path (\\servername\share) in the Restore to drive field.
8. Use the default logon account as indicated, or click Change to select a different one.
9. On the Properties pane, select other job properties that might be appropriate for
your environment.
10. Start the restore job.
1310 Administrator’s Guide

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
Setting default options for SharePoint Portal Server 2003
To set default options for SharePoint Portal Server 2003
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Microsoft SharePoint.
3. Select the appropriate options as necessary:
Backup method ◆ Full - Back up entire database. Select this to back up the
entire database.
◆ Differential - Back up database changes only. Select this to
back up only the changes made to the database since the last
full backup.
Note The differential backup method cannot be used to back up
Index databases or Document Libraries. The Full backup
method will be used to back up these resources.
Enable the restore of
individual documents
from the database backup
(available for full backups
only)
Perform consistency
check before backup of
Microsoft SQL databases
used by Microsoft
SharePoint
Continue with backup if
consistency check fails
Bring restored databases
online and reconnect
previous database links
Restore over existing
documents (applies to
SQL based document
libraries only
Select this option to enable the restore of individual documents
from database backups. This option is only available when
performing full backups. The option will be grayed out if
Differential - Back up database changes only has been selected as
the backup method.
Select this option to run a full consistency check (including
indexes) of the Microsoft SQL databases used by Microsoft
SharePoint before backing up the database.
Select this option to continue with the backup operation even if
the consistency check fails.
Select this option to bring the databases online after a restore job.
When restoring portal sites or Windows SharePoint Services sites,
this option also re-establishes the link between the restored
databases and their corresponding sites.
Check Restore over existing documents to replace existing
documents with documents of the same name in the restore job.
If document versioning is enabled for the existing Document or
Picture library, Backup Exec adds a new version of the document
instead of replacing the existing document.
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint Portal Server
1311

Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services
1312 Administrator’s Guide

Symantec Backup Exec
Agent for Lotus Domino
Server
Appendix
L
The Symantec Backup Exec for Windows Servers Agent for Lotus Domino Server (Lotus
Domino Agent) is installed as a separate, add-on component of Backup Exec for
Windows Servers.
The Lotus Domino Agent allows you to back up and restore Lotus Domino versions R7
and later databases and transaction logs on local media servers and on remote
computers. You can integrate Lotus Domino database backups with regular server
backups without separately administering them or using dedicated hardware.
The Lotus Domino Agent provides support for:
■ Full, incremental, and differential online backups of Lotus Domino databases and
transaction logs using Lotus Domino APIs.
■ Restores of Lotus Domino databases and transaction logs and point in time restores.
■ Recycling of Lotus Domino transaction logs after a successful backup.
■ Flexible scheduling capabilities.
■ Backup and restore of partitioned and clustered Lotus Domino servers.
■ Lotus Domino databases in a Microsoft Cluster Server cluster in both Active-Active
and Active-Passive configurations.
Related Topics:
“Installing the Lotus Domino Agent on the media server” on page 1315
1313

Lotus Domino Agent requirements
Lotus Domino Agent requirements
The Lotus Domino Agent supports Lotus Domino R7 and later.
Following are the requirements for backing up Lotus Domino database files residing on
the media server, or for remote Windows computers and workstations.
Note Backup Exec does not support two versions of Lotus Domino on the same
computer.
If the Lotus Domino files you want to back up are on the local media server, the server
must have:
■ Backup Exec for Windows Servers
■ An Intel-compatible processor
■ The Lotus Domino data directory on the Lotus Domino server
If the Lotus Domino files you want to back up are on a remote computer, the remote
computer must have:
■ Windows operating system
■ Backup Exec Remote Agent for Windows Servers
■ An Intel-compatible processor
■ Corresponding Windows Administrative Share for each volume that contains Lotus
Domino databases
■ The Lotus Domino data directory on the Lotus Domino server
Following are requirements for backing up Lotus Domino transaction logs:
■ Transaction logging must be enabled to perform differential and incremental
backups and to perform point in time recovery.
■ The Lotus Domino logging style must be set to archive if you want to back up the
transaction logs.
If the Lotus Domino databases are running in a Microsoft Cluster Server cluster:
■ Lotus Domino Server must be running on a Microsoft Cluster Server cluster. For
more information, see your Lotus Domino documentation for instructions for
setting up Lotus Domino in a Microsoft Cluster Server cluster.
■ The Backup Exec Lotus/Domino Agent must be installed on all nodes in the
Microsoft Cluster Server cluster.
Related Topics:
“Viewing and selecting Lotus Domino databases” on page 1316
1314 Administrator’s Guide

Appendix L, Symantec Backup Exec Agent for Lotus Domino Server
Installing the Lotus Domino Agent on the media server
Installing the Lotus Domino Agent on the media server
The Symantec Backup Exec Agent for Lotus Domino is installed locally as a separate,
add-on component of Backup Exec for Windows Servers, and can protect local or remote
Lotus Domino databases.
For instructions on installing the Lotus Domino Agent on the local media server, see
“Installing Backup Exec options to the local computer” on page 85.
For instructions on installing the Remote Agent on a remote resource, see “Installing
Backup Exec options to remote computers” on page 92.
For instructions on moving the Remote Agent to another remote Windows computer,
see “Using a command prompt to install the Remote Agent on a remote 32-bit computer”
on page 105.
Related Topics:
“Configuring default Lotus Domino options” on page 1318
“Backing up Lotus Domino databases” on page 1318
“Restoring Lotus Domino databases” on page 1323
1315

Viewing and selecting Lotus Domino databases
Viewing and selecting Lotus Domino databases
After installing the Lotus Domino Agent, you can view and select existing Lotus Domino
databases in the selections pane.
To view databases created while Backup Exec is running, select Refresh from the View
menu or press F5. To back up the newly-created database, select it from the volume
level, unless the entire volume is already selected for backup.
Note If the Lotus Domino databases are in a Microsoft Cluster Server cluster (MCSC),
the virtual computer name or the virtual IP address of the Domino server should
be used when browsing or submitting jobs in a MCSC environment.
To view Lotus Domino databases on the local server
1. On the navigation bar, click the arrow next to Backup
2. Click New Backup Job.
3. In the selections pane, expand Lotus Domino Databases. All of the Lotus Domino
data found on the local server is listed by volume under the Lotus Domino Databases
icon.
Lotus Domino Databases
Lotus Domino transaction logs do not appear under the Lotus Domino Databases;
however, when the database is selected for backup, the transaction logs will
automatically be included.
To select Lotus Domino databases
Lotus Domino Databases view
❖ Select the check box next to the volume to choose all of the databases in a volume, or
expand the volume and select specific folders and databases. When selecting
databases to back up, the databases must be local to the Lotus Domino server.
1316 Administrator’s Guide

Lotus Domino Database Selection
Appendix L, Symantec Backup Exec Agent for Lotus Domino Server
Viewing and selecting Lotus Domino databases
The following file types appear in the view for the Lotus Domino server:
■ filename.nsf - Lotus Domino database files
■ filename.ntf - Lotus Domino template files
■ filename.box - shared mail database
■ filename.dsk - cache files
You must back up all of these files in order to properly recover Lotus Domino
Databases.
Only database files appear under the Lotus Domino Databases view. Domino
Program files and other files such as.id and notes.ini appear in the volume in which
the Lotus Domino Program directory is located. They must be backed up separately
as part of a system backup.
To view Lotus Domino databases on remote computers
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Properties pane, under Source, click Selections.
4. Click Remote Selections, and then click Microsoft Windows Network.
5. If necessary, click the domain that contains the Lotus Domino installations, and then
click the computer in which the Lotus Domino database is located.
A list of shared network directories appears, along with an icon that represents the
Lotus Domino Databases.
Related Topics:
“Backing up Lotus Domino databases” on page 1318
“Restoring Lotus Domino databases” on page 1323
1317

Configuring default Lotus Domino options
“Preparing for disaster recovery on a Lotus Domino server” on page 1328
Configuring default Lotus Domino options
You can configure default settings for Lotus Domino databases for all new jobs you
create. When you create a job, you can use the default settings or modify the Domino
properties for the job.
To configure default Domino options for all new jobs
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Lotus Domino.
3. Select Lotus Domino backup default options. For more information, see the Backup
job properties for Lotus Domino databases table in the “Selecting backup options for
Lotus Domino databases” on page 1321.
4. Select Lotus Domino restore default options. For more information, see the Restore
job properties for Domino databases table in the “Selecting restore options for Lotus
Domino databases” on page 1326.
5. Click OK to save the options or select other options from the Properties pane.
Backing up Lotus Domino databases
When a Lotus Domino backup job is submitted, Backup Exec uses Lotus Domino APIs to
obtain the backup of the database. The transaction logs associated with the Lotus
Domino databases are automatically included in the backup and are stored in a separate
backup set within the Lotus Domino database backup set.
The Lotus Domino Agent supports the backup of the following types of files:
■ .ntf - Lotus Notes Template Files
■ .nsf - Lotus Notes Database Files
■ .box - Lotus Mailbox Files
■ .dsk - Cache Files
You must back up .nsf, .ntf, and .box files to properly recover Lotus Domino databases. If
you want to back up .njf, .ncf, .id, .dic, or notes.ini files, you must select them for backup
from the volume in which the Lotus Domino Program directory is located.
1318 Administrator’s Guide

Related Topics:
“About Lotus Domino transaction logs” on page 1320
“Selecting backup options for Lotus Domino databases” on page 1321
“Selecting restore options for Lotus Domino databases” on page 1326
Appendix L, Symantec Backup Exec Agent for Lotus Domino Server
Backing up Lotus Domino databases
Automatic exclusion of files during volume-level backups
If you select a volume that contains Lotus Domino data for backup, the Lotus Domino
Agent determines which Domino data should not be included in a volume level backup.
For example, .NTF and .NSF files, as well as any active log files, should not be part of the
backup because they are opened for exclusive use by the Lotus Domino system. These
files will be automatically excluded for backup by a feature called Active File Exclusion. If
this exclusion did not happen during a non-snapshot backup, these files would appear as
in use - skipped. If this exclusion did not happen during a snapshot backup, the files
would be backed up in a possible inconsistent state, which could create restore issues.
Supported Lotus Domino database configurations
You can back up the following types of Lotus Domino database configurations using the
Lotus Domino Agent:
■ Domino Server Databases. Domino Server databases can be Logged or Unlogged.
They are located in a folder in the Domino data directory, typically
Lotus\Domino\Data, but may also be linked to the Domino data directory using Lotus
Linked Databases.
■ Logged Domino Server Databases. A logged Domino Server database logs
transactions for one or more Lotus databases. If transaction logging is enabled
on the server, all database transactions go into a single transaction log.
■ Unlogged Domino Server Databases. An unlogged Domino Server database does
not have transaction logging enabled, or the transaction logging has been
disabled for specific server databases. Unlogged Domino Server databases will
be backed up in their entirety when a full, differential, or incremental backup is
performed, but the database can only be restored to the point of the latest
database backup.
■ Local Databases. Lotus databases are considered Local when they cannot be found in
the Domino data directory, cannot be shared, and cannot be logged. This type of
database requires a backup of the database itself when using any of the Lotus
Domino R7 backup methods. The database can be restored only to the point of the
latest database backup.
1319

Backing up Lotus Domino databases
About Lotus Domino transaction logs
Lotus Domino has the ability to log transactions for one or more Lotus Domino
databases. Lotus Domino databases are logged by default when transaction logging is
enabled on the Lotus Domino server and the database is in the Domino data directory.
When transaction logging is enabled on the server, each Lotus Domino database is
assigned a database instance ID (DBIID). Each transaction recorded in the log includes
the DBIID, which is used to match transactions to the database during a restore.
A new DBIID may be assigned to the database when some Lotus Domino operations are
performed. When the new DBIID is assigned, all new transactions recorded in the log use
the new DBIID; however, previous transactions have the old DBIID and will not match the
new DBIID for the database. To prevent data loss, it is recommended that a full backup be
performed when a database receives a new DBIID since transactions with the old DBIID
cannot be restored to the database. A full backup includes all current transactions on the
database and ensures that only the transactions with the new DBIID are needed to
restore the database.
You can select only one logging style when transaction logging is enabled on the server.
Following are the two styles of logging for Lotus Domino databases:
■ Archive logging. This logging style produces a transaction log that is limited only by
the capacity of your mass storage. Archive logging is the recommended logging style
to be used with the Lotus Domino Agent since all the transaction logs can be backed
up and marked for recycling. When the transaction logs are recycled the Lotus
Domino server reuses the existing transaction logs after they are backed up to create
space for new transaction logs.
■ Circular logging. This logging style reuses the log file after a specific log file size is
reached. By reusing the log file you are saving resources; however, you are also
limiting your recovery options because the database can only be recovered to the
point of the last full backup. If the incremental or differential backup method is
selected for a backup job, a full backup of the changed databases is performed since
transaction logs cannot be backed up.
Caution When circular logging is enabled, the circular transaction log cannot be backed
up, which could result in the loss of changes made to the database since the
last backup was performed.
1320 Administrator’s Guide

Appendix L, Symantec Backup Exec Agent for Lotus Domino Server
Selecting backup options for Lotus Domino databases
Selecting backup options for Lotus Domino databases
This procedure details how to select backup job properties for Lotus Domino databases
and provides definitions for Domino-specific backup options. You should back up Lotus
Domino databases during off-peak hours and disable Lotus Domino or third party Lotus
Domino agents before running the backup. The transaction logs will automatically be
included in the backup job.
For details on how to create a backup job, and for definitions of all other backup options
see “Creating a backup job by using the Backup Wizard” on page 347.
Caution All Lotus Domino databases and transaction logs that reside on single or
multiple volumes must be backed up by the same media server. In addition, you
should not back up a Lotus Domino server simultaneously from multiple
media servers.
To select backup job properties for Lotus Domino databases
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Properties pane, under Settings, click Lotus Domino.
4. Select the appropriate options as follows:
Backup method ◆ Full - Back up Database and Logs - Reset Archive Bit. Select
this to back up all the selected databases. To properly back up
your Lotus Domino data, you should perform regular full
backups of the database. This backup method should also be
used when the DBIID for the database has changed since prior
transactions cannot be applied to the new database.
◆ Differential - Changed Database and Logs. Select this to back
up files that were modified since the last Full backup. This
backup method is smaller and faster than a Full backup
because only archived transaction logs, unlogged databases,
and logged databases with DBIIDs that have changed will be
backed up.
◆ Incremental - Changed Database and Logs - Reset Archive Bit.
Select this to back up files that were modified since the last
Full or Incremental backup. This backup method is smaller
and faster than a Full backup because only archived
transaction logs, unlogged databases, and logged databases
with DBIIDs that have changed will be backed up.
1321

Selecting backup options for Lotus Domino databases
Mark archive logs for
recycling
5. Start the backup job or select other backup options from the Properties pane.
Related Topics:
“Backing up data” on page 345
Select this check box to reuse the transaction log after it has been
backed up.
Backup Exec will not delete the transaction log. Selecting this
option only indicates that the transaction log is ready to be reused
after it has been backed up successfully; the Lotus Domino server
actually deletes the transaction logs.
This option is selected automatically when you select the full
backup method. You cannot clear this option when you are using
the full backup method.
If the option is selected when you perform a differential or
incremental backup job, transaction logs that are needed to
maintain the differential backups will be reused. However, it
should be selected regularly to create space for new transaction
logs.
1322 Administrator’s Guide

Restoring Lotus Domino databases
Appendix L, Symantec Backup Exec Agent for Lotus Domino Server
Restoring Lotus Domino databases
The restore of a Lotus Domino database is a two-part process. The first part of the restore
copies database files from the media to the server. The second part of the restore is a
recovery process that applies data from the transaction logs to the database to bring it
up-to-date.
During a restore of the Lotus Domino database, the existing database is taken offline and
deleted, the database is restored, and changed records contained in the backup job are
applied to the database.
If the database is unlogged or local, the database is brought back online. If the database
is logged and multiple databases are being restored, the database name is added to a list
for recovery. During the restore process, Backup Exec assigns a unique name to
databases and then before databases are brought online, reassigns the original name.
Changing the name during the restore process has no effect on restored databases.
The recovery process begins automatically after the last database is copied to the server.
The database is restored to a point in time using transactions from the required
transaction logs. Required transaction logs that were backed up and recycled are also
included in the recovery process. After the recovery process completes, the Lotus
Domino database is brought online.
If you back up your Lotus Domino databases regularly, then restoring the most recent
backup set containing the Lotus Domino data is all that is required to restore the most
recent backups of your Lotus Domino databases.
Note If circular logging is enabled and both the databases and the Domino transaction
log are lost, the database can only be recovered to the point of the last full backup.
Use the same procedures to restore a server in a Microsoft Cluster Server cluster that you
use to restore a server in a non-clustered environment.
When restoring a Lotus Domino database to a MCSC cluster and a failover occurs during
the restore operation, active restore jobs are paused for 15 minutes as they wait for
existing connections to resolve themselves. If the restore job does not restart before the
failover time-out period expires, the job fails. If this occurs, the restore job must be
resubmitted.
Related Topics:
“Selecting Lotus Domino databases for restore” on page 1324
“Redirecting restore jobs for Lotus Domino databases” on page 1327
1323

Restoring Lotus Domino databases
Selecting Lotus Domino databases for restore
When you view Lotus Domino databases in the restore selections pane, two backup sets
appear for each Lotus Domino backup job. The first backup set contains the Lotus
Domino databases and the second backup set contains the transaction logs. To restore
data, selections should be made from the backup set that contains the Lotus Domino
databases; the required transaction logs are automatically restored with the selected
database.
Backup sets for Lotus Domino R7 backup job
Contains Lotus Domino
database files
Lotus Domino data is usually contained in the most recent backup set. However, some
subsequent differential or incremental backup jobs run after a full backup job may not
contain data in the backup set because only the transaction log was backed up. If the data
you want to restore is not located in the most recent backup set, check the previous
backup sets until you find the data.
Note If a new DBIID has been assigned to databases and you run a differential or
incremental backup, the data will be contained in the most recent backup set since
transactions with the new DBIID will not match the old DBIID.
For example, LD Server has a Full Backup 0001 and a Differential Backup 0002. If you
decide you want to restore data from Differential Backup 0002, you may select the Data
directory and find that it is empty.
1324 Administrator’s Guide

Empty data directory for Differential Backup 0002.
Appendix L, Symantec Backup Exec Agent for Lotus Domino Server
Restoring Lotus Domino databases
The data backed up for Differential Backup 0002 is actually contained in the transaction
log backup set. To restore the data, you must select it from the previous Full Backup
0001. The transaction logs from Differential Backup 0002 will be used to bring the
database up to date.
Note When restoring Lotus Domino databases to Microsoft Cluster Server cluster, the
virtual computer name or the virtual IP address of the Domino server should be
used when browsing or making Domino database selections in the View by
Resource tab of the Restore Job Properties dialog box.
Related Topics:
“Redirecting restore jobs for Lotus Domino databases” on page 1327
“Disaster recovery of a Lotus Domino server” on page 1329
1325

Selecting restore options for Lotus Domino databases
Transaction Logs backup set for Differential Backup 0002.
Selecting restore options for Lotus Domino databases
This procedure details how to select restore job properties for Lotus Domino databases,
and provides definitions for Domino-specific restore options.
When you select a Lotus Domino R7 backup set to restore, all database files and
necessary transaction logs are automatically restored. You can also choose to restore
specific database files.
To select restore job properties for Lotus Domino databases
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Settings, click Lotus Domino.
4. Select the appropriate options as follows:
Seconds to wait for the
database to go offline
Enter the number of seconds for the restore process to wait for a
database that is in use. When a Lotus database is restored it must
first be taken offline. This will ensure that the database is not
being accessed, closed, or deleted while the restore operation is
being processed. If the database is still in use and cannot be taken
offline after the specified wait time, the restore will fail.
Retain original IDs Select this option to restore the original database IDs.
1326 Administrator’s Guide

Appendix L, Symantec Backup Exec Agent for Lotus Domino Server
Selecting restore options for Lotus Domino databases
Assign new database ID Select this option to assign new IDs to the database.
Assign new database ID
and replica ID
If your Lotus Domino database is replicated, the databases on each computer must
have identical database and replica IDs. If you want to ensure that the databases
continue to be replicated after the restore, select the Retain original IDs option.
5. Start the restore job or select other options from the Properties pane.
Related Topics:
“Restoring data” on page 483
“About Lotus Domino transaction logs” on page 1320
Redirecting restore jobs for Lotus Domino databases
The Backup Exec logon account must have administrative credentials on the server to
which you want to redirect the backup of the Lotus Domino server. Lotus Domino
databases can only be redirected to a different directory on the local server from which
the database was backed up. If you are restoring a database to a different location, it must
reside in or under the Lotus Domino data directory. Point in time restores cannot be
redirected.
To redirect the restore of a Lotus Domino database
1. Select the media that contains the data you want to restore.
2. On the navigation bar, click the arrow next to Backup.
3. Click New Backup Job.
Select this option to assign new IDs to the database. A replica ID
is used to synchronize two or more databases that are being
replicated in the Lotus Domino environment. You can assign a
new replica ID during a restore to prevent other databases under
replication from overwriting the restored database files.
Point in time restore Select this option to enter a date and time in which to restore the
database. The option is only available for logged databases when
the archive logging style is set. Backup Exec will restore the Lotus
Domino database you selected in the Restore selections dialog box
and then automatically restore the necessary transaction logs
required to bring the databases up to the date and time specified.
If a point in time is not specified, the databases will be restored up
to the last committed transactions in the log file.
1327

Preparing for disaster recovery on a Lotus Domino server
4. Select the Lotus Domino databases.
5. After selecting options on the Restore Job Properties dialog box, on the Properties
pane, under Destination, click File Redirection.
6. Select Redirect file sets.
7. Select the drive to which you are restoring in Restore to drive. You cannot enter the
name of the drive, you must make a selection.
8. Enter the logon account for the server in Server logon account.
9. Enter the path to which you are restoring in Restore to path.
10. Enter the logon account for the path in Path logon account.
11. Start the redirection job or select other restore options from the Properties pane.
Related Topics:
“Restoring data” on page 483
“Creating a new Backup Exec System Logon Account” on page 154
Preparing for disaster recovery on a Lotus Domino server
A Disaster Preparation Plan is necessary for restoring Lotus Domino databases
efficiently and effectively in the event of a catastrophic failure. The goal is to minimize
the time to recover. Developing a backup strategy for your Windows computers and Lotus
Domino databases is the critical part of this plan.
When developing a strategy for backing up your Lotus Domino databases, consider the
following recommendations:
■ If you have linked databases, it is best to keep them on one volume. This allows
Backup Exec to synchronize the databases before they are backed up.
■ Back up active databases often. This reduces the amount of effort required to update
the databases to the point following the most recent backup.
■ Ensure that the notes.ini, cert.id, and server.id files are protected and available if a
disaster occurs.
Related Topics:
“Disaster recovery of a Lotus Domino server” on page 1329
“Disaster recovery of a Lotus Domino server using archive logging” on page 1330
1328 Administrator’s Guide

Appendix L, Symantec Backup Exec Agent for Lotus Domino Server
Preparing for disaster recovery on a Lotus Domino server
“Disaster recovery of a Lotus Domino server using circular logging” on page 1332
Disaster recovery of a Lotus Domino server
Before restoring your Lotus Domino server, you must first completely recover the
Windows computer and then recover or re-install Lotus Domino to the same location as
before the disaster occurred. All of the Lotus Domino system data must be recovered,
including log.nsf, names.nsf, template files, notes.ini, mail.box, and ID files.
Note If transaction logging is enabled on the Lotus Domino server, go to the section that
contains the steps for disaster recovery for the style of logging selected on the
server.
System recovery can be performed manually (see “Disaster preparation and recovery” on
page 653) or with Backup Exec’s Intelligent Disaster Recovery option (see “Symantec
Backup Exec Intelligent Disaster Recovery Option” on page 1501).
Note Disaster recovery of a Lotus Domino server in a Microsoft Cluster Server cluster
uses the same steps as recovering a Domino server in a non-clustered
environment.
After rebuilding the server, you can restore the databases from your most recent backup.
To recover a Lotus Domino server and databases
1. Restore or re-install the Lotus Domino server program directory to the same location
as before the disaster occurred.
2. Restore the notes.ini, cert.id, and server.id files from the last full backup of the Lotus
Domino server program directory.
3. Use the Lotus Domino Agent to restore the databases to the Domino data directory.
4. Start the Lotus Domino Server.
Related Topics:
“Disaster recovery of a Lotus Domino server using circular logging” on page 1332
“Returning to the last known good configuration” on page 655
“Restoring data” on page 483
“Selecting restore options for Lotus Domino databases” on page 1326
1329

Preparing for disaster recovery on a Lotus Domino server
Disaster recovery of a Lotus Domino server using archive logging
If the active transaction log is lost, you can recover the database only up to the
transactions contained in the last transaction log. However, if all of the transaction logs
are lost, you must have the following to recover the database:
■ An up-to-date Notes.ini file from the Lotus Domino server.
■ The backups of the database.
■ All archived log extents.
In addition, if the monitor change journal is enabled, you must disable it in the registry
before beginning the Lotus Domino server recovery.
The following steps provide instructions for disabling and re-enabling the monitor
change journal in the registry, and then recovering the Lotus Domino server, databases,
and transaction logs.
To disable the monitor change journal
1. Open the registry and browse to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\BACKUP EXEC FOR
WINDOWS\BACKUP EXEC\ENGINE\DOMINO
2. Disable monitor change journal by setting the value of the key Enable Change
Journal to 0.
3. Restart the Remote Agent for Lotus Domino.
To recover the Lotus Domino server, databases, and transaction logs when archive logging
is enabled
1. Restore the non-database Domino server files (*.id and notes.ini).
If necessary, reinstall but do not configure the Domino server and then restore the
non-database Domino files, which include the notes.ini and *.id files. Use the same
directory structure, directory location, and logdir path as was created in the original
installation. Do not launch the server after reinstalling it.
2. In the Restore Job Properties dialog box, under Settings, click General.
3. Check Restore over existing files.
1330 Administrator’s Guide

Appendix L, Symantec Backup Exec Agent for Lotus Domino Server
Preparing for disaster recovery on a Lotus Domino server
4. Using a text editor, change the TRANSLOG_Status setting in the notes.ini file on the
Domino server to 0.
For example, TRANSLOG_Status=0
5. Using the Backup Exec Agent for Domino, restore the last transaction log backed up
prior to the loss of the active transaction log.
6. Verify the transaction log restore was successful.
7. Shutdown and then restart the Backup Exec Agent for Lotus Domino.
8. Delete all transaction logs except the transaction log restored in step 5, from the
Domino transaction log directory.
9. Using a text editor, change the notes.ini file for the Domino server to match the
following:
TRANSLOG_Recreate_Logctrl=1
TRANSLOG_Status=1
10. Run a full restore of the Domino databases or a PIT state within the archived log
extents.
After the full restore finishes, the TRANSLOG_Logctrl parameter in the notes.ini file
is reset to 0.
11. Start the Domino server. Disaster recovery is complete.
12. If monitor change journal was disabled prior to beginning the disaster recovery
process, you must re-enable it.
To re-enable monitor change journal
1. Open the registry and browse to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\BACKUP EXEC FOR
WINDOWS\BACKUP EXEC\ENGINE\DOMINO
2. Enable monitor change journal by setting the value of the key Enable Change Journal
to 1.
3. Restart the Remote Agent for Lotus Domino.
1331

Preparing for disaster recovery on a Lotus Domino server
Related Topics:
“Selecting restore options for Lotus Domino databases” on page 1326
“Restoring data” on page 483
Disaster recovery of a Lotus Domino server using circular logging
If circular logging is enabled and the transaction log is lost, the Lotus Domino databases
can only be recovered to the point of the last backup.
To recover the Lotus Domino server and databases when circular logging is enabled
1. Restore or re-install the Lotus Domino server program directory (excluding the
notes.ini, cert.id, and server.id files) to the same location as before the disaster
occurred.
2. Check that the log directory (logdir) is created and does not contain old files.
If the log directory was not created, recreate the directory to the same location as
before the disaster occurred.
Do not start the Lotus Domino server after performing the previous steps.
3. Restore the notes.ini, cert.id, and server.id files from the last full backup of the Lotus
Domino server program directory to the same location as before the disaster
occurred.
4. To have Lotus Domino create the circular log file in the log directory (created in
step 2) when the server starts, set the following parameter in the notes.ini file:
translog_path=logdir
5. Use the Lotus Domino Agent to restore the databases to the Domino data directory.
Related Topics:
“Restoring data” on page 483
“Selecting restore options for Lotus Domino databases” on page 1326
1332 Administrator’s Guide

Frequently asked questions
Appendix L, Symantec Backup Exec Agent for Lotus Domino Server
Frequently asked questions
When I run a standard Backup Exec file system backup of my Lotus Notes server, none of
the transaction logs are backed up. Why?
During a standard file system backup of a Lotus Notes server, Backup Exec actively
excludes the transaction logs. These transaction logs are backed up when they are
included in a Lotus Notes server backup job using the Lotus Domino Agent.
To disable the transaction log exclusion, see the Symantec Technical Support web site for
details.
1333

Frequently asked questions
1334 Administrator’s Guide

Symantec Backup Exec
Agent for Microsoft SQL
Server
Appendix
M
The Symantec Backup Exec Agent for Microsoft SQL Server (SQL Agent) enables
network administrators to perform backup and restore operations on installations of
SQL that are connected to a network. SQL database backups can be integrated with
network backups without separate administration or dedicated hardware.
The SQL Agent provides support for:
■ Database, transaction log, differential, and filegroup backups, as well as database
recovery and replacement.
■ An automated restore of the master database.
■ The Intelligent Disaster Recovery option, which automates the disaster recovery
process of SQL 2000 or SQL 7.0, depending upon which SQL version is installed.
■ Restores of SQL databases to alternate locations.
■ Automated restore selections and options checking, which tests the validity of your
current SQL Server restore selections and job options before the restore job runs.
■ Hot backup copies of SQL databases during backup operations. This feature enables
you to direct a copy of the actual data streams being sent to media by a SQL database
to a local directory for later use.
■ Backups of multiple instances.
■ Integration with the Symantec Backup Exec for Windows Servers Advanced
Disk-based Backup Option (ADBO) and the Advanced Open File Option (AOFO).
ADBO and AOFO are separate, add-on components of Backup Exec. The use of ADBO
and AOFO can reduce both restore time and backup impact on the server.
■ Standby database. If the primary SQL server fails, or is shut down for maintenance,
another database called a standby database can be brought online. The standby
database contains a copy of the primary server's databases so that users can
1335

continue to access the database even though the primary server is unavailable.
When the primary server is available again, the changes on the standby database
must be restored back to the primary server or the changes will be lost. The
databases on the primary server should then be backed up and restored on the
standby database again.
Backup Exec provides a backup option that enables you to put the database in
standby mode when the log file backup completes, and a recovery completion state
of Leave the database in read-only mode to create and maintain a standby database.
■ Database Consistency Checks (DBCC) for each backup and restore job, including a
fast database consistency check of only the physical consistency of the database.
■ Full, bulk-logged, and simple recovery models. The simple recovery model is similar
to setting the truncate log on checkpoint option in SQL 7.0. With the simple recovery
model, copies of the transactions are not stored in the log file, which prevents
transaction log backups from being run. Therefore, you can recover the database to
the point of the last backup, but you cannot restore the database to the point of
failure or to a specific point in time.
■ Restores of transaction logs to a specific point in time or to a named transaction
when log marks are used.
In SQL 7.0 installations, the SQL Agent provides support for:
■ Database Consistency Checks (DBCC) before and after each backup job.
■ Restores of transaction logs to a specific point in time.
In SQL 2005 installations, the SQL Agent provides support for:
■ Database snapshots.
■ New copy backup jobs, which enable you to copy a SQL 2005 database without
having to run a full SQL database backup job.
■ Maintaining replication settings during redirected restores.
■ Verify only restore jobs, which enable you to determine both the validity of the SQL
data on the media and the ability of the destination SQL database to accept this data
before the database is deleted or overwritten during a restore job.
■ Back up with checksum generation. Used as a redundancy check, this option works
with the Verify Only Restore Job option.
■ Continuation of restore jobs when errors are detected. This feature enables you to
restore as much data as possible from a corrupt database backup.
Related Topics:
“Installing the SQL Agent” on page 1337
1336 Administrator’s Guide

Requirements for using the SQL Agent
The following are required for the SQL Agent:
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Requirements for using the SQL Agent
■ Backup Exec must have access rights to read both of the following SQL registry keys:
■ HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server
■ HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer
If Backup Exec does not have access to these registry keys, a restore to the default
directory may not work, and the Automate master database restore option on the
Restore Job Properties for SQL dialog box will not work.
To ensure that Backup Exec has access rights, verify that the logon account used has
administrator rights to the Windows server that the SQL instance is installed on.
■ The media server must have access to the SQL installation.
■ The credentials stored in the Backup Exec logon account used for backing up and
restoring SQL must have been granted the System Administrator role on the SQL
instance.
Installing the SQL Agent
The SQL Agent is installed locally as a separate, add-on component of Backup Exec for
Windows Servers, and can protect local or remote SQL Server databases.
The 64-bit Remote Agent can protect 64-bit SQL databases, although it cannot protect
SQL 7.0 databases.
For instructions on installing the SQL Agent on the local media server, see “Installing
Backup Exec to a local computer” on page 81.
For instructions on installing the 32-bit Remote Agent on a remote resource, see
“Installing Backup Exec to remote computers” on page 87.
For instructions on installing the 64-bit Remote Agent to protect remote 64-bit SQL
databases, see “Installing the Remote Agent to an Itanium-based or x64-based operating
system” on page 104.
Using Backup Exec logon accounts for SQL resources
To back up SQL, use a Backup Exec logon account that stores the credentials of a
Windows user account. The Windows user account must have been granted the System
Administrator role on the SQL instance.
1337

Using Backup Exec logon accounts for SQL resources
In the backup selections list or in the resource credentials list, apply that logon account
to the Windows server that SQL is installed on, not to the actual SQL instance.
How logon account is applied
The Backup Exec logon
account containing the
Windows credentials is
applied to the Windows
server that SQL is installed
on.
If you are using SQL Server Authentication, then add a Backup Exec logon account that
stores the credentials of the SQL user account. In the backup selections list, apply the
Backup Exec logon account for the Windows user account to the Windows server that
SQL is installed on, and then apply the logon account for the SQL user account to the SQL
instance.
1338 Administrator’s Guide

Applying SQL user account credentials
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Backup strategies for SQL
If you use a Backup Exec logon account that does not have the proper rights, you will
receive an error message stating that the username and password are invalid.
Related Topics:
“About selection lists” on page 327
“Creating a new Backup Exec System Logon Account” on page 154
Backup strategies for SQL
The Backup Exec logon
account containing the
SQL user account
credentials is applied to
the SQL instance.
Backup Exec incorporates online, nondisruptive SQL database protection as part of
everyday backup routines, which increases the chance of data recovery and minimizes
data loss without inhibiting daily database activity. Using database, differential, and log
backups provides a good balance between backup windows and minimizes the amount of
time that will be spent recovering a database if the need arises.
To decide which backup methods to use for the best data protection, consider the
following for typical environments:
■ In small environments, consider running a daily full database backup every evening
and daily transaction log backups.
■ In mid-sized environments, consider running a weekly full database backup and
daily transaction log backups along with daily differential backups except on the day
when the full backup is run.
1339

Backup strategies for SQL
■ In large environments, consider running daily differential database backups, weekly
full database backups, and transaction log backups as necessary. Many shops run full
backups on a weekly basis, preferring to run differential backups throughout the
week to keep backup run time to a minimum. Extremely large environments may
need to run filegroup backups in order to split the full backup over several days. Log
backups are required to be able to recover a system from a filegroup backup.
The trade-off with running fewer full backups and running more differential backups
occurs at recovery time when you must recover using the full database backup as well as
the last differential database backup, and all log backups made after the last differential
database backup.
What will work best for you will be based on the size of your environment, the number of
transactions processed each day, and the expectations of your users when a recovery is
required.
When you develop a SQL backup strategy, consider the following:
Recommendations for backing up SQL
SQL Server backup
strategies
Protect the entire SQL
Server.
When you upgrade, run
new full database
backups.
Description
To make sure SQL is completely protected, back up the following on a
regular basis:
◆ The system drive that SQL is on.
◆ The Windows registry and System State.
◆ SQL databases or filegroups. You do not need to back up both.
◆ Transaction logs.
If you upgrade SQL, run new full database backups. You may not be
able to restore backups from one version or service pack level of SQL to
other versions.
1340 Administrator’s Guide

Recommendations for backing up SQL (continued)
SQL Server backup
strategies
Run consistency checks
after backups.
Back up the master
database whenever data
is changed in the master
database.
Description
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Backup strategies for SQL
We recommend that you run a consistency check after a backup. If a
database, transaction log, or filegroup contains errors when it is
backed up, the backup will still contain the errors when it is restored, if
it is restorable at all. These consistency checks include:
◆ A full consistency check, including indexes. This check will have
significant impacts on SQL performance; therefore, it should be
performed in off-peak hours.
◆ A full consistency check with no index check. While not as
thorough as a full consistency check that includes indexes, this
check is faster and can be done during peak hours with little
impact on system performance.
◆ A physical check only. Another low-overhead check, this method
checks only the integrity of the physical structure of the page and
record headers, and the consistency between the pages' object ID
and index ID and the allocation structures.
Note The option to run a physical check only is not supported under
SQL 7.0.
Back up the master database whenever procedures are run that change
information in the database, especially after:
◆ New databases are created.
◆ Files are added to an existing database.
◆ Usernames or passwords are added or changed.
If changes are not backed up before the master database must be
restored, the changes are lost.
Run one backup at a time. Do not schedule more than one backup to occur simultaneously
against a database or its transaction log, or a filegroup.
1341

Backup strategies for SQL
Recommendations for backing up SQL (continued)
SQL Server backup
strategies
Back up both system and
user databases and
transaction logs
regularly.
If you have filegroups,
back them up instead of
databases. Do not back
up filegroups and
databases.
For SQL 7.0 only:
Create a copy of the
master and model
databases, and place the
copies in the same
directory that the
databases are in.
Description
Copies of the master and model databases are automatically created by
Backup Exec whenever you back up the master and model databases. If
these databases become corrupted or are missing, and SQL cannot be
started, you can replace them with the copies of the master and model
databases, and then start SQL. After SQL is running again, you can
restore the latest copy of the master database using Backup Exec’s
Automate master database restore option, and then restore any other
databases, if needed.
If you purchased the Intelligent Disaster Recovery (IDR) option, then
during an IDR recovery of the C: drive, it will automatically replace the
damaged databases with the copies of the master and model databases
that you made.
When databases grow too large to be backed up all at once, filegroups
can provide an alternative backup method. Different filegroups can be
backed up at different times and frequencies. A combination of
filegroup and log backups provides complete database protection.
Make copies of the master and model databases and place the copies
in the same directory that the master and model databases are in.
Then, if the master database becomes critically damaged and SQL
cannot be started, instead of running the Rebuild Master utility or
reinstalling SQL, you can replace the corrupted or missing databases
with the copies of the master and model databases, and then start
SQL. After SQL is running again, you can restore the latest copy of the
master database using Backup Exec’s Automate master database
restore option, and then restore any other databases, if needed.
If you purchased the Intelligent Disaster Recovery (IDR) option, then
during an IDR recovery of the drive C, it will automatically replace the
damaged databases with the copies of the master and model databases
that you made.
For details, see “To create copies of the SQL 7.0 master and model
databases” on page 1390.
1342 Administrator’s Guide

Recommendations for backing up SQL (continued)
SQL Server backup
strategies
If you have filegroups,
run at least one full
database backup first,
then back up the
filegroups instead of
databases. Do not back
up filegroups and
databases.
Consistency checks for SQL
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Consistency checks for SQL
If you back up a database, transaction log, or filegroup that contains errors, these errors
will still exist when the backup is restored. In some cases, this can prevent a successful
restore. Backup Exec enables you to check the logical and physical consistency of the
data before and after a backup. SQL reports any consistency check failures in the Backup
Exec job log. Symantec strongly recommends that you always run a consistency check
either before or after the backup.
Backup Exec’s consistency check uses the following SQL consistency check utilities:
■ CHECKDB
■ CHECKCATALOG
Description
■ CHECKFILEGROUP
■ PHYSICAL_ONLY
CHECKDB, CHECKCATALOG, and PHYSICAL_ONLY are performed for database-related
operations.
Note PHYSICAL_ONLY is not available for SQL 7.0.
CHECKFILEGROUP is performed for filegroup-related operations.
For more information concerning these utilities, see your MS SQL documentation.
Related Topics:
“Setting backup options for SQL” on page 1347
When databases grow too large to be backed up all at once, filegroups
can provide an alternative backup method. Different filegroups can be
backed up at different times and frequencies.
However, SQL 7.0 databases cannot be restored using only filegroup
and log backups. SQL 7.0 databases must have at least one full
database backup in order to be restored. If the database has been
deleted or does not exist, restore the full database backup, and then
restore all the filegroup and log backups.
1343

Using snapshot technology with the SQL Agent
Using snapshot technology with the SQL Agent
The SQL Agent supports snapshot technology for SQL 2000 and SQL 2005 through the
use of the Symantec Backup Exec for Windows Servers - Advanced Open File Option
(AOFO) and the Advanced Disk-based Backup Option (ADBO). ADBO can only be installed
on Windows 2003. The use of ADBO and AOFO can reduce both restore time and backup
impact on the server.
Note The SQL Agent also supports SQL 2005 database snapshot technology. For more
information, see “About SQL 2005 database snapshots” on page 1358.
■ With snapshot technology, a point in time view of the SQL database is "snapped" and
then backed up, leaving the actual SQL database open and available for users.
■ Symantec recommends that SQL backup jobs be run separately from AOFO or ADBO
backup jobs because SQL backups made with snapshot technology are considerably
bigger than regular SQL backups.
■ Performing consistency checks before backup is highly recommended (see
“Consistency checks for SQL” on page 1343).
■ The SQL Agent only supports full snapshot backups; filegroup snapshots, log
snapshots, and differential snapshots are not supported.
■ If a filegroup, differential, or transaction log backup method is selected, AOFO or
ADBO Backup Job Properties are ignored and a traditional differential or transaction
log backup will be performed.
■ With the SQL Agent, snapshot and traditional backups are interoperable when
restoring SQL data.
■ For the Intelligent Disaster Recovery Option to work with SQL backups, copies are
made of the master and model databases. Copies are only made when non-snapshot
backups of master and model are run. If you are using AOFO or ADBO for SQL
backups, make at least one backup of the master and model databases without using
AOFO or ADBO.
■ If SQL is upgraded, refresh the copies with another non-snapshot backup.
■ SQL backups made using AOFO or ADBO will fail if multiple databases are selected
for backup and SQL Service Pack 2 is not installed. If SQL 2000 Service Pack 2 or later
is installed, you can select multiple databases at the same time for backup.
■ Snapshot backups of the master database cannot be redirected.
■ While performing database consistency checks both before and after backups
impacts the time required for the backup jobs
1344 Administrator’s Guide

Related Topics:
“Setting backup options for SQL” on page 1347
Using AOFO with the SQL Agent
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Using snapshot technology with the SQL Agent
When using the SQL Agent together with AOFO, depending on which operating system
you are running, you can select to use the VERITAS Storage Foundation for Windows
FlashSnap Option or the Microsoft Volume Shadow Copy Service. What happens when
the Automatically select open file technology option is selected, also depends on the
operating system being used.
Note When used with the SQL Agent, AOFO snapshot backups are limited to full
backups of the Microsoft SQL Server databases.
Protecting SQL on Windows 2003
The SQL Agent supports Microsoft’s Volume Shadow Copy Service (VSS), a snapshot
provider service only available on Windows 2003 or later, and the VERITAS Storage
Foundation for Windows FlashSnap Option.
In order for the SQL Agent to use VSS, the SQL Agent must be installed and running on
the SQL server. VSS can use different providers, including Default, System, Hardware,
and Software.
In order for the SQL Agent to use the FlashSnap Option, the SQL Agent, VERITAS
Storage Foundation for Windows, and the Advanced Open File Option (AOFO) must be
installed and running on the SQL server.
Related Topics:
“About the Advanced Open File Option” on page 843
Protecting SQL on Windows 2000
When protecting Windows 2000, the SQL Agent only supports the VERITAS Storage
Foundation for Window FlashSnap Option and the ServerFree Option.
In order to protect the SQL server using the FlashSnap Option, the SQL Agent, VERITAS
Storage Foundation for Windows, and the Advanced Open File Option (AOFO) must be
installed and running on the SQL server.
You can select the FlashSnap option through the Advanced Open File options dialog box.
If Automatically select open file technology is selected on the Advanced Open File
options dialog box when running Windows 2000, Backup Exec attempts to use the
1345

Using snapshot technology with the SQL Agent
FlashSnap Option to perform the backup. If the FlashSnap option is not available, the job
will fail. If you select the Symantec Volume Snapshot Provider or Microsoft Volume
Shadow Copy Service options, a non-snapshot backup is performed.
Also, when using AOFO with FlashSnap note the following:
■ The SQL user data and log files must exist on the mirrored volume (plex) in order for
the snapshot to occur.
■ To protect system databases, the system database files must reside on the mirrored
volume (plex).
Related Topics:
“About the Advanced Open File Option” on page 843
“Setting defaults for the Advanced Open File Option for backup jobs” on page 850
“About SQL 2005 database snapshots” on page 1358
Using the ADBO with the SQL Agent
In order to protect the SQL server using ADBO, both the SQL Agent and ADBO must be
installed. ADBO, which can only be installed on Windows 2003, can use different
snapshot providers, including hardware and software. You can select the provider to be
used through the Advanced Disk-based Backup options when creating the backup job.
In order to use the Software - Use VERITAS Storage Foundation for Windows option,
VERITAS Storage Foundation for Windows (VSFW) must be installed.
If Automatic - Use hardware if available; otherwise use software is selected, the first
available the first available hardware provider is used. If a hardware provider is not
available, then the first software provider is used. If neither a hardware nor a software
provider are available, the job status will depend the job disposition option set on the
Advanced Disk-based Backup dialog box.
Also, when using ADBO note the following:
■ The SQL user data and log files must exist on the mirrored volume (plex) in order for
the snapshot to occur.
■ To protect system databases, the system database files must reside on the mirrored
volume (plex).
Related Topics:
“Selecting data to back up” on page 315
“About selection lists” on page 327
“Consistency checks for SQL” on page 1343
1346 Administrator’s Guide

Setting backup options for SQL
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting backup options for SQL
This procedure details how to select backup job properties for SQL and provides
definitions for SQL-specific backup options. For details on how to create a backup job,
and for definitions of all other backup options, see “Creating a backup job by setting job
properties” on page 349.
To select backup job options for SQL
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Properties pane, under Settings, click Microsoft SQL.
1347

Setting backup options for SQL
4. Select the appropriate options:
Backup method ◆ Full - Back up entire database or filegroup. Select this option
to back up the entire database or filegroup. This option is
selected by default.
See “Backing up SQL databases” on page 1352.
◆ Log - Back up transaction log. Select this option to back up
only the data contained in the transaction log; it does not back
up database data. After the transaction log is backed up,
committed transactions are removed (truncated).
Select this option to be able to select No recover - Place
database in loading state or Standby - Place database in
standby state under Enable advanced log backup options.
See “Backing up SQL transaction logs” on page 1357.
◆ Log No Truncate - Back up transaction log - no truncate. Select
this method only when the database is corrupted or database
files are missing. Since the Log No Truncate method does not
access the database, you can still back up transactions that you
may not be able to access otherwise when the database is in
this state. You can then use this transaction log backup along
with the database backup and any previous transaction log
backups to restore the database to the point at which it failed;
however, any uncommitted transactions are rolled back. The
Log No Truncate method does not remove committed
transactions after the log is backed up.
See “Backing up SQL transaction logs” on page 1357.
◆ Differential - Back up database or filegroup changes only.
Select this option to back up only the changes made to the
database or filegroup since the last full backup. Because
differential backups allow the restore of a system only to the
point in time that the differential backup was created, you
should also create multiple log backups between the
differential backups.
◆ Database Snapshot (SQL 2005) - Read-only, point-in-time copy
of another database - Select this option to create a read only,
point-in-time copy of another database.
See “About SQL 2005 database snapshots” on page 1358.
1348 Administrator’s Guide

Database snapshots to
keep
Consistency check before
backup
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting backup options for SQL
◆ Full Copy-only (SQL 2005) - Back up entire database or
filegroup without affecting future differential or log backups -
Select this option to back up the entire database or filegroup
without affecting future differential or log backups.
Unlike the Full backup method, the Full Copy-only backup
method does not reset the SQL 2005 differential baseline that
is used to indicate the database blocks that have changed since
the last full backup.
After making a full backup, you can use the Full Copy-only
backup method to make a copy of a SQL 2005 database without
affecting the baseline backup set required to run future
differential backups.
(SQL 2005 only) Use this option to select the number of database
snapshots to keep on disk. As the threshold is met, older database
snapshots are deleted, which are then replaced with new
snapshots. Because database snapshots continue to grow as the
SQL 2005 database is updated, limiting the number of snapshots
enables you to minimize both the disk space and SQL Server
processing time that is required when the snapshots are updated.
See “About SQL 2005 database snapshots” on page 1358.
Select a consistency check to run before a backup.
◆ None. Select this option if you do not want a consistency check
to run before a backup. Symantec strongly recommends that
you always run a consistency check either before or after the
backup. This option is selected by default.
◆ Full check, excluding indexes. Select this option to exclude
indexes from the consistency check. If indexes are not
checked, the consistency check runs significantly faster but is
not as thorough. Only the data pages and clustered index
pages for each user table are included in the consistency
check. The consistency of the nonclustered index pages is not
checked.
◆ Full check, including indexes. Select this option to include
indexes in the consistency check. Any errors are logged.
◆ Physical check only. Select this option to perform a low
overhead check of the physical consistency of the database.
This option only checks the integrity of the physical structure
of the page and record headers, and the consistency between
the pages' object ID and index ID and the allocation structures.
The Physical check only option is not supported under SQL
7.0.
1349

Setting backup options for SQL
Continue with backup if
consistency check fails
Consistency check after
backup
Enable advanced log
backup options
No recover - Place
database in loading state
Select this option to continue with the backup operation even if
the consistency check fails. You may want to continue with the
backup when the consistency check fails if you think that a
backup of the database in its current state is better than no
backup at all, or if you are backing up a very large database with
only a small problem in a table.
Select a consistency check to run after a backup. Because
database transactions can occur during or after the consistency
check, but before the backup runs, consider running a consistency
check after the backup to ensure the data was consistent at the
time of the backup.
◆ None. Select this option if you do not want a consistency check
to run after a backup. Symantec strongly recommends that
you always run a consistency check either before or after the
backup. This option is selected by default.
◆ Full check, excluding indexes. Select this option to exclude
indexes from the consistency check. If indexes are not
checked, the consistency check runs significantly faster but is
not as thorough. Only the data pages and clustered index
pages for each user table are included in the consistency
check. The consistency of the nonclustered index pages is not
checked.
◆ Full check, including indexes. Select this option to include
indexes in the consistency check. Any errors are logged.
◆ Physical check only. Select this option to perform a low
overhead check of the physical consistency of the database.
This option only checks the integrity of the physical structure
of the page and record headers, and the consistency between
the pages' object ID and index ID and the allocation structures.
The option Physical check only is not supported under SQL
7.0.
Select this option to choose either the No Recover - Place database
in loading state option or the Standby - place database in standby
state option to apply to the backup.
This option is only available after you select the backup method
Log - Back up transaction log.
Select this option to put the database in a loading state when the
log file backup completes. Users cannot connect to or query the
database while it is in a loading state.
This option is only available after you select Enable advanced log
backup options.
1350 Administrator’s Guide

Standby - Place database
in standby state
Use checksums on
backup (SQL 2005 only)
Create on-disk copies of
SQL backups to be placed
on the SQL server where
the database is located
Related Topics:
“Selecting data to back up” on page 315
“About selection lists” on page 327
“Consistency checks for SQL” on page 1343
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting backup options for SQL
Select this option to put the database in standby mode when the
log file backup completes. Users can connect to and query the
database when it is in standby mode, but cannot update it.
Convert a standby database to a live database by restoring the
latest transaction log and specifying the recovery completion
state Leave database operational. No additional transaction logs
can be restored.
This option is only available if Enable advanced log backup
options has been selected.
This option is not supported under SQL 7.0.
Select this option to have SQL 2005 add checksums to the SQL
2005 database data being backed up by Backup Exec. Adding
checksums to the data being backed up is required if you want to
use the option Run verify only; do not restore data. Using this
option, along with Run verify only; do not restore data, ensures
that during a restore of the SQL database, you are restoring from a
verified SQL 2005 backup.
Select this option to create an on-disk copy of the SQL database
being backed up. This option lets you simultaneously back up a
SQL database to storage media while also writing a copy of the
database to a disk path you specify in the Save to path box.
This option gives IT administrators the ability to back up SQL
databases while also providing database administrators with
copies of the database on disk, which can be used for such things
as tests and restores.
Save to path Enter a path in which to save on-disk copies of SQL backups.
Guide Me Click this to start a wizard that helps you select backup job
properties for SQL.
1351

Setting backup options for SQL
Automatic exclusion of files during volume level backups
If you select a volume that contains SQL data for backup, the SQL Agent determines
which SQL data should not be included in a volume level backup. For example, .MDF and
.LDF files should not be part of the backup because they are opened for exclusive use by
the SQL system. These files will be automatically excluded for backup by a feature called
Active File Exclusion. If this exclusion did not happen during a non-snapshot backup,
these files would appear as in use - skipped. If this exclusion did not happen during a
snapshot backup, the files would be backed up in a possible inconsistent state, which
could create restore issues.
While it is not recommended, if you want to include SQL data in a volume level backup,
you must first dismount the database you want backed up. Then, run the backup job.
Related Topics:
“Backing up SQL databases” on page 1352
“About backing up SQL filegroups” on page 1354
“Displaying filegroups on the backup selections pane” on page 1355
Backing up SQL databases
Backup Exec includes three methods for backing up databases: Full, Differential, and Full
Copy-only (for SQL 2005 only). The full method backs up the entire database including
all system tables and filegroups. The differential method backs up only the changes
made to the database since the last full backup. The copy method works in the same
manner as the full method, except that it does not truncate the SQL transaction logs.
A differential backup is smaller and faster than a full backup, so differential backups can
be run more often than full backups. Because differential backups allow the restore of a
system only to the point that the differential backup was created, you should also create
multiple log backups between the differential backups. Using transaction log backups
allows you to recover the database to the exact point of failure.
Consider using differential backups when only a relatively small amount of data changes
between full backups, or if the same data changes often. Differential backups may also
work well in your environment if you are using the simple recovery model and need
backups more often, but cannot spare the time to do frequent full backups. If you are
using the full or bulk-logged recovery models, you can use differential backups to
decrease the time it takes to roll forward log backups when restoring a database.
If you want to run database backups only, instead of a mix of database and log backups,
and you are not running SQL 7.0, use the simple recovery model for the database so that
the transaction log is automatically truncated when a checkpoint occurs in the database.
This helps prevent transaction logs from becoming full since with other recovery models
the logs are not cleared after a database backup.
1352 Administrator’s Guide

Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting backup options for SQL
With the simple recovery model, copies of the transactions are not stored in the log file,
which prevents transaction log backups from being run.
If you want to run database backups only, and are using SQL 7.0, use SQL Enterprise
Manager to enable the database option truncate log on checkpoint for each database you
are backing up. Enabling this option causes the transaction log to be automatically
truncated whenever a checkpoint occurs in the database.
If you do not run transaction log backups, you can recover the database to the point of
the last backup, but you cannot restore the database to the point of failure or to a specific
point in time.
The master database can only be backed up with the full method; you cannot use the log
or differential methods to back up the master database.
To back up SQL databases
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Properties pane, under Source, click Selections, and then select the data you
want to back up.
For information on using logon accounts when making backup selections, see “Using
Backup Exec logon accounts for SQL resources” on page 1337.
4. To select SQL data from local or remote selections, click the domain name icon or
icons that contain the SQL installations, and then click the actual Windows
computer icon that contains the SQL installation. If you are using a cluster server,
make backup selections from the virtual server.
A list of shared network directories appears, along with an icon that represents the
SQL installation.
To select all databases in SQL, click the check box preceding the SQL icon, or you can
select specific databases by clicking the SQL icon, and then selecting individual
databases.
Whether you make SQL database selections using the Windows domain, Active
Directory, DNS names, or IP addresses, you must use the same method when making
full, differential, and incremental backups of your SQL databases. For example, do
not make full backup selections of your SQL databases using the Windows domain,
and then make incremental or differential selections using an IP address.
5. To select the SQL backup job properties, on the Properties pane, under Settings, click
Microsoft SQL.
1353

Setting backup options for SQL
6. Select options for the backup job. For details on these options, see “Setting backup
options for SQL” on page 1347.
7. Start the backup job or select other backup options from the Properties pane, and
then start the backup job.
Related Topics:
“Backing up data” on page 345
“Backing up SQL transaction logs” on page 1357
“Setting backup options for SQL” on page 1347
About backing up SQL filegroups
When databases grow too large to be backed up all at once, filegroups can provide an
alternative backup method. Filegroups can be backed up at different times and
frequencies. Filegroups that change often can be backed up more frequently than
filegroups that remain more static. In certain situations, filegroup backups can greatly
reduce restore time. For example, if a nonprimary filegroup is destroyed or corrupted,
only that filegroup has to be restored.
Backup Exec includes two methods for backing up filegroups: full and differential. The
full method backs up the entire filegroup. The differential method backs up only the
changes made to the filegroup since the last full backup. A differential backup is smaller
and faster than a full backup, so differential backups can be run more often than full
backups. Consider using differential backups when only a relatively small amount of
data changes between full filegroup backups, or if the same data changes often.
Because differential backups allow the restore of a system only to the point that the
differential backup was created, you should also create multiple log backups between the
differential backups. Using transaction log backups enables you to recover the filegroup
to the exact point of failure. A combination of full and differential filegroup backups and
transaction log backups provides complete database protection. Log backups are
required to be able to recover a system from a filegroup backup.
Caution SQL 7.0 databases cannot be restored using only filegroups and log backups.
SQL 7.0 databases must have at least one full database backup in order to be
restored. If the database has been deleted or does not exist, restore the full
database backup, and then restore all the filegroup and log backups.
Related Topics:
“Displaying filegroups on the backup selections pane” on page 1355
“Backing up SQL filegroups” on page 1355
1354 Administrator’s Guide

Displaying filegroups on the backup selections pane
To display filegroups on the backup selections pane
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Microsoft SQL.
3. Select Display filegroups when creating new backup jobs.
Related Topics:
“Backing up SQL filegroups” on page 1355
“Setting backup options for SQL” on page 1347
Backing up SQL filegroups
To back up SQL filegroups
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Properties pane, under Source, click Selections.
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting backup options for SQL
4. Select the data you want to back up.
For information on using logon accounts when making backup selections, see “Using
Backup Exec logon accounts for SQL resources” on page 1337.
5. To select SQL data, click the domain name icon or icons that contain the SQL
installations, and then click the actual Windows computer icon that contains the
SQL installation. If you are using a cluster server, make backup selections from the
virtual server.
Click a SQL container and select specific filegroups.
1355

Setting backup options for SQL
Selections options
6. To select SQL backup job properties, on the Properties pane, under Settings, click
Microsoft SQL.
7. After selecting job options, start the backup job or select other backup options from
the Properties pane, and then start the backup job.
Related Topics:
“Backing up data” on page 345
“Setting backup options for SQL” on page 1347.
1356 Administrator’s Guide

Backing up SQL transaction logs
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting backup options for SQL
Backup Exec includes two methods for backing up transaction logs: Log and Log No
Truncate.
When running log backups, it is recommended that you use Backup Exec exclusively to
perform log truncations if you decide to truncate the logs. After a transaction log has
been truncated by something other than a log backup, you must run a full or differential
backup before you run another log backup.
Use the Log No Truncate method only when the database is corrupted or database files
are missing. This method backs up transactions that you may not be able to access
otherwise when the database is in this state. You can then use this transaction log
backup along with the last database backup and any previous transaction log backups to
restore the database to the point at which it failed; however, any uncommitted
transactions are rolled back. The Log No Truncate method does not remove committed
transactions after the log is backed up.
To use the Log No Truncate backup to restore a database, you should also have a database
backup that was created before the Log No Truncate backup. The transaction log contains
only the log files used in the restore process, which alone are not sufficient to restore a
complete database. You must have at least one database backup or a full set of filegroup
backups and a log backup of the database to restore a database.
Caution Do not run a log backup using either method if the SQL 2000 or SQL 2005
database is using the simple recovery model. With the simple recovery model,
you can recover data only up to the most recent full or differential backup. If
you run a log backup on a database using the simple recovery completion state,
the backup will fail.
If using SQL 7.0, do not run a log backup using either method if the SQL
database option truncate log on checkpoint is enabled. When this option is
enabled, every time a checkpoint occurs in the database, the transaction log is
truncated without the truncated part of the transaction log being backed up,
which prevents more transaction log backups from being created. You should
run a database or differential backup instead.
To check the database properties, from the Enterprise Manager on the SQL Server,
right-click the database, click Properties, click the Options tab, and then view the
configuration settings.
If using SQL 7.0, do not run a log backup using either method f the SQL database select
into/bulkcopy option is enabled, and nonlogged operations have occurred in the
database since the last database backup was created. Nonlogged operations break the
sequence of transaction log backups. The restore of a database using database and
transaction log backups is successful only if there is an unbroken sequence of
1357

Setting backup options for SQL
transaction log backups after the last database or differential backup. If these conditions
are present, you should run a database or differential backup and then start running log
backups again in order to save any changes necessary to restore the database.
To back up SQL transaction logs
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Properties pane, under Source, click Selections, and then select the data you
want to back up.
For information on using logon accounts when making backup selections, see “Using
Backup Exec logon accounts for SQL resources” on page 1337.
4. To select SQL data, click the domain name icon or icons that contain the SQL
installations, and then click the actual Windows computer icon that contains the
SQL installation. If you are using a cluster server, make backup selections from the
virtual server.
A list of shared network directories appears, along with an icon that represents the
SQL installation.
5. To select SQL backup job properties, on the Properties pane, under Settings, click
Microsoft SQL.
6. After selecting job options, start the backup job or select other backup options from
the Properties pane, and then start the backup job.
Related Topics:
“Setting backup options for SQL” on page 1347
“About restoring SQL databases and filegroups” on page 1366
“Restoring from SQL transaction logs up to a point in time” on page 1368
“Restoring from SQL 2000 or SQL 2005 transaction logs up to a named transaction” on
page 1369
About SQL 2005 database snapshots
SQL 2005 database snapshots enable you to quickly revert a SQL 2005 database back to
the state it was in when the database snapshot was created, without requiring a full
restore of the host database. Note however, that changes made to the host between the
time a database snapshot is created and the point at which it is reverted, are lost.
1358 Administrator’s Guide

Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting backup options for SQL
The Backup Exec SQL Agent works with the SQL 2005 database to create database
snapshots, which are read-only, point-in-time copies of an existing host database. When
Backup Exec runs a SQL 2005 backup job using the Database Snapshot (SQL 2005)
backup method, a request is sent to the host database instructing it to create a database
snapshot.
Database snapshots cannot be backed up to storage media. Rather, they are written to a
SQL 2005 snapshot file on disk. After running the database snapshot job, Backup Exec
creates history and job log information to indicate the job’s status.
Because database snapshots cannot be backed up, all database snapshots will be lost if
the disk where the host database is installed fails. Therefore database snapshots should
not be used as your sole database protection strategy. They should be used in conjunction
with an overall Backup Exec database protection strategy that includes full, differential,
and transaction log backups of the SQL 2005 database.
For more information, see your Microsoft SQL 2005 documentation.
Note SQL 2005 database snapshots are not the same as Microsoft Virtual Shadow Copy
Service (VSS) snapshots. Whereas VSS snapshots enable you to create
point-in-time snapshots of disk volumes and shares, database snapshots enable
you to create point-in-time copies of SQL 2005 databases. You cannot use the VSS
option in Backup Exec’s Advanced Open File Option to create SQL 2005 database
snapshots.
Note SQL database snapshot catalog information that refers to deleted database
snapshots is periodically removed from the catalogs. If backup media is
re-cataloged, the database snapshot catalog information will be periodically
removed again.
Related Topics:
“Using the database snapshot (SQL 2005) backup method” on page 1359
Using the database snapshot (SQL 2005) backup method
The backup method, Database Snapshot (SQL 2005), enables you to:
■ Produce SQL 2005 database snapshots.
■ Set the number of SQL 2005 database snapshots to keep on disk.
After selecting the Database Snapshot (SQL 2005) backup method, an option appears
called Database snapshots to keep. This option enables you to set the number of database
snapshots to be kept on disk for each database. As the threshold is met, older database
snapshots are deleted, which are then replaced with new snapshots. Because database
1359

Setting backup options for SQL
snapshots continue to grow as the SQL 2005 database is updated, limiting the number of
snapshots enables you to minimize both the disk space and SQL Server processing time
that is required when the snapshots are updated.
By limiting the number of database snapshots that are kept, you can configure a
database protection strategy that minimizes data loss in the event of a host database
problem. For example, you can create a strategy that protects the SQL 2005 database
from inadvertent table deletions. This strategy consists of a Backup Exec database
snapshot job that you schedule to run once every hour during a 24 hour period. As part
of the strategy, you also configure the job to keep four database snapshots. Because the
job is scheduled to run every hour, a new database snapshot is created every hour.
Beginning with the fifth hour and going forward, the oldest database snapshot is
automatically deleted before a new one is created. Throughout the 24 hour period, there
are no more than four database snapshots on disk. If a user deletes a database table, you
first determine the time the table was deleted and then run a Backup Exec database
snapshot restore job that enables you to revert the host to one of four previous points in
time going back four hours. Remember, however, that any changes made to the host
between the time a database snapshot is created and the point at which it is reverted, are
lost.
Related Topics:
“Creating database snapshots” on page 1360
“Reverting SQL 2005 databases using database snapshots” on page 1381
Creating database snapshots
To create database snapshots
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Properties pane, under Source, click Selections.
4. Select the SQL 2005 database for which you want to create a database snapshot.
5. On the Properties pane, under Settings, click Microsoft SQL.
6. In the Backup method field, select Database Snapshot (SQL 2005) - Read only,
point-in-time copy of another database.
7. Set the number of database snapshots per database to keep, or accept the default of
four.
1360 Administrator’s Guide

Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting backup options for SQL
8. Start the database snapshot job or select other backup options from the Properties
pane, and then start the backup job.
Related Topics:
“Reverting SQL 2005 databases using database snapshots” on page 1381
1361

Setting restore options for SQL
Setting restore options for SQL
This procedure details how to select restore job properties for SQL, and provides
definitions for SQL-specific restore options. For details on how to create a restore job,
and for definitions of all other restore options see “Restoring data” on page 483.
To set restore options for SQL
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Settings, click Microsoft SQL.
4. Select the appropriate options:
Leave database ready to
use. Additional
transaction logs cannot
be restored.
Leave database
nonoperational.
Additional transaction
logs can be restored.
Leave database in
read-only mode
Take existing destination
database offline
Select this option when restoring the last database, differential,
or log backup in the restore sequence in order to have the restore
operation roll back all uncompleted transactions. After the
recovery operation, the database is ready for use. If Leave
database ready to use is not performed, the database is left in an
intermediate state and is not usable.
If Leave database ready to use is selected when an intermediate
backup is being applied, you cannot continue to restore backups.
You must restart the restore operation from the beginning.
Select this option during a restore if you have additional
differential or transaction log backups to be restored in another
restore job.
Select this option during transaction log and database restore to
create and maintain a standby database. See your SQL
documentation for information on standby databases.
Select this option if you want Backup Exec to automatically take
the database offline before the restore job runs. If this option is
not selected and there are active connections to the SQL database,
the restore job will fail.
This option is not supported under SQL 7.0.
1362 Administrator’s Guide

Overwrite the existing
database
Automate master
database restore
Continue restoring if an
error occurs during the
restore (SQL 2005 only)
Run verify only; do not
restore data
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting restore options for SQL
Select this check box to replace a database or filegroup, even if
another database or filegroup with the same name already exists
on the server. If Overwrite the existing database is not specified
for a restore, SQL performs a safety check to ensure that a
different database or filegroup is not accidentally overwritten.
Refer to your SQL documentation for more information about the
safety check that occurs when this option is not selected.
Select this check box to let Backup Exec stop SQL so that the
master database can be restored. All existing users are logged off,
and SQL Server is put into single-user mode.
When this option is selected, only the master database can be
restored; if this option is selected for any other database, those
jobs will fail.
If Backup Exec does not have access to the SQL registry keys,
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL
Server, and
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer, then
a restore to the default directory may not work, and the Automate
master database restore option on the restore job properties for
SQL will not work. To ensure that Backup Exec has access rights,
verify that the logon account used has administrator rights to the
Windows server that the SQL instance is installed on.
Select this option to let Backup Exec restore as much of the SQL
2005 database as possible if SQL 2005 detects database corruption
errors during the database restore.
Select this option to have SQL verify your SQL backup jobs. This
option returns the entire Backup Exec SQL data stream directly to
SQL for verification. Although SQL processes the data stream for
errors, existing SQL databases are not affected; all verification
processes are handled within SQL itself, and nothing is ever
written to the disk.
As SQL processes the data streams, a slight performance impact
on overall database performance occurs until the verification
process finishes.
Although supported in SQL 2000, this option’s best performance
occurs with the Backup Exec SQL backup option, Use checksum on
backups (SQL 2005) and with SQL 2005. See “Setting backup
options for SQL” on page 1347.
1363

Setting restore options for SQL
Consistency check after
restore
◆ Full check, excluding indexes. Select this option to exclude
indexes from the consistency check. If indexes are not
checked, the consistency check runs significantly faster but is
not as thorough. Only the data pages and clustered index
pages for each user table are included in the consistency
check. The consistency of the nonclustered index pages is not
checked.
◆ Full check, including indexes. Select this option to include
indexes in the consistency check. Any errors are logged. This
option is selected by default.
◆ Physical check only. Select this option to perform a low
overhead check of the physical consistency of the SQL 2000
database. This option only checks the integrity of the physical
structure of the page and record headers, and the consistency
between the pages' object ID and index ID and the allocation
structures. Physical check only is not supported under SQL
7.0.
◆ None. Select this option if you are doing sequential restores.
Do not run a consistency check after a restore until all
sequential restores have been done. If a consistency check is
selected during a restore, the restore will complete but the
consistency check will not be done. Check the job log for this
information.
If you need to recover the database after restores are
complete, select one of the consistency checks mentioned
above.
Recover the entire log Select this to recover all of the transactions in the transaction
logs you select for restore.
Point in time log restore Select this check box to restore transactions from a transaction
log up to and including a point in time in the transaction log.
After the point in time, recovery from the transaction log is
stopped.
In the Date box, select the part of the date you want to change, and
then enter a new date or click the arrow to display a calendar from
which you can select a date.
In the Time box, select the part of the time you want to change,
and then enter a new time or click the arrows to select a new time.
1364 Administrator’s Guide

Restore log up to named
transaction
Include the named
transaction
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting restore options for SQL
Select this check box to restore transactions from a transaction
log up to a named transaction (or named mark) in the transaction
log; after that, recovery from the transaction log is stopped. The
named transactions are case-sensitive.
Check your client application event log to find dates and times of
named transactions.
This option is not supported under SQL 7.0.
Select this check box to include the named transaction in the
restore; otherwise the restore will stop immediately before the
named transaction is restored.
This option is only available if you select the Restore log up to
named transaction option.
This option is not supported under SQL 7.0.
Found after Select this check box to specify a date and time after which the
restore operation is to search for the named transaction. For
example, if you specify a restore from a log up to the named
transaction AfternoonBreak, found after 6/02/2000, 12:01 p.m.,
then the restore operation will not search for AfternoonBreak
until after that time.
This option is only available if you selected the Restore log up to
named transaction option.
This option is not supported under SQL 7.0.
Check selections Click this button to have Backup Exec verify or complete the
selections required to successfully restore SQL databases. After
making your database restore selections, use this feature to verify
the database selections are valid. If there are selection issues,
Backup Exec notifies you of the error or errors and then corrects
them for you.
Guide Me Click this to start a wizard that helps you select restore job
properties for SQL.
Related Topics:
“About restoring SQL databases and filegroups” on page 1366.
“Restoring from SQL transaction logs up to a point in time” on page 1368
“Restoring from SQL 2000 or SQL 2005 transaction logs up to a named transaction” on
page 1369
1365

About restoring SQL databases and filegroups
“Restoring from SQL filegroup backups” on page 1370
About restoring SQL databases and filegroups
You can restore a database using one job or using multiple jobs to restore all of the
backup sets, depending on the types of backup used to protect the database or filegroup.
To restore a database using one job, select all the backup sets that you want to apply,
including the full backup, any differential backups, and any log backups, and select the
Leave database ready to use option. Additional transaction logs cannot be restored.
Single-job restores and multiple-job restores can both be used in redirected restore
operations.
Some restore operations must be completed using separate restore jobs to recover data.
These operations include
■ Restoring a database or a primary filegroup from a filegroup backup. Separate
restore jobs must be used to restore the primary filegroup, to restore the rest of the
filegroup backup sets, and to restore the transaction logs.
Caution SQL 7.0 databases cannot be restored using only filegroups and log backups.
SQL 7.0 databases must have at least one full database backup in order to be
restored. If the database has been deleted or does not exist, restore the full
database backup, and then restore all the filegroup and log backups.
■ Restoring a nonprimary filegroup. After running a Log No Truncate backup, separate
restore jobs must be used to restore the missing filegroup from full and differential
backups of the filegroups, and to restore the transaction logs.
If you use multiple jobs to restore a database, make sure that you specify the recovery
completion state Leave the database nonoperational. Additional transaction logs can be
restored for all the jobs except the last one, for which you should specify the recovery
completion state Leave database ready to use. Additional transaction logs cannot be
restored.
SQL database files contain unused space so that the disk file does not have be grown
every time a small amount of data is added to the database. SQL fills the unused space
with zeros. When SQL databases are restored, it is not known how much of the file will
actually be used by the restored data, so SQL creates the required database files on disk
and then fills them with zeros.
With very large databases this process can take several hours to complete. During this
time Backup Exec reports that no data is being transferred, and the Byte count field in
the Job Monitor view is not updated. When SQL has completed filling the files with zeros,
the restore job continues. This occurs for all database restores but is noticeable only on
very large databases.
1366 Administrator’s Guide

Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
About restoring SQL databases and filegroups
For steps on how to create the restore job, and for descriptions of all the options for
restoring SQL data, see “Redirecting restores for SQL” on page 1376.
Note SQL 7.0 database backups can be restored to SQL 2000 and SQL 2005, but SQL 2000
and SQL 2005 backups cannot be restored to SQL 7.0.
Related Topics:
“Restoring data” on page 483
“Restoring from SQL transaction logs up to a point in time” on page 1368
“Restoring from SQL 2000 or SQL 2005 transaction logs up to a named transaction” on
page 1369
“Restoring from SQL filegroup backups” on page 1370
“Redirecting restores for SQL” on page 1376
Restoring from SQL database backups
If the database is using the simple recovery model, there are no transaction log backups
to restore. You only need to restore the most recent full database backup and if you were
running differential database backups, restore the most recent differential database
backup. For details on all other restore options, see “Restoring data” on page 483.
Note Restoring a full SQL 2005 database backup over an existing SQL 2005 database
with active database snapshots will eliminate all existing database snapshots for
the SQL 2005 database being restored. For more information, see “Reverting SQL
2005 databases using database snapshots” on page 1381.
To restore from SQL database backups
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
4. In the restore selections list, select the most recent full database backup set, and the
most recent differential database backup set, if any, to restore.
5. On the Properties pane, under Settings, click Microsoft SQL.
6. On the Restore Job Properties for SQL dialog box, select the recovery completion
state Leave database operational. No additional transaction logs can be restored.
1367

About restoring SQL databases and filegroups
For information on other SQL restore options, see “Setting restore options for SQL”
on page 1362.
7. Start the restore job or select other restore options from the Properties pane.
Related Topics:
“About restoring SQL databases and filegroups” on page 1366
“About SQL 2005 database snapshots” on page 1358
“Reverting SQL 2005 databases using database snapshots” on page 1381
Restoring from SQL transaction logs up to a point in time
You can restore transactions from a transaction log up to and including a point in time in
the transaction log. After the point in time is reached, recovery from the transaction log
is stopped. To find dates and times of transactions, check your client application event
log.
If the specified point in time is later than the time contained in the most recent
transaction log being restored, then the restore operation succeeds, but a warning is
generated and the database remains in an intermediate state. If the specified point in
time is before the time contained in the transaction log or logs being restored, no
transactions are restored.
To restore from SQL transaction logs up to a point in time
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
4. In the restore selections list, select the most recent full database backup set, and the
most recent differential database backup set, if any, and all the log backup sets you
want to restore.
5. On the Properties pane, under Settings, click Microsoft SQL.
6. On the Restore Job Properties for SQL dialog box, select the recovery completion
state Leave database operational. No additional transaction logs can be restored.
7. Select Point in time log restore, and then select a date and time.
For information on selecting other options, see “Setting restore options for SQL” on
page 1362.
1368 Administrator’s Guide

Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
About restoring SQL databases and filegroups
8. Start the restore job or select other restore options from the Properties pane.
Related Topics:
“Restoring data” on page 483
“About restoring SQL databases and filegroups” on page 1366
Restoring from SQL 2000 or SQL 2005 transaction logs up to a
named transaction
If you are running either SQL 2000 or SQL 2005, you can restore transactions from a
transaction log up to and including a named transaction (or mark). After the named
transaction is reached, recovery from the transaction log is stopped.
Since named transactions do not necessarily have unique names, you can also specify a
date and time after which the restore operation is to search for the named transaction.
For example, if you specify a restore from a log up to the named transaction
AfternoonBreak, found after 6/02/2000, 12:01 p.m., then the restore operation will not
search for AfternoonBreak until after that time. To find dates and times of named
transactions, check your client application event log.
If the named transaction is not found, then the restore operation succeeds, but a warning
is generated and the database remains in an intermediate state.
The names of transactions are case-sensitive. Make sure you enter the correct upper- and
lower-case characters when specifying a named transaction.
To restore from SQL 2000 or SQL 2005 transaction logs up to a named transaction
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
4. In the restore selections list, select the most recent full database backup set, and the
most recent differential database backup set, if any, and all the log backup sets you
want to restore.
5. On the Properties pane, under Settings, click Microsoft SQL.
6. On Restore Job Properties for SQL, select the recovery completion state Leave
database ready to use. Additional transaction logs cannot be restored.
1369

About restoring SQL databases and filegroups
7. Select Restore log up to named transaction, and then enter the name of the
transaction.
The names are case-sensitive. Make sure you enter the correct upper- and lower-case
characters.
8. To include the named transaction in the restore, select Include the named
transaction.
9. To specify a particular named transaction in the log, select Found after and then
select a date and time.
If a date and time are not entered, recovery from the transaction log is stopped at the
first transaction with the specified name.
For information on other SQL restore options, see “Redirecting restores for SQL” on
page 1376.
10. Start the restore job or select other restore options from the Properties pane.
Related Topics:
“Restoring data” on page 483
“About restoring SQL databases and filegroups” on page 1366
Restoring from SQL filegroup backups
With filegroup backups, you can restore the entire database, a primary filegroup, a
filegroup containing a deleted or changed table, and a nonprimary filegroup.
Caution SQL 7.0 databases cannot be restored using only filegroups and log backups.
SQL 7.0 databases must have at least one full database backup in order to be
restored. If the database has been deleted or does not exist, restore the full
database backup, and then restore all the filegroup and log backups.
The following are conditions for filegroup restores:
■ All filegroups must be restored to the same point in time. For example, if a table is
deleted from a filegroup, you cannot restore that filegroup to a point in time before
the table was deleted and then leave it at that time; you must continue restoring the
filegroup to the same point in time shared by all existing filegroups.
To be able to restore a filegroup to the same point in time as the other filegroups, run
one of the following log backups:
■ If the database is intact, run a Log backup.
1370 Administrator’s Guide

Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
About restoring SQL databases and filegroups
■ If any files or filegroups are missing, run a Log - No Truncate backup.
Note If the primary filegroup is missing, the log backup methods are unavailable. You
can restore the database only up to the last log backup.
■ Filegroup restores can be redirected to a different server, but the database file paths
cannot be changed. For example, if the filegroup was backed up from G:\SQLDATA
then the filegroup must be restored to G:\SQLDATA, regardless of the server the
restore is redirected to.
The options Restore all databases to default drive and Restore all database files to
the target instance’s data location on the Restore Job Properties for SQL dialog box
do not apply to filegroup restores. Filegroups must be restored to the same drive
letter and path that they were backed up from.
■ When restoring from filegroup backups, separate restore jobs are required.
■ Previous versions of Backup Exec cannot restore filegroup backups made with this
release of Backup Exec.
■ If using SQL 2000 or SQL 2005 and restoring from filegroup backups, separate
restore jobs are required.
Related Topics:
“Restoring the entire database, a missing primary filegroup, or a filegroup containing a
deleted or changed table” on page 1371
“Restoring a missing or corrupted nonprimary filegroup” on page 1372
Restoring the entire database, a missing primary filegroup, or a
filegroup containing a deleted or changed table
Use the following steps to restore an entire database (SQL 2000 and SQL 2005 only), a
missing primary filegroup or a filegroup containing a deleted or changed table.
To restore the entire database (SQL 2000 and SQL 2005 only), a missing primary filegroup,
or a filegroup containing a deleted or changed table
Use separate restore jobs to restore the primary filegroup, the rest of the filegroup
backup sets, and the transaction logs.
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
1371

About restoring SQL databases and filegroups
4. In the restore selections list, select the backup set containing the primary filegroup.
5. On the Properties pane, under Settings, click Microsoft SQL.
6. On the Restore Job Properties for SQL dialog box, select the recovery completion
state Leave database nonoperational but able to restore additional transaction
logs. For information on other SQL restore options, see “Redirecting restores for
SQL” on page 1376.
7. Start the restore job.
8. After the primary filegroup is restored, select the rest of the filegroup backup sets
containing the latest full and differential backups.
9. On the Restore Job Properties for SQL dialog box, select the recovery completion
state Leave database nonoperational but able to restore additional transaction
logs, and then start the restore job.
10. When the full and differential backups are restored, select the backup set containing
the transaction logs.
11. On the Restore Job Properties for SQL dialog box, select the recovery completion
state Leave database operational and restore all of the transaction logs, or select
Point in time log restore or Restore log up to named transaction.
12. Start the restore job or select other restore options from the Properties pane. For
information on other restore options, see “Restoring data” on page 483.
Related Topics:
“Restoring a missing or corrupted nonprimary filegroup” on page 1372
“About restoring SQL databases and filegroups” on page 1366
Restoring a missing or corrupted nonprimary filegroup
To restore a missing or corrupted nonprimary filegroup
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Properties pane, under Source, click Selections.
1372 Administrator’s Guide

4. In the backup selections list, select the database.
5. On the Properties pane, under Settings, click Microsoft SQL.
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
About restoring SQL databases and filegroups
6. Select the backup method Log No Truncate, select None for a consistency check, and
then start the backup job.
7. After the Log No Truncate backup is complete, restore the missing or corrupted
filegroup by selecting the filegroup backup sets containing the latest full and
differential backups, and the transaction log backups.
8. On the Restore Job Properties for SQL dialog box, select the recovery completion
state Leave database operational. No additional transaction logs can be restored.
9. Start the restore job or select other restore options from the Properties pane, and
then start the restore job.
Related Topics:
“Restoring the entire database, a missing primary filegroup, or a filegroup containing a
deleted or changed table” on page 1371
“About restoring SQL databases and filegroups” on page 1366
“Restoring data” on page 483
1373

About restoring SQL databases and filegroups
Restoring the SQL master database
If the master database is damaged, symptoms may include:
■ An inability to start SQL.
■ Segmentation faults or input/output errors.
■ A report generated by SQL Database Consistency Checker utility (DBCC).
If you can still start SQL, you can restore the latest copy of the master database backup
using the Automate master database restore option in Backup Exec’s Restore Job
Properties for SQL dialog box and then restore any other databases, if needed.
If the master database is critically damaged and SQL cannot be started, rather than
running the Rebuild Master utility, or reinstalling SQL to be able to restart SQL, you can
replace the corrupted or missing databases with the copies of the master and model
databases that Backup Exec automatically creates and updates whenever backups of
those databases are run. After SQL is running again, you can restore the latest copy of
the master database using Backup Exec’s Automate master database restore option, and
then restore any other databases, if needed.
If copies of the master and model databases were not made, then you must use
Microsoft’s rebuildm.exe utility to rebuild the master database and start SQL.
Because all changes made to the master database after the last backup was created are
lost when the backup is restored, the changes must be reapplied. If any user databases
were created after the master database was backed up, those databases cannot be
accessed until the databases are restored from backups or reattached to SQL.
To restart SQL using database copies
1. Verify that the database copies are present.
The database copies are named master$4idr, mastlog$4idr, model$4idr, and
modellog$4idr and are found in the following locations:
In a default installation of SQL
2000, the databases are in:
In a named instance of SQL
2000, the databases are in:
In the first installation of SQL
2005, the databases are in:
In a second installed instance of
SQL 2005, the databases are in:
C:\Program Files\Microsoft SQL
Server\MSSQL\Data\*.*
C:\Program Files\Microsoft SQL
Server\MSSQL$Instance_Name\Data\*.*
C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\*.*
C:\Program Files\Microsoft SQL
Server\MSSQL.2\MSSQL\Data\*.*
1374 Administrator’s Guide

In a default installation of
SQL 7.0, the databases are in: C:\MSSQL7\Data
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
About restoring SQL databases and filegroups
If necessary, restore the master and model database copies from a backup set to the
same directory that the original master and model databases are in.
2. Using the Windows Explorer, browse to the default data directory and delete the
following files:
■ master.mdf
■ mastlog.ldf
■ model.mdf
■ modellog.ldf.
3. Open a command prompt window, and delete the original master and model
databases and their transaction logs.
4. Rename the copies of the databases back to their original names. The database
names are as follows:
Copied database name Original database name
master$4idr master.mdf
master$4idr mastlog.ldf
model$4idr model.mdf
modellog$4idr modellog.ldf
Do not use read-only files. The SQL services will not start with read-only files.
5. If you are using SQL 2000 or SQL 2005, use the SQL Service Control Manager to start
SQL Server. If you are using SQL 7.0, use the SQL Server Service Manager to start
SQL.
6. Continue with the next procedure to restore the latest changes to the master
database.
1375

About restoring SQL databases and filegroups
To restore the master database
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
4. On the restore selections list, select the backup set containing the last master
database backup.
5. On the Properties pane, under Settings, click Microsoft SQL.
6. On the Restore Job Properties for SQL dialog box, select Automate master database
restore.
All existing users are logged off, and SQL Server is put into single-user mode.
When this option is selected, only the master database can be restored; if this option
is selected for any other database, those jobs will fail.
If Backup Exec does not have access to the SQL registry keys
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server and
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer, then a restore to the
default directory may not work, and the option Automate master database restore on
the restore job properties for SQL will not work. To ensure that Backup Exec has
access rights, verify that the account that Backup Exec uses has administrator rights
to the computer that is running SQL.
7. Select a consistency check to be run after the restore.
8. Start the restore job.
After the restore, SQL restarts in multi-user mode.
Related Topics:
“Restoring data” on page 483
Redirecting restores for SQL
You can redirect the following:
■ A database backup to a different server, database, or instance.
■ Differential and log backups to wherever the associated database is restored.
1376 Administrator’s Guide

Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
About restoring SQL databases and filegroups
■ One or more filegroups in a backup to a different server or instance. Filegroups can
be redirected to a different server, but the database file paths cannot be changed. For
example, if the filegroup was backed up from G:\SQLDATA, then it must be restored
to G:\SQLDATA, even if it is redirected to another server. Filegroups must be restored
to the same drive letter and path that they were backed up from.
Single-job restores and multiple-job restores can both be used in redirected restore
operations.
To redirect a restore
1. Follow the instructions for the appropriate restore:
■ “Restoring from SQL database backups” on page 1367.
■ “Restoring from SQL transaction logs up to a point in time” on page 1368.
■ “Restoring from SQL 2000 or SQL 2005 transaction logs up to a named
transaction” on page 1369.
■ “Restoring from SQL filegroup backups” on page 1370.
2. After selecting options on the Restore Job Properties dialog box, on the Properties
pane, under Destination, click Microsoft SQL Redirection.
3. Select the appropriate options as follows, and then start the redirected restore job or
select other restore options from the Properties pane:
Redirect Microsoft SQL
Server sets
Select this checkbox to enable redirection of SQL backup sets.
Server Select this checkbox to redirect this restore to a different server.
After checking the checkbox, type the target server name.
You can redirect a full database backup to a different server or
database; however, if the drive configuration is different from
when the database backup was created, you must select either
Default drive for restoring database files or Restore all
database files to the target instance’s data location on the
Restore Job Properties for SQL dialog box (see Setting restore
options for SQL on page 1362).
Instance Select this checkbox to redirect this restore to a named instance.
After checking the checkbox, type the instance name. If you are
restoring to the default instance, leave the field empty.
This option is not supported under SQL 7.0.
1377

About restoring SQL databases and filegroups
Database Select this checkbox to redirect the restore to a different
database on the destination server. After checking the check
box, type the destination database name.
You can redirect a full database backup to a different server
and/or database; however, if the drive configuration is different
from when the database backup was created, you must select
either Default drive for restoring database files or select
Restore all database files to the target instance’s data location
on the Restore Job Properties for SQL dialog box (see
“Redirecting restores for SQL” on page 1376).
If you are restoring a differential or log backup, and the
associated database backup was restored to a different server,
enter the new database name.
Use alternate drive Select this option to select a default drive to which SQL database
files can be restored.
When a SQL database is backed up, the physical file names
(which include the directory path) of the files that make up the
database are stored in the backup set by SQL. For example, for
the logical file pubs, the physical file name is stored as
E:\MSSQL7\DATA\pubs.mdf. If the database must later be
restored, SQL uses these same physical file names to target the
restore to. During a restore, Backup Exec automatically creates
any necessary subdirectories that do not exist.
However, if the drive where one or more of the database files
previously resided no longer exists, Backup Exec moves those
files to their original directory path, but on the default drive
specified. Using the same example, if the default drive C is
specified, then the file with the original directory path of
E:\MSSQL7\DATA\pubs.mdf is restored to
C:\MSSQL7\DATA\pubs.mdf.
If no default drive is specified in this situation, the job will fail.
Only when original drive
does not exist
Even when original drive
does exist
Select this option to use the alternate drive selected in Use
alternate drive when the drive from which the database was
originally backed up does not exist.
Select this option to restore all database files to their original
directory path on the alternate drive selected in Use alternate
drive, even if the drive where they originally resided exists.
Do not select this option when restoring filegroups. Filegroups
must be restored to the same drive letter and path that they
were backed up from.
1378 Administrator’s Guide

Use destination instance’s
default data directory
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
About restoring SQL databases and filegroups
Select this option to restore files to the default data and log
directories of the destination instance. For example, if you are
restoring a database to a different instance of SQL, you would
select this option to move the database files to the correct
location for the new instance.
If this option is not selected, then the files are restored to the
directory that the master database is in.
Do not select this option when restoring filegroups. Filegroups
must be restored to the same drive letter and path that they
were backed up from.
Use this path Select this option to restore the database to a specific location on
disk.
To use this option, enter a drive letter and its corresponding
path. For example, C:\temp. You can also click the ellipsis button
and browse to a disk location. All paths entered are maintained
in the Use this path drop-down list, which can be used for future
redirected database restore jobs.
Server logon account To restore to a server, use a Backup Exec logon account that
stores the credentials of a Windows user account. The Windows
user account must have been granted the System Administrator
role on the SQL instance. The default logon account is displayed.
To use another logon account, click Change. For more
information about logon accounts, see “Using Backup Exec logon
accounts for SQL resources” on page 1337.
SQL logon account If you are using SQL Server Authentication, use a Backup Exec
logon account that stores the credentials of the SQL user
account. Apply the Backup Exec logon account for the Windows
user account to the Windows server that SQL is installed on, and
then apply the logon account for the SQL user account to the
SQL instance.
To use another logon account, click Change. To remove the SQL
logon account displayed in this field, click Clear. For more
information about logon accounts, see “Using Backup Exec logon
accounts for SQL resources” on page 1337.
Retain replication
information
Check this checkbox to retain the default settings of the
database during a redirected database restore job. By default,
Backup Exec retains default database settings during database
restore jobs, except when database restore jobs are redirected.
1379

About restoring SQL databases and filegroups
Check selections Click this button to have Backup Exec verify your SQL database
restore selections. If selection errors are found, Backup Exec
notifies you of the error or errors and then attempts to correct
them for you.
Related Topics:
“Restoring data” on page 483
“About restoring SQL databases and filegroups” on page 1366
1380 Administrator’s Guide

Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
About restoring SQL databases and filegroups
Reverting SQL 2005 databases using database snapshots
SQL 2005 database snapshots created with Backup Exec can be used to revert a SQL 2005
database back to the state it was in at a previous point in time, without having to run a
full database restore job.
When viewed by resource in the Restore Job Properties pane, SQL 2005 database
snapshots appear as backup sets, in chronological order with the most recent snapshot
appearing first. The word SNAPSHOT appears in the backup set description.
How SQL 2005 database snapshots appear in the Restore Job Properties pane
The following caveats apply when reverting a database:
■ You cannot undo a SQL 2005 database that has been reverted.
■ Before reverting a database, Backup Exec deletes all existing database snapshots,
including those created with SQL 2005, with the exception of the snapshot used for
the revert. After being deleted, the database snapshots cannot be recovered.
■ You cannot redirect a database snapshot restore job.
To revert a SQL 2005 database using database snapshots
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
1381

About restoring SQL databases and filegroups
4. Select a database snapshot.
After you click Run Now, all previous SQL 2005 database snapshots (including those
created by SQL 2005) are deleted, and the database is reverted. After the revert
completes, the SQL 2005 database cannot be returned to its previous state.
5. Click Run Now.
Related Topics:
“Restoring data” on page 483
“About restoring SQL databases and filegroups” on page 1366
1382 Administrator’s Guide

Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting default backup and restore options for SQL
Setting default backup and restore options for SQL
You can use the defaults set by Backup Exec during installation for all SQL backup and
restore jobs, or you can choose your own defaults. You can also change the defaults for
any specific backup or restore job.
To set default backup and restore options for SQL
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Microsoft SQL.
3. Select the appropriate options:
Backup method ◆ Full - Back up entire database or filegroup. Select this option
to back up the entire database or filegroup. See “Backing up
SQL databases” on page 1352. This option is selected by
default.
◆ Log - Back up transaction log. Select this option to back up
only the data contained in the transaction log; it does not
back up database data. After the transaction log is backed up,
committed transactions are removed (truncated). See
“Backing up SQL transaction logs” on page 1357.
◆ Log No Truncate - Back up transaction log - no truncate.
Select this method only when the database is corrupted or
database files are missing. Since the Log No Truncate method
does not access the database, you can still back up
transactions that you may not be able to access when the
database is in this state. You can then use this transaction
log backup along with the database backup and any previous
transaction log backups to restore the database to the point
at which it failed; however, any uncommitted transactions
are rolled back.
The Log No Truncate method does not remove committed
transactions after the log is backed up. See “Backing up SQL
transaction logs” on page 1357.
◆ Differential - Back up database or filegroup changes only.
Select this option to back up only the changes made to the
database or filegroup since the last full backup. Because
differential backups allow the restore of a system only to the
point that the differential backup was created, you should
also create multiple log backups between the differential
backups. See “Backing up SQL databases” on page 1352.
1383

Setting default backup and restore options for SQL
Consistency check before
backup
Continue with backup if
consistency check fails
Select a consistency check to run before a backup.
◆ None. Select this option if you do not want a consistency
check to run before a backup. Symantec strongly
recommends that you always run a consistency check either
before or after the backup. This option is selected by default.
◆ Full check, excluding indexes. Select this option to exclude
indexes from the consistency check. If indexes are not
checked, the consistency check runs significantly faster but
is not as thorough. Only the data pages and clustered index
pages for each user table are included in the consistency
check. The consistency of the nonclustered index pages is not
checked.
◆ Full check, including indexes. Select this option to include
indexes in the consistency check. Any errors are logged.
◆ Physical check only. Select this option to perform a low
overhead check of the physical consistency of the database.
This option only checks the integrity of the physical
structure of the page and record headers, and the
consistency between the pages' object ID and index ID and
the allocation structures.
Consistency check before backup is not supported under SQL
7.0.
Select this option to continue with the backup operation even if
the consistency check fails. You may want to continue with the
backup when the consistency check fails if you think that a
backup of the database in its current state is better than no
backup at all, or if you are backing up a very large database with
only a small problem in a table.
1384 Administrator’s Guide

Consistency check after
backup
Display filegroups when
creating new backup jobs
Use checksums on backup
(SQL 2005 only)
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting default backup and restore options for SQL
Select a consistency check to run after a backup. Because
database transactions can occur during or after the consistency
check, but before the backup runs, consider running a
consistency check after the backup to ensure the data was
consistent at the time of the backup.
◆ None. Select this option if you do not want a consistency
check to run after a backup. Symantec strongly recommends
that you always run a consistency check either before or after
the backup. This option is selected by default.
◆ Full check, excluding indexes. Select this option to exclude
indexes from the consistency check. If indexes are not
checked, the consistency check runs significantly faster but
is not as thorough. Only the data pages and clustered index
pages for each user table are included in the consistency
check. The consistency of the nonclustered index pages is not
checked.
◆ Full check, including indexes. Select this option to include
indexes in the consistency check. Any errors are logged.
◆ Physical check only. Select this option to perform a low
overhead check of the physical consistency of the database.
This option only checks the integrity of the physical
structure of the page and record headers, and the consistency
between the pages' object ID and index ID and the allocation
structures.
Consistency check after backup is not supported under SQL
7.0.
Select this checkbox if filegroups exist that you want to select
for backup. If this checkbox is not selected, filegroups are not
displayed as backup selections.
Select this option to have SQL 2005 add checksums to the SQL
2005 database data being backed up by Backup Exec. Adding
checksums to the data being backed up is required if you want to
use the option Run verify only; do not restore data. Using this
option, along with Run verify only; do not restore data, ensures
that during a restore of the SQL database, you are restoring from
a verified SQL 2005 backup.
1385

Setting default backup and restore options for SQL
Database snapshots to
keep
Create on-disk copies of
SQL backups to be placed
on the SQL server where
the database is located
(SQL 2005 only) Use this option to select the number of database
snapshots to keep on disk. As the threshold is met, older
database snapshots are deleted, which are then replaced with
new snapshots. Because database snapshots continue to grow as
the SQL 2005 database is updated, limiting the number of
snapshots enables you to minimize both the disk space and SQL
Server processing time that is required when the snapshots are
updated.
See “About SQL 2005 database snapshots” on page 1358.
Select this option to create an on-disk copy of the SQL database
being backed up. This option lets you simultaneously back up a
SQL database to storage media while also writing a copy of the
database to a disk path you specify in the Save to path box.
This option gives IT administrators the ability to back up SQL
databases while also providing database administrators with
copies of the database on disk, which can be used for such things
as tests and restores.
Save to path Enter a path in which to save on-disk copies of SQL backups.
Recovery completion state
◆ Leave database ready to use. Additional transaction logs
cannot be restored. Select this option when restoring the last
database, differential, or log backups in the restore sequence
in order to have the restore operation roll back all
uncompleted transactions. After the recovery operation, the
database is ready for use. If Leave database ready to use is not
performed, the database is left in an intermediate state and is
not usable.
If Leave database ready to use is selected when an
intermediate backup is being applied, you cannot continue to
restore backups. You must restart the restore operation from
the beginning.
This option is selected by default.
◆ Leave database nonoperational. Additional transaction logs
can be restored. Select this option during a restore if you
have additional differential or transaction log backups to be
restored in another restore job.
◆ Leave database in read-only mode. Select this option during
transaction log and database restores to create and maintain
a standby database. See your SQL documentation for
information on standby databases.
1386 Administrator’s Guide

Consistency check after
restore
Overwrite the existing
database
Related Topics:
“Setting backup options for SQL” on page 1347
“About restoring SQL databases and filegroups” on page 1366
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Setting default backup and restore options for SQL
◆ None. Select this option if you are doing sequential restores.
Do not run a consistency check after a restore until all
sequential restores have been done. If a consistency check is
selected during a restore, the restore will complete but the
consistency check will not be done. Check the job log for this
information.
If you need to recover the database after restores are
complete, select one of the following consistency checks
when you select the Leave database ready to use option.
◆ Full check, excluding indexes. Select this option to exclude
indexes from the consistency check. If indexes are not
checked, the consistency check runs significantly faster but
is not as thorough. Only the data pages and clustered index
pages for each user table are included in the consistency
check. The consistency of the nonclustered index pages is not
checked.
◆ Full check, including indexes. Select this option to include
indexes in the consistency check. Any errors are logged. This
option is selected by default.
◆ Physical check only. Select this option to perform a low
overhead check of the physical consistency of the database.
This option only checks the integrity of the physical
structure of the page and record headers, and the consistency
between the pages' object ID and index ID and the allocation
structures.
Consistency check after restore is not supported under SQL
7.0.
Select this check box to replace a database or file group, even if
another database or file group with the same name already
exists on the server. If Overwrite the existing database is not
specified for a restore, SQL performs a safety check to ensure
that a different database or file group is not accidentally
overwritten. Refer to your SQL documentation for more
information about the safety check that occurs when this option
is not selected.
1387

Preparing for disaster recovery of SQL Server
Preparing for disaster recovery of SQL Server
Backup Exec provides a quicker method for restoring SQL rather than running the
Rebuild Master utility or reinstalling SQL to restart SQL. Using Backup Exec, you can
replace the corrupted or missing databases with copies of the master and model
databases that Backup Exec automatically creates and updates whenever backups of
those databases are run. After SQL is running again, you can restore the latest copy of
the master database using Backup Exec’s Automate master database restore option, and
then restore any other databases, if needed.
If you purchased the Intelligent Disaster Recovery (IDR) option, then during an IDR
recovery of drive C, it will automatically replace the damaged databases with the copies
of the master and model databases. You can then restart SQL, and restore the latest
master database backup and any other databases that are necessary.
To prepare for disaster recovery if you are using SQL 2000 or SQL 2005, do the
following
■ Back up both system and user databases and transaction logs regularly.
Copies of the master and model databases are automatically created by Backup Exec
whenever you back up the master and model databases. Backup Exec places these
copies in the same directory that the databases are in, where they must remain in
order to be updated.
The following table includes information about MS SQL database locations:
MS SQL database locations
MS SQL Version Database location
A default installation of SQL 2000 C:\Program Files\Microsoft SQL
Server\MSSQL\Data\*.*
A named instance of SQL 2000 C:\Program Files\Microsoft SQL
Server\MSSQL$Instance_Name\Data\*.*
An initial installation of SQL 2005 C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\*.*
A second installed instance of SQL
2005
C:\Program Files\Microsoft SQL
Server\MSSQL.2\MSSQL\Data\*.*
1388 Administrator’s Guide

The copies of the master and model databases are named:
■ Master$4idr
■ Mastlog$4idr
■ Model$4idr
■ Modellog$4idr
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Preparing for disaster recovery of SQL Server
■ Back up the system drives that contain SQL instances.
Whenever you back up the system drive that contains a SQL instance, copies of the
master and model databases are backed up. Backing up the system drive that SQL is
on also backs up all the executables and registry settings needed for SQL to run.
■ Back up the master database whenever any changes are made to SQL.
■ Keep records of any service packs that have been installed.
■ Review “Returning to the last known good configuration” on page 655 to make sure
you are prepared to recover the entire server, not just SQL.
To prepare for disaster recovery if using SQL 7.0, do the following
■ Create a copy of the master and model databases, and place the copies in the same
directory that the databases are in (see “To create copies of the SQL 7.0 master and
model databases” on page 1390).
■ Back up both system and user databases and transaction logs regularly.
■ Back up the system drive that contains SQL.
Backing up the system drive that SQL is on also backs up all the executables and
registry settings needed for SQL to run.
■ Back up the master database whenever any changes are made to SQL.
■ Keep records of any service packs that have been installed.
■ Review “Returning to the last known good configuration” on page 655 to make sure
you are prepared to recover the entire server, not just SQL.
To perform a recovery, you will need
■ The latest backup of the SQL directory (\Program Files\Microsoft SQL
Server\MSSQL), and the Windows registry/System State.
■ The SQL database or filegroup backups, and differential and log backups.
■ An Administrator logon account (or an Administrator equivalent) during the
recovery.
1389

Disaster recovery of SQL
To create copies of the SQL 7.0 master and model databases
1. Use the SQL Server Service Manager to stop the SQL services.
2. Open a command prompt window, and copy the original master and model databases
and their transaction logs to the specified file names. In a default installation of SQL
7.0, the databases are in C:\MSSQL7\Data.
Type the following:
C:\ mssql7\data> copy master.mdf master$4idr
C:\ mssql7\data> copy mastlog.ldf mastlog$4idr
C:\ mssql7\data> copy model.mdf model$4idr
C:\ mssql7\data> copy modellog.ldf modellog$4idr
Related Topics:
“Disaster recovery of SQL” on page 1390
Disaster recovery of SQL
You can restore either the entire server, including the SQL databases, from full system
backups, or restore only the SQL databases to a newly installed or other available SQL
server.
Restoring the entire server including the SQL databases
Restoring the entire server, including the SQL databases has the added benefit of
recovering other applications and data that may have resided on the server at the time of
failure, and can be accomplished using one of the following methods:
■ Manual recovery of the Windows server, and then manual recovery of the SQL
databases. This method involves manually restoring the Windows server from full
system backups, and then recovering the SQL databases.
■ The Intelligent Disaster Recovery Option. This option provides an automated
method of restoring the Windows server as well as the SQL databases from full
system backups. See “About Microsoft SQL Server recovery notes” on page 1536.
1390 Administrator’s Guide

Restoring only the SQL databases
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Disaster recovery of SQL
■ To restore only the SQL databases to a newly-installed or other available server, the
server must be running on the same hardware platform (cross-platform restores are
not supported), and the same version of SQL with the same service pack level as the
original server.
■ To restore SQL databases to an existing installation of SQL with other active
databases, see “Redirecting restores for SQL” on page 1376.
Related Topics:
“Recovering SQL manually” on page 1392
1391

Disaster recovery of SQL
Recovering SQL manually
If necessary, restore the Windows computer by following the instructions in “Manual
disaster recovery of Windows computers” on page 658. After recovery of the Windows
computer is complete, or after the new server installation is available, recovery of the
SQL databases can begin.
In order to restore SQL databases, SQL must be running; however, SQL cannot be started
unless the master and model databases are present. You can restore the master and
model databases and start SQL using one of the following methods:
■ Rename the files created by Backup Exec that replace the master and model
databases. After the master and model databases are present on SQL, you must start
SQL, restore the master database with the Automate master database restore option,
and then restore all other databases.
■ Run the Rebuild Master utility (\Program Files\Microsoft SQL
Server\80\Tools\Binn\rebuildm.exe for SQL 2000, or
\MSSQL7\binn\rebuildm.exe for SQL 7.0) to rebuild the master database.
Note The Rebuild Master utility is not supported in SQL 2005; see your MS SQL 2005
documentation for setup options.
■ Reinstall SQL.
This topic only details how to restart SQL by using the copies of the master and model
databases made by Backup Exec. For more information on the Rebuild Master utility, or
on reinstalling SQL, refer to your MS SQL documentation.
If you are restoring to a new SQL installation, start with “To restore the master database”
on page 1376.
To restart SQL 2000 or SQL 2005 using database copies
1. Verify that the database copies are present.
The database copies are named master$4idr, mastlog$4idr, model$4idr, and
modellog$4idr and are found in the following locations:
A default installation of SQL
2000
C:\Program Files\Microsoft SQL
Server\MSSQL\Data\*.*
A named instance of SQL 2000 C:\Program Files\Microsoft SQL
Server\MSSQL$Instance_Name\Data\*.*
An initial installation of SQL
2005
C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\*.*
1392 Administrator’s Guide

A second installed instance of
SQL 2005
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Disaster recovery of SQL
If necessary, restore the master and model database copies from a backup set to the
same directory that the original master and model databases are in.
2. Using the Windows Explorer, browse to the default data directory and delete the
following files:
■ master.mdf
■ mastlog.ldf
■ model.mdf
■ modellog.ldf.
3. Rename the copies of the databases back to their original names. The database
names are as follows.
Do not use read-only files. The SQL services will not start with read-only files.
4. Use the SQL Service Control Manager to start SQL Server.
5. Continue with the next procedure to restore the latest changes to the master
database.
To restart SQL 7.0 using database copies
C:\Program Files\Microsoft SQL
Server\MSSQL.2\MSSQL\Data\*.*
Copied database name Original database name
master$4idr master.mdf
master$4idr mastlog.ldf
model$4idr model.mdf
modellog$4idr modellog.ldf
1. Verify that the database copies are present.
The database copies are named master$4idr, mastlog$4idr, model$4idr, and
modellog$4idr.
In a default installation of SQL 7.0, the databases are in C:\MSSQL7\Data.
1393

Disaster recovery of SQL
If necessary, restore the master and model database copies from a backup set to the
same directory that the original master and model databases are in.
2. Using the Windows Explorer, browse to the default data directory and delete the
following files:
■ master.mdf
■ mastlog.ldf
■ model.mdf
■ modellog.ldf.
3. Rename the copies of the databases back to their original names. The database
names are as follows.
Copied database name Original database name
master$4idr master.mdf
master$4idr mastlog.ldf
model$4idr model.mdf
modellog$4idr modellog.ldf
Do not use read-only files. The SQL services will not start with read-only files.
4. Use the SQL Server Service Manager to start SQL.
5. Continue with the next procedure to restore the latest changes to the master
database.
To restore the master database
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
4. On the restore selections list, select the backup set containing the last master
database backup.
5. On the Properties pane, under Settings, click Microsoft SQL.
1394 Administrator’s Guide

Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
Disaster recovery of SQL
6. On the Restore Job Properties for SQL dialog box, select Automate master database
restore.
All existing users are logged off, and SQL Server is put into single-user mode.
When this option is selected, only the master database can be restored; if this option
is selected for any other database, those jobs will fail.
If Backup Exec does not have access to the SQL registry keys
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server and
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer, then a restore to
the default directory may not work, and the option Automate master database
restore on the restore job properties for SQL will not work. To ensure that Backup
Exec has access rights, verify that the account that Backup Exec uses has
administrator rights to the computer that is running SQL.
7. Select a consistency check to run after the restore.
8. Start the restore job.
After the restore, SQL is restarted in multi-user mode.
9. Continue with the next procedure, restoring the remaining SQL databases.
To restore the remaining SQL databases
Do not select the master database for restore at this time.
If you are restoring the SQL databases from filegroup backups, go to “Restoring from
SQL filegroup backups” on page 1370.
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
4. Select all the backup sets that you want to apply, including the full backup, any
differential backups, and any log backups.
5. On the Properties pane, under Settings, click Microsoft SQL.
6. Select Leave database ready to use. Additional transaction logs cannot be
restored.
7. Select Overwrite the existing database.
1395

Disaster recovery of SQL
8. In the Consistency Check After Database Restore field, select Full check, including
indexes.
9. Start the restore job or select other options from the Properties pane. If the restore is
being redirected, see “Redirecting restores for SQL” on page 1376.
When all of the restore operations have completed successfully, then the recovery of
the SQL databases is complete.
After the recovery has been completed, Symantec strongly recommends that a full
database backup be performed as soon as possible.
Related Topics:
“Restoring data” on page 483
1396 Administrator’s Guide

Appendix
Symantec Backup Exec Agent
for Oracle on Windows or
Linux Servers
N
The Symantec Backup Exec Agent for Oracle on Windows or Linux Servers (Oracle Agent)
uses Oracle's Recovery Manager (RMAN) to protect Oracle databases. RMAN is an Oracle
utility.
About the Backup Exec Oracle Agent
The following features are available with the Oracle Agent:
■ The ability to initiate backup and restore operations:
■ From Backup Exec
■ From the RMAN console as a Database Administrator (DBA). Operations that the
DBA performs on the RMAN console are referred to as DBA-initiated operations.
You should refer to your Oracle documentation for information about RMAN.
■ Multiple data stream support for increased performance during backup and restore
operations.
■ RMAN recovery catalog support to manage the backup, restore, and recovery of
Oracle databases.
■ Oracle Real Application Cluster (RAC) support
The Backup Exec Oracle Agent supports Oracle database versions 9i (9.2 and later) and
10g. In addition, the Oracle Agent supports the following operating systems:
■ Windows 2000 and Windows Server 2003 (32-bit and 64-bit extended)
■ Red Hat Linux 4.0, 3.0, Advanced Server 2.1 (32-bit and 64-bit extended)
■ SuSE Linux 9.0, 8.2, 8.1, 8.0 - Enterprise/Standard, (32-bit and 64-bit extended)
1397

Installation and configuration requirements for the Oracle Agent
The following are not supported:
■ Tivoli Storage Manager (TSM) devices as storage devices for Oracle backup jobs.
■ The Oracle Management Server.
Related Topics:
“Installation and configuration requirements for the Oracle Agent” on page 1398
“About upgrading the Backup Exec Oracle Agent” on page 1411
“What to do when Oracle instance information changes” on page 1413
Installation and configuration requirements for the Oracle
Agent
The Oracle Agent is installed as a separate, add-on component of Backup Exec for
Windows Servers. To protect local or remote Oracle instances, you must install the
following Backup Exec options:
Installing components for the Oracle Agent
Install this agent In this location For more information
Backup Exec Oracle Agent On the media server See “Installing Backup Exec options to
the local computer” on page 85.
Backup Exec Remote
Agent for Windows
Systems
Backup Exec Remote
Agent for Linux and Unix
Servers
On remote Windows
computers
On remote Linux
computers
See “Installing the Remote Agent for
Windows Systems” on page 97.
See “Installing the Remote Agent for
Linux or UNIX Servers” on page 939.
1398 Administrator’s Guide

Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
Configuring the Oracle Agent on Windows computers
After you install the required agents, you must configure them for the Oracle Agent
before you can back up or restore any Oracle resources. Do one of the following:
Configuring the Oracle Agent
Platform For more information
For Oracle instances on remote
Windows computers
For Oracle instances on remote Linux
computers
See “Configuring the Oracle Agent on Windows
computers” on page 1399.
See “Configuring the Oracle Agent on Linux computers”
on page 1404.
You must then add the Oracle server name and logon account to the media server’s list of
authentication credentials. See “Configuring database access on the media server for
Oracle operations” on page 1408.
Related Topics:
“What to do when Oracle instance information changes” on page 1413
About upgrading the Backup Exec Oracle Agent on page 1411
About using the legacy Backup Exec Oracle Agent on page 1412
Configuring the Oracle Agent on Windows computers
Before you can back up or restore Oracle databases, you must use the Remote Agent
Utility to:
■ Configure information about the Oracle instances for the Oracle Agent.
■ Enable database access for the media server.
Whenever Oracle instance information changes, you must update the Remote Agent
Utility. If credential information is not updated or is incorrect, the error “Unable to
attach to a resource...” may appear when you run a backup job.
For Oracle RAC, run the Remote Agent Utility on each node and add information about
the instances. When Oracle RAC nodes are added or removed, you must enter
information about any changes to instances in the Remote Agent Utility.
Note When you use the Remote Agent Utility, the user account with which you are
logged in cannot be a member of the Oracle DBA group. If the user account is a
member of the Oracle DBA group, the credentials cannot be verified.
You must have administrator privileges to run the Remote Agent Utility.
1399

Configuring the Oracle Agent on Windows computers
To configure the Oracle Agent on Windows computers
1. On the computer on which the Remote Agent is installed, on the taskbar, click Start >
All Programs > Symantec Backup Exec for Windows Servers > Backup Exec
Remote Agent Utility.
When the Remote Agent Utility is running, an icon appears in the system tray. You
can double-click this icon to view the utility.
2. Click the Oracle tab.
Any instances that currently exist on the computer appear on the tab. You can edit or
delete these instances, or view information about the instances.
3. Do one of the following:
To add an Oracle instance
To edit an existing Oracle
instance
To delete an Oracle
instance
◆ Click New.
◆ Go to step 4.
◆ Select the instance that you want to edit.
◆ Click Edit.
◆ Go to step 4.
4. Complete the appropriate options as follows:
◆ Select the instance that you want to delete, and then click
Delete.
◆ Go to step 5.
Local instance name To add an instance, enter the name of the Oracle instance. If you
are editing an instance, you cannot change the instance name.
Note For Oracle RAC nodes, enter the name of each physical node
and the name of the virtual node.
The virtual node name appears on the media server in the
Backup Selections tree, under Oracle Real Application
Clusters.
The name is in the format RAC--, where
dbname is the database name, and dbid is the database ID.
1400 Administrator’s Guide

5. Click OK.
Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
Configuring the Oracle Agent on Windows computers
User name Type the user name for the Oracle instance.
If the credentials for the Oracle instance change, you must update
the credentials in this field.
For Oracle RAC nodes, enter the same set of credentials for all of
the nodes.
Password Type the password for the Oracle instance user name.
Confirm password Type the password again to confirm it.
Use recovery catalog Check Use recovery catalog if you plan to use the Oracle recovery
catalog.
The Oracle Agent supports the use of the RMAN recovery catalog
to manage the backup, restore, and recovery of Oracle databases.
If you choose not to use a recovery catalog, RMAN uses the target
database control file as the sole repository of metadata.
TNS name Type the Oracle Net Service name.
User name Type the user name for the Oracle recovery catalog.
Password Type the password for the Oracle recovery catalog.
Confirm password Type the password for the recovery catalog again to confirm it.
Media server name or IP
address
For DBA-initiated jobs, type the name or IP address of the Backup
Exec media server where you want to send the DBA-initiated
backup jobs.
You must use the same form of name resolution for all operations.
For example, if you use the IP address of this computer for backup
operations, you must also use the IP address for restore
operations. If you use the full computer name for backup
operations, you must also use the full computer name for restore
operations.
Job template name Type the name of the Backup Exec job template that you want the
DBA-initiated job to use for backup and restore operations. You
create the job template on the DBA-initiated Job Settings dialog
box on the Backup Exec media server. If you do not specify a job
template, the default job template is used.
For more information, see “Configuring DBA-initiated job settings
for Oracle” on page 1419.
1401

Configuring the Oracle Agent on Windows computers
To configure database access for Oracle operations on Windows computers
1. On the computer on which the Remote Agent is installed, on the taskbar, click Start >
All Programs > Symantec Backup Exec for Windows Servers > Backup Exec
Remote Agent Utility.
When the Remote Agent Utility is running, an icon appears in the system tray. You
can double-click this icon to view the utility.
2. Click the Database Access tab.
3. Complete the appropriate options as follows:
Enable media server
authentication for Oracle
and DB2 operations
Check Enable media server authentication for Oracle and DB2
operations to enter the credentials that the media server will use
for all operations on the Oracle server, including DBA-initiated
operations. The media server also uses these credentials for
authentication of the Oracle server.
You must check this option to enable Oracle operations between
the media server and this computer.
User name Type a user name that has administrative rights to this computer.
This logon account is what the media server uses when it connects
to this computer.
Note If you specify an IP address or a fully qualified computer
name as part of the user name, the Remote Agent Utility
may not be able to verify the user account. If the credentials
are incorrect, the error “Unable to attach to a resource...”
may appear when you run a backup or restore job.
You must add this computer name and logon account to the list of
authentication credentials for Oracle servers. See “Configuring
database access on the media server for Oracle operations” on
page 1408.
If the authentication fails when the Oracle resources are backed
up, the backup job fails. If the authentication fails when you
browse the backup sets for a restore job, then the backup sets
become unavailable, and you must run a DBA-initiated restore job
to restore data.
Password Type the password for this logon account, and then confirm it.
Note For security reasons, the logon credentials are not stored on
the remote computer.
1402 Administrator’s Guide

Use the full computer
name or IP address for
Oracle and DB2
operations
4. Click OK.
Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
Configuring the Oracle Agent on Windows computers
Check Use the full computer name or IP address for Oracle and
DB2 operations to use either the full computer name or IP address
for operations between the remote computer and the media
server. You must use the same form of name resolution for all
Oracle operations.
For example, if you use the IP address of this computer for backup
operations, you must also use the IP address for restore
operations. If you use the full computer name for backup
operations, you must also use the full computer name for restore
operations.
Name or IP address Type the full computer name or IP address for this computer.
For full computer names, the following rules apply:
◆ The maximum number of characters for each label (the text
between the dots) is 63
◆ The maximum total number of characters is 254, including the
dots, but excluding the \\
◆ The name cannot include the following characters: * | < >?
Use a custom port to
connect to the media
server during Oracle and
DB2 operations
Check Use a custom port to connect to the media server during
Oracle and DB2 operations to change the port that is used for
communications between this computer and the media server
during Oracle operations. By default, port 5633 is used.
If you change the port number on this computer, you must also
change it on the media server, and then restart the Backup Exec
Job Engine Service on the media server.
For information on how to change the port number on the media
server, see “Setting default backup network and security options”
on page 400.
Port number Type the port number to use for operation requests that are sent
to the media server.
5. For Oracle RAC installations, type the media server name or IP address that you want
to publish to.
The media server that you publish to lists the RAC databases in its backup selection
tree, under the node named Oracle Real Application Clusters.
If you do not enter a media server name or IP address to publish to, the RAC
databases are not listed in the media server’s backup selection tree.
See “Publishing the remote Windows computer to media servers” on page 919.
1403

Configuring the Oracle Agent on Linux computers
6. On the media server, add the name of the Oracle server and the user name that you
entered on the Database Access tab to the media server’s list of authentication
credentials.
See “Configuring database access on the media server for Oracle operations” on
page 1408.
Related Topics:
“About backing up Oracle resources” on page 1413
“About backing up Oracle RAC resources” on page 1414
“Configuring DBA-initiated job settings for Oracle” on page 1419
“Setting application defaults for Oracle” on page 1421
Configuring the Oracle Agent on Linux computers
Before you can back up or restore Oracle databases, you must use the Remote Agent
Utility to:
■ Configure information about the Oracle instances for the Oracle Agent.
■ Enable database access for the media server.
Whenever Oracle instance information changes, you must update the Remote Agent
Utility. If credential information is not updated or is incorrect, the error “Unable to
attach to a resource...” may appear when you run a backup job.
For Oracle RAC, you must run the Remote Agent Utility on each node and add
information about the instances before you can perform any backup or restore
operations. When Oracle RAC nodes are added or removed, you must enter information
about any changes to instances in the Remote Agent Utility.
Note When you use the Remote Agent Utility to enter Oracle credentials for an instance,
the user account with which you are logged in cannot be a member of the Oracle
DBA group. If the user account is a member of the Oracle DBA group, the
credentials cannot be verified.
To configure the Oracle Agent on Linux computers
1. On the Linux computer on which the Oracle instances are installed, open a Terminal
window.
2. Type the following command:
cd /opt/VRTSralus/bin
1404 Administrator’s Guide

Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
Configuring the Oracle Agent on Linux computers
3. To start the Remote Agent Utility, type the following command:
./AgentConfig
4. Type 2 to select Configure Oracle instance information, and then press Enter.
Any instances that currently exist on the computer are discovered. You can edit or
delete these instances, or view information about the instances.
5. Do one of the following:
If an existing Oracle
instance is discovered
If no instances are
discovered
6. Do any of the following:
Edit an existing Oracle
instance
Proceed to step 6 to edit or delete the instance, or to view
information about the instance.
Proceed with step 7.
Type 2, and then follow the prompts.
Delete an Oracle instance Type 3, and then follow the prompts.
View Oracle entries Type 4.
The following information is listed:
◆ Name of the instance
◆ Logon name for the instance
◆ IP address of the default media server name for DBA-initiated
operations
◆ Name of the DBA-initiated job template
7. Type 1 to select the Add a new Oracle Instance option, and then press Enter.
8. Enter the name of the Oracle instance in upper case characters.
For example, ORACLENAME.
9. Enter the user name for the Oracle instance.
If the credentials for the Oracle instance are changed, you must update the
credentials in this field. For Oracle RAC nodes, enter the same set of credentials for
all of the nodes.
1405

Configuring the Oracle Agent on Linux computers
When you use the Remote Agent Utility to enter the Oracle credentials for an
instance, the credentials cannot be verified if the user account with which you are
logged in is a member of the Oracle DBA group. If the credentials are incorrect, the
error “Unable to attach to a resource...” may appear when you run a backup job.
10. To display the Oracle database in a media server’s backup selection list under
Favorite Resources, type the media server name or IP address to which you want the
remote computer to publish to.
The media server lists the Oracle database under Favorite Resources, under the
Linux/Unix node, under .
Oracle RAC databases are listed in the media server’s backup selection list, under the
node Oracle Real Application Clusters. They are not listed under Favorite Resources.
11. When prompted, specify if you want to use a recovery catalog.
The Oracle Agent supports the use of the RMAN recovery catalog to manage the
backup, restore, and recovery of Oracle databases. If you choose not to use a recovery
catalog, RMAN uses the target database control file as the sole repository of
metadata.
If you specify a recovery catalog, any database that you want to back up must be
registered in the recovery catalog before you can run backup jobs from the media
server.
12. To use a recovery catalog, type the recovery catalog name and a user name and
password for the recovery catalog.
13. To use a customized DBA-initiated job settings template, type the name of the
template.
See “Configuring DBA-initiated job settings for Oracle” on page 1419.
14. Do one of the following:
To commit the new entry to the configuration
file
15. To add more instances, repeat step 7 - step 13.
Type Y, and then press Enter.
To cancel this entry Type N, and then press Enter.
1406 Administrator’s Guide

Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
Configuring the Oracle Agent on Linux computers
To configure database access for Oracle operations on Linux systems
1. In the Remote Agent Utility, to select Configure database access, type 1 and press
Enter.
2. Type the user name that is in the beoper group on the Linux system.
For more information about the beoper group, see “About creating the beoper group”
on page 940.
If the authentication fails when the Oracle resources are backed up, the backup job
fails. If the authentication fails when you browse the backup sets for a restore job,
then the backup sets become unavailable, and you must run a DBA-initiated restore
job to restore data.
3. Type the password for this logon account, and then confirm it.
The logon credentials are not stored on this computer.
4. Type the full computer name or IP address for this computer.
You must use the same form of name resolution for all Oracle operations. For
example, if you use the IP address of this computer for backup operations, you must
also use the IP address for restore operations. If you use the full computer name for
backup operations, you must also use the full computer name for restore operations.
5. When prompted, specify if you want to use a custom port to connect to the media
server communications between this computer and the media server during Oracle
operations.
Port 5633 is used by default. If you change the port number on this computer, you
must also change it on the media server, and then restart the Backup Exec Job Engine
Service on the media server.
For information on how to change the port number on the media server, see “Setting
default backup network and security options” on page 400.
6. Do one of the following:
To commit the Oracle operation settings to
the configuration file
Type Y, and then press Enter.
To cancel this entry Type N, and then press Enter.
7. On the media server, add the Oracle server name and the logon account name to the
list of authentication credentials.
1407

Configuring database access on the media server for Oracle operations
See “Configuring database access on the media server for Oracle operations” on
page 1408.
Related Topics:
“About backing up Oracle resources” on page 1413
“About backing up Oracle RAC resources” on page 1414
“Configuring DBA-initiated job settings for Oracle” on page 1419
“Setting application defaults for Oracle” on page 1421
Configuring database access on the media server for Oracle
operations
You must add the Oracle server name and the logon account name to the media server’s
list of Oracle servers and authentication credentials. The media server has database
access for operations on Oracle instances that are included in the authentication list.
Before you start any backup or restore operations, on the computer on which the Oracle
instances are installed, make sure that you use the Remote Agent Utility to configure
instance information and database access.
The logon account name must have administrative rights or backup operator rights to
the Oracle server. If the user name is incorrect or is not provided, or if it does not have
the appropriate rights, then you cannot perform Oracle backup or restore operations to
that computer.
Note For Oracle RAC nodes, enter the virtual node name and all of the physical node
names for the logon account name. You can view the virtual node name in the
backup selections list. It is in the form RAC--.
To configure database access on the media server for Oracle operations
1. On the media server, on Tools menu, click Options.
2. On the properties pane, under Job Defaults, click Oracle.
3. Click the Modify list button.
On the Authentication Credentials for Oracle and DB2 Servers dialog box, you can
add, edit, or delete a server name and a logon account.
4. Click New.
5. Enter the name of the Oracle server on which the instance is installed.
1408 Administrator’s Guide

Configuring database access on the media server for Oracle operations
For Oracle RAC nodes, enter the virtual node name and all of the physical node
names for the logon account name.
6. To add the logon account name, do one of the following:
Click the arrow Select the logon account name that you want to add.
Click New On the Logon Account Selection dialog box, click New.
For more instructions, see “Creating a Backup Exec logon account”
on page 149.
Use the same logon account format that you use when you enter the logon account
name on the Database Access tab in the Remote Agent Utility. For example, if you
entered Domainname\Username on the Remote Agent Utility, use that same format
on the list of authentication credentials.
7. Click OK.
8. On the Authentication Credentials for Oracle and DB2 Servers dialog box, click OK.
Related Topics:
“Editing an Oracle server name or logon account on the media server’s list of
authentication credentials” on page 1409
“What to do when Oracle instance information changes” on page 1413
“Configuring the Oracle Agent on Windows computers” on page 1399
“Configuring the Oracle Agent on Linux computers” on page 1404
“Deleting an Oracle server name or logon account from the media server’s list of
authentication credentials” on page 1411
“About backing up Oracle resources” on page 1413
Editing an Oracle server name or logon account on the media
server’s list of authentication credentials
If the Oracle server name or the logon account name for the Oracle server changes, you
must update the media server’s list of Oracle servers and authentication credentials.
Make the same changes on the Oracle server by using the Remote Agent Utility to
configure instance information and database access.
Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
1409

Configuring database access on the media server for Oracle operations
The logon account name must have administrative rights or backup operator rights to
the Oracle server. If the user name is incorrect or is not provided, or if it does not have
the appropriate rights, then you cannot perform Oracle backup or restore operations to
that computer.
To edit an Oracle server name or a logon account on the media server’s list of
authentication credentials
1. On the media server, on Tools menu, click Options.
2. On the properties pane, under Job Defaults, click Oracle.
3. Click the Modify list button.
On the Authentication Credentials for Oracle and DB2 Servers dialog box, you can
add, edit, or delete a server name and a logon account.
4. Select the item that contains the server name or logon account that you want to edit.
5. Click Edit.
6. Change the server name, or change the logon account name.
See “Editing a Backup Exec logon account” on page 150.
7. Click OK.
Related Topics:
“Configuring database access on the media server for Oracle operations” on page 1408
“Configuring the Oracle Agent on Windows computers” on page 1399
“Configuring the Oracle Agent on Linux computers” on page 1404
“Deleting an Oracle server name or logon account from the media server’s list of
authentication credentials” on page 1411
1410 Administrator’s Guide

Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
About upgrading the Backup Exec Oracle Agent
Deleting an Oracle server name or logon account from the media
server’s list of authentication credentials
To delete an Oracle server name or logon account from the media server’s list of
authentication credentials
1. On the media server, on Tools menu, click Options.
2. On the properties pane, under Job Defaults, click Oracle.
3. Click the Modify list button.
On the Authentication Credentials for Oracle and DB2 Servers dialog box, you can
add, edit, or delete a server name and a logon account.
4. Select the item that contains the server name or logon account that you want to
delete.
5. Click Delete.
See “Deleting a Backup Exec logon account” on page 153.
6. Click OK.
About upgrading the Backup Exec Oracle Agent
The Backup Exec Oracle Agent 11d replaces the previous (legacy) Oracle Agent. All
existing Oracle jobs are upgraded for use with the new agent. When you upgrade to the
Backup Exec Oracle RMAN Agent, backup jobs for Oracle instances that were created
with the legacy Oracle Agent are placed on hold.
You must do the following:
Upgrading the Backup Exec Oracle Agent
Task Description
Verify that the logon account for each
resource that was backed up by the
previous Oracle Agent is valid for the
new Oracle Agent.
Go to “Changing and testing resource credentials for
restore jobs” on page 516.
1411

About using the legacy Backup Exec Oracle Agent
Upgrading the Backup Exec Oracle Agent
Task Description
Use the Remote Agent Utility to
configure information about the
Oracle instances for the Oracle Agent,
and to enable media server access to
the Oracle databases.
Add the Oracle server name and logon
account to the media server’s list of
authentication credentials.
Go to “Configuring the Oracle Agent” on page 1399.
Go to “Configuring database access on the media server
for Oracle operations” on page 1408.
Take the associated jobs off hold. To remove the hold and run the jobs according to the
schedule, right-click the selection list that is associated
with the jobs, and click Remove Hold.
After upgrading, the database control file resource no longer appears in the backup
selections tree under the Oracle server node. Backup Exec 11d automatically backs up
the database control file whenever a table space or other resource on the Oracle server is
backed up.
If the database control file is the only resource in the backup selection list in the previous
version of the Oracle Agent, then you must create another selection list that contains
other resources. The database control file is then automatically backed up whenever the
other resources in the selection list are backed up.
About using the legacy Backup Exec Oracle Agent
If you install Backup Exec Oracle Agent 11d, then you cannot back up Oracle databases
with the legacy (previous version) Backup Exec Oracle Agent. If you want to continue to
use the legacy agent for backup operations, do not install Backup Exec 11d.
If Backup Exec 11d is installed, you can use the legacy Oracle Agent to run online restore
operations.
To run offline or file system restores of backup sets that were made by the legacy Oracle
Agent, see http://support.veritas.com/docs/204583.
1412 Administrator’s Guide

Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
What to do when Oracle instance information changes
What to do when Oracle instance information changes
Whenever information about the Oracle instance changes, such as the instance user
name and password, you must update the Remote Agent Utility.
When Oracle RAC nodes are added or removed, you must enter information about any
changes to instances in the Remote Agent Utility. After these changes are entered, the
Backup Exec media server discovers them.
If the changes are not updated in the Remote Agent Utility, the error “Unable to attach to
a resource...” may appear when you run a backup job.
Related Topics:
“Configuring the Oracle Agent on Windows computers” on page 1399
“Configuring the Oracle Agent on Linux computers” on page 1404
“Setting application defaults for Oracle” on page 1421
“About performing a DBA-initiated backup job for Oracle” on page 1417
“Configuring DBA-initiated job settings for Oracle” on page 1419
About backing up Oracle resources
Before you back up Oracle resources, review the following:
■ You must run the Remote Agent Utility on the Oracle server and add information
about the instances before you can perform any backup or restore operations.
When Oracle instance information changes, you must update the Remote Agent
Utility. After these changes are entered, the Backup Exec media server discovers
them.
See “Configuring the Oracle Agent on Windows computers” on page 1399 or
“Configuring the Oracle Agent on Linux computers” on page 1404.
■ During a backup operation, the amount of data that is backed up may not equal the
size of the Oracle files that are on the disk. This behavior is normal. Backup Exec
backs up the selected data files as well as a copy of the control file.
■ In a Central Admin Server Option environment, all backup jobs for a specific Oracle
instance must be delegated to the same managed media server. If you do not restrict
the back up job to the same managed media server, then before you can restore data,
you must move the physical media that contains the backup sets to a single managed
media server. For more information about restricting the backup of a selection list,
see “Restricting the backup of a selection list to specific devices” on page 820.
1413

About backing up Oracle resources
■ If the Oracle database resides on volumes that are configured with Oracle Automatic
Storage Management (ASM), you cannot select these volumes as part of a file system
backup. The following message appears when you attempt to select the volumes:
An error was encountered while attempting to browse the
contents of . A device-specific error occurred.
■ The database must be in a mounted or open state before you can make backup
selections.
■ The database must be in ARCHIVELOG mode before an archive log can be displayed
in the backup selections list.
■ The Backup Exec option to display progress indicators for backup jobs is not
available for backup jobs when Oracle resources are included in the backup selection
list.
Related Topics:
“Backing up Oracle resources” on page 1415
“About performing a DBA-initiated backup job for Oracle” on page 1417
“Configuring DBA-initiated job settings for Oracle” on page 1419
About backing up Oracle RAC resources
Oracle Real Application Cluster (RAC) is an active-active cluster with shared storage, in
which multiple instances share a single physical database. Since all of the participating
nodes can access the database, you can initiate backup, restore, or recovery from any
node. Oracle RAC databases appear in the media server’s backup selection list, under the
node Oracle Real Application Clusters.
Requirements for backing up Oracle RAC resources include the following items:
■ You must run the Remote Agent Utility on each node and add information about the
instances before you can perform any backup or restore operations.
When RAC nodes are added or removed, you must update the Remote Agent Utility.
with information about the affected instances. After these changes are entered, the
Backup Exec media server discovers them.
See “Configuring the Oracle Agent on Windows computers” on page 1399 or
“Configuring the Oracle Agent on Linux computers” on page 1404.
■ You must select the RAC virtual node name when making backup selections.
Each node in the cluster uses the same virtual node name. The virtual node name
appears under the Oracle Real Application Clusters resource in the media server’s
backup selections list. It is in the form RAC--.
1414 Administrator’s Guide

Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
About backing up Oracle resources
Backing up Oracle RAC is similar to backing up standard Oracle databases. You should be
aware of the following differences:
■ By default, each node in an Oracle RAC stores its archive logs locally. To have a
meaningful backup of the archive logs, back up each archive log. Alternatively, you
can move the archive logs to a shared device for backup.
■ Each node that is part of the cluster is assigned a priority. For database backups,
Backup Exec connects to the node that has the highest priority. Backup Exec uses the
virtual node name to connect to the node.
Related Topics:
“About performing a DBA-initiated backup job for Oracle” on page 1417
“Configuring DBA-initiated job settings for Oracle” on page 1419
“Setting application defaults for Oracle” on page 1421
Backing up Oracle resources
Before you back up Oracle resources, make sure that you have completed all of the
installation and configuration requirements. See “Installation and configuration
requirements for the Oracle Agent” on page 1398.
You should also review “About backing up Oracle resources” on page 1413.
To back up Oracle resources
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. In the backup selections list, do one of the following:
For Oracle RAC Expand the RAC virtual node name under the Oracle Real
Application Clusters node.
Each node in the cluster uses the same virtual node name. It is in
the form RAC--.
For Oracle resources Expand the appropriate node under Favorite Resources.
The current state of the database appears in brackets next to the database name. If
the database is down, you cannot select it for backup.
1415

About backing up Oracle resources
4. To select data for backup, select the check box next to the item that you want to back
up.
If you select a container item for backup, you cannot exclude individual items in that
container. You must clear the check box for the container item, and then select the
individual items in the container that you want to include in the backup.
5. On the Properties pane, under Settings, click Oracle.
6. Complete the appropriate options as follows:.
Backup method Select one of the following backup methods:
Delete backed up archive
log files
Do not back up archived
logfiles that have already
been backed up
Perform the backup
offline
◆ Full - Back up selections. This method is the equivalent of the
Oracle RMAN Incremental: Level 0 backup. Select this method
to perform a full backup of Oracle selections.
◆ Differential - Back up changes since last full. This method is
the equivalent of the Oracle RMAN Cumulative Incremental:
Level 1 backup. Select this method to back up all database
changes since the last full backup. A full backup is performed
of all archived redo logs since log files are never partially
backed up.
◆ Incremental - Back up changes since last full or incremental.
This method is the equivalent of the Oracle RMAN
Incremental: Level 1 backup. Select this method to back up all
database changes since the last full or incremental backup. A
full backup is performed of all archived redo logs since log files
are never partially backed up.
Check Delete backed up archive log files to delete the archived log
files automatically after the backup.
Check Do not back up archived logfiles that have already been
backed up to have Backup Exec skip any archived logfiles that
have been backed up previously.
Check Perform the backup offline to have Backup Exec take the
database offline before you start the backup job. Backup Exec
brings the database online after the backup job is complete.
7. To configure multiple data streams for backup, under Destination, click Device and
Media.
1416 Administrator’s Guide

8. Complete the appropriate options as follows:
Maximum number of
devices to use for
resources that support
multiple data streams
Minimum number of
devices, terminate job if
fewer devices are
available
9. Complete the remaining backup job properties as necessary.
For more information, see “Backing up data” on page 345.
Related Topics:
“About backing up Oracle resources” on page 1413
“Setting application defaults for Oracle” on page 1421
“Troubleshooting the Oracle Agent” on page 1429
“Configuring DBA-initiated job settings for Oracle” on page 1419
Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
About backing up Oracle resources
Enter the maximum number of devices that the backup job can
use.
If you specify more than one device, you must choose one of the
following items as a destination device for the backup job:
◆ A device pool.
◆ A backup-to-disk folder that has at least two concurrent
operations enabled.
If there is only one device for the backup job to use, then the data
streams from RMAN are backed up serially to the media.
See “Creating a backup-to-disk folder” on page 222.
Note This feature is not available for DBA-initiated jobs.
Enter the minimum number of devices that the job can use.
If the job cannot acquire the minimum number of devices, the job
fails.
Note This feature is not available for DBA-initiated jobs.
About performing a DBA-initiated backup job for Oracle
A Database Administrator (DBA) can initiate a backup or restore operation for Oracle
from the RMAN console. Example scripts for backup and restore operations that you can
run from the RMAN console are installed to the following location:
\Program Files\Symantec\Backup Exec\scripts\Oracle
Refer to your Oracle documentation for more information on using the RMAN console.
Review the following notes before initiating backup jobs for Oracle from the RMAN
console:
1417

About backing up Oracle resources
■ Make sure that you have completed all of the preparations that are listed in
“Configuring the Oracle Agent” on page 1399.
■ The channel is not released if the RMAN console is not exited, or if a new manual
channel is not allocated on that console. For more information, see “Troubleshooting
the Oracle Agent” on page 1429.
■ During a DBA-initiated backup job, the control file and information that are required
for you to browse DBA-initiated backup sets from the Backup Exec Administration
Console are not backed up by default.
Caution The SKIP INACCESSIBLE option is available in RMAN to skip corrupt data and
log files. Jobs that include this option may complete successfully, but it is likely
that if this data is restored, the database will be in an inoperable state.
The SKIP INACCESSIBLE option is not available for media server operations. If
a backup job encounters corrupt data or log files, the job fails.
Symantec recommends that you do not use this option.
Related Topics:
“What to do when Oracle instance information changes” on page 1413
“About backing up Oracle resources” on page 1413
1418 Administrator’s Guide

Configuring DBA-initiated job settings for Oracle
Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
About backing up Oracle resources
When you create a DBA-initiated backup operation, you can specify the default job
template in Backup Exec, or specify a new job template that you create in Backup Exec.
The job template contains the settings that Backup Exec applies to DBA-initiated jobs.
Make sure that the name of the job template that you want to use is also configured in
the instance information on the Windows computer. See “Configuring the Oracle Agent
on Windows computers” on page 1399 or “Configuring the Oracle Agent on Linux
computers” on page 1404.
Note the following about DBA-initiated jobs:
■ DBA-initiated jobs fail when the related job template is deleted. To stop
DBA-initiated jobs from running, delete the related DBA-initiated job template.
■ All DBA-initiated backup and restore jobs are deleted after the jobs have completed.
■ You cannot set minimum device requirements for DBA-initiated jobs.
To configure DBA-initiated job settings for Oracle
1. On the Tools menu, click Options, and then click DBA-initiated Job Settings.
2. Do any of the following:
To create a new job
template
◆ Click New.
◆ Proceed to step 3.
To edit a job template ◆ Select the job template that you want to edit.
◆ Click Edit.
◆ Proceed to step 3.
3. On the DBA-initiated Job Settings pane, under Destination, click Device and Media,
and then complete the options as appropriate.
For more information about completing device and media options, see “Device and
media options for backup jobs and templates” on page 354. Some options are not
available for the DBA-initiated job settings.
4. On the DBA-initiated Job Settings pane, under Settings, click General, and then
complete the options as appropriate.
For more information about General options, see “General options for backup jobs
and templates” on page 357. Some options are not available for the DBA-initiated job
settings.
1419

About backing up Oracle resources
5. On the Properties pane, under Settings, click Network and Security, and then
complete the options as appropriate.
For more information about setting and managing encryption keys, see “Encryption
keys” on page 407. Some options are not available for the DBA-initiated job settings.
6. If you want Backup Exec to notify someone when the backup job completes, click
Notification, and then complete the options as appropriate.
For more information about notification, see “Assigning notification recipients for
completed jobs” on page 565.
7. Click OK.
Related Topics:
“Troubleshooting the Oracle Agent” on page 1429
“Deleting a job template for DBA-initiated jobs for Oracle” on page 1420
Deleting a job template for DBA-initiated jobs for Oracle
To delete a job template for DBA-initiated jobs for Oracle
1. On the Tools menu, click Options, and then click DBA-initiated Job Settings.
2. Select the job template that you want to delete.
3. Click Delete.
4. Click OK.
Related Topics:
“Configuring DBA-initiated job settings for Oracle” on page 1419
1420 Administrator’s Guide

Setting application defaults for Oracle
Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
Setting application defaults for Oracle
You can use the defaults that Backup Exec sets during installation for all Oracle backup
jobs, or you can choose your own defaults.
To set application defaults for Oracle
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click Oracle.
3. Complete the appropriate options as follows:
Backup Method Select one of the following backup methods:
Delete backed up archive
log files
Do not back up archived
logfiles that have already
been backed up
Perform the backup
offline
◆ Full - Back up selections. This method is the equivalent of the
Oracle RMAN Incremental: Level 0 backup. Select this method
to perform a full backup of Oracle selections.
◆ Differential - Back up changes since last full. This method is
the equivalent of the Oracle RMAN Cumulative Incremental:
Level 1 backup. Select this method to back up all database
changes since the last full backup. A full backup is performed
of all archived redo logs since log files are never partially
backed up.
◆ Incremental - Back up changes since last full or incremental.
This method is the equivalent of the Oracle RMAN
Incremental: Level 1 backup. Select this method to back up all
database changes since the last full or incremental backup. A
full backup is performed of all archived redo logs since log files
are never partially backed up.
Check Delete backed up archive log files to delete the archived log
files automatically after the backup job.
Check Do not back up archived logfiles that have already been
backed up to have Backup Exec skip any archived logfiles that
have been backed up previously.
Check Perform the backup offline to have Backup Exec take the
database offline before you start the backup job. Backup Exec
brings the database online after the backup job is complete.
1421

About restoring and recovering Oracle resources
Modify list Click Modify list to add the Oracle computer name and the logon
account name to the media server’s list of authentication
credentials for Oracle servers.
See “Configuring database access on the media server for Oracle
operations” on page 1408.
4. Click OK.
Related Topics:
“Troubleshooting the Oracle Agent” on page 1429
“What to do when Oracle instance information changes” on page 1413
“About backing up Oracle resources” on page 1413
About restoring and recovering Oracle resources
The restore selections that you choose in Backup Exec are converted to a script. RMAN
uses the script to determine what to restore from the Backup Exec media. After the data
has been restored to the Oracle server, RMAN completes any requested recovery and
restore operations. These recovery and restore operations are determined by the options
that you select.
Some recovery operations may not require media from the media server. For example,
the redo logs may still be on the Oracle server. During a restore operation, the amount of
data that is restored may not be equal to the amount of data that is backed up. In some
cases, the amount of data that is restored is listed as 0 bytes. This behavior is normal
because Oracle might skip datafiles that are already up-to-date on the disk.
If you perform a complete recovery on the whole database, or on a tablespace or datafile,
you must restore a backup of the database or files that you want to recover. Then you
must apply online or archived redo logs, or both. For jobs that are initiated both from the
media server and from a DBA, RMAN determines the specific data that it requires from
Backup Exec to complete the restore and the recovery that you request.
You can only choose Oracle restore selections from the View by Resource tab on the
Restore Job Properties dialog box. The View by Media tab displays backup sets, but you
cannot browse or select the contents.
1422 Administrator’s Guide

Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
About restoring and recovering Oracle resources
In the View by Resource tab, you can make restore selections from the online database or
from control files.
Viewing restore selections for Oracle resources
View restore data in Description
Online database Provides a view of the live database (if available). You can
select an entire database or select individual tablespaces
and datafiles.
Note For Oracle RAC, the Oracle database is listed under
its virtual node name. It is in the form
RAC--.
Control files Provides a list of all backed up control files. Each control
file lists the date it was backed up and the control file’s
piece ID.
You cannot select individual tablespaces or datafiles for
restore.
Caution When you recover to a point in time by using a
control file, make sure that the date of the
control file backup is before the specified
recovery point in time. There should not be any
database structure changes between the two
times.
Related Topics:
“Restoring Oracle data” on page 1424
“Redirecting a restore of Oracle data” on page 1427
Additionally, when you restore a control file, the
entire database reverts to the point in time of
the restored control file.
1423

About DBA-initiated restore and recovery for Oracle
About DBA-initiated restore and recovery for Oracle
DBAs can initiate restore jobs directly from the RMAN console. For example, you can
specify the resources you want restored, and the number of channels to allocate for the
restore job. Refer to your Oracle documentation for more information on using the
RMAN console.
All DBA-initiated restore jobs are deleted after the jobs have completed.
Note If you attempt to use a DBA-initiated restore job to restore a datafile, a tablespace,
or a database that is online, a message appears on the RMAN console. The message
indicates that the restore cannot be performed because Oracle does not allow the
restore of these items if they are online. However, this message is not reported to
Backup Exec. Therefore, the DBA-initiated restore job is reported in Backup Exec as
completing successfully.
Restoring Oracle data
Before you restore Oracle resources, make sure that you have completed all of the
configuration requirements. See “Configuring the Oracle Agent” on page 1399.
You should also review “About restoring and recovering Oracle resources” on page 1422.
To restore Oracle data
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
4. Click the View by Resource tab.
5. Expand the All Resources icon.
6. Expand the system resource that contains the database instance that you want to
restore.
7. Expand the database instance that you want to restore.
The current state of the database is listed to the right of the database name. The
database must be in a Mounted, Nomounted, or Open state. You cannot select
databases for restore jobs if they have a status of Down.
8. Expand either the Current Database or Control Files resource.
1424 Administrator’s Guide

Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
About DBA-initiated restore and recovery for Oracle
If you restore a control file, the entire database reverts to the point in time of the
selected control file backup. You cannot use this option to restore an individual
tablespace or datafile.
To restore an individual tablespace or datafile, make your selection from the online
database view instead.
9. Select the appropriate items to restore.
10. On the properties pane, under Settings, click Oracle.
11. Complete the appropriate options as follows.
Restore from full and/or
incremental backups
To the most recent
available
Check Restore from full and/or incremental backups and then
select an option to restore data from:
◆ The most recent available backups
◆ To a point in time,
◆ To a specific system control number (SCN)
RMAN determines which backup objects are necessary for this
restore job, and then Backup Exec restores those objects.
You may also need to check a recovery option for recovering from
redo logs to complete the restore.
Select this option to restore the Oracle database to the most recent
full and incremental backups that are available.
To a point in time Select this option to restore data up to and including a point in
time. After the point in time, recovery stops.
In the Date box, select the part of the date that you want to
change, and then enter a new date or click the arrow to display a
calendar from which you can select a date.
In the Time box, select the part of the time that you want to
change, and then enter a new time or click the arrows to select a
new time.
To an SCN Select this option to restore up to and including a specific system
control number (SCN). Type the SCN in the field provided.
Restore read-only files if
they are not current
Check Restore read-only files if they are not current to let RMAN
examine the headers of all read-only datafiles and restore any that
are not current.
1425

About DBA-initiated restore and recovery for Oracle
Validate only; do not
restore data
Restore/recover data if
validation completes
without errors
Check Validate only; do not restore data to mount all required
media and read it as necessary. RMAN selects the backup sets that
are necessary to perform the operation, and scans them all to
ensure that they are available and not corrupted. No data is
written or restored to the database server.
Symantec recommends that you select this option to ensure that
all required media is available before you attempt to restore to the
database.
Check Restore/recover data if validation completes without
errors to run the restore job immediately if the validation was
successful.
All options that you have selected for restore and recovery are
performed.
Recover using redo logs Check Recover using redo logs to recover committed transactions
from online and archived redo logs. Select an option to recover
transactions up to the most recent available, or to a point in time,
or to a specific system control number (SCN).
RMAN determines which backup objects are necessary for this
restore job, and then Backup Exec restores those objects.
To the most recent
available
Select this option to recover up to the last committed transaction
that is available from the online and archived redo logs.
To a point in time Select this option to recover committed transactions from the
online and archived redo logs up to and including a point in time.
After the point in time, recovery stops.
In the Date box, select the part of the date that you want to
change, and then enter a new date or click the arrow to display a
calendar from which you can select a date.
In the Time box, select the part of the time that you want to
change, and then enter a new time or click the arrows to select a
new time.
This option is only available when the database is in
ARCHIVELOG mode.
Caution When you recover to a point in time by using a control
file, make sure that the backup time of the control file is
before the specified recovery point in time. The database
structure should not have changed between the two
times.
To an SCN Click this option to recover committed transactions from the
online and archived redo logs to a specific system control number
(SCN). After the SCN is recovered, recovery stops.
1426 Administrator’s Guide

After recovery, delete
archived redo logs that
are no longer needed
Open database after
recovery
Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
Redirecting a restore of Oracle data
12. Select other restore options from the Properties pane as appropriate, and then start
the restore job.
For more information see “Restoring data” on page 483.
13. Run a full backup of the restored database.
Related Topics:
“Configuring DBA-initiated job settings for Oracle” on page 1419
“About DBA-initiated restore and recovery for Oracle” on page 1424
“Troubleshooting the Oracle Agent” on page 1429
Redirecting a restore of Oracle data
In Backup Exec, you can redirect an Oracle instance or its files by redirecting:
■ An Oracle instance to another Oracle server.
Check After recovery, delete archived redo logs that are no
longer needed to delete older archived redo logfiles and free space
on the hard disk.
Check Open database after recovery to ensure that the database
is opened as soon as the recovery is finished. Check this option if
you want the database to be online after the recovery.
Note If you redirect the instance to a different Oracle server, ensure that an instance
with the same name and database ID (DBID) is set up on that server. The database
status should be Nomount. Refer to your Oracle documentation for details on
creating an instance with the same name and database ID.
■ An Oracle instance to another Oracle server and specifying alternate paths for the
Oracle files.
■ Tablespaces, datafiles, and archive logs to an alternate location on the original
server.
Symantec recommends that you select only one instance for each redirected restore
operation.
1427

Redirecting a restore of Oracle data
To redirect a restore of Oracle data
1. Follow the instructions for restoring Oracle data in “Restoring Oracle data” on
page 1424.
2. After you select options on the Restore Job Properties dialog box for Oracle, on the
Properties pane, under Destination, click Oracle Redirection.
3. Select the appropriate options as follows:
Restore Oracle instance to server Check Restore Oracle instance to server to redirect the
restore of the Oracle instance to a server other than the
source server.
Server Type the name of the server to which you want to
redirect the restore job.
Server logon account Type a logon account that has rights to restore data to
the server to which you want to redirect the restore job.
Instance logon account: Type a logon account for the Oracle instance that you
want to restore.
Restore datafiles to the following
path
Restore archived log files to the
following path
Check Restore datafiles to the following path, and
then specify the path to which you want to restore the
datafiles.
If you checked Restore Oracle instance to server, use
this option to specify a path other than the default on
that server.
If you do not want to redirect the instance, check this
option to specify an alternate local path for the file on
the Oracle server.
Check Restore archived log files to the following path,
and then specify the path to which you want to restore
the archived log files.
If you checked Restore Oracle instance to server, check
this option to specify a path other than the default on
that server.
If you do not want to redirect the instance, check this
option to specify an alternate local path for the file on
the Oracle server
4. Start the redirected restore job or select other restore options from the Properties
pane.
1428 Administrator’s Guide

Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
Troubleshooting the Oracle Agent
After the restore job is complete, Symantec recommends that you run a full backup
of the restored data.
Related Topics:
“About backing up Oracle resources” on page 1413
Troubleshooting the Oracle Agent
What should I do if I get a message that an attempt by Backup Exec to change the state
of the database timed out?
For media server operations, the Oracle database may take some time to change states,
such as from open to shut down, from shut down to mount, and so on. A SQLplus script
in Backup Exec allows a default time-out of 10 minutes to handle the changing database
state. For Oracle Real Application Cluster (RAC), a srvctl script is used.
The time-out for database state change is named SqlplusTimeout.
You may need to change the length of the default time-out if the following error message
appears:
An attempt by Backup Exec to change the state of the database timed
out. For details, refer to the Database Script output section in
the job log. Contact your database administrator to change the
state of the database.
Try shutting down the database. If you succeed, then the SQLplus time-out is too short.
Change the default time-out appropriately, based on how long it took to shut down the
database. If you cannot shut down the database, contact your DBA to troubleshoot the
database.
If the time-out is too short, then restore jobs and offline backups may fail with a time-out
error. If the time-out is too long, and the database does not respond to the state change
request, the job takes longer to fail.
1429

Troubleshooting the Oracle Agent
The following table describes how to change the SQLplus time-out.
Changing the SqlplusTimeout
On this platform Do the following
For Oracle instances on Windows
computers
For Oracle instances on Linux
computers
◆ Create a registry entry of the type DWORD in:
Software\Symantec\Backup
Exec\Engine\Agents\XBSA\Oracle RMAN
Agent
◆ Name the entry SqlplusTimeout.
◆ Set the time-out value in seconds. For example, a
time-out of 5 minutes is set as 300 seconds.
◆ In a command prompt, type the following:
vi etc/VRTSralus/ralus.cfg
◆ Create the following entry:
Software\Symantec\Backup
Exec\Engine\Agents\XBSA\Oracle RMAN
Agent\SqlplusTimeout
◆ Set the time-out value in seconds. For example, a
time-out of 5 minutes is set as 300 seconds.
What should I do if a job continues to run on the media server even after it ends on the
RMAN console?
When a backup or restore operation is run on an automatically allocated channel, and if
the channel is not released, the job continues to run on the media server even after the
operation ends on the RMAN console. The channel is not released if the RMAN console is
not exited, or if a new manual channel is not allocated on that console. The job ends on
the media server when either the automatic channel is released, or after a time-out
period elapses without any activity on that channel, whichever occurs first. If a new
backup or restore operation is started within the time-out period on the same automatic
channel, a new job is not created. Instead, the existing job performs the operation at the
media server.
The channel time-out has a default value of 10 minutes, which is recommended for most
purposes. If the time-out is too short, then multiple jobs are created for successive
operations on a channel. If the time-out is too long, the job runs for a long time on the
media server unnecessarily, after the operation has ended.
1430 Administrator’s Guide

The following table describes how to change the default time-out.
Changing the time-out for an automatic RMAN channel
On this platform Do the following
For Oracle instances on Windows
computers
For Oracle instances on Linux
computers
Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
Troubleshooting the Oracle Agent
◆ Create a registry entry of the type DWORD in:
HKLM\Software\Symantec\Backup
Exec\Engine\Agents\XBSA\Oracle RMAN
Agent
◆ Name the entry ChannelTime.
◆ Set the time-out value in minutes.
◆ In a command prompt, type the following:
vi etc/VRTSralus/ralus.cfg
◆ Create the following entry:
HKLM\Software\Symantec\Backup
Exec\Engine\Agents\XBSA\Oracle RMAN
Agent
◆ Set the time-out value in minutes.
The error “Unable to attach to a resource...” is displayed
Whenever Oracle instance information changes, you must update the Remote Agent
Utility. If credential information is not updated or is incorrect, the error “Unable to
attach to a resource...” may be displayed when you run a backup job.
Related Topics:
“Configuring the Oracle Agent on Windows computers” on page 1399
“Configuring the Oracle Agent on Linux computers” on page 1404
What should I do if the error ORA-12546: TNS: Permission denied appears?
If a Backup Exec operation fails on the Linux computer on which the Oracle instances are
installed, and the error in the RMAN output section is ORA-12546: TNS: Permission
denied, then you must change the machine-level resource credentials in the job. The
resource credentials must be an account that is a member of the dba and beoper groups
on the Linux computer. Retry the operation.
Related Topics:
“Configuring database access on the media server for Oracle operations” on page 1408
“About creating the beoper group” on page 940
1431

Disaster recovery of the Oracle instance or database
Disaster recovery of the Oracle instance or database
If you have a disaster, you can recover your Oracle instance or databases using the steps
provided in the two disaster recovery scenarios presented in this section.
Related Topics:
“Disaster recovery scenario 1” on page 1432
“Disaster recovery scenario 2” on page 1434
Disaster recovery scenario 1
In this scenario you experience a complete loss, deletion, or destruction of the Oracle
instance or database and you want to use the same Oracle server for the recovery.
Requirements
To successfully complete the recovery using this scenario, you must have the following
items:
Oracle disaster scenario 1 requirements
Item Description
DBID If you do not know the DBID, you can find it in the Backup Exec job log or in
RMAN after you login.
ControlFile
piece ID
A full system
Oracle backup
The original
Oracle server
You can identify the ControlFile piece ID in the Backup Exec restore view in the
Control Files subnode under the Oracle node.
The full system Oracle backup must include the following:
◆ controlfile
◆ datafiles
◆ archive logs
To successfully recover the Oracle system using disaster recovery scenario 1,
you must restore to the original Oracle server.
1432 Administrator’s Guide

Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
Disaster recovery of the Oracle instance or database
To recover the complete Oracle instance or database after it has been lost, deleted, or
destroyed, and you want to use the original Oracle server for the recovery
1. Recreate the Oracle database using the same name you used for the original database
that was lost.
2. Find and rename the pwd.ora file.
3. Create a new pwd.ora file.
To create a new pwd.ora file
1. Open a command prompt.
2. Type the following command:
orapwd file=path\pwdsid.ora password=
To continue the disaster recovery
1. Open a command prompt and do the following:
2. Type the following command:
RMAN
3. Type CONNECT TARGET ;
4. Type SHUTDOWN ABORT;
5. Type STARTUP NOMOUNT;
6. Type SET DBID;
7. Move to the Backup Exec media server.
8. On the navigation bar, click the arrow next to Restore.
9. Click New Restore Job.
10. On the Properties pane, under Source, click Selections.
11. Select the appropriate ControlFile for restore.
12. Click Run Now.
1433

Disaster recovery of the Oracle instance or database
The restore job will fail because the recovery portion encounters inconsistent archive
logs. This is a normal occurrence during a disaster recovery.
13. After the restore job finishes, exit Backup Exec.
14. Move to the Oracle server.
15. In the command prompt, type the following command at the RMAN prompt:
Alter database open resetlogs;
16. Close the command prompt.
The recovery is finished
Disaster recovery scenario 2
In this scenario you experience a complete loss, deletion, or destruction of the Oracle
instance or database and you want to use a new or alternate Oracle server for the
recovery.
Requirements
To successfully complete the recovery, you must have the following items:
Oracle disaster scenario 2 requirements
Item Description
DBID If you do not know the DBID, you can find it in the Backup Exec job log or in
RMAN after you login.
ControlFile
piece ID
A full system
Oracle backup
You can identify the ControlFile piece ID in the Backup Exec restore view in the
Control Files subnode under the Oracle node.
The full system Oracle backup must include the following:
◆ controlfile
◆ datafiles
◆ archive logs
1434 Administrator’s Guide

Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
Disaster recovery of the Oracle instance or database
To recover the complete Oracle instance or database after it has been lost, deleted, or
destroyed, and you want to use a new or alternate Oracle server for the recovery
1. Recreate the Oracle database using the same name you used for the original database
that was lost.
2. Find and rename the pwd.ora file.
3. Create a new pwd.ora file.
To create a new pwd.ora file
1. Open a command prompt.
2. Type the following command:
orapwd file=path\pwdsid.ora password=
To continue the disaster recovery
1. In the command prompt, do the following:
2. Type the following command:
RMAN
3. Type CONNECT TARGET ;
4. Type SHUTDOWN ABORT;
5. Type STARTUP NOMOUNT;
6. Type SET DBID;
7. Move to the Backup Exec media server.
8. On the navigation bar, click the arrow next to Restore.
9. Click New Restore Job.
10. On the Properties pane, under Source, click Selections.
11. Select the appropriate ControlFile to restore.
12. On the Restore job properties pane, under Destination, click Oracle Redirection.
1435

Disaster recovery of the Oracle instance or database
13. Check the check box for the option, Restore Oracle instance to server.
14. Enter account credentials to access the new or alternate Oracle server.
15. Check the check box for the option, Restore datafiles to the following path:
16. Type a path to the new database.
17. Check the check box for the option, Restore archived log files to the following path:
18. Click Run Now.
The restore job will fail because the recovery portion encounters inconsistent archive
logs. This is a normal occurrence during a disaster recovery.
19. Move to the Oracle server.
20. Type Alter database open resetlogs;
21. Do one of the following:
If an error is encountered while
Oracle tries to open the database
To update the online redo log file path
1. At the Oracle server, open a command prompt.
2. Type the following command:
SQLPLUS /nolog
3. Type connect;
Note the online redo log path and then update the path
using the steps below.
If an error does not occur Do nothing. The disaster recovery is complete.
4. Type the following SQLPlus command:
SQLPLUS ALTER DATABASE RENAME FILE to ;
For example,
ALTER DATABASE RENAME FILE ‘D:\ORACLE\ORADATA\JACOB\REDO01.LOG’ to
‘C:\ORACLE\ORADATA\JACOB\REDO01.LOG’;
1436 Administrator’s Guide

5. In the command prompt, type RMAN.
6. Type the following command at the RMAN prompt:
Alter database open resetlogs;
7. Close the command prompt.
The recovery is finished.
Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
Disaster recovery of the Oracle instance or database
1437

Disaster recovery of the Oracle instance or database
1438 Administrator’s Guide

Appendix
Symantec Backup Exec Agent
for SAP Applications
O
The Backup Exec Agent for SAP Applications (SAP Agent) lets you backup, restore, and
archive SAP ® for Oracle and MaxDB databases using either:
■ BACKINT, the backup and restore interface developed by SAP
■ Oracle’s Recovery Manager (RMAN)
To use RMAN to back up SAP for Oracle databases, you must have both the SAP Agent
and the Symantec Backup Exec Agent for Oracle on Windows or Linux Servers (Oracle
Agent).
To back up Oracle databases that are not managed by SAP, you can purchase the Oracle
Agent. To back up SAP applications installed on Microsoft SQL Server, you can purchase
the Symantec Backup Exec for Windows Servers Agent for Microsoft SQL Servers.
Related Topics:
“Symantec Backup Exec Agent for Microsoft SQL Server” on page 1335
“Symantec Backup Exec Agent for Oracle on Windows or Linux Servers” on page 1397
1439

About the SAP Agent
About the SAP Agent
The SAP Agent is a separate, add-on component of Backup Exec for Windows Servers. It
supports multiple media servers running on the same network. The SAP Agent lets you
back up and restore individual files, entire databases, or individual tablespaces in online
or offline mode. You can also archive offline redo logs.
Note Backup Exec for Windows Servers 11d does not support older versions of the SAP
Agent. You must upgrade your previous agent to this release of the SAP Agent.
The following features are available with the SAP Agent:
■ Ability to name jobs.
■ Data encryption.
■ Data compression at the client side.
■ Recipient notification.
■ Dedicated network path for SAP jobs.
■ Data integrity verification following a backup job.
■ Increased protection of the SAP Agent catalog.
Related Topics:
“Configuring DBA-initiated job settings for SAP” on page 1448
“About encrypting SAP data” on page 1444
“Changing the backup network for a job” on page 403
“General options for backup jobs and templates” on page 357
“About preserving the integrity of the SAP Agent catalog” on page 1445
How the SAP Agent works
The SAP Agent acts as a client for Backup Exec. Through the biparam.ini file, you set
Backup Exec parameters for jobs that you submit from SAP interfaces. For example, you
can set a job name, specify a server or device to use for the job, or specify the backup
compression mode.
The SAP Agent connects to your Backup Exec server. The requests are processed
through Backup Exec. Jobs that you submit from SAP interfaces, through the SAP Agent,
are treated as Run Now jobs. If all drives are busy, jobs can be queued in a Backup Exec
job queue. From the queue, the Backup Exec administrator can edit or cancel the job.
1440 Administrator’s Guide

Appendix O, Symantec Backup Exec Agent for SAP Applications
About the SAP Agent
When jobs are complete, Backup Exec writes a standard job log as it does for any
submitted job. You can view the job log from the Backup Exec administration console.
The SAP Agent sends the results of its jobs to the SAP tools. When a job is initiated by a
SAP interface, a job log is produced with an eight-character name that represents the
job. The SAP system stores the job log in the following directory:
:\Oracle\\sapbackup
where is the database installation drive and is the system ID of the Oracle
instance. The file is a plain ASCII text file that you can view with any text editor.
The _backint.xml file, which stores Backup Exec catalog information about the job, is
placed in the folder local to BRTOOLS, a SAP utility program. Generally the path is as
follows:
Usr\sap\\sys\exe\run
In the event of a disaster, you must restore this file to restore data to the SAP server.
Related Topics:
“About system level backup jobs” on page 1450
“About performing disaster recovery using the SAP Agent” on page 1459
About using the SAP Agent with RMAN
Backup Exec requires the Oracle Agent when integrating with RMAN for backing up and
restoring data files. When you back up the database through RMAN the following
occurs:
■ The data files are backed up by RMAN using the Oracle Agent.
■ Control and log files are backed up by BACKINT using the SAP Agent.
You must run the Remote Agent Utility to configure some settings before you run a
backup or restore job through RMAN.
Related Topics:
“Symantec Backup Exec Agent for Oracle on Windows or Linux Servers” on page 1397
“About using the SAP Agent with RMAN” on page 1441
“The Remote Agent Utility for Windows Systems” on page 917
1441

Requirements for using the SAP Agent
Requirements for using the SAP Agent
The SAP Agent supports the following Microsoft operating systems:
■ Windows XP
■ Windows 2000 (32-bit and 64-bit extended)
■ Windows 2003 (32-bit and 64-bit extended)
The SAP Agent supports the following database versions:
■ Oracle 9i (9.2 and later) and 10g
■ Oracle Fail Safe®
■ SAP® 4.6c and 4.6d
■ SAPDB 7.4.03.25
■ SAPDB 7.4.03.30
■ SAPDB 7.4.03.32
■ MaxDB 7.5
Other requirements are as follows:
■ The SAP Agent license key must be installed on the media server.
■ The SAP Agent must be installed on the SAP server.
■ The Backup Exec Remote Agent for Windows Systems must be installed on the SAP
server.
Note The Backup Exec Remote Agent for Windows Systems is automatically installed
on the SAP server as part of the SAP Agent installation.
■ All SAP databases that you want to back up must be placed in ARCHIVE_LOG mode
and Automatic Archival must be enabled using the database administration tools.
See the SAP User Manual or your SAP Database Administrator's Guide.
■ All Oracle databases that you want to back up must be managed by the SAP system.
■ BRTOOLS 6.40 must be installed on the Oracle server that is being backed up if you
are using Oracle 9.i; BRTOOLS 7 must be installed on the Oracle server that is being
backed up if you are using Oracle 10g.
■ The SAP Agent must be configured following the procedures described in
“Configuring biparam.ini” on page 1447.
■ The backup operator must be a member of the ORA_DBA group.
■ You must create the ORA__OPER group and add the backup user.
1442 Administrator’s Guide

Appendix O, Symantec Backup Exec Agent for SAP Applications
About installing the SAP Agent
■ For RMAN backup and restore jobs, the Backup Exec Oracle Agent must be installed
on the SAP server.
The SAP Agent follows the BC-BRI BACKINT Interface for ORACLE Databases
specification, version 3.0.
Note The SAP Agent does not support data stored on RAW partition types.
Related Topics:
“Installing Backup Exec to a local computer” on page 81
“System requirements” on page 79
About installing the SAP Agent
Before you install the SAP Agent, do the following:
■ Ensure the backup operator is a member of ORA_DBA. (If the backup operator is
Administrator, add Administrator to ORA_DBA group).
■ Create group ORA__OPER and add the current user to this group.
■ Verify that the SAP system environment variables are set for the server that you
plan to back up. The SAP Agent default directory is in the SAP database's home as
follows:
Usr\sap\\sys\exe\run
You can install the SAP Agent to your media server when you install Backup Exec, or if
you have already installed Backup Exec, you can install just the SAP Agent.
Related Topics:
“Installing Backup Exec to a local computer” on page 81
“Installing Backup Exec options to the local computer” on page 85
1443

About SAP Agent security and privileges
About SAP Agent security and privileges
Since BACKINT functions as a client to the Backup Exec server, all Microsoft Windows
security limitations that apply to the Backup Exec administration console also apply to
BACKINT.
You must have the appropriate privileges on both the SAP and Backup Exec media
servers to be able to back up and restore data. The Backup Exec service account must
have the following:
■ Access to selections in jobs that are submitted by the BACKINT interface.
■ Rights to the volumes on which the selections are contained.
Related Topics:
“About encrypting SAP data” on page 1444
“Generating alerts” on page 1445
“About preserving the integrity of the SAP Agent catalog” on page 1445
“About performing disaster recovery using the SAP Agent” on page 1459
“Changing Windows security” on page 75
About encrypting SAP data
The SAP Agent lets you encrypt data with encryption keys. This feature is available for
backup jobs done using either RMAN or BACKINT.
Create the encryption key through the DBA-initiated Job Settings when you create or
edit a job template. You must specify the job template name in the biparam.ini file.
If you run jobs with a particular encryption key and the key is deleted, the data that is
backed up using the encryption key cannot be restored.
Related Topics:
“Configuring DBA-initiated job settings for SAP” on page 1448
“Encryption keys” on page 407
1444 Administrator’s Guide

Generating alerts
Appendix O, Symantec Backup Exec Agent for SAP Applications
About SAP Agent security and privileges
Backup Exec generates alerts, which BACKINT handles in one of the following modes:
Unattended mode In Unattended mode, any alert that requires a response causes the job
to fail and the alert to appear in the SAP system console.
Informational alerts also appear in the SAP system console.
Interactive mode In Interactive mode, all alerts appear in the SAP system console. You
must respond to the alerts for the job to continue.
About preserving the integrity of the SAP Agent catalog
You can preserve the integrity of the SAP Agent catalog (_backint.xml) in the following
ways:
■ By restricting which groups can access _backint.xml.
■ By backing up the catalog along with normal backup data.
Only users in the Administrators or Backup Operators groups can access the SAP Agent
catalog (_backint.xml). As an administrator, you can give other users permission to
access _backint.xml, but you should not revoke the default permission given to the
Administrators and Backup Operators groups.
You can include a backup of _backint.xml along with your normal backups by setting the
parameter Backup Catalog to On in biparam.ini. Catalog backups are recommended at
least monthly, but backing up the catalog more frequently provides additional
safeguards if the catalog becomes corrupted.
Note To restore the SAP Agent catalog, you must create a restore job from the Backup
Exec media server.
Related Topics:
“Configuring biparam.ini” on page 1447
1445

Before backing up SAP data
Before backing up SAP data
Before you submit a backup operation, you must do the following:
■ Place all SAP databases to be backed up in the ARCHIVE_LOG mode.
■ Enable Automatic Archival using the SAP interfaces.
For more information on enabling Automatic Archival, consult your SAP or Oracle
documentation.
Caution The SAP Agent does not support concurrent backup or restore operations.
Attempting to back up or restore the same SAP database from more than one
media server at the same time causes the operation to fail.
If you are using RMAN, you must do the following:
■ Configure the SAP Agent by using the Backup Exec Remote Agent Utility.
See “The Remote Agent Utility for Windows Systems” on page 917.
■ Add the Oracle Server to the media server’s Modify list.
See “Configuring database access on the media server for Oracle operations” on
page 1408.
If you want to enter specific configuration information, you should also edit the
biparam.ini file that is found in your Usr\sap\\sys\exe\run directory and the
init.sap file that is found in the \database folder.
Related Topics:
“Configuring biparam.ini” on page 1447
“Setting application defaults for Oracle” on page 1421
1446 Administrator’s Guide

Configuring biparam.ini
Appendix O, Symantec Backup Exec Agent for SAP Applications
Before backing up SAP data
The BACKINT interface lets you specify Backup Exec parameters for backup jobs that
you submit from the SAP interfaces. The parameters are stored in the backup utility
parameter file, biparam.ini. A template of this file is installed with the SAP Agent.
SAP requires that all SAP tools be in a common folder. The SAP Agent is installed in the
same folder as BRTOOLS.
The biparam.ini file lets you specify job parameters from a single location for operations
through RMAN and BACKINT.
To configure biparam.ini
1. Do one of the following:
■ Ensure that the biparam.ini file is local to the BRTOOLS and the SAP Agent
installation.
■ Ensure that the parameter util_par_file in the
database\init.sap file specifies the path of the biparam.ini file.
2. Edit any of the following options in the biparam.ini file to configure the media
server:
Server= Name of the Backup Exec server that will process this backup job.
Note Restore jobs are automatically directed to the Backup Exec
server from where the original backup job was executed
(except in the case of restore jobs through RMAN).
The default is the local computer.
Job Name= User-specified Job Name. The default is the media server generated
Job Name.
Job Template=
The job template that will be used for this job. The job template
includes settings like device, media, and encryption key.
Note The DBA-initiated Job Template has to be created at the
media server.
See “Configuring DBA-initiated job settings for SAP” on page 1448.
The default value is the DEFAULT job template. All job parameters
would be considered from the DEFAULT job template in this case.
If DEFAULT job template is unavailable in the media server and if
the user does not mention any job template name in biparam.ini,
then the job fails. The job also fails if you specify a wrong job
template name.
1447

Before backing up SAP data
Backup
Catalog=
3. Save the file.
Configuring DBA-initiated job settings for SAP
When you create a DBA-initiated backup operation, you can specify the default job
template in Backup Exec, or specify a new job template that you create in Backup Exec.
The job template contains the settings that Backup Exec applies to DBA-initiated jobs.
Make sure that the name of the job template that you want to use is configured in the
biparam.ini file.
See “Configuring biparam.ini” on page 1447.
Note the following about DBA-initiated jobs:
■ DBA-initiated jobs fail when the related job template is deleted. To stop
DBA-initiated jobs from running, delete the related DBA-initiated job template.
■ All DBA-initiated backup and restore jobs are deleted after the jobs are complete.
■ You cannot set minimum device requirements for DBA-initiated jobs.
To configure DBA-initiated job settings for SAP
1. On the Tools menu, click Options.
2. Click DBA-initiated Job Settings.
3. Do any of the following:
To create a new job
template
On: The backup job includes the client-side catalog file
(_backint.xml)
Off: The backup job does not include the client-side catalog file
(_backint.xml)
The default is Off.
◆ Click New.
◆ Proceed to step 4.
To edit a job template ◆ Select the job template that you want to edit.
◆ Click Edit.
◆ Proceed to step 4.
1448 Administrator’s Guide

To delete a job template ◆ Select the job template that you want to delete.
Appendix O, Symantec Backup Exec Agent for SAP Applications
Before backing up SAP data
4. On the DBA-initiated Job Settings pane, under Destination, click Device and Media,
and then complete the options as appropriate.
For more information about completing device and media options, see “Device and
media options for backup jobs and templates” on page 354. Some options are not
available for the DBA-initiated job settings.
5. On the DBA-initiated Job Settings pane, under Settings, click General, and then
complete the options as appropriate.
For more information about General options, see “General options for backup jobs
and templates” on page 357. Some options are not available for the DBA-initiated job
settings.
6. On the Properties pane, under Settings, click Network and Security, and then
complete the options as appropriate.
For more information about setting and managing encryption keys, see “Encryption
keys” on page 407. Some options are not available for the DBA-initiated job settings.
7. If you want Backup Exec to notify someone when the backup job completes, click
Notification, and then complete the options as appropriate.
For more information about notification, see “Assigning notification recipients for
completed jobs” on page 565.
8. Click OK.
◆ Click Delete.
1449

About system level backup jobs
About system level backup jobs
The more frequently you back up the SAP database, the less time it takes to recover it in
the event of data loss. In addition to regularly scheduled SAP Agent backups, it is
recommended that you close the SAP database and run a file-level backup whenever you
alter the structure of the database. Along with backing up the SAP database files, you
should do the following:
■ Create a backup of the Windows directory on the SAP database server and include
the Windows registry.
■ Back up the _backint.xml file. The _backint.xml file is usually located in the
following directory:
Usr\sap\\sys\exe\run
Related Topics:
“About performing disaster recovery using the SAP Agent” on page 1459
About backing up and restoring with the SAP Agent
You create a backup job for SAP applications in one of the following ways:
■ Using the CCMS console, which is a graphical user interface.
■ Using BRTOOLS, which is a command line utility.
When you back up the database from the CCMS console, status messages appear on the
console. These messages report when the database server starts, or stops. They also
report when the backup mode of the tables changes. The detail debugging messages and
log messages also appear. After all files are backed up, the entire file list appears in the
format that is required by the SAP Agent BACKINT interface specification and reports
the success or failure of the submitted job.
When you back up the database from BRTOOLS, you can set the backup_mode by
changing the init.sap parameter file. For example:
backup_type = online_file
Or, you can specify -d with an appropriate backup type on the BRBACKUP command
line. For example, on the command line, type:
-d util_file_online
This command provides a better online backup of very large files, since only the
necessary tablespaces are placed in backup mode. When Backup Exec is ready to process
another file, it notifies BRBACKUP.
1450 Administrator’s Guide

Appendix O, Symantec Backup Exec Agent for SAP Applications
About backing up and restoring with the SAP Agent
Requirements for submitting jobs from remote computers
If the SAP Agent and the Backup Exec media server are installed on different computers,
the following requirements must be met in order for backup and restore jobs to be
successful:
■ The computer on which the SAP Agent is installed and the media server must be in
the same domain.
■ The System Logon Account must exist on both the computer on which the SAP
Agent is installed and on the Backup Exec media server.
■ The System Logon Account must be a member of either the Administrator or Backup
Operators groups on both the computer on which the SAP Agent is installed and on
the Backup Exec media server.
Restoring data with BRRESTORE
BRRESTORE, the BRTOOL utility for restoring data, submits the BID and filename list to
the SAP Agent BACKINT interface. BACKINT checks the date and time when the backup
was made and uses Backup Exec to recover the file. BACKINT monitors the progress of
the restore job and reports status back to BRRESTORE.
When the job completes, BACKINT saves a copy of the Backup Exec restore logs for
auditing purposes. You must restart the database.
Use the following command to restore data:
BRRESTORE -d util_file -b last -m full
Use the following commands to restore the database:
SQL>startup mount
SQL>recover database
SQL>alter database open;
About redirecting SAP restore jobs
The SAP Agent lets you redirect restore jobs to both local and remote computers. If you
are redirecting to a remote computer, you must use a valid full UNC path for the
location.
For example, if you want to restore a tablespace that originally existing on ComputerA
to D:\RestoreDirectory on ComputerB, type:
brrestore -d util_file -b -m =\\ComputerB\D$\RestoreDirectory
1451

Backing up with RMAN
Note The System Logon Account for the media server must be a member of either the
Administrators or Backup Operators groups on the computer on which the data is
being restored.
Backing up with RMAN
Backup Exec integrates with RMAN, an Oracle utility that does the following:
■ Manages backup operations
■ Creates backups of database files
To back up SAP data using RMAN, the Backup Exec Oracle Agent is required, and the
Remote Agent Utility must be run first.
See “The Remote Agent Utility for Windows Systems” on page 917.
You must modify the rman_send parameters in the Init.sap file as follows:
rman_send = ( "channel sbt_1 'NBBSA_SAP_CONFIG_PATH='")
where is the full path for the biparam.ini. For example:
C:\oracle\ora92\database\biparam.ini.
See “Configuring biparam.ini” on page 1447.
Ensure that the ini file path mentioned in the parameter 'util_par_file' in the
init.sap is the same path specified in the rman_send command.
For backups and restores jobs done using RMAN, Symantec Backup Exec does not honor
the configuration parameter (-r option) passed from BRBACKUP or BRRESTORE.
Update init.ora as follows:
control_file_record_keep_time , (say n = 45)
This parameter controls the minimum number of days that a reusable record is kept in
the control file.
To do an online backup, type the following command:
brbackup -d rman_util -t online -m all
To do an offline backup, type the following command:
brbackup -d rman_util -t offline -m all
Note Before doing restores make sure that the database is in the mount state.
Before running online backup jobs, run the following scripts:
1452 Administrator’s Guide

Appendix O, Symantec Backup Exec Agent for SAP Applications
Backing up with RMAN
$ORACLE_HOME\rdbms\admin\catalog.sql
$ORACLE_HOME\rdbms\admin\catspace.sql
$ORACLE_HOME\rdbms\admin\catproc.sql
These scripts will configure the database for an online backup. If the database is not
configured properly, the job could fail.
If you get the following error:
RMAN-00571:
===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
===========================================================
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMS_BACKUP_RESTORE.SET_CHARSET' must be
declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
RMAN-04015: error setting target database character set to
WE8MSWIN1252
Run the following scripts:
$ORACLE_HOME\rdbms\admin\catalog.sql
$ORACLE_HOME\rdbms\admin\catspace.sql
$ORACLE_HOME\rdbms\admin\catproc.sql
After running the scripts, run the backup job again.
1453

Restoring with RMAN
Restoring with RMAN
Backup Exec integrates with RMAN, an Oracle utility that does the following:
■ Manages recovery operations
■ Restores or recovers a database from backups.
To restore SAP data using RMAN, the Backup Exec Oracle Agent is required, and the
Remote Agent Utility must be run first.
See “The Remote Agent Utility for Windows Systems” on page 917.
You must modify the rman_send parameters in the Init.sap file as follows:
rman_send = ( "channel sbt_1 'NBBSA_SAP_CONFIG_PATH='")
where is the full path for the biparam.ini. For example:
C:\oracle\ora92\database\biparam.ini.
See “Configuring biparam.ini” on page 1447.
Ensure that the ini file path mentioned in the parameter 'util_par_file' in the
init.sap is the same path specified in the rman_send command.
For restores done using RMAN, Symantec Backup Exec does not honor the configuration
parameter (-r option) passed from BRBACKUP or BRRESTORE.
Update init.ora as follows:
control_file_record_keep_time , (say n = 45)
This parameter controls the minimum number of days that a reusable record is kept in
the control file.
When BRRESTORE is used to run full restores via RMAN, the database should be in
mount state.
The command for restoring database files only is as follows:
brrestore -d rman_util -b last -m full
For restoring the control files, use the -m 0 [,00] option
For example, to restore the .ctl files type the following on the command line:
brrestore -d rman_util -b last -m 0
To restore the .dbf files, type the following on the command line:
brrestore -d rman_util -b last -m 00
Note When restoring with RMAN, make sure that the media server specified in the
biparam.ini file is the media server on which the backup job was done.
1454 Administrator’s Guide

Appendix O, Symantec Backup Exec Agent for SAP Applications
Migrating the SAP Agent catalog from _backint.mdb to _backint.xml
Migrating the SAP Agent catalog from _backint.mdb to
_backint.xml
This release of Backup Exec stores the SAP Agent catalog in an XML file. If you are
upgrading from a previous version of Backup Exec, during the install process select the
Upgrade option to migrate all the backup metadata from _backint.mdb to _backint.xml.
If you do not select the Upgrade option during the installation, the earlier backup
catalog is not be available to this release of Backup Exec.
You must manually migrate the data if:
■ You did not select the Upgrade option during the time of installation.
■ You want Backup Exec to use a catalog created by earlier version of the SAP Agent.
Before migrating the data, do the following:
■ Make sure that a file named _backint.xml is not already in the path that you plan to
use.
■ Make sure that _backint.mdb is in the same location were BRTOOLS and
_backint.exe are located.
To manually migrate from backint.mdb to backint.xml
1. Copy the _backint.mdb file to the location where the BRTOOLS and _backint.exe is
located (if not already present).
The migration utility (MdbToXML.exe) is located in the directory where the SAP
Agent is installed.
2. Run the Migration Utility (MdbToXML.exe) with proper usage parameters.
For example:
MdbToXml.exe
If _backint.mdb is in the path C:\usr\sap\CER\sys\exe\run, then the command
is:
MdbToXML.exe C:\usr\sap\CER\sys\exe\run
To get online help for this utility, type the following command:
MdbToXML.exe /?
The Path for Log file is optional. If a path is not specified, then the log file is created local
to the _backint.xml file.
The _backint.xml file is created in the same path as the _backint.mdb file.
1455

Backing up a clustered SAP database on Microsoft Cluster Server
After the migration is completed, the _backint.mdb is renamed to
_backint_migrated.mdb.
A log file named MdbToXmlMigrationLog.txt is created in the path that is specified in
the command line. If that parameter is ignored, then it is created local to the
_backint.xml. If the path for log file is mentioned incorrectly, no log file is created. But
this does not affect the migration process.
Backing up a clustered SAP database on Microsoft Cluster
Server
The Backup Exec for SAP Agent supports backup and restore jobs in a clustered
environment for Oracle with the help of Microsoft Cluster Server (MSCS) and Oracle
Failsafe. To use the SAP Agent in a clustered environment, do the following:
■ Install both MSCS and Oracle along with Oracle Failsafe on both nodes of a two-node
cluster environment.
■ Install the database that you want to back up on the shared disk to ensure that the
database is properly failed over to the other node.
■ Ensure that the cluster has a virtual cluster name configured.
See your Oracle Failsafe documentation for additional information on configuring and
installing Oracle Failsafe.
See your Microsoft documentation for additional information on installing and
configuring MSCS.
Note In a cluster environment, if a job created through BACKINT or RMAN is
processing and the node fails over, the job operation does not restart from the
point when the node went down.
1456 Administrator’s Guide

Backing up MaxDB databases
Appendix O, Symantec Backup Exec Agent for SAP Applications
Backing up MaxDB databases
The SAP Agent supports the backup of SAP applications that run on the MaxDB(SAPDB)
database.
Use the DBM command line interface or the MaxDB Database Manager graphical user
interface to initialize and send a backup job to MaxDB's BACKINT interface. MaxDB’s
BACKINT then sends the backup job to the Symantec SAP Agent BACKINT interface,
which executes the job. The SAP Agent supports backups to both local and remote
Backup Exec media servers.
The SAP Agent supports the following SAP DB backup functions:
■ Backup of complete data.
■ Backup of incremental data.
■ Backup of log files.
Before using the SAP Agent to back up MaxDB databases, do the following:
Ensure these files are
present:
Ensure these parameters
are set during the
installation of MaxDB:
Ensure these paths exist:
Ensure the appropriate
versions of these
applications are
installed:
◆ SAP.PAR
◆ BSI.ENV
◆ independent data path = C:\sapdb\data
◆ independent program path = C:\sapdb\programs
◆ dependant path to C:\sapdb\\db
◆ C:\sapdb
◆ C:\sapdb\programs
◆ C:\sapdb\data
◆ C:\sapdb\
◆ C:\sapdb\\db
◆ SQL studio
◆ DBMGUI
Note The SAP Agent must be installed in a directory structure that is only two
directories deep. If this directory structure is changed, and then change the
SAP.PAR and BSI.ENV files accordingly.
1457

Restoring MaxDB databases
To back up MaxDB databases:
1. Copy BSI.ENV into C:\sapdb\data\wrk\
2. Copy SAP.PAR into C:\sapdb\\db
3. From the MaxDB Database Manager, select the Backup Wizard.
4. Provide the appropriate inputs for the backup job, including the following:
■ Type of backup
■ Pipe used
■ Name of pipe
5. Click Start.
Restoring MaxDB databases
The SAP Agent supports the restore of SAP applications that run on the MaxDB(SAPDB)
database.
Use the DBM command line interface or the MaxDB Database Manager graphical user
interface to initialize and send a restore job to MaxDB's BACKINT interface. MaxDB’s
BACKINT then sends the restore job to the Symantec SAP Agent BACKINT interface,
which executes the job. The SAP Agent supports restores to both local and remote
Backup Exec media servers.
The SAP Agent supports the following SAP DB restore functions:
■ Restore last backup.
■ Restore a specified backup from history.
■ Restore a medium.
■ Restore database to a specific time.
To restore data
❖ From the MaxDB Database Manager, run the Recovery Wizard, ensuring the
database is in Admin mode.
1458 Administrator’s Guide

Appendix O, Symantec Backup Exec Agent for SAP Applications
About performing disaster recovery using the SAP Agent
About performing disaster recovery using the SAP Agent
To recover your SAP database server after a catastrophic failure, you must implement a
backup strategy before a failure occurs. When developing a disaster recovery plan, the
following backup strategies should be used:
■ Make at least one flat file database backup and make regular offline backups using
CCMS. See your SAP Database Administrator’s Guide.
■ Back up the Windows directory on the SAP database server, including the Windows
registry.
■ If the structure of the database is altered, perform a full offline database backup.
For example, if you create a new tablespace or remove an old one, make a complete
offline database backup.
■ Always include the backint.xml file in your regular flat file backups of the SAP
database server. The backint.xml file is usually located in the following directory:
Usr\sap\\sys\exe\run
■ Schedule full online backups of your SAP database server regularly.
Related Topics:
“Configuring biparam.ini” on page 1447
SAP disaster recovery prerequisites
The following backups are required to fully recover your SAP database server in the
event of a disaster.
■ Create a full SAP database server file system backup using Backup Exec.
When creating this backup, include both the SAP database directory and the
Windows system directory. However, if the database must remain open, do not
include the SAP database tablespace data files in this backup.
■ Create a second backup containing the SAP database tablespace data files.
See your SAP Database Administrators Guide for details.
After creating these backups, you can recover your SAP database server as needed.
Related Topics:
“Backing up data” on page 345
1459

About performing disaster recovery using the SAP Agent
Recovering a remote SAP database server from a disaster
To recover a remote SAP database server from a disaster
1. Re-install the Microsoft Windows operating system on the SAP database server.
During the re-install process, install Windows into a temporary directory that you
can delete after your SAP database server is back up and running.
2. At the media server, and using the storage media containing the FULL flat file SAP
database server file system backup, restore the entire contents of the media to the
SAP database server using Backup Exec.
3. Reboot your SAP database server.
The computer reboots using its original version of Windows. The system contains
the original version of Windows, the SAP Agent, the SAP database minus the
tablespaces, and any other files contained on the full backup media.
4. If you have a full offline SAP database backup, restore your last full offline SAP
database backup and start your database.
If you do not have a full offline database backup, your database is operational.
Proceed to step 5.
5. Restore the backint.xml file from the latest full server backup.
The backint.xml file correlates the SAP catalog with the Backup Exec catalog.
6. To bring your database up-to-date, restore your most recent online or offline SAP
database backup.
7. At the media server, run another restore operation. This time, use the SAP Agent to
restore the storage media containing all of the SAP tablespace data files.
8. When the restore operation completes, open the CCMS console, and click Check and
Repair Database.
9. Click Automatic Recovery, and then follow the online prompts.
1460 Administrator’s Guide

Appendix O, Symantec Backup Exec Agent for SAP Applications
About performing disaster recovery using the SAP Agent
Recovering a combination SAP database server and media server
To recover a combination SAP database server and media server
1. Re-install the Microsoft Windows operating system on the SAP database server
media server.
During the re-install process, install Windows into a temporary directory that you
can delete after your SAP database server media server is running.
2. Re-install Backup Exec.
3. Recatalog the media containing the full flat file SAP database server file system
backup, and the media containing the SAP database tablespace data files.
4. Restore the entire contents of the media containing the full flat file server file
system backup.
This restores your original Windows system, along with any services required to run
your SAP database.
5. Reboot the computer after the restore operation completes.
Because the full system backup was restored, your computer now boots using its
original version of Windows. The system now contains the original version of
Windows, the SAP Agent, the SAP database minus the tablespaces, and any other
files contained on the full backup media.
6. Restore the backint.xml file from the latest full server backup.
This file correlates the SAP catalog with the Backup Exec catalog.
7. Run another restore operation.
This time, use the SAP Agent to restore the media containing all of the SAP
tablespace data files.
8. When the restore operation completes, open the CCMS console, and select Check
and Repair Database.
9. Select Automatic Recovery, and then follow the online prompts to complete
Disaster recovery of the SAP database server.
1461

About performing disaster recovery using the SAP Agent
1462 Administrator’s Guide

Appendix
Symantec Backup Exec Agent
for DB2 on Windows Servers
P
The Symantec Backup Exec Agent for DB2 on Windows Servers (DB2 Agent) protects IBM
DB2 databases on Microsoft Windows computers.
About the Backup Exec DB2 Agent
The following features are available with the DB2 Agent:
■ The ability to initiate backup and restore operations:
■ From Backup Exec
■ From the IBM DB2 Control Center or command line processor as a Database
Administrator (DBA). Operations that the DBA performs on the Control Center
or command line processor are referred to as DBA-initiated operations. See your
IBM DB2 documentation for information about the Control Center or command
line processor.
■ Support for the DB2 log archiving methods that are known as user exit and
VENDOR.
■ Multiple data stream support for increased performance during backup and restore
operations.
The DB2 Agent supports DB2 database versions 8.1 FixPak 7 and 8.2. In addition, the
DB2 Agent supports the following operating systems:
■ Windows 2000 Standard Edition, Advanced Edition, and Datacenter Edition.
■ Windows Server 2003 (32-bit) Standard Edition, Advanced Edition, and Datacenter
Edition.
1463

Installation and configuration requirements for the DB2 Agent
Note Backup Exec does not support DB2 running as a 32-bit Windows-based application
on a 64-bit Windows operating system.
Related Topics:
“Installation and configuration requirements for the DB2 Agent” on page 1464
“About DBA-initiated jobs for DB2 operations” on page 1475
Installation and configuration requirements for the DB2
Agent
The DB2 Agent is installed as a separate, add-on component of Backup Exec for
Windows Servers. To protect local or remote DB2 instances, you must install the
following Backup Exec options:
Installing components for the DB2 Agent
Install this agent In this location For more information
Backup Exec DB2 Agent On the media server See “Installing Backup Exec options to
the local computer” on page 85.
Backup Exec Remote
Agent for Windows
Systems
After you install the required components, you must configure them for the DB2 Agent
before you can back up or restore any DB2 resources. Do the following:
Configuring the DB2 Agent
On remote Windows
computers
To configure DB2 Agent information Go to
On the computer on which the DB2
instances are installed
See “Installing the Remote Agent for
Windows Systems” on page 97.
“Configuring the DB2 Agent on Windows computers” on
page 1465.
On the media server “Configuring database access on the media server for
DB2 operations” on page 1469.
1464 Administrator’s Guide

Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
Installation and configuration requirements for the DB2 Agent
Configuring the DB2 Agent on Windows computers
Before you can back up or restore DB2 databases, you must use the Remote Agent Utility
to:
■ Configure information about the DB2 instances for the DB2 Agent.
■ Enable database access for the media server.
If you enable DB2 log archiving, you must configure additional information for:
■ The DB2 instance that contains the source database for the archived logs during
backups.
■ The DB2 instance that contains the destination database for any roll forward
operations.
The information that you configure for an instance applies to all of the databases that
are contained in that instance.
Whenever DB2 instance information changes, you must update the Remote Agent
Utility. If credential information is not updated or is incorrect, the error “Unable to
attach to a resource...” may appear when you run a backup job.
To configure the DB2 Agent on Windows computers
1. On the computer on which the Remote Agent is installed, on the taskbar, click Start
> All Programs > Symantec Backup Exec for Windows Servers > Backup Exec
Remote Agent Utility.
When the Remote Agent Utility is running, an icon appears in the system tray. You
can double-click this icon to view the utility.
2. Click the DB2 tab.
3. Do one of the following:
To add a DB2 instance ◆ Click New.
To change an existing
DB2 instance
◆ Go to step 4.
◆ Select the instance that you want to edit.
◆ Click Edit.
◆ Go to step 4.
To delete a DB2 instance ◆ Select the instance that you want to delete, and then click
Delete.
◆ Go to step 5.
1465

Installation and configuration requirements for the DB2 Agent
4. Complete the appropriate options as follows:
Local instance name To add an instance, enter the name of the DB2 instance. If you are
editing an instance, you cannot change the instance name.
User name Type the user name for the DB2 instance. The user name must
have the following:
◆ A valid authorization ID, or the CONNECT privilege to all the
databases that reside in this DB2 instance.
◆ The correct authority levels and privileges.
Correct authority levels may include SYSADM, SYSCTRL,
SYSMAINT, and DBADM.
If the credentials are incorrect, the error “Unable to attach to
a resource...” may appear when you run a backup job.
If the credentials for the DB2 instance change, you must update
the credentials in this field.
You must add this computer name and logon account to the list of
authentication credentials for DB2 servers. See “Configuring
database access on the media server for DB2 operations” on
page 1469.
Password Type the password for the DB2 instance user name.
Confirm password Type the password again to confirm it.
Media server Type the name or IP address of the Backup Exec media server
where you want to process the operations.
You must use the same form of name resolution for all operations.
For example, if you use the IP address of this computer for backup
operations, you must also use the IP address for restore
operations. If you use the full computer name for backup
operations, you must also use the full computer name for restore
operations.
Job template name Type the name of the Backup Exec job template that you want the
DBA-initiated job to use for backup and restore operations. You
create the job template on the DBA-initiated Job Settings dialog
box on the Backup Exec media server. If you do not specify a job
template, the default job template is used.
For databases that have archive logging enabled, enter a separate
archive logs template name in the Archive logs template name
field.
For more information, see “Configuring DBA-initiated job settings
for DB2” on page 1480.
1466 Administrator’s Guide

Archive logs template
name
5. Click OK.
Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
Installation and configuration requirements for the DB2 Agent
To configure database access for DB2 operations on Windows computers
1. On the computer on which the Remote Agent is installed, on the taskbar, click Start
> All Programs > Symantec Backup Exec for Windows Servers > Backup Exec
Remote Agent Utility.
When the Remote Agent Utility is running, an icon appears in the system tray. You
can double-click this icon to view the utility.
2. Click the Database Access tab.
3. Complete the appropriate options as follows:
Enable media server
authentication for Oracle
and DB2 operations
Type the name of the Backup Exec archive logs job template that
uses the user exit or VENDOR method. These methods are
specified for a database on the DB2 Control Center or command
line processor. If you use an incorrect job template name, then log
files cannot be archived correctly.
Note If you use the user exit or VENDOR method for a database,
you must create a Backup Exec job template specifically for
archiving logs. The archive logs job template should specify
destination devices that are different than the devices that
are specified in the job template for database backups.
If the same device is used for both jobs, then the archive log
backup must wait until the database backup completes.
However, the database backup cannot complete until the
archive log backup completes.
For more information on creating and configuring a Backup Exec
job template for DBA-initiated jobs, see “Configuring
DBA-initiated job settings for DB2” on page 1480. For more
information about the user exit or VENDOR method, see “Using
the DB2 database archive logging methods” on page 1476.
Check Enable media server authentication for Oracle and DB2
operations to enter the credentials that the media server will use
for all operations on the DB2 server, including DBA-initiated
operations. The media server also uses these credentials for
authentication of the DB2 server.
You must check this option to enable DB2 operations between the
media server and this computer.
1467

Installation and configuration requirements for the DB2 Agent
User name Type a user name that has administrative rights to this computer.
This logon account is what the media server uses when it
connects to this computer.
Note If you specify an IP address or a fully qualified computer
name as part of the user name, the Remote Agent Utility
may not be able to verify the user account. If the credentials
are incorrect, the error “Unable to attach to a resource...”
may appear when you run a backup or restore job.
You must add this computer name and logon account to the list of
authentication credentials for DB2 servers. See “Configuring
database access on the media server for DB2 operations” on
page 1469.
If the authentication fails when the DB2 resources are backed up,
the backup job fails. If the authentication fails when you browse
the backup sets for a restore job, then the backup sets become
unavailable, and you must run a DBA-initiated restore job to
restore data.
Password Type the password for this logon account, and then confirm it.
Note For security reasons, the logon credentials are not stored
on the remote computer.
Use the full computer
name or IP address for
Oracle and DB2
operations
Check Use the full computer name or IP address for Oracle and
DB2 operations to use either the full computer name or IP
address for operations between the remote computer and the
media server. You must use the same form of name resolution for
all DB2 operations.
For example, if you use the IP address of this computer for backup
operations, you must also use the IP address for restore
operations. If you use the full computer name for backup
operations, you must also use the full computer name for restore
operations.
Name or IP address Type the full computer name or IP address for this computer.
For full computer names, the following rules apply:
◆ The maximum number of characters for each label (the text
between the dots) is 63
◆ The maximum total number of characters is 254, including the
dots, but excluding the \\
◆ The name cannot include the following characters: * | < > ?
1468 Administrator’s Guide

Use a custom port to
connect to the media
server during Oracle and
DB2 operations
4. Click OK.
Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
Installation and configuration requirements for the DB2 Agent
Check Use a custom port to connect to the media server during
Oracle and DB2 operations to change the port that is used for
communications between this computer and the media server
during DB2 operations. By default, port 5633 is used.
If you change the port number on this computer, you must also
change it on the media server, and then restart the Backup Exec
Job Engine Service on the media server.
For information on how to change the port number on the media
server, see “Setting default backup network and security options”
on page 400.
Port number Type the port number to use for operation requests that are sent
to the media server.
5. On the media server, add the name of the DB2 server and the user name that you
entered on the Database Access tab to the media server’s list of authentication
credentials.
See “Configuring database access on the media server for DB2 operations” on
page 1469.
Related Topics:
“Using the DB2 database archive logging methods” on page 1476
“Backing up DB2 resources” on page 1472
“Configuring DBA-initiated job settings for DB2” on page 1480
“Setting application defaults for DB2” on page 1482
Configuring database access on the media server for DB2
operations
You must add the DB2 server name and the logon account name to the media server’s
list of DB2 servers and authentication credentials. The media server has database access
for operations on DB2 instances that are included in the authentication list. Before you
start any backup or restore operations, on the computer on which the DB2 instances are
installed, make sure that you use the Remote Agent Utility to configure instance
information and database access.
The logon account name must have administrative rights to the DB2 server. If the user
name is incorrect or is not provided, or if it does not have administrative rights, then
you cannot perform DB2 backup or restore operations to that computer.
1469

Installation and configuration requirements for the DB2 Agent
To configure database access on the media server for DB2 operations
1. On the media server, on the Tools menu, click Options.
2. On the properties pane, under Job Defaults, click DB2.
3. Click the Modify list button.
On the Authentication Credentials for Oracle and DB2 Servers dialog box, you can
add, edit or delete a server name and a logon account.
4. Click New.
5. Enter the name of the DB2 server on which the instance is installed.
6. To add the logon account name, do one of the following:
Click the arrow Select the logon account name that you want to add.
Click New On the Logon Account Selection dialog box, click New.
For more instructions, see “Creating a Backup Exec logon account”
on page 149.
Use the same logon account format that you use when you enter the logon account
name on the Database Access tab in the Remote Agent Utility. For example, if you
entered Domainname\Username on the Remote Agent Utility, use that same format
on the list of authentication credentials.
7. On the Authentication Credentials for Oracle and DB2 Servers dialog box, click OK.
Related Topics:
“Editing a DB2 server name or logon account on the media server’s list of authentication
credentials” on page 1471
“Configuring the DB2 Agent on Windows computers” on page 1465
“Backing up DB2 resources” on page 1472
“Setting application defaults for DB2” on page 1482
“Configuring DBA-initiated job settings for DB2” on page 1480
“Deleting a DB2 server name or logon account from the media server’s list of
authentication credentials” on page 1472
1470 Administrator’s Guide

Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
Installation and configuration requirements for the DB2 Agent
Editing a DB2 server name or logon account on the media server’s
list of authentication credentials
If the DB2 server name or the logon account name for the DB2 server changes, you must
update the media server’s list of DB2 servers and authentication credentials. Make the
same changes on the DB2 server by using the Remote Agent Utility to configure instance
information and database access.
The logon account name must have administrative rights to the DB2 server. If the user
name is incorrect or is not provided, or if it does not have administrative rights, then
you cannot perform DB2 backup or restore operations to that computer.
To edit a DB2 server name or a logon account on the media server’s list of authentication
credentials
1. On the media server, on the Tools menu, click Options.
2. On the properties pane, under Job Defaults, click DB2.
3. Click the Modify list button.
On the Authentication Credentials for Oracle and DB2 Servers dialog box, you can
add, edit or delete a server name and a logon account.
4. Select the item that contains the server name or logon account that you want to edit.
5. Click Edit.
6. Change the server name, or change the logon account name.
See “Editing a Backup Exec logon account” on page 150.
7. Click OK.
Related Topics:
“Configuring database access on the media server for DB2 operations” on page 1469
“Configuring the DB2 Agent on Windows computers” on page 1465
“Deleting a DB2 server name or logon account from the media server’s list of
authentication credentials” on page 1472
1471

Backing up DB2 resources
Deleting a DB2 server name or logon account from the media
server’s list of authentication credentials
To delete a DB2 server name and a logon account from the media server’s list of
authentication credentials
1. On the media server, on the Tools menu, click Options.
2. On the properties pane, under Job Defaults, click DB2.
3. Click the Modify list button.
On the Authentication Credentials for Oracle and DB2 Servers dialog box, you can
add, edit or delete a server name and a logon account.
4. Select the item that contains the server name or logon account that you want to
delete.
5. Click Delete.
See “Deleting a Backup Exec logon account” on page 153.
6. Click OK.
Backing up DB2 resources
Before you back up DB2 resources, review the following:
■ You must run the Remote Agent Utility on the DB2 server and add information
about the instances before you can perform any backup or restore operations.
When DB2 instance information changes, you must update the Remote Agent
Utility. After you enter these changes, the Backup Exec media server discovers
them.
See “Installation and configuration requirements for the DB2 Agent” on page 1464.
■ If you run database backups and archive logging, you must have at least two storage
devices that are available for the jobs.
■ If you use multiple data streams for the backup job, the number of backup devices
that are available for the job must at least equal the number of data streams. If
archive logging is enabled for the database, an additional backup device must be
available.
1472 Administrator’s Guide

To back up DB2 resources
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
Backing up DB2 resources
3. In the backup selection list, under the Favorite Resources node, expand the Windows
Systems node.
4. Expand the DB2 server that you want to back up.
If the DB2 server is not listed under Favorite Resources, then you can add it.
See “About the Favorite Resources node” on page 318.
5. Select the following objects as appropriate:
Instance Select an instance to back up all of the DB2 databases that it
contains.
Database Select a database to back up all of the partitions that it contains.
Partition Select a partition to back up all of the tablespaces and log folders
that it contains.
Tablespace Select all tablespaces or individual tablespaces to back up.
6. On the Properties pane, under Settings, click DB2.
7. Complete the appropriate options as follows:.
Backup method Select one of the following backup methods:
◆ Full - Back up selections. Select this method to perform a full
backup of DB2 selections.
◆ Differential - Back up changes since last full. Select this
method to back up all database changes since the last full
backup.
◆ Incremental - Back up changes since last full or incremental.
Select this method to back up all database changes since the
last full or incremental backup.
1473

Backing up DB2 resources
Perform the backup
offline
Quiesce the database
before offline backup
8. To configure multiple data streams for backup, under Destination, click Device and
Media.
9. Complete the appropriate options as follows:
Maximum number of
devices to use for
resources that support
multiple data streams
Minimum number of
devices, terminate job if
fewer devices are
available
Check Perform the backup offline to have Backup Exec take the
database offline before you start the backup job. Backup Exec
brings the database online after the backup job is complete.
If circular logging is enabled for the database, then you must
select this option; otherwise the backup job fails.
Check Quiesce the database before offline backup to have
Backup Exec force users off the database before it brings the
database offline for the backup job. Users who are not actively
running databases tasks are forced off the database. Users who
are running database tasks can complete their current task before
being forced off.
Enter the maximum number of devices that the backup job can
use.
When you run a DB2 database backup job, Symantec recommends
that the number of backup devices that are available for the job is
at least equal to the number of streams. If archive logging is
enabled for the database, an additional backup device must be
available.
If you specify more than one device, you must choose one of the
following items as a destination device for the backup job:
◆ A device pool.
◆ A backup-to-disk folder that has at least two concurrent
operations enabled.
See “Creating a backup-to-disk folder” on page 222.
Note This feature is not available for DBA-initiated jobs.
Enter the minimum number of devices that the job can use.
If the job cannot acquire the minimum number of devices, the job
fails.
Note This feature is not available for DBA-initiated jobs.
10. Complete the remaining backup job properties as necessary.
For more information, see “Backing up data” on page 345.
1474 Administrator’s Guide

Related Topics:
“Configuring DBA-initiated job settings for DB2” on page 1480
“Setting application defaults for DB2” on page 1482
About DBA-initiated jobs for DB2 operations
Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
About DBA-initiated jobs for DB2 operations
Backup Exec supports DBA-initiated backup, restore, redirected restore, and recovery of
DB2 databases.
The Backup Exec DB2 Agent installs the following files:
Files that are installed with the DB2 Agent
File Description
The vendor dll file db2sqluv.dll and
the user exit program db2uext2.exe
These files are installed in the Windows System
Directory. The Windows System Directory may have a
pathname such as:
C:\winnt\system32 or D:\windows\system32.
On the DB2 Control Center, if you use a vendor library or
a user exit program as a method for archiving log files,
then db2sqluv.dll and db2uext2.exe are used by default.
See “Using the DB2 database archive logging methods” on
page 1476.
A configuration file named db2.conf This file includes specifications for redirected restore
jobs and roll forward operations. The Backup Exec vendor
dll file and user exit program use the information in this
file.
The db2.conf file is installed to the following location on
the media server:
\Program Files\Symantec\Backup
Exec\db2.conf
The db2.conf file is installed to the following location on
the remote DB2 server:
\Program Files\Symantec\Backup
Exec\RAWS\db2.conf
See “About the db2.conf file” on page 1477.
1475

About DBA-initiated jobs for DB2 operations
Files that are installed with the DB2 Agent
File Description
Example scripts for backup and
restore operations
Review the following notes before you run DBA-initiated jobs for DB2:
■ Complete all of the preparations that are listed in “Installation and configuration
requirements for the DB2 Agent” on page 1464.
■ If you use a domain administrator logon account to browse DB2 databases on a DB2
server, you may not be able to expand or select databases for operations from
Backup Exec. If this situation occurs, add the domain administrator account to the
DB2ADMNS group.
■ On the media server, the logon account that you use to back up the DB2 resources
should have backup operator or administrator rights.
Related Topics:
“About troubleshooting DB2” on page 1488
“Using the DB2 database archive logging methods” on page 1476
Using the DB2 database archive logging methods
DB2 supports the user exit and VENDOR methods for archiving its log files. Backup Exec
provides a user exit program and a vendor dll file to support these methods. When the
you use the user exit method, Backup Exec backs up the archive logs by using the user
exit program named db2uext2.exe. When you use the VENDOR method, Backup Exec
backs up the archive logs by using the Backup Exec vendor dll file named db2sqluv.dll.
Before you can use the user exit or VENDOR method, you must add information in the
Remote Agent Utility about the DB2 instances that contain:
■ The source database for the archive logging operations.
These example scripts are available for you to run at the
DB2 command line processor.
These scripts are installed to the following location:
\Program Files\Symantec\Backup
Exec\scripts\DB2
■ The destination database for any roll forward operations.
You must also add the DB2 server name that contains these instances to the media
server’s list of DB2 servers and authentication credentials.
1476 Administrator’s Guide

Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
About DBA-initiated jobs for DB2 operations
If you use archive logging for DB2 databases, you must create a Backup Exec
DBA-initiated job settings template that is used exclusively by archive logging jobs. This
job template must specify destination storage devices that are different than the devices
that are specified in the job template that is used for database backups. You must add
the name of the DBA-initiated job settings template for archive logs in the Remote Agent
Utility.
Some errors for DBA-initiated jobs that use the vendor dll file db2sqluv.dll are described
in the following table.:
Errors that may occur while using db2sqluv.dll
Error Description
514 Backup Exec could not find the logon account
information that is required for database access. Ensure
that the information has been updated in the media
server's list of authentication credentials.
SQL2062N See the Application log in the Windows Event Viewer for
details about the error.
Related Topics:
“Configuring the DB2 Agent on Windows computers” on page 1465
“Configuring DBA-initiated job settings for DB2” on page 1480
“About troubleshooting DB2” on page 1488
“About the db2.conf file” on page 1477
About the db2.conf file
The Backup Exec db2.conf file provides the settings for DBA-initiated redirected restore
jobs and roll forward jobs. You must configure the required settings in the db2.conf file
before you can run DBA-initiated redirected restore or roll forward jobs.
The Backup Exec DB2 configuration file, db2.conf, consists of a series of keywords and
values that define how to back up the database and the archive logs. Use this file to
define the source database and the source instance for the redirected restore operations
and redirected roll forward operations.
Instructions and examples are in the db2.conf file. For an example of a completed
db2.conf file, see “Configuring DBA-initiated job settings for DB2” on page 1480.
1477

About DBA-initiated jobs for DB2 operations
Related Topics:
“About DBA-initiated jobs for DB2 operations” on page 1475
“Editing a db2.conf file” on page 1478
Editing a db2.conf file
The db2.conf file contains two blocks of settings. The first block contains the settings
that you can use to perform a redirected database restore using Backup Exec’s vendor dll
db2sqluv.dll. The second block contains the settings that you can use to perform a
redirected roll forward of a database using the Backup Exec vendor dll db2sqluv.dll. or
user exit program db2uext2.exe.
For an example of a completed db2.conf file, see “Configuring DBA-initiated job settings
for DB2” on page 1480.
To edit a db2.conf file
1. On the computer on which the DB2 instances that you want to redirect are installed,
open the db2.conf file for editing.
On the media server, the db2.conf file is located at the following path:
\Program Files\Symantec\Backup Exec\db2.conf
On remote DB2 servers, the db2.conf file is located at the following path:
\Program Files\Symantec\Backup Exec\RAWS\db2.conf
The db2.conf file consists of keyword lines that form object identifiers. The lines in
each object identifier specify the database and other information.
2. Remove the pound sign (#) that precedes the lines and add the appropriate
information.
3. Save and close the db2.conf file.
4. Repeat step 1 - step 3 on each DB2 server that you want to back up with the DB2
Agent.
After you complete a redirected restore job or a roll forward, you must remove the
instructions for that database. If you do not remove the instructions, they apply to
all subsequent restore operations.
Related Topics:
“About DBA-initiated jobs for DB2 operations” on page 1475
“Example db2.conf file” on page 1479
1478 Administrator’s Guide

Example db2.conf file
The sample db2.conf file is as follows:
Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
About DBA-initiated jobs for DB2 operations
#
# The following settings are used by Backup Exec to perform
# an alternate restore or a rollforward of a DB2 database during a
# a DBA-initiated operation using Backup Exec's vendor dll
# db2sqluv.dll or user exit program db2uext2.exe.
# Reminders:
#
# Uncomment the following lines by removing the # preceding every line
# and add appropriate data to perform an alternate restore/rollforward operation.
# You can add more blocks for any additional alternate restore/rollforward
operations.
# -------------------------
# Settings for alternate database restore using
# Backup Exec's vendor dll db2sqluv.dll
# -------------------------
#OBJECTTYPE ALTERNATE # Specifies an alternate restore
#SRCINST srcinstname # Names the source instance that was backed up
#SRCALIAS srcaliasname # Names the source database alias that was backed up
#DESTINST destinstname # Names the destination instance name
#DESTALIAS destaliasname # Names the destination database alias name
#ENDOPER # Ends the object identifier
OBJECTTYPE ALTERNATE # Specifies an alternate restore
SRCINST myinst1 # Names the source instance that was backed up
SRCALIAS mydb1 # Names the source database alias that was backed up
DESTINST myinst2 # Names the destination instance name
DESTALIAS mydb2 # Names the destination database alias name
ENDOPER # Ends the object identifier
OBJECTTYPE ALTERNATE # Specifies an alternate restore
SRCINST myinst3 # Names the source instance that was backed up
SRCALIAS mydb3 # Names the source database alias that was backed up
DESTINST myinst4 # Names the destination instance name
DESTALIAS mydb4 # Names the destination database alias name
ENDOPER # Ends the object identifier
# ----------------------------------
# The following are settings for an alternate database rollforward operation using
# Backup Exec's vendor dll db2sqluv.dll or user exit program db2uext2.exe.
# Use this block to indicate the source database
# if the log files were archived from a different source database.
# ----------------------------------
# If DB2 log file archiving is enabled (DB2 USEREXIT ON), DB2 will invoke
# the Backup Exec user exit program to back up and restore DB2 archive log files.
# If DB2 log file archiving is enabled for vendor dll, DB2 will invoke the
# Backup Exec vendor dll db2sqluv.dll to back up and restore DB2 archive log files.
# DESTALIAS parameter indicates the destination database alias for the user exit.
1479

About DBA-initiated jobs for DB2 operations
# DESTINST parameter indicates the destination instance alias for the user exit.
# SRCALIAS parameter indicates the source database alias from which log files were
# archived and should now be used for the rollforward operation.
# SRCINST parameter indicates the source instance from which log files were
# archived and should now be used for the rollforward operation.
#
#OBJECTTYPE ARCHIVE # Specifies that this block is for alternate rollforward.
#ARCFUNC SAVE
#DESTALIAS destaliasname # Names the destination database alias name for which this
setting applies.
#DESTINST destinstname # Names the destination instance name name for which this
setting applies.
#SRCALIAS srcaliasname # Names the source database alias from which log files
were archived.
#SRCINST srcinstname # Names the source instance from which log files were
archived.
#ENDOPER # Ends the object identifier
OBJECTTYPE ARCHIVE # Specifies that this block is for alternate rollforward.
ARCFUNC SAVE
DESTALIAS mydb1 # Names the destination database alias name for which this setting
applies.
DESTINST myinst1 # Names the destination instance name for which this setting
applies.
SRCALIAS mydb2 # Names the source database alias from which log files were
archived.
SRCINST myinst1 # Names the source instance from which log files were archived.
ENDOPER # Ends the object identifier
Configuring DBA-initiated job settings for DB2
When you create a DBA-initiated backup operation, you can specify the default job
template in Backup Exec, or specify a new job template that you create in Backup Exec.
The job template contains the settings that Backup Exec applies to DBA-initiated jobs.
Make sure that the name of the job template that you want to use is also configured in
the instance information on the Windows computer where the DB2 instance runs. See
“Configuring the DB2 Agent on Windows computers” on page 1465.
Note the following about DBA-initiated jobs:
■ DBA-initiated jobs fail when the related job template is deleted. To stop
DBA-initiated jobs from running, delete the related DBA-initiated job template.
■ All DBA-initiated backup and restore jobs are deleted after the jobs complete.
■ You cannot set minimum device requirements for DBA-initiated jobs.
1480 Administrator’s Guide

To configure DBA-initiated job settings for DB2
Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
About DBA-initiated jobs for DB2 operations
1. On the Tools menu, click Options, and then click DBA-initiated Job Settings.
2. Do any of the following:
To create a new job
template
◆ Click New.
If you use the user exit or the vendor library method to
archive logs, you must create an Archive log job template
specifically for archiving logs. The archive logs job template
should specify destination devices that are different than the
devices that are specified in the job template for database
backups.
The archive logs job template name must be the same name
that you entered in the Archive logs template name field in
“Configuring the DB2 Agent on Windows computers” on
page 1465.
◆ Proceed to step 3.
To edit a job template ◆ Select the job template that you want to edit.
◆ Click Edit.
◆ Proceed to step 3.
3. On the DBA-initiated Job Settings pane, under Destination, click Device and Media,
and then complete the options as appropriate.
For more information about completing device and media options, see “Device and
media options for backup jobs and templates” on page 354. Some options are not
available for the DBA-initiated job settings.
4. On the DBA-initiated Job Settings pane, under Settings, click General, and then
complete the options as appropriate.
For more information about General options, see “General options for backup jobs
and templates” on page 357. Some options are not available for the DBA-initiated job
settings.
5. On the Properties pane, under Settings, click Network and Security, and then
complete the options as appropriate.
For more information about setting and managing encryption keys, see “Encryption
keys” on page 407. Some options are not available for the DBA-initiated job settings.
6. If you want Backup Exec to notify someone when the backup job completes, click
Notification, and then complete the options as appropriate.
1481

Setting application defaults for DB2
For more information about notification, see “Assigning notification recipients for
completed jobs” on page 565.
7. Click OK.
Related Topics:
“Deleting a job template for DBA-initiated jobs for DB2” on page 1482
Deleting a job template for DBA-initiated jobs for DB2
To delete a job template for DBA-initiated jobs for DB2
1. On the Tools menu, click Options, and then click DBA-initiated Job Settings.
2. Select the job template that you want to delete.
3. Click Delete.
4. Click OK.
Related Topics:
“Configuring DBA-initiated job settings for DB2” on page 1480
Setting application defaults for DB2
You can use the defaults that Backup Exec sets during installation for all DB2 backup
jobs, or you can choose your own defaults.
To set application defaults for DB2
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click DB2.
1482 Administrator’s Guide

3. Complete the appropriate options as follows:
Backup method Select one of the following backup methods:
Perform the backup
offline
Quiesce the database
before offline backup
4. Click OK.
Related Topics:
“Backing up DB2 resources” on page 1472
“Restoring DB2 data” on page 1484
“About troubleshooting DB2” on page 1488
Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
Setting application defaults for DB2
◆ Full - Back up selections. Select this method to perform a full
backup of DB2 selections.
◆ Differential - Back up changes since last full. Select this
method to back up all database changes since the last full
backup.
◆ Incremental - Back up changes since last full or incremental.
Select this method to back up all database changes since the
last full or incremental backup.
Check Perform the backup offline to have Backup Exec take the
database offline before you start the backup job. Backup Exec
brings the database online after the backup job is complete.
Check Quiesce the database before offline backup to have
Backup Exec force users off the database before it brings the
database offline for the backup job. Users who are not actively
running databases tasks are forced off the database. Users who
are running database tasks can complete their current tasks
before being forced off.
Modify list Click Modify list to add the DB2 computer name and the logon
account name to the media server’s list of authentication
credentials for DB2 servers.
See “Configuring database access on the media server for DB2
operations” on page 1469.
1483

Restoring DB2 data
Restoring DB2 data
Before you restore DB2 resources, make sure that you have completed all of the
preparations that are listed in “Installation and configuration requirements for the DB2
Agent” on page 1464.
To restore DB2 data
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. On the Properties pane, under Source, click Selections.
4. Click the View by Resource tab.
5. Expand the All Resources icon.
6. Expand the system resource that contains the database instance that you want to
restore.
7. Do one of the following:
To restore the entire
database
8. On the properties pane, under Settings, click DB2.
9. Complete the appropriate options as follows.
Check Current Database.
Note If the database is offline, the Current Database is empty and
you cannot make selections.
To restore a backup set Check a backup set, or a historical set.
To restore a table space Expand either Current Database or a backup set, and then check
any of the table spaces that you want to restore.
Restore from full and/or
incremental backups
To the most recent
available
Check Restore from full and/or incremental backups to enable
restore options.
Select this option to restore the DB2 database to the most recent
full and incremental backups that are available.
1484 Administrator’s Guide

Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
Restoring DB2 data
To a point in time Select this option to restore data up to and including a point in
time that is in the job log. After the point in time, recovery stops.
In the Date box, select the part of the date that you want to
change, and then enter a new date or click the arrow to display a
calendar from which you can select a date.
In the Time box, select the part of the time that you want to
change, and then enter a new time or click the arrows to select a
new time.
Roll forward using logs Check Roll forward using logs to enable a restore of a database
that has archive logging enabled. To restore a database
completely, you must also check Restore from full and/or
incremental backups.
You can restore the database, and then perform the roll forward
operation later.
Note For databases that have circular logging enabled, you must
uncheck Roll forward using logs or the job will fail.
To the most recent
available
Select this option to roll the DB2 database forward to the most
recent logs that are available.
To a point in time Select this option to restore logs up to and including a point in
time. After the point in time, recovery stops.
In the Date box, select the part of the date that you want to
change, and then enter a new date or click the arrow to display a
calendar from which you can select a date.
In the Time box, select the part of the time that you want to
change, and then enter a new time or click the arrows to select a
new time.
Override default log file
path on DB2 server for
this job
Bring database online
when finished rolling
forward
Specify an alternate log file path location to search for archive log
files during the roll forward operation. You should specify an
alternate location if archive log files were moved to a location
other than the location that was specified by the logpath database
configuration on the destination DB2 server. Type a drive letter,
and then the path name, for example, C:\temp.
Check Bring database online when finished rolling forward to
ensure that the database is brought online as soon as the recovery
is finished.
1485

Redirecting a restore of DB2 data
10. Select other restore options from the Properties pane as appropriate, and then start
the restore job.
For more information see “Restoring data” on page 483.
11. Run a full backup of the restored database.
Related Topics:
“Setting application defaults for DB2” on page 1482
“About troubleshooting DB2” on page 1488
Redirecting a restore of DB2 data
The instance that you are redirecting DB2 data to must already exist. Backup Exec does
not create a new instance.
To redirect a restore of DB2 data
1. Follow the instructions for restoring DB2 data in “Restoring DB2 data” on page 1484.
2. After you select options on the Restore Job Properties dialog box for DB2, on the
Properties pane, under Destination, click DB2 Redirection.
3. Select the appropriate options as follows:
Redirect DB2 instance to server Check Restore DB2 instance to server to redirect the
restore of the DB2 instance to a server other than the
source server.
Server Type the name of the server to which you want to
redirect the restore job.
Server logon account Type a logon account that has rights to restore data to
the server to which you want to redirect the restore
job.
Redirect to a new instance Check Redirect to a new instance to redirect the
restore of a database to another instance.
The instance that you want to redirect to must already
exist or the job fails.
Instance Type the name of the instance to which you are
redirecting the restore of the database.
1486 Administrator’s Guide

Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
Redirecting a restore of DB2 data
Instance logon account If you want to change the logon account, type a logon
account for the database that you want to restore. This
logon account must have backup operator or
administrator privileges.
Restore to a new database Check Restore to a new database to redirect the
restore of the database to a new database other than
the source server.
Database name Type the name of the database to which you want to
redirect the restore job.
Drive to restore to Type a drive to which you want to redirect the DB2
database.
Restore log location Specify the full path of the location where you want the
log files for the new database to reside.
Redirect containers Check Redirect containers to specify a different
location for the DMS and/or SMS containers for the
tablespaces or database that you want to restore.
SMS tablespace container relative
path
Type the path to which you want to redirect the system
managed space (SMS) table spaces containers.
For example, you restore the tablespace TS1, which has
the following SMS and DMS containers:
C:\TS1Containers\SMS\SMSCONT001\
C:\TS1Containers\SMS\SMSCONT002\
C:\TS1Containers\DMS\DMSCONT001
C:\TS1Containers\DMS\DMSCONT002
You can redirect the SMS and DMS containers to
different locations by typing the path for the SMS
container as D:\TS1SMS\. Type the path for the DMS
container as D:\TS1DMS\. When the tablespace is
restored, the containers are restored as follows:
SMS containers
D:\TS1SMS\SMSCONT001\
D:\TS1SMS\SMSCONT002\
DMS containers
D:\TS1DMS\DMSCONT001
D:\TS1DMS\DMSCONT002
1487

About troubleshooting DB2
DMS tablespace container relative
path
4. Start the redirected restore job or select other restore options from the Properties
pane.
After the restore job is complete, Symantec recommends that you run a full backup
of the restored data.
Related Topics:
“About troubleshooting DB2” on page 1488
About troubleshooting DB2
Type the path to which you want to redirect the
database managed space (DMS) table space containers.
See the example in the description of the SMS
tablespace container relative path field.
What should I do if roll forward operations fail when I redirect a restore of DB2?
For complete recovery of databases for which archive logging is used, you must restore
both the database and the archived logs. This operation is known as roll forward. If you
used the VENDOR method, then db2sqluv.dll is located in the Windows system
directory. This directory can be located in different paths, such as:
C:\winnt\system32 or D:\windows\system32
Information about the archival method and the location of the db2sqluv.dll is in each
backup of the database. If you restore the backup to another computer, the information
about the location of the db2sqluv.dll points to the same path that is on the source
computer. However, the computer that you redirected the restore to may have a
different path for the Windows system directory. For example, on the source computer,
the db2sqluv.dll may be located in the Windows system directory, in the path:
C:\winnt\system32
On the computer that you redirect the restore to, the Windows system directory may use
another path, such as:
D:\windows\system32
When you run the roll forward on the restored database, DB2 attempts to run
db2sqluv.dll from the Windows system directory path on the source computer. The roll
forward fails because the db2sqluv.dll is not located in that path. To run a successful roll
forward, db2sqluv.dll must exist in the same path on source and destination computers.
1488 Administrator’s Guide

Appendix
Symantec Backup Exec Agent
for Microsoft Data Protection
Manager
Q
The Symantec Backup Exec Agent for Microsoft Data Protection Manager (DPM Agent)
lets you back up and restore the Microsoft Data Protection Manager (DPM) environment
and DPM replicated data with Backup Exec.
With the DPM Agent, you can:
■ Back up available DPM databases, protected file servers, and shadow copies.
■ Restore DPM data to the DPM server, a file server in the protection group, or an
alternate destination.
How to install the DPM Agent
To back up and restore DPM components, you must install the following Backup Exec
components in the following order:
■ On the Backup Exec media server, install the DPM Agent.
See “Installing Backup Exec options to the local computer” on page 85.
■ On the DPM server, install the DPM Agent and the Remote Agent for Windows
Systems.
See “Installing Backup Exec options to remote computers” on page 92.
■ [Optional] If you want to restore data that is backed up by Backup Exec to file servers
in the DPM protection group, you must install the Backup Exec Remote Agent for
Windows Systems on those file servers. You must have the correct permissions and
rights to restore files to these servers.
1489

About the DPM backup selections tree
About the DPM backup selections tree
You can select the following DPM data sources from the Microsoft Data Protection
Manager node in the backup selections tree:
DPM components
To back up See
DPM databases “About Backing Up DPM Databases” on page 1491
DPM Protected
Servers
Data Protection Manager Backup Job Selections
“About Backing up DPM protected servers” on page 1491
Replicas “About Backing up DPM replicas” on page 1492
Shadow Copies “About Backing up DPM shadow copies” on page 1492
Databases
File server
Replicas
Shadow copies
1490 Administrator’s Guide

About Backing Up DPM Databases
Appendix Q, Symantec Backup Exec Agent for Microsoft Data Protection Manager
About the DPM backup selections tree
DPM databases include DPM settings and configuration information such as protection
group definitions and schedules.
Include the DPM server’s System State in your normal backup schedule. If you plan to
make significant changes to the server, verify that you have a current backup of the
System State before you make the changes.
When you select the Databases node for a backup job, Backup Exec performs a
consistency check of the databases before the backup job starts. If the consistency check
fails, try running the backup job at another time. The consistency check is an important
indicator of the integrity of the backup.
Related Topics:
“About Backing up a DPM server” on page 1493
About Backing up DPM protected servers
DPM protected server data includes any shares, volumes, folders, and files replicated to
the DPM server during a DPM backup.
Expand the Protected Servers node to see the list of file servers in the DPM protection
group. Within each file server node, replicas of the data sources (shares, volumes,
folders, and files) appear as volumes. You can back up any of this data with Backup Exec.
Schedule backups for this data according to your typical backup schedule. You can select
all of the protected file server data or select individual shares, volumes, or folders.
By default, DPM scans Active Directory routinely and reports new servers and shares.
Monitor this report so you can add the new DPM selections to Backup Exec jobs you have
set up for the DPM environment.
Related Topics:
“About the DPM backup selections tree” on page 1490
“About Backing up a DPM server” on page 1493
1491

About the DPM backup selections tree
About Backing up DPM replicas
Replicas are complete copies of the data backed up by DPM. DPM creates replicas when a
DPM backup job begins. Each successive DPM backup replicates the changed bytes to the
DPM server.
To back up only critical data, select data from specific replicas. If necessary, you can use
the replica set backups to rebuild server data. Along with backups of the databases, you
can use the replica sets to restore your DPM environment in the event of a disaster.
Related Topics:
“About the DPM backup selections tree” on page 1490
“About Backing up a DPM server” on page 1493
About Backing up DPM shadow copies
Shadow copies are static copies of DPM replicas that are taken at a point in time. They
are created by Volume Shadow Copy Service (VSS).
The Shadow Copies node lists the shadow copies on the DPM server. DPM shadow copies
are listed by the date and time when the DPM shadow copy was created.
Back up each initial shadow copy of your DPM file server. Then, you can back up shadow
copies as needed. For example, if you plan to take a server offline, you should consider
backing up its most recent shadow copy first. This method provides a straightforward
way of restoring the server later, if necessary.
In most environments, you do not need to back up shadow copies frequently. Most of the
data that is captured from shadow copy to shadow copy is redundant because, typically,
the majority of the data on the server does not change between snapshots.
If you select to back up a DPM shadow copy and the shadow copy is deleted before the job
runs, the job fails with the message, “Unable to attach”. Edit the backup job to include a
shadow copy other than the one that was deleted, or remove the shadow copy selection
from the backup job.
Related Topics:
“About the DPM backup selections tree” on page 1490
“About Backing up a DPM server” on page 1493
1492 Administrator’s Guide

About Backing up a DPM server
Appendix Q, Symantec Backup Exec Agent for Microsoft Data Protection Manager
About Backing up a DPM server
Backing up the DPM server is a critical step in safeguarding the DPM environment. If the
DPM server fails, you must recover it quickly to continue hosting DPM replications.
The following components are required to recover a DPM server in a disaster situation,
and they should be included in your normal backup schedule for the DPM server:
■ System State
■ DPM databases
■ The system drive where the operating system is installed and the drive where the
DPM software is installed (if it is not installed on the system drive).
■ Protected file server data
■ Microsoft DPM SQL instance
The DPM SQL instance is captured when you perform a full backup of the DPM
server.
1493

About the DPM restore selection tree
About the DPM restore selection tree
In the Resource view, Backup Exec shows the DPM Databases and Protected Servers
nodes under the Microsoft Data Protection Manager node. DPM shadow copies are listed
under each applicable DPM file server node.
You can select the following DPM data sources from the Microsoft Data Protection node
in the restore selections tree::
DPM components
To back up See
DPM databases “About Restoring DPM databases” on page 1495
DPM Protected Servers “About Restoring DPM protected server data” on page 1495
Replicas “About Restoring DPM protected server data” on page 1495
Shadow Copies “About Restoring DPM shadow copy data” on page 1496
Data Protection Manager Restore Job Selections
Related Topics:
“About Restoring DPM databases” on page 1495
“About Restoring DPM protected server data” on page 1495
DPM Database backups
DPM protected server backups
Replica backup
1494 Administrator’s Guide

“About Restoring DPM shadow copy data” on page 1496
About Restoring DPM databases
Appendix Q, Symantec Backup Exec Agent for Microsoft Data Protection Manager
About the DPM restore selection tree
You may need to restore DPM databases if the databases become corrupted or in disaster recovery
situations.
By default, when you select a database for restore, Backup Exec restores the full database to the
DPM server from which it originated. You may be required to restart DPM services after restoring
the database.
To locate a database, expand the Microsoft Data Protection Manager node. The Databases node
shows the list of DPM database backup sets from which you can restore.
Related Topics:
“About the DPM restore selection tree” on page 1494
“Recovering a DPM server” on page 1497
About Restoring DPM protected server data
You can restore all or part of the data that was backed up from a protected server, including the
entire server, individual folders, or individual files contained within replicas. Selections that are
grayed out in the protected servers node represent data on the protected server that has not been
backed up and therefore, cannot be restored.
You can restore protected server data to one of the following locations:
Locations to which you can restore DPM protected server data
Location Notes
The DPM Server By default, replica sets are restored back to the DPM server from
which they were backed up.
The DPM protected server You can restore data directly to a protected server on which you
have the Backup Exec Remote Agent for Windows Systems
(RAWS) installed. You must also have the correct rights and
permissions.
An alternate location You can redirect the restore of DPM protected server data to
alternate locations, provided you have sufficient rights. RAWS is
required if you are restoring the DATA to a remote system.
Related Topics:
“About the DPM restore selection tree” on page 1494
1495

About the DPM restore selection tree
“Restore jobs and the catalog” on page 484
“Redirecting a restore job” on page 517
About Restoring DPM shadow copy data
Restore shadow copy data by expanding a shadow copy from the file server nodes. The file server
nodes are listed by name in the Resource view.
By default, the shadow copy data is restored to the file server from which it originated. You can
redirect the data to any file server in the protection group or to an alternate location to which you
have rights.
You can restore data from within the shadow copy. For example, if you backed up a shadow copy
that was created on Monday at 10:00 A.M., and someone lost a file named financial.doc on Monday
at 11:00 A.M., you can restore the file from the shadow copy that was created at 10:00 A.M.
Before you restore shadow copy data, you can verify the DPM shadow copy date and time by
viewing the properties of the files that were originally backed up. Verifying the date and time can
be useful if the file owner knows the approximate time a file was lost.
Related Topics:
“About the DPM restore selection tree” on page 1494
“Recovering a DPM server” on page 1497
“Restore jobs and the catalog” on page 484
“Redirecting a restore job” on page 517
1496 Administrator’s Guide

Recovering a DPM server
To successfully recover a DPM server, you need:
■ A new or repaired Windows 2003 server
■ Backups of the required data from the failed server
The requirements for the replacement DPM server are as follows:
Appendix Q, Symantec Backup Exec Agent for Microsoft Data Protection Manager
Recovering a DPM server
■ A Windows 2003 server that contains the same disk structure as the previous DPM
server. For example, if the DPM server contained two physical disks, the new DPM
server must also have two disks that are partitioned and formatted in the same way.
■ The computer name, Windows directory, and the file system (such as, NTFS) must be
the same as the Windows installation on the previous DPM server.
■ If the previous DPM server was in a specific domain or workgroup, do not join the
domain or workgroup during the installation of Windows 2003.
■ The service pack version on the new server must match the service pack that was
installed on the previous DPM server.
For more information about the backup sets that you need to restore all of the data from
the DPM server, see “About Backing up a DPM server” on page 1493.
To recover the DPM server
1. Install the Remote Agent for Windows Systems (RAWS) on the replacement DPM
server.
2. From the Backup Exec media server, set up a job to restore the previous DPM server’s
System State and system drives to the new DPM server.
3. Exclude the DPM replica mount points from the restore job.
The default location for the mount points is C:\Program Files\Microsoft Data
Protection Manager\DPM\Volumes\Replica\[application server name]\[mount point
name].
4. When the restore job completes, you are prompted to restart the DPM server. Do not
restart the server.
5. From the DPM server, rename the copies of the DPM databases back to their original
names.
1497

Recovering a DPM server
The default location for these files is C:\Program Files\Microsoft Data Protection
Manager\Prerequisites\MSSQL$MICROSOFT$DPM$\Data. Rename the database
files as follows:
Rename: To:
master$4idr master.mdf
maslog$4idr mastlog.ldf
model$4idr model.mdf
modellog$4idr modellog.ldf
6. Remove the read-only attribute from the files.
7. Restart the DPM server.
After restarting, you may see warnings about services failing to start. Ignore the
warnings. If you are prompted by Windows hardware Plug-n-Play to restart the
server, restart it.
8. From the Backup Exec media server, restore the SQL Master database from the DPM
instance. Check Automate master database restore option in the Microsoft SQL
settings.
9. Restore the rest of the SQL databases, excluding the SQL Master database, from the
DPM instance.
10. Restore the DPM databases from the DPM Database node in the restore view.
11. From the DPM server, start the DPM Administration Console to check for database
connectivity and to verify that the DPM services start.
12. Shut down the DPM Administration Console.
13. From the DPM server, open a command line window and navigate to C:\Program
Files\Microsoft Data Protection Manager\DPM\bin (assuming DPM was installed to
the default folder).
14. From the command line, type the following command to recover the DPM mount
points:
dpmsync -reallocatereplica
1498 Administrator’s Guide

Appendix Q, Symantec Backup Exec Agent for Microsoft Data Protection Manager
Recovering a DPM server
15. From the Backup Exec media server, restore the DPM replica backup sets (protected
server sets) from the previous DPM server.
16. After the replica backup sets are restored, start the DPM Administration Console.
17. From the Protection view, expand the replicas and click Synchronize...
18. Check Synchronization with consistency check.
19. Create DPM shadow copies, as necessary.
For the latest DPM database disaster recovery instructions, access the Backup Exec
support knowledge base online and search on “DPM disaster recovery”.
1499

Recovering a DPM server
1500 Administrator’s Guide

Appendix
Symantec Backup Exec
Intelligent Disaster Recovery
Option
R
The Symantec Backup Exec for Windows Servers Intelligent Disaster Recovery Option
(IDR) enables you to quickly and efficiently recover Windows computers after a hard
drive failure. The IDR wizards guide you in preparing for disaster recovery and in
recovering a local or remote computer to its pre-disaster state.
Before you can recover computers, you must prepare for a disaster by performing the
following:
1. On the media server, use the IDR Configuration Wizard to specify a location where a
copy of the computer-specific disaster recovery file (*.dr file, where the asterisk
represents the name of the computer being protected) will be stored.
2. Run full backups of the hard drives on the computers to be protected. Include System
State for Windows 2000 and Windows XP computers, and Shadow Copy Components
for Windows 2003 computers. Do not exclude any files from the full backups;
otherwise the *.dr file will not be created.
3. Run the IDR Preparation Wizard to create bootable media for each computer.
The IDR Configuration Wizard guides you through setting an alternate data path for
the *.dr file. The default data path for the *.dr file is on the media server’s hard drive,
but Symantec recommends that you specify an alternate data path to store another
copy of the *.dr file in case the media server’s hard drive is damaged.
Backup Exec creates the *.dr file during a full backup and stores it in the default and
alternate storage locations. Catalog entries from subsequent backups are added to
the *.dr file as these backups are completed.
The IDR Preparation Wizard guides you through the preparation of the bootable
media that you use to recover protected computers. The IDR Preparation Wizard also
lets you copy the *.dr file to a diskette.
1501

Requirements for using IDR
After you have performed these steps for each computer you want to protect, you are
prepared to recover those computers using any of the following recovery methods:
■ Restore a media server (Backup Exec server) using a locally attached storage device.
■ Restore a media server (Backup Exec server) using a remote backup-to-disk folder.
■ Restore a Windows computer by moving the media and the storage device to the
computer being restored, and then restoring the computer through the locally
attached storage device.
■ Restore a remote Windows computer using a network connection to the media server
Related Topics:
“Getting started with IDR” on page 1505
“About creating and updating recovery media” on page 1509
Requirements for using IDR
The following items are required before you use IDR:
■ Symantec Backup Exec for Windows Servers.
■ The Symantec Backup Exec Remote Agent for Windows or NetWare Servers (Remote
Agent) or Backup Exec must be installed on any remote computers to be protected
with IDR.
■ Windows 2000/XP/Server 2003 recovery requires sufficient hard drive space to hold
an entire Windows installation (600 MB to 2 GB).
Note Media servers can be recovered using remote backup-to-disk folders.
Mixed media loaders are not supported for local IDR.
■ A third party ISO 9660-compliant CD burning application to burn the IDR-created
bootable CD image to a CD.
■ A writable or rewritable CD device.
Related Topics:
“Requirements for running the IDR Preparation Wizard” on page 1510
“Using an evaluation version of the IDR option” on page 1503
1502 Administrator’s Guide

Installing the IDR option
Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
Installing the IDR option
You can install IDR as an option during the initial installation of Backup Exec for
Windows Servers, or it can be installed later. All IDR license keys, both local and remote,
are entered on the local media server.
The Remote Agent must be purchased separately from the IDR option, and must also be
installed on any remote computer you want to protect with IDR. The Remote Agent is a
system service that runs on remote servers and enhances backup and restore
performance. It is required for IDR functionality.
Related Topics:
“Installing Backup Exec options to the local computer” on page 85
“Installing Backup Exec options to remote computers” on page 92
“Installing the Remote Agent for Windows Systems” on page 97
“Getting started with IDR” on page 1505
Using an evaluation version of the IDR option
The Intelligent Disaster Recovery option can be installed and evaluated for up to 60 days
or until Backup Exec and IDR are licensed, but you must recreate the IDR recovery media
after the IDR option has been purchased and installed. The recovery media includes the
boot media.
If you must use the IDR Disaster Recovery Wizard to recover a computer after the
evaluation period has expired, you will be prompted to enter a valid IDR license key to
continue the recovery process, unless you recreated IDR recovery media after IDR was
licensed.
1503

Preparing computers for IDR
Preparing computers for IDR
The key to successfully recovering computers after a disaster is to carefully and properly
prepare those computers for a disaster. Preparing computers for IDR involves:
1. Using the IDR Configuration Wizard to determine the alternate location where a
copy of the *.dr file will be stored.
2. Performing full backup jobs on the computers to be protected.
3. Creating the bootable recovery media using the IDR Preparation Wizard.
Tape
Run the IDR Prep
Wizard to create a
tape image.
Run an overwrite
backup job.
Run the IDR Prep
Wizard again to
update a diskette.
Use the Configuration
Wizard to set the alternate
data path.
Do you want to create
bootable tape or CD?
Run a full backup
Run the IDR Prep
Wizard to create
the bootable CD.
Run the IDR Prep
Wizard again to
copy.dr files to
diskette.
CD-ROM
You can create two types of bootable media with the IDR Preparation Wizard:
■ CD-R (CD-Recordable) or CD-RW (CD-Rewritable).
■ Bootable tape (the tape device must support bootable specifications)
1504 Administrator’s Guide

Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
Getting started with IDR
Consider what type of Windows computer is being protected, the available hardware, and
the system BIOS when selecting the type of bootable media to create. You can also
combine media to make updating the *.dr files easier. If you are using bootable CD-R or
CD-RW, or tape, you can still back up the *.dr files to diskette using the IDR Preparation
Wizard so that you can easily update them when required.
Use the chart below to decide which type of media to use.
Bootable media comparison chart
Type of Media Advantages Disadvantages
CD-R, CD-RW ◆ Can also be used to protect
remote Windows computers on
the network.
◆ Can create bootable CD images
for remote computers.
Bootable tape ◆ Requires less preparation and
recovery time than diskettes
◆ Does not required a CD burner.
Getting started with IDR
◆ Requires a BIOS that supports
booting from a CD.
◆ Requires a CD burner.
◆ Requires a BIOS that supports
booting from a SCSI CD and a
bootable tape device that
emulates a SCSI CD drive.
◆ Cannot create bootable tape
images for remote computers.
The IDR Configuration Wizard appears on the Backup Exec Getting Started page. This
wizard prompts you to set an alternate data path for the computer-specific disaster
recovery file, called a *.dr file. The asterisk (*) represents the name of the computer for
which the file was created. A *.dr file contains specific information for the computer
being protected, including:
■ Hardware-specific information for each computer, such as hard disk partition
information, mass storage controller information, and Network Interface Card
information.
■ A list of catalog entries that identify the backup media used to recover the computer.
■ For Windows XP and Windows Server 2003 computers, Windows Automated System
Recovery (ASR) configuration information files (asr.sif and asrpnp.sif). The ASR files
are necessary to recreate partitions on Windows XP and Windows Server 2003
computers during the recovery process.
1505

Getting started with IDR
To run the IDR Configuration Wizard
1. On the Welcome screen, click Next.
Backup Exec automatically creates a *.dr file for the IDR-protected computer when it
is backed up and stores it in the default location on the media server’s hard drive,
which is:
C:\Program Files\Symantec\Backup Exec\idr\Data\.dr.
The Enter An Alternate Data Path screen enables you to specify an alternate location
where a copy of the *.dr file can be stored so that the *.dr file is available even if the
media server has been damaged.
Symantec recommends that the alternate location be on another computer or on a
different physical drive than the default location.
Note When using Backup Exec’s Remote Administrator, specifying drive A: as the
Alternate Data Path points to the media server’s floppy disk drive. The remote
computer’s drive A: is not used as the Alternate Data Path unless the full path is
entered and a valid share exists for this drive. Be sure to check the path and make
sure that the correct computer and directory path are specified.
2. Enter the alternate location where a copy of the *.dr file will be stored, and then click
Next. Symantec recommends that you enter a mapped network location.
Note If you are using IDR to protect a media server in a cluster, or any remote media
server, set the alternate data path to a shared drive or to a drive outside the cluster.
3. The IDR configuration is complete. You are ready to run backups and create bootable
media. Click Finish, and then go to “About creating and updating recovery media” on
page 1509 to continue disaster recovery preparation.
Related Topics:
“About recovering a computer and using the Disaster Recovery Wizard” on page 1525
“About creating and updating recovery media” on page 1509
“Creating a bootable tape image” on page 1514
“Backing up data” on page 345
1506 Administrator’s Guide

Manually setting data paths for the *.dr files
Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
Getting started with IDR
If you did not use the IDR Configuration Wizard to set an alternate data path for the *.dr
files, you can set it manually.
Copies of the *.dr files, which contain the computer-specific information for the
computer being protected, are necessary to automate the recovery of an IDR-protected
computer.
Backup Exec automatically creates the *.dr file during a backup and stores it in the
Disaster Recovery Data Path default location on the media server’s hard drive, which is
C:\Program Files\Symantec\Backup Exec\IDR\Data\.dr.
Symantec recommends that you do not change this default.
You can also specify an alternate location where a second copy of the *.dr file is stored so
that the *.dr file is available even if the media server has been damaged. It is
recommended that the alternate location be on another computer or on a different
physical drive than the default location, and that it be a mapped network drive.
To manually set the default and alternate data paths for the *.dr file
1. From the Tools menu, click Options.
2. Under Settings, click Intelligent Disaster Recovery.
3. Enter the data paths as described in the following table:
Data path Enter a directory path where a copy of the *.dr file for the protected
computer will be stored. Backup Exec automatically creates the *.dr
file during a backup and stores it in the default location on the
media server’s hard drive, which is
C:\Program Files\Symantec\Backup Exec\IDR\Data\.dr.
1507

Getting started with IDR
Alternate path Enter an alternate directory path where a copy of the *.dr files for
the protected computers will be stored. Backup Exec automatically
creates or updates the *.dr file during a backup and stores it in the
specified location during a backup.
It is recommended that you specify an alternate data path that is
not on the media server, or is on a different physical drive than the
default location. During a recovery, you can copy the *.dr file from
the alternate path to a diskette to recover the target computer if the
media server’s hard drive is unavailable.
If you are specifying a remote computer’s hard drive as the
alternate data path, it is recommended that you map a drive letter
to the remote computer. When mapping the drive letter, be sure to
select the Reconnect at Logon option so that you can reconnect to
the drive letter every time you log on. Check the directory later to
make sure the *.dr files were copied.
If you are specifying a directory on a different physical hard drive
on the local computer, browse to or type the drive name and the
path:
d:\drfiles
When using Backup Exec’s Remote Administrator, specifying drive
A: as the Alternate Data Path points to the media server’s floppy
disk drive. The remote computer’s drive A: is not used as the
Alternate Data Path unless the full path is entered and a valid share
exists for this drive. Be sure to check the path and make sure that
the correct computer and directory path are specified.
1508 Administrator’s Guide

About creating and updating recovery media
Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About creating and updating recovery media
Before running the IDR Preparation Wizard to create or update the recovery media, run a
full backup of the hard drive (unless you are creating bootable tape media - see “Creating
a bootable tape image” on page 1514 for details). The *.dr file is created when a full
backup of the entire hard drive is run.
Note If you exclude files from backups, the *.dr file is not created.
After the *.dr file is created, Backup Exec automatically updates it with data from all
subsequent backups (except copy backups) in its default location on the computer and in
the alternate location you specified.
For each backup set that is backed up, an alert appears reminding you to use the IDR
Preparation Wizard to copy the *.dr files to a diskette. Label the diskette and then store it
with the rest of the disaster recovery media. To see the default locations, on the Tools
menu, click Options, and then in the Properties pane, click Intelligent Disaster
Recovery.
If you do not run a full backup before running the IDR Preparation Wizard, you can still
create all the media, but the computer-specific *.dr file will not contain the catalog
entries for the backup sets, and during the recovery phase, you will have to manually
search for and restore the backup sets necessary to recover the computer.
The IDR Preparation Wizard guides you through creating or updating bootable media
and creating or updating a recovery diskette that together contain all of the files required
to recover a Windows computer:
Note For the local media server, update the bootable media after every successful full
backup. For remote computers, you do not need to create or update bootable media
until a disaster occurs, as long as a *.dr file for the remote computer is available on
the media server.
■ The bootable media contain the system files necessary to make a failed Windows
computer operational after a disaster. Create a new bootable image whenever
hardware, SCSI drivers, or storage device drivers change on the computer that is
being protected.
Prepare and test bootable media before a disaster to make sure that the media was
prepared correctly. For more information on testing the bootable media, see “About
recovering a computer and using the Disaster Recovery Wizard” on page 1525.
The bootable media also contains a text file called -diskconf.txt,
which contains information about the computer’s hard disk layout.
■ The recovery diskettes, which you can create and update separately from the
bootable media by using the IDR Preparation Wizard, are labeled the Intelligent
Disaster Recovery diskette 1 and 2, and contain:
1509

About creating and updating recovery media
■ One or more *.dr files, which include computer-specific information such as
hardware-specific information, and catalog entries that identify the media
necessary to recover the computer. For XP and Windows Server 2003 computers,
Windows Automated System Recovery (ASR) configuration information is also
included and is required in order to recreate critical partitions on these
computers during the recovery process.
■ Any necessary drivers.
■ The Disaster Recovery Wizard.
These items are copied to the Intelligent Disaster Recovery diskettes. Create and
update this diskette separately from the bootable media.
At times, the *.dr file may not fit on the Intelligent Disaster Recovery diskettes. If
this occurs, copy the *.dr file to a separate diskette.
Related Topics:
“Creating a bootable CD image” on page 1512
“Creating a bootable tape image” on page 1514
“Creating the Intelligent Disaster Recovery nonbootable CD image only” on page 1516
Requirements for running the IDR Preparation Wizard
Please note the following before running the IDR Preparation Wizard:
■ Run a full backup of the hard drive before creating the boot and recovery media
(unless you are creating a bootable tape image).
When running full backups for IDR preparation:
■ Make sure that volumes (C, D, etc.) have been backed up. The *.dr files are not
created or updated if only individual directories are backed up. Additionally:
■ For Windows 2000 and Windows XP, back up System State.
■ For Windows Server 2003, back up Shadow Copy components.
■ If the server is also the media server, back up the Backup Exec SQL instance.
■ Make sure that if utility partitions are present on the computer, they are selected
for backup. Utility partitions are usually small partitions installed on the hard
disk by OEM vendors and contain system diagnostic and configuration utilities.
For more information on selecting utility partitions for backup, see “Utility
Partition” on page 318.
■ Do not include or exclude files from the backup using the Advanced File
Selection feature.
1510 Administrator’s Guide

Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About creating and updating recovery media
■ Make sure that if the computer is a remote computer, a compatible version of the
Remote Agent has been installed on it. To determine if the Remote Agent is
installed on a remote computer, from Windows Explorer, right-click the remote
server and then from the shortcut menu, click Properties. The status of the
Remote Agent, if installed, is displayed.
About running the IDR Preparation Wizard
The IDR Preparation Wizard guides you through the process of creating the bootable
media used to recover protected computers. You can also use the Intelligent Disaster
Recovery Preparation Wizard to copy disaster recovery *.dr files to a diskette. It can also
guide you through process of creating a non-bootable disaster recovery CD image. A
non-bootable disaster recovery CD can be used to run the Intelligent Disaster Recovery
Wizard if the manufacturer of the computer you are protecting requires you to start the
computer using the manufacturer’s bootable CD.
For example, if you are running a RAID system on a Dell, HP or other type of computer,
you may be required to start the computer with the manufacturer’s bootable CD in order
to install the required RAID drivers.
To start the IDR Preparation Wizard, on the Tools menu, click Wizards> Intelligent
Disaster Recovery Preparation Wizard.
When running the IDR Preparation Wizard, the local computer on which the IDR option
is installed is used by default to create or update the disaster recovery media. However, if
the computer does not have the IDR option installed locally, select Choose a media server
that has the IDR option installed to select another media server on which the IDR option
is installed in order to create or update the media.
Related Topics:
“About creating and updating recovery media” on page 1509
“Requirements for running the IDR Preparation Wizard” on page 1510
“Preparing IDR media by using other media servers” on page 1520
“Creating a bootable CD image” on page 1512
“Creating a bootable tape image” on page 1514
“Creating the Intelligent Disaster Recovery nonbootable CD image only” on page 1516
“Copying the disaster recovery files to a diskette” on page 1519
About creating recovery media after a disaster
If a disaster occurs on a computer before you create the recovery media for it, you can
still create recovery media if you made a full backup of the computer before the disaster.
1511

About creating and updating recovery media
Note For remote computers, this feature is available only if the Remote Agent version
10.0 or higher is installed on the remote computer.
When you create a full backup of a computer, IDR creates a *.dr file that contains system
and catalog information. IDR uses the *.dr file to create the recovery media needed to
recover the computer.
If a disaster occurs on the local media server, you can create recovery media for it after a
disaster if you have another media server and a copy of the *.dr file from the local media
server in an alternate location. Also, you can use the Remote Administrator to recover
the local media server.
Related Topics:
“Creating a bootable CD image” on page 1512
“Creating a bootable tape image” on page 1514
“Creating the Intelligent Disaster Recovery nonbootable CD image only” on page 1516
“Updating bootable media” on page 1517.
Creating a bootable CD image
Use the IDR Preparation Wizard to create a bootable CD image.
The IDR Preparation Wizard also lets you to copy the *.dr file to a diskette on a regular
basis and to recreate the bootable CD image whenever hardware, SCSI drivers, or tape
drivers change on the computer.
In addition to the requirements listed in “Requirements for running the IDR Preparation
Wizard” on page 1510, note the following:
■ Backup Exec does not include support for burning the disaster recovery CD image to
supported CD-R and CD-RW drives. To write the CD image to a CD, use a third party
ISO 9660-compliant application. You should verify the image created by third-party
CD burning software before you need it for disaster recovery.
■ CD-R is the recommended media for creating a bootable CD image. If CD-RW media
is used, the CD drive must have MultiRead ability; otherwise, inconsistent behavior
may occur when running IDR. Test the media with the CD drive before relying on it
for disaster recovery.
■ Prior to a disaster, test the bootable CD to ensure that the computer can start from it.
1512 Administrator’s Guide

To create a bootable CD image
Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About creating and updating recovery media
1. Verify that the computer to be protected has been backed up using the full backup
method.
2. On the Tools menu, click Wizards> Intelligent Disaster Recovery Preparation
Wizard.
By default, the IDR Preparation Wizard uses this computer to create a bootable CD
image. If this computer does not have the IDR option installed locally, select another
media server on which the IDR option is installed to create a bootable CD image.
3. Do one of the following:
To use this computer to create the
bootable CD image
To use another computer to create the
bootable CD image
4. On the Create IDR Boot Media screen, under Create, select Bootable CD Image for use
with CD Writers (ISO 9660) and then click Next.
5. On the Starting CD Image Creation screen, click Next.
6. In the Available Computers pane, select the computers for which you want to create
bootable media, and then click the right arrow to move the computer to the Selected
Computers pane.
7. If a computer you want to protect does not appear in the Available Computers pane,
click Browse to search for the computer. You can also type the name of the computer
in the field next to the Add button and then click Add.
8. Click Next.
9. On the Select Location for CD Image screen, type a path where you want to store the
bootable CD image until you burn a CD, or click Browse to navigate to a storage
location.
10. Click Next.
On the Welcome screen, click Next.
Click Choose a media server that has the IDR
option installed, and see “Preparing IDR media by
using other media servers” on page 1520 for details
1513

About creating and updating recovery media
11. On the Select Path to Windows Operating System Installation Files screen, type a
path to where copies of the operating system setup files are located. You can also
click Browse to navigate to the location.
The Windows operating system you specify in the installation path must match the
Windows version and language of the computer being protected.
You can enter one of the following:
If the files are on a CD Type the CD drive letter.
If the files are stored on a
network or the local computer’s
hard drive
If an .ISO image for operating
system CD is available
12. Click Next.
The wizard begins creating the bootable image.
13. When the bootable CD image is complete, click Next.
14. Click Finish.
15. Use a third-party CD burning software tool to burn the bootable CD image to a CD as
a CD disk image. Do not burn the CD image as a file.
Related Topics:
“About recovering a computer and using the Disaster Recovery Wizard” on page 1525
“Creating the Intelligent Disaster Recovery nonbootable CD image only” on page 1516
Creating a bootable tape image
Type the path to files.
Specify the path to that image.
Note This option is available only for the local media server with a compliant bootable
tape device.
Use the IDR Preparation Wizard to create a bootable tape image, and then run an
overwrite backup job so that the image is written to the tape.
1514 Administrator’s Guide

Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About creating and updating recovery media
The IDR Preparation Wizard also enables you to update the *.dr file on diskette on a
regular basis, and to recreate the bootable tape image whenever hardware, SCSI drivers,
or tape drivers change on the computer. Prior to a disaster, test the bootable tape to
ensure that the computer can start from it. Follow the tape drive manufacturer’s
documentation for testing tape drive booting capability.
Before starting this procedure, please read the requirements listed in “Requirements for
running the IDR Preparation Wizard” on page 1510.
To create a bootable tape image
Note A bootable tape drive and its driver must be detected by the Intelligent Disaster
Recovery Preparation Wizard before the option to create a bootable tape image is
displayed.
1. Click Tools menu, click Wizards> Intelligent Disaster Recovery Preparation
Wizard.
By default, the IDR Preparation Wizard uses this computer to prepare the bootable
tape image. If this computer does not have the IDR option installed locally, select
another media server on which the IDR option is installed to create the boot image.
2. Do one of the following:
To use this computer to create the
bootable tape image
To use another computer to create the
bootable tape image
3. Under Create, select Bootable Tape Image for use with bootable tape devices, and
then click Next.
4. Read the Starting Tape Image Creation screen, and then click Next.
5. Type a path to store the bootable image until you perform a full backup, or click
Browse to navigate to a storage location.
6. Click Next.
On the Welcome screen, click Next.
Click Choose a media server that has the IDR
option installed, and see “Preparing IDR media by
using other media servers” on page 1520 for details.
7. Type a path to the location of the Windows operating system files, or click Browse to
navigate to the location.
1515

About creating and updating recovery media
8. Click Next.
9. When the bootable tape image has completed, click Next.
10. To view the computer’s hard disk configuration, click View Disk Configuration.
11. Click Finish.
12. Run an overwrite backup job so that the bootable image is written to the tape.
Related Topics:
“Updating bootable media” on page 1517
“About recovering a computer and using the Disaster Recovery Wizard” on page 1525
Creating the Intelligent Disaster Recovery nonbootable CD image
only
You can create a non-bootable disaster recovery CD image to complete the disaster
recovery media set if the computer being protected has a bootable tape or CD image
already created, or if the boot image has just been updated. The nonbootable CD image,
named nonbootable_idrcd.iso, includes the necessary drivers, the Disaster Recovery
Wizard, and the computer-specific *.dr file.
Note You must burn the nonbootable CD image to a CD as a disc image using third-party
software. Do not burn the CD image as a file.
To create an Intelligent Disaster Recovery nonbootable CD image only
1. On the Tools menu, click Wizards> Intelligent Disaster Recovery Preparation
Wizard.
By default, the IDR Preparation Wizard uses this computer to create the nonbootable
CD image. If this computer does not have the IDR option installed locally, select
another media server on which the IDR option is installed to create the nonbootable
CD image.
2. Do one of the following:
To use this computer to create the
nonbootable CD image
On the Welcome screen, click Next.
1516 Administrator’s Guide

To use another computer to create the
Intelligent Disaster Recovery
nonbootable CD image
Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About creating and updating recovery media
3. Under Create, click Nonbootable disaster recovery CD Image and then click Next.
4. On the Starting nonbootable CD Image Creation screen, click Next.
5. Type a path to a storage location for the nonbootable CD image, or click Browse to
navigate to a storage location.
6. Click Next.
The wizard begins creating the nonbootable image.
7. When the nonbootable CD image is complete, click Next.
8. Click Finish.
9. Use a third-party CD burning software tool to burn the nonbootable CD image to a
CD as a CD disk image. Do not burn the CD image as a file.
10. Label the nonbootable disaster recovery CD image appropriately and then store it
with your bootable IDR CD.
Related Topics:
“Backing up data” on page 345
Updating bootable media
If the media server hardware configuration changes, run the IDR Preparation Wizard and
create a new bootable image.
Updating a bootable CD image
Click Choose a media server that has the IDR
option installed, and see “Preparing IDR media by
using other media servers” on page 1520 for details.
If you initially created a bootable image on CD and then you change the media server’s
hardware, you must create a new bootable CD image by running another full backup of
the protected computer. After backing up the media server, run the IDR Preparation
Wizard again to create a new bootable CD image. For more information, see “Creating a
bootable CD image” on page 1512.
1517

About creating and updating recovery media
Updating a bootable tape image
To update a bootable tape image, use the following procedure.
Note A bootable tape drive and its driver must be detected by the Intelligent Disaster
Recovery Preparation Wizard before the option to create a bootable tape image is
displayed.
To update the bootable tape image
1. On the Tools menu, click Wizards> Intelligent Disaster Recovery Preparation
Wizard.
By default, the IDR Preparation Wizard uses this computer to update the bootable
tape image. If this computer does not have the IDR option installed locally, select
another media server on which the IDR option is installed to update the boot image.
2. Do one of the following:
To use this computer to
update the bootable tape
image
To use another computer
to update the bootable
tape image
On the Welcome screen, click Next.
The Create IDR Boot Media screen appears.
Click Choose a media server that has the IDR option installed,
and see “Preparing IDR media by using other media servers” on
page 1520 for details.
3. Under Create, click Bootable Tape Image for use with bootable tape devices, and
then click Next.
The Starting Tape Image Creation screen appears.
If you have previously prepared a bootable image for tape, the Disaster Recovery
Image Found screen appears.
4. Click Delete the existing image to write the new bootable image to the bootable tape
when the first overwrite backup job runs.
5. Continue to follow the prompts until the wizard is complete.
6. When the bootable image is complete, run an overwrite backup job so that the image
is written to the tape.
1518 Administrator’s Guide

Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
Copying the disaster recovery files to a diskette
Related Topics:
“About recovering a computer and using the Disaster Recovery Wizard” on page 1525
“Backing up data” on page 345
Copying the disaster recovery files to a diskette
Symantec recommends that you copy the disaster recovery information *.dr files that are
created during the IDR process to a floppy diskette as a backup.
To copy the *.dr files, you must have a functioning floppy disk drive on the media server
where IDR is installed. If the media server does not have a floppy drive, you can
manually back up the disaster recovery files using any method you find suitable. For
example, you can burn the files to a CD using third party CD burning software or you can
copy them to networked computer. The *.dr files reside in the \Program
Files\Symantec\Backup Exec\IDR\Data directory, on the media server where IDR is
installed.
To copy the disaster recovery files to a diskette
1. Run a full backup of the target computer.
When running full backups for IDR preparation:
■ Make sure that the default shares on each hard disk volume (C$, D$, etc.) have
been backed up. The *.dr files are not created or updated if only individual
directories are backed up. Additionally:
■ For Windows 2000 and Windows XP, back up System State.
■ For Windows Server 2003, back up the Shadow Copy and System State
components.
■ If the server is also the media server, back up the Backup Exec SQL instance.
■ Make sure that if utility partitions are present on the computer, they are selected
for backup. Utility partitions are usually small partitions installed on the hard
disk by OEM vendors, and contain system diagnostic and configuration utilities.
For more information on selecting utility partitions for backup, see “Utility
Partition” on page 318.
■ Do not include or exclude files from the backup using the Advanced File
Selection feature.
2. On the Tools menu, click Wizards> Intelligent Disaster Recovery Preparation
Wizard.
1519

Copying the disaster recovery files to a diskette
By default, the IDR Preparation Wizard uses this computer to copy the disaster
recovery information to a diskette. If this computer does not have the IDR option
installed on it, select another media server on which the IDR option is installed to
copy the disaster recovery files.
3. Do one of the following:
To use this computer to
copy the disaster
recovery information
files
To use another computer
to copy the disaster
recovery information
files
On the Welcome screen, click Next.
On the Welcome screen, click Choose a media server that has the
IDR option installed and see “Preparing IDR media by using other
media servers” on page 1520 for details.
4. Under Copy, click Disaster recovery information (.dr) file to a diskette, and then
click Next.
5. Select the computer or computers for which you want to update the disaster recovery
information, and then click Next.
6. Insert a floppy diskette for the computer you selected in step 5, and then click Next.
Use a different floppy disk for each computer selected.
When the Finish screen appears, the disaster recovery information files are copied.
7. Remove the diskette from the drive and store it with the computer’s disaster recovery
media.
Related Topics:
“Preparing IDR media by using other media servers” on page 1520
Preparing IDR media by using other media servers
When running the IDR Preparation Wizard, the local computer where the IDR option is
installed is used by default to create or update the disaster recovery media. However, if
the computer does not have the IDR option installed locally, you can select another
media server on which the IDR option is installed in order to create or update the media.
1520 Administrator’s Guide

Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About preparing to recover from a disaster by using IDR
To perform disaster recovery preparations on a different media server
1. On the Tools menu, click Wizards> Intelligent Disaster Recovery Preparation
Wizard.
2. On the IDR Preparation Wizard Welcome screen, click Choose a media server that
has the IDR option installed, and then click Next.
3. Click Browse to browse the network and select a media server that has the IDR
option installed.
4. Enter the credentials required to access the media server.
Media Server name The name of the remote media server that is selected to run
the restore job.
User name The user name with administrator rights to the remote
media server.
Password The password required for access.
Domain The domain in which the remote media server is a member.
If the media server is in a workgroup, leave this field blank.
5. Click Next to continue preparing disaster recover media.
The media server that you select is the computer that actually creates the media.
Related Topics:
“About recovering a computer and using the Disaster Recovery Wizard” on page 1525
“Performing an automated restore by using the Disaster Recovery wizard” on page 1526
“Performing a manual restore by using the Disaster Recovery Wizard” on page 1534
About preparing to recover from a disaster by using IDR
When a disaster occurs, you can use IDR to return the computer to its pre-disaster state.
Recovering a computer is a multi-step process that involves both manual and automatic
processes. To recover a computer, you must follow these steps in order:
1521

About preparing to recover from a disaster by using IDR
Caution Disconnect any storage area network (SAN) or cluster that is attached to the
computer being recovered; otherwise, the hard drives on those computers may
also be repartitioned and reformatted.
■ Plan any hardware changes to the computer to be recovered. For more information,
see “About changing hardware in the computer to be recovered” on page 1523.
■ Review additional requirements for IBM computers if the computer to be recovered is
an IBM computer. For more information, see “About using IDR to recover IBM
computers” on page 1524.
■ Start the computer using the bootable media created with the IDR Preparation
Wizard to start the recovery process.
■ Use the Disaster Recovery Wizard to restore the computer to its pre-disaster state
and restore the data files. For more information, see “About recovering a computer
and using the Disaster Recovery Wizard” on page 1525.
Note Boot managers, such as System Commander or the OS/2 Boot Manager, cannot be
restored with IDR. Boot managers are usually installed at a very low level that
Backup Exec cannot protect. For example, the OS/2 Boot Manager resides in its
own hard drive partition that Backup Exec cannot access. Because of the many
different boot managers available, you may not be able to restart the computer
after an IDR recovery, even though the operating system was restored. If this
happens, re-installing the boot manager should fix the problem.
Before recovering the computer, note the following:
■ There must be enough disks to restore all of the critical system disks. A disk is
considered critical if it is required for the computer to start successfully.
■ The storage capacity of each critical disk must be greater than or equal to the
corresponding original disk. Disk geometries, which may also be called disk
parameters, must be compatible.
■ Floppy and CD devices cannot be external PC-card drives. Because external PC-card
devices are not supported during the GUI-mode Windows Setup phase, they cannot
be used to access data, and recovery cannot be completed.
■ If a *.dr file is unavailable for the computer being restored, you can still use IDR to
recover the computer, but you must first manually restore the non-critical partition
information, including utility partitions.
■ IDR does not recover software mirrored volumes or any kind of software RAID with
the auto-partitioning feature. You must manually apply the mirror with the Disk
Manager. In addition, hardware RAID components must be set up before you perform
the disaster recovery.
1522 Administrator’s Guide

Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About preparing to recover from a disaster by using IDR
Related Topics:
“About changing hardware in the computer to be recovered” on page 1523
“About recovering a computer and using the Disaster Recovery Wizard” on page 1525
About changing hardware in the computer to be recovered
During the creation of the *.dr files, IDR creates a device driver database on the media
server running IDR. This database contains the drivers required for the various hard
drives and network interface cards installed in each of the computers. If you experience a
hard drive or network interface card failure in a particular computer and you replace
either of the failed components with the same type found in your other computers, IDR
automatically installs the correct device driver during the recovery.
You can also use IDR to recovery a computer that is no longer functioning. For example,
if the computer’s main system board fails, you can restore the computer’s data after you
replace the system board, even if the new board is a different model or contains multiple
processors.
If you plan to change the hardware in the computer being recovered, note the following:
■ Hard drives. Any hard drives you replace should be the same size or larger than the
original drives, and the number of hard drives you replace must equal or exceed the
number of hard drives that were in the original computer configuration; otherwise
repartitioning problems may occur.
■ System boards. After you replace a faulty system board and after you use IDR to
recover the computer, you must use the system board manufacturer’s driver CD to
re-install additional functionality such as onboard sound and video.
■ Network interface cards. If you change the network interface card in the computer
you are recovering, you must install the necessary network drivers. Without the
network drivers, you cannot access the network if you want to use a remote media
server or remote backup-to-disk folders to recover the computer. After you complete
the recovery, you must install new network interface card drivers that match the
network card presently in the computer. The backup sets that you use to recover the
computer contains the original network interface card drivers for the faulty network
interface card that you replaced.
Related Topics:
“About recovering a computer and using the Disaster Recovery Wizard” on page 1525
“About encrypted backup sets and the Disaster Recovery Wizard” on page 1525
“Performing a manual restore by using the Disaster Recovery Wizard” on page 1534
1523

About preparing to recover from a disaster by using IDR
About using IDR to recover IBM computers
To recover an IBM computer equipped with an IBM ServeRAID card, perform the
following additional procedures before starting the IDR process:
■ Install and configure the IBM ServeRAID controller card and ServeRAID software so
that a boot partition will be visible to the Windows operating system.
■ Start the server using the IBM server’s ServeRAID Configuration and Management
CD in the CD-ROM drive prior to using the IDR bootable media. This will start IBM
ServeRAID utilities configuration and installation process to view and update the
current BIOS and firmware levels.
Refer to the IBM ServeRAID documentation for complete installation instructions for
installing Windows on an IBM Server with the ServeRAID controller. Create and
initialize the ServeRAID disks in order for partitions to be visible to the Windows
operating system.
Related Topics:
“About recovering a computer and using the Disaster Recovery Wizard” on page 1525
1524 Administrator’s Guide

Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About recovering a computer and using the Disaster Recovery Wizard
About recovering a computer and using the Disaster Recovery
Wizard
To recover a computer with the Disaster Recovery Wizard, you must:
■ Start the computer by using the bootable tape or CD that was created with the IDR
Preparation Wizard.
■ Use Windows Setup to prepare the computer for recovery.
■ Use the Disaster Recovery Wizard to restore the computer to an operational state
and to restore the computer’s data from the last backup set.
However, to fully automate the recovery, you must have the current *.dr file for the
computer that you want to restore. If a *.dr file is unavailable or if the *.dr file is not
current, you can still use IDR to manually recover the computer. For more information,
see “Performing a manual restore by using the Disaster Recovery Wizard” on page 1534.
When you use the Disaster Recovery Wizard to perform a recovery, the Disaster Recovery
Wizard lets you access the media device that is required for restore from three sources.
You can:
■ Use locally-attached media devices at the computer being that you want to recover.
■ Use remote backup-to-disk folders that reside on remote computers.
■ Run restore jobs from remote media servers.
To restore data by using the Disaster Recovery Wizard, the following items are required:
■ The media set that contains the full backup of the target computer being restored.
■ For recovery on a local computer, a storage device must be connected to the
computer being that you want to recover.
■ If you are using a bootable CD, a media server that can restore the backup sets to the
target computer must be connected on the network.
Related Topics:
“Performing an automated restore by using the Disaster Recovery wizard” on page 1526
“Performing a manual restore by using the Disaster Recovery Wizard” on page 1534
About encrypted backup sets and the Disaster Recovery Wizard
The Disaster Recovery Wizard supports the recovery of computers with previously
encrypted backup sets.
1525

About recovering a computer and using the Disaster Recovery Wizard
When you use the Disaster Recovery Wizard’s automated recovery option to recover a
local media server, the wizard prompts you for the pass phrase of each encrypted backup
set that is required to complete the restore job.
When you use a remote media server to recover a computer with encrypted backup sets,
one of the following occurs:
If the backup set was created
on the remote media server
If the backup set was not
created on the remote media
server
When you use the Disaster Recovery Wizard’s manual recovery option, the wizard
prompts you for the pass phrase of each encrypted backup set that is required to
complete the recovery. For more information, see “Encryption keys” in the Backup Exec
for Windows Servers Administrator’s Guide.
Performing an automated restore by using the Disaster Recovery
wizard
To perform an automated restore by using the Disaster Recovery Wizard
1. Place the bootable IDR CD in the CD drive of the computer to be recovered and then
start the computer.
2. After reading the IDR boot screen, press Enter.
The Disaster Recovery Wizard automatically retrieves the
encryption keys.
The Disaster Recovery Wizard prompts you to enter the pass
phrase.
3. On the initial Symantec Intelligent Disaster Recovery screen, click Start> Intelligent
Disaster Recovery.
If the Disaster Recovery Wizard fails to run and brings you back to the initial
Intelligent Disaster Recovery screen, click Start> View Log File to view a debug log
file. Use this log file when you contact Technical Support.
4. Click Automated Recovery, and then click Next.
If SCSI or RAID controller drivers are required, the drivers are automatically
installed if the Disaster Recovery Wizard finds them in its driver database. If the
SCSI or RAID drivers are not found, click Have Disk to install the required drivers,
and then click OK.
1526 Administrator’s Guide

Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About recovering a computer and using the Disaster Recovery Wizard
5. Select the *.dr file for the computer that you want to recover, and then click Next.
Each *.dr file is labeled using the name of the computer from which it was created. It
also shows the date and time it was created. Make sure you select the correct *.dr file.
If the Disaster Recovery Wizard does not detect a valid IDR license key, you must
enter a valid license key to continue.
6. If the *.dr file does not appear, copy the *.dr file from the alternate location to a
diskette.
7. Insert the diskette into drive A, and then click Browse to find the *.dr file.
8. If the *.dr file resides on a network drive, click Install Network to install the network
drivers for the computer that you want to recover.
9. After installing the network drivers, click Browse to find the file. For more
information, see “Installing network drivers” on page 1533.
If the evaluation period has expired, enter a valid license key after you select a *.dr
file.
The Disaster Recovery Wizard begins restoring the original hard disk layout.
10. When the Restore Hard Disk Layout screen appears, click Next.
11. Do one of the following:
To use the original
configuration from the
*.dr file
To make additional
changes to the partition
information
If a *.dr file does not exist
for the computer being
recovered
Click Next.
Do the following:
◆ Click Run Disk Management.
◆ Modify the disk layout.
◆ Click Next.
For more information on these programs and fault tolerant
configurations, please refer to your Windows documentation, and
to “About altering hard drive partition sizes” on page 1533.
Do the following:
◆ Click Run Disk Management.
◆ Modify the partition layout.
◆ Click Next.
1527

About recovering a computer and using the Disaster Recovery Wizard
12. Select one of the following methods to access the storage device.
Use locally attached
media device
Install networking, and
then restore from remote
backup-to-disk folders
Install networking and
then restore from a
remote media server
Related Topics:
“Restoring from a locally-attached media device” on page 1528
“Restoring from remote backup-to-disk folders” on page 1530
“Restoring from a remote media server” on page 1531
Restoring from a locally-attached media device
To restore from a locally-attached media device
1. From the Select Restore Method screen, select Use locally attached media device
and then click Next.
2. After media devices are detected, click Next.
Depending on the level of assistance selected, all backup sets may be automatically
restored, or you can select individual backup sets to restore.
After the restore is complete, you can provide additional media to restore.
If a *.dr file does not exist, or if there are no catalog entries in the *.dr file, then
perform a manual restore and select I will provide my own media, and then go to
“Performing a manual restore by using the Disaster Recovery Wizard” on page 1534.
3. Do one of the following:
◆ Select this option if you have locally-connected backup media
such as tape drives, autoloaders, or backup-to-disk folders. If
you use bootable tape, you must use this option.
◆ Go to “Restoring from a locally-attached media device” on
page 1528.
◆ Select this option if your backup-to-disk folders are located on
remote computers.
◆ Go to “Restoring from remote backup-to-disk folders” on
page 1530.
◆ Select this option if you want to submit the restore jobs from
remote media servers.
◆ Go to “Restoring from a remote media server” on page 1531.
■ If you are restoring from a stand-alone tape drive, insert the correct media and
then click Next.
1528 Administrator’s Guide

Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About recovering a computer and using the Disaster Recovery Wizard
■ If you are restoring from a backup-to-disk folder, click Next.
If you use a robotic library to recover your computer, the first drive in the robotic
library is used for the restore.
4. Click Next.
On the Restore Data screen, all of the backup sets that you need to fully restore the
computer are checked by default.
5. Click Next.
6. On the Insert Media into Restore Device screen, select the backup-to-disk folder or
drive that contains the required media that you want to restore.
7. Click Next.
8. When the automated restore process finishes, click the appropriate response.
Yes The Disaster Recovery Wizard prompts you to select another media set
from which to continue the restore process.
No The Disaster Recovery Wizard updates the hard disk drivers and then
finishes the recovery process.
9. On the You have completed the Disaster Recovery Wizard screen, you can run the
following:
Run CMD.exe The Disaster Recovery Wizard lets you open a command window
that you can use to make further modifications to your computer.
Edit Boot.ini The Disaster Recovery Wizard lets you edit the boot.ini file by
using the Windows Notepad application to modify the boot.ini file
on the root of the system partition.
Messages Click the Messages button to review messages that were generated
by the Disaster Recovery Wizard during the recovery process.
10. Click Finish. Before the computer restarts, remove the CD.
As the computer restarts, a Symantec screen momentarily appears while the
Disaster Recovery Wizard makes final recovery modifications. After the
modifications are finished, the computer restarts again and the recovery process is
complete.
1529

About recovering a computer and using the Disaster Recovery Wizard
Related Topics:
“About changing hardware in the computer to be recovered” on page 1523
Restoring from remote backup-to-disk folders
To restore from remote backup-to-disk folders
1. From the Select Restore Method screen, click Install networking and then restore
from remote backup-to-disk folders.
2. Click Next.
The Disaster Recovery Wizard attempts to detect and install the correct network
drivers.
3. After networking is installed, click Next.
The Disaster Recovery Wizard attempts to detect the remote backup-to-disk folders.
After it finds them, a Connect to screen appears, prompting you
for access credentials to the remote computer where the backup-to-disk folders
reside.
4. Enter the credentials that are required to access the remote computer.
5. Click Next.
The Detecting Media Devices screen appears, showing the backup-to-disk folders.
6. Click Next.
On the Restore Data screen, all of the backup sets that you need to fully restore the
computer are checked by default.
7. Click Next.
8. On the Insert Media into Restore Device screen, select the backup-to-disk folder that
contains the required media that you want to restore.
9. Click Next.
10. When the automated restore process finishes, click the appropriate response.
Yes The Disaster Recovery Wizard prompts you to select another media set
from which to continue the restore process.
1530 Administrator’s Guide

Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About recovering a computer and using the Disaster Recovery Wizard
No The Disaster Recovery Wizard updates the hard disk drivers and then
finishes the recovery process.
11. On the You have completed the Disaster Recovery Wizard screen, you can run the
following:
Run CMD.exe The Disaster Recovery Wizard lets you open a command window
that you can use to make further modifications to your computer.
Edit Boot.ini The Disaster Recovery Wizard lets you edit the boot.ini file using
the Windows Notepad application to modify the boot.ini file on
the root of the system partition.
Messages Click the Messages button to review messages generated by the
Disaster Recovery Wizard during the recovery process.
12. Click Finish. Before the computer restarts, remove the CD.
As the computer restarts, a Symantec screen momentarily appears while the
Disaster Recovery Wizard makes final recovery modifications. After the
modifications are finished, the computer restarts again and the recovery process is
complete.
Restoring from a remote media server
To restore from a remote media server
1. From the Select Restore Method screen, select Install networking and then restore
from a remote media server.
2. Click Next.
The Disaster Recovery Wizard attempts to detect and install the correct network
drivers.
3. After networking is installed, click Next.
4. On the Connect to Media Server screen, enter the credentials that are required to
access the media server.
Server Name The name of the remote media server that you selected to run the
restore job.
1531

About recovering a computer and using the Disaster Recovery Wizard
Domain The domain in which the remote media server is a member.
User Name The user name that has administrator rights to the remote media
server.
Password The password that is required for access.
5. Click Next.
On the Restore Data screen, all backup sets that are required to fully restore the
computer are checked by default.
6. Click Next.
7. When the automated restore process finishes, click the appropriate response.
Yes The Disaster Recovery Wizard prompts you to select another media set
from which to continue the restore process.
No The Disaster Recovery Wizard updates the hard disk drivers and then
finishes the recovery process.
8. On the You have completed the Disaster Recovery Wizard screen, you can run the
following:
Run CMD.exe The Disaster Recovery Wizard lets you open a command window
that you can use to make further modifications to your computer.
Edit Boot.ini The Disaster Recovery Wizard lets you edit the boot.ini file using
the Windows Notepad application to modify the boot.ini file on
the root of the system partition.
Messages Click the Messages button to review messages generated by the
Disaster Recovery Wizard during the recovery process.
9. Click Finish. Before the computer restarts, remove the CD.
As the computer restarts, a Symantec screen momentarily appears while the
Disaster Recovery Wizard makes final recovery modifications. After the
modifications are finished, the computer restarts again and the recovery process is
complete.
1532 Administrator’s Guide

Installing network drivers
Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About recovering a computer and using the Disaster Recovery Wizard
You can install network drivers from any screen in the Disaster Recovery Wizard where
the Install Network or Configure Network buttons appear.
To install network drivers
1. Click Install Network.
2. On the Network Configuration screen, click Next after the Disaster Recovery Wizard
detects and binds each detected network adapter.
By default, each network adapter is assigned IP addresses from the default DHCP
server. To assign a static IP address for each detected network adapter, select a
network adapter and then click Configure.
Related Topics:
“Performing an automated restore by using the Disaster Recovery wizard” on page 1526
“Performing a manual restore by using the Disaster Recovery Wizard” on page 1534
About altering hard drive partition sizes
When you recover a Windows 2000 computer, IDR restores the hard drive partitions to
the same sizes they were before the disaster. There may be unused and unallocated
space. If the hard drive in the target computer is larger than the hard drive that was in
place before the disaster occurred, run the Windows Disk Management program (within
the IDR Recovery Wizard) to alter the partition sizes to reflect the larger hard drive size.
If you did not select the option Let IDR automatically partition the boot and system drive
during restore when you recover a Windows 2000 computer, you must specify hard drive
partitioning information during setup.
Following is an example of why the hard drive partitions should be resized:
If the pre-disaster computer hardware contained a 4 GB hard drive with two 2 GB
partitions, and you replaced it with a 9 GB model, IDR (using the *.dr file) rebuilds the
hard disk partition table by using the partition information that is found on the original
4 GB hard drive. As a result, only 4 GB of space is allocated on the new 9 GB hard drive,
with a partition map that consists of two 2 GB partitions.
Use the Disk Management program to repartition the hard drive to include the additional
space.
Related Topics:
“About changing hardware in the computer to be recovered” on page 1523
1533

About recovering a computer and using the Disaster Recovery Wizard
Performing a manual restore by using the Disaster Recovery
Wizard
If a *.dr file is missing, you can still recover the computer by initiating a manual restore
using the Disaster Recovery Wizard. The Disaster Recovery Wizard identifies individual
backup sets by reading the backup media, so you can select the backup sets that you want
to restore.
Caution If the media that you want to restore contains both Full backup sets and
Incremental or Differential backup sets, restore the Full backup sets first.
To perform a manual restore
If you are restoring Windows 2000 computers that have utility partitions, first
recreate the utility partitions using the OEM-supplied media.
1. Place the bootable IDR CD in the CD drive of the computer to be recovered and then
start the computer.
2. After you read the IDR boot screen, press Enter.
3. On the initial Symantec Intelligent Disaster Recovery screen, click Start >
Intelligent Disaster Recovery.
If the Disaster Recovery Wizard fails to run and brings you back to the initial
Intelligent Disaster Recovery screen, click Start > View Log File to view a debug log
file. Use this log file when you contact Technical Support.
4. Select Manual Recovery, and then click Next.
If SCSI or RAID controller drivers are required, the drivers are automatically
installed if the Disaster Recovery Wizard finds them in its driver database. If the
SCSI or RAID drivers are not found, click the Have Disk button to install the required
drivers, and then click OK.
5. On the Modify Hard Disk Layout screen, click Run Disk Management.
6. Recreate the hard disk partition layout to match the computer’s original partition
layout.
7. After you create the hard disk partition layout, click Next.
1534 Administrator’s Guide

Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About recovering a computer and using the Disaster Recovery Wizard
8. Select one of the following methods to access the storage device.
Use locally attached
media device
Install networking, and
then restore from remote
backup-to-disk folders
Install networking and
then restore from a
remote media server
9. Select the tape drive where the restore media resides.
The Found a Backup Set dialog box appears, showing you the first backup set found
on the media.
10. To restore to a location other than the one that appears, click Change, and then
select a location where you want to restore the data. Do not use drive C for the
alternate location.
11. Click one of the following:
◆ Select this option if you have locally-connected backup media
such as tape drives, autoloaders, or backup-to-disk folders. If
you use bootable tape, you must use this option.
◆ Go to “Restoring from a locally-attached media device” on
page 1528.
◆ Select this option if your backup-to-disk folders are located on
remote computers.
◆ Go to “Restoring from remote backup-to-disk folders” on
page 1530.
◆ Select this option if you want to submit the restore jobs from
remote media servers.
◆ Go to “Restoring from a remote media server” on page 1531.
Click Restore Set To restore the backup set that appears in Media Information and
Set Information. IDR restores the data to the selected partition.
When the restore is complete, the Found Backup Set dialog box
reappears and shows the next backup set that is found on the
media. If there are no more backup sets, the Select Tape Drive
screen appears.
To restore another backup set, click Restore Set again to restore
the next backup set. Repeat this step for each backup set found on
the media.
Click Skip Set To skip the restoration of this backup set and search the media for
another backup set from which to restore.
Click Skip Media To eject the media and replace it with different media.
1535

About recovering a computer and using the Disaster Recovery Wizard
12. After you restore the last backup set, click Finish to end the recovery process and
exit the Disaster Recovery Wizard.
Related Topics:
“About changing hardware in the computer to be recovered” on page 1523
About Microsoft SQL Server recovery notes
The Backup Exec Agent for Microsoft SQL Server option must be installed on the media
server in order to perform a complete SQL Server database recovery.
After using Intelligent Disaster Recovery to recover the Windows server, IDR
automatically replaces the damaged master and model databases with copies of the
master and model databases. After SQL is restarted and the latest master database
backup and all other system databases are restored, you must still restore all user
databases after completing the IDR Recovery.
Caution For the Intelligent Disaster Recovery Option to work with SQL 2000, copies are
made of the master and model databases. Copies are made only after running
non-AOFO (Advanced Open File Option) backups of the master and model
databases. If you are using AOFO for SQL backups, you must make at least one
backup of the master and model databases without using AOFO.
If you upgrade SQL 2000, run another non-AOFO backup of the master and
model databases.
Related Topics:
“Using snapshot technology with the SQL Agent” on page 1344
“Symantec Backup Exec Advanced Disk-based Backup Option” on page 865
About Microsoft Exchange recovery notes
The Backup Exec Agent for Microsoft Exchange Server option must be installed on the
media server in order to perform a complete Exchange Server database recovery.
After you use Intelligent Disaster Recovery to recover the Windows server, use Backup
Exec to restore the Exchange Server databases from the most recent Exchange Server
database backups.
1536 Administrator’s Guide

Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
About recovering a computer and using the Disaster Recovery Wizard
About SharePoint Portal Server recovery notes
After you use Intelligent Disaster Recovery to recover a Windows server that has
SharePoint Portal Server 2001 installed (after restarting the system), the SharePoint
Portal Server software is installed but is not functional; you must remove SharePoint
Portal Server 2001 and reinstall it before the SharePoint data can be restored.
About Citrix Metaframe recovery notes
Backup Exec supports IDR of Citrix Metraframe 1.8, XPa, XPe, and XP computers with the
following exceptions:
■ IDR of a remote computer is not supported if Citrix is installed on the media server
and drive C on the media server is remapped.
■ If other drives on a Citrix computer were remapped prior to IDR, the drives must also
be remapped during the IDR process before any files are restored.
■ If you selected Automated Recovery during the IDR process and selected a *.dr
file, Backup Exec automatically remaps the drives.
■ If you selected Automated Recovery or Manual Recovery during the IDR process,
but did not select a *.dr file, you must manually remap the drives.
About using IDR with the Central Admin Server Option
If you have purchased and installed the Central Admin Server Option (CASO), you can
perform IDR of the managed media servers in a CASO environment. To prepare recovery
media for the managed media servers, you must run the IDR Preparation Wizard on the
central administration server. The *.dr files are stored on the central administration
server. During IDR recovery of a managed media server, all restore jobs are submitted
from the central administration server. The central administration server will then send
the restore jobs to the appropriate managed media server.
Note You cannot select a managed media server node as a valid media server for IDR
preparation if the managed media server node is active in a CAS environment. To
create the IDR boot media, you must select the CAS server to which the managed
media server is attached.
About using IDR with Veritas Storage Foundation for Windows
If you use VERITAS Storage Foundation for Windows on Windows 2003, IDR can restore
the dynamic volumes. During backup, IDR gathers the applications and components
necessary to restore the dynamic volumes and adds them to the recovery media. During
1537

Best Practices for IDR
recovery, the gathered applications are run as part of the Windows Automated System
Recovery (ASR) process in order to bring back the dynamic volumes. After the dynamic
volumes are recovered, the data recovery on the volumes proceeds as usual.
Best Practices for IDR
The following table presents best practices when using IDR
.
Best practices for IDR
Item Description
Remote IDR To perform disaster recovery on a remote computer, you
must purchase the Remote Agent separately, and it must
be running on the remote computer.
Creating Bootable Media ◆ Always verify that the *.dr file was created in the
alternate data path that you selected.
◆ When creating bootable tape, run the IDR Preparation
Wizard and create the bootable image before you run a
full backup.
◆ When creating a bootable CD, run a full backup before
you create the bootable media.
◆ If the backup media resides on another Backup Exec
media server, select the option Choose a media server
that has the IDR option installed on the first IDR
Preparation Wizard screen.
◆ For local IDR, backup-to-disk folders must be on a
drive or drives that can be accessed for recovery.
Disaster Recovery ◆ Windows 2000/2003/XP must have at least 2 GB of
hard drive space available.
◆ The new partition layout must be the same size or
larger than the original.
◆ Have the latest RAID, SCSI, or NIC (if remote) drivers
available on disks.
1538 Administrator’s Guide

Appendix
Symantec Backup Exec
Library Expansion Option
S
The Symantec Backup Exec for Windows Servers Library Expansion Option enables you
to use a robotic library with Backup Exec, which provides convenient, automated support
for large capacity network environments. Support for a single robotic library drive is
included with Backup Exec for Windows Servers. To obtain license keys for additional
robotic library drives, you must purchase the Symantec Backup Exec for Windows
Servers Library Expansion Option (LEO). This option allows concurrent processing on
multi-drive robotic libraries.
Related Topics:
“About robotic libraries in Backup Exec” on page 206
“Configuring multi-drive robotic libraries” on page 1540
1539

Setting up robotic library hardware
Before installing Backup Exec, make sure that the robotic library hardware is configured
properly.
■ Make sure the robotic arm is set to “Random” mode. Refer to your robotic library
documentation for more information.
■ If you have a multi-LUN robotic library, make sure that the controller card is set to
support multiple LUNs (if supported).
■ If you have a multi-LUN robotic library, make sure that the target LUN for the tape
drive is lower than the target LUN for the changer.
■ The SCSI ID of the robotic arm must precede the SCSI ID of the drives in the robotic
library. You should not use 0 or 1 because these SCSI IDs are typically reserved for
boot devices.
■ Make sure the inquiry strings match for the drive and the robotic library.
For a list of supported devices, see:
http://support.veritas.com/menu_ddProduct_BEWNT_view_CL.htm
Configuring multi-drive robotic libraries
Configuring Backup Exec to work with multiple drive robotic libraries is accomplished by
making associations between the robotic library’s media drives, robotic arm, and Backup
Exec. Backup Exec supports serialized drives; manual configuration of serialized drives
is not required.
Each drive in the robotic library and the robotic arm requires its own SCSI ID. Multi-drive
robotic libraries require separate SCSI IDs for each device.
In addition to separate SCSI IDs, each drive in a multi-drive robotic library has unique
drive element addresses. You must know each drive’s element address to properly
configure the robotic library to work with Backup Exec (refer to your robotic library
documentation to determine the drive element address for each storage device).
1540 Administrator’s Guide

After determining the drive considered to be the first drive in the robotic library (Storage
Device 0), you will need to arrange the SCSI IDs to match the sequence of the drive
element addresses. For example, if your robotic library has two drives, the drive with the
lowest drive element address should be assigned the lower SCSI ID.
Example configuration for a multi-drive robotic library
Data Transfer Element
(Storage Devices)
SCSI ID Drive Element Address
Robotic Arm 4 N/A
Storage Device 0 5 00008000
Storage Device 1 6 00008001
Related Topics:
“Bar code rules in mixed media libraries” on page 281
Appendix S, Symantec Backup Exec Library Expansion Option 1541

Installing the Library Expansion Option
Installing the Library Expansion Option
Backup Exec’s optional Library Expansion Option installation requires:
■ Purchasing a Library Expansion Option license key for each additional robotic
library drive.
Note Support for a single robotic library drive is included with Backup Exec for Windows
Servers.
■ Installing the necessary Library Expansion Option files.
■ Configuring the robotic arm and drives.
Backup Exec’s Library Expansion Option installation copies all necessary robotic
library-related files including the software needed to control the robotic arm and storage
devices.
To install the Library Expansion Option, follow the installation steps described in
“Installing Backup Exec options to the local computer” on page 85.
Starting Backup Exec after installing the Library Expansion
Option
You can view configuration information for the storage devices in the Device
Configuration Wizard. You can access the wizard using one of the following methods:
■ When you start Backup Exec for the first time, the Getting Started with Backup Exec
page appears. Click Configure Devices to configure the robotic library drives.
■ On the Tools menu, click Wizards > Device Configuration Wizard.
■ On the Help menu, click Backup Exec Assistant. In Device and Media Management,
click Configure Devices to configure the robotic library drives.
The Device Configuration Wizard displays dialog boxes to guide you through setting up
your robotic library. The dialog boxes include the following:
■ The Review Backup Devices dialog box shows all of the devices that are attached to
the media server. If a drive attached to your media server does not appear in the list,
click Next.
■ The Create and Configure Backup Devices dialog box lets you configure your robotic
library.
1542 Administrator’s Guide

Appendix S, Symantec Backup Exec Library Expansion Option
Starting Backup Exec after installing the Library Expansion Option
The Configure Library Drives dialog box shows how the devices appear to Backup Exec.
Make sure that each device in the robotic library is properly associated with the robotic
library.
Make sure that the drives in the robotic library appear in the Device Configuration
Wizard under the robotic library in the order matching their drive element address. The
drive with the lowest drive element address should appear at the top of the list.
If a robotic library storage device appears in the list as a stand-alone device, make sure
the SCSI addresses of the robotic library and the storage device are configured properly.
Note During startup, if the storage devices in the robotic library contain media, Backup
Exec attempts to return the media to its original magazine slot. If the media
cannot be returned to the slot, you are prompted to eject the media from the
storage device.
Related Topics:
“Setting up robotic library hardware” on page 1540
“Using the Getting Started with Backup Exec page” on page 132
“Viewing a device’s configuration properties” on page 198
1543

Starting Backup Exec after installing the Library Expansion Option
Viewing robotic libraries
The following is an example of how robotic libraries are depicted when Devices is
selected from the navigation bar:
Robotic libraries in the Devices view
Robotic library
Robotic library drive
All slots
Individual slots
Depending upon your robotic library configuration, the first slot could be numbered 1 or
0. If your robotic library uses a zero-based slot configuration you can reassign how the
slots are displayed in Backup Exec, by right clicking the Robotic Library in the left pane,
selecting Properties, and then selecting Configuration. Depending on whether your
robotic library begins slot numbering at 0 or 1, specify the appropriate number in the
Slot Base option.
1544 Administrator’s Guide

Robotic library properties for Library|Configuration tab
Appendix S, Symantec Backup Exec Library Expansion Option
Starting Backup Exec after installing the Library Expansion Option
After completing the configuration of your robotic library, perform an Inventory
operation to update the Backup Exec media database.
Related Topics:
“Inventorying media” on page 238
1545

Starting Backup Exec after installing the Library Expansion Option
1546 Administrator’s Guide

Appendix
Symantec Backup Exec SAN
Shared Storage Option
T
The Symantec Backup Exec for Windows Servers SAN Shared Storage Option enables
multiple media servers to share secondary storage devices, such as robotic libraries, in a
SAN. The secondary storage devices are not directly connected to a single server by SCSI,
but are connected to a Fibre Channel Switched Fabric (FC-SW) or iSCSI.
To allow for sharing of storage devices and media between multiple media servers, a
shared Advanced Device and Media Management (ADAMM) database resides on one
media server called the database server or primary server. All media servers on the SAN
connect to this database to obtain a single, unified view of all shared devices and media.
Backup Exec uses this shared database to arbitrate all device and media requests with
comprehensive overwrite protection policies to prevent accidental media overwrites. To
resolve potential access conflicts between multiple media servers, Backup Exec
“reserves” robotic arms and tape devices while operations are being performed.
Media catalogs are shared between media servers, so restore operations can be
performed using any media servers that share catalogs. If the media must be moved from
one device to another on the SAN, the media does not have to be cataloged again. In a
shared storage environment, secondary storage devices also can be attached to the local
SCSI, SATA, SAS, USB, or ATAPI buses of any media server. However, these local
devices, disk or tape drives connected to a server, are only available to the server to
which they are attached. Storage devices used with the SAN Shared Storage Option must
have a vendor-assigned serial number.
You can use any media server to change the names of the robotic libraries and drives to
names that are more descriptive of your operations.
If you have multiple SANs, it is recommended that you treat each SAN independently,
with each SAN having its own Backup Exec database server for the shared ADAMM
database and catalogs for that loop. Using a single Backup Exec database server for more
than one SAN increases the number of single-point failures that can affect the system.
1547

Requirements for the SAN Shared Storage Option
Job completion statistics or errors can be viewed through any administration console
attached to the server that ran the job.
RELATED TOPICS:
“Sharing media” on page 1561
“Scheduling and viewing jobs in a SAN SSO environment” on page 1560
“Requirements for the SAN Shared Storage Option” on page 1548
Requirements for the SAN Shared Storage Option
The following are the minimum system requirements for running this release of the SAN
Shared Storage Option:
■ Windows 2000 or Windows Server 2003 must be installed.
■ Physical Memory Available, as shown in the Windows Task Manager, plus the File
Cache should exceed 256 MB.
■ The SAN Shared Storage Option must be locally installed at each server that will be
sharing secondary storage devices.
■ The devices in your SAN must be on the supported device list at
http://support.veritas.com/menu_ddProduct_BEWNT_view_CL.htm
■ All hardware drivers must be up to date and started. See
http://support.veritas.com/rd/bews-drivers.htm
■ The primary server must have enough space for the catalogs of all the servers in the
SAN.
For a fibre channel-connected installation, note the following additional requirements:
■ A fibre channel host adapter and its device drivers must be installed and connected
to the SAN.
■ A hub or switch must be connected to all the fibre to SCSI bridges or to the fibre
libraries on the SAN.
■ All the robotic libraries must be connected to the SCSI bridges or to the fibre
switches/hubs.
■ The hub or switch must be powered up before the bridges or fibre channel libraries.
■ All robotic libraries must be powered up before the bridges.
■ The bridges must be powered up before Windows loads the fibre channel driver
(usually during the boot phase).
1548 Administrator’s Guide

Appendix T, Symantec Backup Exec SAN Shared Storage Option
Installing the SAN Shared Storage Option
Note If the SAN Shared Storage Option is installed on a media server, Backup Exec
disables all fibre channel-connected devices in Removable Storage. You cannot
re-enable the devices in Removable Storage until the SAN Shared Storage Option
and Symantec Device Drivers are uninstalled.
Related Topics:
“Installing the SAN Shared Storage Option” on page 1549
Installing the SAN Shared Storage Option
You must install the Backup Exec SAN Shared Storage Option on the shared database
server before installing Backup Exec SAN Shared Storage Option on other servers. The
server containing the shared database must be running before other media servers can
be installed properly.
Tip For best performance, install the shared ADAMM and catalog databases on the
fastest server on the SAN that is not heavily loaded with non-Backup Exec tasks.
You can install the SAN Shared Storage Option while installing Backup Exec by following
the procedures described in “Installing Backup Exec to a local computer” on page 81. If
you have already installed Backup Exec, follow the procedures described in “Installing
Backup Exec options to the local computer” on page 85. If installing to the database
server, select Primary. You can install the Backup Exec device drivers as part of the
Backup Exec installation.
If the SAN Shared Storage Option has already been installed to the primary, or database,
server, and you are installing to a secondary server, select Secondary and enter the name
of the database server.
If you installed Backup Exec on the database server, reboot the database server before
loading Backup Exec on other servers. The server containing the shared database must
be running before other media servers can be installed properly.
The first time you run Backup Exec, the Getting Started with Backup Exec page appears.
The Getting Started with Backup Exec page provides a series of steps that you can follow
to configure environment settings in Backup Exec, including logon accounts, devices, and
media sets. You must complete the applicable sections of this wizard as it guides you in
preparing Backup Exec for operations. Setting the overwrite protection level is important
since the media is shared throughout the SAN.
Note When uninstalling Backup Exec, you must uninstall from the secondary servers
before uninstalling from the primary server. For more information about uninstall
procedures, see “Uninstalling Backup Exec” on page 124.
1549

Installing the SAN Shared Storage Option
Related Topics:
“Symantec Backup Exec Remote Agent for Windows Systems” on page 913
“Starting Backup Exec” on page 132
“Scheduling and viewing jobs in a SAN SSO environment” on page 1560
“Best practices for SAN SSO” on page 1569
1550 Administrator’s Guide

Appendix T, Symantec Backup Exec SAN Shared Storage Option
About devices in the shared storage environment
About devices in the shared storage environment
At startup, Backup Exec recognizes all local storage devices as well as the storage devices
on the SAN. If you do not see one or more of your attached storage devices or if the
shared storage devices do not appear when Devices is selected from the navigation bar,
on the Tools menu, click Wizards > Device Configuration Wizard. This wizard guides
you through installing the appropriate drivers for the storage hardware connected to
your system.
Note The SAN Shared Storage Option must be installed for Backup Exec to recognize
any devices connected to Fibre Channel Switched Fabric (FC-SW). FC-SW is a fibre
channel configuration in which the devices are connected in a network using a
fibre channel switch.
Storage devices are categorized as either robotic libraries or stand-alone drives. The
Library Expansion Option is required to support robotic libraries with multiple tape
drives (see “Symantec Backup Exec Library Expansion Option” on page 1539).
If you need to add a new device to the SAN after you install Backup Exec, follow your
storage network vendor’s instructions. After you add the new device, reboot the Backup
Exec database server to verify that the new device is recognized. You should reboot the
other media servers according to your storage network vendor’s instructions because
some vendors do not support booting multiple servers concurrently or booting any
server while active jobs are running.
Backup Exec’s device management feature provides the following functionality for the
secondary storage units on a SAN:
■ Device allocation. Jobs must first reserve the shared secondary backup devices
before they can be used. The job that gains a reservation on a drive keeps it reserved
while the drive is in use. The drive is released after a job completes, which allows
other jobs to compete for it.
■ Drive pools. You can assign the drives to drive pools in which one or more drives are
combined as a backup target. Jobs submitted to a particular drive pool run on the
first available drive in that pool. You can also submit a job to a selected individual
drive in the drive pool.
Note Cascaded drive pools, in which multiple drives are linked together to create the
appearance of one drive with greater capacity, are not supported for shared storage
environments.
Related Topics:
“Using drive pools with the SAN Shared Storage Option” on page 1553
“Using device operations with the SAN Shared Storage Option” on page 1554
1551

About devices in the shared storage environment
Monitoring drives in the shared storage environment
When Devices is selected from the navigation bar, you can view all the physical drives
attached to your server, as well as the logical groups they are associated with. All the
logical groupings of the physical drives are displayed under Drive Pools as well as all
devices locally attached (by SCSI, SATA, SAS, USB, or ATAPI) to all servers on the SAN
and the secondary storage units accessed through the SAN.
Expanding the view for All Devices allows you to view all of the storage devices on the
SAN. Robotic libraries are listed below each server that has access to that robotic library,
even if the robotic library is not directly connected to the server.
You can also run the Device Summary report to monitor drives in the SAN Shared
Storage Option.
To view drive properties for shared devices, follow the steps in “Viewing storage device
properties” on page 195. With shared devices, the Write single block mode and Write
SCSI pass-through mode options are selected by default. Selecting these options
decreases the chances of dropping critical blocks of data and provides more detailed
information when write errors occur. These options are required for FC-connected tape
drives.
Related Topics:
“Policy Jobs Summary Report” on page 639
“Viewing a device’s configuration properties” on page 198
Viewing media in the shared storage environment
If you select a drive or select Slots from the Devices view, information for the media
contained in the drive or slot appears in the right pane. This information also appears
when All Media is selected from the Media view. For more information about viewing
media, see “Viewing media in storage devices” on page 170.
Related Topics:
“Using drive pools with the SAN Shared Storage Option” on page 1553
“Using device operations with the SAN Shared Storage Option” on page 1554
“Scheduling and viewing jobs in a SAN SSO environment” on page 1560
1552 Administrator’s Guide

Appendix T, Symantec Backup Exec SAN Shared Storage Option
About devices in the shared storage environment
Using drive pools with the SAN Shared Storage Option
When Backup Exec is installed, the All Drives () is created by default. In
a non-shared storage environment, this default drive pool contains the server’s locally
attached drives. In a shared environment, this default drive pool is created for each
server using the SAN Shared Storage Option, and contains both locally attached and
shared devices.
Symantec recommends creating a shared storage drive pool, which contains only shared
devices. To create a drive pool, see “Creating device pools” on page 177.
You can create other drive pools to meet your particular requirements. For example, you
may want to create a drive pool for high-performance drives and create a second drive
pool for lower-performance drives. High-priority jobs can then be sent to the
high-performance drive pool for faster completion.
Drives can belong to more than one drive pool, and drive pools can contain different
types of drives. In the shared storage environment, drive pools can contain both local
and shared drives, but jobs will run only on those drives in the pool to which the server has
access.
For example, suppose you create a drive pool that contains the local drives for both
media server A and media server B. If a job is submitted at media server B to this drive
pool, the job will run only on available drives attached to server B. If all of server B’s
drives are in use, the job has to wait for a drive on server B to become available. If a job
was submitted from server B to a drive pool that contained both its local and shared
devices, the job would run on the first available drive.
The steps for creating and deleting drive pools, adding or deleting drives from a drive
pool, and setting priorities for drives in a drive pool are the same in a shared storage
environment as in a non-shared storage environment.
Related Topics:
“Managing devices” on page 167
“Creating device pools” on page 177
1553

About devices in the shared storage environment
Using device operations with the SAN Shared Storage Option
Device operations allow you to manage the physical drives attached to the media servers
and perform some operations on the media in the drives. The steps for deleting drives,
pausing and resuming drives, completing the inventory drive process, cataloging media,
labeling media, and erasing media are identical in the shared and non-shared storage
environments.
Related Topics:
“Managing devices” on page 167
“Scheduling and viewing jobs in a SAN SSO environment” on page 1560
“About devices in the shared storage environment” on page 1551
“Sharing media” on page 1561
Renaming robotic libraries and drives
You cannot rename a server, but you can rename robotic libraries and drives to make
them more easily identifiable. You may want to use names that are more descriptive of
your operations, or you may want to identify the device by the user or location, such as
DATA_CENTER_ROBOTIC LIBRARY.
The names of all servers attached to the SAN appear when Devices is selected from the
navigation bar. Press F5 to manually refresh the screen and view new names.
The robotic libraries and drives can be renamed from any server sharing the ADAMM
database, and the new names will appear on all servers on the SAN.
Note The Device Management window on other Backup Exec administration consoles
may need to be manually refreshed before the new names appear on them.
Related Topics:
“Pausing and resuming devices” on page 175
1554 Administrator’s Guide

Appendix T, Symantec Backup Exec SAN Shared Storage Option
About devices in the shared storage environment
Sharing robotic libraries between Backup Exec for NetWare
Servers and Backup Exec for Windows Servers
Backup Exec for NetWare Servers and Backup Exec for Windows Servers SAN Shared
Storage Options inside the same fibre environment can share robotic libraries, which
lowers hardware costs. With robotic library sharing, you first create partitions of the
robotic libraries within Backup Exec for Windows Servers. Then you can create
additional partitions for the same robotic libraries for use within Backup Exec for
NetWare Servers.
You can view NetWare servers from a NetWare console and Windows servers from a
Windows console. If a Backup Exec for NetWare Servers job is targeted to a drive being
used for a Backup Exec for Windows Servers job, the drive appears as reserved.
Related Topics:
“Viewing storage devices” on page 168
“Library sharing prerequisites” on page 1555
“Configuring media servers for robotic library sharing” on page 1556
Library sharing prerequisites
Before you can share libraries, you must have the following installed:
■ Backup Exec for Windows Servers on the Windows media servers.
■ Backup Exec for NetWare Servers version 9.0 or later on the NetWare media servers.
■ The Backup Exec for Windows Servers SAN Shared Storage Option on each Windows
media server you want to operate in the shared environment.
■ Backup Exec for NetWare Servers SAN Shared Storage Option on each NetWare
media server you want to operate in the shared environment.
■ The Backup Exec for Windows Servers Library Expansion Option or the Backup Exec
for NetWare Servers Library Expansion Option.
Note The drive licenses you purchase for your robotic library are not platform-specific
for this implementation. For example, if you plan to share a ten-drive robotic
library, you can purchase nine Backup Exec for Windows Servers or Backup Exec
for NetWare Servers drive licenses (the first drive in a robotic library does not
require a Library Expansion Option license).
In order to successfully share robotic libraries, you need a working knowledge of both
Backup Exec for Windows Servers and of Backup Exec for NetWare Servers. You also
should have complete access to hardware and the ability to restart media servers.
1555

About devices in the shared storage environment
Before proceeding with the robotic library sharing configuration, plan how you want to
use your robotic library in this shared environment. For example, if you have a robotic
library that has 100 slots in it, you may want to partition your robotic library so Backup
Exec for Windows Servers uses 50 slots and Backup Exec for NetWare Servers uses 50
slots. Factors affecting how many slots you use for each operating system include media
rotation schemes, the number of servers you are protecting, and the types of data stored
on each server.
Label your media according to operating system or Backup Exec type. Color-coded or
unique bar codes identifying whether the tapes are being used with Backup Exec for
Windows Servers or Backup Exec for NetWare Servers is recommended. This will help
you identify the media when you need to restore data or rotate the media back into your
media rotation schedule.
Configuring media servers for robotic library sharing
You must ensure that no backup activity is occurring during robotic library sharing
configuration.
Note If you are running Backup Exec for NetWare Servers 9.1 on any of the media
servers that will be sharing the library, all Backup Exec for NetWare Servers media
servers in the shared storage environment must be installed in the same media
handling mode.
To configure media servers for robotic library sharing
1. At the Windows server where the SAN Shared Storage Option is installed, start the
Backup Exec administration console.
2. On the navigation bar, click Devices.
The tree pane contains a list of any fibre-attached or locally-attached devices.
3. Select the robotic library you want to share.
4. Under Robotic Library Tasks in the task pane, select Configure partitions.
5. Set up your partitions following the steps provided in “Creating robotic library
partitions” on page 214.
6. From the Devices tree pane, select the drive in this partition that will not be used by
your Backup Exec for Windows Servers media servers.
7. Delete the drive to ensure no jobs run to the unused partition.
1556 Administrator’s Guide

8. Repeat steps 6 and 7 for all drives in the unused partition.
Appendix T, Symantec Backup Exec SAN Shared Storage Option
About devices in the shared storage environment
9. Reboot all other Windows servers and make sure you can see the shared robotic
library on each server.
Note No fibre activity or backup jobs should be run until all Backup Exec for Windows
Servers and all Backup Exec for NetWare Servers are configured for robotic library
sharing.
To configure Backup Exec for NetWare Servers 9.x running in the partition management
mode
1. From the Administration Console, ensure you are connected to the Primary Group
Server and that you are running in partition management mode.
From the Administration Console for NetWare at the Primary Group Server, ensure
you are running in partition management mode.
2. Delete existing partitions.
To delete a partition from the Administration Console:
a. Click Drives.
b. Click Partitions.
c. Right-click the partition you want to delete, and click Delete.
d. When prompted, click OK.
e. Repeat step c and step d for each partition you want to delete.
To delete a partition from the Administration Console for NetWare:
a. Select Drives.
b. Select Partitions.
c. Select the partition you want to delete, and press DEL.
d. When prompted, press Y.
e. Repeat step c and step d for each partition you want to delete.
3. Create the partitions in the shared library to be used by Backup Exec for NetWare
Servers.
1557

About devices in the shared storage environment
To create a partition from the Administration Console:
a. From the Administration Console, click Drives.
b. Right-click Partitions.
c. Click New Partition.
d. Enter options on the New Partition dialog box.
e. Click OK.
4. Enter options in the New Partition General dialog box.
5. Enter options in the New Partition Configuration dialog box.
6. Click OK.
To create a partition from the Administration Console for NetWare:
a. From the Administration Console for NetWare, select Drives.
b. Select Partitions.
c. Press INS.
d. Select a drive to be included in this partition.
e. Ensure Configuration is selected, and press ENTER to view or edit options on the
Configuration dialog box.
f. Press F2 to return to the General dialog box.
g. Select Advanced Configuration and then press ENTER to view or edit options on
the Advanced Configuration dialog box.
h. Press F2 to return to the General dialog box.
i. Press F2.
7. If you plan to share more than one library, repeat step 2 and step 3 for each library
that will be shared.
8. Restart Backup Exec for NetWare Servers on the group servers and make sure you
can see the shared library on each server.
1558 Administrator’s Guide

Appendix T, Symantec Backup Exec SAN Shared Storage Option
About devices in the shared storage environment
To configure Backup Exec for NetWare Servers 9.x running in the media management mode
1. From the Administration Console, ensure you are connected to the Primary Group
Server and that you are running in media management mode.
From the Administration Console for NetWare at the Primary Group Server, ensure
you are running in media management mode.
2. Select Drives.
3. Select Drive Pools.
4. Select All Drives.
5. From the Administration Console, right-click the robot you want to share, and then
click Properties.
From the Administration Console for NetWare, select the robot you want to share,
and press F4.
6. Select Configuration.
7. Enter the starting slot and number of slots to be used by NetWare servers.
8. From the Administration Console, click OK.
From the Administration Console for NetWare, press F2.
9. Restart Backup Exec for NetWare Servers on the group servers and make sure you
can see the shared library on each server.
Related Topics:
“Symantec Backup Exec Library Expansion Option” on page 1539
1559

About devices in the shared storage environment
Scheduling and viewing jobs in a SAN SSO environment
Creating backup and restore jobs with the SAN Shared Storage Option is identical to
creating jobs in a non-shared storage environment. You can also create test run jobs,
resource discovery jobs, and duplicate backup data jobs.
While the SAN Shared Storage Option does not provide a central view of the jobs
scheduled on all servers on the SAN, you can always view your scheduled, active, and
completed jobs on the media server to which you submitted the jobs by selecting Job
Monitor from the navigation bar.
Note If your job is awaiting a storage device, the Job Monitor window will not display a
Device Name. Also, if the Job Status displays as Queued, the job is awaiting an
available storage device.
With the SAN Shared Storage Option enabled, all of the media servers share access to the
storage devices through the shared ADAMM database. The server that reserves the
storage device first runs its job first. Therefore, a job scheduled by a server may not run
exactly when scheduled if all the storage devices are being used by other servers.
When a server releases control of a device, there is a short delay before the server looks
for additional jobs to process. This delay provides a window of opportunity for other
media servers to reserve the shared storage device.
If a device fails during a nonrecurring job, that job will fail and will be rescheduled on
hold. If a device fails during a recurring job, the job is rescheduled. The device is then
released for the next job scheduled for that device. But, depending on why the device
failed, the second job may become trapped. This might prevent other jobs from seeing
the device, running to normal completion, or failing and being rescheduled to an "on
hold" status. If you determine that a device is malfunctioning, you may want to retarget
jobs to another drive or quickly replace the failed drive and resume the jobs that were
placed on hold.
Related Topics:
“Backing up data” on page 345
“Restoring data” on page 483
“Monitoring jobs” on page 442
“Viewing and changing completed jobs” on page 455
1560 Administrator’s Guide

Sharing media
Appendix T, Symantec Backup Exec SAN Shared Storage Option
About devices in the shared storage environment
The Backup Exec servers can share media within the shared storage devices, but not
simultaneously. For example, media server A can write a backup to a media, and when
that job is finished, media server B can append another backup to the same media. Or, if
overwrite protection is not enabled, media server B may overwrite that media.
Media sets are not server-centric. In the shared storage environment, all users have a
view of all media and media sets. Each media set can contain media in the shared devices
and media in any local devices attached to servers.
Note The default media overwrite protection is not server-centric; this option is set in
the shared ADAMM database and affects all media, including media in locally
attached devices. For example, if media overwrite protection is set to None by one
server, all media in the shared storage environment – including media in other
servers’ locally attached devices – are immediately available for overwriting.
Media stored in locally-attached secondary storage devices are not accessible by other
media servers.
Cataloging media in SAN SSO environments
The SAN Shared Storage Option uses a shared catalog database. A tape that has already
been cataloged can be physically moved from one device to another and will not have to
be recataloged.
If the primary server is not available over the network when a secondary server
generates catalog information, the information is stored temporarily on the secondary
server until automatic catalog synchronization occurs.
Because catalogs are shared, information can be restored using any server that has
access to a device where the tape resides. If the tape resided in a shared device, or in a
local device on the server where you want to perform the restore, simply start a restore
job. Otherwise, you have to move the tape into a drive that is accessible.
Related Topics:
“Cataloging media while reviewing devices or media” on page 284
1561

About devices in the shared storage environment
Media rotation in SAN SSO environments
Media rotation jobs are treated the same as backup jobs. You can schedule a media
rotation job to run on any device you have access to, such as a local device or a shared
storage device. You cannot schedule a media rotation job to run on a device you do not
have access to, such as a tape drive attached to the local SCSI bus of another server.
If a media rotation job is scheduled to begin, but all available devices are in use, the job
will be placed into the queue.
To successfully use the Media Set Wizard in a shared storage environment, you must use
one of the following strategies:
■ Restrict use of the Media Set Wizard to a single media server.
■ Use the same Overwrite Protection Periods and the same full backup day whenever
you use the Media Set Wizard on all media servers in the shared storage
environment.
■ Edit the jobs and rename the media sets created by each Media Set Wizard used so
the jobs and media sets are server-centric.
Related Topics:
“Scheduling and viewing jobs in a SAN SSO environment” on page 1560
1562 Administrator’s Guide

Appendix T, Symantec Backup Exec SAN Shared Storage Option
Designating a new database server and setting up servers
Designating a new database server and setting up servers
You can change the SAN Shared Storage Option configuration through Backup Exec
Utility (Beutility.exe). This utility allows you to assign a new database server and attach
media servers to or disconnect them from the database server.
You may wish to replace the database server for several reasons, including:
■ A newer, faster server has become available.
■ The database server has stopped functioning.
If the current database server is functioning, you should consider specifying the current
database server when installing SAN Shared Storage Option to the new system. This will
allow you to test the fibre connections before designating a new database server. If the
current database server is not functioning, installing the new system as the database
server is recommended.
Tips for maintaining the database server and the ADAMM
database
The ADAMM database and the database server are important components of the SAN
Shared Storage Option. To protect against possible loss of the ADAMM and catalog
databases, you should run frequent backup jobs of the entire Backup Exec directory tree
on the shared database server.
When scheduling backups of the database server’s Backup Exec directory, base the
frequency of these backup jobs on the rate at which backup sets are being created and the
number of tapes affected by all of the media servers on the SAN. All backup sets and
tapes affected since the last shared database/catalog server backup would have to be
recataloged if all information on the database server was lost.
Create a special media set just for backing up the Backup Exec directory tree and the
Windows operating system on the database server. This will reduce the number of tapes
that must be cataloged to find the files for restoring the ADAMM database and catalogs.
Caution If you allow the backups of these files to go to a large media set, you may have
to catalog every tape in that large media set in order to find the latest versions
of the ADAMM database and catalogs to restore.
If the database server is not operational, Backup Exec is unusable on all of the servers on
the SAN. The Intelligent Disaster Recovery Option is strongly recommended for
protecting the database server. Should this entire system be lost, you can use IDR to
quickly recover this system.
1563

Designating a new database server and setting up servers
If you deem the Backup Exec functions to have a high availability requirement, you
should consider setting up one of the other media servers on the storage network as a
standby primary server.
Creating a standby primary database server
You should have a standby server configured and available in case your primary server
fails. To avoid data loss if the primary database server fails, Symantec recommends that
you save the bedb.bak file and the Catalogs directory to a separate server after the
scheduled daily database maintenance.
To create a standby primary database server
1. Use BEUtility to add all the SAN servers that will use the new primary SAN SSO
server.
2. Use BEUtility to create a media server group that contains all the servers you added
in step 1.
Note Do not select the Create group from SAN SSO configuration option.
3. Use BEUtility to promote a new SAN SSO server to primary in the media group you
created.
4. Use BEUtility to stop the Backup Exec services on all media servers in the media
server group.
On the media server that you promoted to primary, navigate to \Program
Files\Symantec\Backup Exec\Data directory and rename the bedb.bak file to
indicate that this is the original file.
Example originalbedb.bak or bedborg.bak
On the original primary server, navigate to \Program Files\Symantec\Backup
Exec\Data directory. Copy the bedb.bak file to the same directory on the new primary
server.
If the original primary server is unavailable, locate the latest copy of the bedb.bak
file and copy it to the new primary server.
5. On the media server that you promoted to primary, navigate to \Program
Files\Symantec\Backup Exec. Rename the Catalogs directory to indicate that
this is the original.
1564 Administrator’s Guide

Appendix T, Symantec Backup Exec SAN Shared Storage Option
Designating a new database server and setting up servers
6. On the original primary server, navigate to \Program Files\Symantec\Backup
Exec\. Copy the Catalogs directory to the same directory on the new primary server.
If the original primary server is unavailable, locate the latest copy of the Catalogs
directory and copy it to the new primary server.
7. Use BEUtility to restore the database you copied in step 6. Be sure to select the Drop
existing database and reload from backup option.
8. Use BEUtility to start the Backup Exec services on all the media servers in the media
server group.
Related Topics:
“Symantec Backup Exec Intelligent Disaster Recovery Option” on page 1501
“Restoring data by setting job properties” on page 488
Starting and stopping Backup Exec Services on multiple servers
Stopping Backup Exec services is the first step in system maintenance. After system
maintenance, you can start the services again. You can start and stop services at the
same time, called "bouncing", which refreshes the database, re-establishes connections,
and forces the system back into synchronization. It is similar to rebooting all the servers.
For steps for starting and stopping servers, refer to “Starting and stopping Backup Exec
services” on page 123.
1565

Troubleshooting and recovering failed components
Troubleshooting and recovering failed components
Various problems can occur at any location in a SAN. In order for Backup Exec to work
properly, a device has to be recognized in three locations; the bridge/router must
recognize it as a SCSI device, the operating system must recognize it as a device, and
Backup Exec must recognize it as a supported device. In some cases, there will be a
problem with your hardware that will require you to contact your hardware vendor for
technical support.
You may need to replace a component of your SAN, such as a bridge or hub. For specific
steps for replacing your equipment, refer to your hardware vendor’s documentation.
Related Topics:
“Checklist for troubleshooting devices that have gone offline” on page 1566
Checklist for troubleshooting devices that have gone offline
If a device in your SAN has gone offline, follow these steps to determine the source of the
problem.
1. Before you begin troubleshooting, verify that your devices are on the Backup Exec
supported device list, which is located at:
http://support.veritas.com/rd/bews-compatibility.htm.
Also verify that all hardware drivers are up to date and started.
2. Use the Windows Device Manager to verify that the operating system recognizes the
device. If the device is not recognized, see “SAN hardware tips” on page 1567.
3. For robotic libraries, verify that robotic library support is installed.
4. Check the system event log for the following errors, which indicate SAN
communication errors: SCSI errors 9, 11, and 15, or timeout errors relating to
storage. Check the application event log for multiple events 33152. These events
indicate SAN communication errors. See “SAN hardware tips” on page 1567 or
contact your hardware vendor.
5. If the library is online, but some or all of the drives are offline, use Backup Exec to
initialize the library. To initialize the library:
a. On the navigation bar, click Devices.
b. Select the library, and then under Robotic Library Tasks, click Initialize.
1566 Administrator’s Guide

Appendix T, Symantec Backup Exec SAN Shared Storage Option
Troubleshooting and recovering failed components
6. If initializing the library does not bring the devices online, check the library for the
following: an error display on the front panel, mechanical problems, or tapes
inappropriately in the drives. Correct any errors that you find.
7. If no errors exist on the library or if you corrected the errors and the devices are still
offline, stop Backup Exec services and then restart them when all Backup Exec jobs
are inactive in the SAN.
8. If restarting the services does not bring the devices online, restart the operating
system. Be sure that no Backup Exec jobs are running when you restart.
9. If restarting the operating system does not bring the devices online, reset the SAN to
help identify problem tape devices. Recycling the SAN may also resolve fibre
problems.
Related Topics:
“Resetting the SAN” on page 1568
SAN hardware tips
The following is a list of common hardware errors that occur in a SAN environment. If
you find errors with your hardware, please contact your hardware vendor for specific
instructions.
1. Verify that the proper device drivers were installed.
2. Verify that the fibre cable is securely connected to the HBA and the switch.
3. Verify that the SCSI bridge is properly connected to the library and the switch. Apply
normal SCSI troubleshooting techniques at the fibre to SCSI bridge. Use a bridge
administration tool to verify that the bridge recognizes all of the devices. Also verify
that the bridge firmware is up to date.
4. If some of the servers in the SAN recognize the tape devices, but other servers do
not, check for a failed hardware component between the server and the switch. If
none of the servers in the SAN recognize the tape devices, check for a failed
hardware component between the switch and the tape devices.
5. Reset the SAN, which may identify problem hardware components and may resolve
fibre problems.
1567

Troubleshooting and recovering failed components
Resetting the SAN
To reset the SAN
1. Power down all servers, libraries, and SCSI to fibre bridges in the SAN.
In rare cases, you may need to power down the switch also. If you need to power
down the switch, you should power it on before any other components and wait for
all checks to complete before powering on other components.
2. Power on the library.
3. After the library initialization is complete, power on the bridge.
4. Verify that the switch recognizes the library.
5. Power on the primary SSO server.
6. Verify that the operating system recognizes the library and drives.
7. Power on one of the secondary SSO servers. Wait for the secondary server to boot
before powering on the other secondary SSO servers.
Bringing devices online after an unsafe device removal event
If a device is in use by Backup Exec at the time of an unsafe device removal event, the
device will go offline in Backup Exec.
To bring a device online after an unsafe device removal event
1. Verify that no Backup Exec jobs are running in the SAN.
2. If the library is online, but the drives are offline, use Backup Exec to initialize the
library. If initializing the library brings the drives online, you have completed this
procedure. If initializing the library does not bring the drives online, proceed to step
3.
3. If the library is offline or if the drives are offline after initialization, stop all Backup
Exec services and then restart them.
4. If steps 1-3 do not bring the device online again, see “SAN hardware tips” on
page 1567.
1568 Administrator’s Guide

Best practices for SAN SSO
Appendix T, Symantec Backup Exec SAN Shared Storage Option
Best practices for SAN SSO
■ Before installing Backup Exec, be sure that all hardware in the SAN is working and
configured properly.
■ Make sure that the primary server is the fastest server and has the fewest extraneous
operations.
■ Use a separate primary server for each SAN.
■ Make sure that the HBA drivers, SCSI to fibre bridges, and library firmware have
been updated to the hardware vendor’s most current release.
■ Make sure that all HBA cards on the SAN are using the same and the most current
firmware and driver levels.
■ Keep the servers in the SAN in the same Microsoft Administration domain.
Cross-domain environments can cause authentication problems during install and
can block access to resources during backups.
■ Change the display names of libraries and drives to names that reflect the servers or
jobs for which you will use them.
■ Do not use cascaded drive pools in a SAN environment.
■ Run frequent backups of the entire Backup Exec directory tree on the shared
database server.
■ Create a separate media set to use only for backups of the Backup Exec directory tree
and the Windows operating system on the database server. This will reduce the
number of tapes you need to catalog to find the files to restore the ADAMM database
and catalogs.
■ Use a switch administration tool to verify that each server is in a zone configuration
with the tape devices.
■ Disable the operating system’s removable storage service.
1569

Best practices for SAN SSO
1570 Administrator’s Guide

Symantec Backup Exec
NDMP Option
Appendix
U
The Symantec Backup Exec for Windows Servers NDMP Option lets Backup Exec use the
Network Data Management Protocol (NDMP) to initialize and control backups and
restores of Network Attached Storage (NAS) devices.
You can back up data to a storage device that is connected directly to the NDMP server
(direct-attached) or that is connected to another NDMP server (filer-to-filer).
You can back up NDMP data only to the NDMP storage devices; however, the Backup Exec
server and the NDMP server can share a storage device. The duplicating of NDMP backup
sets is not supported.
Related Topics:
“Requirements for using the NDMP Option” on page 1571
“About installing the NDMP Option” on page 1572
Requirements for using the NDMP Option
To use the NDMP Option, the Backup Exec server must have the following items
installed:
■ Windows 2000/XP/Server 2003.
■ Backup Exec for Windows Servers 11.d or later.
In addition, you must have the following:
■ A NetApp filer with Data ONTAP 7.0 or later installed.
■ An NDMP server with the Network Data Management Protocol enabled.
■ A supported storage device that is attached to an NDMP server.
1571

About installing the NDMP Option
About installing the NDMP Option
The NDMP Option is installed locally on the media server as a separate add-on
component of Backup Exec. No files are copied to the NDMP server.
To install the NDMP Option on the local media server, see “Installing Backup Exec
options to the local computer” on page 85.
Configuring the NDMP server
In order for Backup Exec to back up NDMP resources, the NDMP service must be
running on the NDMP server and you must authenticate with the NDMP server.
To start the NDMP Service
❖ Entering the following command on the NDMP server (accessed by using telnet or
the Web interface):
filerA> ndmpd on
To configure the NDMP server to use the challenge (MD5) method for authentication
❖ Enter following command:
filerA> options ndmpd.authtype challenge
To authenticate with the NDMP server you should use the root password or non-root
user with the NDMP-specific password that the system generated. To configure these
and other settings, refer to your NAS documentation.
Configuring Backup Exec to use the NDMP Option
Before you can use the NDMP Option, you must do the following tasks in Backup Exec:
■ Add the NDMP server that you want to back up to the backup selection list. You can
add the NDMP server to the NDMP Servers node or the User-defined Selections
node.
■ Add the storage device that is attached to the NDMP server to the Backup Exec
device list.
When you add an NDMP storage device to the Backup Exec device list, Backup Exec
automatically adds the NDMP server to the NDMP Servers node. If you want to protect
an NDMP server that does not have an attached storage device, add the NDMP server to
the backup selections list as a user-defined selection.
1572 Administrator’s Guide

Appendix U, Symantec Backup Exec NDMP Option
Configuring Backup Exec to use the NDMP Option
To add an NDMP server to the backup selections list, see “Adding a user-defined selection
to the User-defined Selections node” on page 323.
Note In a CASO environment, you can add an NDMP Server only to a central
administration server or to a managed media server on which the device and
media database is located.
To add an NDMP storage device
1. On the navigation bar, click Devices.
2. In the task pane, under NDMP Tasks, click Add NDMP Server.
3. In the Add NDMP Server dialog box, enter the following information:
NDMP Server Enter the name of the NDMP Server.
Port Enter the port to be used for communications between the
Backup Exec server and the NDMP server.
Logon Account Select the Logon Account for the NDMP server.
NDMP server supports
ICMP ping operations
4. Click OK to add the NDMP server.
Check NDMP server supports ICMP ping operations to
ensure that the Backup Exec can use ping to locate the
NDMP server.
5. After adding the NDMP server, restart Backup Exec services.
The NDMP server and the storage devices that are directly attached to it appear in
the devices pane.
Related Topics:
“Starting and stopping Backup Exec services” on page 123
1573

Backing up NDMP resources
Backing up NDMP resources
The following limitations exist when creating backup jobs for NDMP resources:
■ Backup selection lists cannot contain selections for both NDMP and non-NDMP
resources.
■ The NDMP Option will not exclude folders from the backup job if the parent folder is
being backed up. Instead, all items in the parent folder will be backed up, even if you
marked items for exclusion from the backup.
■ Backup Exec cannot gather sufficient file and directory information on an NDMP
backup to accurately populate the Job Summary and Set Detail Information sections
of the job history with the number of files, directories, files skipped, corrupt files,
and files in use. These numbers always appear as 0.
■ While the Verify after backup completes option is supported, the creation of a
separate verify job is not supported for the NDMP option. To ensure that data from a
previous backup can be read, run a restore job using the option Restore without
writing data to disk.
See “Restoring NDMP data” on page 1576.
To back up NDMP resources
1. On the navigation bar, click the arrow next to Backup.
2. Click New Backup Job.
3. On the Properties pane, under Source, click Selections.
4. In the backup selections tree, expand either NDMP Servers or User-defined
Selections.
If Backup Exec added the NDMP server to the backup selection list automatically,
the NDMP server appears in the NDMP Servers node. If you added the NDMP server
to the backup selection list manually, the NDMP server appears in the User-defined
Selections node.
5. Select the NDMP resource you want to back up.
You may be prompted to select or create a logon account for this resource.
6. Do one of the following:
■ Select the entire NDMP server for backup or expand the resource.
■ Select individual volumes or directories to backup.
You can browse to the individual file level, but you cannot select them for backup.
1574 Administrator’s Guide

7. On the Properties pane, under Destination, click Device and Media.
Appendix U, Symantec Backup Exec NDMP Option
Backing up NDMP resources
8. In the Device list, select a storage device that is attached to an NDMP server.
9. On the Properties pane, under Settings, click NDMP.
10. Select any of the following options:
Backup method Select this option to specify the backup level. Level
0 provides a full backup. Levels 1 through 9 provide
various levels of incremental backups. Level 1
backup method backs up new or modified files since
the level 0 backup, level 2 backup method backs up
new or modified files since the level 1 backup, and
so on.
Backup Access Control Lists Check Backup Access Control Lists to have Backup
Exec back up the access control lists during the
backup. The access control lists contain the users’
or groups’ access rights to each share.
Disable file history Select this option to prevent the generation of file
history data. File history is used to optimize
recovery of selected subsets of data from the
backup image. File history generation and
processing increase the backup time. To improve
backup time, check Disabling file history. If file
history is made unavailable and you must later
restore data, restore the entire backup image.
11. Do one of the following:
■ Start the backup job.
■ Select other backup options from the Properties pane, and then start the backup
job.
Related Topics:
“Configuring logon accounts” on page 146
“Creating a backup job by setting job properties” on page 349
“Configuring Backup Exec to use the NDMP Option” on page 1572
“Configuring the NDMP server” on page 1572
“Restoring NDMP data” on page 1576
1575

Restoring NDMP data
Restoring NDMP data
During the backup selection process, all selections were made at the folder level or
higher. During the restore process, you can select individual files for restore if file
history was not disabled for the backup job.
Backup Exec cannot gather sufficient file and directory information on an NDMP restore
to accurately populate the Job Summary and Set Detail Information sections of the job
history with the number of files, directories, files skipped, corrupt files, and files in use.
These numbers always appear as 0.
NDMP backup sets cannot be cataloged unless the option Use storage media-based
catalogs is selected as a catalog default.
See “Setting catalog defaults” on page 485.
To restore NDMP data
1. On the navigation bar, click the arrow next to Restore.
2. Click New Restore Job.
3. Select the data you want to restore.
4. To change or test logon credentials, on the Properties pane, under Source, click
Resource Credentials.
See “Changing and testing resource credentials for restore jobs” on page 516.
5. On the Properties pane, under Source, click Device.
See “Device options for restore jobs” on page 492.
6. On the Properties pane, under Settings, click NDMP.
7. Select any of the following options:
Restore Access Control Lists Select this option to have Backup Exec restore the
access control list data when the restore is performed.
The access control lists contain the users’ or groups’
access rights to each share.
1576 Administrator’s Guide

8. Do one of the following:
■ Start the restore job.
Appendix U, Symantec Backup Exec NDMP Option
Setting default backup and restore options for NDMP
Enable Direct Access Recovery Select this option to have Backup Exec use Direct
Access Recovery (DAR) during the restore job. With
DAR-enabled recovery, Backup Exec can specify the
exact location of a file in a backup data stream. The
NDMP server can then read the data applicable to the
single file being restored, which reduces the amount of
information that is processed and significantly reduces
recovery time. If DAR is not available, the restore may
take significantly longer.
Restore without writing data to disk
(Verify data without doing a restore)
■ Select other restore options from the Properties pane, and then start the restore
job.
Related Topics:
“Setting catalog defaults” on page 485
“Restoring data by setting job properties” on page 488
“Backing up NDMP resources” on page 1574
“Setting default backup and restore options for NDMP” on page 1577
Setting default backup and restore options for NDMP
You can use the defaults set by Backup Exec during installation for all NDMP backup and
restore jobs, or you can choose your own defaults. You can also change the defaults for
any specific backup or restore job.
To set default backup and restore options for NDMP
1. On the Tools menu, click Options.
2. On the Properties pane, under Job Defaults, click NDMP.
Select this option to have Backup Exec verify the
integrity of the data without actually restoring the
data. Running a restore job with this option selected is
the only way to verify data with the NDMP option.
1577

Setting default backup and restore options for NDMP
3. Select the appropriate options as follows:
Backup method Select this option to specify the backup level. Level 0 provides a
full backup. Levels 1 through 9 provide various levels of
incremental backups. Level 1 backup method backs up new or
modified files since the level 0 backup, level 2 backup method
backs up new or modified files since the level 1 backup, and so on.
Backup Access Control
Lists
4. Click OK.
Related Topics:
“Backing up NDMP resources” on page 1574
“Restoring NDMP data” on page 1576
Check Backup Access Control Lists to have Backup Exec back up
the access control lists during the backup. The access control lists
contain the users’ or groups’ access rights to each share.
Disable file history Select this option to prevent the generation of file history data.
File history is used to optimize recovery of selected subsets of
data from the backup image. File history generation and
processing increase the backup time. To improve backup time,
check Disabling file history. If file history is made unavailable
and you must later restore data, restore the entire backup image.
Restore Access Control
Lists
Enable Direct Access
Recovery
Select this option to have Backup Exec restore the access control
list data when the restore is performed. The access control lists
contain the users’ or groups’ access rights to each share.
Select this option to have Backup Exec use Direct Access Recovery
(DAR) during the restore job. With DAR-enabled recovery, Backup
Exec can specify the exact location of a file in a backup data
stream. The NDMP server can then read the data applicable to the
single file being restored, which reduces the amount of
information that is processed and significantly reduces recovery
time. If DAR is not available, the restore may take significantly
longer.
1578 Administrator’s Guide

Appendix
Accessibility and Backup Exec
V
V
Symantec products meet federal accessibility requirements for software as defined in
Section 508 of the Rehabilitation Act:
■ http://www.access-board.gov/508.htm
Keyboard shortcuts are available for all graphical user interface (GUI) operations and
menu items. Symantec products are compatible with operating system accessibility
settings as well as a variety of assistive technologies. All manuals also are provided as
accessible PDF files, and the online help is provided as HTML displayed in a compliant
viewer.
The following topics detail accessibility features and compliance in Backup Exec:
■ “Keyboard navigation and shortcuts in Backup Exec” on page 1580
■ “General keyboard navigation within the GUI” on page 1580
■ “Keyboard navigation within dialog boxes” on page 1581
■ “Keyboard shortcuts” on page 1582
■ “Support for accessibility settings” on page 1586
1579

Keyboard navigation and shortcuts in Backup Exec
Keyboard navigation and shortcuts in Backup Exec
All program functions and menu items are accessible using the keyboard exclusively.
Backup Exec uses standard operating system navigation keys and keyboard shortcuts.
For its unique functions, Backup Exec uses its own keyboard shortcuts, which are
documented “Keyboard shortcuts” on page 1582.
Items in the task pane that do not have keyboard shortcuts can be accessed by using the
operating system’s "mouse keys", which allow you to control the mouse through the
numerical keyboard.
To see a table of the standard Microsoft navigation keys and keyboard shortcuts, select
your version of Microsoft Windows from the table at:
http://www.microsoft.com/enable/products/keyboard.aspx
General keyboard navigation within the GUI
You can navigate and use Backup Exec with only the keyboard. In the GUI, the current
active tree or table has a dark blue highlight, and the current active tab, radio button, or
checkbox is enclosed within a rectangle formed by dotted lines. These areas are said to
have focus and will respond to commands.
All Symantec GUIs use the following keyboard navigation standards:
■ The TAB key moves the focus to the next active area, field, or control, following a
preset sequence. SHIFT+TAB moves the focus in the reverse direction through the
sequence.
■ CTRL+TAB exits any Console area that you internally navigate with the TAB key.
■ UP and DOWN ARROW keys move focus up and down the items of a list.
■ The ALT key in combination with the underlined mnemonic letter for a field or
command button shifts the focus to that field or button.
■ Either ENTER or the SPACEBAR activates your selection. For example, after pressing
the TAB key to select Next in a wizard panel, press the SPACEBAR to display the next
screen.
■ SHIFT+F10 provides access to context menus.
1580 Administrator’s Guide

Keyboard navigation within dialog boxes
Appendix V, Accessibility and Backup Exec
Keyboard navigation and shortcuts in Backup Exec
Dialog boxes contain groups of controls necessary to set options or settings for
programs. Here are some general rules about dialog box navigation:
■ The TAB key moves focus between controls within the dialog box along a preset
sequence.
■ Controls displaying a mnemonic (an underlined letter) can be selected regardless of
focus by typing ALT and the underlined letter.
■ A dark border indicates the default command button. Press ENTER at any time to
choose the button with a dark border.
■ ESC chooses the Cancel button if one exists.
■ SPACEBAR chooses a control you select with the TAB key.
■ SPACEBAR changes the state of a checkbox that has focus. Typing a mnemonic (if
one is available) will move the focus to the checkbox and change its state.
■ Arrow keys move focus within radio buttons, list boxes, sliders, groups of option
controls, or groups of page tabs.
■ Items that cannot be changed are not visited by the TAB key sequence. Options that
are unavailable are grayed-out and can neither be selected nor given focus.
While the controls described here are typically found in dialog boxes, they also can occur
in other contexts. The same navigation standards will apply.
Tabbed dialog boxes
Some dialog boxes use tabbed pages to subcategorize groups of many options. Each
tabbed page contains different groups of controls. Use TAB to move the focus between
tabbed pages within a dialog box. Typing the mnemonic for a tab also moves the focus to
the tabbed page and displays its page of controls.
The following table lists keyboard navigation rules within tabbed dialog boxes:
Keyboard navigation within tabbed dialog boxes
Keyboard input Result
CTRL+PAGE
DOWN or
CTRL+TAB
Switches to the next tab and displays the page.
CTRL+ PAGE UP Switches to the previous tab and displays the page.
1581

Keyboard navigation and shortcuts in Backup Exec
Keyboard navigation within tabbed dialog boxes (continued)
Keyboard input Result
RIGHT ARROR
or LEFT
ARROW
List boxes
List boxes display a column of available choices. There are different kinds of list boxes
with additional navigation conventions:
■ Drop-down list boxes by default show only the selected item. A small button to the
right of the control shows a downward-pointing arrow. Select the arrow to display
more items from the list box. If there are more choices than can fit in the preset list
box area, a slider appears along the side of the list box. Show or hide the list using
ALT+DOWN ARROW, ALT+UP ARROW, or F4. The TAB key selects an item.
■ Extended selection list boxes support selecting single items, blocks of items, or
combinations of the two. After selecting an item, hold down CTRL+navigation keys
to select or clear additional items or blocks of items.
Keyboard shortcuts
When the focus is on a tab selector, chooses the next or previous tab in the
current row and displays the page.
All menu items can be selected by using accelerator or mnemonic keyboard shortcuts. An
accelerator is a key combination that provides shortcut access to a GUI function. A
mnemonic (sometimes referred to as a “hot key”) is a single-key equivalent (used in
combination with the ALT key) for selecting GUI components such as menu items. The
mnemonic “hot key” letter is underlined in the GUI.
Routine functions such as opening, saving, and printing files can be performed using the
standard Microsoft keyboard shortcuts. Other menu items are unique to Backup Exec.
The following table lists the keyboard shortcuts unique to Backup Exec:
Keyboard shortcuts unique to Backup Exec
Backup Exec
Accelerator
Backup Exec
Mnemonic
Result
ALT F The File menu expands. From the File menu, you can create
new jobs, devices and media, print selected items, view
properties, or exit Backup Exec.
1582 Administrator’s Guide

Keyboard shortcuts unique to Backup Exec (continued)
Backup Exec
Accelerator
Backup Exec
Mnemonic
Appendix V, Accessibility and Backup Exec
Result
Keyboard navigation and shortcuts in Backup Exec
ALT E The Edit menu expands. From the Edit menu, you can
rename, delete, copy, and select items. In addition, you
can work with selection lists and search catalogs.
ALT V The View menu expands. From the View menu, you can
change the information that displays on the screen. The
options on the View menu change according to which
item is selected on the navigation bar.
ALT N The Network menu expands. Use the Network menu to
work with Backup Exec logon accounts, connect to
media servers on the network, or to reconnect to a local
media server.
ALT T The Tools menu expands. The Tools menu provides many
important options for working with Backup Exec,
including starting and stopping services, using device
and media operations, using Wizards, and setting
default options.
ALT W The Window menu expands. Use the Window menu to
move to a new window or view.
ALT H The Help menu expands. Use the Help menu to access
Backup Exec documentation and various Symantec
Web sites.
Select secondary menu items by opening the main menu and using the UP or DOWN
ARROW key until the desired item is highlighted. Press the RIGHT ARROW key to open a
submenu, and ENTER to select your choice.
Keyboard shortcuts are not case-sensitive. Mnemonic keystrokes may be pressed either
sequentially or simultaneously. All menu items have mnemonics, but not all menu items
have accelerators.
1583

Keyboard navigation and shortcuts in Backup Exec
The following table lists the shortcut keys in Backup Exec Utility.:
Keyboard shortcuts unique to Backup Exec Utility
Backup Exec
Accelerator
Backup Exec
Mnemonic
Result
ALT F The File menu expands. From the File menu, you can create
new media servers and media server groups, view properties,
or exit Backup Exec Utility.
ALT E The Edit menu expands. From the Edit menu, you can
rename, delete, and select items
ALT V The View menu expands. From the View menu, you can
change the information that displays on the screen.
ALT H The Help menu expands. Use the Help menu to access
Backup Exec documentation and various Symantec Web
sites.
The following table lists the shortcut keys in the Backup Exec Desktop and Laptop Option
Administration Console:
Keyboard shortcuts unique to Backup Exec Desktop and Laptop Option Administration Console
Backup Exec
Accelerator
Backup Exec
Mnemonic
Result
ALT F The File menu expands. From the File menu, you can create
new Profiles and Storage Locations, and add users.
ALT E The Edit menu expands. From the Edit menu, you can restore
files, search for files to restore, manage alerts, and delete
items.
ALT V The View menu expands. From the View menu, you can
change the information that displays on the screen.
ALT N The Network menu expands. Use the Network menu to
work with administrator accounts, connect to media
servers on the network, or to reconnect to a local media
server.
1584 Administrator’s Guide

Appendix V, Accessibility and Backup Exec
Keyboard navigation and shortcuts in Backup Exec
Keyboard shortcuts unique to Backup Exec Desktop and Laptop Option Administration Console
Backup Exec
Accelerator
ALT T The Tools menu expands. Use the Tools menu to set global
excludes, access all DLO wizards, and manage service
credentials.
ALT W The Window menu expands. Use the Window menu to move
to a new window or view.
ALT H The Help menu expands. Use the Help menu to access
Backup Exec documentation and various Symantec Web
sites.
The following table lists the shortcut keys in the Backup Exec Desktop and Laptop Option
Desktop Agent:
Keyboard shortcuts unique to Backup Exec Desktop and Laptop Option Desktop Agent
Backup Exec
Accelerator
Backup Exec
Mnemonic
Backup Exec
Mnemonic
Result
Result
ALT F The File menu expands. From the File menu, you can
minimize or exit the Desktop Agent.
ALT V The View menu expands. From the View menu, you can
change the information that displays on the screen.
ALT K The Tasks menu expands. Use the Tasks menu to run a job or
refresh the view.
ALT T The Tools menu expands. Use the Tools menu to reset dialog
boxes and accounts.
ALT H The Help menu expands. Use the Help menu to access the
online help for the Desktop Agent.
1585

Support for accessibility settings
Support for accessibility settings
Symantec software responds to operating system accessibility settings.
Symantec products are compatible with Microsoft's accessibility utilities. In Windows
operating systems, accessibility options involving keyboard responsiveness, display
contrast, alert sounds, and mouse operation can be set through the Control Panel.
Note Accessibility features are primarily for the English version. Localized versions of
this product include support for keyboard (mouseless) navigation using accelerator
keys and mnemonic keys.
To set accessibility options
1. On the Start menu, select Settings, and then select Control Panel.
2. Select Accessibility Options.
You can also set accessibility options through the Accessibility Wizard. On the Start
menu, click Programs > Accessories. Select Accessibility, and then select
Accessibility Wizard.
Though all graphics in Symantec documentation can be read by screen readers,
setting your screen reader to ignore graphics may improve performance.
1586 Administrator’s Guide

Glossary
ADAMM (Advanced Device and Media Management)
A Backup Exec database that automates the tracking of media and storage devices and
ensures that backups are written to the appropriate media.
administration console
The user interface that allows you to run Backup Exec operations. The user interface can
be run from the media server or a remote computer.
Advanced Encryption Standard (AES)
A cipher that is used in the encryption process. Backup Exec supports 128-bit AES and
256-bit AES. The 128-bit AES provides faster backups than 256-bit AES, but provides less
protection than 256-bit AES.
agent
alert
A component that allows workstations or other computers, for example, Microsoft SQL
Server, to interact with the Backup Exec media server.
An event that usually requires some form of user interaction or acknowledgment.
alert category
A group of one or more events that occur in Backup Exec and that can generate an alert.
Examples of alert categories include Job Success, Install Warning, and Database
Maintenance Failure.
alert source
A source that can generate an alert. Alert sources include jobs, media, devices, and
systems.
alert type
allocated media
The classification of an alert that lets you determine the severity of the alert. Alert types
include Error, Warning, Information, and Attention Required.
The media that are associated with a media set and that have current append and
overwrite protection periods.
1587

append period
The length of time that data can be added to the media. The append period starts when
the first backup job is written to the media.
archive bit
A file attribute that is set whenever a file is modified. For full and incremental backups
that use archive bits, this bit is turned off after the backup completes, to indicate that the
file was backed up. If the file changes again before the next incremental or full backup, the
bit is turned on and Backup Exec backs up the file.
audit log
backup
A running history of all actions that are performed in Backup Exec. An entry into the log
is created each time an action that is configured to display in the audit log occurs.
A process where selected files on a computer drive are copied and stored on a reliable
form of media.
Backup Exec service account
A user account that is configured for the Backup Exec system services. If contains a user
name and password and provides the rights to log on as a service and act as a Backup
Exec administrator.
backup-to-disk folder
A virtual device that Backup Exec treats as any real storage device. Backup-to-disk folders
can be part of drive pools, but not cascaded drive pools.
backup method
An option that you select when you run a backup job to specify how Backup Exec sets
each file’s backup status. For example, depending on the method that you select, Backup
Exec may reset the archive bit or use modified time to determine if a file needs to be
backed up.
backup set
The data that is selected from a single resource, such as a Microsoft Exchange dataset, and
placed together on media when a backup job is run. Files selected from multiple resources
create multiple backup sets.
1588 Administrator’s Guide

ackup strategy
The procedures that you implement for backing up your network. A good backup
strategy requires minimal time to get a computer running in the event of a disaster.
baseline
The first backup job to run in a synthetic backup policy. The baseline backup runs one
time only and backs up all of the files on the selected resources. A full backup is
assembled, or synthesized, from a baseline backup and the subsequent incremental
backups that are also contained in a policy.
cascaded drive pool
The grouping of drives of the same drive type so that they appear logically as one drive.
This grouping allows backups that exceed the capacity of media in one drive to
automatically continue on the next drive that is defined in the pool.
catalog
A database that tracks the contents of media created during a backup or archive
operation. You can only restore information from fully cataloged media.
central administration server
A Backup Exec media server on which the Central Admin Server Option (CASO) is
installed. In a CASO environment, the central administration server provides centralized
administration and delegated job processing and load balancing functionality for Backup
Exec media servers in your storage environment.
centralized catalog
A catalog location in the Central Admin Server Option. All of the files in the catalog are
kept on the central administration server.
centralized restore
A process in which you can run and manage all restore operations from a central
administration server. Centralized restore is only available with the Central Admin Server
Option.
cluster
A group of two or four computers (called nodes) that are connected in a network, and run
software to allow each node to access the shared disks.
Glossary 1589

common encryption key
A type of encryption key that anyone can use to back up data using encryption and to
restore encrypted data.
custom error-handling rule
An error-handling rule that you can define for a specific error code in an error category.
When a job fails with the error code that is associated with the custom error-handling rule,
the retry options and the final job disposition are applied to the job.
custom filter
A filter that you can define to display only the information that you specify in the Job
Monitor.
database server
The server on which the shared Advanced Device and Media Management (ADAMM)
database and the shared catalog database reside when the Backup Exec SAN Shared
Storage Option is installed.
Differential - Back up changed files since last full
A backup method that includes all files that have been changed (based on archive bit)
since the last full or incremental backup. This method does not affect any media rotation
scheme because the archive bit is not reset.
Differential - Using modified time
A backup method that includes all files since the last full backup using the files’ last
modified date and time stamp.
decryption
The process of converting data from an encrypted format to a format that can be read.
device
device pool
A robotic library drive, a stand-alone drive, a backup-to-disk folder, a backup-to-disk
device, or a cascaded drive pool in Backup Exec.
A group of devices that can be used for Backup Exec operations. Jobs assigned to the
device pool are run on the first available device.
1590 Administrator’s Guide

distributed catalog
A catalog location in the Central Admin Server Option. Image files in the catalog are
distributed to the central administration server from every managed media server. These
distributed files are small because they do not contain the entire catalog. They contain
only information about the backup set. The history files, which contain detailed
information about the backup set, remain on the managed media server.
Duplicate Backup Sets template
A template that allows you to use a multi-stage backup strategy for backing up data to
disk and then copying it to tape.
encryption
The conversion of data into a format that cannot be read without special knowledge.
error-handling rule
A default or custom rule that sets retry options and the final job disposition for failed or
canceled jobs. Retry options let you specify how often to retry a job if it fails and the time
to wait between retry attempts. The final job disposition lets you place the job on hold
until you can fix the error.
event
failover
An action that occurs during a Backup Exec operation; for example, job cancellation.
An event that occurs when a node in a cluster becomes unavailable and cluster resources
migrate to an available node.
Full - Back Up Files - Using modified time
A backup method that includes all of the files selected for backup and allows the use of
incrementals and differentials using the modified date and time stamp.
Full - Back Up Files - Using archive bit (reset archive bit)
A backup method that backs up all of the files selected for backup and resets the archive
bit to indicate that the files have been backed up.
Full - Back Up Files - Copy the files
A backup method that includes all selected data. It does not affect any media rotation
scheme because the archive bit is not reset.
Glossary 1591

Full - Back Up Files - Archive the files (delete files after successful copy)
A backup method that backs up the selected data, verifies the media, and then deletes the
data from the volume. For data to be deleted, rights to delete a file must be granted;
otherwise data will be backed up, but not deleted.
imported media
The media that are created by a product other than this installation of Backup Exec, but
are in storage devices in the Backup Exec environment.
Incremental - Back up changed files since last full or incremental - Using archive bit (reset archive
bit)
A backup method that backs up only the files that have changed (based on the archive bit)
since the last full or incremental backup. It resets the archive bit to indicate that the files
have been backed up
Incremental - Back up changed files since last full or incremental - Using modified time
A backup method that backs up all files that have changed since the last full or
incremental backup using the files’ last modified date and time stamp.
job
An operation that has been scheduled for processing by the media server. For example, if
you make selections and submit a backup based on those selections, you have created a
backup job. Jobs contain source or destination information, settings, and a schedule.
Types of jobs include backup, restore, media rotation, resource discovery, report, test run,
and utility jobs.
job delegation
A process by which jobs are distributed by a central administration server to available
storage devices on managed media server. Job delegation is only available with the
Central Admin Server Option.
job history
job log
A report of what happened during the processing of the job (statistics, errors, and so on).
A log that contains the results of a job. It is created when the job runs. You can review the
job log for job errors and job details.
1592 Administrator’s Guide

junction point
A physical location on a hard disk that points to data at another location on the hard disk
or on another storage device.
Also called mount point.
load balancing
A feature in Backup Exec that automatically distributes jobs among any available storage
devices.
Also a feature of the Backup Exec Central Admin Server Option in which jobs are
automatically distributed from a central administration server to multiple managed
media servers for processing among the various storage devices.
local device
A disk or tape drive that is connected to a server. It is only available to the server to which
it is attached.
logon account
An account that stores the credentials of a Windows user account and that enables Backup
Exec to manage user names and passwords. It can be used to browse resources or process
jobs.
managed media server
A media server that is managed by a central administration server. Managed media
servers are responsible for the actual processing of backup and restore jobs in a Central
Admin Server Option environment. Managed media servers are only available with the
Backup Exec Central Admin Server Option.
media ID
A unique internal label that Backup Exec assigns to each media used in Backup Exec. The
ID keeps statistics for each media. The media ID cannot be erased or changed.
media label
A label used to identify media. Backup Exec can assign the label automatically or you can
specify a label prefix and number to be assigned for a type of media. If the media was first
used in a library with a bar code reader, the media label will already have a bar code label.
media overwrite protection level
A global setting in Backup Exec that lets you specify whether to overwrite scratch,
imported, or allocated media regardless of the media’s overwrite protection period.
Glossary 1593

media rotation
A strategy that determines when media can be reused, or rotated back into use, by Backup
Exec. Common examples of a media rotation strategy are Son, Father/Son, and
Grandfather/Father/Son.
media server
The computer on which Backup Exec is installed and where the Backup Exec services are
running.
media server pool
A feature of the Backup Exec Central Admin Server Option that lets you group managed
media servers in a pool to which you can restrict backup jobs.
media set
A set of rules that apply to media that are associated with a media set. These rules specify
append periods, overwrite protection periods, and vaulting periods.
media vault
A user-defined logical representation of the actual physical location of media, such as a
special media room, a scratch bin, or an offsite location.
mount point
The directory under which a file system is accessible after being mounted.
Also called junction point.
node
A server in a cluster environment. A node can also be a selection in a tree view on the
administration console.
offhost backup
A feature of the Backup Exec Advanced Disk-based Backup Option that enables the
backup operation to be processed on a Backup Exec media server instead of on the remote
computer, or host computer. Moving the backup from the remote computer to a media
server enables better backup performance and frees the remote computer as well.
offline media location
A node on the Media view that lists media that are onsite but are not in drives, slots, or
media vaults. Media are automatically moved to the offline media location if you use
Backup Exec to remove media from a device or slot.
1594 Administrator’s Guide

online media location
A node on the Media view that lists media that reside in a storage device, robotic library
slot, or backup-to-disk folder.
overwrite protection period
The length of time that data is retained on a specific media before being overwritten
(unless the media is erased, formatted, moved to scratch media, or if the media overwrite
protection level is set to None). The overwrite protection period is measured from the last
time data was appended to the media.
partition
A grouping of slots in a robotic library for use in Backup Exec operations.
pass phrase
A combination of letters, numbers, and special characters that are used to create
encryption keys. A pass phrase is similar to a password, but is longer and provides a
stronger level of data protection.
policy
A method for managing backup jobs and strategies. Policies contain templates, which
provide settings for jobs.
protected server
Any computer on the network that is being backed up by Backup Exec, including Backup
Exec media servers.
recyclable media
Media that is assigned to a media set but has expired data overwrite protection periods.
remote administrator
The Backup Exec user interface (Administration Console) that is run on remote
computers.
remote agent
A Backup Exec system service that runs on Microsoft Windows computers or NetWare
remote servers and workstations and allows remote backup and restore of those
computers and provides increased backup throughput.
Glossary 1595

eplicated catalog
A catalog location in the Central Admin Server Option. All of the files in the catalog are
replicated from the managed media server to the central administration server.
resource
Data files and databases, such as Windows shares and Microsoft SQL databases, that can
be selected for backup.
resource discovery
A Backup Exec operation that allows detection of new backup resources within a
Windows domain.
restore
A process by which data that has been backed up to media is returned to disk.
restricted encryption key
A type of encryption key that anyone can use to back up data using encryption. Only the
key owner or a user with knowledge of the pass phrase can restore data that was
encrypted with a restricted encryption key.
retired media
Media that has been taken out of service, usually because of an excessive number of
errors. Media that is retired is available for restore jobs but not for backup jobs. Media
must be retired before it can be deleted. If you want to use media that has been deleted,
Backup Exec will recognize it as imported media. It must be cataloged before you can
restore from it.
robotic library
A high-capacity data storage system for storing, retrieving, reading, and writing multiple
magnetic tape cartridges. It contains storage racks for holding the cartridges and a robotic
mechanism for moving the cartridge to the drive or drives.
scratch media
Media that are not associated with a media set and that can be overwritten. Scratch media
includes new or blank media, erased media, and media moved from another group.
selection list
The data selected to be backed up or restored. Selection lists can be save and used for
multiple jobs.
1596 Administrator’s Guide

shared device
A disk or tape drive that can be accessed by multiple servers.
silent mode installation
The process of installing Backup Exec from the command line using the setup.exe
program on the Backup Exec installation CD.
snapshot
A consistent point-in-time view of a volume that is used as the reference point for the
backup operation. After a snapshot is created, the primary data can continue being
modified without affecting the backup operation.
synthetic backup
A feature of the Advanced Disk-based Backup Option that enables a full backup to be
assembled, or synthesized, from a baseline and subsequent incremental backups.
template
A required element of a policy that defines how and when Backup Exec processes a job.
Templates specify the device, settings, and schedule options to be used for the job. Each
policy must contain at least one template.
template rule
A method of setting up relationships between templates in a policy.
true image restore
A feature of the Advanced Disk-based Backup Option that enables Backup Exec to restore
the contents of directories to what they were at the time of any full or incremental backup.
Restore selections are made from a view of the directories as they existed at the time of the
particular backup. Files that were deleted before the time of the backup are not restored.
In true image restore, only the correct versions of files are restored from the appropriate
full or incremental backups that contain them. Previous versions are not unnecessarily
restored and then overwritten
Unique Message Identifier (UMI)
A unique code that is associated with an error reported in the job log. These codes contain
hyperlinks that you can click to go to the Symantec Software Support Services web site
and access technical notes and troubleshooting steps that are related to a specific error.
Glossary 1597

wizard
A series of instructional panels that guide you through the steps needed to accomplish a
task, such as creating a backup job.
Working Set - Back up files - Changed today
A backup method that backs up all files that were created or modified today.
Working Set - Back up files - Last accessed in (x) days
A backup methods that backs up data that has been accessed in a specified number of
days. If you select this backup method, you can then indicate the number of days in the
Files accessed in x days field.
1598 Administrator’s Guide

Index
A
accessibility
dialog boxes, 1581
keyboard navigation, 1580
keyboard shortcuts, 1582
overview, 1579
settings, 1586
active alerts
defined, 528
responding to, 535
viewing, 528
Active Alerts by Media Server Report, 609
Active Alerts report, 608
Active Directory, 982
for Automated User Assignments, 1063
for connection policies, 1190
Active Directory Recovery Agent
about restoring individual objects, 905
about the, 903
installing, 903
passwords, 906
recreating purged objects, 908
requirements, 901
tombstones, 905
Active Directory, backing up in
Exchange, 1228
Active File Exclusion
Exchange data, 1228, 1319
active jobs
canceling, 446
removing hold, 446
viewing, 442
viewing properties, 442
ADAMM, defined, 1587
add users in DLO, CSV file to, 1076
administration console
defined, 1587
Desktop Agent Console, 1165
Desktop and Laptop Option (DLO), 1012
overview, 133
role in backup process, 69
administrator accounts
creating, 996
Advanced Device and Media Management
(ADAMM)
database overview, 1547
device management overview, 167
Devices view, 169
Advanced Disk-based Backup Option
baseline, setting, 866
best practices for offhost backup, 891
host computer, defined, 887
offhost backup overview, 887
offhost backup requirements, 889
offhost backup snapshot provider,
choosing, 893
offhost backup, List Snapshot Providers
option, 895
offhost backup, single volume snap,
choosing, 894
synthetic backup policy, example, 873
synthetic backup template rules, 878
synthetic backup template rules,
example, 873
synthetic backup template,
requirements, 869
synthetic backup, creating, 873
synthetic backup, encryption in, 875
synthetic backup, option to enable, 871
transportable snapshots, defined, 888
true image restore, creating, 883
true image restore, option to
enable, 871
true image restore, overview, 880
true image restore, requirements, 882
VSFW FlashSnap option, using with
offhost backup, 890
Advanced Encryption Standard (AES),
defined, 1587
Advanced File Selection options
selecting files, 325
Advanced Open File Option
cache file location, 856
cache file size, setting, 860
changing default settings for Symantec
VSP, 856
databases, backing up, 845
encrypted files, backing up, 847
installing using the command line, 849
minimum quiet time, setting, 861
1599

overview, 843
requirements, 847
Snap Start for VSFW volumes, 855
snapshot providers, 846
Symantec Volume Snapshot
Provider, 852
using with Exchange Agent, 1232
wizard, 858
Advanced options
for backup, 362
Agent for Microsoft SharePoint Portal
Server
about, 1299
about restoring a SharePoint Server or
Workspace, 1291
adding a server farm, 1300
backing up SharePoint Portal Server
2003 resources, 1303
disaster recovery, 1297
installing, 1288
overview, 1287
redirecting a restore for SharePoint
Portal Server 2003, 1308
redirecting restore jobs, 1294
selecting SharePoint Portal Server 2003
resources for backup, 1299
setting default options, 1311
system requirements, 1288
agent, defined, 1587
Agents, Backup Exec
See also Exchange Server Agent, Lotus
Domino Agent, NetWare Agent,
Oracle Agent, SAP Agent, Remote
Agent, SharePoint Agent, SQL Server
Agent
list of agents with descriptions, 62
See also Desktop and Laptop Option
upgrading on remote computers, 130
alert
notifications, 981
alert category, defined, 1587
alert history
defined, 528
viewing, 528
Alert History report, 610
alert history, defined, 1109
alert notification, printers, 558, 560, 1127,
1128
alert source, defined, 1587
alerts
alert types, 527
assigning recipients, 564
clearing recipients, 564
configuring default options, 140, 141,
142
defined, 527
defined for DLO, 1106
deleting in DLO, 1111
displaying in DLO, 1109
filters, 528, 529
grooming, 1105
handling with SAP Agent, 1445
managing in DLO, 1110
monitoring in DLO, 1105
notification methods, 1112
properties, 532
responding to, 535
viewing, 528
viewing job log, 534
views, 528
all media, defined, 257
allocated media
defined, 258, 1587
overwriting, 274
AOFO See Advanced Open File Option
append period
defined, 260, 265, 1588
setting for media set, 265
append to media option, 355
archive bit, defined, 312, 1588
archive logging
Lotus Domino, 1320
recovery of Lotus Domino, 1330
archiving
freeing disk space, 380
NTFS and VFAT file systems, 380
using disk grooming, 380
ARCserve media, restoring data from, 507
ASR files, in IDR
defined, 1505
ASR See Automated System Recovery
audit log
viewing, 161
Audit Log report, 612
audit log, defined, 1588
AUTOEXEC.NCF file, Remote Agent for
NetWare Servers, 926
auto-inventory media after import job
1600 Administrator’s Guide

B
completes, 250
Automated System Recovery, 658
Automated User Assignment, 1060
creating, 1060
defined, 977
deleting, 1065
modifying, 1063
priority, changing, 1064
properties, viewing, 1064
using Active Directory, 1063
automatic exclusion of files during volume
level backups, 1319, 1352
automatic updates, scheduling, 126
availability windows, 334
back up on log on/off option in DLO, 1082
backing up
desktop data, 1168
files and directories by following
junction points, 362
Microsoft clusters
database files, 728
local disks, 727
shared disks, 727
Windows 2000 and Windows Server
2003, 726
NDMP resources, 1574
Outlook PST files, 1179
remote storage, 363
VERITAS clusters
database files, 744
local disks, 743
shared disks, 743
Windows 2000 and Windows Server
2003, 742
BACKINT
handling alerts, 1445
overview, 1444
using with CCMS console, 1450
backup
defined, 1588
overview, 345
Backup Access Control Lists, 1575, 1578
Backup Exec
accessibility, 1579
dialog boxes, 1581
keyboard shortcuts, 1582
installing
command line installation, 111
silent mode installation, 111
uninstalling, 124
upgrading, 129
using Repair option, 122
options, 62
overview
how it works, 69
new features, 49
system requirements, 79
repairing, 122
starting after installing Library
Expansion Option, 1542
System Summary
viewing, 465
upgrading
options on remote computers, 130
overview, 129
Backup Exec 8.x and 9.x Agent for Unix
advertise to media server, 697
agent.cfg file, 696
back up symbolic links, 698
loading, 698
system requirements, 692
Backup Exec 8.x and 9.x Agent for Unix
commands
exclude directories/files, 698
identify exported paths, 697
include remote file systems, 697
password-protect published path, 697
password-protect workstation, 696
preserve ctime, 698
publish directory tree, 697
write-protect published path, 697
Backup Exec Environment Check, 72
Backup Exec for Windows Servers,
described, 47
Backup Exec Retrieve
description, 1006
retrieving files, 1204
using with DLO, 1006
Backup Exec Server in SAN, 1547
Backup Exec services
account, defined, 1588
Backup Exec Services Manager dialog
box, 123
stopping and starting, 123
backup folder
creating more disk space, 354
Index 1601

ackup folder, defined, 1588
backup job
Advanced options, 362
choices for creating, 345
copying to another server, 440
creating manually, 349
creating using the wizard, 347
Device and Media options, 354
Microsoft Data Protection Manager
selections, 1490
pre/post commands, 366
scheduling, 368
selecting devices and data, 315
Selections options, 350
tasks to do before, 346
Backup Job Properties dialog box
SQL Agent, 1347
Backup Job Success Rate, 613
backup methods
defined, 1588
selecting, 358
setting default, 389
using modified time, 313
backup network
changing for a backup job, 403
configuring, 400
overview, 398
setting up, 400
backup options
backing up data in remote storage, 363
contents of mounted local drives, 362
Backup Selection dialog box, 1172
backup selections
adding, 1035
macros in, 1044
backup selections, changing order, 351
Backup Set Details by Resource report, 615
backup set, defined, 1588
Backup Sets by Media Set report, 616
Backup Size by Resource report, 617
backup strategies
See also names of individual agents
choosing resources to back up, 307
defined, 305, 1589
frequency of backups, 306
increasing throughput with Remote
Agent for Windows Systems, 913
length of data retention, 307
multiple resources per job, 308
one job per resource, 307
protecting against viruses, 307
backup types
archive, 308
copy, 308
daily, 309
differential, 309
full, 308
incremental, 309
working set, 309
Backup Wizard, launching, 347
backups option, Configure desktop and
laptop, 1012
backup-to-disk file
defined, 218
deleting, 233
recreating a deleted file, 234
renaming, 232
backup-to-disk folder
advanced options, 225
auto detect settings, 225
Backup-to-disk Wizard, 221
buffered reads, 226
changing the path, 229
concurrent jobs, 224
concurrent operations, 218
creating, 222
defined, 218
deleting, 230
disk space reserve, 225
maximum number of backup sets, 223
maximum size, 223
maximum size, allocate at, 224
overview, 218
pausing and resuming, 232
recreating, 231
renaming, 229
requirements, 219
requirements for removable, 220
set global defaults, 226
sharing, 228
bandwidth settings, DLO, for users in, 1021
bar code labels
and media ID, 279
default, 280
mixed media libraries, 281
overview, 280
robotic library support, 280
bar code rules
1602 Administrator’s Guide

C
changing, 282
deleting, 282
setting up, 281
baseline, defined, 1589
baseline, setting for synthetic backup, 866
BE Diagnostics, running from server
properties, 188
bediag.fax file, 935
bediag.nlm utility, saving configuration
information, 935
besernum.xml file, importing license keys
with, 82, 86, 89
BESTART command, to start Remote Agent
for NetWare Servers, 926
BESTOP command, to stop Remote Agent
for NetWare Servers, 927
BEUtility.exe utility
Microsoft clusters, using in, 714
biparam.ini
options, 1447
overview, 1440
specifying Backup Exec
parameters, 1447
BKUPEXECDLO MSDE database
instance, 1136
blackout window, setting, 1086
block size, setting for devices, 199
Boot managers, restoring in IDR, 1522
bootable media for IDR
CD image, creating, 1512
comparing types, 1505
tape image, creating, 1514
types of media, 1504
BRRESTORE, restoring data with, 1451
BRTOOLS, using with SAP Agent, 1450
buffer count, setting for devices, 200
buffer size, setting for devices, 199
build and version information,
displaying, 678
byte count, incorrect, 672
cache file location, for AOFO, 856
cache file size, setting for AOFO, 860
calendar
custom filters, 472
cascaded drive pools
adding drives, 184
creating, 183
defined, 167, 1589
deleting, 186
deleting drives, 185
overview, 183
properties, 187
renaming, 187
requirements for using, 183
using hardware compression in, 183
CASO
alerts, configuring, 812
Backup Exec Utility, running, 802
catalog location
changing, 816
displayed, 833
overview, 814
central administration server
installing, 785
pausing storage devices from, 837
port number
SQL 2000 or 2005
instance, 794
SQL Express instance, 792
setting for a managed media
server, 801
centralized catalog, overview, 815
centralized restore
multiple storage devices, 828
overview, 827
communication status, none, 810
communications, disabling and
enabling, 837
configuring, 804
device and media data, location of, 784
distributed catalog, overview, 815
duplicate backup data job
requirements, 826
features in, 782
job delegation, 779, 818
job history options, setting, 810
managed media server
alias, creating for SQL 2000 or
2005, 794
alias, creating for SQL Express, 793
device and media data, choosing the
location of, 790
firewall, installing across, 792
installing, 786
installing for SAN Shared Storage
Index 1603

Option, 789
job history options, 810
job log options, 810
pausing and unpausing, 836
stalled, 810
status messages, 833
viewing properties, 840
media server pool
advantages of, 819
apply settings to all servers in a
pool, 825
deleting, 822
filter data for, 819
overview, 818
removing a managed media
server, 823
renaming, 822
statistics, viewing, 824
media server, changing to a managed
media server, 801
monitor jobs on local managed media
server, 807
network interface cards, using any
available, 814
network traffic, reducing, 805
notification, configuring, 813
overview, 779
recovered jobs, 809, 810
recovering failed jobs, 812, 835
replicated catalog, overview, 815
requirements, 783
selection list, restrict backup of, 820
stopping and starting Backup Exec
services, 838
synthetic backup job requirements, 826
time differences between servers, 807
upgrading, 795
catalog
defined, 1589
levels, 486
media in drive, 284
searching, 513
catalog database, in SAN Shared Storage
Option, 1561
catalog operation errors
DLT tape drive hangs, 670
CCMS console, using with SAP Agent, 1450
Cell phone
notification, 543
central administration server,
defined, 1589
centralized catalog
defined, 1589
centralized catalog, in CASO, 815
centralized restore
best practices, 830
centralized restore, defined, 1589
CHECKCATALOG utility, 1343
CHECKDB utility, 1343
CHECKFILEGROUP utility, 1343
checkpoint restart on Microsoft cluster
failover
enabling or disabling, 711
overview, 709
circular logging
Exchange Agent, reviewing in, 1229
Lotus Domino, 1320
recovery of Lotus Domino server, 1332
cleaning jobs, submitting for robotic
libraries, 248
Cleaning tab for device properties, 203
Clear default encryption key, 412
clone CD image
creating, 120
overview, 119
clrest command, 733
Cluster Failover error-handling rule, 475,
479
cluster, defined, 1589
clusters
backing up SAP database, 1456
disaster recovery
entire cluster manually, 749
nodes using IDR, 747
using IDR to prepare, 747
installation
Backup Exec on a VERITAS cluster
server, 737
Microsoft
adding or removing a failover
node, 712
all drives pool, 708
backing up shared disks, 727
BEUtility, 714
changing the order in which nodes
fail over, 712
configurations, 715, 716, 717, 718,
720
1604 Administrator’s Guide

creating drive pools, 708
database files, 728
database server, designating new in
SAN SSO, 714
disaster recovery, 752, 753, 755
disaster recovery of Backup Exec on
a cluster using IDR, 749
failover restart, 702
installation, 704, 706
local disks, 727
Open File Option, and using, 706
overview, 725
Remote Agent, installing, 704
restoring, 729, 730, 732
system state, backing up, 727
uninstalling Backup Exec, 707
virtual servers, backing up, 728
Windows 2000 and Windows Server
2003, 726
restoring
specifying a new drive letter for the
Microsoft cluster quorum
disk, 734
SAP Agent, 1456
size, 673
troubleshooting, 755
using with Backup Exec, 701
VERITAS
backing up, 742, 743, 744
disaster recovery, 746, 754
overview, 741
Remote Agent, installing, 737
restoring Windows 2000 and
Windows 2003, 745
system state, backing up, 743
virtual servers, backing up, 744
clusters, Desktop and Laptop Option, 1136
combination SAP database server/media
server recovery, 1461
command line installation of Backup
Exec, 111
command line interface, 1139
-assignSL, 1140
-changeserver, 1143
-emergencyrestore, 1152
-enableuser, 1141
-keytest, 1144
-listprofile, 1145
-listsl, 1146
-listuser, 1147
-logfile, 1148
remote server options, 1139
-setrecoverypwd, 1152
syntax, 1139
-update, 1149
commands See also names of individual
commands
common encryption key, defined, 1590
common encryption keys, 408
completed jobs, job log overview, 461
compression
delta file transfer, 1042, 1048, 1176
DLO backup selections, setting, 1042,
1176
enable hardware compression
option, 199
in cascaded drive pools, 183
setting backup defaults, 392
using with encryption, 409
configuration settings
copying to another server, 156
Configuration Settings report, 618
Configuration tab for device
properties, 199
Configuration tab for robotic library, 212
configuration wizard for DLO, 1019
Configure Alerts dialog box, 1109
Configure desktop and laptop backups
option, 1012
configuring
devices, 198
holidays, 376
NDMP devices, 1572
robotic library, 208
connection based policies, 981
configuring, 1031, 1188
using Active Directory, 1190
consistency check options
Exchange Agent, 1250
SQL Agent, 1341
continuing Exchange backup if consistency
check fails, 1250
Continuous backup option for Exchange
data, 1247
continuous protection
Exchange data, best practices, 1239
for Exchange data, overview, 1235
job statuses in Exchange, 1236
Index 1605

D
requirements for Exchange, 1221
copy jobs, selection lists, and policies, 440
creating more disk space for backup
folder, 354
current jobs
custom filters, 468
custom error-handling rule, defined, 1590
custom filter, defined, 1590
custom reports
copying, 599
creating, 584
deleting, 600
editing, 600
filter criteria and expressions, 583
graph options, 593
grouping fields, 591
overview, 583
previewing, 599
setting filters, 586
sorting fields, 592
daily backups, defined, 309
Daily Network Device Utilization
report, 620
damaged media, removing, 296
database, 984
database files, backing up in a Microsoft
cluster, 728
database files, backing up in a VERITAS
cluster, 744
database instance, BKUPEXECDLO
MSDE, 1136
database maintenance
configuring, 163
overview, 162
database server
defined, 1547, 1590
in Microsoft clusters, 714
Date Modified tab, 515
DB2 Agent
archive logging methods. using with
Backup Exec, 1476
archive logs template name,
configuring for DB2 instance, 1467
authentication, configuring on DB2
instance, 1467
backing up, 1472
credentials, updating for instance, 1466
database access, configuring on media
server, 1469, 1471, 1472
db2.conf configuration file,
installing, 1475
db2.conf file, creating, 1478
db2.conf file, overview, 1477
DBA-initiated job settings,
configuring, 1480
DBA-initiated jobs, about, 1475
DBA-initiated jobs, job template name
for, 1466
defaults for backup and restore, 1482
example script, for command line
processor, 1476
features, 1463
installation and configuration, 1464
multiple data streams, specifying, 1474
overview, 1463
port, configuring for DB2
operations, 1469
redirected restore, 1486
restoring, 1484
troubleshooting, 1488
user exit db2uext2.exe, installed, 1475
user exit method, configuring for, 1465
vendor library db2sqluv.dll,
installed, 1475
vendor library method, configuring
for, 1465
DBA-initiated job settings
configuring for SAP Agent, 1448
for SAP, 1448
decryption, defined, 1590
default options
backup and restore for Exchange
Agent, 1240
IDR, setting, 1507
NDMP backup and restore, 1577
overview, 70
restore, 520
setting, 138
setting for backup jobs, 389
SQL Agent, backup and restore, 1383
default preferred configuration settings for
devices, 200
default settings
changing, 1000
delegation
maintenance server, 1050
1606 Administrator’s Guide

deleting
Automated User Assignment, 1065
device pools, 180
devices from pools, 180
DLO desktop computer, 1085
media, 296
revisions in DLO, 1043
Storage Location in DLO, 1059
user entry from DLO, 1078
vault, 290
delta file transfer, 980, 1042, 1048, 1176
Desktop, 1077
Desktop Agent
advanced view option, 1172
backing up data, 1168
Backup Selection dialog box, 1172
backup selections
compression, setting, 1176
modifying, 1170
overview, 1168
console, 1165
customizing installation, 989
Desktop User Data Folder,
moving, 1187
filter options, History view, 1206
glossary, 1216
History view, 1205
include/exclude, 1173
install, 989
install set default location, 1159
installing, 988
log files, overview, 1205
menu bar, described, 1167
overview, 1157
Reset accounts option, 1163
reset dialogs option, 1163
Restore dialog box, 1201
restoring files, 1199
revision control tab, 1175
revisions, deleting automatically, 1176
schedule, customized, 1082, 1183
scheduling backup jobs, 1183
see also Desktop and Laptop Option
(DLO)
standard view option, 1170
Status view, 1195
storage limits for user data, 1185
synchronization
create new sets, 1192
delete synchronized folder, 1193
Synchronized Selections view, 1190
tasks bar, described, 1167
views menu, described, 1167
Desktop Agent Users, managing, 1074
desktop and laptop backups option,
Configure, 1012
Desktop and Laptop Option (DLO), 977
see also Desktop Agent
access, disabling/enabling, 1077
adding user, 1075
administration console, 1012
administrators, creating, 996
alerts
categories, defined, 1106
Configure Alerts dialog box, 1109
deleting, 1111
displaying, 1109
managing, 1110
monitoring, 1105
Automated User Assignment
creating, 1061
defined, 977
deleting, 1065
modifying, 1063
priority, changing, 1064
properties, viewing, 1064
backup selection
adding, 1033
deleting, 1046
modifying, 1046
BEUtility.exe utility, using, 1136
Computer History pane, 1098
Configuration Wizard, 1019
configuring, 1019
deleting entry from DLO database, 1085
encryption, setting for backup
selection, 1042, 1176
filter options, History view, 1100
glossary, 1216
History view, 1098
import multiple users in CSV file, 1076
include/exclude, 1038, 1173
installing, 987
Job History pane, 1099
Move priority down option, 1064
Move priority up option, 1064
MSDE database instance,
maintaining, 1136
Index 1607

overview, 977
Profile
creating, 1020
defined, 977
edit schedule, 1028
log on/off option, 1082
logging options, 1029, 1083
Schedule tab, 1027, 1082
properties, changing user, 1077
removing user, 1078
reset dialogs and accounts, 1163
restoring, 1088
revisions
defined, 1039
deleting automatically, 1043
setting number to keep in
DLO, 1040, 1175
Search history log file option, 1104
storage limits for user data, 1021
Storage Location
defined, 977
deleting, 1059
moving users, 1079
summary status, 1017
user bandwidth settings, 1021
User Data Folder, 1053
User Properties dialog box, 1077
View history log file option, 1101
viewing users, 1081
Desktop and Laptop Option,
clustering, 1136
device
allocation in a shared storage
environment, 1551
selecting for backup job, 354
device and media data, location of in
CASO, 784
Device and Media options for backup
job, 354
device management, 167
device operations
See also robotic library
cataloging media, 284
ejecting media, 247
Enable Hardware Compression
Option, 199
erasing media (quick or long), 240
formatting media, 244
inventorying a drive, 238
labeling media, 246
overview of utility jobs, 237
retensioning a tape, 243
using with SAN Shared Storage
Option, 1554
Device pool properties dialog box, 182
device pool, defined, 1590
device pools
adding devices, 178
creating, 177
defined, 167
deleting, 180
deleting devices, 180
overview, 176
prioritizing devices, 179
properties, 182
renaming, 182
using the default device pool, 177
viewing properties, 182
device properties
Configuration tab, 198
General tab, 196
Media Types tab, 205
SCSI Information tab, 201
viewing, 195
Device Summary Report, 1552
Device Summary report, 620
Device Usage by Policy report, 622
device, defined, 1590
devices
block size, 199
buffer count, 200
buffer size, 199
configuring, 198
default settings, 200
high water count, 200
Hot-swappable Device Wizard, 173
iSCSI-attached, adding, 173
pausing, resuming, renaming, 175
SCSI information, 201
specifying media types for, 205
statistics on usage, 202
statistics since cleaning, 203
Symantec Device Driver Installation
Wizard, 174
troubleshooting, 1566
USB tape devices, reconnecting, 173
viewing, 168
viewing with Library Expansion
1608 Administrator’s Guide

Option, 1544
Devices view, 169
Dfs See Distributed file system
dialog box, Move User, 1079
dialog boxes, overview, 136
differential - Back up changed files since
last full
defined, 1590
differential - Using modified time
defined, 1590
differential backups
advantages and disadvantages, 311
defined, 309
disable device for Backup Exec, 197, 211,
222
Disable file history, 1575, 1578
disaster preparation
Disaster Preparation Plan (DPP), 654
emergency repair disk, 657
Exchange 2000 and 2003, 1280
hardware protection, 654
Lotus Domino Agent, 1328
off-site storage, 654
overview, 653
SQL 2000, 1388
disaster recovery
See also names of individual agents
clusters
Backup Exec on a Microsoft cluster
using IDR, 749
entire cluster manually, 749
nodes using IDR, 747
using IDR to prepare, 747
data protected by Backup Exec
agents, 658
different types of computers,
overview, 658
Exchange 2000 and 2003, 1281
Exchange 5.5, 1283
local Windows 2000 computers
(non-authoritative), 659
Lotus Domino Agent, 1329
manual recovery of Windows
system, 658
Microsoft clusters
Backup Exec, 755
data files, 752
shared disks, 753
overview, 658
performing using SAP Agent, 1459
Remote Agent for NetWare Servers, 936
remote Windows 2000 computers
(non-authoritative), 663
VERITAS clusters
overview, 746
shared disks, 754
disaster recovery alternate data path, in
IDR, 1508
disaster recovery data path, in IDR, 1507
disaster recovery file (*.dr file) in IDR
defined, 1505
setting locations for, 1507
Disaster Recovery Wizard
requirements, 1525
running, 1525
disk grooming, using for archive job, 380
disk space reserve, backup-to-disk folder
option, 225
distributed catalog
defined, 1591
distributed catalog, in CASO, 815
Distributed file system (Dfs)
backing up, 324
restoring, 505
DLO Administration Console, restoring
from, 1088
DLO see also Desktop and Laptop Option
(DLO), Desktop Agent
DLT tape, drive hangs when cataloging, 670
Domain Controller, using redirected
restore to install from media, 518
domains, host and target, defined, 76
DPM Agent
database selections for restore
jobs, 1495
overview, 1489
requirements, 1489
selections for backup jobs, 1490
selections for restore jobs, 1494
server selections for restore jobs, 1495
shadow copy data selections for restore
jobs, 1496
DPP See also Disaster Preparation Plan
drive pools
See also cascaded drive pools
creating in a Microsoft cluster, 708
default for SAN Shared Storage
Option, 1553
Index 1609

E
SAN Shared Storage Option, 1551
drivers
download latest, 669
drives
using exclusively with Backup Exec, 236
duplicate backup data template
defined, 1591
duplicate backup sets template
overview, 435
duplicate backup sets templates
adding to a policy, 436
duplicating backup data, 381
Dynamic Host Configuration Protocol
(DHCP), 690
editions of Backup Exec, listed and
described, 47
See also names of individual editions
eject media
after job completes, 356
from a drive, 247
e-mail
configuring MAPI notification, 545,
1114
configuring SMTP notification, 543,
1113
configuring VIM notification, 546, 1115
emergency repair disk, creating, 657
Enable Direct Access Recovery, 1577, 1578
enabling
bar code rules, 212
device for Backup Exec option, 197, 211,
222
hardware compression, 199
Removable Storage (RSM), 213
robotic library initialization on
startup, 212
encrypted files, backing up with AOFO, 847
encrypting SAP data, 1444
encryption, 1090, 1191, 1212
encryption keys
128-bit AES, 408
256-bit AES, 408
common, 408
creating, 410
deleting, 413
encryption types, 408
managing, 409
overview, 407
pass phrases, 408
removing the default status, 412
restoring encrypted data, 414
restricted, 408
selecting for a backup job, 411
setting a default, 411
using with compression, 409
encryption, backup selections, in
DLO, 1042, 1176
encryption, defined, 1591
Environment Check, running for Backup
Exec, 72
erase media operation, quick or long, 240
error codes, Unique Message Identifier,
viewing, 459
error-handling rule, defined, 1591
error-handling rules
Cluster Failover rule, 475, 479
configuring, 475
custom rules, defined, 474
default rules, defined, 474
overview, 474
Recovered Jobs custom rule, 475
Evaluation version, installing Backup
Exec, 82, 86, 89
Event Logs report, 624
Event Recipients report, 625
event, defined, 1591
example policies, 419
Exchange 5.5, restoring
defaults, 1243
redirecting database restores, 1274
Exchange Agent
Active Directory, backing up, 1228
automatic exclusion of files during
volume level backups, 1228
backing up, recommended
selections, 1227
backup methods, 1241, 1247
best practices, 1223
change password when recreating
mailboxes, 1244
circular logging, reviewing, 1229
Continuous backup option, 1247
continuous protection, best
practices, 1239
continuous protection, overview, 1235
continuous protection, requirements
1610 Administrator’s Guide

for, 1221
creating backup job, 1245
disaster recovery, 1281
enable the restore of individual mail
messages and folders from
Information Store backups
option, 1242, 1249
Exchange 2003 with VSS, backing
up, 1231
Exchange 2007 in LCR/CCR
configurations, 1251
Exchange 2007 snapshot backup
method, 1232
exclude specific folders, 1253
excluding files during volume level
backups, 1228
granular restore, 1230
granular restore, requirements
for, 1221
Guide Me wizard for backup, 1249
installation, 1223
Internet Information Service (IIS)
metabase, backing up, 1227
Key Management Service (KMS),
backing up, 1227
legacy mailbox backup options, 1242,
1252
mailbox access requirements, 1224
mount database after restore
option, 1271
no loss restore option, 1269
overview, 1219
process logical volumes one at a
time, 1232
protecting Exchange using VSS, 1231
recovery point option, 1248
recovery points, overview, 1238
recreating mailboxes and user
accounts, 1268
redirecting data, 1273
redirecting mailboxes, 1275
redirecting storage groups and
databases, 1273
Redirection dialog box, 1277
requirements, 1220
resource discovery feature, using
with, 1220
restore defaults, 1240
restore from continuous protection
backups, 1263
Restore Job Properties dialog box, 1267
restore of individual items,
requirements for, 1221
restore over existing messages and
folders when restoring individual
mail messages and folders, 1268
restore public folder option for
Exchange 5.5, 1269
restore requirement, 1259
restore requirements for 5.5, 1259
restoring
commit after restore completes
option, 1271
DS/IS consistency adjuster after
restore, 1279
temporary location for log and
patch files, 1271
restoring an Exchange 2007 database to
a recovery storage group, 1261
restoring data to server, 1259
restoring Exchange 2003 and 2007 with
Recovery Storage Group, 1260
restoring individual mail messages and
folders from Information Store
backups, 1264
restoring individual public folder
messages from tape, 1266
restoring mailboxes and public folders,
overview, 1265
restoring mailboxes and user
accounts, 1268
services accounts, overview, 1220
Site Replication Services (SRS)
database, backing up, 1227
snapshot technology, and, 1231
storage groups, backing up, 1245
strategies for backing up, 1225
system state, backing up, 1227
troubleshooting snapshot and offhost
jobs, 1233
volume level backups, automatic
exclusion of files, 1228
Exchange Redirection page, 1277
Exchange Server Agent
excluding files during volume level
backups, 1319
executing a command
after backup, 366
Index 1611

F
after restore, 499
before backup, 366
before restore, 499
export media template, 424
exporting media, 251
failback, defined, 702
Failed Backup Jobs report, 625
failover
defined, 701
Microsoft
adding or removing a failover
node, 712
changing the order in which nodes
fail over, 712
restart, 702
failover, defined, 1591
farms
adding, 1300
changing the default farm name, 1302
deleting, 1302
FAT
cluster size, 673
partition, 672
father/son media rotation strategy, 302
file permissions, restoring, 500
file to add users in DLO, CSV, 1076
filegroups
backing up
SQL, 1354
displaying, 1355
restoring
SQL Agent, 1370
restoring nonprimary
SQL 2000, 1366
restoring primary
SQL 2000, 1366
filter
jobs, 465
filter criteria for reports, 583
filter expressions for reports, 583
filters
custom
calendar, 472
current jobs, 468
job history, 470
jobs, 466
History view filters, setting in Desktop
Agent, 1206
History view filters, setting in
DLO, 1100
filters for alerts, 528, 529
finding media in a location or vault, 289
firewall, installing a managed media server
across, 792
formatting media, 244
frequently asked questions about using
Backup Exec, 136
Full - Back Up Files - Archive the files
defined, 1592
Full - Back Up Files - Copy the files
defined, 1591
Full - Back Up Files - Using archive bit
(Reset Archive Bit)
defined, 1591
Full - Back Up Files - Using modified time
defined, 1591
full backups
advantages and disadvantages, 310
defined, 308
fully qualified computer name, 323
1612 Administrator’s Guide
G
H
general job defaults, setting, 144
general media properties, viewing, 298
general options
restore jobs, 492
Getting Started with Backup Exec page, 132
global excludes, 981
adding, 1065, 1066, 1067, 1069, 1070
deleting, 1065, 1066, 1067, 1069, 1070
macros, 1073
glossary for DLO, 1216
glossary of terms, 1216
grandfather media rotation strategy, 303
grooming
alerts, 1105
files, 1040
groups, configuring recipients, 560, 1128
hardware
compression in cascaded drive
pools, 183
creating profile, 656
enable hardware compression
option, 199
protection in case of disaster, 654

I
high water count, setting for devices, 200
hold jobs
job queue, 452
holding jobs that back up selection
lists, 330
host domain, defined, 76
hub
defined, 1592
IBM computers, recovering with IDR, 1524
IDR Configuration Wizard, 1505
IMG subfolders, described, 219
imported media
defined, 258, 1592
labeled by Backup Exec, 280
overwriting, 274
importing media, 249
importing templates, 426
include/exclude
Desktop Agent backup selections, 1173
DLO backup selections, 1038
Incremental - Back up changed files since
last full or incremental - Using archive
bit, defined, 1592
Incremental - Back up changed files since
last full or incremental - Using modified
time, defined, 1592
incremental backups
advantages and disadvantages, 311
defined, 309
initialize robotic library panel, 253
install
Desktop Agent
options, 989
install from media, 519
installation
silent, 989
installation parameter file
creating, 118
defined, 118
using, 118
installed updates, viewing, 128
installing
additional Backup Exec options on a
Microsoft cluster, 706
Backup Exec, 81
Backup Exec in a Microsoft cluster, 704
Backup Exec in a VERITAS cluster, 737
besernum.xml file, import license
keys, 82, 86, 89
Desktop Agent, 988
Desktop and Laptop Option, 987
Domain Controllers from media, 518
Environment Check, running
pre-install, 72
Evaluation version, 82, 86, 89
import license keys, 82, 86, 89
Library Expansion Option, 1542
locally
additional options, 85
using clone CD image, 120
methods, 71
Microsoft Data Access Components
(MDAC), 76
Microsoft SQL Server 2000 Desktop
Engine (MSDE 2000), 76
NDMP Option, 1572
Remote Administrator, 109
remotely using clone CD image, 121
SharePoint Agent, 1288
storage devices, 72
to an existing Microsoft SQL Server
2000 instance, 77
using installation program on CD, 81
using Repair option, 122
using Terminal Services, 81
Windows Management
Instrumentation performance
counter, 572
Windows Management
Instrumentation SNMP provider, 572
instance, BKUPEXECDLO MSDE
database, 1136
Intelligent Disaster Recovery (IDR), 1501
alternate data path on a remote
computer, 1508
ASR files, 1505
automated restore
performing an, 1526
boot managers, 1522
catalog entries, added to *.dr file, 1501
clusters
recovering Backup Exec on a
Microsoft Cluster, 749
recovering nodes, 747
disaster recovery file (*.dr file),
defined, 1505
Index 1613

J
encrypted backup sets, 1525
First Time Startup Configuration
Wizard, 1505
hard drive partition, altering sizes
using IDR, 1533
IBM computers, 1524
installing, 1503
Microsoft Exchange Server,
recovering, 1536
Microsoft SQL Server, recovering, 1536
Options - Set Application Defaults
dialog box, 1507
OS/2 boot manager, restoring, 1522
Recovery Wizard, running, 1525
requirements, 1502
restoring from a locally-attached media
device, 1528
restoring from a remote media
server, 1531
restoring from remote backup-to-disk
folders, 1530
Sharepoint Portal Server,
recovering, 1537
System Commander boot manager,
restoring, 1522
utility partitions, backing up, 1510
virtual devices, using in, 219
Windows Automated System Recovery
(ASR) files, 1505
Internet Information Services (IIS)
metabase, backing up, 1227
inventorying
all drives on startup, 139
all drives when Backup Exec starts, 240
drives, 238
IPv4, 400
IPv6, 400
iSCSI-attached devices, adding, 173
job delegation, defined, 1592
job delegation, in CASO, 779
Job Distribution by Device report, 626
job history
custom filters, 470
defined, 70, 1592
deleting report, 581
History view filters, setting in
DLO, 1100
saving report, 581
viewing, 456
viewing in Desktop Agent, 1205
viewing report, 580
job log
configuring default options, 462
defined, 1592
status overview, 461
job log options
CASO, setting in, 810
job monitor
views, 442
job monitor, DLO jobs, viewing, 1098
job priority
setting for cleaning jobs, 249
setting for eject job, 247
setting for erase job, 243
setting for export job, 251
setting for format job, 245
setting for import job, 250
setting for inventory job, 239
setting for label media job, 246
setting for retension job, 244
job progress indicators, displaying, 140,
141, 142
job queue
hold, 452
job status, and setting thresholds for, 480
jobs
changing priority for scheduled, 453
configuring default Lotus Domino
options, 1318
configuring default schedule, 377
configuring error-handling rules, 475
configuring new recipients, 565
configuring schedule, 368
creating from policies, 432
defined, 1592
deleting jobs created from policies, 434
deleting scheduled, 454
edit recipients, 565
filtering, 466
filters, 465
hold queue, 452
holiday scheduling, 376
Lotus Domino backup properties, 1321
managing custom filters, 466
removing hold
active jobs, 446
1614 Administrator’s Guide

K
L
scheduled jobs, 452
run report, 578
running scheduled job, 451
running scheduled test job, 454
scheduled, modifying, 448
scheduled, viewing, 448
scheduling, 368
selecting recipients for
notifications, 565
setting general defaults, 144
viewing active, 442
viewing and scheduling in a SAN, 1560
viewing completed, 455
Jobs Summary report, 627
junction point, defined, 1593
Key Management Service (KMS) database,
backing up, 1227
labeling media
creating default labels, 276
imported media label, 280
in drive, 246
renaming, 282
using bar code labels, 280
last known good menu, 655
legacy mailbox backup methods, in
Exchange, 1252
Library Expansion Option
overview, 1539
SCSI addresses for hardware, 1540
setting up hardware, 1540
library sharing, configuring server
for, 1556
license
default, 980
license information, viewing, 129
license keys
Backup Exec, adding and removing, 82,
85, 89
Remote Agent for Windows
Systems, 914
linked drives See cascaded drive pools
LiveUpdate
about, 125
running manually, 128
scheduling automatic updates, 126
load-balancing, defined, 1593
local device, defined, 1593
local media server, breaking connection
with, 109
location, media in Backup Exec, 286
lock open files for backup, 364, 394
lock robotic library panel, 252
logon account, defined, 1593
logon accounts
changing default, 154
changing for a resource being backed
up, 352
default, defined, 147
deleting, 153
editing, 151
overview, 146
replacing, 152
SQL resources, 1337
system logon account, 148
testing, 352
logon information
copying to another server, 159
Lotus Domino Agent
APIs, 1318
archive logging, 1320
backup options, 1321
circular logging, 1320
configuring default options, 1318
database backup overview, 1318
database backup requirements, 1314
disaster preparation, 1328
disaster recovery
archive logging, 1330
circular logging, 1332
of server, 1329
Microsoft Cluster Server, 1314
restoring, 1323
overview, 65, 1313
redirecting restore, 1327
requirements, 1314
restore overview, 1323
selecting for restore, 1324
selecting restore options, 1326
supported configurations, 1319
viewing databases, 1316
Lotus Notes
back up nsf files, 980, 1180
Index 1615
M
Machines Backed Up report, 628

macros, global excludes, 1073
mailbox access requirements for
Exchange, 1224
mailboxes
exclude specific folders, 1253
redirecting restores, 1275
restore overview, 1265
maintenance server
delegation, 1050
majority node in a cluster, 703
managed media server
copying jobs to, 826
defaults, setting, 805
installing, 786
network connection speed to central
administration server, 806
network interface card, using any
available, 814
pools, 818
upgrading, 795
managed media server, defined, 1593
Managed Media Servers report, 628
manually update server list, for
NetWare, 935
MAPI e-mail notification method, 545,
1114
MAPI, configuring recipients, 550, 1118
master database backup, 1341
master database restore
SQL Agent, 1363
MaxDB databases
protecting with SAP Agent
backing up, 1457
overview, 1439
restoring, 1458
media
adding to the offline location or
user-defined media vault, 291
all media, defined, 257
allocated, defined, 258
append backup to, 355
associating with a media set or
vault, 297
creating default labels, 276
damaged, 296
deleting, 296
deleting vault, 290
displaying media ID, 298
drag and drop, to move media, 294
finding in a location or vault, 289
general properties, 298
imported, defined, 258
moving to a location or vault, 290
overwrite for backup, 355
overwrite options, 270
overwriting allocated or imported, 274
properties, 298
recyclable, defined, 258
retired, defined, 258
scanning bar code labels, 291
scheduling a job to move media, 292
scratch, defined, 259
setting default options, 274
sharing, 1561
statistical properties, 299
testing integrity of, 384
using with Removable Storage, 235
Vault Wizard, to move media, 293
with excessive errors, 296
media capacity, testing before backup
runs, 388
media catalogs, 1547
media categories, 257
media ID, defined, 279, 1593
media label
bar code rule
changing, 282
deleting, 282
in mixed media libraries, 281
bar codes, 280
defined, 1593
imported, 280
overview, 278
renaming, 282
media location, updating, 293
media operations
associating media with media sets, 297
deleting media, 296
viewing media properties, 298
media overwrite protection level,
defined, 270
media overwrite protection, overview, 264
Media Required for Recovery report, 630
media rotation, 415
media rotation in SAN, 1562
media rotation strategies
father/son, 302
grandfather, 303
1616 Administrator’s Guide

son, 302
media rotation, defined, 1594
media server
defined, 1594
running diagnostics on, 188
viewing properties, 188
media server pool, defined, 1594
media server properties, general, 189
media server, connecting to, 1018
media servers
configuring for robotic library
sharing, 1556
media set
creating, 264
default, 263
defined, 257
deleting, 267
overwrite and append properties, 268
renaming, 268
selecting for backup job, 355
shared storage environments,
and, 1561
vault rule properties, 288
wizard, running, 266
Media Set report, 631
media types, specifying for devices, 205
media vault
defined, 287
deleting, 290
finding media in a vault, 289
media vault
renaming, 289
moving media, 290
user-defined
creating, 287
defined, 259, 287
Media Vault Contents report, 632
media vault, defined, 1594
media view, 483
menu bar, overview, 134
menus, described
Help, 1585
Window, 1583
menus, described, Help, 1216
messages
error, 671
Microsoft Cluster Server, using with
Backup Exec, 702
Microsoft clusters
clrest command, 733
Microsoft Data Access Components
(MDAC), installing, 76
Microsoft Data Protection Manager Agent
overview, 1489
requirements, 1489
selections for backup jobs, 1490
selections for restore jobs, 1494
Microsoft SQL Server 2000 Desktop Engine
(MSDE), installing, 76
Microsoft Terminal Services, and installing
Backup Exec, 81
Microsoft Volume Shadow Copy Service
(VSS), and AOFO, 853
minimum quiet time, setting for AOFO, 861
Missed Availability report, 633
mixed media library bar code labeling, 281
Mobile phone notification, 543
Monitor jobs on local managed media
server, 807
mount point, defined, 1594
mounted local drives, backing up files and
directories, 362
Move Media to Vault report, 634
Move priority options in DLO, 1064
Move User dialog box, 1079
moving
media, using drag and drop, 295
MSCS, using with Backup Exec, 702
MSDE, 984
MSDE 2000 components, installed with
Backup Exec, 76
MSDE database instance,
BKUPEXECDLO, 1136
MSDE database instance, DLO, 1136
multi-stage backup strategy, 435
Index 1617
N
Name & Resource dialog box, 514
named transaction
include in restore, SQL 2000, 1365
restore up to, SQL 2000, 1365, 1369
navigation bar, overview, 134
NDMP backup options, 1574
NDMP Option
backing up data with, 1572
backing up resources, 1574
configuring devices, 1572
installing, 1572

overview, 1571
requirements, 1571
restoring data, 1576
NDMP restore options, 1576
NDMP service, starting, 1572
Net Send, configuring recipients, 556, 1125
network
changing a backup network for a
job, 403
overview of backup networks, 398
setting up a backup network, 400
Network Attached Storage (NAS),
protecting, 1571
Network Data Management
ProtocolSeeNDMP Option
network traffic, reducing in CASO, 805
network user data folder, creating, 1074
node, defined, 1594
nodes
configurations in a Microsoft
cluster, 715
defined, 701
disaster recovery using IDR, 747
Microsoft
adding or removing a failover
node, 712
changing the order in which nodes
fail over, 712
nonlogged operations occurring in SQL
7.0, 1357
notification
assigning recipients to alerts, 564
defined, 528
notification, recipients, 1116
notifications
assigning alert categories, 564
clearing recipients, 564
configuring MAPI e-mail, 545, 1114
configuring pager, 546, 1115
configuring SMTP e-mail, 543, 1113
configuring SNMP, 567
configuring VIM e-mail, 546, 1115
methods defined, 1112
modifying recipient properties, 562,
1130
scheduling recipients, 561
selecting recipients for jobs or selection
lists, 565
nsf files
backing up, 980, 1180
NTFS
cluster size, 673
partition, 672
numbering, specify for media label, 277
1618 Administrator’s Guide
O
offhost backup
best practices, 891
host computer, defined, 887
List Snapshot Providers option, 895
overview, 887
requirements, 889
single volume snap, choosing, 894
snapshot provider, choosing, 893
transportable snapshots, defined, 888
VSFW FlashSnap option, using
with, 890
offhost backup, defined, 1594
offline media location
adding media to, 291
defined, 259, 287
offline media location, defined, 1594
offline, when devices display as, 197, 211,
222
off-site storage of backups, 654
online media location, 286, 1595
online, putting device back, 197, 211
open files
backing up with AOFO, 844
unable to back up, 672
Operations Overview report, 635
optimizing remote backups, 363
options
default for job log, 462
Options - Set Application Defaults
Preferences, 139
options, additional Backup Exec options
described, 62
Oracle Agent
authentication for Oracle
operations, 1408
backing up with, 1413
channel time-out, changing default
for, 1430
configuring, 1398
credentials for instances,
updating, 1401, 1405, 1413
database time-out, changing

default, 1429
DBA-initiated backup, 1417
DBA-initiated job settings, creating
template for, 1419
DBA-initiated jobs, job template name
for, 1401, 1406
DBA-initiated restore, 1424
defaults for backup and restore
operations, 1421
features, 1397
installing, 1398
Linux, configuring instances on, 1404
logon account, entering on Remote
Agent Utility, 1402
media server authentication on Remote
Agent Utility, 1402
multiple data streams,specifying, 1417
Oracle instances in CASO, 1413
Oracle Net Service name, 1401
port, configuring for Oracle operations
on Linux, 1407
port, configuring for Oracle operations
on Windows, 1403
publishing Oracle databases on
Linux, 1406
Real Application Cluster (RAC), backing
up, 1414
Real Application Cluster (RAC), listed in
backup selection list, 1406
Real Application Cluster (RAC),
publishing on media server, 1403
recovery catalog, using, 1401, 1406
redirected restore, 1427
restoring, 1422
troubleshooting, 1429
upgrading, 1411
using previous Oracle Agent, 1412
Windows, configuring database access
on, 1402
Windows, configuring instances
on, 1399
Oracle instances
Linux, configuring on, 1404
Windows, configuring on, 1399
Outlook PST files, backing up, 1179
overview, 1501
overwrite default media label, 276
overwrite media option, specifying for
backup job, 355
overwrite protection levels
full, 275
none, 275
partial, 275
overwrite protection period
defined, 260, 265, 1595
setting for media set, 265
overwrite protection, disabling, 275
Index 1619
P
pager
configuring recipients, 553, 1121
notification method, 546, 1115
partial overwrite protection, 275
partition
creating for robotic library, 214
defined, 1595
FAT, 672
NTFS, 672
redefining for robotic library, 217
pass phrase, defined, 1595
pass phrases, 408
password database, Remote Agent for
NetWare Servers, 927
pausing device, 175
performance, increasing during backups of
remote Windows computers, 914
physical check, SQL 2000, 1350
physical only check, available with SQL
2000 only, 1341
PHYSICAL_ONLY utility, 1343
placing scheduled job on hold if test run
fails, 388
point in time log restore option
SQL Agent, 1364, 1368
policies
copying to another server, 440
policy
adding a backup template, 421
adding a duplicate backup sets
template, 436
adding an export media template, 424
changing template rules, 431
creating jobs, 432
creating manually, 416
creating synthetic backup using the
Policy Wizard, 872
creating true image restore, 883
creating using the Policy Wizard, 417

defined, 1595
deleting, 418
deleting a template, 427
deleting jobs created from policies, 434
deleting template rules, 431
duplicate backup sets template
overview, 435
editing a template, 427
importing templates, 426
migrating templates, 421
overview, 415
setting template schedules, 423
template rules, 428
using an example policy, 419
using templates, 420
Policy Jobs by Resource Summary report
reports
Policy Jobs by Resource
Summary, 638
Policy Jobs Summary report, 639
Policy Properties report, 640
Policy Protected Resources report, 641
portal support, 251
post-job command
setting for backup job, 366
setting for restore job, 498
prefix, creating for media label, 276
pre-job command
setting for backup job, 366
setting for restore job, 498
preserve tree option
for backup job, 359
for restores, 494
primary server
defined, 1547
printer, configuring recipients, 558, 1127
priority
changing for scheduled job, 453
setting for devices in pools, 179
setting for drives in pools, 223
setting for restore job, 492
priority for selection lists, 334
priority options in DLO, Move, 1064
priority, Automated User Assignment,
changing, 1064
Problem Files Report, 642
Problem Files report, 642
Process logical volumes for backup one at a
time, with Exchange Agent, 1232
Profile, 1020
back up on log on/off option, 1082
creating, 1020
defined, 977
edit schedule, 1028
logging options, 1029, 1083
profile
copy, 1032
prompt before overwriting allocated or
imported media, 275
properties
active job, 442
alerts, 532
Lotus Domino, 1321
media
general, 298
statistical, 299
report, 602
properties, user, changing in DLO, 1077
protected server, defined, 1595
PST files, backing up, 1179
published drives, defined, 685
publishing
default interval, 920
disabling on remote computer, 920
to media servers, using Remote Agent
for Windows Systems, 919
1620 Administrator’s Guide
R
RALUS
Installation overview, 939
Manual install and uninstall, 953
Manually starting the RALUS
daemon, 954
Manually stopping the RALUS
daemon, 954
requirements, 938
Setting Linux/Unix properties, 947
Uninstalling, 949
Using, 946
Using the Installer, 940
Using with the Backup Exec 8.x and 9.x
Agent for Unix, 955
RALUS.CFG
About, 944
Editing, 945
Format components, 945
RAMS
Backup job properties, 969

Installation overview, 961
Manually starting the RALUS
daemon, 972
Manually stopping the RALUS
daemon, 972
RALUS.CFG
About, 965
Editing, 965
Format components, 966
requirements, 960
Uninstalling, 971
Using the Installer, 961
Using with the Backup Exec 8.x and 9.x
Agent for Unix, 973
reassigning how slots appear, 213
Recently Written Media report, 643
recipients
assigning alert categories, 564
clearing recipients, 564
configuring, 552
configuring groups, 560, 1128
configuring MAPI e-mail, 550, 1118
configuring Net Send, 556, 1125
configuring new for jobs or selection
lists, 565
configuring pager, 553, 558, 1121, 1127
configuring SMTP, 548, 1117
configuring SNMP Trap, 1124
configuring VIM e-mail, 1120
defined, 547, 1116
selecting for notifications, 565
Recovered Jobs custom error-handling
rule, 475
recovering jobs, threshold for, 480
recovery password, setting, 993
recovery points, in Exchange,
overview, 1238
recovery points, setting in Exchange, 1248
recovery requirements in IDR, 1522
Recovery Storage Group, 1260
recyclable media, defined, 258, 1595
redirected restore
See also names of individual agents
using to install Domain Controllers
from Media, 518
redirecting Exchange data, 1273
redirecting SAP data, 1451
redirecting scheduled jobs, 181
registry
restoring, 496
Remote Administrator
defined, 1595
running, 109
system requirements, 109
Remote Agent
installing on a Microsoft cluster, 704
installing on a VERITAS cluster
server, 737
Remote Agent for NetWare Servers
AUTOEXEC.NCF file, 926
installing, 924
overview, 923
system requirements, 924, 933
Remote Agent for NetWare Servers,
backing up
BEDIAG.NLM utility, 935
create BEDIAG.FAX, 935
decompressed files, 934
password database, 927
rights for backup, 927, 928
single server backup strategies, 928
strategies for multiple
administrators, 929
strategies for single administrator, 929
Remote Agent for NetWare Servers,
restoring, 932
Remote Agent for Windows Servers
installing 64-bit using command
script, 107
installing 64-bit using the installation
program, 104
Remote Agent for Windows Systems
64-bit overview, 914
hardware requirements, 914
installing on Itanium-based and x-64
based operating systems, 104
installing on Itanium-based and
x64-based operating systems, 107
installing using the command line, 105
license keys, 914
publishing to media servers, 919
Remote Agent Utility, 917
stopping, 916
uninstalling using the command
line, 106
Remote Agent Utility
credentials for Linux instances,
updating, 1406
Index 1621

DB2 archive logs job template name,
adding, 1467
DB2 DBA-initiated job template name,
adding, 1466
DB2 instances, configuring for database
access, 1402, 1467
DB2 instances, configuring information
about, 1465
default publishing interval, 920
Event Viewer, opening, 917
job template name for DBA-initiated
jobs, 1406
Linux, configuring Oracle instances
on, 1404
Linux, database access for Oracle
instances on, 1407
Oracle instances, configuring logon
account for, 1402
Oracle instances, media server
authentication for, 1402
port, configuring for DB2
operations, 1469
port, configuring for Oracle operations
on Linux, 1407
port, configuring for Oracle operations
on Windows, 1403
publishing to media servers, 919
publishing to media servers,
disabling, 920
Real Application Cluster (RAC),
publishing to media server, 1403
refresh interval, 918
Registry Editor, opening, 917
Services, opening, 917
starting on log on, 918
viewing status, 918
Windows, configuring Oracle instances
on, 1399
Windows, database access for Oracle
instances on, 1402
Windows, updating credentials for
Oracle instances, 1399
Remote Agent, defined, 1595
remote storage, back up data, 363
Removable Storage feature, Microsoft’s
monitoring Backup Exec, 236
using with Backup Exec, 234
using with the SAN SSO, 235
renaming
cascaded drive pools, 187
device pools, 182
media labels, 282
robotic library or device, 176
vault, 289
renaming libraries and drives in shared
environment, 1554
replicated catalog
defined, 1596
replicated catalog, in CASO, 815
reports, 1132
active alerts, 608
Active Alerts by Media Server, 609
alert history, 610
audit log, 612
available in Backup Exec, 604
Backup Job Success Rate report, 613
Backup Set Details by Resource, 615
backup sets by media set, 616
Backup Size by Resource, 617
configuration settings, 618
Daily Network Device Utilization, 620
deleting in job history, 581
device summary, 620
Device Usage by Policy, 622
event logs, 624
Event Recipient, 625
Failed Backup Jobs, 625
Job Distribution by Device, 626
Jobs Summary, 627
Machines Backed Up, 628
Managed Media Servers, 628
Media Required for Recovery, 630
media set, 631
media vault contents, 632
Missed Availability, 633
Move Media to Vault, 634
operations overview, 635
overview, 573
Policy Jobs Summary, 639
Policy Properties, 640
Policy Protected Resources, 641
Problem Files, 642
Recently Written Media, 643
Resource Backup Policy
Performance, 644
Resource Risk Assessment, 645
Restore Set Details by Resource, 647
Retrieve Media from Vault, 648
1622 Administrator’s Guide

unning, 574, 1133
running job, 578
saving, 581
Scheduled Server Workload, 650
scheduling report jobs, 582
Scratch Media Availability, 651
setting notification recipients, 582
test run results, 652
viewing, 574, 1132
viewing in job history, 580
viewing properties, 602
requirements
Central Admin Server Option, 783
Exchange Agent, 1220
Lotus Domino Agent, 1314
NDMP Option, 1571
SAN Shared Storage Option, 1548
system, for Backup Exec, 79
TSM option, 759
reset accounts option, in Desktop
Agent, 1163
Reset Cleaning Statistics, 203
reset dialogs option, in Desktop
Agent, 1163
resource
credentials, changing for restore
job, 516
order, changing, 351
Resource Backup Policy Performance
report, 644
resource discovery
creating job, 339
defined, 1596
used with Exchange Agent, 1220
Resource Risk Assessment report, 645
resource, defined, 1596
responding to active alerts, 535
Restore Access Control Lists, 1576, 1578
Restore dialog box
Desktop Agent, 1201
restore job
Advanced File Selection, 511
advanced options, 494
canceling, 524
copying to another server, 440
creating through dialog boxes, 488
creating with wizard, 487
file permissions, 500
general options, 492
Lotus Domino options, 1326
Microsoft Data Protection Manager
selections, 1494
over existing files, 492
pre/post commands, 498
preserve tree option, 494
redirecting, 517
redirecting Lotus Domino, 1327
redirecting SAP data, 1451
security, 493
Selections options, 490
setting defaults, 520
Restore Job Properties dialog box
SQL Agent, 1362
Restore Set Details by Resource report, 647
restore to named instance, 1377
restoring
ARCserve tapes, 507
byte count does not match, 675
creating a selection list, 510
Distributed file system (Dfs), 505
encrypted data, 414
Exchange data, 1259
files, using Desktop Agent, 1199
files, using DLO Administration
Console, 1088
Lotus Domino Agent, 1324
media view, 483
Microsoft clusters
cluster quorum for Windows 2000
and Windows Server 2003, 730
cluster quorum on node running
Active Directory, 732
Windows 2000 and Windows Server
2003, 729
NDMP data, 1576
registry, 496
Remote Agent for NetWare Servers
volume restrictions, 934
resource view, 483
searching for files, 513
selecting data, 508
using the media view, 508
using the resource view, 508
VERITAS clusters
Windows 2000 and Windows Server
2003, 745
with Backup Exec Retrieve, 1204
restoring SQL master database, 1374
Index 1623

estricted encryption key, defined, 1596
restricted encryption keys, 408
resuming a device, 175
retargeting job, 181
retensioning a tape, 243
retired media
defined, 258, 1596
moving damaged media, 296
Retrieve Media from Vault report, 648
returning to a previous configuration, 655
revisions
defined, 1039
deleting automatically in Desktop
Agent, 1176
deleting automatically in DLO, 1043
number to keep, setting in Desktop
Agent, 1175
number to keep, setting in DLO, 1040,
1175
Revision Control tab, Desktop
Agent, 1175
Revision Control tab, DLO, 1040
RMAN
backing up with SAP Agent, 1452
restoring with SAP Agent, 1454
using SAP Agent with, 1441
using to protect SAP for Oracle
databases, 1439
robotic library
cleaning jobs, 248
configuring, 208
configuring partitions, 214
creating partitions, 214
displaying storage devices, 1542
example configuration, 1541
importing media, 249
lock front panel, 252
portal support, 251
problem with not displaying, 669
redefining partitions, 217
setting up hardware, 1540
unlock front panel, 254
using with Backup Exec, 206
viewing, 1544
robotic library properties
Configuration tab, 212
General tab, 210
SCSI Information tab, 213
robotic library sharing
between Windows and NetWare
servers, 1555
prerequisites, 1555
robotic library, defined, 1596
1624 Administrator’s Guide
S
SAN Shared Storage Option (SSO)
device allocation, 1551
device operations, 1554
installing, 1549
requirements, 1548
SAP Agent
about disaster recovery, 1459
backing up with RMAN, 1452
disaster recovery requirements, 1459
features, 1440
how it works, 1440
installing, 1443
overview, 1439, 1440
privileges, 1444
requirements, 1442
restoring with RMAN, 1454
security, 1444
submitting jobs from remote
computers, 1451
using for backups and restores, 1450
SAP Agent catalog
manually migrating, 1455
migrating from _backint.mdb to
_backint.xml, 1455
preserving integrity, 1445
restoring, 1445
SAP data, before backing up, 1446
SAP database server, restoring, remote
recovery, 1460
SAP database, system level backup
jobs, 1450
schedule, 376
scheduled jobs
changing priority, 453
configuring, 368
configuring default options, 377
deleting, 454
hold, 452
modifying, 448
removing hold, 452
running immediately, 451
running test job, 454
viewing, 448

Scheduled Server Workload report, 650
schedules
setting for templates, 423
scheduling
automatic updates using
LiveUpdate, 126
backup jobs in Desktop Agent, 1183
backup jobs in DLO, 1027, 1082
notification recipients, 561
SAN SSO jobs, 1560
scheduling report jobs, 582
scratch media
creating, 274
defined, 259
Scratch Media Availability report, 651
SCSI
address for devices, 1540
defined, 1596
information about devices, 201
information about robotic library, 213
setting address for robotic library
drives, 1540
SCSI bus, configuring for tape devices in a
Microsoft cluster, 718
SCSI pass-through mode, setting for
devices, 201
search
log file history, 1104
search catalogs, 513
security
changing for Windows systems, 75
restoring, 493
select into/bulk copy option, SQL 7.0, 1357
selecting devices and data to back up, 315
selection lists
configuring new recipients, 565
copying to another server, 440
creating, 328
creating separate for each computer or
resource, 335
defined, 327, 1596
deleting, 331
editing, 332
excludes, 333
holding jobs that back them up, 330
merging and replacing, 330
notification, 327
searching, 337
selecting recipients for
notifications, 565
setting priority and availability, 334
selections
Desktop Agent, backup, 1168
DLO, backup, 1033
user-defined, adding, 323
user-defined, using TCP/IP
addresses, 323
selections list
set up notification, 329
Selections options for backup job, 350
server clusters See also clusters
server list
adding and removing servers, 123
manually update for NetWare, 935
server properties
viewing, 189, 191, 192, 194
viewing media server information, 189
service account
changing, 123
service credentials, managing, 995
service state, 342
services
starting and stopping, 123
starting and stopping on multiple
servers, 1565
Set Application Defaults, Preferences, 139
Set Remote Agent Priority, 363
Setting, 584
setting notification recipients for
reports, 582
Shadow Copy Components File System, 341
shared catalogs, using, 1547
shared device, defined, 1597
SharePoint Agent
about, 1287
adding a server farm, 1300
backing up folders and documents from
a portal workspace, 1291
backing up SharePoint Portal Server
2003 resources, 1303
best practices for SharePoint Portal
Server 2001, 1298
changing the default name of a
farm, 1302
default backup and restore
options, 1311
deleting a farm, 1302
disabling or enabling communication
Index 1625

etween Web servers and Backup
Exec, 1301
disaster recovery, 1297
installing, 1288
overview, 1287
redirecting restore jobs, 1294
redirecting restore jobs for SharePoint
Portal Server 2003, 1308
redirecting workspace data to a file
path, 1296
redirecting workspace data to another
workspace, 1295
requirements, 1288
restoring a SharePoint Portal
Server, 1292
restoring a SharePoint Portal
Workspace, 1292
restoring SharePoint Portal Servers and
Workspaces, 1291
selecting SharePoint Portal Server 2003
resources for backup, 1299
system requirements, 1288
uninstalling and reinstalling the
SharePoint Portal Server
software, 1298
using with SharePoint Portal Server
2003, 1299
SharePoint Portal Server
disaster recovery, 1297
redirecting restore jobs, 1294
SharePoint Services, 342
sharing a backup-to-disk folder, 228
sharing media, 1547, 1561
silent install, 989
silent mode installation, 71, 111, 1597
simple recovery model, SQL 2000, 1336
single block mode, setting for devices, 200
single instance backup for NTFS, 362
Site Replication Services (SRS) database,
backing up, 1227
size, cluster, 673
slot base configuration, 213, 1544
Small Business Server Edition of Backup
Exec, described, 48
SMTP
configuring e-mail recipients, 548
e-mail notification method, 543, 1113
Snap Start, for VSFW volumes, 855
snapshot technology
using with Exchange Agent, 1231
snapshot, used in Advanced Open File
Option, 843
SNMP
configuring notification, 567
configuring system service for
Windows 2000, 571
installing WMI provider, 572
object identifier prefix, 567
traps, defined, 567
WMI, 572
SNMP Trap
configuring e-mail recipients, 1117
configuring recipients, 1124
notifications, 1124
software license agreement, 109
son media rotation strategy, 302
Specified Backup Network feature
configuring, 400
described, 398
specify a date and time for restoring named
transaction, 1365
splash screen, show at startup, 139
SQL 2000
64-bit Remote Agent, 1337
disaster recovery preparation, 1388
physical check after backup, 1341
restore to named instance, 1377
simple recovery models, 1336
standby database, 1335
SQL 2000, backing up
disaster recovery preparation, 1388
Guide Me wizard, 1351
loading state, 1350
standby mode, 1350
SQL 2000, restoring
disaster recovery, 1390
filegroups, 1370
Intelligent Disaster Recovery (IDR)
option, 1388
named transaction, 1369
named transaction, include, 1365
named transaction, to a, 1365
primary and nonprimary
filegroups, 1366
SQL 7.0
agent features, 1336
SQL 7.0, backing up
nonlogged operations occurring, 1357
1626 Administrator’s Guide

select into/bulk copy option, 1357
truncate log on checkpoint option, 1357
SQL Agent
backing up
backup methods, 1348
consistency check after
backup, 1350
consistency check
recommendations, 1341
databases, 1352
filegroups, 1355
strategies for, 1339
transaction logs, 1357, 1358
Windows registry, 1340
Backup Job Properties dialog box, 1347
consistency check,
recommendations, 1341
Database Consistency Check (DBCC),
recommendations, 1341
default options, 1383
excluding files during volume level
backups, 1352
features, 1335
installation, 903, 1337
logon accounts, 1337
overview, 1335
requirements, 1337
restoring
automate master database
restore, 1363
create standby database, 1362
database files to target
instance, 1379
filegroups, 1370
Guide Me wizard, 1365
master database, 1374
point in time log restore
option, 1368
redirecting restores, 1376
Redirection dialog box, 1377
Restore Job Properties dialog
box, 1362
specify date and time for named
transaction, 1365
very large databases, 1366
SQL database backups, restoring
from, 1367
SQL Server, 984
staging data, 435
stalled job status, threshold for, 480
standby database
creating
SQL Agent, 1362
SQL 2000, 1335
starting
Backup Exec, 132
services, 1565
starting, Desktop and Laptop Option
(DLO), 1012
static volume, defined, 1597
statistical properties for media, 299
statistics
device usage, 202
devices, since cleaning, 203
Status tab for a robotic library, 214
step, 320
stopping services, 1565
storage devices
installing, 72
storage limits for user data
Desktop Agent, 1185
DLO, 1021
Storage Location, 1053
defined, 977
deleting, 1059
Symantec Backup Exec for Windows
Servers, described, 47
Symantec Device Driver Installation
Wizard, 174
Symantec Volume Snapshot Provider
changing defaults, 858
Symantec Volume Snapshot Provider
(VSP), changing defaults, 856
Symantec Volume Snapshot Provider, and
AOFO, 852
synchronization
create new sets, 1192
delete synchronized folder, 1193
overview, 1190
Synchronized Selections view, in Desktop
Agent, 1190
synthetic backup
baseline, 866
creating, 873
encryption, requirements for, 869
requirements, 869
template rules, 878
template rules, example, 873
Index 1627

T
synthetic backup, creating, 872
synthetic backup, defined, 1597
system logon account, 148
system requirements
Backup Exec, 79
See also names of individual agents and
options
System State
restoring, 501
System Summary
viewing, 465
tapeinst.exe, Symantec Device Driver
Installation Wizard, 174
tapes
See also media
DLT tape drive, 670
target domain, defined, 76
task pane, overview, 135
TCP/IP
adding for user-defined shares, 323
required for Backup Exec 8.x and 9.x
Agent for Unix, 692
required for RALUS Agent, 938
required for RAMS Agent, 960
template
defined, 1597
template rule
defined, 1597
templates
adding a duplicate backup sets template
to policies, 436
adding an export media template to a
policy, 424
adding backup templates to a
policy, 421
backup template file exclusions, 423
changing template rules, 431
deleting from a policy, 427
deleting template rules, 431
duplicate backup sets template
overview, 435
editing in a policy, 427
importing into a policy, 426
migrating from previous versions, 421
setting template rules, 428
setting the schedule, 423
using in policies, 420
test run job
creating, 386
defined, 385
running for scheduled job, 454
setting defaults, 387
Test Run Results report, 652
testing logon accounts, 352
to a local computer, 81
transaction logs
Lotus Domino DBIID, 1320
overview, Lotus Domino, 1320
recycling, Lotus Domino, 1322
viewing Lotus Domino, 1316
transaction logs, backing up
SQL Agent, 1357
troubleshooting
clusters, 755
TSM option, 775
true image restore
CASO and, 884
creating a policy for, 883
defined, 1597
icons, 886
overview, 880
requirements, 882
troubleshooting, 887
true image catalogs, 885
truncate log on checkpoint option, SQL
7.0, 1357
TSM Option
Backup Exec as TSM client, 760
commands
management classes created by
bex.mac macro, 773
MC_PI management class created by
bex.mac macro, 773
MC_VT management class created
by bex.mac macro, 773
objects, default size, 773
objects, defined, 773
password for backupexec node,
default, 774
policy domain VERITAS,
default, 773
policy set bex_backup, default, 773
registering nodes, 774
time to retain only backup version,
setting, 774
VERITAS policy domain,
1628 Administrator’s Guide

default, 773
components
Backup Exec default node name, 774
Backup Exec default node
registration, 774
backupexec_pi storage pool
associated with bexpi.dsm
file, 773
backupexec_pi storage pool,
defined, 763
backuppool, 763, 773
bex.mac macro, command
details, 773
bex.mac macro, defaults created
by, 773
bex.mac macro, defined, 764, 772
bex.mac macro, errors while
executing, 767
bex.mac macro, using with shared or
individual nodes, 767
bex_backup policy set, default, 773
bexpi.dsm file, as used in bex.mac
macro, 773
creating backupexec_pi storage
pool, 764
creating the bexpi.dsm file, 765
diserror.log error log, 775
dsmfmt utility, defined, 764
dsmfmt utility, using to create a
storage volume, 765
dsmrc.h file, 775
MC_PI management class, 762
MC_VT management class in theory
of operation, 763
Position Information (PI) data
stream, defined, 762
setting backup versions to keep, 774
storage volume, creating with
dsmfmt utility, 765
theory of operation, 762
error logs, 775
individual nodes, 767
registering nodes, 768
registry keys, 768
changing default number of slots in
robotic library, 770
changing default password, 771
communications timeout, changing
default, 769
file space name, changing in Backup
Exec, 770
MC_PI management class in Backup
Exec, 771
MC_VT management class,
changing default name, 771
node name for Backup Exec, 770
objects in Backup Exec, 771
shared nodes, 767
system requirements, 759
troubleshooting, 775
Virtual Tape (VT) data stream,
defined, 763
Index 1629
U
unattended backup jobs, 183
uninstalling
Backup Exec, 124
Backup Exec from a Microsoft
cluster, 707
using command line, 117
Windows Management
Instrumentation SNMP provider, 572
Unique Message Identifier (UMI) error
code, viewing, 459
Unique Message Identifier (UMI),
defined, 1597
unlocking robotic library panel, 254
up on log on/off option in DLO, back, 1082
Update vault using wizard, 293
updating, DLO, 1007
USB tape devices, reconnecting, 173
User Data Folder, defined, 1053
User Properties dialog box, 1077
user-defined media vault, 259, 287
adding media to, 291
creating, 287
user-defined selections
about, 322
adding, 323
Users
properties, changing in DLO, 1077
removing from DLO, 1078
viewing in DLO, 1081
users
access, disabling/enabling in DLO, 1077
adding in DLO, 1075
Desktop Agent access via Profile, 1157
import in CSV file in DLO, 1076

V
managing, 1074
using RMAN to protect SAP for Oracle
databases, 1439
utility jobs, overview, 237
utility partitions
backing up in IDR, 1510
restoring, 504
selecting for backup, 318
vault
drag and drop, to move media, 294
finding media, 289
moving media to, 290
scan bar code labels to move media, 291
scheduling a job to move media, 292
Vault Wizard, to move media, 293
vault rules for media sets, 288
Vault wizard, 293
vaults, moving media, 293
verify
after backup completes, 360
after duplicate backup completes, 383,
877
verify job
creating, 384
defined, 384
version and build information,
displaying, 678
view history, 327
viewing
active alerts, 528
active job properties, 442
alert history, 528
alert job log, 534
alert properties, 532
alerts, 528
Automated User Assignment
properties, 1064
completed job, 456
job monitor, 442
jobs, 1560
Lotus Domino databases, 1316
Lotus Domino transaction logs, 1316
scheduled jobs, 448
system summary, 442
users in DLO, 1081
views, alerts, 528
VIM
configuring recipients, 552, 1120
e-mail notification method, 546, 1115
virtual devices, using in IDR, 219
virtual servers, backing up in a Microsoft
cluster, 728
virtual servers, backing up in a VERITAS
cluster, 744
virus, effect on data storage
requirements, 307
volume level backups, automatic exclusion
of files, 1352
volume restrictions, Remote Agent for
NetWare Servers, 934
VSS
perform consistency check before
Exchange backup, 1250
using to protect Exchange data, 1231
1630 Administrator’s Guide
W
Window menu, 1583
Windows 98/Me Agent
allow registry restore, 688
current status, 688
disable and enable network backup, 687
installing, 686
overview, 687
password-protecting published
folders, 689
publish directories, 688
publishing drives and directories, 689
set directories as read-only, 689
set up network protocol, 690
set workstation password, 688
system requirements, 686
Windows 98/Me Agent, configuring
using DHCP, 690
Windows Automated System Recovery
(ASR) files, in IDR, defined, 1505
Windows Change Journal
option to use for backup job, 359
using to determine backed up
status, 314
Windows Explorer, backups
creating, 378
enabling, 140, 141, 142
overview, 377
submitting, 378
Windows Management Instrumentation
(WMI), adding WMI capability, 572

Windows registry, backing up with SQL
Agent, 1340
Windows remote computers
backing up with Backup Exec Remote
Agent, 915
Windows Server 2003
backing up, 341
disaster recovery, 658
Windows XP, disaster recovery, 658
wizard for DLO, configuration, 1019
wizards
defined, 1598
WMI
installing performance counter
provider, 572
installing SNMP provider, 572
performance counters, 572
uninstalling SNMP provider, 572
working set back up files changed today,
defined, 1598
working set back up files last accessed in (x)
days, defined, 1598
working set backups, defined, 309
Index 1631

1632 Administrator’s Guide